*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
AT&T Samsung Galaxy S5 Safestrap
SAFESTRAP INSTALLATION VIDEO BY @Tomsgt:
https://www.youtube.com/watch?v=5d-cPtK-CR8&feature=youtu.be
CURRENT PROJECT STATUS:
BETA v3.75 (ND3)
READ KNOWN ISSUES IN POST #2
MAKE SURE YOU CHECK REQUIREMENTS BELOW BEFORE INSTALLING
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.1.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (probably only 1 on the S5 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer.
Requirement: External SD card
Requirement: Remove (temporarily) XPosed framework while installing Safestrap
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN AT&T SAMSUNG GALAXY S5
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
[KITKAT:ND3]
LATEST BETA FILE: Safestrap-KLTEATT-ND3-3.75-B03.apk
XDA Downloads
Mirror 1 (Crackflasher)
As of version 3.75, Safestrap Recovery is now based on TWRP 2.7.1.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
For the purposes of direct user testing I've established a channel on freenode.net IRC: #safestrap
I'm in the channel mostly all the time, but may not be active for discussion.
Special Thanks To
DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
XDA:DevDB Information
Safestrap Recovery v3.75, Tool/Utility for the AT&T Samsung Galaxy S 5
Contributors
Hashcode, DeesTroy & TeamWin
Version Information
Status: Beta
Current Beta Version: 3.75 B03
Beta Release Date: 2014-06-26
Created 2014-06-25
Last Updated 2014-06-26
Reserved
DO NOT USE ROM-SLOTS YET. STILL DEBUGGING A MOUNTING ISSUE WHERE IT WIPES THE INTERNAL STORAGE.
KNOWN ISSUES:
If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*
Rebooting from a rom-slot will end up at a blank screen. Battery pull and re-power on.
Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
No Aroma installer support. This is due to the stock S5 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
Reserved
CHANGELOG
[2014-06-26]Fixed /data/media files being included in backups (making them huge)
[2014-06-26]Changed splashmenu time from 8 seconds to 4 seconds (trying to avoid "device memory" error)
[2014-06-24]initial release
Had a user test rom-slots and it showed "Device memory damaged" and then it wiped the ENTIRE internal storage.
So no go for rom-slots for now, till i figure out what happened.
Hashcode said:
Had a user test rom-slots and it showed "Device memory damaged" and then it wiped the ENTIRE internal storage.
So no go for rom-slots for now, till i figure out what happened.
Click to expand...
Click to collapse
That would be me.
Don't mind sacrificing my phone a few times before we get this figured out
Thank you!!!
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Do you think this is compatible with the ANCE build number? From what I understand, the differences are extremely small.
And a million thanks for working on this for us!
@Hashcode Confirmed work on ATT SM-G900A NCE ......U are Amazing.....:good::good:
EDIT: @chronicaust YES
chronicaust said:
Do you think this is compatible with the ANCE build number? From what I understand, the differences are extremely small.
And a million thanks for working on this for us!
Click to expand...
Click to collapse
@mcnaught82 YES
mcnaught82 said:
I'm on 2AND3. This will work?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added to [INDEX][FAQ][Q&A][ALL-IN-ONE][ATT][SM-G900A][Jun.24.2014]
Awesome thank you so much
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I'm on 2AND3. This will work?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
This is great man. Thanks for all your hard work. I hit thanks until I ran out and donated. Can't wait to start seeing roms.
ted77usa said:
@Hashcode Confirmed work on ATT SM-G900A NCE ......U are Amazing.....:good::good:
Click to expand...
Click to collapse
Woot, awesome news!
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
mcnaught82 said:
I'm on 2AND3. This will work?
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Megadoug13 said:
I'm in the same boat
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Looks like it is working on mine..
Lets take care of Hashcode fellas. This is great news !!!!! I knew he would come through !!!! Just like on the note 3.
Might be a dumb question but what Roms can you use with this setup
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
BigSexySCJCD said:
Might be a dumb question but what Roms can you use with this setup
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I might be wrong but I think the OP said we can't use roms yet. I'm assuming this is more or less just a recovery option right now. Someone correct me if I'm wrong.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
There are no ROMs for us yet. You will be able to flash roms, just not to a slot. It will be to the Stock Slot only. But you can back up your stock rom before flashing over the stock slot. Most ROMs will act better on the stock slot anyway.
1st thing I did with this recovery was wipe dalvick cache and regular cache. Phone is really acting better now. I mean a whole lot better. Thanks to Hashcode, and Geohot, we will have development here soon....
Thank you for this @Hashcode it was worth the wait..
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Cjohns8792 said:
I might be wrong but I think the OP said we can't use roms yet. I'm assuming this is more or less just a recovery option right now. Someone correct me if I'm wrong.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
LuckyColdJohnson said:
There are no ROMs for us yet. You will be able to flash roms, just not to a slot. It will be to the Stock Slot only. But you can back up your stock rom before flashing over the stock slot. Most ROMs will act better on the stock slot anyway.
1st thing I did with this recovery was wipe dalvick cache and regular cache. Phone is really acting better now. I mean a whole lot better. Thanks to Hashcode, and Geohot, we will have development here soon....
Click to expand...
Click to collapse
I'm using the Alliance Rom from the T-Mobile forum. so far running good.
Related
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
***All Credit to Hashcode***Take a minute to donate to Hashcode if you like his work: http://forum.xda-developers.com/member.php?u=4243514
Posted by Hashcode on Page 9:
Updated Safestrap for RAZR-HD/Atrix-HD to v3.12:
Download the APK Installer Here for "RAZR-HD/ATRIX-HD"
md5sum: 9b3d75e84c06d1e71af1bf1bad57faf3
FOLLOW THESE INSTRUCTIONS: How to Safestrap
CHANGES:
[01/04] (3.12) Fix initial file selector location for backup/restore
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions. * STILL TESTING -- BUGGY*
[12/29] (3.10) Enable flashing to stock ROM
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
SPECIAL THANKS TO:
- The entire TWRP team who has built an AMAZING recovery system.
- The testers (BigDX) which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always let Hashcode know what you think!!!
For users running jellybean leak only
INSTRUCTIONS for getting STOCK running on a rom-slot:
[ EDIT: 11/15, Removed fix-rom-slot.zip from instructions. It's no longer needed and screws up paid apps. ]
STEPS:
1. Install Safestrap 3 from the above notes
2. Reboot into recovery
3. Make a backup of your stock rom slot
4. Go into "Boot Options" and create a new rom-slot (if you haven't) -- 1GB data is probably good enough for most users
5. Once that is created it may say "rom slot: off" at the top, make sure to go back into the new rom-slot and use "Activate" button
6. Now use the "Restore" button on the main menu to restore the backup you made of stock to the new rom-slot
7. When that's done restoring, use "Wipe" -> "Factory Reset" and then "Dalvik Cache" from the main menu
8. At this point you should have a full working copy of the stock MotoBlur ROM on a rom-slot which you can flash and modify w/o fear of bricking.
9. Reboot and enjoy
IF USERS on STOCK ICS want a method for getting that onto a rom-slot as well, let Hashcode know.
When I open up the apk it closes and says unfortunately safe strap has stopped working
Sent from my Galaxy Nexus using xda premium
Your signature says GNex... hoping you have a HD too? Also have you allowed installation from unknown sources and did you check the md5 sum of the download??? I haven't personally tried this yet but if you look and respond here http://www.droidrzr.com/index.php/t...-v30-11072012-v305x-all-versions/page__st__20 you can see that others have gotten it installed fine...
GoClifGo05 said:
Your signature says GNex... hoping you have a HD too? Also have you allowed installation from unknown sources and did you check the md5 sum of the download??? I haven't personally tried this yet but if you look and respond here http://www.droidrzr.com/index.php/t...-v30-11072012-v305x-all-versions/page__st__20 you can see that others have gotten it installed fine...
Click to expand...
Click to collapse
yeah with the new 4.2 camera everything thinks it's a gnex. any way be sure that you have updated your binary's or you'll look like a dumb ass like me. but all is well now had to flash back to the stock backup it wouldn't allow me to download paid apps it said no room on internal or sd card
The paid apps thing seems to be a common issue people are having... awaiting Hashcodes response to it.
Sent via Xparent Cyan Tapatalk 2
Niiiiceeee: Root, Recovery, and next ROMS :victory:
Ok, response from Hashcode over on the original thread: "If you have ANY problems using this what-so-ever feel free to swap back to Stock while I work out the details. I don't have a RAZR-HD to test on so I'm sort of shooting from the hip"
That was the easiest thing ever... Running ICS.
I have a few things I'm going to try for the paid app fix.
Feel free to monitor the other thread or follow me on twitter for updates:
@hashcode0f
Sent from my XT894 using Tapatalk 2
Hi,
really good thank you !
Is it usefull for unlocked bootloader or not at all ? (functionnality or something else ?)
Would be nice if there will be some custom roms for the RHD to try this here out ^^
Sent from Wemsi's Rasperry PI
wemsinho said:
Would be nice if there will be some custom roms for the RHD to try this here out ^^
Sent from Wemsi's Rasperry PI
Click to expand...
Click to collapse
There's 1 posted at rootzwiki that will be updated tonight for SS.
koftheworld said:
There's 1 posted at rootzwiki that will be updated tonight for SS.
Click to expand...
Click to collapse
Yeah, i know. But its only for the Verizon versions. Ive got an european GSM model.
Sent from Wemsi's Rasperry PI
OP updated with newer version. Thanks Hashcode.
Cant wait to see CM10 on this. Its gonna be awesome.
Sent from my SCH-I535 using xda premium
wemsinho said:
Yeah, i know. But its only for the Verizon versions. Ive got an european GSM model.
Sent from Wemsi's Rasperry PI
Click to expand...
Click to collapse
GSM model is international version whereas Verizon model is just Verizon version...
Will Cyanogenmod support gsm Razr HD or not ?
koftheworld said:
There's 1 posted at rootzwiki that will be updated tonight for SS.
Click to expand...
Click to collapse
Do you have the link?
Don't worry about my device I have the M, HD, and HD maxx
Sent from my XT907 using Tapatalk 2
Link
http://rootzwiki.com/topic/36022-rom-vitreous-10-11082012-jelly-bean-41-42/
Will this work on the Maxx HD?
Safestrap Talk
Basically, we can use this thread for any info/help regarding Safestrap and keep Hashcodes thread clean for him and testers that know what their talking about
Thanks HASHCODE for your hard work !!!!!!!!
I'm running X Note 6 on the At&t Galaxy Note 3 100% flawless.
Special Thanks to》 Hashcode for Safestrap >http://forum.xda-developers.com/showthread.php?t=2572978
drakeymcmb >1st Flash method we had> http://forum.xda-developers.com/showthread.php?t=2554411
evilpotatoman >For Restore and going out of his way to help >http://forum.xda-developers.com/showthread.php?t=2559715
Raiderman >For his tech help/themes>http://forum.xda-developers.com/showthread.php?t=2534671
bri315317 >For his help and script thread>http://forum.xda-developers.com/showthread.php?t=2574137
Without y'all, I would of sold this phone.
KNOWN ISSUES:
No Aroma installer support. This is due to the stock Note 3 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you're stock ROM is modified then the "Reboot Recovery" function from inside Safestrap APK may / may not work.
Right now flashing / booting ROMs on rom-slots is broken. I'm debugging best I can.
EXFAT support seems broken right now (64gb SD cards)
Here is how we are using it now, but please read and follow instructions.
>bri315317 >http://forum.xda-developers.com/showthread.php?t=2574137
We are not responsible for your phone messing up. If your scared then go to church.
J/K > We have a restore thread if you make a mistake by > evilpotatoman >For Restore>http://forum.xda-developers.com/showthread.php?t=2559715
Did you activate that rom slot once you installed a rom to it or was the stock slot still active?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
P1Tater said:
Did you activate that rom slot once you installed a rom to it or was the stock slot still active?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It was active but I just rebooted after flashing. I did not click on activate again. Should I do that after flashing and wiping the C/D ?
Worth a shot in my opinion
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I installed SS made a back up. That worked great. Tried to install galaxymans theme SS showed failed. What am I doing wrong?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
P1Tater said:
Worth a shot in my opinion
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I downloaded the theme again and booted into recovery. Selected the Stock Slot (already checked).
I installed the theme and went to select the slot again but its already selected so I just wiped cache and dalvik cache.
Rebooted phone and nothing. Same stock look.
I wonder if it would work without wiping?
c-mack said:
I installed SS made a back up. That worked great. Tried to install galaxymans theme SS showed failed. What am I doing wrong?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Mine doesn't say failed. It installs but no theme when rebooting. ABout to try again
Have you tried just powering off after its installed and then just boot the phone up manually?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Nope. Reading some info from the Themes thread now
Sent from my SAMSUNG-SM-N900A using Tapatalk
So I have never posted here I just lurk. But I wanted to post this info up and as I get more info and testing done I'll update. Going to try and flash a couple roms this evening but here is where I am so far. If someone could post this in the dev thread that would be awesome. Post 1 for me.
CURRENT TESTS:
TEST #1: Hijack stability to enter recovery on every boot. RESULT: untested.
TEST #2: Reboot to recovery functionality RESULT: pass every time, either through safe strap app or manually.
TEST #3: Recovery removal leaves device in clean state RESULT: pass. Uninstalled recovery after 2 reboots into safe strap and worked fine.
TEST #4: ADB access from recovery RESULT: untested.
TEST #5: ROM-slot creation RESULT: pass. created 3 with default values. No issues.
TEST #6: Backup stock ROM RESULT: pass. Done in 167 seconds for roughly 3300mbs.
TEST #7: Restore stock ROM backup to stock slot: pass. No issues
TEST #8: Initial 2nd-init ROM installation on rom-slot RESULT: untested
TEST #9: Custom ROM flash on rom-slot RESULT: untested
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Still no luck for me tried a few times. Not that it matters but I've tried starting SS from both touch wiz and nova launcher. SS says failed both times.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
hey
akdrift said:
So I have never posted here I just lurk. But I wanted to post this info up and as I get more info and testing done I'll update. Going to try and flash a couple roms this evening but here is where I am so far. If someone could post this in the dev thread that would be awesome. Post 1 for me.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I posted it in there for you sir....
c-mack said:
Still no luck for me tried a few times. Not that it matters but I've tried starting SS from both touch wiz and nova launcher. SS says failed both times.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
You have to turn the phone off or just regular reboot and then the option will pop up to boot in recovery. This will happen if you clicked "install recovery" inside the SS apk.
Sent from my SAMSUNG-SM-N900A
dirtydroidx said:
You have to turn the phone off or just regular reboot and then the option will pop up to boot in recovery. This will happen if you clicked "install recovery" inside the SS apk.
Sent from my SAMSUNG-SM-N900A
Click to expand...
Click to collapse
>> C MACK
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
I installed SS as soon as it went up and everything has gone smoothly. It's worth mentioning that I used the original De La Vega root and never updated because I had zero problems afterwards. I never tried any of the dirty workarounds to flashing roms. I rebooted into recovery from the app (flawlessly) and made a backup. Then decided to g3t ballsy and install galaxyman's theme while wiping caches. It only appeared to partially work. Then I remembered that I had partially themed my phone using Wanam/X-Blast. I turned those off and viola! My phone looks ultraslick.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 12:39 PM ---------- Previous post was at 12:37 PM ----------
My only question now is:
Can we flash T-Mobile roms and swap modems or are there other important differences? I'd really like to just hijack their dev section.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Also SS is meant to be a failsafe recovery, meaning your active slot should be your current setup. You should not flash anything to your stock rom slot unless your comfortable. If you want to flash a rom like Encore that's in the development section , create a new rom slot and flash to it; Then if **** hits the fan you always have your stock rom to switch back to.
Sent from my SAMSUNG-SM-N900A
Boraltis said:
I installed SS as soon as it went up and everything has gone smoothly. It's worth mentioning that I used the original De La Vega root and never updated because I had zero problems afterwards. I never tried any of the dirty workarounds to flashing roms. I rebooted into recovery from the app (flawlessly) and made a backup. Then decided to g3t ballsy and install galaxyman's theme while wiping caches. It only appeared to partially work. Then I remembered that I had partially themed my phone using Wanam/X-Blast. I turned those off and viola! My phone looks ultraslick.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 12:39 PM ---------- Previous post was at 12:37 PM ----------
My only question now is:
Can we flash T-Mobile roms and swap modems or are there other important differences? I'd really like to just hijack their dev section.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I started with Mj5....Did the install ROM without recovery a couple of times.
Did the restore Mj5 Thread a bunch.
Before I installed Safestrap, I restored back to stock rooted and installed SS.
Can't flash themes yet.
Maybe I should start all over again but this time restore twice and go to system settings/back up factory reset.
The last time i did the factory reset option after a restore, the phone was perfect.
Maybe I will just do that and start over...Will report back.
Hey guys, I've held off from any exploits thus far including root. However, I am now interested in using safestrap. I am on MJ5, is my only option for root kingo?
Sent from my SAMSUNG-SM-N900A using Tapatalk
theROMinator said:
Hey guys, I've held off from any exploits thus far including root. However, I am now interested in using safestrap. I am on MJ5, is my only option for root kingo?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
I wonder if you can try this. It worked for me but only after I got into a bootloop
http://forum.xda-developers.com/showthread.php?t=2559715
At the end of all steps, the last step is an easy "put files here" and it rooted. (after a reboot twice)
Just follow instructions
When I reboot and the safestrap screen comes up where I can choose to enter recovery or enter regular system. In red it says safestrap disabled. Is this typical?
I know safestrap is installed and running as I created a backup did a factory reset then then did a back up from the recovery I created.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Introduction
This kit is designed to update Stock rooted Nexus 5 devices to Android 4.4.4 while retaining all user data as well as root permissions. This will also work on non-rooted devices with an unlocked Bootloader.
Before you Start
# This kit is designed to update without wipe but anything is possible, so I strongly urge you
to back up all data. Also I am not liable for any lost information.
# Please configure all ADB drivers
# Place phone in Fastboot mode. Power down the device; (Press and hold Power + Volume Down)
until the device boots into Fastboot.
# Extract all files, open the Unfathomable EXE file in the provided folder and follow the prompts Carefully.
Instructions
Run the EXE. After your device reboots, boot your Nexus into recovery. TWRP recovery should boot. Select the reboot option and reboot system.
You will be prompted "Swipe to flash SuperSU". This will restore all Root permissions.
*Also in the event that your device is stuck in a bootloop, just wipe the cache and you should be good to go!
Downloads
Nexus 5 Auto Updater 4.4.4 by Unfathomable.zip
The Kit can also be downloaded at this Dev Host URL
http://d-h.st/mRY
[Nexus 5 Auto Updater 4.4.4 By Unfathomable.zip - 451.78 MB]
Other Information
The Nexus 7 Wi-Fi Auto-Updater 4.4.4 can be found at this URL
http://forum.xda-developers.com/showthread.php?t=2791773
XDA:DevDB Information
Nexus 5 Auto-Updater, Tool/Utility for the Google Nexus 5
Contributors
Unfathomable
Version Information
Status: Beta
Created 2014-06-29
Last Updated 2014-06-29
Got to be one of the slowest downloads for such a small file in the history of man.
Painful to say the least.
For me, almost half a gig is something other than small.
TiltedAz said:
For me, almost half a gig is something other than small.
Click to expand...
Click to collapse
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
@home said:
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And you're complaining in the OP's thread, why? Blame Dev-Host not them. Lol.
Not complaining, just stating a fact.
Sent from my SM-G900F using XDA Premium 4 mobile app
With all do respect to opinions I would greatly appreciate if this thread is used for and remains a hub for questions and support. With that being said I have taken the liberty of uploading the file into XDA's server for downloading. Please respect my wishes as I have taken my own personal time to provide the community with this tool and many more to come. Thank you all! If you have any concerns, feedback or need support please feel free to contact me at [email protected].
Sent from my Nexus 5 using XDA Premium 4 mobile app
Thanks for do us a easy way to update to v4.4.4 with stock rom! :good:
Just want to thank the op for making it so easy
It's a good idea but a little long winded when you can just flash a rooted stock ROM.zip via recovery.
Sent from my Nexus 5 using Tapatalk
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
miserableboy said:
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
Click to expand...
Click to collapse
Yes, it is not a requirement to be running 4.4.3. Let me know if you have any difficulties.
Out of Memory
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
ddukatz said:
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
Click to expand...
Click to collapse
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same thing here. Already wiped cache but no memory message appears.
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Click to expand...
Click to collapse
Not sure which one but one of these things fixed it for me.
Thanks!
ddukatz said:
Not sure which one but one of these things fixed it for me.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing the issue to my attention, and no problem I'm glad I was able to help.
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
PsychDrummer said:
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
Click to expand...
Click to collapse
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
rootSU said:
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh ok. That would make sense why the file is so big. So then, isn't this basically deleting the -w from the batch file and flashing normally? Well and retaining root.