Hello everyone!
Iv recently acquired a new milestone 3, and after gettint out of the box only did the one click root service to root it up, and installed bootstrap / rom manger and so on. But when I power off the phone holding X I get into a ! triangle screen, which I cant even power down the phone via button.
Also booting with M, or both vol buttons I can get into a list of options, but recovery, bt tools or any other wont get into the recovery mode.
is there any other way? clockwork mod is already installed says the app, and the normal boot goes ok.
Iv downloaded from another post the CM7 which I wanna install, but impossible without the recovery mode.
any help appreciated, all Iv found in the forums was how to get into recovery, but none worked for me.
... never mind
If you are using cwm, make sure you are using the DROID 3 bootstrapper. There is no way to enter recovery without it.
Imo, you should use safestrap (the official version) . It's way better. Because the only way to get to recovery when you have cwm is the bootstrap app, if you bootloop your phone, the only solution is an sbf. Safestrap retains access to the custom recovery.
EDIT: I saw you installed the bootstrap. To get to recovery, open the app and click the reboot recovery option, then reboot your phone.
Sent from my DROID3 using xda premium
both options: bootstrap recovery and reboot recovery goes to normal boot into the OS.
since its a payd up app, already sent email to the devs so I can help troubleshoot whats going up on my device, but got no answer.
Odd. Make sure you hit bootstrap recovery, wait for it to say success, then hit reboot recovery.
Sent from my DROID3 using xda premium
I've had that.problem before with the bootstrap before. I could not get it to work no matter what. Rerooted, made sure I had su, busybox etc. Sbf'd and did it all again. Just use safestrap, it works. Just uninstall your bootstrap first
Sent from my XT860 using xda premium
http://db.tt/XzRiaG55
This is the modded version. Its supposed to be able to flash both safe and non safe modes but it doesn't. You can only flash in safe mode. But it does have a console included which can be handy. Its still cwm but redesigned ui. Note that if a rom isn't specifically meant for the xt860 you will need a patch for it. So far only eclipse 3.0 and mavrom 4.0 have xt860 version. I'll also find you the sbf for you. Always handy to have
Sent from my XT860 using xda premium
http://sbf.droid-developers.org/umts_solana/list.php
Choose the one for your carrier. If you are running windows you'll need rsdlite to use it. Just unzip the sbf somewhere on your comp and point rsdlite to the xml file in the unzipped folder. Make sure your battery is charged before doing this. And before flashing anything too. Just in case.
Sent from my XT860 using xda premium
Related
Hi guys:
I have rooted my phone today using SuperOneClick root. Then I have installed ROM Manager, and installed Clockwork Recovery Mod 3.0.0.5. I have being reflashing Clockwork and recovery menu via ROM Manager because when I turn off my phone and turn it up (holding up power on and vol down button) and press to go to Recovery then appears the error image that is like an Android logo, cellphone and a yellow caution sign.
¿Can you guys help me? ¿What I'm doing wrong?
Thanks!
That's the stock recovery. If you still have a stock rom, it will restore stock recovery unless you delete the following files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
I don't understand.
I have installed to it CM7 last build. And is running without any problems, but I am scared that if I have some problem with the OS and I can't boot to recovery.
It has Clockwork Recovery Mod but I can access it unless I use ROM Manager to start it.
¿I need to delete those 2 files and It will be fixed?
Thanks!
That is definitely the stock recovery (Android with an exclamation in a triangle).
If you have CM7 installed, I've no idea how you got the stock recovery, but re-flashing another recovery should fix it. The two files I mentioned aren't included in CM7, so that's not the problem...
Sent from my Nexus One using XDA App
Agree. That's the stock recovery. Sometimes you need to apply the new recovery twice under rom manager. I did have similar experience. Install a custom recovery again. I beg it will be fine next time. Hope this help.
When I first rooted using a one click method my custom recovery would only stick for one boot. On the xda nexus one wiki there's instructions on how to install a recovery after one click root and get it to stick.
Hope this helps!
Sent from my Nexus One using XDA App
Today, Koush added support for the Droid 3 to ClockworkMod.
This includes releasing a Droid 3 Bootstrap which I believe he'll have some download links for or be placing on the market.
BEWARE: If you plan on using the new bootstrap from Koush, PLEASE use the "Remove Recovery" button and uninstall my Bootstrap APK before installing his.
Don't use 2 Bootstrap APKs together. Universe Explode. Or, maybe it could be unpredictable if you decide to remove mine later.
Thank you for listening to this public service announcement.
i see it in the market
Whats the difference with this one and yours Hashcode? Are you still updating yours?
-smc
Its the newest version. It works with rom manager. Probably flashes all partitions, but not sure.
Sent from my DROID3 using XDA App
So you don't need to install bootstrap before installing this?
So quick question, if we were to flash something and it ended up boot looping, like flashing a theme, how do we get back into cwm if we can't get back into android to access the app? Need to be able to restore in case something like this happens.
Sent from my DROID3 using XDA App
No. You have to uninstall the previously released bootstrap/recovery. After which you install this new one.
Sent from my DROID3 using XDA App
Yep uninstall Hashcodes version from his app, then install the "Droid 3 bootstrap" on the market or from here http://t.co/IM110WZ3 then use clockwork mod to install the recovery for Droid 3 in the flashable list.
@clockworkmod
-smc
edru said:
No. You have to uninstall the previously released bootstrap/recovery. After which you install this new one.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
But if you havent installed the old one?
buckmarble said:
So quick question, if we were to flash something and it ended up boot looping, like flashing a theme, how do we get back into cwm if we can't get back into android to access the app? Need to be able to restore in case something like this happens.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Yeah i'm also curious how your supposed to get back into recovery in case of a boot loop?
Are either you or Koush going to be continuing work on your alternate-system-partition scheme for making 2nd-init not an accident waiting to happen?
Xenoproctologist said:
Are either you or Koush going to be continuing work on your alternate-system-partition scheme for making 2nd-init not an accident waiting to happen?
Click to expand...
Click to collapse
This. It is nice having official support, but the idea of keeping a 99% pure system and almost no risk of fubaring 2nd-init is extremely attractive.
Hmm not sure how to access the recovery from device power down using this, going to bptools just initiates a normal start up.
-smc
I too hope we see the 2nd init partition I Don't plan on installing the official at this point.
I used Hashcode's app to uninstall his recovery.. rebooted... downloaded Koush's Rom Manager from the market.. installed... started the app and flashed clockworkmod recovery... gave su permissions.... clicked Reboot into Recovery and it just reboots normally... no CWM... am i missing a step? is there a keyboard combo that will boot into CWM... vol-down+power only takes you to fastboot..
Thanks to all for continuing to develop this phone!
ckarrow2 said:
I used Hashcode's app to uninstall his recovery.. rebooted... downloaded Koush's Rom Manager from the market.. installed... started the app and flashed clockworkmod recovery... gave su permissions.... clicked Reboot into Recovery and it just reboots normally... no CWM... am i missing a step? is there a keyboard combo that will boot into CWM... vol-down+power only takes you to fastboot..
Thanks to all for continuing to develop this phone!
Click to expand...
Click to collapse
yeah, you need to bootstrapper app, and i believe you need to click bootstrap recovery everytime you need to reboot into cwm.
you can get the app here http://t.co/IM110WZ3 (thank somemadcaaant)
erismaster said:
yeah, you need to bootstrapper app, and i believe you need to click bootstrap recovery everytime you need to reboot into cwm.
you can get the app here http://t.co/IM110WZ3 (thank somemadcaaant)
Click to expand...
Click to collapse
Thanks! worked perfectly! I couldn't see the forest for the trees
I seem to be having some issues getting this to work.
I uninstalled the Hashcode recovery, then removed his app. After that I downloaded the Droid3 recovery from the market and installed that. Going into Rom Manager, after a reboot, I was it did not list any Clockwork as being installed. I clicked on the list and Droid 3 was now one of the options so I applied that and went to test by having Rom manager reboot into recovery.
It sat there for a good 5 minutes on the red Motorola logo. Pulled the battery to reboot and it booted fine but I cannot figure out how to access the recovery.
calash said:
I seem to be having some issues getting this to work.
I uninstalled the Hashcode recovery, then removed his app. After that I downloaded the Droid3 recovery from the market and installed that. Going into Rom Manager, after a reboot, I was it did not list any Clockwork as being installed. I clicked on the list and Droid 3 was now one of the options so I applied that and went to test by having Rom manager reboot into recovery.
It sat there for a good 5 minutes on the red Motorola logo. Pulled the battery to reboot and it booted fine but I cannot figure out how to access the recovery.
Click to expand...
Click to collapse
Using the bootstrap app make sure you click bootstrap recovery then reboot recovery using the app. See if that helps.
Sent from my DROID3 using XDA App
erismaster said:
Using the bootstrap app make sure you click bootstrap recovery then reboot recovery using the app. See if that helps.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
That did it. Now it shows up in ROM manager and I can boot into the recovery from both apps.
Thanks
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860
Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.
Okay right about now i am really confused about flashing roms on droid 3,
ok so i have root access now what recovery should i put?
and here is my big question.
can i flash dark droid or steel droid regardless of system?
my phone says .866 and droid steel says i need .890?
am confused on this part,
sorry for the stupid questions.
Yes you do need .890, and I recommend that you install the tweaked bp tools bootstrap by hashcode to get cwm, it saved my softbricked droid3
Sent from my DROID3 using XDA App
jojo4747 said:
Yes you do need .890, and I recommend that you install the tweaked bp tools bootstrap by hashcode to get cwm, it saved my softbricked droid3
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Not gunna lie im a lil confused too..what's the point of flashing the tweaked one if when you flash a new rom it overwrites it? So you can't access cwr from bp tools then
/droid3
under settings, about phone, your system version is .866? i think we were .959 and now we're .890. Yes, you would want to use hashcodes modified version of koush's bootstrap.
beard0 said:
Not gunna lie im a lil confused too..what's the point of flashing the tweaked one if when you flash a new rom it overwrites it? So you can't access cwr from bp tools then
/droid3
Click to expand...
Click to collapse
Basically installed on your phone as an app, and you re-bootstrap/recovery after you flash your custom rom so you can create new backups/restore/flash update .zip files ect. After the rom is flashed as well... if you think you wont have any issues ever after, by all means, brave the world without your cwm recovery on there... but that kinda seems like you'd be sinking your d*** in looseness w/o a rubber... and no body likes that itch in the AM...
Sent from my DROID3 using Tapatalk
Seirÿu said:
Basically installed on your phone as an app, and you re-bootstrap/recovery after you flash your custom rom so you can create new backups/restore/flash update .zip files ect. After the rom is flashed as well... if you think you wont have any issues ever after, by all means, brave the world without your cwm recovery on there... but that kinda seems like you'd be sinking your d*** in looseness w/o a rubber... and no body likes that itch in the AM...
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Not saying it wont be usefull but if you can manage to navigate to the bootstrap app and hit the button for bootstrap recovery..why can't you just hit the button for reboot recovery? I guess im just missing my unlucked bootloader from my incredible lol I used to screw with my phone so much lol
But why does no one wipe for any of these roms?
And what is safe strap exactly?
/droid3
IF you can access the app, yes you could just hit reboot recovery. If youre bootlooping or something you can go into recovery and select bp tools and that reboots into the same recovery as selecing reboot recovery in cwm. and the safestrap is different from the tweaked bootstrap. the safestrap boots from /preinstall or something. Also, you should wipe especially after switching to/from CM7
MrJudylicious said:
IF you can access the app, yes you could just hit reboot recovery. If youre bootlooping or something you can go into recovery and select bp tools and that reboots into the same recovery as selecing reboot recovery in cwm. and the safestrap is different from the tweaked bootstrap. the safestrap boots from /preinstall or something. Also, you should wipe especially after switching to/from CM7
Click to expand...
Click to collapse
This. ^^^
Basically you want it if you can't actually boot your phone.
if you don't redo your recovery and just rely on clicking those buttons when you need them from the app... you'll be stuck if you bootloop and have to flash the sbf in order to get your phone back. I much rather restore from recovery and have 99% of my phone data back with no issues.
The safestrap and 2nd Int. stuff is wicked cool, I just wish i knew more about that... I couldn't really help describe that part lol.
recently I have attempted to flash the monster rom to my droid 3 and I havent had success it was 1.2 version and i used D3 Safestrap. I went into safe mode then installed zip from my sd card and it loaded and was successful. Then went in to reg mode to boot up ( because it is not able to in safe) and nothing changed i went into the about phone and it does not show a new rom was loaded nor does anything look different. Did i miss a step? what happened?
Sounds like it didn't work. The point of safe mode is that it's a separate system to non-safe mode, so non-safe mode should still work exactly like it did.
So your phone not booting in safe mode means that the ROM's not working or whatever. Switching to non-safe mode is like flashing back to the backup before you installed the ROM, it _should_ not look any different.
Ok so then that mean even though it says successfull it is in fact not? I am a noob, so i apologize for my ignorance.
Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App
Unfortunately MonsterROM is not Safestrap compatible in its current form. You need to unzip it, delete a folder and rezip it for use inside of Safestrap. There's a post somewhere within the Safestrap discussion of the Android Development section that indicates what to do.
Manic_Dragon said:
Did you toggle back to safe mode and reboot. That should boot up the new rom.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I did and it wont go past the multicore display it just goes blank after
SBF, reroot, then just install the other bootloader. Don't use Safestrap. I had the same problem with Monster. Someone probably should convert it.
Sent from my DROID3 using XDA App