Related
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.
How can I install two ROMS (MavROM and ICS) on my D3? one in SAFE MODE and one without.
what programs to use?
I already have MAVROM installed with SAFESTRAP from hashcode, but if i disable it, i get the stock rom.
thank you.
You have to use a bootstrap to flash your nonsafe before you install safestrap
Sent from my XT860 using xda premium
can you direct me to a link to that application? all I can find is safestrap from hashcode.
i have this one: "Droid3CWBootstrap"
http://www.appbrain.com/app/droid-x-recovery-bootstrap/com.koushikdutta.droidx.bootstrap
but how can I install zip with it?
I'm sorry I didn't see your last PMs
Anyway.
1) Start in stock ROM http://forum.xda-developers.com/showthread.php?t=1336980
(Or your non-safe ROM in safestrap and then remove safestrap)
2) After root, download bootstrap (I uploaded it) http://www.mediafire.com/?3u8xhmsp3lg5yfx
3) Install the APK and open the bootstrap app. Press install recovery then reboot recovery. You're now in bootstrap, not from using vol -+ etc (from your PM)
4) Flash mavrom using their CWM Recovery instructions
5) Once you got it setup, remove bootstrap app and install safestrap http://goo.gl/1pr5T
6) Reboot into safestrap and switch to safe system. Make a backup if you want before swithing. The switch will backup your current ROM (data), which is mavrom. Once in safe-system you can now flash ICS using the instructions. This will flash ICS in a different place. When you go back to non-safe system your mavrom will be restored.
Hope it's clear now
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
bogdan_wrc said:
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
Click to expand...
Click to collapse
Np aside from the fact that I'm not on XDA all day the notification is very small - most of the time I don't see it until the next day
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
zzandrewst said:
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Endoroid said:
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
zzandrewst said:
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
you can't flash nonsafe with safestrap. Gotta use a bootstrap to flash your nonsafe, then install safestrap for flash safesystem. But yes, i have liberty as my nonsafe and ics as my safe
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
what to do?
I dont have the INSTALL from zip option, just UPDATE from zip.
that why i used safestrap.
but if I want to install the boot animation from RAZR, now in which location shall I do that? it used to be in /system/media folder. still there?
thank you, i managed to install both one successfully.
bogdan_wrc said:
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
Click to expand...
Click to collapse
I think thats because you tried to flash using original recovery, you said something with -+ volume buttons?
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Really a fastboot flash isn't such a big deal. I've done it more times than I can count. Takes 10 minutes. Id rather have my fav rom in nonsafe so I can use safe to testing new roms and new ics builds
Sent from my XT860 using xda premium
Is this dual boot system possible for my phone ? I would like to switch froyo and cynaogenmod !
Sent from my Optimus Me using XDA App
DoubleYouPee said:
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
Click to expand...
Click to collapse
I think you miss a key point. When you boot safestrap it starts in the non-safe system no matter what you do. Depending on your mode it then moves you to a totally separate partition on the device, preventing you from doing any harm to the boot rom.
The non-safe is key for the entire system to work. Yes it can be any rom, but you do put yourself at risk of losing two installs, including all the data.
Easy unbrick may be as fast to get to stock, but to rebuild back to where you were is going to take a lot longer.
In the end I am just advising caution, not telling people what to do. It does go against what the system was designed for and people should be aware of that before jumping off the ledge.
I understand, but now I have to go back to bootstrap to do essentially the same thing
Not sure if I follow you..
If you are only working in Safe-mode Rom the worst you can do is blow that rom up. Fixing it is just a matter of restoring your last backup via Safestrap recovery.
The problem with working in non-safe rom is that you can blow up both and lose your recovery. From that point you have to do Fastboot, install bootstrap, restore non-safe backup, install SafeStrap, restore Safemode backup.
Unless I am not understanding you correctly.
I need some help please. I rooted my Verizon Droid 3 using Pete's tool, then debloated using the script found here. I then installed Safestrap 1.06 did my my backup etc. and have been running Mavrom. I needed to go back to stock unrooted for some testing so I restored my backup,uninstalled Safestrap, rebloated, unrooted and then factory data reset my phone and SD card. Now when I reboot I still get the Safestrap spalsh screen? Any ideas?
Thanks
rccadman said:
I need some help please. I rooted my Verizon Droid 3 using Pete's tool, then debloated using the script found here. I then installed Safestrap 1.06 did my my backup etc. and have been running Mavrom. I needed to go back to stock unrooted for some testing so I restored my backup,uninstalled Safestrap, rebloated, unrooted and then factory data reset my phone and SD card. Now when I reboot I still get the Safestrap spalsh screen? Any ideas?
Click to expand...
Click to collapse
Did you go into the Safestrap app and uninstall recovery before you uninstalled and unrooted? (My guess is no.) If not, I would re-root, re-install Safestrap, and then open the app and tap the button to uninstall recovery. Then unroot again and you should be all set.
Thanks for the reply. You are correct I did not do that! I will try following your directions! Thanks again!
Sent from my DROID3 using XDA
OK guys i am needing a little help with this one. Been running the MavRom 3.0 on my droid 3 and been loving it. I was looking to update to the 4.0 and the CWM will not boot to the recovery screen. Even through ROM manager when I try to "install Rom from SD card" it does nothing. It goes from the Moto logo right to the boot animation. This one is a little frustrating to say the least...I've never had this kind of problem before. Im almost close to doing a damn factory reset and trying the safestrap method. I really would like to avoid this...
Why would you need to factory reset to try the safestrap method?
You shouldn't have to SBF. Try removing CWM and then uninstalling it then install Safestrap.
MrObvious said:
You shouldn't have to SBF. Try removing CWM and then uninstalling it then install Safestrap.
Click to expand...
Click to collapse
Ok...I'll remove/uninstall CWM. So what is the best way to install safestrap? I have the apk file on this computer. Really, I haven't had to trouble shoot like this before that is why I am asking.
I have always used CWM since my OG Droid...so Im used to such. I just don't know why I can't boot into a recover mode..
Just install the apk, install the Safestrap into the bootstrap area from the app, then reboot and you can push the menu key on bootup to get into Safestrap.
MrObvious said:
You shouldn't have to SBF. Try removing CWM and then uninstalling it then install Safestrap.
Click to expand...
Click to collapse
Hey buddy. So I have CWM uninstalled. Do I need to remove any related files/folders from the root browser? I have the safestrap file in my download folder.
trykrohm22 said:
Hey buddy. So I have CWM uninstalled. Do I need to remove any related files/folders from the root browser? I have the safestrap file in my download folder.
Click to expand...
Click to collapse
If by CWM you mean bootstrap, safestrap removes all of that by itself if you uninstalled bootstrap
DoubleYouPee said:
If by CWM you mean bootstrap, safestrap removes all of that by itself if you uninstalled bootstrap
Click to expand...
Click to collapse
All is good! Got the MavRom4 put on my phone. Thanks for the bit of help.