Stuck in bootloop. Please Help!
Recovery booting.
Recover is not android enforcing.
Set Warranty Bit: Recovery.
I flashed Freeza's stock KITKAT tar, no problem.
Flashed CF-Auto Root, no problem. Flashed TWRP, stuck in bootloop.
CAN'T get into download mode!! Is this salvagable???
pocholo36 said:
Stuck in bootloop. Please Help!
Recovery booting.
Recover is not android enforcing.
Set Warranty Bit: Recovery.
I flashed Freeza's stock KITKAT tar, no problem.
Flashed CF-Auto Root, no problem. Flashed TWRP, stuck in bootloop.
CAN'T get into download mode!! Is this salvagable???
Click to expand...
Click to collapse
Always. It's a recovery bootloop, and can recur multiple times.
Oftentimes the recovery you're using could be the one intended for Jellybean. What is the filename of the recovery you flashed? It should be TWRP (or Philz) designated specifically for 4.4.2.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars;508TWRNO3 said:
Always. It's a recovery bootloop, and can recur multiple times.
Oftentimes the recovery you're using could be the one intended for Jellybean. What is the filename of the recovery you flashed? It should be TWRP (or Philz) designated specifically for 4.4.2.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Bless you micmars.
I can update later when home with the exact filename. I believe it was from the link rlmiller posted in the Sacs rom thread. Perhaps it was merely a bad download.
No worries. It appears that the third battery pull was the needed loving touch. I was finally able to get back into Odin and re-flash TWRP.
However, I am a bit wary of booting into recovery now.
The loop occurred after attempting a Boot Recovery from within Goomanager.
Regardless thanks so much for the swift reply.
How
micmars said:
Always. It's a recovery bootloop, and can recur multiple times.
Oftentimes the recovery you're using could be the one intended for Jellybean. What is the filename of the recovery you flashed? It should be TWRP (or Philz) designated specifically for 4.4.2.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I am in the same boat. I have tried pulling the battery started with Volume up and down with and without the home button. All I get is that red android with his patch mocking me. Thanks for your help in advance. I acan't seem to find away out of the loop. Finally got out of loop . Thanks for being so positive. That "always" answer did it for me three times and it finally worked after a day of trying
Related
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Anyone? Any suggestions at all will be appreciated
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Naddict said:
Sure... You can flash a rom immediately following the flash of cwm.... Did you also install busy box?
Which cwm are you trying to use? 5.8.4.7 seems to do me good....?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I tried using that CWM version as well as an older one. Both work and I can get busy box and superuser installed once it boots up. But when I power down and try to go back into recovery, CWM is gone. I do get to keep root though.
iiApotheosis said:
Before your phone boots after installing cwm in Odin do a battery pull then boot into recovery （Volume Up+Home+power) then flash your superuser/root package. It will stick then.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I tried unchecking the auto-reboot button on Odin 4 and 7, and going that route. Both allow me to get into CWM, where I try to flash the recovery v5.zip. Still doesn't stick unfortunately.
My flash counter is up to about 10 now, trying to get CWM to stick..
No1ustad said:
I've tried flashing recovery via Odin and CWM Recovery and it will reboot into recovery just fine. However, when I let it reboot into android, turn it off, and then go back into recovery, CWM is gone. The phone, however, stays rooted.
Any idea what could be wrong or how to fix this?
Secondly, if I can get into CWM immediately after flashing, is it safe to flash a new ROM at that point or do I need to get CWM to stick first?
Click to expand...
Click to collapse
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
cbond007 said:
Flashing 5.8.4.7 after renaming it to recovery.img with mobile odin did the trick for me and it stuck.
I used this guide below
http://forum.xda-developers.com/showthread.php?p=28687877
Sent from a Third Galaxy
Click to expand...
Click to collapse
Thanks everyone. I used CWM toolkit, reflashed the stock recovery, then used odin 3.07 to re-flash CWM 5.5.0.4 and it stuck.
I flashed Devil kernel over my Paranoid Android 2.18 rom, and it booted into devil recovery, with lots of errors. It wouldn't let me flash my previous rom, so I restored a previous jb "boot" [recovery] from a nandroid [advanced restore], then it went into a bootloop.
I tried heimdall, flashing the cwm boot.img from the parandoid android rom [extracted from .zip], still got the recovery bootloop. Then I tried repartitioning with atlas2.2.pit, and thought I was out of the woods when it booted into cwm 6.x recovery.
Then I wiped data and flashed my PA rom again, and this time I had a black screen [yes I know it's hard to see a black screen on SAMOLED screens, but it was dark and I could see the screen coming on and off] bootloop. No SAMSUNG logo, just the screen turning off and on again.
Download mode didn't work until I took out the battery, so I'm gonna try Odin. only thing is I have to reboot into windows since I use linux, but I'm wondering if anyone knows what happened here?
lucky I have a recent TiBa..
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
bbrad said:
If you booted into recovery you should have odined instead of trying too reflash cwm that's just gonna srew it more because its the kernel messing it up not the recovery. Any way get the full stock files for your device put them in Odin get the Atlas pit put it in there and check repartician and when its done flash it in Odin again with repartician not checked hope it works
Sent from my SCH-I500 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Yeah I got it fixed by odining eh03 then CWM and flashing jb ROM..
The problem was I didn't have access to Odin right away so I was trying to fix it with cwm.
I updated my phone to me7 and I followed a root procedure. After I used goo manager to install twrp and clicked reboot recovery but when it rebooted it went into downloading mode and won't let me boot normally! It says on the top could not do normal boot. Please help!!!
Yeah mine is doing the same thing. Not really sure what's going on, heh.
Any help would be greatly appreciated.
**EDIT**
Nevermind...now when I reboot it goes into the OS like normal. Thanks again, man.
You cant install a custom recovery on the me7 ota. Theres a ton of posts on this already. To get past that turn your phone off and use the button combo for booting into odin(vol down + power). Itll ask if you want to proceed or cancel, hit cancel and your phone will boot. To fix you will either need to flash a stock recovery or use odin and reflash me7.
Sent from my SCH-I545 using Tapatalk 2
This got me back into the phone but now I'll have to reflash the stock img via ODIN?
Anywhere I can find the stock recovery?
BoostinBen said:
This got me back into the phone but now I'll have to reflash the stock img via ODIN?
Anywhere I can find the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301259
I need help to revive my ME7 SCH-I545 VERIZON. my device was rooted and had a twrp recovery. accidently I installed 4.3 on stock slot in TWRP. Now I can't boot anymore into sys or recovery. I tried to flash stock rom through ODIN but it failed with "no pit partition error".
I loaded a pit file (which I am not sure is compatible with ME7) and it failed again.
I don't know how to remove the TWRP recovery while the device is dead. It seems to me the logical thing to do because of pit error in odin.
Any idea?
momu
momu said:
I need help to revive my ME7 SCH-I545 VERIZON. my device was rooted and had a twrp recovery. accidently I installed 4.3 on stock slot in TWRP. Now I can't boot anymore into sys or recovery. I tried to flash stock rom through ODIN but it failed with "no pit partition error".
I loaded a pit file (which I am not sure is compatible with ME7) and it failed again.
I don't know how to remove the TWRP recovery while the device is dead. It seems to me the logical thing to do because of pit error in odin.
Any idea?
momu
Click to expand...
Click to collapse
Well it's impossible to have TWRP on ME7 so that might be you're first problem.
Sent from my SCH-I545 using Tapatalk
Are you sure?
joshm.1219 said:
Well it's impossible to have TWRP on ME7 so that might be you're first problem.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As far as I know I had a twrp. I installed it and got a recovery which I encounter the first time: first an option to choose if to continue to system or to recovery. press recovery and then you get all the options like boot options, install, wipe and so on. I had my stock rom me7 installed on the stock slot and I installed a custom rom on slot 1. My mistake was to install the new ver 4.3 on the stock slot instead of an new slot.
I hope that I convinced you. I still need a help! my device is dead!
momu
Oh you had Safestrap not TWRP lol but sorry I never used Safestrap, you should ask in the thread for it.
Sent from my SCH-I545 using Tapatalk
solved
joshm.1219 said:
Oh you had Safestrap not TWRP lol but sorry I never used Safestrap, you should ask in the thread for it.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
joshm.1219 thank you for trying.
I finally found an uncorrupted tar file. I flashed it with odin and everything is working now.
I can say now with certainty that most files out there are corrupted which is very bad news for us users.
momu
Sorry, not a newb. Searched, but apparently not enough.
Knox counter is tripped, but as long as it doesn't affect anything besides warranty, I don't really care.
Problem is, even though I'm rooted, and Odin (3.0.9) tells me that recovery flash was successful, I still cannot boot into recovery (trying for TWRP). I have TWRP on my Sensation, but this phablet is a no-go.
I'm still getting the
"RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
loop.
Easily to get out of, by getting the phone into the download mode, but the issue still remains. No matter what I try, I get the "Done" message via Odin, Rashr, etc. Yet, every time I try to reboot into recovery (to flash a custom ROM), I find myself stuck back in the recovery loop.
Help, please!
alik713 said:
Sorry, not a newb. Searched, but apparently not enough.
Knox counter is tripped, but as long as it doesn't affect anything besides warranty, I don't really care.
Problem is, even though I'm rooted, and Odin (3.0.9) tells me that recovery flash was successful, I still cannot boot into recovery (trying for TWRP). I have TWRP on my Sensation, but this phablet is a no-go.
I'm still getting the
"RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
loop.
Easily to get out of, by getting the phone into the download mode, but the issue still remains. No matter what I try, I get the "Done" message via Odin, Rashr, etc. Yet, every time I try to reboot into recovery (to flash a custom ROM), I find myself stuck back in the recovery loop.
Help, please!
Click to expand...
Click to collapse
What recovery are you using and what Rom ....newest twrp only work with 4.4.2 they will not work ... When you Flash twrp don't let it reboot pull battery and vol up home and power boot into recovery and you Will good just make sure your using the right recovery for bootloader
Sent from my SM-G900P using Xparent BlueTapatalk 2
Thanks, I'll try
Sent from my SM-N900P using XDA Free mobile app
Using TWRP and stock 4.4.2, but no matter what I do, cannot seem to boot into recovery. ..
Epix4G said:
What recovery are you using and what Rom ....newest twrp only work with 4.4.2 they will not work ... When you Flash twrp don't let it reboot pull battery and vol up home and power boot into recovery and you Will good just make sure your using the right recovery for bootloader
Sent from my SM-G900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Ah! Stupid me.
Grabbed the LATEST recovery from #RASHR, and all is good. TWRP ftw!
Sent from my SM-N900P using XDA Free mobile app
This doesn't work for me at all.