It is on 605 stock.
Installed Droid Wall, Rom manager.
I tried D2/X/X(2nd-Init) recovery images and NONE of them are working.
(Currently 5.0.2.0 is flashed - so it says).
Never mind. I did not know that one needs to run an reboot to recovery application in order to reboot to recovery due to locked bootstrap.
What? I'm having same problem.
thedsk said:
What? I'm having same problem.
Click to expand...
Click to collapse
newbie here but I mess up twice like this. For .605 stock you need to unstall Droid 2 Recovery Bootstrap from the market.
Related
I'm trying to make a nandroid backup so I can mess with my droid 2 but having issues...
The phone is rooted.
Have Installed: Rom Manager and Droid 2 Bootstrapper - both 'green' in superuser permissions.
When I try to boot into recovery mode using Rom Manager (trying to make a backup) or the D2 Bootstrapper the phone just boots up as it normally would. I can get into the default recovery mode by using the 'X' and 'PWR' key combo but that's not what I need.
Have tried renaming these files as suggested here in another thread and reflashing clockworkmod but that didn't work.
EDIT: can't link so these are the two files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any ideas?
Meh... nvm - I figured it out.
Help!
Hey, my friend has the SAME EXACT issue. what did you do to fix it?
Everyone says to reinstall clockwork, but that doesn't fix it.
sonok said:
Hey, my friend has the SAME EXACT issue. what did you do to fix it?
Everyone says to reinstall clockwork, but that doesn't fix it.
Click to expand...
Click to collapse
I've never used ROM manager because koush's D2 bootstrap does everything you need. But if you don't get clockwork from the application make sure you are properly rooted and you press "bootstrap recovery" and get the "success" box before you press "reboot recovery".
newk8600 said:
I've never used ROM manager because koush's D2 bootstrap does everything you need. But if you don't get clockwork from the application make sure you are properly rooted and you press "bootstrap recovery" and get the "success" box before you press "reboot recovery".
Click to expand...
Click to collapse
My friend is using Rom manager. He installed CWM via rom manager. Do you think it is safe for him to get "Koush's D2 bootstrap" and re-install CWM that way? Will that break anything?
PS: I use Amon_Ra's recovery on my nexus one. I do all my installations via ADB but he is not comfortable using ADB. I'm just trying to get him into a stable custom recovery because ever since he installed clockwork (which is not working) he says the phone is really slow.
sonok said:
My friend is using Rom manager. He installed CWM via rom manager. Do you think it is safe for him to get "Koush's D2 bootstrap" and re-install CWM that way? Will that break anything?
PS: I use Amon_Ra's recovery on my nexus one. I do all my installations via ADB but he is not comfortable using ADB. I'm just trying to get him into a stable custom recovery because ever since he installed clockwork (which is not working) he says the phone is really slow.
Click to expand...
Click to collapse
I don't know installing koush's bootstrap will do but the D2 has to be bootstrapped because it's locked down and normal Clockwork Mod won't work because of it. If it doesn't work and his phone isn't working he can just SBF with the 2.3.2 version (he probably has the update already) he can do it in linux or windows (linux is easier) and it will put him back to stock so he can install koush's bootstrap from the market after re-rooting it.
If he want's he can back up his contacts and applications with google and data with titanium backup.
You can PM me if you have any questions about the process.
Here's my tool for flashing sbf's in linux on any computer. It's got a lot of useful info about flashing and problems at the bottom read it even if you flash in windows.
Can someone tell me why would Clockwork not function properly? My problem is that when i click on anything the screen goes blank. This is wen i use the volume keys. A fix for this is using the keyboard. besides this. I took a rom and renamed it update bcuz i am tryin to flash droid 2 to cricket. This is one of the steps. Rename a rom to update. The only thing this the recovery do is show a line that says "replacing clockwork recovery with clock work recovery" or something like that and then jus goes back to the main menu
vlug said:
Can someone tell me why would Clockwork not function properly?
Click to expand...
Click to collapse
Are you using the Clockwork Recovery provided in koush's bootstrap? or have you run koush's bootstrap at all?
If not then that's why. On the Droid 2 and newer Moto droids the bootloader has been locked so we have to overcome this by bootstrapping or hijacking the boot process to include clockwork recovery when we need it. koush's bootstrap does
this for us and includes clockwork recovery.
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...........
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
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