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...........
Related
Alright. Not new to rooting/flashing, all that jazz. I'm having an issue with my X boot looping, but I do a battery pull and it's fine.
I've actually sbf'ed (sp? lol) my phone and everything again to avoid this, thinking it was an issue with my process. Still getting booty loops.
So, I sbf'ed from froyo 2.2/fly x/tranquilty.
Here is what I've done, exact process.
-SBF'ed to stock 2.1
-Boot loop, pulled battery, rebooted into recovery, factory reset/clear cache (i know this one was necessary)
-Back to stock 2.1
-Used Easy Root method to root.
-moved SU from system/bin to system/xbin (to keep root before froyo update)
-downloaded Rom Manager from market, flashed CWR
-used Koush's bootloader apk
-downloaded 2.2 froyo from Rom Manager
-installed 2.2 froyo, booted back up.
First thing I did was download rom manager, backup my rom before flashing Fly X/Tranquility, Rom Manger rebooted me, threw me in a boot loop. Battery pulled, booted fine.
Only thing I can think of is I flashed CWR before using the bootloader apk, but not sure if that would even affect anything? Maybe clear cache partition in CWR might help something?
Any ideas? Thanks for your help in advance.
Try always using the "boot strap recovery" before rebooting from rom manager. See if that helps.
Sent from my DROIDX using XDA App
citanes-26 said:
Try always using the "boot strap recovery" before rebooting from rom manager. See if that helps.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
so, use the bootstrap.apk everytime before I need to reboot into recovery?
Kinda redundant.
Do you use this method?
Thanks for the response btw.
when u sbf, ur suppose to factory reset/clear cache before booting up to avoid that bootloop.
and to avoid bootloop from happing with a new rom, your suppose to bootstrap ive been reading...
Yep, if you reboot or flash I always do the bootstrap, read alot of people having to do it. First thing I do before I try to backup or restore.
Sent from my DROIDX using XDA App
cool, thanks for the responses guys.
i'll just keep boot strapping for the time being.
cant wait til we crack that sob.
BRUTAL BROCK said:
cool, thanks for the responses guys.
i'll just keep boot strapping for the time being.
cant wait til we crack that sob.
Click to expand...
Click to collapse
lol
"-downloaded Rom Manager from market, flashed CWR"
I did this same thing too.... We gotta use bootstrap.
Please pardon my ignorance but what is bootstrap?
Droidx bootstrapper, its in the market. You have to use it to get into clockwork recovery since we still have a locked bootloader.
Sent from my DROIDX using XDA App
Never mind this can be removed if necessary!
7/26
Well I need help again, so I figured I might as well use this post rather than creating clutter...
So my original help request involved my inability to get my phone into bootloader OR recovery but I eventually got it... I was trying to SBF back to Froyo so I can re-root and flash MIUI.
So I got all that done, but I seem to be having issues getting Clockwork recovery to stick around. After I recovered back to Froyo via SBF, I was able to download ROM manager and flash CWM recovery and then bootstrap it, reboot to it and flash MIUI. After MIUI boots up (runs great by the way, for those considering it), I installed ROM manager again but it said that I had no recovery (or stock) so I re-flashed CWM, bootstrapped it again and rebooted into recovery, only to find myself in the STOCK recovery...??? So without doing a THING in stock recovery, I hit reboot and now my phone is stuck at the Motorola logo and I am unable to reach CWM recovery to re-flash or anything. I cannot find another way to get back into my phone without an SBF back to Froyo, thus back to step 1.
Can anyone help me out?
Oh and I've already wiped data/cache with stock recovery - still no dice
See above post
I asked a similar question. It's a good thing I decided to wait until I got an answer before using ROM Manager. I am not sure why it did what it did.
I would also like to know the answer to your question.
edit: Perhaps (after you SBFed again) if you flashed CWM from Rom Manager but don't bootstrap? It seems like bootstrapping erases the ROM Manager's CWM and doesn't install the one it has. Just a thought. (If bootstrapping is important, though, then disregard this.)
Another thought. Bootstrap first, then flash CWM from ROM Manager. See if that works. Also try going to CWM through the bootstrapper, if you can't do it manually.
edit2: Just tried it that way (D2B first, RM second). worked like a charm. Was able to successfully update Miui.
Man, I don't get why these phones do some of the things they do...
I just SBF'd my phone again, re-rooted and re-installed MIUI and NOW, for some strange reason, I am able to make my way into CMW recovery.
Veeerrryy interesting
n1ghtwish said:
Man, I don't get why these phones do some of the things they do...
I just SBF'd my phone again, re-rooted and re-installed MIUI and NOW, for some strange reason, I am able to make my way into CMW recovery.
Veeerrryy interesting
Click to expand...
Click to collapse
lol With this stuff it's hit and miss. You just gotta keep trying till it works.
after the OTA update to 2.3.4 my rooted droid 2 boots into ClockworkMod Recovery 2.5.0.8.
From what I'v read it isn't possible to to restore my phone to 2.3.3. So I'd like to remove clockwork mod recovery so it boots normally. Currently I have to choose "reboot system now" from recovery,when I do a cold restart, then the phone boots normally.
So far I'v only wiped my user data, but thought i'd better check what would be the best course of action. Don't want to brick my phone.
Sorry if it's a noob question.
Don't think about downgrading to 2.3.3 you'll be bricked and have to install 2.3.4 and lose cwm and root
Sent from my DROID2 using xda premium
Yeah saw the posts (of people trying to downgrade). I'm thinking of selling it, but need to remove the clockwork recovery. Any ideas on how to get it off of there?
Use the 2.3.4 SBF as mentioned above.
devinpatterson said:
Yeah saw the posts (of people trying to downgrade). I'm thinking of selling it, but need to remove the clockwork recovery. Any ideas on how to get it off of there?
Click to expand...
Click to collapse
if your not worried about losing root, SBF use http://forum.xda-developers.com/showthread.php?t=1662091
if you just want to fix cwm, read Proper Use Droid 2/X Bootstrapper
the logwrapper or hijack is the problem,
also read Droid Wiki: SBF, Recovery, CWM info
When I was on the stock Verizon ROM I was able to simply run the Droid 2 Bootstrapper and it booted into recovery. From there I installed this Galnet MIUI ROM. I'd like to check out some other ROMS but I cannot get CWM to install.
In ROM Manager 3.0.1.4 I tap on Flash CWM and it says "An error occurred while downloading your recovery"
I tried installing the D2 bootstrapper and when I click on boot into recovery my device simply reboots back into MIUI and everything has been reset to default. I'm kind of new at all this and tried searching but didn't really come up with a solution. I've heard something about SBF but not sure what that is. Any help would be appreciated. Thanks.
Here, try this. CM7 is the best ROM for this phone anyways
http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2:_Full_Update_Guide
Cool I will check it out. I figured out how to get back to stock using RSD Lite. Slowly but surely I'm getting all this Android stuff.
So now I'm running into another issue. Once I get the SBF installed and I'm back on stock 2.2 I can't seem to get any other ROM flashed. At all.
On 2.2 I root the device using z4root. Then I install the D2 bootstrapper and reboot into recovery. The standard CWM screen comes up. I wipe cache. Clear Davlik cache, etc, etc. I install the update.zip and everything seems fine. Says process is complete but when the phone is restarted I'm stuck in an endless boot loop of the white Motorola logo.
Did you only wipe the cache or did you wipe data/factory also?
I did both. When I got this device it was on 2.3.7 I think. It's not activated and I plan on using it as a PDA/MP3/WIFI device. Seems like I can't do any factory updates without cellular data so it's on 2.2.
I can't even get MIUI 2.2.10 back on there.
You need to be on GB not Froyo to run Galnet. There's an SBF for 2.3.7 posted here on the forums.
there is no 2.3.7
2.3.4/4.5.621 is latest and it is unrootable and can not flash older sbfs
use 2.3.3/4.5.601 aka 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf
find here http://1kds.tk/
2.3.4; you knew what I meant =p
I got it all worked out. Are there any overclocking enabled kernels for the D2?
I recommend Milestone Overclock. It doesn't load on boot with all Roms, but it does on most and it's free and doesn't come with AirPush like some apps.
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