Heres my situation:
I installed the froyo rom without installing the new CWM first. So i tried renaming the new cwm and replacing it with update.zip to no success, and never reverted back to the old one. Now i decided to revert back to stock, install the new CWM, and than flash the froyo rom. But something went wrong.
I flashed odin stock-i500-vzw-system.tar.md5, and upon reboot it sounds the vzw sound, but stays in the samsung bootup screen, and it won't go into recovery because my update.zip is broken.
My odin for some reason fails every time i try to flash the old recovery, or the old kernels, it only wants to flash system.tar.
Thats as detailed as i can get it for now, any help would be great.
look around for some different stock odin files. i had a hard time with flashing cwm files as my phone just wouldnt accept them for some reason.
i'm gonna try adrenalyn's system.tar, kernel and CWM DI01 package, see if this works. keep fingers crossed
Hey Everyone.. not sure what I did here.
I was rocking Superclean 2.3 NV with out any issues, decided to venture to the world of Voodoo and install the 2.4 voodoo version. Ever since than I have been unable to install themes/restore backups/install new rooms. I get stuck in a boot loop. I then go into RED CWM to restore my backup and get stuck in a boot loop there as well. I have since flashed the EB01 deoxed via odin to try to get rid of VoodDoo and have the disable_lagfix file in the voodoo folder and flashed back Red CWM though Odin. Able to use phone fine, but as soon as I flash a rom/theme I get stuck in the same boot loop and unable to restore backup.
I next ODIN'd DL09 full package, manually got root/cwm and flashed 2.4NV and updated to EB01 Modem. Attempted to update to Blackhole 4.21 with lagfix_disable and red CWM and got stuck in the bootloop again.
What am I doing wrong?
Not sure if this should be in general, so apoligies if I'm in the worng place... Anyway, I was running the first Cyanogenmod nightly and tried to update to the latest. After updating, the phone stuck at the M logo. I can't get into clockwork but can get into stock recovery.
I can sbf, reroot, reinstall gingerbread, and it works fine. whenever I apply the latest cyanogenmod nightly I get stuck on the M logo.
Each time, after sbf I'm doing factory rest and wiping cache at each step. Works right up to the CM part. I also tried sbf, then OTA update, then the CM nightly, same result.
Looking for suggestions on other things to try... I really want to get CM working on this phone again, because I can't stand the stock!!
If you install CM and it boots back up and gets stuck, try going to stock recovery and doing a wipe data and cache and it should boot into CM.
When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.
droid2master said:
When you install the CM7, make sure the FIRST TIME you are about to boot into CM7 you do a full data/factory reset (with bootloader) not stock, because it will bootloot every time if it tries to boot with the gingerbread settings, and after the first try, i couldnt get factory resets to work from the stock recovery.
Click to expand...
Click to collapse
This happened to me. I'm trying to do this for a friends phone and I am a little unfamiliar with Motorola because I have an EVO. Could you describe the steps for doing a full/data factory reset with bootloader?
The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.
my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7.
My mistake, I've downloaded the wrong kernel, you must get GB CM7 or it will loop.
sangweb said:
my does the same, I flash back to stock 2.2, OTA to Gingerbread, root using droid 3, install the clockmod recovery, wipe, format, clear cache, install CM7, again wipe, format and clear cache, now it is stuck on M logo. factory recovery won't even give me the option of wipe and clear cache option. Looks like I am going back to stock again without CM7. Avoid cm7 at all cost unless someone has a solution to fix this.
Click to expand...
Click to collapse
I'm assuming you guys are installing CM7 version for OTA GB. Simple mistake but I know it happens.
0vermind said:
The nightlies must be screwed up or something cause I'm having the exact same problem. I can SBF, flash the pre-rooted Gingerbread, and install the bootstrap Clockwork Recovery, but as soon as I flash one of the later nightlies, it's stuck at the Motorola logo with no where to go. Data wipe using stock recovery after words doesn't help at all.
Will be SBF'ing, and re-flashing, then will wipe data and cache while still in Clockwork Recovery and I will report back if this works.
Click to expand...
Click to collapse
This is true, dunno why CM Team is not updating the nightlies, I've tried everything, already SBFed to 2.2, updated to 2.3, rooted 2.3, wiped everything, flashed, no go, but boot loop.
I have managed to get earlier nightlies working b4 but it seems the latest nightlies are broken, can someone test them out???
Trust me, I've rooted enough phones to know what to do here (look at my sigs), these CM7.1 D2 nightlies DO NOT WORK!
The worst part about D2 is that you have to start from scratch once you end up in a boot loop, meaning you have to unroot back to 2.2 SBF, update to 2.3, then try flashing, a process that takes about 30 minutes. I've done it all day long yesterday and today, now trying to get some of the older nightlies to work.
i'm helping my co-worker put on CM for the first time and i got this same thing. i dont want to buy her a new phone. how do i fix this? im a long time htc user and so this is all new to me.
I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.
I Am Marino said:
I used stock recovery, rebooted, still stuck. I'm having to sbf and I'm even having issues with that. Definitely gonna stick with Liberty until this gets sorted out now.
Click to expand...
Click to collapse
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now
nadcicle said:
I was having alot of issues from not reading and thinking that I had to be on the GB OTA.
I read somewhere that you are supposed to be on Verizon 2.3.20 with sbf then do a factory wipe. Afterwards you root with ADB. Then you use droid bootstrab 1.0.0.5 to install the nightly after factory wiping once more.
I kept thinking I had to be on the latest OTA and I would get stuck on the M every time. Then I ran into the cyanogenmod wiki for the droid2.. Now I am just stuck wondering about overclocking, but at least I have a working cm now
Click to expand...
Click to collapse
After going with sbf nightmare after nightmare and having to buy a new battery, I finally got restored to stock and then rerooted, sticking with Liberty until I can easily flash CM like anything else without all the added steps.
I have installed the rooted BL7 DFP-231 SBF and everything works fine, but when I install 2ndinit the phone goes into a boot loop and I have to reflash it with RSD Lite again.
try to flashing the stock sbf, then root it from there.
There's no real way to root BL7 that people know of.. the only way is to flash the rooted SBF.
Does anyone have any idea?
Hey
try this Link
It might work
Got it all working and flashed with CM7! v1.4.2 gives permisson errors, 2.0 and 1.9 put my phone in a boot loop.. so I figured it may be because it's actually downloading the recovery you select instead of installing it locally, so I went to 1.7 and it worked like a charm!
I can't post this in dev section because it's my first post, so I'll try asking here.
I have a Droid X on the .621 firmware that I rooted using the "DX ezSBF & Root 2.3.4/4.5.621" which worked like a charm [THANKS sd_shadow & phifc]. Then I decided to install Kiladar's "[ROM] CM9ICS with APn Support for cricket or sprint flashed from verizon" & the ICS Gapps. All went well with the installs until I rebooted. Now I'm stuck on the boot animation for CM9, I cannot access CWM recovery because I can't bootstrap outside of the OS. I can access stock recovery, but that will not allow me to reflash due to signature verification error. Does anyone know what I can do now?
[EDIT] Fixed the issue by going into stock recovery and doing a factory reset. Rebooted, loaded OS, now so far, so good.