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

.902 update keeps failing, any ideas?

I am forever rooted, and defrosted all the apps I froze with TB. Any ideas as to why this update keeps failing?
Sent from my DROID BIONIC using XDA App

Download the official update.
Open root explorer and go to the /cache/ directory.
Copy or move the update from there to your SD card.
Power off phone
Hold Volume up and down together and press power button
You see a menu. Hit volume down to go to recovery. Hit volume up to select it
Now you see a Droid and upside down triangle. Hit both volume buttons.
Now you are fully into stock recovery.
Choose the update with zip option.
When it fails it will tell you exactly why it failed.
Sent from my Microwave using Tapatalk and super heated water molecules

Sci3ntific1 said:
I am forever rooted, and defrosted all the apps I froze with TB. Any ideas as to why this update keeps failing?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Try here or here.

How did you download it I notice when I dl from phone it has no issues when I transfer from computer its a no go usually downloading again fixes it something to do with md5 mismatch I believe
Sent from my XT875 using XDA App

Another Problem...
I followed Legato Bluesummers advice, found out it was the modifications to systemui.apk I made. I pushed the original systemUI using root explorer, but now I just get a blank screen with no status bar or anything.

Sci3ntific1 said:
I followed Legato Bluesummers advice, found out it was the modifications to systemui.apk I made. I pushed the original systemUI using root explorer, but now I just get a blank screen with no status bar or anything.
Click to expand...
Click to collapse
Neither of those solutions worked for you?
Sent from my XT875 using Tapatalk

I downloaded the .902 update, ran from SD but it stalled because it wouldnt verify systemUI.apk. I have the dhacker tool and releasedroot tool but Im doing everything I can to not have to wipe my device. Stll cant get the stock systemUI.apk to work though, not sure what Im doing wrong

Sci3ntific1 said:
I downloaded the .902 update, ran from SD but it stalled because it wouldnt verify systemUI.apk. I have the dhacker tool and releasedroot tool but Im doing everything I can to not have to wipe my device. Stll cant get the stock systemUI.apk to work though, not sure what Im doing wrong
Click to expand...
Click to collapse
what system version are you on?

901 I believe

Sci3ntific1 said:
901 I believe
Click to expand...
Click to collapse
AWWW come on Dude... damn you should have said so a LOOONG TIME ago. There is no way to go from .901 to .902 unless your still on OTA's. I take it your not because you have this problem.
You have 2 choices
1. Go back to Stock 5.8.886 and then flash updates .893 and then .902(which you can find here)
2. Or Flash the .902 Stock FXZ using RSD lite. It will put you on .902 without having to applied updates manually. Loacted here. Copy the stuff you want to keep to your PC or External SDcard as is way wipes Internal Sdcard(which isnt a real problem)
Thats it dude. Anyone else will tell you the same thing.
CHEERS!!
PM me if you want instructions on all of this..

Thanks for all your help, I was trying to avoid wiping but now that I know its not possible Ill just go ahead and do it. Thanks for all your help.

Sci3ntific1 said:
Thanks for all your help, I was trying to avoid wiping but now that I know its not possible Ill just go ahead and do it. Thanks for all your help.
Click to expand...
Click to collapse
no prob man
You can back up all your apps/game data/ call log and all that good stuff using Titanium Backup

[Q] How safe is safestrap?

I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!

First off, I have an XT862 not the XT860. The hijack is a 2nd init hijack. Safestrap does this hijack itself as opposed to with bootstrap where whatever ROM you flash has to do the hijack. Safestrap also as you mentioned uses /preinstall to store /system of the ROM you flash. This means that nothing other than safestrap itself touches your stock /system. This allows safestrap to protect itself so you can always get back to recovery even if there is a bad flash it can't overwrite the hijack and recovery so you can try again.
I also don't remember seeing much of problems with safestrap itself other than a partition size problem. I think I remember seeing that some update took care of that problem. I have seen people having more problems with ROMs on the XT860 than other versions of the phone.

danifunker said:
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
Click to expand...
Click to collapse
First off, the most common problem I have seen people have with safestrap is not understanding what it does and even more common is not knowing how to use it, basically a lot of user error. The previous poster summed up pretty well how it works. Finally, uninstalling safestrap will NOT bring you back to original stock, it will remove itself and the secondary ROM it allowed you to install. Since you have to be rooted to even install it, if you uninstall it you will still be rooted, not stock.
Just so you are clear, you can have whatever ROM you want on your phone BEFORE installing Safestrap and this will become the Safe system by default. You will no longer be able to change this ROM as long as Safestrap is installed. Instead, it allows you to put another ROM, basically a dual-boot, in addition to the original rom you have. Now you have a Safe system and a Non safe system. The Non safe system is the only one Safestrap will allow you to change (and brick for that matter). So if/when you install a ROM that boot loops or crashes, you simply can revert back to your safe system and now your phone works again, neat huh?

AFAIK, he does have the XT860, since the XT862 is the Verizon Droid 3 (3G, not Bell Canada 4G). Also, using it on my 862, I have not been able to brick it. If flashing the experimental system fails, you can just reboot into the Safestrap menu and flash something new. I don't see why it wouldn't work on the 860, as all it does it modify the booting. Any issues would most likely be caused by a ROM flashing issue, not safestrap.

I took the plunge this afternoon... Installed SafeStrap and CM9 nightly on my device... Not sure if everything is working just yet, but will be doing testing throughout the day
No problems were reported with the installation or instructions, so that's great. Thanks a lot!

I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.

Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.

Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium

Endoroid said:
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I realize that before reviewing its radio specs.
Munckster said:
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Click to expand...
Click to collapse
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.

Thiago AmP said:
Yeah, I realize that before reviewing its radio specs.
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Click to expand...
Click to collapse
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium

Endoroid said:
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I've already tried it, but without success... I'll keep searching what to do in this situation...

Thiago AmP said:
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
Click to expand...
Click to collapse
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.

doogald said:
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
Click to expand...
Click to collapse
I've tried it several times before I came with the idea of unroot my phone and redo the process. Here is my dicoveries http://forum.xda-developers.com/showthread.php?t=2082292
I know that it's obvious, but I guess that just few people knew that it would work.

SafeStrap problems
Odd problem, I can't get the menu button to work. In order to get back to my "safe" rom I have to start safestrap,and select uninstall recovery.
Then reboot, and it will bring up my "Safe" rom. If I then go back to SafeStrap, and re-install the recovery, and reboot, it will again bring up SafeStrap, but if I hit Menu, it doesnt' bring up any options it again boots up my non-safe ROM (minimoto 1.6)
Anyone have any ideas...I guess I can try to remove the safestrap directory on the sdcard after I uninstall the recover, and then try to reinstall the App, and try all over again?

[Q] Missing /preinstall files for ota update

I am trying to update to ics from 2.3.6 I have uninstalled safestrap and frozen root with otarootkeeper. I get hung up during install, so I checked my error log. It seems I am missing files from /preinstall specifically from /knowyourdevice which no longer exists. Is there a way of getting a copy so I don't need to go through fast boot? There was a link up elsewhere, but it's dead. Any help is greatly appreciated.

I recommend to flash fastboot 4.0.4 files.

I know, but this has turned into a pet project for me. I was really hoping to do it the hard way. There was a link up in the dev forum, but it's dead now...

I had the same issue when upgrading. Turns out, the update scans your system for ANY modifications that would signify you were, or had been rooted. You either need to completely remove anything that signifies you are rooted and any apps that require root, or sbf to either gb or ics. Doing a simple factory format still leaves files behind. Honestly, just doing an sbf would easier, as it ensures your system is 100% clean. If you need new links to the one click sbf, I can pm you a link later.
Sent from my DROID4 using xda premium

I had this problem and just downloaded the fastboot files, extracted the /preinstall archive from there, and copied it to my phone using adb. Simple.
Sent from my DROID4 using Tapatalk

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