[THOR] Successfully rolled back to 13.3.1.0 (Safestrap working)

Search This thread

058515471

Member
Jan 12, 2012
48
57
Just let you guys know. I have Safestrap back to work :)

This is instructions to roll back to 13/14.3.1.0 from earlier version than 1x.3.2.5

Download below file and tool:

HDX ToolKit:
http://xdaforums.com/showthread.php?t=2665683

Roms:
13.3.1.0 (Kindle HDX 7"): https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin
or
14.3.1.0 (Kindle HDX 8.9"): https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin

Build prop editor:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor


PLEASE READ INSTRUCTION CAREFULLY

INSTRUCTION:

1. Root your Kindle by HDX ToolKit
Instruction at: http://xdaforums.com/showthread.php?t=2665683
1.1 Do not turn off Auto Update, just turn off and forget wifi to prevent auto update
1.2 If you have safestrap installed, remove it.


2. Change Version and Build Number to lower values than 13/14.3.1.0 and 310079820
2.1 Use Build prop editor
2.2 Change those lines:
ro.build.version.incremental : "13.3.0.9_user_300079820"
ro.build.version.number : "300079820"
ro.build.description : "thor-user 4.2.2 JDQ39 13.3.0.9_user_300079820 release-keys"
ro.build.fingerprint : "Amazon/thor/thor:4.2.2/JDQ39/13.3.0.9_user_300079820:user/release-keys"
(same for apollo but use: 14.3.0.9 and keep apollo name in description and fingerprint - only change build number and version)

3. Reboot the Kindle and go to Device > System Updates to check if Version and Build Number changed


4. Do manually update to 13/14.3.1.0
- Connect Kindle to PC by usb cable
- Copy rom file (.bin) from PC into Internal storage
- Go to Device > System Updates and Press Update


5. Root and install Safestrap HDX ToolKit.
Instruction at: http://xdaforums.com/showthread.php?t=2665683


6. Press Thanks

FOR 1x.3.2.5 and 1x.3.2.6
USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
How to use it.
1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
2. If Disable OTA update , Airplane mode ON and Enable OTA update
3. If Install SafeStrap, uninstall safestrap on App.

4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
5. execute install.bat
6. reboot
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
8. Downgrade, wait a minute on the update menu, because display update button to take time.
9. disable OTA update.

This batch file works "kindle fire hdx 7" ONLY
This is tested on version 13.3.2.5 and 13.3.2.6.
http://d-h.st/MAs



This batch file works "kindle fire hdx 8.9" ONLY
sorry I do not have kindle fire hdx 8.9. I cannot test.

10/3/14 update build.prop
http://d-h.st/Tz8

Thank @Poesini
Very good that the rollback of Apollo is working .
 
Last edited:

jimyv

Senior Member
Jan 31, 2012
591
189
central Indiana
umm

Just let you guys know. I have Safetrap back to work :)

Instructions:
1. use Vroot to root : http://xdaforums.com/showthread.php?t=2781665
2. chage current version and build number in build.prop to lower values:
ex: i change to: 13.3.0.9_user_300079820 (replace all cases in your file)
3. restart the kindle and go to Device > System Updates to check if it changed.
4. Factory reset the kindle
5. Do manually update the 13.3.1.0
(https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin, copy to internal storage and go to System Updates > Update)
After updated, VROOT will gone, no more Chinese App worring.
6. Root and install Safetrap: http://xdaforums.com/showthread.php?t=2665683

:)
okay well I haven't seen any of the senior guys verify the root to be safe much less being able to roll back by simple mod. that has been attempted before. I am waiting for verification. I get the feeling somebody is going to be able to call the BS but hey 1 can always hope.

---------- Post added at 05:50 PM ---------- Previous post was at 05:40 PM ----------

okay well I haven't seen any of the senior guys verify the root to be safe much less being able to roll back by simple mod. that has been attempted before. I am waiting for verification. I get the feeling somebody is going to be able to call the BS but hey 1 can always hope.

I have a blacklisted 13.3.2.2_user_322095220 im willing to test with but so far I havent even been able to find right tool with info provided iv tried a couple of apks and a couple run on pc all vroot...no luck here
 

iMJets

Senior Member
Sep 25, 2012
129
46
New York
I attempted this apparent root and did not get results. Figured it would not work since i have tried vroot in the past. Wait until there is more verification from other trusted members of the community.
 

jimyv

Senior Member
Jan 31, 2012
591
189
central Indiana
+1

I attempted this apparent root and did not get results. Figured it would not work since i have tried vroot in the past. Wait until there is more verification from other trusted members of the community.

FAIL FAIL FAIL FAIL and then FAIL
Omg! Confirmed ! Confirmed! Confirmed!
Was 13.3.2.2 now 13.3.1.0 rooted with safestrap!
 
Last edited:

058515471

Member
Jan 12, 2012
48
57
i dont know if vroot will work in your devices or not, but it work for me.
However, Safetrap didnt work and I dont like Chinese apps, so i tried to roll back and got lucky (maybe) :).
Now, SuperSU and Safetrap are working perfectly
 
  • Like
Reactions: jimyv and alireza21

stapler85

Senior Member
Oct 13, 2010
143
36
soft bricked. need 13.3.2.2 build prop

can someone please upload their 13.3.2.2 build.prop??

i guess in a moment of excitement, i've done a copy and paste of the build.prop from OP and over write it without backing up original build prop, after rooting with vroot now its soft bricked and wont turn on? im not even sure if i can recover it, i just need to reapply the build.prop
 

058515471

Member
Jan 12, 2012
48
57
can someone please upload their 13.3.2.2 build.prop??

i guess in a moment of excitement, i've done a copy and paste of the build.prop from OP and over write it without backing up original build prop, after rooting with vroot now its soft bricked and wont turn on? im not even sure if i can recover it, i just need to reapply the build.prop

here is build.prop from original 13.3.2.2 bin file.

p/s: did you root with vroot after edit the build.prop?
 

Attachments

  • build2.2.zip
    2.4 KB · Views: 167
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 43
    Just let you guys know. I have Safestrap back to work :)

    This is instructions to roll back to 13/14.3.1.0 from earlier version than 1x.3.2.5

    Download below file and tool:

    HDX ToolKit:
    http://xdaforums.com/showthread.php?t=2665683

    Roms:
    13.3.1.0 (Kindle HDX 7"): https://s3.amazonaws.com/kindle-fire-updates/update-kindle-13.3.1.0_user_310079820.bin
    or
    14.3.1.0 (Kindle HDX 8.9"): https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin

    Build prop editor:
    https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor


    PLEASE READ INSTRUCTION CAREFULLY

    INSTRUCTION:

    1. Root your Kindle by HDX ToolKit
    Instruction at: http://xdaforums.com/showthread.php?t=2665683
    1.1 Do not turn off Auto Update, just turn off and forget wifi to prevent auto update
    1.2 If you have safestrap installed, remove it.


    2. Change Version and Build Number to lower values than 13/14.3.1.0 and 310079820
    2.1 Use Build prop editor
    2.2 Change those lines:
    ro.build.version.incremental : "13.3.0.9_user_300079820"
    ro.build.version.number : "300079820"
    ro.build.description : "thor-user 4.2.2 JDQ39 13.3.0.9_user_300079820 release-keys"
    ro.build.fingerprint : "Amazon/thor/thor:4.2.2/JDQ39/13.3.0.9_user_300079820:user/release-keys"
    (same for apollo but use: 14.3.0.9 and keep apollo name in description and fingerprint - only change build number and version)

    3. Reboot the Kindle and go to Device > System Updates to check if Version and Build Number changed


    4. Do manually update to 13/14.3.1.0
    - Connect Kindle to PC by usb cable
    - Copy rom file (.bin) from PC into Internal storage
    - Go to Device > System Updates and Press Update


    5. Root and install Safestrap HDX ToolKit.
    Instruction at: http://xdaforums.com/showthread.php?t=2665683


    6. Press Thanks

    FOR 1x.3.2.5 and 1x.3.2.6
    USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
    How to use it.
    1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
    2. If Disable OTA update , Airplane mode ON and Enable OTA update
    3. If Install SafeStrap, uninstall safestrap on App.

    4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
    5. execute install.bat
    6. reboot
    7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
    8. Downgrade, wait a minute on the update menu, because display update button to take time.
    9. disable OTA update.

    This batch file works "kindle fire hdx 7" ONLY
    This is tested on version 13.3.2.5 and 13.3.2.6.
    http://d-h.st/MAs



    This batch file works "kindle fire hdx 8.9" ONLY
    sorry I do not have kindle fire hdx 8.9. I cannot test.

    10/3/14 update build.prop
    http://d-h.st/Tz8

    Thank @Poesini
    Very good that the rollback of Apollo is working .
    15
    Rollback Batch file for HDX 7 and 8.9

    USE IT AT YOUR OWN RESPONSIBILITY because rewrite recovery partition.
    How to use it.
    1. install Towelroot and Supersu using KFHDX Toolkit v 0.94
    2. If Disable OTA update , Airplane mode ON and Enable OTA update
    3. If Install SafeStrap, uninstall safestrap on App.

    4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
    5. execute install.bat
    6. reboot
    7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage.
    8. Downgrade, wait a minute on the update menu, because display update button to take time.
    9. disable OTA update.

    This batch file works "kindle fire hdx 7" ONLY
    This is tested on version 13.3.2.5 and 13.3.2.6.
    http://d-h.st/MAs



    This batch file works "kindle fire hdx 8.9" ONLY
    sorry I do not have kindle fire hdx 8.9. I cannot test.

    10/3/14 update build.prop
    http://d-h.st/Tz8

    Thank @Poesini
    Very good that the rollback of Apollo is working .
    7
    Download update-kindle-13.3.1.0_user_310079820.bin

    extract 4 files by 7zip or other tools.
    ---example---
    7z.exe e update-kindle-13.3.1.0_user_310079820.bin "boot.img" "recovery/recovery-from-boot.p" "system/etc/recovery-resource.dat" "system/etc/security/otacerts.zip"

    //4files send to kindle
    adb shell mkdir /sdcard/recovery
    adb push otacerts.zip /sdcard/recovery/otacerts.zip
    adb push boot.img /sdcard/recovery/boot.img
    adb push recovery-from-boot.p /sdcard/recovery/recovery-from-boot.p
    adb push recovery-resource.dat /sdcard/recovery/recovery-resource.dat

    // Rewrite OTACerts.zip file
    adb shell
    su
    mount -o remount, rw /system
    cd /sdcard/recovery
    cp otacerts.zip /system/etc/security/otacerts.zip

    //make Recovery.img
    Code:
    applypatch -b recovery-resource.dat boot.img recovery.img 063993bdc8b5b866ce29899c63323369b6eaeb33 8939520 52fdd36db56cd4f52aa7566050026df5890e49f4:recovery-from-boot.p

    //Rewrite Recovery.img
    Code:
    dd if=/sdcard/recovery/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

    I am gooing to make bat file and test
    if you want to bat file ,Please wait 3 day.

    Sorry this is kindle fire hdx 7 only
    In the case of hdx 8.9, applypatch command is different.

    This work might break the recovery partition .
    At your own responsibility
    5
    Success to Rollback form 13.3.2.5

    :laugh:
    There is a Two signature Check . One is otacerts.zip, another is keys in /recovery

    Octacers.zip is picked up from /system/etc/security in update-kindle-13.3.2.4_user_324002120.
    I rewrite Octacers.zip on device.

    Keys is in recovery partitions.
    I made recovery.img from 13.3.2.4 ROM.

    I extract 4 files from update-kindle-13.3.2.4_user_324002120.

    boot.img
    recovery/recovery-from-boot.p
    recovery/etc/install-recovery.sh
    system/etc/recovery-resource.dat

    install-recovery.sh file is simplified below.
    Code:
    #!/system/bin/sh
    applypatch -b recovery-resource.dat boot.img:7047168:0fc460789279f0e01e3bacae132687b5f7ff6346 new-recovery.img 0ff1e4113a6d0e0c49c3693c72957c4009ac443f 8939520 0fc460789279f0e01e3bacae132687b5f7ff6346:recovery-from-boot.p

    4 files copy to /system directory of device
    -example-
    /system/recovery-from-boot.p
    /system/boot.img
    /system/recovery-resource.dat
    /system/install-recovery.sh

    When system directory is read only, .
    mount -o remount, rw /system

    set parmission
    chmod 744 /system/install-recovery.sh

    make NEW-RECOVERY.IMG From Boot.img ,recovery-resource.dat and recovery-from-boot.p , when excute install-recovery.sh.

    In the good case , sha1 hash is 0ff1e4113a6d0e0c49c3693c72957c4009ac443f and file size is 8939520

    Finally rewirte recovery
    dd if=/system/new-recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

    After , please update 13.3.1.0 firmware as usual.



    Please do only expert and since it may break
    I became rickety about three times.

    I think that will work well using version 13.3.1.0,
    then notice SHA1 hash of new-recovery.img.

    Thank to focusfre4k and ggow.
    3
    ...
    btw i have the apollo edition

    I believe the files and script are for Thor only... not sure if those files are applicable to Apollo too. The error seems to indicate that boot.img file is not found. Sure that boot.img is in the Recovery folder?

    Might want to hold off until we get confirmation so that you don't brick your HDX since we're messing with the recovery...

    [EDIT]

    Downloaded the BIN archive file for Apollo from:

    https://kindle-fire-updates.s3.amazonaws.com/update-kindle-14.3.1.0_user_310079820.bin

    Found the comparable 14.3.1.0 (Apollo) files to be different from those for 13.3.1.0 (Thor):

    boot.img
    install-recovery.sh
    recovery-from-boot.p
    recovery-resource.dat
    otacerts.zip (but releasekey.x509.pem within the ZIP is the same)

    The equivalent script for Apollo should probably be:

    Code:
    applypatch -b recovery-resource.dat boot.img:7014400:807359528efa11ae0fd6da4840ddf3630bf0b801 recovery.img 80d339c46afc1ac00e9f0655f485c8dfb7103d9d 8904704 807359528efa11ae0fd6da4840ddf3630bf0b801:recovery-from-boot.p
    [/EDIT]