I was busy trying to install a mod which didn't go very well. Shouldn't be a big problem, just go back to the recovery and put back the backup.... But there things went wrong....
I reïnstalled the rom, but after that I ended up in a bootloop, but what's even worse is that the recovery also reboots the whole time. For a split second I see the recovery screen but then it reboots again.
So now I can't even get into the recovery. I can get into the bootloader and fastboot, so the solution to this problem but be there somewhere.....
The Factory reset options also doesn't work, because therefore it has to go into the recovery, which reboots... So until now I'm in a sort of never ending circel. Who can help me out of this?
edit:
Found the official RUU here on XDA, so I rebooted the phone into fastboot, and started the RUU update. It's installing now.... fingers crossed...
(doing this update, because maybe in the future it might be helpfull to others).
edit2:
Hmmm getting an error that the phone can't be updated...
edit3:
I had to shut down the phone and reboot, according to the problem solver of the RUU updater... Did that, but the phone rebooted again, after that it tried to enter the recovery again, but this time it actually did. So no recovery reboot. At this moment I'm trying to reinstall by previous made backup.
edit4:
REstoring the backup gave me 1 little error, so I also ran the rom installer again. The phone seems to reboot in a normal way now. Android is booting up again.
Related
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
I've tryed to root the tattoo with superoneclick but it failed to root, since and the end came across some supposely memory errors and when when I boot into system its all apparently the same. I guessed it hadn't done anything so I jumped to the method as described on http://forum.xda-developers.com/showpost.php?p=5835675&postcount=1
I even done the gold card. And tried it. it does some command lines with no errors and at the end it boots normally. The problem is when I try to go to recovery mode it doesn't go to it and when I try to go to normal stock boot loader it algo fails. It tries to enter, I even see the screen for some part of a second but it just doesn't enters.
It boots aparently with no errors into to the system, but somehow somethings seem not work properly like factory reset and screen callibration.
It seems I've got stuck between halfway to nothing.
I just wanted some 2.3.3 goodness to my haunt and I'm afraid I've just messed up her phone!
Any smart and easy solutions? Even back to full stock would be good!
Thanks in advanced!
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
potattoo said:
you can allways (well, as long as its not completely bricked) flash a RUU to go back to stock rom.
for me first time rooting also failed (dont remember the errors exactly), then i installed the RUU, tried rooting again and it worked.
Tattoo RUUs: http://shipped-roms.com/shipped/Click/
Click to expand...
Click to collapse
Thanks!
I thought that could be a solution! I promissed I've been trying to resolve this situation for about 4 days. And I did it!!!
Everytime I ran a root solution it said it failed but they also said it was rooted.
tried again using this app:
http://forum.xda-developers.com/showthread.php?t=761507
Used the CM7 recovery (http://forum.xda-developers.com/showthread.php?t=854152) with described method: http://forum.xda-developers.com/showpost.php?p=9192029&postcount=21
i thought the problem could be not the rooting part but the flashing of the recovery.
Did it step by step and worked!
Thank you very much for your reply!
I was running CM 9 nightly builds for the last year, and decided to upgrade to CM10. In my system settings there was a handly little "upgrade" button which I mistakenly used- and my phone got stuck in a reboot loop. I booted into recovery mode, and tried to restore the phone, but it did not work. It kept sticking at the blue circle boot image for over 20 minutes.
I tried recovery mode again, and every time I went to CW recovery I would get several lines saying can't mount SD card. OK, I broke it.
I then downloaded the factory firmware from samsung-updates.com - and flashed with Odin- just to get my phone to work. It's been 2 hours where I cna't get anything up. After rebooting (from factory firmware) I have the regular samsung s repeatedly coming up, and I'm still in a reboot circle.
Any suggestions or ideas? I need my phone for work, so I really just want to get it up at this point, with whatever will work.
I found the EZBase recovery kit thread, fixed myself Of course, it's the 101th thread I read in my search!
http://forum.xda-developers.com/showthread.php?t=2095519
Sorry, next time will keep searching. Worked to get my phone up and running,w ill now attempt CM10 again...
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
madeofscars117 said:
Hello, so...where to start. Phone was original stock. It randomly froze and started boot looping. I had installed the Sprint update 6.23.651. 6 about a month prior to this. (the update made it sluggish)
So I did research, I went to Hboot, but recovery and factory reset didnt do anything. After selecting either one, it just started looping immediately. So tried fastboot commands, nothing work really except erase cache. ADB did not show anywhere even though my drivers were up to date. Contaced HTC and dowloaded the update application. Put the phone on fastboot, ran the wizard. when it was all done, it said it was finish updating. But was still looping. HTC told me i had to send it in and pay a fee. BS! i did nothing to my phone, they broke it with the updates.
Long story short, i figure how to unlock it. Great, so i started trying to flash updates that had the same CID and Model. To list last few:
1) Guru_Reset_M7_Sprint_1.31.651.2
2)Guru_Reset_M7_Sprint_3.04.651.2
3)RUU_M7_WLS_JB_50_Sprint_1.29.651.7
But none of them worked. Just gave me some error that i cant recal. tried other comands that further bricked my phone, like (fastboot flash boot boot_signed.img) (fastboot flash recovery recover.img). I have been working on this for 3 days, today is the 4th. After this, it would loop once and turn off. So i tried multiple recovery images out of the zips listed above. Those made it so that it finally say entering recovery, but then it would loop and turn off.
Then i kept reading that people are being told to relock the hboot (fastboot oem relock) and then flash the zip. Tried it with those 3 listed above again. the 12 signature error showed up of course.
Tried running the update 6.23....from spring, the wizard gave me some error, basically, my phone is way off to even set back to where it was at first.
After some research, I tried tried cwm 6.0.4.8-m7 to have a standard known recovery image flashed. I had actually tried it before but it didnt work. and for whatever reason, it lunched clockworkrecovery.
Here i erased data/factory reset. Also wiped the calvik data (something like that) since that what it says everywhere to do for first step. (kept a mental note that wouldn't fix my phone since it was further bricked than before i began). But before exiting the recovery mode, i noticed that adb commands were finally working! so i tried the two methods if found to install a rom. Sideload and push. Through side load, it takes forever to reach 100% but once it gets there it says
* failed to write data 'protocol fault (no status)' * {in cmd}
So i tried to push. after pushing it to the sdcard (internal btw) i got to the sdcard and run it. End result. *(bad) installation aborted * {on the phone}
so then im like whatever, lets reboot and see if anything changes. Bootlooping still. Recovery and factory/reset send me to bootloader now (it used to just loopboot). so i flash recovery again. Doesnt work. fastboot erase cache, then flash image, still not working. So i managed to remember some steps i followed that might of been the reason recovery worked. so I flash boot_signed.img, then flash recovery. doesnt work. so fastboot boot boot.img cmd responds but phone freezes, then manually turn it off. then get back into fastboot, flash recovery, erase cache, flash recovery(x3 times). and recovery works.
This is the 3rd time i got into recovery, but it takes me about 10 mins of doing the different combinations of the what i just mentioned before it goes through.
So im at the point where i could possibly get it fixed. But nothing seems to work
I would really appreciate it if someone could help me. I know that the rom has to match my hboot version? but im at hboot 1.6 and the only thing i found was here
http://forum.xda-developers.com/showthread.php?t=2795856
but that only gives me the firmware and the exe that doesnt work for me. I also tried to run the exe and during it, seach my C-drive for rom.zip. Apparently it creates a temporary rom. I pulled it out, it doesnt contain everything
Last thing i was going to do, was put relock it and run recovery. but because im not sure how to make recovery work every time from the get-go. when relocked, recovery didnt work, so i had to flash, thus i had to unlock, spent 10 minutes making it work and forgot that it was unlocked. I could try and see if i could relock and get recovery to run. But it could take forever to get it to work, thus is why im looking to see if there is anything i can do from recovery. (also, both time i was in recovery, i did erase wipe everything, so maybe thats why it wont work after reboot and have to reflash it)
This is where im on.
clockwork recovery window in phone.
phone stuff:
hboot-1.6 something
s-on
os 6.23.651...etc
cid SPCS_001
modelid: PN0720000
the guru zip mention above have the same cid and modelid as my phone according to
http://www.htc1guru.com/downloads/ruu-file-downloads/
Thank You, I hope i am as close to fixing it as i think i am.
Click to expand...
Click to collapse
Make sure you have latest HTC drivers installed on your computer, relock your bootloader and then launch the 6.23.651.6 RUU
Wow, I dont know why I didnt think of that. Everything must be running together.
Alright, so it updated. My phone is back to how it used to be looping like when it first broke. So, from here. Should I unlock it, flash the recovery to cwm, relock bootloader and see if it enters cwm recovery and try to push or sideload a rom?
when relock, i beleive it restarts, so i dont know if it that would stop the cwm recovery from working. Also, if i manage to get all of what i mentioned working. Wouldnt I get the 12 signature error?
Im sorry, its been days and nothing seems clear anymore since I havent been able to fix it
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!