Related
Hi,
Currently using latest firmware KI3 with root.
I'm able to use CWM, backup, install zips, everything.
However, if i install a ROM trough a ZIP, i get a boot loop.
Only way to get back the phone, it's to install via ODIN with latest KI3.
Even tried with Litening Rom, and got the boot loop.
Any ideas ?
I was very keen to return to CM7.
Tx in advance.
Did you exactly what's mentioned here?
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
Did you try flashing a old stock ROM like KH3, root it then try from this base?
I went from Villain ROM 2.3.5 to CyanogenMOD without any problems.
It's essential that you flash CyanogenMOD !TWICE! in a row when you're coming from a stock ROM.
Thanks.
Gonna check, as soon as i'm @ 127.0.0.1
Same behaviour, back to boot loop.
Tanx anyway!
I had a similar problem so here goes my help.
Cf root kernel uses a modified version of CWM that isn't compatible with CM7 or something like that. So what I did was flash this kernel http://forum.xda-developers.com/showthread.php?t=1118693. Get the kernel with CWM 5.x.y.z With that I got a compatible version of CWM and from there I flashed CM7. It is important that you do a full wipe, wipe cache, wipe dalvik cache, format \system, everything so you don't get any trouble. THen you flash the CM7 zip file, when tha t is done, flash the zip again for a second time (don't reboot just do it after the first flash). After that reboot. That worked for me at least.
A tip: If you can't reboot your phone and you have no ROM zip file to flash via CWM you can mount usb storage from CWM for putting the ROM in sd card and flash with CWM. That way you don't have to use ODIN to recover.
Tanx Tomas.
Tried with CWM 5.x.y.z and upon "WIPE" always got an error for mounting partitions.
Could't mount CACHE, SDCARD .....
Tx anyway.
Back to ODIN, back to stock 2.3.5
PS : I have to get a JIG to reset ...
I just did the biggest F-Up of my flashing life. While following QBKing77's Rooting & CWM with unlocked, at approx 3:50, during the flashing of the root SYSTEM.img file, rather than that file, I used the wrong file to flash used an IMG file that was meant for cwm, which is a completely different task.
So now I am trying to get into fast boot and try to do it with correct SYSTEM.IMG, then to find out I never got it downloaded, the link was deadand now I can not find where to DL it from. I must've not been paying attention and got ahead of myself.
Anyone know where I can a mirror of the file found here. Its the first link in the root section labelled "moto-fastboot flashable /system image".
Am I screwed? Does anybody have a copy of that system.img file laying around. I can not find any mirrors. That is the only way I can see this getting fixed bc I can still go into fastboot mode.
ckeck this ????
http://rootzwiki.com/topic/4137-pudding-photon-pudding-bootloader-unlock-updated-8302011/
Use at own risk. ???
Can u get into rsd mode and flash 154_5 sbf
Sent from my MB855 using xda premium
Important files
Thank shabbypenguin for those
If you can get into rsd mode and connected/recognized in rsd lite you should be able to flash one of those sbf files and return to stock.
I read the instructions carefully! It said to put the oven on 350 degrees for 10mins but for some out of this world reason I put it on broil and let it cook for 20mins :/
Sent from my MB855 using XDA App
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
enzyme said:
LOL no kidding Custodian. I did get a laugh out of that.
Thanks CubanLuke & ShabbyPenguin. I did use RSDLite to flash the current sbf you directed me to, I can boot into the phone again. Thanks again.
Now as to how to proceed, I will have to unlock the bootloader again, np, but when I run into that very step where I broiled it, the rooting via speedboot.... would it be okay to root using AIO instead because I can not find the SYSTEM.IMG needed to follow along w/ the video using this method.
Can I just root a different method, then proceed on with CWM recovery, then flash rom from the video?
Click to expand...
Click to collapse
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
SOLVED!!! THANK YOU EVERYONE!
KTT16 said:
- Unlock using derpunlock.sbf
- use fastboot to erase recovery and install CWM recovery
- boot into CWM
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Click to expand...
Click to collapse
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
enzyme said:
SOLVED!!! THANK YOU EVERYONE!
Thanks KTT. Okay, I'm back on track now. I am unlocked again, rooted as well. but I am not sure about 2 things. This will be my very first android rom flash and just coming from a big whoopsies, I just want to be sure.....
1) Format system: in cwm recovery, which option is that? I don't see "format system" in the main or advanced menu. Maybe its worded differently?
2) Flash ROM: I can only assume its either "Apply Update from SD" or Update from SD". Not sure which one though.
Click to expand...
Click to collapse
1) Format system is in the "mount" options. Although it's unneeded to flash a ROM. Personally I just wipe data/factory reset and then wipe cache and have zero issues. Others may tell you different though.
2) "Install .zip from SD Card" then select whichever .zip you're looking to install.
Sent from my MB855 using xda premium
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Flashing the 198_7 sbf unroots and relocks, so you're back to square one.
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Reboot into stock recovery, when you get the recovery logo thing push both volume up and volume down at the same time to get the recovery options. Then do a factory reset and it should boot for you. After that, root and unlock again. And you didn't have the Market because you forgot to install Gapps...
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
The reason cm7 didn't have the market is that you needed to flash gapps. Try doing a hard reset. http://www.hard-reset.com/motorola-photon-4g-hard-reset.html That should do it.
try the 154 sbf
enzyme said:
Okay well I am in some trouble again. successfully flashed an alpha cm7.1, but it didn't have market and the one i installed did not work so decided to flash to cm7.2 via CWM. When it booted I didn't really see anything change, later realized that maybe I was suppose to wipe/format in cwm first(idk).
So I decided to flash 198_7, same one that I used to restore back to stock earlier. But I did not get back to stock. The process was 100%, it told me to manually turn on the device, which was in rsd mode. So I unplugged, pulled batt, reboot. The phone now starts up until the pulsing Moto logo then screen goes black, then it loops.
In the process I lost CWM & unlocked. So trying to flash a ROM via cwm is no longer an option. Any thoughts?
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
i had the same problem i think and was going thru boot loops but some one told me to start into recovery when you try you get that ? android screen from there hold down volume up and down at same time then wipe phone booted up fine after that.
It worked like a charm. Thanks. I'm still very new to android and hate to admit it but will be running into problems like these again. The best way to minimize it for me is, not only follow certain directions correctly to get out of these binds, but to understand them.
- So theres an image of the stock ROM stashed away on the phone regardless? And it can be accessed only via the stock recovery? Because after I succeeded in flashing cm7.1, I did a factory reset once from settings>privacy and that restored me to a fresh CM7.1. The factory reset from settings>privacy and in CWM is the same, but both different from the factory reset via STOCK RECOVERY?
- Also what would be the correct method to go from one custom ROM to another? Would it be this? :
(in CWM)
- Format system
- Wipe data/factory reset
- wipe cache/dalvik
- Reboot recovery
- Flash ROM
Or can I just jump to install from zip ?
- Also regarding SD Storage (internal), only holds storage files? So on any fresh ROM there shouldn't be anything in that partition relating to that new ROM yet right? So I can delete things without worry?
You should not have to reboot into recovery, once your wipes are complete, normally you can just flash your ROM of choice in the same recovery session.
Before I flashed anything I would make a backup with CWM so you don't have to keep rooting and unlocking. You can just restore your backup.
Sent from my MB855 using xda premium
After flashing 198 7 sbf, all u need to do is flash derpunlock not go through oem unlocking, then reflash recovery.
Simple generic process for going between roms (assuming already unlocked + cwm recovery flashed; process may be different for some roms, always make sure to read directions, but this is the general concept)
1. Download rom (and gapps if necessary) and put on your sdcard
2. Boot into recovery and make a nandroid backup
3. You made a nandroid backup right?
4. Secure your nandroid backup (move it to your pc or something).
5. You know where your nandroid backup is right?
6. Wipe data/factory reset.
7. Install zip from sd (flash), choose the rom.
8. Reboot system.
At this point your rom should be all set. If for some reason you don't like it, simply boot into recovery and restore your nandroid backup. You can even make nandroid backups of various roms if you want to swap between them for whatever reason.
Hi,
yesterday I tried to upgrade to CM7.2 from a nightly. As I've been doing, I put the .zip in the sdcard and flashed it with ROM Manager (wiping everything). After flashing it, my phone stucked at HTC white screen and there is no way to switch it on, it stays at this screen all the time.
For my disgrace, it's S-ON, so I can't boot into recovery and restore anything. I've tried to restore a nandroid with fastboot and it doesnt't work (says "Failed (remote: signature verify fail)").
Any ideas? It's definetly bricked? Is there any hope of repairing it?
Thanks in advance (and please forgive my poor english xD)
vitiin92 said:
Hi,
yesterday I tried to upgrade to CM7.2 from a nightly. As I've been doing, I put the .zip in the sdcard and flashed it with ROM Manager (wiping everything). After flashing it, my phone stucked at HTC white screen and there is no way to switch it on, it stays at this screen all the time.
For my disgrace, it's S-ON, so I can't boot into recovery and restore anything. I've tried to restore a nandroid with fastboot and it doesnt't work (says "Failed (remote: signature verify fail)").
Any ideas? It's definetly bricked? Is there any hope of repairing it?
Thanks in advance (and please forgive my poor english xD)
Click to expand...
Click to collapse
What do you mean you cant boot into recovery because you are S-ON?
All you need to do is put the recovery file other wise known as flakeflash "UPDATE.ZIP" into the root of the SDcard, turn off your phone (Pull Battery), then press the down button and power button together, wait for the phone to do its stuff, then select recovery in the menu, the phone will reboot into red exclamation mark, press volume up and power, it will then go into stock recovery menu and will then look for the "UPDATE.ZIP" if all is well you should then go into the fakeflash version of clockworkmod recovery.
Does it boot when USB cable is plugged in (soft usb brick)?
ranger4740 said:
What do you mean you cant boot into recovery because you are S-ON?
All you need to do is put the recovery file other wise known as flakeflash "UPDATE.ZIP" into the root of the SDcard, turn off your phone (Pull Battery), then press the down button and power button together, wait for the phone to do its stuff, then select recovery in the menu, the phone will reboot into red exclamation mark, press volume up and power, it will then go into stock recovery menu and will then look for the "UPDATE.ZIP" if all is well you should then go into the fakeflash version of clockworkmod recovery.
Click to expand...
Click to collapse
Thank you very much, now I can boot into cwm, but I'm having some troubles when trying to flash CM7.2 (or even trying to restore any nandroid backup).
First, when I try to install CM7.2, it does it very fast, without showing any error, but when I restart the phone it gets stuck again on HTC screen.
Then I try to restore a nandroid backup but it doesn't find boot.img, system.img and data.img, skips all steps and restores nothing.
My last shot, try to install the last nightly I used, fails at the same point as when I try it with CM7.2.
I don't know what else can I do, any ideas? I hope there's still any chance for my Legend (and again forgive my bad english xD)
A few points, make sure the rom zip file you are going to flash is not corrupt or incomplete.
Boot into cwm recovery,
Make sure to format the boot, system, data, cache & ext, it wouldn't hurt to delete the dalvik cache too before flashing new Rom. Just remember NOT TO FORMAT SD card.
Using this method I have always been able to flash a new Rom.
Sent from my HTC Legend using xda app-developers app
ranger4740 said:
A few points, make sure the rom zip file you are going to flash is not corrupt or incomplete.
Boot into cwm recovery,
Make sure to format the boot, system, data, cache & ext, it wouldn't hurt to delete the dalvik cache too before flashing new Rom. Just remember NOT TO FORMAT SD card.
Using this method I have always been able to flash a new Rom.
Sent from my HTC Legend using xda app-developers app
Click to expand...
Click to collapse
I've tried this way but it didn't work
Ideas?
Thank you for your help.
vitiin92 said:
I've tried this way but it didn't work
Ideas?
Thank you for your help.
Click to expand...
Click to collapse
Prepare a new SD card in your PC (FAT32), put UPDATE.ZIP on it and a stock ROM, reboot into recovery, wipe all you can (factory settings) and flash the stock ROM, see if that works. If so, you could try to flash a custom ROM.
That is what I would try...
I'm too.
I can't up CookROm by Rom Manager,
but when i use ClockworkMod recovery, its OK
wim69 said:
Prepare a new SD card in your PC (FAT32), put UPDATE.ZIP on it and a stock ROM, reboot into recovery, wipe all you can (factory settings) and flash the stock ROM, see if that works. If so, you could try to flash a custom ROM.
That is what I would try...
Click to expand...
Click to collapse
I also tried your way but it's still broken
I don't know what else to do, seems dead xD
Thank you.
Some new ideas?
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
lopiop said:
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
Click to expand...
Click to collapse
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
tail.adam said:
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
Click to expand...
Click to collapse
i tried to manually reboot into recovery, but it wont enter.
can you use adb sideload if you cannot enter recovery?
lopiop said:
i tried to manually reboot into recovery, but it wont enter.
Click to expand...
Click to collapse
You may need to flash back to stock using Odin then re rooting again.
so i should flash the latest stock rom (4.3) for my region using odin? like this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
fixed using odin, though rather sad that my internal sd got wiped as well
lopiop said:
fixed using odin, though rather sad that my internal sd got wiped as well
Click to expand...
Click to collapse
Glad it's fixed I would recommend not to use apps from playstore to flash recoveries or roms seen nothing but trouble from them.Either use Odin or custom recovery to flash to avoid trouble in the future.
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