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
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?
A friend of mine has Droid 3 on Verizon. I'm want to know what I need to do to flash a recovery on it so I can backup and flash roms on it. I'm not sure if I need a custom bootloader for it aswell. I found this thread with recovery as a sticky but it doesn't have much explanations in it. I also see you guys don't have a sticky with a guide anywhere besides just the one click root.
Can anyone point me in a direction?
Thank you.
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
slayer621 said:
On my phone so I can't give links. But you need safestrap. It's a bootstrap that will essentially allow your phone to boot into recovery even with the locked bootloader.
Safestrap is unique because it does not touch your primary system. You can back it up, but you flash everything to a "safe" system. It is ideal because no matter what you doing to your safe system, your primary will always be there. Even if you flash something that you know will brick your phone, all that will happen is that you won't be able to boot into your safe system. You can still load up your custom recovery and switch back to your primary system where you can download a different ROM.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
So how do I install this safe strap and where do I get it. I assume this will also let me flash a custom recovery like CWM?
Everything you need to know on installing safestrap can be found here
There are 2 versions. One is the standard version in the link, the other is a "tweaked" version found on the forums here. While the tweaked version has a few extra features, from what I've read, it can be a bit unstable. Use the version provided in the link.
Yeah what he said ^^^ then once u have the safestrap you just download the rom u want and flash it and your good to go
Sent from my XT883 using Tapatalk
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
obsanity said:
Ok. So far I can understand that the Moto Droid 3 has a locked boot loader which can not be unlocked. Correct?
I can understand using a bootstrap instead. Can someone explain what happens to your first system when the safe mode is turned on? Does it move the contents into the available internal SD card? What kind of memory is emmc? Also, I'm not clear on what is hijack. Is that just the initial hack from the apk on 1st system? I assume one can install it again in the 2nd system and mess things up.
Click to expand...
Click to collapse
The 1st system gets renamed to systemorig and is otherwise left untouched. /reinstall gets renamed to /system and becomes your safe mode system. Im not 100% on hijack but as I understand it, it quite literally hijacks the boot sequence at a certain point by killing all the processes and inserting its own in order to give us a custom recovery
Sent from my XT860 using xda premium
OK. So why not just backup the original system and overwrite it? If the partition gets renamed why is there a need to keep it? Wouldn't deleting it give more room for roms? Is there even enough room for 2 partitions on the emmc?
The whole idea was that you keep your original system intact so you can still receive OTA updates. I've never had an issue with not having enough room for roms. They are only about 150 MB.
Many of us actually use this to dual boot. The common way is to have a stable rom on your /systemorig and test new roms on safe system.
There is a plain old bootstrap that installs regular old cwr and just overwrites /system. Everything should be compatible with it. I think I have a copy of it in my dropbox
The main reason for using safestrap(in my view) is that when you're messing around in safemode its next to impossible to brick your phone so bad you can't access recovery, since when it first boots it still boots from /system, and then redirects to the safe system. You should never have to fastboot flash your phone
Sent from my XT860 using xda premium
So can you dual boot? And how do you boot into your orig 1st system? Don't you have to toggle the safe mode each time? Also, how much total room is there on emmc on D3?
try here :
http://forum.xda-developers.com/showthread.php?t=1436380
The internal SD memory is roughly 11GB. The phone stores which system was last booted and then you can backup and restore between them though the SafeStrap pre-boot recovery. Once you try it, it's really simple and effective. I was hesitant to leave old faithful bootstrap, but now that I'm on safestrap, I wonder why I ever hesitated.
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Also, do I download ver 1.09 which says Droid 4? I have a Droid 3.
obsanity said:
So the 1st system is simply copied to SD storage when the safe mode is turned on?
Click to expand...
Click to collapse
It creates a backup of /system and /data when you switch between safe and non safe. And I think also /cache. However as I mentioned before it renames /system to systemorig.
Sent from my XT860 using xda premium
It runs off the /preinstall partition IIRC. You should/can DL the original from Hash's blog or get Rick's tweaked version from the Dev section.
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
obsanity said:
I downloaded and installed ver 1.0.8 because the other 1.0.9 said Droid 4.
Click to expand...
Click to collapse
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Endoroid said:
I do believe that's the correct version. I'm running a tweaked version that includes a bash console and a redesigned ui but its kinda buggy atm so for now I would recommend the one you've got
One other thing I should point out, as this is a common mistake, the first time you switch to safe mode you HAVE to flash a rom. Because you're now running off the /preinstall, there is no safe mode rom yet. A lot of ppl switch to safe then boot up straight away and all you get is a blank screen cause you're booting...well nothing
Also I'm not sure if you have a rom in mind already but mavrom is the only gb rom that still gets updates. Everyone else is deving ics, however all ics roms are beta and have more or less the same bugs/missing features
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I just did it on his phone. All worked OK. Thanks for all your help. I'm used to the nexus devices which are much easier and straightforward. I installed nightly CM9 from hashcode. I'm not sure what works yet. Is there a better version of CM9 besides that one? He really wants ICS and CM.
All of the ICS roms are currently limited in the same way: no HW codecs, bluetooth on but not connected = loss of audio, etc. There's a thread here in the general section that compares all of the ICS roms. I would advise looking through it and deciding which one suits you best.
EDIT: to answer your question, the may 7 build of Hashcode's CM9 is a good build. They just brought back the theme engine so that opens up possibilities.
Sent from my DROID3 using xda premium
I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.
DiGi91 said:
I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.
Click to expand...
Click to collapse
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app
ruben8448 said:
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will consider doing that, it's just a giant PITA since I will have start from scratch.. Coming from the S III and flashing a new ROM every day this is so different to me lol. There is nothing wrong with the stock ROM just regretting not waiting for the dev edition to be honest.. I still use my S III as a media player and lately have been thinking of switching back, just hoping we get 4.4 soon or something to make it a bit better.
I know safe strap is another option but haven't heard great things about it and back in the droid 3 days remembered using it.
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Can you use the new FXZ to return to OTA'd stock if necessary down the road?
pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap
anotherfiz said:
Can you use the new FXZ to return to OTA'd stock if necessary down the road?
Click to expand...
Click to collapse
Yup, stock OTA, but you can't go back to a previous version
DiGi91 said:
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap
Click to expand...
Click to collapse
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.
jayboyyyy said:
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.
Click to expand...
Click to collapse
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?
http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's
DiGi91 said:
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?
Click to expand...
Click to collapse
if you are worried about space then just flash it to the stock rom. I have plenty of space. with 500 photos on it. I don't use music though. You don't have to rsd to get the ota. You can just flash the recovery.img if you didn't touch the system or flash the system.img as well if you need to using fastboot. Take some time to learn what fastboot and adb are and how to use them and you will be happy you did. Doesn't take much time at all. They are kind of the same thing, how they work at least.
Use fastboot when in fastboot mode. Use adb when the phone is just on normally. Then run appropriate commands. "adb reboot" "fastboot reboot"
here is a link on how to use adb and if you go through it and understand everything then you will also understand fastboot and fastboot will already be installed as well). Then you can take the ota without losing data and having to use RSD.
http://forum.xda-developers.com/showthread.php?t=872128
As for the new radios, you will need to use fastboot. you flash the non-hlos.bin then erase modemst1 and modemst2 then flash the fsg.mbn. if you want help with it just send me a pm
shane1 said:
http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's
Click to expand...
Click to collapse
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.
Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.
shane1 said:
Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.
Click to expand...
Click to collapse
So boot into SS, backup my stock ROM - save on my pc, then make a ROM slot in SS and restore the backup to the slot? Can you even do that lol
Then if all is well flash the SS OTA ROM on top and I SHOULD be okay..
Might give it a shot likely need to update SS idk what the latest version is
DiGi91 said:
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.
Click to expand...
Click to collapse
I just flashed it over my stock backup and it worked but doesn't fix wifi
shane1 said:
I just flashed it over my stock backup and it worked but doesn't fix wifi
Click to expand...
Click to collapse
That is a big issue, I need WiFi working...
I finally got around to messing with SS and the OTA ROM and did a backup of my stock slot and flashed the ROM to it. everything was working but no WiFi and I can't deal with that =/
Ended up restoring my stock slot backup.
I did however manage to update the baseband, super easy!
EDIT: Flashed the ROM on XDA and now I have working WiFi, looks like the one on droidrzr didn't work for me.
I have a Verizon moto X DE with TWRP recovery installed. I was wondering is it possible to install safestrap recovery also? Or if I wanted to install safestrap recovery would I have to re wipe and start over?
Sent from my XT1060
Why would you want to install Safestrap Recovery, if you have an unlocked bootloader and TWRP already installed.
Mr. Orange 645 said:
Why would you want to install Safestrap Recovery, if you have an unlocked bootloader and TWRP already installed.
Click to expand...
Click to collapse
In order to switch from stock rom to another rom without reloading things.
Sent from my XT1060
Swimboy46163 said:
In order to switch from stock rom to another rom without reloading things.
Sent from my XT1060
Click to expand...
Click to collapse
Just make a nandroid back up. That's what nandroids are for and it does the same thing as what you're wanting to do.
Mr. Orange 645 said:
Just make a nandroid back up. That's what nandroids are for and it does the same thing as what you're wanting to do.
Click to expand...
Click to collapse
Not as quick. You have to load and reload apps.
Sent from my XT1060
Swimboy46163 said:
Not as quick. You have to load and reload apps.
Sent from my XT1060
Click to expand...
Click to collapse
I don't know what you are referring to by loading and reloading apps, I guess. Here's the procedure for both recoveries for installing and switching between ROMs:
TWRP:
1. Set up Stock OS they way you like it. Settings, apps, etc.
2. Reboot into TWRP Recovery
3. Perform nandroid backup of Stock ROM.
4. Wipe System/Data
5. Install Custom ROM
6. Boot system and set up ROM how you like it. Settings, apps, etc.
7. Reboot into TWRP Recovery
8. Perform nandroid backup of Custom ROM.
Now you can switch between Stock and Custom without having to reload any apps. Once you restore, everything goes back to the way you saved it, apps and all. You can load as many Custom ROMs as you want and just keep them as nandroid backups. Then when you want to switch, you just restore the appropriate nandroid.
Safestrap Recovery:
1. Set up Stock OS the way you like it. Settings, apps, etc.
2. Reboot into Safestrap
3. Back up Stock (Safe) side
4. Activate Custom side.
5. Create slot for Custom ROM
6. Install Custom ROM
7. Boot System and set up ROM how you like it. Settings, apps, etc.
8. Reboot into SafeStrap Recovery
9. Perform nandroid back up of Custom ROM.
You can add different ROMS to each slot, and switch on the fly, but you still have to download apps and set everything up the first time for each ROM. Plus, by creating slots, your are dividing the devices resources such as storage and memory between each slot and the stock side, so less is available.
Keeping nandroid backups allows you to do the same exact thing without keeping a stock ROM and a custom ROM both loaded up on the device at the same time sharing resources.
Safestrap was merely a workaround for an unlockable bootloader, and an ability to quarantine your stock ROM, so if you mess up the custom ROM, you can just switch back to the Stock side. This was necessary, because without an unlocked bootloader, you couldn't always just flash back the factory image. Having the bootloader unlocked and the availability of factory images direct from Motorola eliminates the need for Safestrap.
Believe me, it is much more advantageous to have TWRP and just make nandroid backups, BUT if you insist on using Safestrap, then you will likely need to flash back to stock and lock your bootloader through mfastboot. Then you would treat your Moto X like a consumer version and follow the appropriate instructions in this forum for rooting and installing Safestrap. That's a lot of work and you're giving up the main advantage for having an unlockable bootloader, but that is your choice.
Swimboy46163 said:
Not as quick. You have to load and reload apps.
Sent from my XT1060
Click to expand...
Click to collapse
Nope. Phone is exactly how it was when you did the backup.
However....is this twrp restore working? I'd be sure of that first. I had to use cwm ...only thing I could get restores to work with.
Sent from my Moto X cellular telephone...
Mr. Orange 645 said:
I don't know what you are referring to by loading and reloading apps, I guess. Here's the procedure for both recoveries for installing and switching between ROMs:
TWRP:
1. Set up Stock OS they way you like it. Settings, apps, etc.
2. Reboot into TWRP Recovery
3. Perform nandroid backup of Stock ROM.
4. Wipe System/Data
5. Install Custom ROM
6. Boot system and set up ROM how you like it. Settings, apps, etc.
7. Reboot into TWRP Recovery
8. Perform nandroid backup of Custom ROM.
Now you can switch between Stock and Custom without having to reload any apps. Once you restore, everything goes back to the way you saved it, apps and all. You can load as many Custom ROMs as you want and just keep them as nandroid backups. Then when you want to switch, you just restore the appropriate nandroid.
Safestrap Recovery:
1. Set up Stock OS the way you like it. Settings, apps, etc.
2. Reboot into Safestrap
3. Back up Stock (Safe) side
4. Activate Custom side.
5. Create slot for Custom ROM
6. Install Custom ROM
7. Boot System and set up ROM how you like it. Settings, apps, etc.
8. Reboot into SafeStrap Recovery
9. Perform nandroid back up of Custom ROM.
You can add different ROMS to each slot, and switch on the fly, but you still have to download apps and set everything up the first time for each ROM. Plus, by creating slots, your are dividing the devices resources such as storage and memory between each slot and the stock side, so less is available.
Keeping nandroid backups allows you to do the same exact thing without keeping a stock ROM and a custom ROM both loaded up on the device at the same time sharing resources.
Safestrap was merely a workaround for an unlockable bootloader, and an ability to quarantine your stock ROM, so if you mess up the custom ROM, you can just switch back to the Stock side. This was necessary, because without an unlocked bootloader, you couldn't always just flash back the factory image. Having the bootloader unlocked and the availability of factory images direct from Motorola eliminates the need for Safestrap.
Believe me, it is much more advantageous to have TWRP and just make nandroid backups, BUT if you insist on using Safestrap, then you will likely need to flash back to stock and lock your bootloader through mfastboot. Then you would treat your Moto X like a consumer version and follow the appropriate instructions in this forum for rooting and installing Safestrap. That's a lot of work and you're giving up the main advantage for having an unlockable bootloader, but that is your choice.
Click to expand...
Click to collapse
How does TWRP back up the downloaded apps, system files, and all other miscellaneous files that's about 8 Gb into a 3 Gb package
Sent from my XT1060
Swimboy46163 said:
How does TWRP back up the downloaded apps, system files, and all other miscellaneous files that's about 8 Gb into a 3 Gb package
Sent from my XT1060
Click to expand...
Click to collapse
It doesn't back up your sd card. but if you don't wipe the sd card it stays safe when flashing.
Sent from my Moto X cellular telephone...
Swimboy46163 said:
How does TWRP back up the downloaded apps, system files, and all other miscellaneous files that's about 8 Gb into a 3 Gb package
Sent from my XT1060
Click to expand...
Click to collapse
Same way Safe strap does it. It makes a system IMG of the current ROM, apps, and settings and restores it all just how you left it.
I've never seen an 8GB nandroid back up file...they are usually between 1GB and 2GB. And I'm not sure what 3GB package you are talking about...The DE is a 32 GB model, so you have plenty of storage available.
The nandroid backup is 2.6 Gb and the total system is about 8 Gb. And when you do a nandroid back up how does it know not to delete the backup when you wipe the systen
Sent from my XT1060
Mr. Orange 645 said:
Same way Safe strap does it. It makes a system IMG of the current ROM, apps, and settings and restores it all just how you left it.
I've never seen an 8GB nandroid back up file...they are usually between 1GB and 2GB. And I'm not sure what 3GB package you are talking about...The DE is a 32 GB model, so you have plenty of storage available.
Click to expand...
Click to collapse
The nandroid backup is 2.6 Gb and the total system is about 8 Gb. And when you do a nandroid back up how does it know not to delete the backup when you wipe the system
Sent from my XT1060
Mr. Orange 645 said:
I don't know what you are referring to by loading and reloading apps, I guess. Here's the procedure for both recoveries for installing and switching between ROMs:
TWRP:
1. Set up Stock OS they way you like it. Settings, apps, etc.
2. Reboot into TWRP Recovery
3. Perform nandroid backup of Stock ROM.
4. Wipe System/Data
5. Install Custom ROM
6. Boot system and set up ROM how you like it. Settings, apps, etc.
7. Reboot into TWRP Recovery
8. Perform nandroid backup of Custom ROM.
Now you can switch between Stock and Custom without having to reload any apps. Once you restore, everything goes back to the way you saved it, apps and all. You can load as many Custom ROMs as you want and just keep them as nandroid backups. Then when you want to switch, you just restore the appropriate nandroid.
Safestrap Recovery:
1. Set up Stock OS the way you like it. Settings, apps, etc.
2. Reboot into Safestrap
3. Back up Stock (Safe) side
4. Activate Custom side.
5. Create slot for Custom ROM
6. Install Custom ROM
7. Boot System and set up ROM how you like it. Settings, apps, etc.
8. Reboot into SafeStrap Recovery
9. Perform nandroid back up of Custom ROM.
You can add different ROMS to each slot, and switch on the fly, but you still have to download apps and set everything up the first time for each ROM. Plus, by creating slots, your are dividing the devices resources such as storage and memory between each slot and the stock side, so less is available.
Keeping nandroid backups allows you to do the same exact thing without keeping a stock ROM and a custom ROM both loaded up on the device at the same time sharing resources.
Safestrap was merely a workaround for an unlockable bootloader, and an ability to quarantine your stock ROM, so if you mess up the custom ROM, you can just switch back to the Stock side. This was necessary, because without an unlocked bootloader, you couldn't always just flash back the factory image. Having the bootloader unlocked and the availability of factory images direct from Motorola eliminates the need for Safestrap.
Believe me, it is much more advantageous to have TWRP and just make nandroid backups, BUT if you insist on using Safestrap, then you will likely need to flash back to stock and lock your bootloader through mfastboot. Then you would treat your Moto X like a consumer version and follow the appropriate instructions in this forum for rooting and installing Safestrap. That's a lot of work and you're giving up the main advantage for having an unlockable bootloader, but that is your choice.
Click to expand...
Click to collapse
So no need for a titanium backup of all my apps and texts or anything?
Sent from my XT1060
Swimboy46163 said:
The nandroid backup is 2.6 Gb and the total system is about 8 Gb. And when you do a nandroid back up how does it know not to delete the backup when you wipe the system
Sent from my XT1060
Click to expand...
Click to collapse
I have a nandroid backup on my phone right now that is 1.8 GB, but you may have more apps than I do. But that 1.8GB is a total system image. It includes all system files, apps, data, settings.
As far as deleting the nandroid, it is not stored in /system, so wiping that partition will not touch the nandroid backup file. The backup file is stored in the /media portion, same as your pictures, videos, and music files. Unless you choose to wipe Internal Storage in TWRP, you will not delete the nandroid backup file.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
Swimboy46163 said:
So no need for a titanium backup of all my apps and texts or anything?
Sent from my XT1060
Click to expand...
Click to collapse
The nandroid is basically a photograph of the ROM when you backed it up. Any changes you make after the backup will not be saved. It best to do a backup right before wiping and flashing. Just remember, when you install the new ROM or restore the backup of a different custom ROM, none of that carries over. I back up my texts through the MySMS app, which syncs it accross devices. You can still use titanium back up to restore app data (and ONLY app data...never use it to restore system data) if you're concerned about losing your place in a game, etc... I believe there is also an option in TWRP to selectively restore the data portion of your backup, which would include all downloaded apps and the data for them.
Out of curiosity, is this the first phone you've owned with an unlocked bootloader? (Nexus, OG Droid, etc...)
Mr. Orange 645 said:
I have a nandroid backup on my phone right now that is 1.8 GB, but you may have more apps than I do. But that 1.8GB is a total system image. It includes all system files, apps, data, settings.
As far as deleting the nandroid, it is not stored in /system, so wiping that partition will not touch the nandroid backup file. The backup file is stored in the /media portion, same as your pictures, videos, and music files. Unless you choose to wipe Internal Storage in TWRP, you will not delete the nandroid backup file.
---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------
The nandroid is basically a photograph of the ROM when you backed it up. Any changes you make after the backup will not be saved. It best to do a backup right before wiping and flashing. Just remember, when you install the new ROM or restore the backup of a different custom ROM, none of that carries over. I back up my texts through the MySMS app, which syncs it accross devices. You can still use titanium back up to restore app data (and ONLY app data...never use it to restore system data) if you're concerned about losing your place in a game, etc... I believe there is also an option in TWRP to selectively restore the data portion of your backup, which would include all downloaded apps and the data for them.
Out of curiosity, is this the first phone you've owned with an unlocked bootloader? (Nexus, OG Droid, etc...)
Click to expand...
Click to collapse
Yeah. Thanks for the help. Just trying to learn all there is to learn.
Sent from my XT1060
Swimboy46163 said:
Yeah. Thanks for the help. Just trying to learn all there is to learn.
Sent from my XT1060
Click to expand...
Click to collapse
No problem. I think you'll find this much better than using Safe strap and other workarounds. I've had an OG Droid, a Galaxy Nexus, a Droid RAZR, a Droid RAZR MAXX, a Galaxy S3, and a Note II, so I've got a little experience flashing and rooting on locked and unlocked boot loaders.
I suggest reading as much as you can, then rereading it, and ask questions until you understand. Search the forums first, but never be afraid to ask if you can't find the answer. A lot of times Google is your friend when looking for answers too.
Mr. Orange 645 said:
No problem. I think you'll find this much better than using Safe strap and other workarounds. I've had an OG Droid, a Galaxy Nexus, a Droid RAZR, a Droid RAZR MAXX, a Galaxy S3, and a Note II, so I've got a little experience flashing and rooting on locked and unlocked boot loaders.
I suggest reading as much as you can, then rereading it, and ask questions until you understand. Search the forums first, but never be afraid to ask if you can't find the answer. A lot of times Google is your friend when looking for answers too.
Click to expand...
Click to collapse
Btw does mysms have quick reply messages like chomp does? It's not very clear
Sent from my XT1060
Swimboy46163 said:
Btw does mysms have quick reply messages like chomp does? It's not very clear
Sent from my XT1060
Click to expand...
Click to collapse
Yes. Its called popup notifications in the settings and is turned on by default.
Mr. Orange 645 said:
Yes. Its called popup notifications in the settings and is turned on by default.
Click to expand...
Click to collapse
Ok seriously thanks for the mysms suggestion. I've been trying to find a replacement for Google voice forever. I hate google voice lol
Sent from my XT1060
Swimboy46163 said:
Ok seriously thanks for the mysms suggestion. I've been trying to find a replacement for Google voice forever. I hate google voice lol
Sent from my XT1060
Click to expand...
Click to collapse
No problem.