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

[Peepdog]

I had the same problem. I ended up upgrading to 3.2.5 and then downgrading. I tried a lot of different ways to edit buildprop and nothing would stick after a reboot.

I put the steps I took here, http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82.

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.

 

[travanx]

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]

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]

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]

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?

 

[Peepdog]

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]

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.

 

[kirewade]

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

 

[lekofraggle]

What is the error you are getting?

 

[DB126]

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]

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]

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.

 

[DB126]

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.

Wrong forum. Try here.

 

[junglistknot]

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

 

[jeryll]

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

Try again forum that Davey126 suggested, you didn't talked there...
7" Kindle Fire HD Q&A, Help & Troubleshooting

 

[junglistknot]

its the most current fire hd the one he pointed at is the older version. I was already posting in the current version forum.

 

[jeryll]

its the most current fire hd the one he pointed at is the older version. I was already posting in the current version forum.

LOL dude, seriously? OK, whatever...

 

[W99DEY]

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

 

[DB126]

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.

 

[W99DEY]

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