• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[THOR/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]

Search This thread

W99DEY

Senior Member
Jun 21, 2009
249
55
Not sure if this is the right thread... but here goes.....
So, I have installed13.3.2.3.2, rooted and disabled updates. I have installed safestrap 3.75 and installed Gapps over the restored original on Slot 1 with the play store that worked for a day.....
I know that I need to either unlock the boot loader or go for safestrap 4.1.
I have a couple of questions, I have looked through all the forum posts but can’t definitively find the answers....
For the full unlocking of the bootloader do you need to uses a Linux PC? Seems to be the case....
I have 13.3.2.3.2 on slot 0 and also on slot 1 with the so so Gapps. Can I update the slot 1 rom to 4.5.1 then install safestrap 4.01 and still keep my 13.3.2.3.2 on slot 0, or do I need to uninstall safestrap 3.75 upgrade the main slot to 4.5.1 then install 4.01 safestrap? Will the root remain or will I need to reroot then disable updates? If so, is there a root for 4.5.1?
Presumably if I get root for 4.5.1 then add safestrap 4.01 I can then flash the later Roms such as the Nexus one, with the working gapps packages....
I presume if I go down this route, i will never be able to unlock the bootloader, which I suppose is the riskier preferred option.
Any help answering the above will be greatly appreciated..... :)
 
Last edited:

DB126

Senior Member
Oct 15, 2013
15,263
10,042
Not sure if this is the right thread... but here goes.....
So, I have installed13.3.2.3.2, rooted and disabled updates. I have installed safestrap 3.75 and installed Gapps over the restored original on Slot 1 with the play store that worked for a day.....
I know that I need to either unlock the boot loader or go for safestrap 4.1.
I have a couple of questions, I have looked through all the forum posts but can’t definitively find the answers....
For the full unlocking of the bootloader do you need to uses a Linux PC? Seems to be the case....
I have 13.3.2.3.2 on slot 0 and also on slot 1 with the so so Gapps. Can I update the slot 1 rom to 4.5.1 then install safestrap 4.01 and still keep my 13.3.2.3.2 on slot 0, or do I need to uninstall safestrap 3.75 upgrade the main slot to 4.5.1 then install 4.01 safestrap? Will the root remain or will I need to reroot then disable updates? If so, is there a root for 4.5.1?
Presumably if I get root for 4.5.1 then add safestrap 4.01 I can then flash the later Roms such as the Nexus one, with the working gapps packages....
I presume if I go down this route, i will never be able to unlock the bootloader, which I suppose is the riskier preferred option.
Any help answering the above will be greatly appreciated..... :)
You researched options well! Brief responses:
- Bootloader unlock can be done from Windows which the platform most have used. Windows adb/fastboot drivers can be finicky but most get them to work. Just need to be persistent.
- Safestrap v3 and v4 can not coexist (sorry); a recovery embedded within a recovery would likely yield a cluster that you don't want to experience.
- Root is lost if you upgrade to FireOS v4. Versions up to 4.5.2 can be rooted. After rooting you need to block OTA to prevent further upgrades which will break root and likely wreak havoc with Safestrap v4
- At present you can run the following roms using Safestrap v4: Nexus v4, CM11 and FireOS v4

Your best course of action IMO is to uninstall Safestrap v3, install (flash) twrp and then unlock your bootloader which will open the door to all roms available for the HDX (Nexus, CM11, CM12 and FireOS). You can flash Nexus v2 and an earlier build of CM11 with a locked bootloader. Nexus v2 in particular is a very nice rom albeit a bit dated. Point is you can be using Nexus v2 while working on unlocking your bootloader. v2 and v4 are very similar (former is Jelly Bean based; latter is KitKat).

To remove Safestrap v3 delete all secondary slots from within Safestrap recovery and verify your device can still boot to the 'stock' slot. Then uninstall Safestrap recovery using the original 3.7.5 apk.
 

W99DEY

Senior Member
Jun 21, 2009
249
55
You researched options well! Brief responses:
- Bootloader unlock can be done from Windows which the platform most have used. Windows adb/fastboot drivers can be finicky but most get them to work. Just need to be persistent.
- Safestrap v3 and v4 can not coexist (sorry); a recovery embedded within a recovery would likely yield a cluster that you don't want to experience.
- Root is lost if you upgrade to FireOS v4. Versions up to 4.5.2 can be rooted. After rooting you need to block OTA to prevent further upgrades which will break root and likely wreak havoc with Safestrap v4
- At present you can run the following roms using Safestrap v4: Nexus v4, CM11 and FireOS v4

Your best course of action IMO is to uninstall Safestrap v3, install (flash) twrp and then unlock your bootloader which will open the door to all roms available for the HDX (Nexus, CM11, CM12 and FireOS). You can flash Nexus v2 and an earlier build of CM11 with a locked bootloader. Nexus v2 in particular is a very nice rom albeit a bit dated. Point is you can be using Nexus v2 while working on unlocking your bootloader. v2 and v4 are very similar (former is Jelly Bean based; latter is KitKat).

To remove Safestrap v3 delete all secondary slots from within Safestrap recovery and verify your device can still boot to the 'stock' slot. Then uninstall Safestrap recovery using the original 3.7.5 apk.
Thanks for that confirmation.... Is there a thread here to unlock 4.5.1? I was under the impression that I I updated to 4.5.1 the bootloader couldn't be unlocked....

Sent from my A0001 using Tapatalk
 

Cl4ncy

Senior Member
Jul 9, 2015
367
198
Thanks for that confirmation.... Is there a thread here to unlock 4.5.1? I was under the impression that I I updated to 4.5.1 the bootloader couldn't be unlocked....

Sent from my A0001 using Tapatalk
You can NOT unlock the bootloader of 4.5.x!
You can root up to 4.5.2 atm.
If you're on 3.2.3.2 I'd suggest you unlock the bootloader, and use TWRP.
To install TWRP you should remove the secondary slots in Safestrap, (do NOT delete the stock slot, do NOT wipe System!), then remove Safestrap and install TWRP.
If in doubt ask first, before you brick your HDX. ;)
 

DB126

Senior Member
Oct 15, 2013
15,263
10,042
Thanks for that confirmation.... Is there a thread here to unlock 4.5.1? I was under the impression that I I updated to 4.5.1 the bootloader couldn't be unlocked....

Sent from my A0001 using Tapatalk

Agree with @Cl4ncy on all points. Once unlocked the bootloader remains unlocked provided you do not flash a stock image from Amazon. There are methods for running FireOS while remaining unlocked but most people prefer one of the other roms. If you are unsure it's quite easy to sample Nexus with your current Safestrap v3 config. You can stick with that and/or unlock later for access to one of the newer roms. The older version of Nexus (Jelly Bean based) is quite nice and gives you full access to Google Play including past purchases. A low risk/effort option. :)
 

W99DEY

Senior Member
Jun 21, 2009
249
55
Just one last thing.... If I back up my 3.3.2.3 in safestrap 3.75...... then upgrade to 4.5.2 then install safestrap 4.01.... to try it with the Nexus ROM, can I restore the original 3.2.3.2 back to slot 0 using 4.01?

The reason for asking this, is if I restore that, then hopefully I can unlock the bootloader further down the line..... as I will be using 3.2.3.2 as a base to unlock the bootloader.... Cheers....
 

Cl4ncy

Senior Member
Jul 9, 2015
367
198
Just one last thing.... If I back up my 3.3.2.3 in safestrap 3.75...... then upgrade to 4.5.2 then install safestrap 4.01.... to try it with the Nexus ROM, can I restore the original 3.2.3.2 back to slot 0 using 4.01?

The reason for asking this, is if I restore that, then hopefully I can unlock the bootloader further down the line..... as I will be using 3.2.3.2 as a base to unlock the bootloader.... Cheers....
Once you update to 4.5.2 you can NOT unlock your bootloader anymore. Because you can NOT unlock the 4.5.2 bootloader, and you can NOT downgrade to 3.2.3.2 anymore either.
And what's the point of unlocking in the future, if you can unlock it now? Especially if you currently are on 3.2.3.2.
 
Last edited:
  • Like
Reactions: DB126

DB126

Senior Member
Oct 15, 2013
15,263
10,042
Just one last thing.... If I back up my 3.3.2.3 in safestrap 3.75...... then upgrade to 4.5.2 then install safestrap 4.01.... to try it with the Nexus ROM, can I restore the original 3.2.3.2 back to slot 0 using 4.01?

The reason for asking this, is if I restore that, then hopefully I can unlock the bootloader further down the line..... as I will be using 3.2.3.2 as a base to unlock the bootloader.... Cheers....
Good of you to ask; @Cl4ncy has already responded. Many try first and whine later. If you want to taste Nexus just create a slot and install the prior version as previously suggested; see parts 3 & 4 in this guide. Low effort, low risk and very representative of the overall Nexus experience. Gentle suggestion: stop trying to overthink the process or propose clever workarounds. The available paths have been outlined in earlier posts. Choose an option (hopefully not of your own design) and go forward.
 

Cl4ncy

Senior Member
Jul 9, 2015
367
198
I have decided to go for 4.5.2 and safestrap 4.01..... cant for the life of me find how to root the 4.5.2 version.... :s
Well, too bad j/k ;)
4.5.2 must be rooted with Kingroot, I've no experience with it, so you've to research yourself a bit about it. Disable OTA ASAP, you don't want to be updated to 4.5.4.
 

DB126

Senior Member
Oct 15, 2013
15,263
10,042
I have decided to go for 4.5.2 and safestrap 4.01..... cant for the life of me find how to root the 4.5.2 version.... :s
Your choice; you seem to understand the bootloader unlock implications. Curious - did you even try Nexus on Savestrap v3? Why go through the trouble of upgrading/rooting/freezing OTA/configuring safestrap/flashing Nexus/etc (and possibly bricking if you overshoot 4.5.2 and have to roll back) if you are not sure it will meet your needs? If you can't "for the life of me" figure out how to root 4.5.2 then you should seriously consider if you are prepared for the journey. A simple search of the HDX forums yields dozens of posts on that topic.
 

Cl4ncy

Senior Member
Jul 9, 2015
367
198
Your choice; you seem to understand the bootloader unlock implications. Curious - did you even try Nexus on Savestrap v3? Why go through the trouble of upgrading/rooting/freezing OTA/configuring safestrap/flashing Nexus/etc (and possibly bricking if you overshoot 4.5.2 and have to roll back) if you are not sure it will meet your needs? If you can't "for the life of me" figure out how to root 4.5.2 then you should seriously consider if you are prepared for the journey. A simple search of the HDX forums yields dozens of posts on that topic.
I don't get this either. Why even think about updating to 4.5.2, if you are on 3.2.3.2 and just have to unlock the bootloader, remove Safestrap & install TWRP to be in the wonderland of HDX ROMs? Why remove possibilities you have with 3.2.3.2, unlocked bootloader & TWRP to be limited with 4.5.2, a locked bootloader & Safestrap, not to mention all the risks which come along by updating and rooting.
Well, have it your way W99DEY - but don't say we didn't say we told you so after you realized updating to 4.5.2 was a bad idea. ;)
 
Last edited:
  • Like
Reactions: EncryptedCurse

uramisten

Member
Jan 13, 2010
21
2
Hi,
I received a hdx7 running cm11 under safestrap. Is there any way of finding out what version of fireos will run on it (i.e. what the firmware is)? I'd love to be able to fully unlock it and run cm13 as I did on the other device I got on ebay? If it has a compatible firmware version, is it feasible to remove safestrap, unlock, etc..?
Thanks
 

DB126

Senior Member
Oct 15, 2013
15,263
10,042
Hi,
I received a hdx7 running cm11 under safestrap. Is there any way of finding out what version of fireos will run on it (i.e. what the firmware is)? I'd love to be able to fully unlock it and run cm13 as I did on the other device I got on ebay? If it has a compatible firmware version, is it feasible to remove safestrap, unlock, etc..?
Thanks
With that configuration the underlying version of FireOS prior to the installation of CM11 was almost certainly 4.5.2 which can not be unlocked. The bootloader version is what really counts. Unfortunately there is no way to query it directly. The quickest test is to attempt an unlock via this tool. There is no risk to the device; only your time to set-up and execute. It will either work or not...simple as that.
 

Cl4ncy

Senior Member
Jul 9, 2015
367
198
Hi,
I received a hdx7 running cm11 under safestrap. Is there any way of finding out what version of fireos will run on it (i.e. what the firmware is)? I'd love to be able to fully unlock it and run cm13 as I did on the other device I got on ebay? If it has a compatible firmware version, is it feasible to remove safestrap, unlock, etc..?
Thanks
Which Safestrap version is installed on the device? v3.72, v3.75 or v4?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 64
    ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
    https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b


    *** 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.


    PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
    MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
    THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
    ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!



    WARNING: 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.


    UNKNOWN ISSUE: If you try and start Wifi and the device crashes/reboots, try turning on bluetooth prior to enabling wifi and see if that works.



    CURRENT PROJECT STATUS:
    BETA-STABLE


    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.x.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:
    1. Here you can create virtual ROM-slots 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.
    2. 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.
    3. 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.
    4. For more information you can read up here:
      http://blog.hash-of-codes.com/how-to-safestrap/

    HOW DO I INSTALL SAFESTRAP?
    1. Requirement: Rooted w/ SuperSU installed
    2. Requirement: Allow APK install from Unknown Sources
    3. Download the Safestrap APK
    4. Find the APK using a Filemanager tool and open it on your device, then click "Install".
    5. (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.)
    6. Once installed, open up the Safestrap application as you would any other app.
    7. 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..
    8. 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.
    9. 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.
    10. 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.

    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
    • Open an "explorer" of some sort (ESFileExplorer, etc)
    • 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 YOUR STOCK OS VERSION BELOW AND THAT YOU ARE USING THE KINDLE FIRE HDX 7" (THOR)
    [13.3.2.1 and earlier] LATEST FILE: Safestrap-Thor-3.72.apk
    [13.3.2.3.2 and later] LATEST FILE: Safestrap-Thor-3.75-os3.2.4-B02.apk
    Mirror 1: Crackflasher Download
    Mirror 2: Goo.im Download

    Here's an amazon-os .zip that can be used on rom-slots for re-flashing the OS -- MUST MATCH STOCK ROM:

    THOR ONLY (HDX 7") 13.3.1.0: Download from goo.im
    md5sum: 24fee10d8c6b0dbf583465baa938e842

    It's the straight Amazon OS:
    • not DeOdexed
    • will not stop OTAs
    • is not rooted
    • the only changes I made, were to strip out the boot.img or modem.img flashing stuff.

    To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:
    http://download.chainfire.eu/supersu



    As of version 3.x, Safestrap Recovery is now based on TWRP. 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
    16
    For those that missed it in the 1st post:

    PLEASE PLEASE BE VERY CAREFUL WITH SAFESTRAP!!
    MAKE A BACKUP OF STOCK RIGHT AFTER YOU GET SAFESTRAP INSTALLED SO THAT YOU HAVE SOME KIND OF DISASTER RECOVERY.
    THEN YOU CAN RESTORE IT TO A ROM-SLOT (AFTER YOU MAKE ONE).
    ONLY MODIFY ROM-SLOT FILES. LEAVE YOUR STOCK ROM ALONE!!



    KNOWN ISSUES WHEN USING ROM-SLOTS (The ROMs are kept on loop device mounted partitions)
    1. In theory you will lose an extra 3-4 percent battery compared to normal usage from 100% to 0% due to the extra read/write work involved when using ROM-slots.
    2. The /data partition is kept separate from the "/sdcard" contents on SS ROMs. This causes the Storage settings to only show the size of the loopback data partition and then it shows "used" which includes the "sdcard" + /data so this can look odd at times (larger usage than partition size). It doesn't have any adverse affects that I know of.
    3. No custom kernel flashing support at this time. Don't try it. It won't work. All kernels need to be signed by Amazon at the moment.

    CHANGELOG:
    • [v3.75-B02]Bugfix rom-slot booting
    • [v3.75-B01]TWRP 2.7.1.0 update + display fix for 13.3.2.3.2/13.3.2.4
    • [v3.72]TWRP 2.7.0.0 update. *** This includes a bugfix for backup time showing correctly ***
    • [v3.72]Raised /data partition size to 16gb
    • [v3.72]Swapped "Reboot" -> "Download" mode to "Reboot" -> "Bootloader" (places you in fastboot mode)
    • [v3.70-B01]Seems like I have a solid fix for the "snow" effect when getting into Safestrap sometimes
    • [v3.70-B01]System partition now matches stock EXACTLY. You can't even change it in the settings due to the way I'm creating it during rom-slot creation. It's not a bug, that's on purpose. That being said, there should be plenty of room in that space to do what we want.
    • [v3.70-B01]Battery % now being displayed correctly in recovery
    • [v3.70-B01]Updated to latest Safestrap sources
    • [v3.65-B01]Initial release for Thor (Kindle HDX 7")
    9
    I just saw the posts regarding the new update woes.

    I may need a day or 2 to debug the update... I'm always nervous when patching Amazon's stuff.

    I also need to d/l the new sources as well.

    Sent from my SM-N900V using Tapatalk
    8
    Safestrap update for those on 13.3.2.3.2/13.3.2.4 ONLY

    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
    • Open an "explorer" of some sort (ESFileExplorer, etc)
    • 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

    CHANGELOG:
    • [v3.75]TWRP 2.7.1.0 update + display fix for 13.3.2.3.2/13.3.2.4

    DOWNLOADS:
    CONFIRM YOUR STOCK OS VERSION BELOW AND THAT YOU ARE USING THE KINDLE FIRE HDX 7" (THOR)
    [13.3.2.3.2 and later] LATEST FILE: Safestrap-Thor-3.75-os3.2.4-B01.apk
    Mirror 1: Crackflasher Download
    Mirror 2: Goo.im Download (May not be showing up here yet)

    Enjoy
    7
    Updated the OP for a new v3.70 build for the Kindle Fire HDX 7" (ONLY!)

    DOWNLOADS:
    CONFIRM THAT YOU ARE USING THE KINDLE FIRE HDX 7" (THOR) DEVICE (8.9" NOT SUPPORTED ATM)
    LATEST FILE: Safestrap-Thor-3.70-B01.apk
    Mirror 1 (Goo.im) http://goo.im/devs/Hashcode/thor/safestrap

    [ NOTE: RECREATE ALL ROM-SLOTS FOR v3.70, SIZE INCREASED / PROCESS CHANGED ]


    CHANGELOG:
    • [v3.70-B01]Seems like I have a solid fix for the "snow" effect when getting into Safestrap sometimes
    • [v3.70-B01]System partition now matches stock EXACTLY. You can't even change it in the settings due to the way I'm creating it during rom-slot creation. It's not a bug, that's on purpose. That being said, there should be plenty of room in that space to do what we want.
    • [v3.70-B01]Battery % now being displayed correctly in recovery
    • [v3.70-B01]Updated to latest Safestrap sources


    Here's an amazon-os-13.3.1.0 .zip that can be used on rom-slots for re-flashing the OS:
    Download from goo.im
    md5sum: 24fee10d8c6b0dbf583465baa938e842

    It's the straight Amazon OS:
    • not DeOdexed
    • will not stop OTAs
    • is not rooted
    • the only changes I made, were to strip out the boot.img or modem.img flashing stuff.

    To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:
    http://download.chainfire.eu/supersu

    I'm guessing devs can grab that .zip and modify it till their hearts content.