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

[DB126]

Yes it's still operational, although I had to install another launcher as after instilling Open Gapps I could not pass the setup wizard. Please note that I have Safestrap installed.

Are you interested replacing FireOS with Nexus or CM11 which effectively yields a standard Android tablet detached from Amazon's ecosystem? The work effort and risks (low) are similar for all three paths. All work with Safestrap.

Sorry for the series of questions. Trying to identify the best path and minimize rework.

 

[mohzean]

[/COLOR]

Are you interested replacing FireOS with Nexus or CM11 which effectively yields a standard Android tablet detached from Amazon's ecosystem? The work effort and risks (low) are similar for all three paths. All work with Safestrap.

Sorry for the series of questions. Trying to identify the best path and minimize rework.

First Thank you for your responsiveness,
Currently I have Safestrap that I could create a new space for CM11. However I'm not so happy with it, I'd rather go back to the original Amazon's image then later I can create new space for CM11 to have both working in parallel.

 

[DB126]

[/COLOR]

First Thank you for your responsiveness,
Currently I have Safestrap that I could create a new space for CM11. However I'm not so happy with it, I'd rather go back to the original Amazon's image then later I can create new space for CM11 to have both working in parallel.

Below are two links to Safestrap compatible roms:
- first replaces current image with FireOS 4.5.2 (no 4.5.5.1 counterpart)
- second is an emergency recovery option (Nexus) if the first fails

Download both and place in internal storage. Reboot to Safestrap recovery. Use the install option to flash FireOS to the stock slot. Accept option to wipe dalvik+cache after flash completes. Then reboot system.

You mentioned 'create a new space for CM11’ should you opt to switch at a future time. Never do this with Safestrap v4! Custom roms replace FireOS on this device; they should never be loaded into secondary slots.

Safestrap Flashable HDX Stock Images
Fire Nexus ROM for HDX

 

[mohzean]

Below are two links to Safestrap compatible roms:
- first replaces current image with FireOS 4.5.2 (no 4.5.5.1 counterpart)
- second is an emergency recovery option (Nexus) if the first fails

Download both and place in internal storage. Reboot to Safestrap recovery. Use the install option to flash FireOS to the stock slot. Accept option to wipe dalvik+cache after flash completes. Then reboot system.

You mentioned 'create a new space for CM11’ should you opt to switch at a future time. Never do this with Safestrap v4! Custom roms replace FireOS on this device; they should never be loaded into secondary slots.

{links pending}

Again thank you for your reply,
I just wanted to know after installing 4.5.2, can I upgrade to the latest?

Waiting for links

 

[DB126]

Again thank you for your reply,
I just wanted to know after installing 4.5.2, can I upgrade to the latest?

Waiting for links

Links posted. Be sure to pick the version appropriate to your device (check twice).

4.5.2 *should* auto update to 4.5.5.1 once flashed. However Amazon OTAs can be fickle once FireOS has been updated via Safestrap. There have been reports both ways...OTA to 4.5.5.1 worked perfectly and OTA never worked leaving the user stuck on 4.5.2. If the latter occurs your device will still be fully functional and missing no features. However, you may run into trouble running custom roms in the future as increasingly 4.5.5.1 is the recommended base level when using Safestrap. It's a risk you have to assess before moving forward.

After flashing 4.5.2 you can subsequently reinstall the Safestrap v4 app (here) to either reinstall Safestrap recovery or remove it entirely.

 

[mohzean]

Below are two links to Safestrap compatible roms:
- first replaces current image with FireOS 4.5.2 (no 4.5.5.1 counterpart)
- second is an emergency recovery option (Nexus) if the first fails

Download both and place in internal storage. Reboot to Safestrap recovery. Use the install option to flash FireOS to the stock slot. Accept option to wipe dalvik+cache after flash completes. Then reboot system.

You mentioned 'create a new space for CM11’ should you opt to switch at a future time. Never do this with Safestrap v4! Custom roms replace FireOS on this device; they should never be loaded into secondary slots.

Safestrap Flashable HDX Stock Images
Fire Nexus ROM for HDX

Thank you for all your support, I'm following this now and will let you know how it is gone.

---------- Post added at 02:48 PM ---------- Previous post was at 02:15 PM ----------

Links posted. Be sure to pick the version appropriate to your device (check twice).

4.5.2 *should* auto update to 4.5.5.1 once flashed. However Amazon OTAs can be fickle once FireOS has been updated via Safestrap. There have been reports both ways...OTA to 4.5.5.1 worked perfectly and OTA never worked leaving the user stuck on 4.5.2. If the latter occurs your device will still be fully functional and missing no features. However, you may run into trouble running custom roms in the future as increasingly 4.5.5.1 is the recommended base level when using Safestrap. It's a risk you have to assess before moving forward.

After flashing 4.5.2 you can subsequently reinstall the Safestrap v4 app (here) to either reinstall Safestrap recovery or remove it entirely.

I installed 4.5.2 successfully using Safestrap, cleared cache and reboot; now it's stuck on Yello logo for around 30 mins. Is this normal? Should I force turn-off and restart again?

 

[DB126]

Thank you for all your support, I'm following this now and will let you know how it is gone.
::
I installed 4.5.2 successfully using Safestrap, cleared cache and reboot; now it's stuck on Yello logo for around 30 mins. Is this normal? Should I force turn-off and restart again?

It is not and may be a result of previous modifications to build.prop. Suggest returning to Safestrap recovery and clearing system/data/dalvik/cache from the Wipe menu. Before doing that make sure the previously download ROM files are located in the the sdcard folder (or subfolder in sdcard.) via advanced->file manager. Definitely do not want to wipe those files! Then reflash FireOS and reboot system.

Before doing any of the above:
- insure device has at last 25% battery remaining (preferably close to a full charge)
- try powering off and restarting; simple, risk-free and might just work

 

[mohzean]

It is not and may be a result of previous modifications to build.prop. Suggest returning to Safestrap recovery and clearing system/data/dalvik/cache from the Wipe menu. Before doing that make sure the previously download ROM files are located in the the sdcard folder (or subfolder in sdcard.) via advanced->file manager. Definitely do not want to wipe those files! Then reflash FireOS and reboot system.

Before doing any of the above:
- insure device has at last 25% battery remaining (preferably close to a full charge)
- try powering off and restarting; simple, risk-free and might just work

If I wipe the data, won't this delete the ROM files from the SD Card?

 

[DB126]

If I wipe the data, won't this delete the ROM files from the SD Card?

No - sdcard and folders/files within it are considered "internal storage" and are not flushed by the (user) data wipe option.

 

[mohzean]

No - sdcard and folders/files within it are considered "internal storage" and are not flushed by the (user) data wipe option.

Thank you so much for your help, now I have version 4.5.2 working successfully, although update does not work, giving me error "Last update failed"
I rooted using Kingsroot and installed Safetrap.

Thank you

 

[DB126]

Thank you so much for your help, now I have version 4.5.2 working successfully, although update does not work, giving me error "Last update failed"
I rooted using Kingsroot and installed Safetrap.

Thank you

Let's leave well enough alone. Can revisit 4.5.2 -> 4.5.5.1 update should you wish to install a custom rom in the future. Strongly suggest you not attempt to install any variation of Google Play Services and/or Play Store with FireOS v4. Outcomes are variable but almost universally unsatisfactory depending on pain threshold. Custom ROM is the best path if you find Amazon's offerings too limiting.

 

[mohzean]

Let's leave well enough alone. Can revisit 4.5.2 -> 4.5.5.1 update should you wish to install a custom rom in the future. Strongly suggest you not attempt to install any variation of Google Play Services and/or Play Store with FireOS v4. Outcomes are variable but almost universally unsatisfactory depending on pain threshold. Custom ROM is the best path if you find Amazon's offerings too limiting.

Yes I guess it is enough for now , however do you think custom Rom can give higher version of Android (e.g. Lollipop)?

 

[ivan_nik]

Download link for update files for Apollo 3.2.5 did not work. I cann't download install.sh file. PM to me or post new link to it please.

 

[DB126]

Download link for update files for Apollo 3.2.5 did not work. I cann't download install.sh file. PM to me or post new link to it please.

This procedure is obsolete any any xx.3.x.x version of FireOS can be rooted with Towelroot. From there you can unlock the bootloader, install TWRP and flash any custom rom for this device including KitKat, Lollipop and Marshmallow variants. No need to rollback or mess with Safestrap.

The above statements may counter some older guidance you see in the forums. The 'discovery' that the bootloader can be unlocked on any 3rd gen device is fairly recent.

After rooting be sure to keep the device network isolated (WiFi off; Airplane/flight mode engaged) to prevent an unwanted OTA update from Amazon that may ruin your day.

See the following thread to unlock the bootloader. You'll benefit from some technical background as the guide is written for experienced users.

http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982

 

[ivan_nik]

Ok, thank you.