Related
My wife's 7" Kindle Fire HD keeps rebooting into the TWRP recovery. I had rooted it and installed a custom ROM several months ago, but could never get it stable and working correctly. So I gave up and restored the original images backup and all was well for several months. She used it quite regularly without issues.
Then a couple of weeks ago, she would charge it up 100%, use it to read then go to bed. By the next evening it would be as dead as a door nail. So thinking it was a bad battery I did some investigating and found that when she puts it into standby mode it will eventually reboot and go into TWRP. Of course it never enters sleep mode while on the recovery screen and the battery will eventually run down.
A couple of notes - If I reboot it to the system from TWRP but never unlock the screen it never reboots to recovery. Only when I unlock the screen and enter the Home screen, or open ANY program will it eventually reboot to TWRP.
I am suspecting that some program updated itself and that is causing the problem, but since she has numerous programs and I had auto update installed it is impossible to know which one is the culprit.
It is running software version 7.4.8_user_4849020, TWRP 2.6.3.1
Has anybody seen this issue? Any suggestions?
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
SafinWasi said:
Amazon'n software doesn't want to play nice with the 2nd bootloader and recovery. I suggest you to flash a custom rom like CM. The unofficial builds and monthly snapshots are pretty stable.
Oh,and you need to upgrade TWRP to 2.7.0.0 to install CM 11.
Click to expand...
Click to collapse
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
pastorbob62 said:
Not going to happen. I went down that obstacle course several months ago and had nothing but problems with CM. Never could get the tablet stable and working in spite of following all of the suggestions and tweaks.. That is why I went back to stock. It worked without issues for several months so as far as I'm concerned it is a problem that can be fixed. It is just going to take me a while to solve it. In the meantime, it seems that as long as she is in the Kindle Reader software and actively using it the reboot doesn't happen. If it gets to where it is not usable I'll just bite the bullet and buy her a new tablet.
Click to expand...
Click to collapse
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
So far no one has found a way around Amazon's bootloader checks, so there's no way to solve it. And CM has become much much more stable now (we're considered official now ). So CM may be worth another go
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
pastorbob62 said:
Hmmmm. Well, I may give this a shot after I replace her Kindle for her. I have about $100.00 in my Amazon account that I can apply to the price of a new tablet (not another Kindle, she wants a REAL Android device ). Then I can experiment as much as I desire and if things go badly, she will still have a tablet.
Thank you for the feedback!
Click to expand...
Click to collapse
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Bao289 said:
Cm11 has changed ALOT in the past 9 months. It's very stable, and has the latest android version 4.4.4. Also think about upgrading your Twrp version to 2.7.0.
Click to expand...
Click to collapse
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
pastorbob62 said:
Upgrading to TWRP 2.7.0 is understood. I had to do that in order to run a Kit-Kat based ROM on my Asus TF300. (Which, by the way, is MUCH easier to customize than this Kindle.)
The main problem I previously had with CM was getting the Kindle app to work without crashing and causing a reboot. or locking the tablet up. Has that issue been resolved?
Click to expand...
Click to collapse
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
NO one can access Prime videos outside of a Kindle OS. It seems like the one thing devs can't crack yet.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Bao289 said:
Yes that issue has been resolved. Hascode changed the build prop file to make amazon apps work. I can acess books, apps but NOT prime videos.
Click to expand...
Click to collapse
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
pastorbob62 said:
Okay, I bought my wife a new tablet (Asus 10.1") and I am finally at the point where I am ready to give this a try.
Just to recap, I am running software version 7.4.8_user_4849020, TWRP 2.6.3.1.
Can I just flash TWRP 2.7.0.0 from TWRP 2.6.3 and then flash CM 11 from TWRP 2.7.0.0? I was able to do that with my Asus tablet without any issues. Or do I have to go back through using fastboot.
Click to expand...
Click to collapse
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Bao289 said:
flash twrp 2.7.0.0 using fire flash app DO NOT FLASH TWRP IN OLD TWRP. So that you have the latest twrp version. Make sure you do a full back up then clear davalik, cache (factory reset) in twrp. THEN flash cm 11 with gapps.
Click to expand...
Click to collapse
Can't seem to locate a version of Fire Flash to download. Where might I find it?
pastorbob62 said:
Can't seem to locate a version of Fire Flash to download. Where might I find it?
Click to expand...
Click to collapse
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Bao289 said:
LINK TO TRWP 2.7.0.0= https://goo.im/devs/Hashcode/tate/kfhd7-twrp-2.7.0.0-recovery.img/
FireFlash = http://forum.xda-developers.com/showthread.php?t=2168512
Under RECOVERY PARTITION put the TWRP image file. LEAVE OTHER BOXES ALONE.
Then Reboot into recovey.
You will have the latest twrp recovery. Backup in twrp then flash cm11 with gapps.
Click to expand...
Click to collapse
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
pastorbob62 said:
Thank you. I had TWRP 2.7.0.0 but could not find fire flash.
Click to expand...
Click to collapse
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Fabulous!! I now have a nice 7" tablet with decent resolution, performance and all of the accessibility to Android apps that my 10.1" tablet has.
Thank you to all for your help.
Bao289 said:
At the bottom of the fireflash app youshould be able to boot into recovery. do not boot into eecovey by shutting it down and holding the volume butoons. Use the app to reboot as the reboot makes the change.
Just to let you know if you haven't done so.
Click to expand...
Click to collapse
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
No Problem make sure you are updated to the latest cm11.
pastorbob62 said:
Yes, I had it figured out and am now running CM 11 with TWRP 2.7.0.0. I am running it in ART and OC'ed at 1.5 Ghz. So far no reboots or crashes.
Thank you for your help.
Click to expand...
Click to collapse
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
SafinWasi said:
Wait. You're using ART? I normally use Dalvik but it's mostly up to personal preference.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Yup! Been using ART on my TF300T for about six months so I enabled it on this tablet too.
ART runs circles around Dalvik as far as performance is concerned. I've heard that there are some apps that won't run with ART and Xposed Framework is not compatible with it, but I don't use Xposed and I have never run into an app that has caused me any problems.
***PLEASE UNLOCK YOUR BOOTLOADER INSTEAD. ***
*** IF ANY OF THE INFORMATION ON THIS THREAD IS MISUSED IT CAN RESULT IN A BRICKED DEVICE ***
Introduction
- BEFORE PROCEEDING READ THROUGH CAREFULLY, IF THERE IS ANY DOUBT THEN ASK BEFORE PROCEEDING
- Safestrap provides TWRP like recovery capabilities for locked devices.
- This is based on the original work of Hashcode.
- This is for Apollo and Thor devices only.
Known Issues
- Secondary slots boot, but the WiFi module does not load
- Since the secondary slots work but have no WiFi, you will need to flash Nexus v4 to the stock slot for now
Compatible ROMS
- HDX Nexus ROM v4
- CM-11
- Fire Nexus ROM
Prerequisites for Installation
- You must be on FireOS stock firmware 4.5.2, 4.5.3, 4.5.4, 4.5.5 or 4.5.5.1 <- Please confirm this before proceeding <-
- You must have root access
Installation
- Install the app
- Grant root access if needed
- Read user agreement and accept to proceed
- Then click install recovery
- When recovery is installed click reboot to recovery
- You should eventually end up in safestrap recovery.
Download
*** Please do NOT create any mirrors ***
- Safestrap for THOR
- Safestrap for APOLLO
Thanks to my Testers
- Davey126
- kudoz83
- lekofraggle
- zamtang
- paul26rem
XDA:DevDB Information
Safestrap KK, Device Specific App for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2015-06-18
Created 2015-06-18
Last Updated 2019-10-02
Reserved
Is there a possibility of running cm 12 in this recovery?
paul26rem said:
Is there a possibility of running cm 12 in this recovery?
Click to expand...
Click to collapse
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
ggow said:
- Not at the moment and probably not likely.
- If amazon release a FireOS based on lollipop and we get root then yes maybe.
Click to expand...
Click to collapse
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Davey126 said:
Although I prefer AOSP/Nexus the next logical question would be CM11 as it shares common roots with FireOS v4 / Nexus v4 and at present does not require an unlocked bootloader. Actually, not sure why anyone would opt for CM11 over Nexus on HDX given the status of the two roms. Don't get me wrong - CM is great and has some nice built in functionality (all of which is obtainiable via Xposed on Nexus) but the CM11/CM12 implementations still have a few issues with the HDX variants.
Click to expand...
Click to collapse
I agree. Don't get me wrong, I love cm, but If you want a stable Rom, Nexus is where it's at.
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
thuyrs said:
Hi, I used your safetrap version on fire OS 4.5.2 rooted, when I flash rom nexus 4.0.1 on secondary slot rom, It booted greatly! But as you said, it haven't wifi module, but when I flash it in stock slot, successfully, but it only boot to splash screen and no more, do you know my error? Please help me, thanks!
One more thing, I use fire OS 14.4.5.2.2004220, not 2004120, nothing different, right?
Click to expand...
Click to collapse
Can you get into Safestrap recovery? If so try a 'factory reset' located under the 'wipe' option and then reboot. If that does not work return to Safestrap recovery and perform an 'advanced wipe'. Check all of the partitions (Dalvik Cache, Data, Cache, System). After wiping reinstall Nexus v4 and gaps from within Safestrap and then reboot.
A few cautions/notes:
- make sure you are working with the correct slot!
- make sure you perform the 'factory reset' from safestrap recovery - not the native Amazon recovery built into your Kindle
- gaps is important for proper operation of Nexus v4. Some low level functions (eg: the home button) do not work correctly if gaps is not flashed immediately after Nexus v4
Please post the results to others can learn from your experience. Thanks!
Hi, after I wiped everything and reinstall to slot stock, it booted, and Wifi module worked correctly, thanks for your help!
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
loco09 said:
hi
does ur version of stock 4.5.2 that u attached here already rooted? or do i have to towelroot it?
thx
Click to expand...
Click to collapse
Flash SuperSU after and you have root access.
Also you will need to block ota updates so do not enable WiFi until you have done so.
EDIT: I have just added a note to the OP about this.
Sent from my Nexus 6 using Tapatalk
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
hfpop said:
I run HDX 7in ver 3.2.8 rolled back by Amazon CS with OTA blocking included, with Safestrap and Nexus 1.0.1. Why will I need to update to this and how do I do it safely?
Click to expand...
Click to collapse
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Davey126 said:
You are in a tough situation given Amazon CS performed the 3.2.8 rollback and OTA is apparently blocked using an unknown method (likely at the Amazon servers but can't be sure).
Options as follows:
1) Contact Amazon CS and request an upgrade to 4.5.2. However, they will likely upgrade to 4.5.4 which is unrootable at present. You would then need to manually rollback to 3.2.8 followed by a manual upgrade to 4.5.2. All this involves risk with the consequence being a bricked device if things go wrong.
2) Attempt to manually update to 4.5.2 which may or may not work given the OTA block. There is less risk but the consequence of a bad upgrade is equally severe (bricked tablet).
3) Stay on FireOS 3.2.8, Safestrap v3.7.x and Nexus 1.0.1 for now. Better/safer upgrade options will likely evolve with time. Nexus 1.0.1 remains quite serviceable for all but the newest applications especially when combined with Xposed Framework and Gravitybox.
I strongly advise option #3 unless you are willing to toss your Kindle in the trash if things go wrong (or are still within your 1 year warranty).
Click to expand...
Click to collapse
Just to add to what Davey126. My current understanding is that a manual upgrade does indeed work. 3.2.8 only stops the OTA updates from coming through.
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
ChuTeng said:
after install safetrap now i got a problem, i cannot boot on stock slot, my kindle boot and stop at logo kindle fire (white - yellow). I try wipe all but nothing change. How can i copy Stock Image to the sd card to flash in stock slot, my computer does not find kindle. Please help
Click to expand...
Click to collapse
Can you still get into Safestrap?
ggow said:
Can you still get into Safestrap?
Click to expand...
Click to collapse
adb driver in my computer is problem, i fixed. Thanks.
ChuTeng said:
adb driver in my computer is problem, i fixed. Thanks.
Click to expand...
Click to collapse
Does that mean you are up and running again?
Awesome job!!!!!!!!!!
Confirmation number: 67M75398MF9375820
I'm on 4.5.4 7", any options for me? Can I contact amazon n hope they will roll me back? What version do I ask for?
Hey! I am currently running the newest version of ROM][AOSP] Fire Nexus ROM - LMY49J [08 FEB 2017] on m 7inch Amazon Fire tablet.
I want to reset it to stock but I dont know how without messing up! I`d like to get to the newest fire os version which supports rooting
freaky2xd said:
Hey! I am currently running the newest version of ROM][AOSP] Fire Nexus ROM - LMY49J [08 FEB 2017] on m 7inch Amazon Fire tablet.
I want to reset it to stock but I dont know how without messing up! I`d like to get to the newest fire os version which supports rooting
Click to expand...
Click to collapse
Wait - you want FireOS 5.3.1 (which doesn't support Alexa) over Nexus? Ok, see link.
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Davey126 said:
Wait - you want FireOS 5.3.1 (which doesn't support Alexa) over Nexus? Ok, see link.
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Click to expand...
Click to collapse
haha thanks ut I`ve jsut found a FlashFire backup with 5.3.1
however, I only wanted to reinstall NEXUS ROM
freaky2xd said:
haha thanks ut I`ve jsut found a FlashFire backup with 5.3.1
however, I only wanted to reinstall NEXUS ROM
Click to expand...
Click to collapse
You dont need to be on stock to re-install the Nexus ROM. Just use FF to wipe the /data /cache Dalvic ETC, and reinstall the zip.
crazyates said:
You dont need to be on stock to re-install the Nexus ROM. Just use FF to wipe the /data /cache Dalvic ETC, and reinstall the zip.
Click to expand...
Click to collapse
Was on Nexus; wanted to revert to FireOS. Now in a bootloop. Reloading FireOS only option assuming stock recovery still functional.
Davey126 said:
Was on Nexus; wanted to revert to FireOS. Now in a bootloop. Reloading FireOS only option assuming stock recovery still functional.
Click to expand...
Click to collapse
When I read this thread, I didn't realize he was in a bootloop. Yeah, that means his only option is sideloading.
crazyates said:
When I read this thread, I didn't realize he was in a bootloop. Yeah, that means his only option is sideloading.
Click to expand...
Click to collapse
Yep - he's got bread crumbs in several threads.
I have flashed blu r1 hd with CM 14 but stupid me i did not backup my old rom. How can i flash stock rom back? I have twrp install and unlock bootloader.
mengkheanb said:
I have flashed blu r1 hd with CM 14 but stupid me i did not backup my old rom. How can i flash stock rom back? I have twrp install and unlock bootloader.
Click to expand...
Click to collapse
These are the most recent "stock" ROMs we have available.
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
V8.4 is prime ROM with ads already removed
V21 is the non-prime that comes from Blu already without ads.
hello after i flashed the v8.4 rom it stuck at blu bold like us logo
mengkheanb said:
hello after i flashed the v8.4 rom it stuck at blu bold like us logo
Click to expand...
Click to collapse
did you do full wipe of data?
coming from cm it would be needed
how to do full wipe in twrp?
mengkheanb said:
how to do full wipe in twrp?
Click to expand...
Click to collapse
sorry, just meant wipe.
but from the wipe screen you can then select format if needed or desired.
It's working now thank you!
How to?
Hi,
I'm sorry for this newb question but this is my first android.
Is there a tutorial in here on how to flash the ROM?
I have a new Blu R1 HD with the:
BLU_R0010UU_V8.4_GENERIC 05-05-2017 18:49
and I want to flash the ROM to get rid of the ads.
PREngineer said:
Hi,
I'm sorry for this newb question but this is my first android.
Is there a tutorial in here on how to flash the ROM?
I have a new Blu R1 HD with the:
BLU_R0010UU_V8.4_GENERIC 05-05-2017 18:49
and I want to flash the ROM to get rid of the ads.
Click to expand...
Click to collapse
sorry, at the present time, there is no method to root or modify V8.4
What are the steps to flashing back the stock rom and unrooting the phone?
I've unlocked the bootloader, flashed twrp, and obtained a system-less root. I would like to get the phone back to as close as possible as it originally was.
waylonh said:
What are the steps to flashing back the stock rom and unrooting the phone?
I've unlocked the bootloader, flashed twrp, and obtained a system-less root. I would like to get the phone back to as close as possible as it originally was.
Click to expand...
Click to collapse
To what end? I mean I have put an unmodified non prime version ROM up. It is as close to original as you can easily get. And when you install a new ROM after a systemless root, root is undone by default. Because systemless root is in the boot.img, which is replaced when you put new ROM. And also if it was system type root, the new ROM replaces system, so it would also remove root.
You can use twrp to install v21, a stock ROM, then do not install SuperSU. That's all there is to it.
If you then want to put stock recovery on too. Simply reboot to system after installing v21 and the factory recovery-from-boot.p should take over and put stock recovery on. (This was actually a problem for a couple of people, but it is what you want so , there you go)
But I need to ask , what do you hope to achieve by doing that?
Quick question I have the 2017 Blu R1 HD R3003UU-01 Amazon phone with ads. Just about 2 days ago my phone randomly rebooted it went to the Blu bold like us screen then to the colorful bold like us screen then it stops and just stays like that never changes till I power it off. What are my options, I have never rooted this phone never downloaded anything to mess with any updates or firmware why would this happen?
I'm currently using Fire 7 5th gen at 5.3.6.4. Is there any way that I could downgrade it to the "rootable" version which is 5.3.1. Thanks in advance!
Lance AJ said:
I'm currently using Fire 7 5th gen at 5.3.6.4. Is there any way that I could downgrade it to the "rootable" version which is 5.3.1. Thanks in advance!
Click to expand...
Click to collapse
You can not downgrade below 5.4.0.0 nor root at present.
No Updates to this Topic?
-DDD- said:
No Updates to this Topic?
Click to expand...
Click to collapse
Same answer; not possible.
Also mine autoupdated in a moment of distraction to 5.3.6.4---
Still no solutions?
Lance AJ said:
I'm currently using Fire 7 5th gen at 5.3.6.4. Is there any way that I could downgrade it to the "rootable" version which is 5.3.1. Thanks in advance!
Click to expand...
Click to collapse
Here is a solution: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
Stuck on TWRP
AmznUser444 Dev said:
Here is a solution: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
Click to expand...
Click to collapse
Hello all,
I followed the above solution and i'm up to:
step 9. Use TWRP to flash custom ROM, Magisk or SuperSU
but don't know what to do at this point to downgrade it to 5.3.1
I tried "Install"
I copied "fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin" on a microSD but It doesn't see the .bin file so i changed it to .img.
I see under "Select Partition to Flash Image:"
Boot
Recovery
But when i tried it they both say "Size of image is larger than target device"
I don't have firmware option
Any help would be appreciated.
Logansan1 said:
Hello all,
I followed the above solution and i'm up to:
step 9. Use TWRP to flash custom ROM, Magisk or SuperSU
but don't know what to do at this point to downgrade it to 5.3.1
I tried "Install"
I copied "fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin" on a microSD but It doesn't see the .bin file so i changed it to .img.
I see under "Select Partition to Flash Image:"
Boot
Recovery
But when i tried it they both say "Size of image is larger than target device"
I don't have firmware option
Any help would be appreciated.
Click to expand...
Click to collapse
Dont try downgrading, install lineage. What 7 inch device do you have Ford (2015) Austin (2017) or Maverick (2019)?
Michajin said:
Dont try downgrading, install lineage. What 7 inch device do you have Ford (2015) Austin (2017) or Maverick (2019)?
Click to expand...
Click to collapse
5th generation. - Ford
Logansan1 said:
5th generation. - Ford
Click to expand...
Click to collapse
Download lineage 12.1 or 14.1 from here (14.1 will require a bunch of patches) as the OP isn't updating currently... Follow the directions here...
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3962457
Michajin said:
Download lineage 12.1 or 14.1 from here (14.1 will require a bunch of patches) as the OP isn't updating currently... Follow the directions here...
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3962457
Click to expand...
Click to collapse
Awesome! Thank you. Looks good.