Related
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
How compareable is flashing roms on the Droid 3 compared to the HTC Eris. I'm tired of the lag and bloat and wish to try some new ROMs. I just don't want brick my phone. Rooting looked simple but I don't understand bootstrap/safestrap. Any help would be greatly appreciated!
Sent from my DROID3 using XDA App
jwanny10 said:
How compareable is flashing roms on the Droid 3 compared to the HTC Eris. I'm tired of the lag and bloat and wish to try some new ROMs. I just don't want brick my phone. Rooting looked simple but I don't understand bootstrap/safestrap. Any help would be greatly appreciated!
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Get bootstrap/safestrap from the internet -- install the app.
Run the app, install recovery.
Turn phone off.
Press m + power.
Scroll to BP Tools -- select it.
You're in custom recovery.
Which is better, bootstrap or safestrap?
Sent from my DROID3 using XDA App
jwanny10 said:
Which is better, bootstrap or safestrap?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap by far, the rom will install to another partition /preinstall rather that /system. This keeps the VZW rom intact to prevent bricking and still get OTAs easily. It's practically impossible to brick it using Safestrap.
Thanks, I'll be giving this a try!
Sent from my DROID3 using XDA App
So root (obviously), install safestrap, then I just boot into recovery via safestrap and flash Liberty 2.0? Just being anal, the more I read the less confident I get. Once I burst my cherry, I should feel better. Lol. Thanks for all the help everyone!
Sent from my DROID3 using XDA App
if ur stock 5.6.890, root, install otarootkeeper, install safestrap, open the app, install recovery, boot into recovery (during boot you will hit menu), backup data, toggle safe mode, install ROM, wipe data/cache, reboot
---
check http://hash-of-codes.blogspot.com/p/android-downloads.html for safestrap and CM7 downloads. also if you are on 5.7.894 you will need to use his patch to run any roms.
Did you mean wipe data/cache THEN install ROM?
Sent from my DROID3 using XDA App
jwanny10 said:
Did you mean wipe data/cache THEN install ROM?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
most roms either way will work
Rooted, install ota rootkeeper, installed and ran safestrap, rebooted into recovery, tried to turn on safe mode and got error. rebooted and tried to make a back up, got error.
Error occured when attempting to make backup image of /data
Happened both times. Am I royally screwed?
Phone works still but I don't dare flashing a ROM until I get safe mode. Hints?
If im not mistaken, rootkeeper doesnt need to be used unless you are going to install 5.7.894, as it messes with your roms ability to access SU
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
My phone had trouble mounting as R/W when i got a SU update via the superuser app off the market, i unprotected and updated my binary again and it worked fine. Keep OTA Rootkeeper installed, activate it before upgrading to an update that has no root method yet, then after you reinstall SU, and reestablish the symlink in your new update, remove the protection and verify you still have root. Its not necessary for CWM recovery tasks though
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
So if I lose ota rootkeeper, I can create a backup? My problem is I can't create a data backup or switch to safe mode. It gives me an error message that says unable to create backup image of /data. Am I corrupted? My phone still works as far as I know.
Sent from my DROID3 using XDA App
jwanny10 said:
So if I lose ota rootkeeper, I can create a backup? My problem is I can't create a data backup or switch to safe mode. It gives me an error message that says unable to create backup image of /data. Am I corrupted? My phone still works as far as I know.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap and bootstrap(I believe) have issues creating a backup of a file that cannot be changed. So yes if you remove it, then you be able to use safestrap correctly.
Sent from my DROID3 using XDA App
Removed ota rootkeeper changes still get "Error occurs in creating backup image of /data"
Any other ideas.
Running Verizon 5.6.890 stock blur. Used psouza one click root. Ran debloat script, but I don't think I did it right.
Sent from my DROID3 using XDA App
I tried to run the debloat restore and then make a backup, but still the same error. I noticed in the thread pertaining the debloat script that someone also gets it to run until myverizon.apk messes it.
Making backups and flashing new ROMs was so easy with the Eris. I apologized because I'm such a noob when it comes to Moto Droids and scripting.
Sent from my DROID3 using XDA App
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?
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.
I've tried deleting the bloatware manually using a root explorer but it isn't letting me delete them. I've tried using Titanium Backup as well and it says it uninstalls the apps, but when I check my app drawer they're still there. What's wrong with my phone? All root apps are working perfectly so I have no idea what's going on. Anyone know what the problem is? This is on my Verizon Moto X, by the way.
Try freezing apps with titanium backup instead of deleting them.
finalarcadia said:
Try freezing apps with titanium backup instead of deleting them.
Click to expand...
Click to collapse
Tried that, nothing happens. I've never seen this on any phones I've rooted in the past and have no idea how to go about fixing it.
I believe the moto x root method only allows you to make permanent changes when booted through the recovery. So try that.
finalarcadia said:
I believe the moto x root method only allows you to make permanent changes when booted through the recovery. So try that.
Click to expand...
Click to collapse
What do you mean exactly? Go into recovery and reboot from there? Oh and by the way, freezing in TiBu worked, but I need to uninstall the MyVerizon app. It doesn't work. When I open it it just freezes up, hence why I'm trying to remove it so that I can install it from the Play Store directly.
bd1212 said:
What do you mean exactly? Go into recovery and reboot from there?
Click to expand...
Click to collapse
Recovery is hijacked into a version of the system with system-write enabled. So it is no longer a recovery. All you need to do is boot into recovery and it will seem like you're booting normally, but you can do root changes. Then reboot normally after you're done.
Also, this is why I don't like to root my moto x. Way too complicated and it messes with OTAs. (never take an OTA when already rooted, since you don't have a real recovery you will end up in a boot loop. There are certain steps you need to take.)
finalarcadia said:
Recovery is hijacked into a version of the system with system-write enabled. So it is no longer a recovery. All you need to do is boot into recovery and it will seem like you're booting normally, but you can do root changes. Then reboot normally after you're done.
Also, this is why I don't like to root my moto x. Way too complicated and it messes with OTAs. (never take an OTA when already rooted, since you don't have a real recovery you will end up in a boot loop. There are certain steps you need to take.)
Click to expand...
Click to collapse
Wow, that seems like a really complicated root exploit. I wasn't aware it was like that. The only reason I rooted was to add the one-click toggles to the quicksettings page in the notification bar and to add in a few other toggles (e.g. rotation toggle). The bloatware was just something I noticed today that I figured I'd remove (mostly the MyVerizon app, since I actually need that to work since I use it frequently). I am aware that I should never take an OTA, though. That part is clear to me. Thanks for the help, man!
finalarcadia said:
Recovery is hijacked into a version of the system with system-write enabled. So it is no longer a recovery. All you need to do is boot into recovery and it will seem like you're booting normally, but you can do root changes. Then reboot normally after you're done.
Also, this is why I don't like to root my moto x. Way too complicated and it messes with OTAs. (never take an OTA when already rooted, since you don't have a real recovery you will end up in a boot loop. There are certain steps you need to take.)
Click to expand...
Click to collapse
So I just tried to uninstall the MyVerizon app using TiBu after booting through recovery and I still can't uninstall it. Any ideas?
What root method did you use?
Sent from my XT1053 using XDA Premium 4 mobile app
Rhiannon224 said:
What root method did you use?
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
RockMyMoto
Sent from my XT1060 using xda app-developers app
bd1212 said:
RockMyMoto
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Are you using safestrap? Check the settings in TIBU, is there an option for freezing system apps? Maybe that's the problem.
Sent from my XT1053 using XDA Premium 4 mobile app
Before you go deleting bloatware--could you send me the "CallerID" bloatware app? I really need it; if you do, I'll walk you through every step of the way.
What's the file name?
Sent from my XT1060 using Tapatalk
icon123 said:
What's the file name?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I honestly have no clue. :| It's only on the Verizon MotoX as far as I know. It's "CallerID" something. It's in /system/apps. The icon is green, I know that much.