Database Develop

[RECOVERY][UNLOCKED BL] TWRP 3.5.0_9-1

Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Prerequisites for Installation
- Must have an unlocked bootloader
Installation
- Use Flashify OR:
- Go into fastboot mode
- Install using the following command where <recovery-image> is the relevant file for your device
Code:
fastboot flash recovery <recovery-image>
*** Please do NOT create any mirrors ***
Downloads
All TWRP Builds for Apollo and Thor
Source Code
- Kernel Source
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Stable Release Date: 2016-02-25

Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can, as long as your bootloader is unlocked

I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?

Cl4ncy said:
I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?
Click to expand...
Click to collapse
Should be fine
Sent from my Nexus 6 using Tapatalk

ggow said:
Should be fine
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked fine.
The screenshot function still creates a 0 bytes file in Pictures\Screenshots though, which can be deleted via TWRP only.

Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?

Cl4ncy said:
Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?
Click to expand...
Click to collapse
It's not a bug, usually appears on first run only and should not impact TWRP's ongoing use.

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Click to expand...
Click to collapse
ggow said:
Yes you can, as long as your bootloader is unlocked
Click to expand...
Click to collapse
Worked like a charm. Nice visual upgrade over 2.8.7.0. Summary of other changes here.

New Build is Up
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0

ggow said:
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0
Click to expand...
Click to collapse
Updated via Flashify on a pair of Thors; no issues.

Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....

chaefei said:
Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....
Click to expand...
Click to collapse
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?

Davey126 said:
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?
Click to expand...
Click to collapse
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........

chaefei said:
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........
Click to expand...
Click to collapse
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197

Davey126 said:
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
Click to expand...
Click to collapse
thank you very much

chaefei said:
thank you very much
Click to expand...
Click to collapse
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.

Cl4ncy said:
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.
Click to expand...
Click to collapse
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？

chaefei said:
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？
Click to expand...
Click to collapse
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.

Cl4ncy said:
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.
Click to expand...
Click to collapse
thanks. i will try .
i want use fastboot method. But when i connect hdx to computer, the computer have nothing response.....

Newest root-possible Fire OS???

hey! whats the newest fire os version I can root? I have recently got my 7 inch Fire Tablet (5th Gen) and updated it to 5.3.2.1 which is not downgradeable and cannot be rooted so I sent it back and ordered another one which I won`t update ota so I want to know which firmware I can flash but still can root
great would be a link to the .bin file ^^

freaky2xd said:
hey! whats the newest fire os version I can root? I have recently got my 7 inch Fire Tablet (5th Gen) and updated it to 5.3.2.1 which is not downgradeable and cannot be rooted so I sent it back and ordered another one which I won`t update ota so I want to know which firmware I can flash but still can root
great would be a link to the .bin file ^^
Click to expand...
Click to collapse
At of this post (check the date) FireOS 5.3.1 is the highest version that can be exploited with KingRoot on a 5th gen Fire.

freaky2xd said:
hey! whats the newest fire os version I can root? I have recently got my 7 inch Fire Tablet (5th Gen) and updated it to 5.3.2.1 which is not downgradeable and cannot be rooted so I sent it back and ordered another one which I won`t update ota so I want to know which firmware I can flash but still can root
great would be a link to the .bin file ^^
Click to expand...
Click to collapse
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware
On this page you can find the 5.3.1 update file which can be manually installed with ADB. fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin is the correct file to download. Info on how to install:
Jrhotrod said:
Actually, I'm pretty sure that you can easily sideload FireOS 5.3.1 (rootable) from recovery mode easily. Here's how to do it:
1. Go to http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/SuperTool and download the AmazonFire5thGenSupertool.zip. Extract it to somewhere where you can conveniently access it.
2. Also go to http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware and download fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin.
3. Now open the Supertool folder you downloaded and run auto.bat. Once everything loads up, select option 1 and when those options load, select option 3 to test your drivers. Depending upon your result, you can install the necessary drivers now or move along as you were. This test can also determine whether you have ADB.
4. Enable USB debugging on your Fire.
5. Plug in your tablet.
6. Now go to the folder where you downloaded the 5.3.1 firmware. Hold down Shift and right click inside the folder. Select "Open command window here".
7. Type "ADB devices" in the window. If a series of numbers appears, then your Fire is recognized and you are good to go. If it says "unauthorized", you may need to turn on the tablet and allow USB debugging from this certain PC.
8. Now reboot your tablet to recovery by typing .
9. Once in recovery, on your Fire select "Apply update from adb". Now go to the Command Prompt window you have open and type:
10. The downgrade will begin in earnest. DO NOT be afraid if it says "patching system image unconditionally" because that is TOTALLY NORMAL and you will be fine. You will know when the downgrade is complete when the menu reappears on the tablet.
11. Now select on your Fire "reboot device now".
12. Okay! You are now in a ROOTABLE ROM! To take advantage of this we need to go and open the Fire 5th gen Supertool once again and this time select option 6 (or whatever it is) and root device now! Follow the onscreen instructions.
BOOM! Done and rooted with SuperSU. Now you can install CM 12.1. Contact me if you have any questions regarding this or the ROM.
Click to expand...
Click to collapse

jrhotrod said:
http://rootjunkysdl.com/files/?dir=amazon fire 5th gen/firmware
on this page you can find the 5.3.1 update file which can be manually installed with adb. Fire-os-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin is the correct file to download. Info on how to install:
Click to expand...
Click to collapse
*** warning *** warning *** warning ***
Do not attempt to flash/install/sideload fireos 5.3.1 if current version is 5.3.2.1 or greater. Device will hard brick with no possibility of recovery.
*** warning *** warning *** warning ***

Davey126 said:
*** warning *** warning *** warning ***
Do not attempt to flash/install/sideload fireos 5.3.1 if current version is 5.3.2.1 or greater. Device will hard brick with no possibility of recovery.
*** warning *** warning *** warning ***
Click to expand...
Click to collapse
He is right, do not attempt if the device is running 5.3.2.1. But FireOS 5.3.2 is fine ☺

Jrhotrod said:
http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware
On this page you can find the 5.3.1 update file which can be manually installed with ADB. fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin is the correct file to download. Info on how to install:
Click to expand...
Click to collapse
thanks but I have root, xposed and cyanogenmod 12 since two weeks already ^^

freaky2xd said:
thanks but I have root, xposed and cyanogenmod 12 since two weeks already ^^
Click to expand...
Click to collapse
Haha, okay. ??

reset to stock Android from Nexus ROM

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.

Removed Root on Costum FIrmware

As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford

Unversed said:
As Mantioned in the title I accidentally removed my Root permission on my Amazon Fire . I'd tried to reeinstall busybox and after a reboot root permissions where gone :/
I also tried to use King Root again but with no luck. Flashed it with FireFlash
Model:KFFOWI
ROM:Cyanogenmod 12.1-20161122-UNOFFICIAL-ford
Click to expand...
Click to collapse
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.

Davey126 said:
,
Assume you have tried re-enabling root under developer options to no avail (don't forget to reboot between attempts).
You will need to reinstall/sideload FireOS (same version that was on your device before installing CM 12.1) from stock recovery and start again. Be sure to keep device off WiFi except when running KingRoot; otherwise Amazon will push an OTA update that will block root and any hope of running a custom ROM.
Click to expand...
Click to collapse
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?

Unversed said:
Is there a way to see what version of fireOS I had ? I installed CM12 a long Time ago.
Do I really need to install the same version ?
Click to expand...
Click to collapse
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?

Davey126 said:
If you go too low your device will brick. If uncertain sideload FireOS 5.3.1 which is the highest rootable build at present. You can find links in the index thread.
Do you recall using TWRP or FlashFire to install CM?
Click to expand...
Click to collapse
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it

Unversed said:
I used flashfire. I have the stock recovery so no twrp
I guess this means installing stock firmware version 5.3.1.0 via sideload will work
I will try it
Click to expand...
Click to collapse
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.

Unversed said:
doesn't work. this is what I get:
loading: 'update-kindle-global-37.5.5.2_user_552153420.bin'
error: insufficient permissions for device.
See [http://developer.android.com/tools/device.html] for more information.
Click to expand...
Click to collapse
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.

Davey126 said:
Reboot both devices then follow instructions in this thread. Be sure to use the 5.3.1 bin, not the older one referenced in the video.
Click to expand...
Click to collapse
ok my problem solved after sidloading with my windows partition
thanks for the huge help

Kindle Fire 7" (9th Gen, 2019) Any way to install Lineage OS to it?

Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.

Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329

Michajin said:
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
once you are unlocked you will have freedom, post questions in the threat, or post back here and i will help. 14.1 LOS for mustang is solid after you are unlocked...
[ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Click to expand...
Click to collapse
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?

Reiixas said:
I appreciate the help, however my device out of the box has 6.3.1.4 OS and that method only works until 6.3.1.2. Anyway on how to downgrade it to where it needs to be?
Click to expand...
Click to collapse
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.

Michajin said:
The hardware unlock version should still work ( i am not sure how amazon could block it) The software version just gave you access to the bootrom without opening the tablet. Once you get into the bootrom you are golden to run the bootrom-step script which will give you a hacked fastboot, to allow you to flash TWRP recovery (fastboot-step script). Once in recovery you can flash LOS instead of fw.zip.
Click to expand...
Click to collapse
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?

Reiixas said:
I understand that. I'm trying to do the software version instead of opening it. In the software version I get stuck on step 4. and I get this prompt:
mustang:/ $ cd /data/local/tmp
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
So, I assume that the only way to do so is with the hardware version?
Click to expand...
Click to collapse
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.

Michajin said:
From Rapid Temporary Root for HD 8 & HD 10
https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595
Fire 7 9th gen (2019) (thanks @Michajin) -- up to Fire OS 6.3.1.2 build 0002517050244 only
Yes , the hardware way is the only way. Opening the tablet is easier than is sounds and shorting it fairly easy too, a wire or a piece of aluminum foil rolled up works well.
Click to expand...
Click to collapse
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?

Reiixas said:
Hello,
Thank you for your help. I managed to install TWRP and Lineage OS 14 with Gapps. However, I removed the micro sd card to change Gapps nano to pico and my device won't boot now and won't be recognized by adb. Did I make this kindle a paperweight?
Click to expand...
Click to collapse
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?

Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
Hello,
I managed to fix it. But I REALLY appreciate your help. You helped A LOT.
THANK YOU :victory:

How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks

brankota said:
How did you manage to downgrade and install it in the end? I am also stuck on 6.3.1.5 Nand getting
mtk-sumustang:/data/local/tmp $ ./mtk-su
Failed critical init step 4
This platform cannot be supported
How to downgrade to 6.3.1.2 or how to get past it on existing version? thanks
Click to expand...
Click to collapse
You need to do the hardware hack by opening the tablet.
Start here -
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/ama...grade-t3944365

Michajin said:
No, from a power off state you should be able to boot into recovery. I think it's volume up (possibly down) and power button. From there your can go back and flash it again or restore a backup... Are you boot looping? You can fix it. Might need to run the scripts again. But likely you can get into recovery to fix it.
---------- Post added at 10:13 PM ---------- Previous post was at 09:58 PM ----------
Are you looping in Amazon or los? Or just black screen?
Click to expand...
Click to collapse
OP says local video playback in LOS is still not supported. Is this still true?

thisisnotatest said:
OP says local video playback in LOS is still not supported. Is this still true?
Click to expand...
Click to collapse
Seems like it was all working. I haven't had it on in months. Make a back up flash it and test it. If you don't like it or it has many issues, restore the backup.

Reiixas said:
Hello all,
I currently just got a new Kindle Fire 7" 9th Gen. It's running Fire OS 6.3.1.4 Any way that it can be rooted easily and add Lineage OS to it? Or can someone help me out on going to the right thread?
Thanks in advance.
Click to expand...
Click to collapse
For everyone that has the fire tablet 7 gen 9 , aka mustang , if your tablet was made
in 2020 or later you won't be able to unlock , or flash it .
After 2019 and the first production run , they hardware locked this model tablet.
Starting in 2020 the fire tablet 7 gen 9 aka mustang was shipped with the
chip hardware locked and even opening it up to perform the bypass won't work.
They basically did a bait and switch at Amazon ,
Mid production run for this model they secretly changed the major
possibilities and functions that could be done on it .
Essentially you were buying an inferior unit with the same model number .
Personally I think Amazon should give millions of people their money back for
unethical and wrong business practices being used on its customers.
I talked to Amazon corporate offices and they said that their policy is that at any time
They can modify a current model unit and change its hardware features , all without
informing the customer that their current model being sold was now
with a hardware lock . just like in 2019 , people bought this model tablet , but by 2020
The same model tablet was redesigned secretly to now be fully hardware locked.
People who were unaware like me bought this model in 2020 , and yes it
unfortunately was made hardware locked , but people who bought the first
production run of them in 2019 were lucky enough to buy ones that were not made with any
Hardware lock .
There's different methods to see if your mustang model tablet is locked ,
Either way it all means one thing . your tablet will never be unlocked or flashed ,
At least not without specific engineering , and ROM flashers anyway.
Even then , good luck .
It don't look good .