Database Develop

Update to Koush's Bootstrap with BP Tools Support by Hashcode

Hashcode has modified Koush's fully functional bootstrap so it can be booted from power-off using BP tools!
http://hash-of-codes.blogspot.com/p/android-downloads.html
Nice work!

So do we just uninstall koush's bootstrap and then install this one
Sent from my DROID3 using XDA App

I just installed over top the existing one. Already had it installed. It worked perfect!
I'm able to get into the full version of CWM using BP tools.

Seeing as how I have been using Koush's bootstrap, I am assuming I need only remove the 'original' bootstrap and use this one in it's place?
P.S. This is what we needed. It works! Wow. You should perhaps remove the prior bootstrap before installing this new one. To avoid contusion. This new one says 'tweaked'
Sent from my DROID3 using xda premium

Yeah, it makes sense to uninstall the original version. Otherwise you'll have two installed (with duplicate names and icons) and kinda makes it confusing.

This is a massive help - I've been fiddling with the 5.6.890 ROM, but its painful as everytime I get an unbootable system, it needs a reflash to get to recovery - that means being near a PC every time I want to try a tweak.

Doing a nandroid backup now...

Nandroid backup and restore successful with this new install.
Apprehensive to restore from older backups now even though this should be the same version of Koush's since it's his core app.
Thoughts?

ckarrow2 said:
Nandroid backup and restore successful with this new install.
Apprehensive to restore from older backups now even though this should be the same version of Koush's since it's his core app.
Thoughts?
Click to expand...
Click to collapse
I would think a backup WITH this installed is one step better than with the old
Sent from my DROID3 using xda premium

Wolfhere said:
I would think a backup WITH this installed is one step better than with the old
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
No doubt! I'm really glad we have this now.

ckarrow2 said:
No doubt! I'm really glad we have this now.
Click to expand...
Click to collapse
We have yet another new recovery coming shortly, with cm7 support. Cm7 is booted, but don't expect anyone to see it soon. It needs a good week or 2 before it becoms beta. Radio, wifi, etc don't work yet. The new recovery will have a way to swap between cm7(for now, probably all roms later) and back to stock system very easily.
Sent from my DROID3 using XDA App

I do have a small problem with this...
Downloaded, installed, clicked on "Bootstrap Recovery" and granted Superuser Permissions. Then, my phone rebooted. And since then, every time it came up, it stayed alive just up to the message where Superuser grants permission, and a new reboot took place.
I am, however, able to access the new recovery via BP tools.
Managed to get back to an operable state by removing the apk via adb. Still, I wonder how that strange scenario could happen and what I could do against it?
Notes:
The phone is running the "old" firmware, Superuser 3.0 and the newest su that came via the updating tool. Did some unbloating as well, some time ago.

CWM always fails!
Everytime I go into recovery from bp tools. I click restore it always ends up saying "error in restoring system!". No matter which back up i click.

Do you think that there is any plan of updating the "Market" version of the Droid 3 Recovery Bootstrap ? Or is this something else ?

what does BP tools provide?
noob question, what does this do for us that Koush's bootstrap doesn't? I've never heard of BP tools.

Basically this version allows you to access CWR when your bootlooping. Koush's bootstrap is supposed to kick over to recovery after the first loop, but if it doesn't your basically SOL and the only way to recover your system is to flash the sbf. What hashcode has done is modify it so you can also enter recovery by holding M while powering it on, and getting the boot options. You can then scroll down to BP Tools, and it will boot over to CWR. Thus if you bootloop you still have an option to get to CWR and your backups.
This is the same as the version on the market with tweak of the the extra boot optioni. ROM manager works fine with hashcodes tweaked version just like it did with Koush's version

VincentDHam said:
Everytime I go into recovery from bp tools. I click restore it always ends up saying "error in restoring system!". No matter which back up i click.
Click to expand...
Click to collapse
it may not support your old backups... try doing a new backup, and restoring it... This tends to happen when recoveries first come out and new ones take its place..

Just did another full backup and restore with this version. No problems at all.

Thanx to Hashcode for this and his work, champion effort.
-smc

ok forgive me, but i bought koushs, and downloaded hashcodes. i was going to rename the current apk to bak and drop the new apk using root explorer, but what directory am i suppose to look in? data/app has com.koush.droid3.bootstra-1.apk, but im not super familiar to android yet (obviously lol)
edit: also i didnt see any d3bootstrapanything in system/app

Guide?

A friend of mine has Droid 3 on Verizon. I'm want to know what I need to do to flash a recovery on it so I can backup and flash roms on it. I'm not sure if I need a custom bootloader for it aswell. I found this thread with recovery as a sticky but it doesn't have much explanations in it. I also see you guys don't have a sticky with a guide anywhere besides just the one click root.
Can anyone point me in a direction?
Thank you.

On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium

slayer621 said:
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
So how do I install this safe strap and where do I get it. I assume this will also let me flash a custom recovery like CWM?

Everything you need to know on installing safestrap can be found here
There are 2 versions. One is the standard version in the link, the other is a "tweaked" version found on the forums here. While the tweaked version has a few extra features, from what I've read, it can be a bit unstable. Use the version provided in the link.

Yeah what he said ^^^ then once u have the safestrap you just download the rom u want and flash it and your good to go
Sent from my XT883 using Tapatalk

Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.

obsanity said:
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
Click to expand...
Click to collapse
The 1st system gets renamed to systemorig and is otherwise left untouched. /reinstall gets renamed to /system and becomes your safe mode system. Im not 100% on hijack but as I understand it, it quite literally hijacks the boot sequence at a certain point by killing all the processes and inserting its own in order to give us a custom recovery
Sent from my XT860 using xda premium

OK. So why not just backup the original system and overwrite it? If the partition gets renamed why is there a need to keep it? Wouldn't deleting it give more room for roms? Is there even enough room for 2 partitions on the emmc?

The whole idea was that you keep your original system intact so you can still receive OTA updates. I've never had an issue with not having enough room for roms. They are only about 150 MB.
Many of us actually use this to dual boot. The common way is to have a stable rom on your /systemorig and test new roms on safe system.
There is a plain old bootstrap that installs regular old cwr and just overwrites /system. Everything should be compatible with it. I think I have a copy of it in my dropbox
The main reason for using safestrap(in my view) is that when you're messing around in safemode its next to impossible to brick your phone so bad you can't access recovery, since when it first boots it still boots from /system, and then redirects to the safe system. You should never have to fastboot flash your phone
Sent from my XT860 using xda premium

So can you dual boot? And how do you boot into your orig 1st system? Don't you have to toggle the safe mode each time? Also, how much total room is there on emmc on D3?

try here :
http://forum.xda-developers.com/showthread.php?t=1436380

The internal SD memory is roughly 11GB. The phone stores which system was last booted and then you can backup and restore between them though the SafeStrap pre-boot recovery. Once you try it, it's really simple and effective. I was hesitant to leave old faithful bootstrap, but now that I'm on safestrap, I wonder why I ever hesitated.

So the 1st system is simply copied to SD storage when the safe mode is turned on?

Also, do I download ver 1.09 which says Droid 4? I have a Droid 3.

obsanity said:
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Click to expand...
Click to collapse
It creates a backup of /system and /data when you switch between safe and non safe. And I think also /cache. However as I mentioned before it renames /system to systemorig.
Sent from my XT860 using xda premium

It runs off the /preinstall partition IIRC. You should/can DL the original from Hash's blog or get Rick's tweaked version from the Dev section.

I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.

obsanity said:
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
Click to expand...
Click to collapse
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium

Endoroid said:
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I just did it on his phone. All worked OK. Thanks for all your help. I'm used to the nexus devices which are much easier and straightforward. I installed nightly CM9 from hashcode. I'm not sure what works yet. Is there a better version of CM9 besides that one? He really wants ICS and CM.

All of the ICS roms are currently limited in the same way: no HW codecs, bluetooth on but not connected = loss of audio, etc. There's a thread here in the general section that compares all of the ICS roms. I would advise looking through it and deciding which one suits you best.
EDIT: to answer your question, the may 7 build of Hashcode's CM9 is a good build. They just brought back the theme engine so that opens up possibilities.
Sent from my DROID3 using xda premium

Safestrap 3.05 help please.

I uninstalled the old version of safestrap, then installed the new version. I can do everything just fine (install, wipe, etc) but when I try to boot from the ROM slots, the phone just sits at a black screen.. I tried flashing Eclipse 3.0 and nothing happens.. help???
Sent from my DROID3 using xda app-developers app

Well eclipse 3.0 hasn't worked for me. The latest cm10,aokp,and aosp boot for me as well as mavrom 4.5 and axiomcs 1.0. Have u tried any other roms aside from eclipse?
Sent from my XT862 using xda app-developers app

Don't think eclipse works with new Safestrap. I have tested CM10, AOKP, AOSP, and Steel Droid. Those 4 all are "working".
Steel Droid is the most stable one i have tried so far, CM10, AOKP and AOSP all lag for me.

Hey guys,
New to Droid 3/ Milestone 3 World here.
I just bought one, actually with the 5.2.390.XT860.Brasil.en.BR version.
I'm not exacly new to flashing roms, and recoveries, but in this case I'm a little confused. Is it possible to use SafeStrap on this one? Or better go for an older version of it?
Thanks in advance.

@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!

bArAbAts said:
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
Click to expand...
Click to collapse
I was thinking about trying... Maybe during the weekend..
Thanks for the advice, man!

I took my phone back to stock (from an oldish CM9 that had been working reasonably well for me for some time) so I could install SS3. Made the mistake of letting the phone OTA update itself and then had to find a new root hack before I could get SS3 installed.
Unfortunately the OTA update has messed with the radio, as reinstalling the CM9 I've used for months gets a system where the phone app just crashes.
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.

Well,
I installed the 3.0.5 version. Works like a charm! The easiest to use recovery that I ever use.
But the question is: Is it safe to downgrade it?
Sorry about the dumb question.

SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.

matthewgeier said:
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Click to expand...
Click to collapse
Is the issue you're having that when you're speaking to people on the phone you can't hear anything and they can't hear you? Cause on CM9 there should be no issues with using it as a phone as long as you don't enable bluetooth ever or use buttons on a headset connected to your phone. I haven't tried CM10 yet so I wouldn't know too much about that. Just for some extra info to save your time do not flash Liberty or Eclipse, they don't seem to work. The newest Maverick works fine.

matthewgeier said:
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
Click to expand...
Click to collapse
I was going to try from the stock.
I am much more familiar with clockworkmod.
Anyway, thank you for the advice
Sent from my XT860 using xda app-developers app

I'm an idiot please help

So in my infinite wisdom I deleted com.android.providers.media using titanium backup. I thought I had backed the file up but apparently I didn't. Either that or it didn't actually back the file up. Either way elements of my phone are now totally burned as you would imagine. No gallery, no music in my music player, and no ringtones. So my question is even if I do a factory reset will that help? Yes this was the stock ROM yes I tried installing a stock image on top of the ROM but the installation froze and I had to reboot and restore my nan droid. No I didn't have a nandroid of before I started dicking around. And finally yes I am a complete idiot. Any help would be much appreciated.
Sent from my MB886 using xda premium

Actually if some one would just be willing to use titanium backup to backup that file then post it here I could probably just restore it? Hope some one can help
Sent from my MB886 using xda premium

Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.

Sweet thanks man. So would u say that I should safely be able to install over the stock ROM? Or should I wipe then install? Also since these are stock I can install them to ROM slot stock right?
Sent from my MB886 using xda premium

skeevy420 said:
Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.
Click to expand...
Click to collapse
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.

metalmike6 said:
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.
Click to expand...
Click to collapse
That's where I'm at. On my stock rom, /system/etc/safestrap was added, logwrapper was modified to execute 2nd-init. AFAIK, that's all that was added. I'm so used to the Defy bootstrap method that I'm having a hard time getting used to SS - Defy BS was clearly laid out on what was executed and when that was done -- I've even looked at the SS source and its scripts and still can figure out what's the first script called by the 2nd-init loader....makes me feel super noob .

Well supposedly hash code said that after every restore and flash to the safe slot (stock) safe strap will reinstall itself on /system so if that's the case restoring any backup to that safe slot should be OK. But if that were the case no one would be able to brick. And I've seen people brick with and lose safestrap, and have to use RSD. Which is the road I don't want to have to go down. Really wish I had a definite answer because it seems like it should work but I don't want to do it unless some one who knows more about this than me confirms it.
Sent from my MB886 using xda premium

[Q] Rom Replacement Procedure

My wife's droid 3 has been acting up. I have done multiple factory resets and nothing has worked. Eventually the phone will start just freezing in the middle of an app and the phone has to go thru a battery pull. Currently installed is Steel Droid 4.8. Safestrap 1.08 is currently installed with the safe system enabled. I would like to replace the rom with minimoto. My wife doesnt need alot of bells and whistles. Just the basics and that everything works. IE wifi camera etc. What steps do I need to take and in what order so I can do this safely. Thanks in advance.

No response.....

Please help. Thanks.

HarielA4 said:
Please help. Thanks.
Click to expand...
Click to collapse
First install new safestrap 3.05 when you do this go to boot menu, create a rom slot and install new rom from your sdcard

So I don't have to disable the safe system first?
Sent from my DROID BIONIC using Tapatalk

HarielA4 said:
So I don't have to disable the safe system first?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Yes, you do. Disable safe system and restart the phone to stock. Start the safestrap app and uninstall recovery. Install the new safestrap. Start it and tap install recovery. Restart the phone to make sure it works.
That said, I can't think of any reason why Minimoto wouldn't work on the older version of safestrap. Minimoto doesn't use the kexec kernel extensions in safestrap 3.x (that I know of.)
So, rather than going through the trouble of uninstalling the old version of safestrap, installing the new one, creating a rom slot for it, etc., maybe just install Minimoto with the older safestrap? Just do a wipe data/factory reset in safestrap and flash Minimoto. You should be good to go.