Database Users

[Q] Rom Manager/ Bootstrap help?

So I accidently flashed CW Recovery before I used bootstrap and now I can't boot into CW Recovery or create a backup. Any ideas?
Ive searched all over the place, Ive found some threads that describe what each do, but I guess Im just trying to understand the whole picture. I have the Bootstrap program on my phone, I also have Rom Manager (Im rooted and have SuperUser also.)
I guess where Im confused at is what to do with each of them.
On other phones Ive just went through Rom Manager, Flashed CW Recovery, created a backup then I was up and running.
Do I need to do this before running bootstrap, do I run bootstrap first?
Sorry for the rookie question, I guess this boot strap thing has me confused. Any help would be greatly appreciated

You have to use the bootstrap to get into clockwork recovery, run the first option in bootstrap, it should say "success" then use rom manager or the reboot recovery option. You need to do the bootstrap option every time you want to go to custom recovery.
Sent from my DROIDX using XDA App

So is it bad I flashed the CW recovery before using bootstrap? If so how the heck do I fix it, lol

I flashed CW recovery before I hit bootstrap. Shows I have the current Recovery Image
If I hit "reboot into recovery" through Rom manager it doesnt do anything. If I hit "bootstrap recovery" through droid x bootstrapper it says success, but when i hit reboot recovery it doesnt do anything either...
power+home button on power up just brings me to stock recovery screen..
im lost

Try running the first option in bootstrapper again, same with reflashing clockwork... rom manager can boot to recovery.
Sent from my DROIDX using XDA App

I tried that, still nothing...
Sent from my DROIDX using XDA App

Would it have anything to do with me having the official 2.3.15 update already on my phone? Its rooted of course but even when I click S.U it opens up but its just a blank black screen and says S.U permissions at the top
Sent from my DROIDX using XDA App

DrewDanger said:
Would it have anything to do with me having the official 2.3.15 update already on my phone? Its rooted of course but even when I click S.U it opens up but its just a blank black screen and says S.U permissions at the top
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
something is wrong with your root. try to re-root your phone the first time you run bootstrapper and rom manager you need to give them permission and it looks like you haven't yet so they can't work right. redo your root and it should solve your issues. also i find i need to bootstrap recovery before each time i try to use rom manager. kinda a pain i use recovery from bootstrap more often as its the same thing.

So even though Im rooted with the stock 2.2 I need to re-root it? Like just download a one-click-root and do it all over?
Should I factory reset before I do this?
The thing is I got the phone from a friend and it already had S.U on it, I just dont know what program he used to root it and what not...neither does he.

http://alldroid.org/default.aspx?g=posts&m=9209
Try this, its the new one click
Sent from my DROIDX using XDA App

citanes-26 said:
http://alldroid.org/default.aspx?g=posts&m=9209
Try this, its the new one click
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I re-did the root with that and now it lets me boot into CW recovery! Your the man! Do you have paypal by any chance =) I'll gladly shoot you a tip!

Help rooting phone. Trouble getting green recovery screen.

So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.

Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App

creglenn said:
Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I went into ROM Manager and clicked "boot into recovery". Where it brings me to the blue recovery screen. So you think I should unroot then re root? Because everything with the root seemed to work fine. It installed superiser and I had no problems downloading Titanium Backup or ROM Manager and allowing superuser permissions. Which made me think I was just forgetting something...but I might just try that. Thanks!

if your rooting stock 2.2 your gonna need a modded 3e recovery or one of supercurios voodoo kernels with CWM & root already built in. Superoneclick will root stock 2.2. If its 2.1, then you may need to hit reinstall packages a couple of times to get it to take.

drscott333 said:
So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.
Click to expand...
Click to collapse
All you should need to do is hit reinstall packages again. When you do it the first time it will boot back into the same blue recovery again. Hit it once more then it should boot to the green recovery. If that doesn't work you probably have a bad zip file on the phone. In which case you'd re flash CWM again.
If you're not getting the superuser request when you flash CWM then root didn't take. Make sure root works first.

Did you actually run install cwm from rom manager so the update. zip is there?

Just make sure with Astro or another file manger that you have a .zip file and it should be 1.72 MB in size and you want that on your internal SD card....Then when you boot to recovery it should let you hit reinstall packages with no problem

I'm new here, but I have flashed 3 vibrants since last week. I had the same problem you did.
When I flashed my phone last week it was stock 2.2, so I had to flash the modified 3e recovery which fixed my issue getting into CWM to install my ROM. Today i was flashing a co-worker's vibrant who also was on stock 2.2. However, on his it would keep rebooting when reinstalling packages, even though i did the 3e recovery flash. I ended having to Odin back to 2.1 on his phone before i could flash the new ROM.
I just used AIO Vibrant Toolbox 2.5. Hope this helps.

Thanks for all the feedback!! I don't have the phone with me to check if the update.zip folder was for sure there. But if it is, I'll try reinstalling the packages again. Otherwise I'm just going to unroot and try rerooting with the AIO Toolbox. I'm not going to be able to do this until tomorrow though since our work schedules were pretty much opposite today. But once again, huge thanks to all of you!!! However I've never unrooted before...if I haven't flashed any ROMs, I shouldn't have any problems should I? Just click unroot?

CWM Problems

UPDATE: To fix 3.0.2.4 from not formatting /system
Open rom manager and select settings, and check erase recovery. hit menu again and select clear cache, then flash 3.0.2.4 again.
now if your in recovery and you cant boot back up to use rom manager, use the file below. It will allow you to restore your backup then once booted back up use the method above to fix 3.0.2.4.
The reason im leaving custom over 3.0.2.4 is bc i know fastboot flash with this one will allow you to restore without wiping recovery or clear cache or anything else.
http://www.mediafire.com/file/b8ejhqbf3tgnsoe/recovery.img - this is CMW 3.0.1.4 just altered for installing zips. linking for people needing a recover img to boot up
To install:
1. If in recovery, open ur terminal on ur pc and type adb reboot boatloader
2. Once in bootloader it will load fast boot and say fastboot usb in red
3. cd to the folder with fastboot.exe and also place recover.img in that folder
4. then enter fastboot flash recovery recovery.img
5. adb reboot recovery
6. restore your backup and boot up

RafficaX said:
Little FYI for all, cwm recovery wont format system on a restore. made a backup, tried a flash and went to restore and it fails formatting system.
So be careful with flashing and all bc yo may not be able to restore currently with cwm.
UPDATE: format system in menu also fails! be careful bc you pretty much cant restore or flash atm!
Click to expand...
Click to collapse
Oh how I miss Amon_Ra

jlevy73 said:
Oh how I miss Amon_Ra
Click to expand...
Click to collapse
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.

RafficaX said:
im really hoping Amon_Ra does do his recovery on T-Bolt. I like Rom Manager and its features but would rather loose features for stability and reliability on each use.
Click to expand...
Click to collapse
QFT
can't wait for amon-ra

raffica, what version of CWM worked for you?

MYxdaUSERNAME said:
raffica, what version of CWM worked for you?
Click to expand...
Click to collapse
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.

Thanks for the heads up I agree I always loved CWM on my N1 but it started giving me all kinds of grief for several different reasons so I finally went to Amon Ra.

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
Can you help me out and provide it because right now i cant even boot

RafficaX said:
A custom compiled one 3.0.1.4, working on porting The Ultimate Droid to T-bolt so blackdroid also compiled cwm to make sure it would install the zip but has working restore. i messaged koush on cwm twitter about the issue so hopefully he fixes it quickly. only problem is the one im running you need to flash through fastboot with adb.
Click to expand...
Click to collapse
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes

superchilpil said:
isnt UD banned on these forums?
just curious dont flame me or anything! cuz when a Ud rom hit the inc the thread was deleted in minutes
Click to expand...
Click to collapse
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...

nosympathy said:
yeah, if you go on their forums all they do is flame XDA left and right. But I find it funny since their roms take advancements from XDA developers and then they incorporate it into their roms...
Click to expand...
Click to collapse
See that's what I thought, but wasn't sure
Sent from my ADR6300 using XDA Premium App

Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.

jgrimberg1979 said:
Can you help me out and provide it because right now i cant even boot
Click to expand...
Click to collapse
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically and I followed the steps from 7 on to regain root. Worked for me, but now I have to start over. Hopefully they will get CWM working again. I will be much more careful about what I delete from now on. I think I will freeze it in TiBackup first to make sure everything is still working correctly. Hope this helps.

lynseyw said:
I ran into the same problem. I tried to do a restore and got stuck. I used an sd card reader and put the 3rd file from the root thread PG05IMG.zip on the root of my sd card. I then put the card back in. Rebooted into recovery holding the volume down and the power button. It reflashed the file automatically
Click to expand...
Click to collapse
This is the exact procedure I used when the same thing happened on my N1

i added the recovery.img i used to OP with instructions for those stuck in recovery or bootloader.

jeffnucci said:
Yes Clockwork 3.0.2.4 is borked on Thunderbolt. I've been helping people on AndIRC's thunderbolt channel all day. Install 3.0.2.2, it's given me no problems.
Click to expand...
Click to collapse
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App

miketoasty said:
Latest Rom manager is 3.0.1.3 sorry if I am missing something I am a bit of a clockwork noob.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.

My battery died and am in the same position. Got an expensive paperweight at the moment. I'll try to get another battery today and give this a try. After fooling around with it last night, the computer wouldn't even recognize the phone. Ughh!

RafficaX said:
Newest Rom Manager is 3.0.1.3 but the newest ClockworkMod Recovery for the tbolt is 3.0.2.4
Under flash clockworkmod recovery it stats the current and latest recovery.
Click to expand...
Click to collapse
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App

miketoasty said:
Good call just checked and 3.2 does wipe date and cache properly.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Where did you get 3.2? 3.0.2 you mean?

Clockwork backup

What's the best way to create a full backup before flashing a rom? I have clockwork recovery installed and Droid x bootstrap. I flashed the clockwork recovery but it wont reboot into the recovery or create a backup of my current rom.
Sent from my DROIDX using XDA App

crxin said:
What's the best way to create a full backup before flashing a rom? I have clockwork recovery installed and Droid x bootstrap. I flashed the clockwork recovery but it wont reboot into the recovery or create a backup of my current rom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
On Gingerbread: I ran into a similar issue. In order for it to boot into bootstrap recovery for me I had to install Droid 2 Bootstrap recovery and bootstrap with that one for it to boot properly. I had issues with Clockworks recovery from Clockword mod and Droid X bootstrapper. Try Droid 2 Bootstrapper and let us know if that works.

I'm not sure what you're using to make a backup but here's a way that should work for you. Using Droid x bootstrapper, click bootstrap recovery and then click reboot recovery. If you're on the GB leak disable USB debugging and it will work. Then when in CWM, use the up/down volume keys to navigate to backup and restore, and press the camera button to select it. If you need to go back you can press the power button or back key. After selecting backup and restore, select the first option and it will backup everything on your phone. It will take about five minutes or more, just be patient. When its done you can flash a rom or reboot

I am on the regular Verizon rom with the latest update. The phone wont boot into the recovery either through bootstrap or clockwork GUI.
Sent from my DROIDX using XDA App

You are rooted I presume? I would try installing bootstrap and reinstalling as well.
Sent from my DROIDX using XDA App

Yes I am rooted, I users z4 root. Whenever i manually boot into recovery I get the guy with the ! And it says can't open e:recovery/command or something but loads just fine into the stock recovery.
Sent from my DROIDX using XDA App

crxin said:
Yes I am rooted, I users z4 root. Whenever i manually boot into recovery I get the guy with the ! And it says can't open e:recovery/command or something but loads just fine into the stock recovery.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
What buttons are you using to boot into recovery? It should be just power and volume down

crxin said:
Yes I am rooted, I users z4 root. Whenever i manually boot into recovery I get the guy with the ! And it says can't open e:recovery/command or something but loads just fine into the stock recovery.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You can only make a backup by getting into cwm. It sounds like you are still getting into stock recovery. Follow the instructions by jmoney above and you should be good. There is a way to boot into cwm from a powered off state. Just search the forums if you feel like going that route.
Sent from my DROIDX using XDA App

Thanks for the help guys i got it working. something was fubar with the installs, so i wiped the cache and wiped the application data on bootstrapper and clockword and reinstalled. worked like a charm.
thanks for the help guys.
rob

[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...........