Database Users

Black screen and no boot after flashing cyanogen mod 7.1

Hello guys !
I have a problem, i have an european (french) motorola milestone 2, i have this stock firmware "MILS2_U6_4.1-22" and i have rooted the phone with DoomLorD and i have install droidbootstrap, go into recovery of the droidbootstrap, flashed bootmenu 0.86, go into custom recovery with bootmenu, flash cyanogen mod (http://forum.xda-developers.com/showthread.php?t=1239778), did a wipe data and cache, reboot the phone, have picture (rayman's rabbit and blue logo motorola) and have black screen after this picture, can't go in boot menu (haven't got a blue led). Somebody can help me ?
PS : Sorry for my english.

Hold camera+vol down to boot into bootloader and then flash stock SBF (http://and-developers.com/sbf:milestone2) via RSDLite.

I have already done, so i can't put cyanogen 7.1 v1.3 in my phone ? May be it's the bootmenu ? I set i to default boot to normal, help me please.

It should be set to boot via 2nd-init. You need to flash fixed-sbf from the CM7 post. There should be a link for that in the same post or thread.
edit: I am guessing you are on Official GB.
Sent from my MotoA953 using XDA App

Yes i'm on official gingerbread, it's a problem ?
I have tried to put the default boot on 2nd-init and i have no boot already (black screen after the rabbit and motorola logo)
What can i do ??

Flash fixed-sbf using RSDLite. That's the complete install process for GB CM7 on GB kernel.
After applying the zip file you have to apply fixed-sbf from Endless7's CM7 thread. And if it does not boot after that try a data wipe.
Sent from my MotoA953 using XDA App

Thank's a lot, i have not flashed the fixed sbf after flashing the zip file (cyanogen), after flashed the fixed sbf the phone reboot corectly, thank's !

[Q] droid x borked?

So on a wild hair i decided to try out the latest official firmware. Stupid i know.
Now when i SBF back to the old firmware as stated in the cyanogenmod full update guide, root and bootstrap i can get into CWM recovery but no matter what rom i use it just bootloops. Then if i try to go back into CWM i of course find its the stock 3e recovery.
Did i perma-bork my phone from having custom roms or is there a problem between the chair and monitor? lol

did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT

marculous said:
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
Click to expand...
Click to collapse
Yeah, after I got the first bootloop I tried with apex and liberty and on each attempt wiped data and cache 3x

wipe data and cache, factory reset, then sbf? idk, I've been where you are many times and i always have to go back to the guides to get the process right, in the correct order.
DX .605 ROOT

So is there no reason that the newest OTA* would ruin the ability to put custom roms on?

i wouldn't think so, but i know for cm7 to get on my phone i had to sbf back to 2.2 from the. 596 i was on. guess it depends on the rom. me personally, i just left cm7 for. 605, rooted because i like the blur camera and hdmi support. took off most of the bloat but not all, it jacked up my contacts.
DX .605 ROOT

just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms

spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
can you sbf back to an earlier version?
DX .605 ROOT

Yes I can go back to the froyo SBF without any problem. The issue is, once i do that, then repeat the steps and flash a custom rom, no matter what rom i use, i get a bootloop. the stock SBF and OTA work fine, its just once a custom rom is installed.

spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3

hootowlserenade said:
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
Click to expand...
Click to collapse
No, it bootloops at the M Logo screen.
the M logo comes up for like 2 seconds, then the phone reboots.
The only variance to this is when i flash the AIO APEX rom, then it just sits at the google logo indefinitely. But on any other rom including Cyanogenmod and Libery it bootloops at the "M" Logo.

There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App

infazzdar said:
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
^This werk'd! I owe you vigorous oral.

spockmeat said:
^This werk'd! I owe you vigorous oral.
Click to expand...
Click to collapse
wow...........

[Q] no blue LED... please help!

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

[Q] Can't load after downgrade to 7.2 Jordan

Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?

llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that

llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck

Exactly the same problem here, cannot downgrade to CM7.
Any good news?

Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium

So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!

Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^

llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.

skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?

Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?

llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium

farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.

It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.

That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense

[Q] Recovery Stock motorola not work

Hi, so i have latest miui V4 2ndboot on my defy. First i have latest CM10 Quarx.
When I change Rom all perfect
but when I try enter to stock recovery my phone stay on moto logo and i pull out battery fot boot phone
For other i can enter to cwm recovery and phone work,
For restore motorola recovery? I flash any zip?
this can cause problems?
Thanks for all
P.S. I have motorola defy MB525 red lense

up

Why you need stock recovery, if you have included 2ndinit in custom roms. 2nd: if you want to restore stock recovery, you'll need to start from scratch...

Gianluca85 said:
Hi, so i have latest miui V4 2ndboot on my defy. First i have latest CM10 Quarx.
When I change Rom all perfect
but when I try enter to stock recovery my phone stay on moto logo and i pull out battery fot boot phone
For other i can enter to cwm recovery and phone work,
For restore motorola recovery? I flash any zip?
this can cause problems?
Thanks for all
P.S. I have motorola defy MB525 red lense
Click to expand...
Click to collapse
stock recovery is available through bootmenu (2nd or 3rd option). So reboot in bootmenu.

pgreed said:
stock recovery is available through bootmenu (2nd or 3rd option). So reboot in bootmenu.
Click to expand...
Click to collapse
when I try, bootmenu -> recovery -> stock recovery stay on motorola logo and i pull off battery

turffe said:
Why you need stock recovery, if you have included 2ndinit in custom roms. 2nd: if you want to restore stock recovery, you'll need to start from scratch...
Click to expand...
Click to collapse
Because when i have cm 10 (2nd-boo) stock recovery work , I try install cm7 official (2nd-init) but i can enter to cwm but stock recovery don't work.
If this not cause problem, I stay whit this rom and work whit cwm recovery
If I want restore recovery? I flash sbf file whit ROM stock?

Gianluca85 said:
when I try, bootmenu -> recovery -> stock recovery stay on motorola logo and i pull off battery
Click to expand...
Click to collapse
In that case you need to start from begining: flash sbf. etc. because I dunno if you find a bootloader.img to flash.

pgreed said:
In that case you need to start from begining: flash sbf. etc. because I dunno if you find a bootloader.img to flash.
Click to expand...
Click to collapse
I have found my bachup of original rom and on this file i find boot img and recovery img?
If I restore this?
I restore original stock recovery?
the cwm recovery remaning?
thanks for all.

you can reinstall custom recovery (which contain stable recovery) through terminal emulator (with an sh script) or restore a img.

pgreed said:
you can reinstall custom recovery (which contain stable recovery) through terminal emulator (with an sh script) or restore a img.
Click to expand...
Click to collapse
if I use 2ndinit.apk and install cwm this restore the stock recovery?
if no i have download sbf rsd lite and ready for all
Thanks for all

Stock recovery disappeared, it's happen sometimes when using custom roms. No clue too.
But it's not even a problem, you don't need stock recovery if you're using custom roms. Custom/stable recovery work it all.
You only need Stock recovery once you want to revert back to stock roms.
When you flash stock SBF successfully Stock recovery will work again! (and let you wipe to gracefully boot into rom.)
So, you plan to return to stock? If not, stop this worries until you planned to.

intemptesta said:
Stock recovery disappeared, it's happen sometimes when using custom roms. No clue too.
But it's not even a problem, you don't need stock recovery if you're using custom roms. Custom/stable recovery work it all.
You only need Stock recovery once you want to revert back to stock roms.
When you flash stock SBF successfully Stock recovery will work again! (and let you wipe to gracefully boot into rom.)
So, you plan to return to stock? If not, stop this worries until you planned to.
Click to expand...
Click to collapse
thanks for all, i asked if this is a problem. only you say me this not a problem. Now I Know the procedure and that happen when flash rom.
For me the tread closed