hello i use droid pro in cm7 but when I flash another rom into my droid pro i always reset my phone with rsd lite...... How can i get into cwm recovery in cm7???? I also use bootstrapper but it doesn't work in cm7 please help me!!
stevehanwoo said:
hello i use droid pro in cm7 but when I flash another rom into my droid pro i always reset my phone with rsd lite...... How can i get into cwm recovery in cm7???? I also use bootstrapper but it doesn't work in cm7 please help me!!
Click to expand...
Click to collapse
MB this helps you.
You can get to the bootmenu by rebooting your phone and when it starts up the LED will turn blue. When it turns blue press the volume down button. From the bootmenu you can choose the Recovery option.
same prolem
i can't recovery cwm in cm7 also using droid recovery . but after that the phone will be stuck in logo
Related
hello,
is it possible to switch from cm7.1-nightly to ms2ginger easily?
(cm7.1 is android v. 2.3.7 with kernel 2.32.9)
regards
Yes you can do that easily. The ms2Ginger thread has enough information on how to do that. I have switched twice from Cm7 to ms2g and vice versa.
In a nut shell just restore the manseoid back up of ms2g system, data, boot , dev tree and recovery. Before you do this just take nandroid backup of your current cm 7, which can be useful to switch back at later time if needed.
Sent from my MB526 using XDA App
ok. after installing ms2ginger it seem to be not my flavour.
i tryed to install cm72 (120131.05331-nightly) by epsylon. now, the device boots up, lights blue and green up and nothing more happens..
what can i do? (got backup but want a fresh install)
regards
now, when i push the poweron button, nothing happens..
the led lits up, when usb plugged in.. but thats all..
help?
_xo said:
now, when i push the poweron button, nothing happens..
the led lits up, when usb plugged in.. but thats all..
help?
Click to expand...
Click to collapse
CM7.2 is for Defy+ which uses GB kernel.
You can either flash CM7 kernel if it works, otherwise go to advance restore and restore boot and devtree from MS2 nandroid.
hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help
coolgame said:
hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help
Click to expand...
Click to collapse
Are you installing MS2G 2.1? and Did you follow the complete restore of nandroid backup, - system, data, boot, devtree and recovery?
yup i did twice.
coolgame said:
hey guyz need some help here.i own a defy+. i dont noe why but when i tried to install the walter9 MS2Ginger over the CM7.2,i got the bootloader err msg and the phone wouldnt startup.then i flashed the 2.3.6 sbf file via rsdlite and phn was back to its original working condition.then i rooted it again and then again tried MS2Ginger but after installation in recovery it asks for reboot.and after reboot, i got the same error saying
the same thing again
Bootloader
09.10
Err:A5,70,00,0023
again had to flash to original sbf
need help
Click to expand...
Click to collapse
I am searching for the instructions too:
http://forum.xda-developers.com/showthread.php?t=1468867&page=2
Will work the ms2ginger with cg version 6?
Anyone?
I had managed to get working, with instruction in the ms2ginger topic
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Root your DEFY and Install BOOTMENU - CWM (2ndInit-Installer 2.0.apk - install 1.0.7) or use this SndInitDefy_2.0.apk
REBOOT
run 2nd-init (voldown on blue LED)
wipe data and cache in "Stable/Custom - Recovery"
Go to "Recovery"
Go to "Latest Recovery"
Go to "Backup and Restore"
Go to "Restore" (system+data)
reboot.
Booting up can take a while, max is about 10 minutes.
THEN(if you want to try also the 3.0)
wipe data/cache/dalvik; Do an advanced recovery and only restore system and data from 3.0NG.
well I have defy green lense... I just flash miui pikachu edition, It was working fine then last night I'd just flash another JB ROM that was working fine... but when I again try to flash pikachu ROM it was stuck on motorola M logo no blue LED turn on ....after that I flash a fixed sbf "4.5.3-109-fixed.sbf" this one....
the problem is same no blue LED turn on ... Please let me know how I can get CMW again .. step by step procedure needed. Thanks!
Note: I was using GB kernel 3.4.7
Your 2ndinit got wiped, hence no blue LED. If you can boot into the stock ROM, you need to root it and install 2ndinit apk(just search for 2ndinit defy on Google) and install your custom recovery again. After this you will get the blue LED again
Sent from my MB526 using xda premium
thekguy said:
Your 2ndinit got wiped, hence no blue LED. If you can boot into the stock ROM, you need to root it and install 2ndinit apk(just search for 2ndinit defy on Google) and install your custom recovery again. After this you will get the blue LED again
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I cant boot into stock ROM, phone stuck on motorola M logo..... Can I flash full sbf again, coz I was on fixed GB sbf?
slhysf said:
I cant boot into stock ROM, phone stuck on motorola M logo..... Can I flash full sbf again, coz I was on fixed GB sbf?
Click to expand...
Click to collapse
Get into stock recovery by keeping volume down pressed when powering the phone.
When you see a triangle with excl. mark press volume down and up at the same time
Wipe data and cache
If above doesn't work flash proper full sbf and repeat the procedure
You're stuck on red logo as you have not wiped data from stock recovery, and instructions are /\
Sent from my MB526 using xda premium
So apparently I have two different versions of ClockWorkMod Recovery on my Droid X. ROM manager says I have 5.0.2.0, but when I reboot into Recovery (via ROM Manager, or manually) it boots into CWM 2.5.0.8. I can then Flash the 5.0.2.0 zip, and use it normally, I just can't boot directly into it. I recently got a replacement Droid X off ebay because my screen developed a huge black blob in it, but it didn't have the same CWM weirdness going on..
Is there any way to get rid of the 2.5.0.8? Everything works correctly once I flash into 5.0.2.0, but it would be nice to be able to get there directly.
TIA
bump?
Anyone?
same here
Hello i have the same issue just by me i cant do any thing in recovery it will just always go to a blank screen in rom manger it will show 5.0.....
in recovery it shows 2.0....
pls help will love you for ever :crying:
Regarding droid x cwm
IndyRoadie said:
So apparently I have two different versions of ClockWorkMod Recovery on my Droid X. ROM manager says I have 5.0.2.0, but when I reboot into Recovery (via ROM Manager, or manually) it boots into CWM 2.5.0.8. I can then Flash the 5.0.2.0 zip, and use it normally, I just can't boot directly into it. I recently got a replacement Droid X off ebay because my screen developed a huge black blob in it, but it didn't have the same CWM weirdness going on..
Is there any way to get rid of the 2.5.0.8? Everything works correctly once I flash into 5.0.2.0, but it would be nice to be able to get there directly.
TIA
Click to expand...
Click to collapse
i think it has something to do with bootstrap did you try using 2.5.0.8 not sure but i think you should be able to use it the same as 5.0.2.0
tzvblsm said:
i think it has something to do with bootstrap did you try using 2.5.0.8 not sure but i think you should be able to use it the same as 5.0.2.0
Click to expand...
Click to collapse
Both work, just you can't Restore backups made in 5.0.2.0, using 2.5.0.8.. So ever time I want to do a Back Up, or a Restore, I boot into Recovery and it loads 2.5.0.8, then I flash 5.0.2.0, then run my Back Up or Restore..
It all works, it's just a pain..
Simple solution
IndyRoadie said:
Both work, just you can't Restore backups made in 5.0.2.0, using 2.5.0.8.. So ever time I want to do a Back Up, or a Restore, I boot into Recovery and it loads 2.5.0.8, then I flash 5.0.2.0, then run my Back Up or Restore..
It all works, it's just a pain..
Click to expand...
Click to collapse
Why don't you Boot in to recovery and backup from recovery instead of ROM manger to my understanding that will solve all your problems.
if i helped hit the thanks button
tzvblsm said:
Why don't you Boot in to recovery and backup from recovery instead of ROM manger to my understanding that will solve all your problems.
if i helped hit the thanks button
Click to expand...
Click to collapse
That's what I am doing.. Any way I get into Recovery, by booting directly into it, or via ROM Manager, it boots into 2.5.0.8.
Got it worked out, thanks to this thread..
http://forum.xda-developers.com/showthread.php?t=2133052&page=2
I started using my milestone 2 from stock (Argentina) froyo, then updated to CM7, then after some time started using CM10.
Now after some time, I wished to revert to CM7. I rebooted into recovery and flashed CM7 and Gapps, but got stuck in red Motorola logo when booting up. What should I do? Follow the downgrade instructions posted here in xda?
Thanks in advance!
fischer22 said:
I started using my milestone 2 from stock (Argentina) froyo, then updated to CM7, then after some time started using CM10.
Now after some time, I wished to revert to CM7. I rebooted into recovery and flashed CM7 and Gapps, but got stuck in red Motorola logo when booting up. What should I do? Follow the downgrade instructions posted here in xda?
Thanks in advance!
Click to expand...
Click to collapse
Wipe data/factory reset in stock recovery.
Lean946 said:
Wipe data/factory reset in stock recovery.
Click to expand...
Click to collapse
You mean pressing X and power when booting? It doesnt work, I dont get the exclamation mark, only the red motorola logo.
If I press volume down when booting (blue led) I can access the android bootmenu, and from there custom recovery (clockworkmod).... but when I choose for example Stock recovery (from the android bootmenu) I get just the rred moto logo, nothing else...
Any ideas?
Thanks again.
fischer22 said:
I started using my milestone 2 from stock (Argentina) froyo, then updated to CM7, then after some time started using CM10.
Now after some time, I wished to revert to CM7. I rebooted into recovery and flashed CM7 and Gapps, but got stuck in red Motorola logo when booting up. What should I do? Follow the downgrade instructions posted here in xda?
Thanks in advance!
Click to expand...
Click to collapse
latest CM7 build does not contain kernel and you have wrong kernel. if your bl=2 you need to flash one of the previous builds and then latest or flash only this kernel. if your bl=3 you need revert to stock, then downgrade and flash rom (maybe kernel too). I tested it for bl2 and also bl3.
fischer22 said:
You mean pressing X and power when booting? It doesnt work, I dont get the exclamation mark, only the red motorola logo.
If I press volume down when booting (blue led) I can access the android bootmenu, and from there custom recovery (clockworkmod).... but when I choose for example Stock recovery (from the android bootmenu) I get just the rred moto logo, nothing else...
Any ideas?
Thanks again.
Click to expand...
Click to collapse
If you can get to the bootmenu you can go to the custom recovery and wipe data from there too.
oh yeah !!that all right
thank you !!
hackerc5 said:
thank you !!
Click to expand...
Click to collapse
You don't need to say "thank you", just click the Thanks button
Hi guys!
I have Droid Pro Verizon American.
I have put CM7 V8 by VanillaLVL and then Cm7 V9 by vanillaLVL.
After putting this versions, and then installing Droid 2 Recovery Bootstrap from app store, and trying to Reboot to Recovery i cannot load to the OS.
I have tried to restore to factory settings, but nothing - it just freeze with load screen with M letter - it's doesn't go further.
I have sbf'ed it back, then rooted, then put the CM7 again two times, and every time is the same bug - i cannot reboot to recovery with Droid 2 Recovery Bootstrap installed over the CM7. Does anybody have the same problem? It works ok on rooted stock, but not on CM7.
Do you know how to resolve it? Maybe there is other software for clockworkmod instead of Droid 2 Recovery Bootstrap for CM7?
Anyone?
Any ideas, guys? Really it's not simple bug, it would be good to know what is happening?
Maybe somebody could give some tips how to install clockworkmod manually? without application? I cannot find this info on the internet, everybody says to use rom manager or droid 2 bootstrap.
I believe you just cannot install bootstrap over cm7. So just try:
1. Root
2. Bootstrap
3. Cm7
4. Gapps
5. ????
6. Profit
Sent from my MB855
not.a.troll said:
I believe you just cannot install bootstrap over cm7. So just try:
1. Root
2. Bootstrap
3. Cm7
4. Gapps
5. ????
6. Profit
Sent from my MB855
Click to expand...
Click to collapse
I actually don't understand what you mean. I already have cm7 installed on my phone. The problem was that I used Droid 2 Bootstrap on cm7. I actually found the solution, i didn't know that vanillaLVL cm7 has custom bootloader with cwm inside, for this you just need:
sorry yor are right. i was my fault. i found it.
In order to get in to recovery: press power for 3 seconds. ->chose reboot -> chose bootloader -> reboot and wait for the LED to flash BLUE and then PRESS volume down button when its BLUE. it wil take to BOOT MENU. -> select RECOVERY -> then CLOCKWORK RECOVERY.