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

I traded my Galaxy Nexus for a Bionic

'Ello lads!.. So yes, I've traded my Galaxy Nexus for a Bionic(+ cash) with some fine chap. Sure the Nexus has a bit of a screen advantage but performance wise I honestly don't notice a dfference. The big thing is I'm glad the reception issues I was having with the Nexus are gone.
Anyway, that's alo for now. Cheerio!

Welcome! Update to .901 so this phone doesn't piss you. Can be a real slag without that update.
Cheers!
Sent from my DROID BIONIC using XDA App

voxigenboy said:
'Ello lads!.. So yes, I've traded my Galaxy Nexus for a Bionic(+ cash) with some fine chap. Sure the Nexus has a bit of a screen advantage but performance wise I honestly don't notice a dfference. The big thing is I'm glad the reception issues I was having with the Nexus are gone.
Anyway, that's alo for now. Cheerio!
Click to expand...
Click to collapse
I am a bionic owner and love my phone, with that said you need to have your head examined I've been trying to get a nexus for weeks, lol. Just don't wanna pay $600 for it. If I could trade my bionic plus $200 or so I would be all over it!!!!!
Sent from my DROID BIONIC using Tapatalk

Nicelysedated said:
Welcome! Update to .901 so this phone doesn't piss you. Can be a real slag without that update.
Cheers!
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
So far I've done that Zerg manual root on the phone. Can I simply just download a ROM w/ .901 integrated or do I still have to do some sort of .901 update first?

lrs421 said:
I am a bionic owner and love my phone, with that said you need to have your head examined I've been trying to get a nexus for weeks, lol. Just don't wanna pay $600 for it. If I could trade my bionic plus $200 or so I would be all over it!!!!!
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
well, the battery life was pretty bad on the thing and was pissed that the 'extended battery' was only 250mAh more then the stock. on top of that, unless the phone was charging in 'ac mode', it would lose charge if you were trying to use it while in 'usb mode' charging. also i had severe reception issues with it(kept going back & forth from 3g to 4g & occasionally lost signal all together). and finally, i wanted the extra cash for something.
either way though i qualify for another upgrade this march anyway... pretty sure though that i'm just going to hold off until the quad's are out.

voxigenboy said:
So far I've done that Zerg manual root on the phone. Can I simply just download a ROM w/ .901 integrated or do I still have to do some sort of .901 update first?
Click to expand...
Click to collapse
If you look in one of the .901 threads you can find a link to.download the update. Flash it in bootstrap. After that you can change to any of the .901 compatible ROMs. I don't think the ROMs update the radio.
Sent from my DROID BIONIC using XDA App

voxigenboy said:
well, the battery life was pretty bad on the thing and was pissed that the 'extended battery' was only 250mAh more then the stock. on top of that, unless the phone was charging in 'ac mode', it would lose charge if you were trying to use it while in 'usb mode' charging. also i had severe reception issues with it(kept going back & forth from 3g to 4g & occasionally lost signal all together). and finally, i wanted the extra cash for something.
either way though i qualify for another upgrade this march anyway... pretty sure though that i'm just going to hold off until the quad's are out.
Click to expand...
Click to collapse
I was just poking fun . I'm sure you had your reasons. Welcome aboard.
Sent from my DROID BIONIC using Tapatalk

lrs421 said:
I am a bionic owner and love my phone, with that said you need to have your head examined I've been trying to get a nexus for weeks, lol. Just don't wanna pay $600 for it. If I could trade my bionic plus $200 or so I would be all over it!!!!!
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I would stay away from the nexus from what I have been reading. Getting some bad reviews.
I have a Tbolt and the Bionic and I like the Bionic better. The only thing the Bionic does not do is be on the phone and surf at the same time on 3G, but I never do that...
Now that I rooted the Bionic I like it even better, but just staying on the stock rom and stock radio I have no issues. Great phone...

kendive said:
I would stay away from the nexus from what I have been reading. Getting some bad reviews.
I have a Tbolt and the Bionic and I like the Bionic better. The only thing the Bionic does not do is be on the phone and surf at the same time on 3G, but I never do that...
Now that I rooted the Bionic I like it even better, but just staying on the stock rom and stock radio I have no issues. Great phone...
Click to expand...
Click to collapse
Yeah, in reality there is nothing wrong with my Bionic and once we get ICS I'll be content. Kudos to Moto for setting the trend, announcing the Bionic would get ICS before other manufacturers made statements about their devices.
Sent from my DROID BIONIC using Tapatalk

We will get ics. Just dont trust moto on time frames. We were supposed to have an unlocked bootloader end of last year. Its january 11 2012.

davwman said:
We will get ics. Just dont trust moto on time frames. We were supposed to have an unlocked bootloader end of last year. Its january 11 2012.
Click to expand...
Click to collapse
Anyone get CWR to work on the Bionic? It is suppose to work but I can't get it to reboot into recovery?

kendive said:
Anyone get CWR to work on the Bionic? It is suppose to work but I can't get it to reboot into recovery?
Click to expand...
Click to collapse
yeah the how to's in the dev section aren't exactly user friendly. basically though, i was not able to get CWM to work on it's own. you have to download that "Safestrap" .apk and install it. after doing so, it will install recovery itself. once that's done, you reboot your phone and press the MENU key once prompted, then you'll go into recovery.

voxigenboy said:
yeah the how to's in the dev section aren't exactly user friendly. basically though, i was not able to get CWM to work on it's own. you have to download that "Safestrap" .apk and install it. after doing so, it will install recovery itself. once that's done, you reboot your phone and press the MENU key once prompted, then you'll go into recovery.
Click to expand...
Click to collapse
Thanks I will get that a shot today.
Update... Working now. Thanks again

I may write out a few how to's with all the fixes.
I agree, out of all the phones/tabs I've rooted/ROM'd the how to's in the Bionic Dev section are a bit...lacking.
All the info is there, but it takes you 5 hours to figure it out b/c the steps, dummy guides, fixes are spread out all over the place between here and a few other forums.
Safestrap is really nice though.

got556 said:
I may write out a few how to's with all the fixes.
I agree, out of all the phones/tabs I've rooted/ROM'd the how to's in the Bionic Dev section are a bit...lacking.
All the info is there, but it takes you 5 hours to figure it out b/c the steps, dummy guides, fixes are spread out all over the place between here and a few other forums.
Safestrap is really nice though.
Click to expand...
Click to collapse
Yeah, your right. I don't know exactly what safestrap is (assuming its similar to bootstrap which I use) and when I tried to research it I got confused and just decided to stick with bionic bootstrap since I can't find a reason why its needed even though everyone talks about it.

I wouldn't use rom manager, just do everything in one of the two recoveries. Here's a breakdown of the recoveries for the Bionic
Bionic Safestrap
-Allows two system partitions
-One system is non-safe system where your main stock system resides. You can make and restore backups in this partition but you cannot install custom roms.
-The other system is safe system. This is the partion that lets you install roms and what not.
-You can toggle between the two systems from within safestrap recovery. It will automatically backup the current system before switching over.
-Safestrap has a nice feature that prevents bricks. On restart if Safestrap is installed there is a boot menu that pops up. You can hit the menu button to get into recovery from there. This comes in handy if you are having a bootloop. Just pull battery, restart phone and hit menu key when safestrap animation appears.
-One downside is that webtop doesn't work in safe system and the rom may run a tad bit slower in safe system partition
Bionic Bootstrap
-This is the riskier one
-This is more like regular clockwork recovery. You boot intro recovery from the bootstrap app.
-You can make backups, install roms etc in bootstrap recovery
-If you enter a bootloop while using bootstrap recovery, your phone is pretty much bricked. Because of the encrypted bootloader there is not a way to get back into recovery if using bootstrap. You will have to use sbf/fxz from a pc computer to unbrick your phone.
*You can use bootstrap to install a custom rom as your main system, and then install safestrap after if you want. But fully know what your are doing before you do this. If you don't use webtop, I recommend safestrap recovery for everything. Here is something I wrote over at Droidforums
-I have been testing roms out in safestrap to make sure they install and load up correctly
-I then toggle back to my main system in safestrap
-I then uninstall safestrap and install bootstrap.
-Then I boot into bootstrap recovery through that app
-Make a backup in bootstrap (always have a backup of your stock unmodified system)
-Wipe data and cach
-Install the Rom that I first tested in safestrap
-After Rom loads up and your are done flashing you can install safestrap again if you want. This way you will have a rom as your safe system and you can have another rom as your non-safe system. Webtop will work with roms on your main system.

stelv said:
I wouldn't use rom manager, just do everything in one of the two recoveries. Here's a breakdown of the recoveries for the Bionic
Bionic Safestrap
-Allows two system partitions
-One system is non-safe system where your main stock system resides. You can make and restore backups in this partition but you cannot install custom roms.
-The other system is safe system. This is the partion that lets you install roms and what not.
-You can toggle between the two systems from within safestrap recovery. It will automatically backup the current system before switching over.
-Safestrap has a nice feature that prevents bricks. On restart if Safestrap is installed there is a boot menu that pops up. You can hit the menu button to get into recovery from there. This comes in handy if you are having a bootloop. Just pull battery, restart phone and hit menu key when safestrap animation appears.
-One downside is that webtop doesn't work in safe system and the rom may run a tad bit slower in safe system partition
Bionic Bootstrap
-This is the riskier one
-This is more like regular clockwork recovery. You boot intro recovery from the bootstrap app.
-You can make backups, install roms etc in bootstrap recovery
-If you enter a bootloop while using bootstrap recovery, your phone is pretty much bricked. Because of the encrypted bootloader there is not a way to get back into recovery if using bootstrap. You will have to use sbf/fxz from a pc computer to unbrick your phone.
*You can use bootstrap to install a custom rom as your main system, and then install safestrap after if you want. But fully know what your are doing before you do this. If you don't use webtop, I recommend safestrap recovery for everything. Here is something I wrote over at Droidforums
-I have been testing roms out in safestrap to make sure they install and load up correctly
-I then toggle back to my main system in safestrap
-I then uninstall safestrap and install bootstrap.
-Then I boot into bootstrap recovery through that app
-Make a backup in bootstrap (always have a backup of your stock unmodified system)
-Wipe data and cach
-Install the Rom that I first tested in safestrap
-After Rom loads up and your are done flashing you can install safestrap again if you want. This way you will have a rom as your safe system and you can have another rom as your non-safe system. Webtop will work with roms on your main system.
Click to expand...
Click to collapse
Thanks I too was a little fuzzy on Safestrap. Now I know.

No problem. Here is a good link on safestrap http://rootzwiki.com/topic/8794-bionic-safestrap-bootstrap-recovery-12142011/page__fromsearch__1

kendive said:
I would stay away from the nexus from what I have been reading. Getting some bad reviews.
I have a Tbolt and the Bionic and I like the Bionic better. The only thing the Bionic does not do is be on the phone and surf at the same time on 3G, but I never do that...
Now that I rooted the Bionic I like it even better, but just staying on the stock rom and stock radio I have no issues. Great phone...
Click to expand...
Click to collapse
It's not possible to talk and surf at the same time on Verizon's 3g network. I don't believe that is a feature most people need or would even use, but it sounds good on the commercials.
Sent from my DROID BIONIC using XDA App

lrs421 said:
I am a bionic owner and love my phone, with that said you need to have your head examined I've been trying to get a nexus for weeks, lol. Just don't wanna pay $600 for it. If I could trade my bionic plus $200 or so I would be all over it!!!!!
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
The Nexus isn't worth it. I've tested it out and wasn't too impressed. One big thing I didn't like about it was that it only had 3 buttons compared to the normal 4 (home, back, search, menu). That might not be as big of deal with newer users who aren't as used to certain things, but I've been with Android for almost 3 years so the typical 4 buttons is a must as its something I became used to.
As far or the specs, its nothing to get excited about when they have much better coming out this spring and summer.
As far as ice cream sandwich, the bionic is getting it and will have Google's help with getting it set up for our phones.
Sent from my DROID BIONIC using XDA App

[How To] Two Roms on One Device

People have been asking in the dev forum alot about how to have two roms on the same device. So i thought I would make a how to.
You do this at your own risk.
Things Needed:
external SD
Get CWM for droid3
SafeStrap for droid3
stable rom to use as nonsafe [put on external SD]
rom to use as safe [put on external SD]
TiBu
1. (make sure you are in nonsafe, if you don't know what this means then dont worry). Do a backup of everything you will want to keep with TiBu.
2. Put the backup on external SD or on dropbox.
3. Uninstall any existing recoveries.
4. Reboot device.
5. Install cwm.
6. Reboot into CWM Recovery and install stable rom.
7. Reboot device.
8. Uninstall CWM and Then install safestrap.
9. Reboot into safestrap recovery.
10. Use volume rockers to go to safe boot menu.
11. Toggle safesystem.
12. select install a zip
13. choose safe rom
14. DONE "]
The nonsafe system will now contain your stable rom. and the safe system will contain your 'experimental' or second rom. I recommend not putting any new or buggy roms as your nonsafe. And this is already considered a dangerous thing to do. And give a huge thanks to hashcode for providing us with safestrap and koush for cwm :]
I currently use MavRom as a nonsafe. Its extremely stable and has not caused any issues at all.

Also if you want to transfer the safe to the nonsafe, use tibu to entirely back up the rom, system and user apps, you can then restore it after flashing it to nonsafe. Make a new backup folder to put it in so you don't mix it up with other backups from different roms
Sent from my XT860 using xda premium

I can't seem to get this to work with Cm7 as Safe rom and Cm9 as my experimental. I got Steel Droid to boot up and stock but I'm starting to think any rom that isn't blur based (which is really only cyanogen) isn't able to be dual booted. I just get a black screen after the splash screen I've been trying for a week now. If anybody is willing to give it a shot just to see if its me then please let me know of your findings but Mavrom Liberty SD all of those I can boot its cm7.1 or Cm9 that won't...
Sent from my DROID3 using Tapatalk

Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk

can somebody unite thiese 2 topics?
http://forum.xda-developers.com/showthread.php?t=1436380

Dri94 said:
Thwe blur based thing may be right. Im unsure, but cm7 to me personally shuld not be used as stable
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Damnit man I would rather not have to run cm7 as my stable rom seeing how I have no front facing camera support but the other features that the blur based roms lack just make it impossible to use as a daily driver. I need control over which buttons are in the notification widget and a few of the other features cm provides and none of the blurless roms give me that unfortunately... I'm determined to get this to work if its the last thing I do lol
Sent from my DROID3 using Tapatalk

Whats not working about it ?
Sent from my XT862 using Tapatalk

Dri94 said:
Whats not working about it ?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I can't get cm7 to boot up past the safestrap splash screen.... I start out with bootstrap boot cm7 up and then remove bootstrap and install safestrap thus making cm7 my non safe or main rom but upon rebooting the phone I just get the black screen after the splash screen... I can get into safestrap and switch to safe mode and run whatever rom I last had there or flash any nandroids I had in non safe mode but whatever rom I had on prior to installing safestrap (cm7 or cm9) they won't actually reboot. I thought cm9 would work which would really be a hastle keeping that as my non safe rom and cm7 as my main one on the safe side thus leaving me to redo the entire process everytime a new cm9 is released but cm9 wouldn't boot up past the initializing apps screen that first pops up... It counts up to all the apps I have then just stays stuck on starting applications or whatever it says, cm7 doesn't even boot up beyond the splash screen...
Edit: And I know that I'm doing it right because I have got Steel Droid to dual boot before I just can't understand y blurfree roms can't boot in non safe mode
Sent from my DROID3 using Tapatalk

ill test it when i get home.
Sent from my XT862 using Tapatalk

Dri94 said:
ill test it when i get home.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Appreciate it *fingers crossed*
Sent from my DROID3 using Tapatalk

Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk

Dri94 said:
Im sorry. I got behind on some work, when i catch up ill get back to you.
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
No pressure man I do appreciate the response tho lol
Sent from my DROID3 using Tapatalk

Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk

Dri94 said:
Ill do it tonight when i install the new ics :]
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I was gonna do the same lol hilarious
Sent from my DROID3 using Tapatalk

Lol cool :] lets see if we can both get it
Sent from my XT862 using Tapatalk

Ok im gonna give this another shot tonight..... haven't had the time or patience especially since I think its gonna fail again but ill update with my progress.... gonna try cm7 as the non safe and aokp as the safe one...
Sent from my DROID3 using Tapatalk

Ok, time to feel like a total noob.
So, my idea was to use safestrap to install aokp on the safe partition and leave my stock (+root) rom on the unsafe one.
I had bootstrap installed, just to back up my stuff and whatnot, so, I uninstalled it, installed safestrap, put all the stuff needed for AOKP ( rom, gsm patch and gapps ) and rebooted the phone. I enabled the safe system, and flashed rom, patch and gapps. then I rebooted, and I got into a loop where I would see the motorola logo ( the still one, which says "dual core technology" or something like that), then I got the safestrap splashscreen and if I pressed search, or left the phone idle so it would boot on it's own, it would get me to the motorola logo again, and repeat the loop.
I had to go back to the unsafe system and luckily it's all still there, but, since that point I tried every combination that I could think off, with wipes and I've flashed even just the rom, between wipes, and still, nothing.
I'm thinking that safestrap is not being able to write on the partition, or something like that, but I don't know how to solve it.
Any Ideas?
EDIT: I checked with a root explorer on /preinstall ( which I understand is the /system folder for the safe system ) and all the data seems to be there, but it's just not booting. Which makes me even more confused

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

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