I flashed the following KA6, and I didn't realize it would wipe my apps and contacts. I took a nanroid backup using CWM beforehand, and I'm trying to boot into CWM to restore my backup. However whenever I tell CWM to reboot into recovery or to restore the backup, the phone reboots into the standard Samsung Andriod e3 recovery, which does not allow me to restore my backup.
How can I get CWM to boot up so I can do a restore?
http://forum.xda-developers.com/showthread.php?t=919760
I figured it out.
I'm having the same problem. How did you fix it?
I have flashed, deleted the clockwork recovery files, re-flashed, rebooted, etc, etc.
I can only get the standard blue recovery mode. I run reinstall packages and all it does is quickly shows it's attempting to install the clockwork update.zip file but just boots back into the blue standard recovery mode. Yes I have confirmed the update.zip file is there. I have removed it, reflashed, rebooted, etc. Running reinstall packages takes me into a constant loop.
This really sux.
Anyone got ideas on what my problem might be?
Thanks
Getting the same, and when I go check on my rom backups of my default OS there are no roms to be found after it says it created them successfully.
I erased any existing update.zip, then I told clockworkmod to reinstall, boot into recovery, in the blue menu I selected reinstall package, it rebooted into blue recovery again, and I selected reinstall package for the second time and then it finally rebooted into clockworkmod.
If this doesn't work you can try to follow this guide to get clockworkmod working again.
http://forum.xda-developers.com/showthread.php?t=925400
In the mist of my experimenting trying to get this to work, I did use the app Quickboot which is on the phone already to boot the phone into download mode. Then I did a hard reset (hold power button for 10 seconds), and tried the whole process I described in the previous post. I would guess this is not necessary, but it's just what I did.
Related
So I got my Gtablet today and after charging I immediately began to flash a new rom. My first step was to install CWM. I downloaded CWM internal and loaded the two files onto the root of the internal sdcard. It initially booted into CWM. I rebooted. It would boot into the stock rom but would not load CWM. I would press the + volume and power. Every time it would hang at the birds. I attempted to delete CWM from the internal card and reinstall. No luck. So I searched around the boards and someone mentioned they had the same problem and fixed it by resetting to factory in the settings menu. I tried that. It immediately rebooted and now it hangs at the birds. It says loading recovery kernel but nothing happens. It won't load into the stock rom. It hangs and says loading recovery kernel image, but doesn't do anything. So as of now my brand new gtablet isn't working.
Any advice?
Sounds like you have a 1.2 bootloader and tried to load CWM for the 1.1 version. You'll probably need to nvflash a good stock recovery image into place to let it finish that data wipe or nvflash back to a factory stock condition.
Had ICScrewed running for 4+ months and out of nowhere phone won't boot and is stuck in samsung bootloop.
I have searched and can't seem to get any solutions to work. I have done so much crap I am thoroughly confused as to what I have done and what I haven't tried yet.
Someone please send me in the right direction.
Right now last thing I flashed was "I777UCKH7 OCD Root No BL" oneclick.
Any ideas? I appreciate your help!!
Something changed to trigger the bootloop. If you can pinpoint some event that occured just before it, that might help determine a solution.
From what you say, you must now have stock UCKH7 installed. If you can boot into 3e recovery mode, try a wipe data/factory reset, and clearing anything that it will let you clear. Don't remember the stock recovery very well.
Or, if the bootloop will let you get into 3e recovery, you could flash a custom kernel back onto the phone, enter recovery and clear cache and dalvik cache, etc. Also, if you have a nandroid backup, from custom recovery you can restore the backup to get your phone to boot again.
If you need specialized files to flash to recover the phone, you will find them in the Download Repository, linked in my signature.
creepyncrawly said:
Something changed to trigger the bootloop. If you can pinpoint some event that occured just before it, that might help determine a solution.
From what you say, you must now have stock UCKH7 installed. If you can boot into 3e recovery mode, try a wipe data/factory reset, and clearing anything that it will let you clear. Don't remember the stock recovery very well.
Or, if the bootloop will let you get into 3e recovery, you could flash a custom kernel back onto the phone, enter recovery and clear cache and dalvik cache, etc. Also, if you have a nandroid backup, from custom recovery you can restore the backup to get your phone to boot again.
If you need specialized files to flash to recover the phone, you will find them in the Download Repository, linked in my signature.
Click to expand...
Click to collapse
I didn't do anything I can think of that would trigger this. I can't get into 3e Recovery it says "Deleting Cryption Meta Data" and just reboots.
I flashed via odin "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar" That gets me into CWM Recovery... i wiped data/factory reset... cleared cache... doesn't help.
Then I tried SD card to load a custom ROM and everything on the external SD card is completely not what shows up when i have it in my computer.
I am so lost.
bdkvxd said:
I didn't do anything I can think of that would trigger this. I can't get into 3e Recovery it says "Deleting Cryption Meta Data" and just reboots.
I flashed via odin "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar" That gets me into CWM Recovery... i wiped data/factory reset... cleared cache... doesn't help.
Then I tried SD card to load a custom ROM and everything on the external SD card is completely not what shows up when i have it in my computer.
I am so lost.
Click to expand...
Click to collapse
I just got a custom rom onto /sd with Droid Explorer and renamed it update and it installed but is still stuck in bootloop.
Any ideas? I need my phone for my business I am soo screwed!
Flashed SiyahKernel v2.6.14 and with stock rom it works. Thanks!
Be sure to make a nandroid backup once you have it configured the way you want. Restoring a nandroid backup is the first thing I would try if that type of problem ever happens again.
Resolved - when after many attempts to boot into recovery I gave up and downloaded the Odin version of CWM and was trying to go into boot mode I accidentally managed to go into recovery and was able to recover. I think I will stay away from goo manager or rom manager - neither worked for me. Never had problems just following posted steps on XDA.
I decided to take the plunge and flash my first rom and now my phone is stuck on the CM9 boot loop. I had rooted with CMW through odin followed by superuser. I was on stock ics. I replaced cwm with twrp. No problems up to this point I then downloaded cm9 and the gaaps with goo manager. then tried to flash it after backing up, deleting data, dalvik and cache. It did not work but instead booted back into stock with all my data gone. I added back in my google accounts and wifi password. Then downloaded quick boot. Booted into recovery and installed the CM9 and fgaaps zips.
Now it just cycles in the cynagen bootloop ans will not boot into recovery. In my attempts to get boot recovery started it did once go into download mode. Anyway to recover using odin?
So you are up and running okay ??....g
Hi everyone, I have a problem with my phone.
It is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as what the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go", expecting that it would work. It said "Rebooting..." and booted to recovery mode, so I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. And, this is where I discovered that CWM has a rainbow color mode. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted to Recovery Mode.
I tried . . .
Odin, but since it boots only to recovery, Odin isn't detecting it.
Wiped the data, cache partition, and Dalvik cache. Then restore.
Can this be fixed? I badly need help.
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Any inputs will be very much appreciated. Thanks.
No intention of giving the "Rashr" app a bad name. I just didn't know how to use it.
Endroyed said:
My device is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and I got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go" with expecting that it would work. It said "Rebooting..." and it booted to recovery mode. And I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted into Recovery Mode. Can this be fixed?
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Click to expand...
Click to collapse
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Cheers!
manojkumar8552 said:
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Click to expand...
Click to collapse
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Finally fixed it!
What I did:
1) Flashed the stock Recovery. I was surprised it was able to boot to Android cause I was thinking that the zip is only the stock recovery. It had errors though. Home Screen won't appear or load.
2) When rebooted, it got stuck in SAMSUNG boot animation, but it was all good cause Odin was still able to detect it which means it can still be rooted. So . . .
3) Flashed CWM Recovery v6.0.3.6
3) Wiped data, cache partition, and Dalvik cache.
4) Restored the backup.
Endroyed said:
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Click to expand...
Click to collapse
No Problems Buddy !!!
Step by step getting all f,,,, Fundas of Android soon
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
SOLVED!
zhzhou said:
Hello,
I have a Kobo 10HD and rooted and installed CWM v6.0.5.1. I made a backup before and then installed Titanium Backup update.zip. Installation of that zip caused a bootloop (back to CWM). No problem, I thought, I can just restore the backup I made. No dice. I tried to restore the backup and still bootlooping. I even tried to installed the stock ROM ZIP and it fails with the message: (from recovery.log):
nv_copy_blob_file: couldn't get the device path
script aborted (no error message)
script aborted (no error message)I:Legacy property environment disabled.
E:Error in /data/media/0/macallan-ota-932.zip
(Status 7)
Installation aborted.
I have read that some people have had success installing this zip using stock recovery, but I have no idea how to get stock recovery.
Also, I noticed using adb shell that CWM does actually put all the files back into system and other areas during the restore. Upon reboot, and subsequent bootloop, the system files are gone. It must have something to do with an automatic script that is running after restore.
Click to expand...
Click to collapse
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Hi zhzhou!
Just a quick question:
do you happen to remember if stock recovery for Kobo was CWM? I'm in process of restoring stock ROM +recovery and little bet surprised to see CWM after flashing stock recovery
Thanks a lot!
zhzhou said:
After a few more hours of fiddling, I was able to get the device back up. I wiped absolutely everything manually with CWM (format /X) instead of Wipe/Factory Reset. The factory reset was not clearing the SD card, but format/data and /data/media cleared it. I then applied the stock zip that is available via adb sideload. Installation failed with the same error, but I rebooted with the adb reboot command. The device booted back into Kobo stock requiring several updates. It actually got stuck repeating one update several times until I booted back into stock recovery and cleared data and did a factory reset. The update applied correctly and then another upgrade came (a total of three upgrades). I rooted again and we are back in business.
For some reason, I think the key step was manually wiping /data/media. I'm not exactly sure why this would cause a bootloop for CWM restore. Anyway, I hope this helps someone else who may run into a similar issue.
Click to expand...
Click to collapse
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Thanks for quick reply! I had CM on it but had some artifact issues so wanted to revert to full stock, even recovery
zhzhou said:
Stock was definitely not CWM. It was a long time ago and I no longer have the device, but I think CWM was still present after restoring stock. I think you'll need fastboot if you want to flash the stock recovery image back on. But why do that? TWRP is now available for the device.
Click to expand...
Click to collapse