[Completed] Help! Stuck on Samsung boot screen! - XDA Assist

Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!

Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk

dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.

Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..

In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps

Related

Unable to flash ROMs

Hi guys!
Yesterday I successfully rooted my NS (it is a European SLCD model with stock 2.3.6 on it) following the newest guide on nexusshacks.com. So I ended up with TWRP recovery.
Then I thought the easiest to install CM is via Rom Manager. Therefore I had to change recovery for CWM. (I flashed the latest one.)
And here comes my question: why am I unable to flash CM?
First I tried it in Rom Manager, after wiping everything and rebooting system nothing happens, except for a big yellow exclamation mark.
Then I downloaded the proper CM myself and I tried to do the whole process manually in recovery menu. After wiping and choosing update from SD card I get a message like the process is aborted.
I also tried with an older CWM and with other ROM.
Any suggestions?
Thanks a lot
Sent from my Nexus S using XDA App
Boot into bootloader, then flash recovery via fastboot.
fastboot flash recovery recovery.img
stock firmware will rewrite your recovery after each boot. flash recovery then flash this right after.
Follow what SEAN SAys..............He is a Master in all these , and he helped me with details to root, flash cwm, make it sticky and flash custom ROMS.
It took me 5 minutes to do all those , and Now I am switching Roms like I switch my underwears every day twice.
I must say, Sean has the best possible way which is like a finger click.

Galaxy TAb 7.7 brick, please help

Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
I also tried to flash it with .pit, PDA, PHONE and CSC. I got this screen and then stopped and Odin says "Now Writing, Please wait about 2 minutes."
I appreciate your help!
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
TML1504 said:
same problem here, but caused from rom-manager! did nothing more than using the "reboot into recovery" option, i did NOT flash anything with rom-manager before!
download mode works, recovery works, but i can flash what i want, after turning the device on the "samsung 7.7" stays for about 30sec, then it reboots ad infinitum!
any ideas?
i'm within the one week were i can exchange the device without any problems, but i want to fix it myself if possible!
thx in advance!
Click to expand...
Click to collapse
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
(CWM could not fix this filesystem problem.)
(areyou sure rom manager is compatible with the different partitions on the 7.7)
Remember you will loose all user data !!!!!
Click to expand...
Click to collapse
again thx,
but the problem is seems to be "deeper" than only a corrupt /data!
The tab doesnt boot further then "samsung 7.7", if data is corrupt then
at least android will load (bootanimation) and go into a bootloop in some stage!
Also, I didn't change or install or flash anything in rom-manager, I "only" used the reboot function!
After reflashing the device with repartition and HongKong.pit I think I messed up the partitions totally, so I would really need the PIT for 6810 (6800 has different partition layout) to repair this!
But as it seems no one has this PIT or is willing to provide it,
so I ordered an new tab which will arrive in the next hours, and return this one within the next days!
Where did you find the PIT file ? You may just destoried the partition. God bless you!
matth3w said:
Hi,
My SGT 7.7 seems brick after I took it out of my bag. It gets stuck and stays on the boot screen where says "Samsung Galaxy Tab 7.7" for a few seconds, and then just keep rebooting.
It is able to go into the Download Mode when I press "Power+Vol-", but no response when I press "Power+Vol+". I tried to flash all kinds of firmware with Odin, but nothing work.
Click to expand...
Click to collapse
I have a familiar problem....
I have not flashed or rooted my device - it is exactly how it came out of the box...
One morning while using it it froze - I did are reset by holding the power button down and then let it reboot but when it did it can not get past the "Samsung Galaxy Tab 7.7" screen.
Can get it into download mode, but if I go to recovery mode then all I get it a headline saying "Manual Mode" which grabs some manual .apk files and then just goes back into the boot mode with the "Samsung Galaxy Tab 7.7" screen.
Any ideas?
Had a Galaxy Tab Original and got the Galaxy SII and have mod them to death - just though for this one I would leave it original and enjoy the OTA updates as the were delievered - especially considering ICS in a matter of days
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
suwandiapr said:
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
yes, that is what he means.
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem.
Obviously you will lose all user data!
suwandiapr said:
If you can boot into download mode you can call this a soft brick..
dont use ROM manager and install clockworkmod from that, incompatibility of cwm recovery will brick your phone..
Use odin only on PDA slots, you dont need repartition or pit files..it seems you got a corrupt recovery..
Click to expand...
Click to collapse
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
davp said:
Also, if you still have trouble after the first flash, you may need to go into samsung 3e recovery and do a data wipe/factory reset. Then flash again. Since these are non-wipe firmwares, simple flashing may not clear a corrupt filesystem!
Click to expand...
Click to collapse
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Aspi914 said:
Suwandiapr - Thank you for this. When you say "Use odin only on PDA slots" you are suggesting that I will have to download and install a stock ROM aren't you?
Cheers (and again thank you)....
Click to expand...
Click to collapse
Yes you right, thats what i mean..
TML1504 said:
thx, but as i said i DID NOT FLASH OR INSTALL ANYTHING with rom-manager, i only used the option "reboot into recovery"!
and i used odin to try to unbrick my device (i flashed a dozen roms as well as the sbl etc.), without any success. also, till now nobody has provided a 16GB PIT for 6810, therefore i returned the tab and grabbed a new one!
Click to expand...
Click to collapse
Im sorry , my answer cannot solve your problem.. You say your device "stuck on Samsung logo" right? your recovery and download mode seem ok, from my experience its because /data corrupt or something crash on your filesystem..
If you can go to recovery menu, do factory reset,..
I cannot help you with pit.file coz i actually dont have the device right now..
Aspi914 said:
Thank you Davp...
Ok...got the P6800ZSLA2 stock ROM and have managed to get it back...while I don't want to have to re-do all the data, I think I will take your advise and do a data wipe/reset.
Click to expand...
Click to collapse
Good luck..
davp said:
I have seen similar symptoms on mine. it turned out to be corrupt /data filesystem. I had to use the sammy 3e recovery wipe data/factory reset option. And then reflash with odin.
Click to expand...
Click to collapse
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
白い熊 said:
I've experienced a similar problem with corrupt /data and couldn't overcome it.
How did you use Samsung recovery when you had CWM recovery flashed?
Click to expand...
Click to collapse
You either get it from a full flash of stock firmware, or make your own tar with just recovery.img in it (extracted from stock). And flash with odin in the pda.
It is handy to be able to switch recoveries. CWM doesn't seem to match the 3e data wipe/factory reset.
The problem was:
I was playing a game, in the middle of it the Tab reset, I've never had it reset. Then it rebooted to the Samsung Tab 7.7 logo.
I thought, I'm lucky, made a CWM backup. So tried to restore the CWM backup. When the restore got to /data the tab rebooted again, i.e. something was messed with it.
So got stock firmware, flashed it from PC odin, flashed with success. But rebooted to the logo again.
Tried to get into the stock recovery, but it would only show "Updating..." something, I don't remember anymore, but the stock recovery wouldn't boot. Flashed it a couple of times, same result. Had to take the Tab back to the store...
Am kinda afraid to mess with it now, since I don't want it to happen.
So am wondering what to do if the same happens, or just forget CWM and flash stock recovery.img just to be safe?
I had similar issues after hard power-off [long hold power button]. Confirmed with adb into insecure cwm recovery that /data was corrupt. It explained why my restores stopped at /data.
Cwm data wipe, or format data did not help.
I flashed the stock 3e recovery.img in a tar with odin.
3e data wipe/factory reset. Reflash whole stock firmware with odin.
Check system boots ok.
Reflash cwm, then do restore ok.
I have seen stock 3e recovery fail to start properly. It seemed to be related to files/directories on the external sd card. It came up and said something like 'manual mode', 'updating'.
I tried clearing cache and hidden.
I know I deleted at least tmp_sec_fota directory off the external sd card, maybe someting to do with fota is upsetting our tabs from time to time.
Yep, exactly, that's it, it was "Manual mode" and "Updating", same symptoms, I couldn't get past it.
So what you're saying, I had a MicroSD in it, and that's why it was stuck at this? Not sure if I had an SD in it, but I flashed stock like three times, and then still couldn't enter 3e recovery, all the time had this "manual mode" come up...
Thanks for the guide of what you did.
Am downloading the latest Thai firmware now, to extract the stock recovery, so that I'm ready just in case.
Do you just tar the recovery.img and use that for flashing if necessary? No special permissions, nothing?
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd. It is possible the problems are in multiple locations,
It is also possible that multiple attempts have an effect.
I personally feel I need both stock 3e and insecure cwm [and odin and adb] to be able to recover this tab. The broken 3e/reboot was my worst experience on this so far.
Use linux tar or the tab's busybox tar, to create an uncompressed tar with recovery.img as the only file. Do not use 7zip to create the tar, it didn't work for me (although it works fine to extract from the stock).
davp said:
Sorry, not as clear cut as that... I did three things, cleared cache, cleared hidden, and
then started deleting files on sd.
Click to expand...
Click to collapse
You mean you did this in CWM recovery? Because I hastily flashed the stock ROM when it wouldn't boot, and then I couldn't get into the recovery anymore and there was no way to flash CWM recovery from PC Odin, or is there?
SD you mean internal? Since with external you just pull it out...
This was my worst experience as well, and want to be ready if it ever happens again.
So to sum it up. If the /data is messed up, should we do the following?
1. In CWM recovery clear cache, clear hidden.
2. Flash stock e3 recovery.
3. In stock recovery wipe everything.
4. Flash stock ROM.
5. Boot.
6. Flash CWM recovery.
7. Restore backup.
please i have the same problem,where i find the stock e3 recovery?
thanks Davp!
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
please,post a link for download the recovery.img tar for to flash with odin.this is my last hope!

Problem with TWRP and CWM

So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
TheBuzzard said:
So, last night I was updating my phone to a newer version of Paranoid Android. In the process, I accidentally flashed TWRP over my preexisting flash of CWM and, in both being unfamiliar with TWRP, and an apparent conflict between the flashes, it soft bricked my phone. Most of my day has been spent recovering my phone.
I was able to restore my phone to stock using the excellent guide found here: http://forum.xda-developers.com/showthread.php?t=1840030
Then spent the next couple of hours installing updates, at which point I was eager to reflash my custom roms, etc.
Problem is, I can't get the phone to boot into CWM (or TWRP). Just goes to stock recovery. I've tried flashing the lazy way in ROM Manager, and in Odin (reads PASS), but it always goes to stock recovery. For that matter, in trying to flash with ROM Manager, it reads "an error occurred while trying to flash..."
Ideas?
Click to expand...
Click to collapse
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Do you want CWM or TWRP? If TWRP, you could just download GooManager from the Play Store and press Menu/Install Open Recovery Script.
For flashing either via Odin, deselect auto reboot in Odin then flash the recovery tar. Once its passed, pull the battery and boot directly into your custom recovery.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the advice, but I got it working.
Tried Odin one more time, and it's booting into CWM properly now. Not sure why it didn't "take" the other 2-3 times that I followed the identical procedure, but it appears that my problems are fixed now.

"Install aborted" when trying to flash roms?

The error message doesn't get any more specific than that.
I have a Samsung Galaxy S Relay 4g, and I followed this guide to root it, using the files provided: http://forum.xda-developers.com/show....php?t=2256821 It seemed to work perfectly.
Then I backed up the factory (4.0.4/touchwiz) rom, used the recovery to wipe user data, cache partition, and dalvik cache, and then tried installing the stock kitkat zip. It got a little way into the process and then stopped, saying "Install aborted". It was able to boot into the stock (4.0.4/touchwiz) rom after that, so I did some googling and tried again with a version of Liquidsmooth specifically for the device. Same problem, except it said "Error 7" this time. I fixed that, tried again, and the "Error 7" message went away, but the "Install aborted" message stayed.
Now whenever I try to start it up, it boots straight into recovery mode. I tried restoring from the backup I made at the beginning, and it says "md5 mismatch". I've considered trying to flash the rom with Odin, but 1) the files aren't md5s/tars? and 2) I'm hesitant to do anything that may damage my phone further.
I've also tried googling around, with a lot of not-quite-helpful results. Any help would be amazing and highly appreciated.
Thanks!
TL;DR phone won't boot out of recovery mode, nor successfully flash any rom.
Usually there is an option to skip a md5 check when flashing from recovery. If you are confident your using a good copy of the rom, just skip the check and install.
croogrog said:
Usually there is an option to skip a md5 check when flashing from recovery. If you are confident your using a good copy of the rom, just skip the check and install.
Click to expand...
Click to collapse
I think I did that, though? The "toggle verification" option, right?
if your still stuck,
I would try using odin to flash the recovery again,
then flash a "recent" recovery, (I'm using the cwm recovery 6.0.3.7)
and finally try to flash the rom (possibly including the modem and bootloader)
Good luck

I cant install TWRP on SM-P900 ;(

Hi
This is really frustrating. I own many Samsung devices and never had any issue installing twrp, so I am not a noob when it comes to firing up Odin and flashing the image however I am stuck with this device.
I used couple guides with no success. ;( I cant get rid of the Samsung recovery and replace with TWRP. Odin says success but that is just a lie.
I tried both the lollilop bootloader and the older one then TWP with various versions (3.1x , 2.8.x) No luck.
Can anyone please provide me "working files" with "simple steps" in case I am missing out on some minor details. This is SM-P900 Kitkat 4.4.2 version.
- I flash the bootloader using the BL slot in dl mode
- I reboot to downloader again and and install TWRP
- I type adb revoot recovery
Boom, I am back to frigging Samsung recovery
Hi ,
This is a follow up
The only guide that worked for me is this one. It might be helpful to others.
https://forum.xda-developers.com/ga...guide-install-official-lollipop-p900-t3154362
I had trouble getting TWRP to take at first too. It seems Samsung overwrites the recovery upon rebooting so even though TWRP flashed successfully it just gets overwritten when the system restarts. The simple solution for me was to disable the Reboot option in Odin, install TWRP, manually shut down and then enter Recovery mode. Hope that helps. I came across this suggestion either in the thread linked to above or while googling.
Im installing into properly rooted and I have twrp 2.8.7. I want 3+ TWRP.
I flash with PDA/AP and with "autoreboot" unchecked. I power off and power+home+volUP for recovery.
Tablet enters a "enttering recovery" bootloop which can be only disrupted by going into power+home+volDWN to enter Download, and than I can flash with ODIN 2.8.7.
2.8.7 is the latest I can boot into. WHAT IS WRONG?!!!!!!!!! I lost hope, with flashing 100x
Did you try updating TWRP from inside TWRP?
Sent from my Samsung SM-P900 using XDA Labs
try do a full wipe from stock recovery . after that flash twrp selecting the ap and bl in ODIN twrp3.1....tar booth of them (AP & BL)
no no no i tried everything. but than I found out this post : https://s4.postimg.org/s3pel2ekd/this_guy.png and that solved the day!!
With p900 work perfect, but install hard. With this twrp 3.1 i install lineage 14.1, all works good.

Categories

Resources