I've been trying to flash TWRP recovery via Odin on my S7 (G930W8), however I would constantly get the verification error. Now I'm trying to reflash the stock firmware but it gave me a Fail on Odin. This is probably my fifth time reflashing the stock rom, and it worked previously today but then it decided it had enough and started giving me a bootloop I guess lol. But yeah, everytime I try reflashing the stock now it fails to do so. I'm absolutely sure I have the right firmware.
My phone is stuck on a bootloop now with the Samsung text and black screen. I can get to TWRP recovery via volume up, power button, and home button, but I can't really do anything there, not even full wipe as it tells me it couldn't mount or something. I can get to Download mode though.
Any advice? I'm really stuck right now.
EDIT: So it looks like this worked: I turned off the device via recovery mode, and then flashed my stock firmware.
Related
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
I flashed the stock n8000 recovery file via odin and it booted me out of the update loop. I had to do it twice tho. I rooted via odin so our fixes may be different.
I used file posted here http://forum.xda-developers.com/showthread.php?p=30450339#post30450339 post 45
Hope this helps a little
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
ej_424 said:
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
Click to expand...
Click to collapse
This need not be so complicated follow directions here http://forum.xda-developers.com/showthread.php?t=1847054&page=6 see post 58 and 39
Stuck, can't restore factory settings
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
bee_rob said:
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
Click to expand...
Click to collapse
I have same Problem
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
ultramag69 said:
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
Click to expand...
Click to collapse
Not working, not go the Recovery Mode, Only Samsung Logo.
I'm having similar issue as Odin keeps failing when trying to flash ROM.
Does anyone know the commands to do it through ADB? I've done it before on my nexus7 but don't know the commands to exactly use for the note. I still can't get into recovery. Only can get into that ODIN mode. I have all drivers and Android ADB installed on PC.
It seems like nothing will write to the NAND. Although my flash count changes now showing my attempts. I might have no choice but to call Samsung and file a warranty claim. I just don't want to lose all the pictures and info that's in my tablet.
Well I got my tablet back yesterday from Samsung. They fixed it. The report showed they replaced some piece that burned out. I forgot the name of it. Unfortunately all my info and stuff was erased. So I had to reinstall everything manually. At least my tablet working like new again. So glad to have it back. Been like a month or so since I've been able to use it. My nexus 7 and galaxy s3 was holding me down in the meanwhile.
This note is a great device. IM seeing again why I've missed it so much. Works flawlessly on stock Tom.
OK so I was playing with my tablet and it froze, so I pressed the power button for 10 secs and it rebooted only to get stuck at the Samsung screen. Tried again to hold power rebooted and no go. So I try boot into recovery and it wont boot so then I tried download mode and it worked.
I then put official JB 4.1.2 firmware via Odin 3.04 and still wont boot still stuck at Samsung screen then I tried several different cwm to try get recovery back and still no go. Tried ics 4.0.3 and nada. Tried updating boot loader still not working.
I dunno what else I can do.
I was using zap blaster rom prior and overclocked the gpu to 512mhz and cpu to 1.42ghz been working great for past 3 months. Now I cant get warranty as flash counter says 6. I suspect I might have emmc bug.
Any help and ideas would be much appreciated.
Well just tried more firmwares but still cant get it going. I'm really puzzled why it wont boot. I thought download mode would have fixed my problem. is there another way to flash the firmware other than Odin?
I have a similar problem. Following this guide: http://forum.xda-developers.com/showthread.php?t=1722745
I tried to restore the P5100 to stock (This is the firmware I downloadad: http://samsung-updates.com/details/....1_3G_plus_WiFi/GT-P5100/TPA/P5100UBDMD2.html)
Now my device is stuck in charging boot loop. I can enter stock download mode (however Odin fails at the "setupConnection")
Any advice? I just want to return to stock.
I was on CM10
I have a huge problem!
I flashed the twrp (http://forum.xda-developers.com/galaxy-s6/development/rom-aterminatorg920f3zpa1m-6-0-11-0b-t3295183 ) via odin ,as said, and then the phone stayed in download mode instead of rebooting or saying something like "finish" (in odin i got a message that the process successed) only the writing "dont turn the phone off". it stay like this for a long time so i had turn the phone off and since then the phone doesnt go past the samsung s6 logo screen and can be booted into recovery mode in any way!!
Ive tried reflashing twrp (many versions) and to use every other combination to get into Recovery mode (so i could do a factory reset or a data wipe) but it doesnt work.
I had this issue. It was because I was running the latest 5.1.1 update and couldn't flash TWRP. My solution was to use odin to flash stock recovery.
Hope that helps
where cani find stock recovery?
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
djxn40 said:
Uncheck auto reboot in Odin and Odin twrp.
Reboot straight from download mode into twrp and flash either smoar rom or the deodexed rom by tdunham. Did you make sure you oem lock is off ?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I already helped him get back to stock so he's at least up and running.
timsmooth said:
Tried to root my Note 5 using Zedomax's method for 6.0.1 and I think something went wrong. My phone ran through the Odin flashing process and passed, but on reboot I was left with red letter saying "recovery is seandroid enforcing" or something to that effect along with a boot loop. I was unable to boot into TWRP. I can still get the phone in download mode, but it seems like every firmware/recovery I try to flash leaves me in the same predicament or it freezes odin before I can flash it. My note 5 is a 920p Sprint model and on 6.0.1. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Use the twrp 3.0.2.0 tar.tar found via @tdunham moar for mm threads note 5 recoveries link. I had same issue until using it.
This thread can be closed. Mrmike2182 helped me fix my issue in another thread.
Please help me!
MrMike2182 said:
I already helped him get back to stock so he's at least up and running.
Click to expand...
Click to collapse
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
N_MBU said:
I have the same exact problem with my phone. Same model and everything. I can make it to Odin mode but when I try and boot the phone I'm stuck on the boot screen with kernel is not seandroid enforcing in red.
Click to expand...
Click to collapse
Download one of these for your phone. .
http://www.sammobile.com/firmwares/database/SM-N920P/
Make sure you uncheck auto reboot in Odin and as soon as it's done and says success disconnect the phone and immediately press and hold the volume down button and the power button at the same time and when the screen comes back up you HAVE to select factory reset wipe if you don't you'll be stuck again just let the little android dude install the update and then the phone will reboot and you'll be ok.
Unzip the md5 you get from the sammobile site and flash only the .tar
This is what he told me that got my phone up and working again. Be warned it is the nuclear option. All of your data will be lost upon recovery good luck.
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
hotspace said:
I hate bringing old posts back to life....But I'm stuck in a series of boot loops that I can't get out of.
I was rooted on MM, decided to go back to stock for a Gallery error I was having.
Downloaded the PD2 from Sammobile, Odin'd it, appears successful.
Reboot
I get to the stock ROM setup screens and the boot loop occurs. I can't complete setup.
I've tried unticking the reboot in Odin and going directly into system recovery...then I do a Factory reset which appears successful.\\Reboot phone, back into the stock ROM Welcome screen....start the setup, and usually after adding WiFi or during Activation reboot.
Any help??
Click to expand...
Click to collapse
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Thanks for the reply. Earlier today I visited my local Sprint store and gave them a crack at it. After about 30 minutes in the store, the tech suggested I leave with it them and they were going to completely wipe it and load the stock image.
After about an hour I went back to the store and he gave me the bad news that he was unable to get it out of the boot loop as well. They've ordered me a new device.
I really trust what you say about letting the phone battery die...but I fear that would fix it and I'd be out a new replacement device.
954wrecker said:
It's extremely common and has one simple solution. Let the battery completely die and then charge it up a little and you won't loop anymore
Click to expand...
Click to collapse
Dude!! It worked. I put the phone in download mode and just let it sit until it died.
Booted it back up and it went straight into hands free activation. And no reboots.
Why does this work?
So, my Sprint S6 is currently in a boot loop after I deleted the operating system because I am an idiot. I can get into download mode, I use odin to flash recovery that I got from updato.com, and I get "Complete write operation failed." I get this every. damn. time. I'm about to lose my mind. I've tried different firmware files across different odin versions to nothing. I'm going to blow my brains out if nothing works. Please for the love of God help.
Edit: Currently downloading the file from Sammobile, 2 hours, God help me.
If you hold down volume down, home and power key simultaneously, then let go and reapply the split second the phone tries to reboot...
It's tricky, but doable.
Do you have TWRP or CWM?
Yes. TWRP is installed.
In my case, when flash twrp went into bootload, but then flash magisk (root), wipes caches and it was normal.
That's in a g920f.