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

Search This thread

Peepdog

Member
May 3, 2013
11
0

travanx

Senior Member
Apr 4, 2010
234
43
Los Angeles
I'll try that. I downloaded the 3.2.5 bin and put it in the sdcard folder. But when I go to System Updates, there is no Update button. Just 'Check Now' which wants to use WiFi.

When I factory reset, booted back in and put the bin file on the sdcard, it worked. Exact same problems. I had to keep factory resetting for each upgrade/downgrade along the way. I always forgot all wireless connections so there was never anything to connect to.
 

Peepdog

Member
May 3, 2013
11
0
When I factory reset, booted back in and put the bin file on the sdcard, it worked. Exact same problems. I had to keep factory resetting for each upgrade/downgrade along the way. I always forgot all wireless connections so there was never anything to connect to.

First, I want to say I appreciate your help. However, when I do a factory reset then place the BIN in the Internal Storage folder, it still does not give me the option to update. I tried connecting it to wifi and hit the Check Now button, but it just says "Last Update Failed".

Any other ideas?
 

DB126

Senior Member
Oct 15, 2013
15,298
10,068
First, I want to say I appreciate your help. However, when I do a factory reset then place the BIN in the Internal Storage folder, it still does not give me the option to update. I tried connecting it to wifi and hit the Check Now button, but it just says "Last Update Failed".

Any other ideas?
A "Last Update Failed" message is often (albeit not always) an indication your device believes it is at a higher firmware version than the 'upgrade' being attempted. Suggest the following:
- restore your original build.prop (you made a backup, right?)
- attempt an upgrade to 3.2.5 using bin and instructions here; if the update doesn't take try a factory reset per guidance from @travanx
- once at 3.2.5 you will need to reroot (suggest HDX toolkit) and block OTA if you need to temporarily connect to wifi
- follow the guidance in the OP to downgrade from 3.2.5 to 3.1.x (lower portion of post; don't mess with build.prop)

I assume your device shipped with 3.2.4 or naturally upgraded from a lower version via Amazon's normal OTA process.

If it still doesn't recognize the 3.2.5 bin as an update then something is likely messed with build.prop and/or a previous attempt to block OTA updates that hasn't been fully reversed.

As always be sure to remove all wifi profiles and stay away from open hotspots so your device can't spontaneously connect. Once on 3.2.5 Amazon will attempt to push 4.x updates which you clearly do not want.
 

travanx

Senior Member
Apr 4, 2010
234
43
Los Angeles
After I factory reset I went into the device, made sure wireless didn't connect to anything. Then I used towelroot. Then reset the device. Then put the .bin file on the root sdcard folder. See if that updates. If not reset again and see if the .bin file is still where you placed it, then try updating. I kept doing some variation of this over and over until it finally worked. Once you get to 3.2.5 its smooth sailing.

Like Davey says check your build prop after the factory reset to verify its showing the correct number, 3.2.4?
 
  • Like
Reactions: Peepdog

Peepdog

Member
May 3, 2013
11
0
A "Last Update Failed" message is often (albeit not always) an indication your device believes it is at a higher firmware version than the 'upgrade' being attempted. Suggest the following:
- restore your original build.prop (you made a backup, right?)
- attempt an upgrade to 3.2.5 using bin and instructions here; if the update doesn't take try a factory reset per guidance from @travanx
- once at 3.2.5 you will need to reroot (suggest HDX toolkit) and block OTA if you need to temporarily connect to wifi
- follow the guidance in the OP to downgrade from 3.2.5 to 3.1.x (lower portion of post; don't mess with build.prop)

I assume your device shipped with 3.2.4 or naturally upgraded from a lower version via Amazon's normal OTA process.

If it still doesn't recognize the 3.2.5 bin as an update then something is likely messed with build.prop and/or a previous attempt to block OTA updates that hasn't been fully reversed.

As always be sure to remove all wifi profiles and stay away from open hotspots so your device can't spontaneously connect. Once on 3.2.5 Amazon will attempt to push 4.x updates which you clearly do not want.

I had to reenable the OTA Updates to get it to go to 3.2.5. Unfortunately, I forgot to turn it back off, and it upgraded to 4.5.3 overnight. Am I totally screwed now? My end goal was to install CM.
 

DB126

Senior Member
Oct 15, 2013
15,298
10,068
I had to reenable the OTA Updates to get it to go to 3.2.5. Unfortunately, I forgot to turn it back off, and it upgraded to 4.5.3 overnight. Am I totally screwed now? My end goal was to install CM.
At present there is no path from 4.5.3 (or any version above 3.2.6) to a firmware level that will accommodate CM or any other rom as a native install (ie: vulnerable to exploits that permit bootloader signature bypass or unlocking). You can rollback to 3.2.8 and use Safestrap to toggle between Fire OS and Nexus which are both JellyBean based. A KitKat flavor of Nexus may become available in the future. You can also upgrade to 4.5.2 and install gapps which has its own set of benefits and issues.

In short, CM is off the radar until another vulnerability/exploit combo becomes available which seems unlikely. Another path involves disabling Amazons anti-rollback protection which seems more promising. Keep an eye on the forums for further developments.
 
  • Like
Reactions: Peepdog

kirewade

Senior Member
Sep 24, 2013
83
36
i followed the OP and it put me on 13.0.0.0 and now it wont update to anything no matter how many times i do a factory reset
 

DB126

Senior Member
Oct 15, 2013
15,298
10,068
i followed the OP and it put me on 13.0.0.0 and now it wont update to anything no matter how many times i do a factory reset


You are not actually on 13.0.0.0. The rollback script (or build.prop tweaks you made) artificially sets this version so your device sees the 13.1.x file as an upgrade; rollbacks are not permitted.

Best guess is the 13.1.x bin is not present or in the wrong location. Needs to be in the root of sdcard or "internal storage" when viewed from a windows host.

Sent from my XT1030 using XDA Forums Pro.
 

tom00998877

New member
Jun 26, 2015
1
0
Damn... okay I'll start going through the dozens of unbrick threads... thank you for your help with everything. I'm gonna try and get ADB working later tonight... I'll post back if I am able to.

Hi,
did you achieve anything in this matter?
It seems I have a similar problem. After downloading build.prop, editing on my pc, reuploading and rebooting I get the exact same bahaviour (can boot to kindle recovery, cannot boot normally, cannot see device in adb any more [not even in usbdeview for that matter :( ] )
 

junglistknot

Senior Member
Jan 31, 2013
78
9
I am in the same boat with a kindle fire hd 7 4th gen. I need to downgrade from 5.2.0 OS to 4.5.3 OS and I cannot get my kindle to take the downgrade zip and an upgrade any help would be appreciated.
 

junglistknot

Senior Member
Jan 31, 2013
78
9
that was also the wrong forum but I have been talking in there. I am just looking for support with my efforts wherever I can get it
 

junglistknot

Senior Member
Jan 31, 2013
78
9
its the most current fire hd the one he pointed at is the older version. I was already posting in the current version forum.
 

W99DEY

Senior Member
Jun 21, 2009
249
55
I am sure I have seen a thread here with all the bin files available before.... searched and searched and I cant find them again....

I take it I need 13.3.1.0 then to upgrade to 13.3.2.3....

I have researched putting safestrap on but this seems old hat now.....

There doesnt seem to be any instructions from going from safestrap to full TWRP.... :s

Presumably I root, do the disable amazon updates, flash the two bim files by putting into root then using the system upgrader.... Can I then install TWRP then flash a ROM? If so which version and is it that easy?

Presumably TWRp hast to be installed by ADB transfer or fast boot? There seems to be a gulf in information between the two types of flashing.... could just be me being thick though.... :)
 
Last edited:

DB126

Senior Member
Oct 15, 2013
15,298
10,068
I am sure I have seen a thread here with all the bin files available before.... searched and searched and I cant find them again....

I take it I need 13.3.1.0 then to upgrade to 13.3.2.3....

I have researched putting safestrap on but this seems old hat now.....

There doesnt seem to be any instructions from going from safestrap to full TWRP.... :s

Presumably I root, do the disable amazon updates, flash the two bim files by putting into root then using the system upgrader.... Can I then install TWRP then flash a ROM? If so which version and is it that easy?

Presumably TWRp hast to be installed by ADB transfer or fast boot? There seems to be a gulf in information between the two types of flashing.... could just be me being thick though.... :)

Images can be found here: http://forum.xda-developers.com/showthread.php?p=55954966

Strongly suggest you do some more reading before attempting to flash any of these. You are correct, there are no step-by-step how-to guides. One f-up and your device is toast. That said there are a ton of helpful posts to help you through. Folks will respond to targeted questions provided you have done your homework first.

Your options are largely determined by your current firmware version. Sometimes you can rollback, often not. Don't assume Safestrap is old hat. It is often the only solution and works remarkably well. Don't make the mistake if thinking you can revive a brick through twrp/fastboot/adb magic. Kindles don't work that way.

Good luck.
 
Last edited:
  • Like
Reactions: travanx

W99DEY

Senior Member
Jun 21, 2009
249
55
Images can be found here: http://forum.xda-developers.com/showthread.php?p=55954966

Strongly suggest you do some more reading before attempting to flash any of these. You are correct, there are no step-by-step how-to guides. One f-up and your device is toast. That said there are a ton of helpful posts to help you through. Folks will respond to targeted questions provided you have done your homework first.

Your options are largely determined by your current firmware version. Sometimes you can rollback, often not. Don't assume Safestrap is old hat. It is often the only solution and works remarkably well. Don't make the mistake if thinking you can revive a brick through twrp/fastboot/adb magic. Kindles don't work that way.

Good luck.
Thanks for the quick and frank response.... :) just a pity that the safestrap ROMs are a bit dated....

Sent from my A0001 using Tapatalk
 
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://forum.xda-developers.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://forum.xda-developers.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://forum.xda-developers.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]