Related
*************************************************************
INCORRECT USE OF THESE FILES WILL BRICK YOUR DEVICE
PLEASE ENSURE YOU KNOW WHAT YOU ARE DOING AND
I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG
*************************************************************
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
- Do NOT use these images to downgrade or upgrade your base firmware.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0 <- Flashable on Safestrap 3.7.2
- 13.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 13.4.5.2 <- Flashable on Safestrap v4.0.1
Apollo Images:
- 14.3.1.0 <- Flashable on Safestrap 3.7.2
- 14.3.2.6 <- Flashable on Safestrap 3.7.5
*** THESE ONES DO NOT HAVE ROOT OR BLOCK UPDATES ***
- 14.3.2.8 <- Flashable on Safestrap v3.7.5
- 14.4.5.2 <- Flashable on Safestrap v4.0.1
If you want to re-enable over the air updates then do the following:
- Skip this if you are using the 4.5.2 files - As stated above this does not apply so be careful.
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
ggow said:
Hi All,
Here you can find stock firmware for both thor and apollo devices which are safestrap flashable.
Please note the following:
- These updates do NOT flash a new kernel or recovery - only a new /system image
- Before flashing ensure you know which stock base/kernel/safestrap you have installed and choose the appropriate version for that stock base/kernel.
I will be uploading them as and when I have time.
Thor Images:
- 13.3.1.0
Apollo Images:
- 14.3.1.0
If you want to re-enable over the air updates then do the following:
- rename /system/etc/security/otacert.old to otacert.zip
- rename /system/app/com.amazon.dcp.old to com.amazon.dcp.apk
Click to expand...
Click to collapse
Excellent! I am able to revert back to this stock firmware after nearly bricking my device. Thank you!!
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
D0ubl3_X said:
Will you make a pre rooted 4.5.1 image for the HDX 7.0 Thor?
Can I flash this over a Stock 4.5.1 device?
Click to expand...
Click to collapse
As of right now, it's impossible to root 4.5.1.
No, you can't flash them over a newer version just like that. If you want to downgrade, check this thread.
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_, yes I'll sort one out for you.
ggow
I goofed - flashed the apollo zip over my already properly up(down)graded stock. Now of course I get a blank screen when trying to boot the stock - not that I do it that often of course. I can still get into safestrap and boot the nexus 2.01 rom with no issues so am okay for now. Would I need something like a rooted 14.3.2.6 to fix this?
aren't these roms very old? Is there any way to get the latest AMAZON STOCK apps AND keep root? I really like the FIRE OS (way more than stock Android) but I also want all apps etc.
_Alex_ said:
Since I"m heavily tied into the Amazon ecosystem and have other Kindle devices, installing HDX Nexus 2.01 didn't work for me.
However, thanks to @ggow, using the same upgrade guide, Iwas able to get my 3.1.0 to 3.2.6, allowing my fire hdx devices to finally be able to do screen sharing with my fire TVs! I did have to restore /data, enable xposed + hdxposed, re-install kindlefree + Google play store APKs & stucks wallpaper fix to be back at 100%...
Click to expand...
Click to collapse
Was screen sharing to Fire TV not available on 13.3.2.3.2? Furthermore, what exactly does 13.3.2.6 offer that's new/improved? Does anyone have the changelog for this?
OK, so the LATEST FIRE OS Version that is rootable is "13.3.2.6" for the THOR device, is that correct? Or is there any other way to root a newer OS Version?ยด
Oh, and how can I flash this update? My device is rooted, but I have a very old OS Version on my kindle hdx.
Hey guys.. I screwed up.
I have a fire hdx Apollo that had been properly up(down)graded and running fine with 2.01. For some reason (and my lack of understanding the correct versions of things) I thought it would be a good idea to install the Apollo update on my stock rom. This of course has now caused boot loops on my stock boot but not my 2.01 boot.
Would love to be able to restore the stock as I do use some of the fire's capabilities from time to time. Sadly I did not do a backup before the update (kicks self furiously).
I DO have a backup from before the upgrade/downgrade so maybe I could restore that then push through the upgrade steps again or something. I'm worried that I will bork my safestrap or do something worse based on my proclivity for damage and chaos.
E.
_Alex_ said:
Hey @ggow, would it be possible for you to release a rooted 14.3.2.6?
Click to expand...
Click to collapse
Hi _Alex_,
Sorry about the long wait, I have posted a zip for 14.3.2.6. See OP.
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
NextDroid said:
Hey @ggow,
Thanks for your hard work. Could you possibly make an image for 13.3.2.4 (Thor)? It would be nice to have along with Nexus HDX 2.0.2.
Click to expand...
Click to collapse
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Looks like we're going to need it with the new bootloader bypass!
Just to clarify because someone asked, users of the HDX Nexus ROM would need it to downgrade to a firmware that the unlock works on.
ggow said:
Yes, I'll sort one out for you. Let you know when its up.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Sent from my device
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
aquaphun said:
recreated the error with the Symlink. Crossposting from the TWRP Thor thread
Wiped system manually
The error log is:
Code:
Wiping system...
Symlinking...
symlink: some symlinks failed
[COLOR="Red"]E: Error executing updater binary in zip '/sdcard/TWRP13.3.1.0.zip'[/COLOR]
Error flashing zip '/sdcard/TWRP13.3.1.0.zip'
Updating partition details
Interesting... Getting the same error when I try to flash the original HDX 13.3.2.3 firmware, after I renamed it from .bin to .zip
Click to expand...
Click to collapse
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Cpasjuste said:
Hi @ggow !
I made a flashable zip of the 4.5.2 update for Thor which is compatible with the signing exploit (bootloader/fw flashing removed and modified bootimage with happened dt) as there was some demand.
I'm not sure i should again create a thread for this rom(s) as we may be easily lost. Maybe all our "stock/modified stocks" roms should be in the same thread. What do you think about this ? Here is the link in case : http://android.mydedibox.fr/hdx/update-kindle-13.4.5.2_user_452004120-twrp.zip
Note that i only renamed "otacert.zip" to "otacert.old" on this rom as the "dcp" apk name has changed and i don't remember how i fixed that ... so ota updates may still be enabled isnt it ?
---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------
I don't know if it's the problem but the appolo recovery is based on an older kernel (3.1.0?) which doesn't have full selinux support. This prevented some zip to be properly flashed (at least on thor) until i use the 4.5.2 kernel sources. Unfortunately we will have to wait for @ggow to receive his new device, in the hope of an exploitable one (but this may be a different problem)
Edit : oups, you are on thor so it's not the problem !
Click to expand...
Click to collapse
Hi @Cpasjuste,
Yes that's fine, I'll put your 4.5.2 image up on the same thread - no point replicating things
On 4.5.2 I wasn't sure which services needed to be disabled to prevent OTA. I'll add a note for this file to warn people to be careful when using it.
DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.
I'm running v8.4 on the Blu r1 hd 16gig and received the 8.5 updated last night but it wouldn't install and is telling me the reason is because my phone doesn't support FOTA, so Is there a work around or could I just find the file and manually install it. Also I'm rooted and using solid explorer, much appreciated if anyone could help.:fingers-crossed:
Trailblaza said:
I'm running v8.4 on the Blu r1 hd 16gig and received the 8.5 updated last night but it wouldn't install and is telling me the reason is because my phone doesn't support FOTA, so Is there a work around or could I just find the file and manually install it. Also I'm rooted and using solid explorer, much appreciated if anyone could help.:fingers-crossed:
Click to expand...
Click to collapse
OTA update does not install when rooted.
Update file gets erased after attempted to install.
Location has been /data/data/adopusfota (very similar name)
Update has been patchd and "safe" twrp install posted.
Already in rom section
I've managed to get the file but not sure what to do with me now.
Trailblaza said:
I've managed to get the file but not sure what to do with me now.
Click to expand...
Click to collapse
You'll need to boot into TWRP recovery mode and do the Install from there.
see
HTML:
https://www.xda-developers.com/how-to-install-custom-rom-android/
you can chain install zip files as you'll probably need to reinstall SuperSu and Xposed framework if you use those.
I did similar on my two R1 HDs last night.
/data/data/com.adups.fota
Hey
I have a tablet that I would like to install magisk on.
However I am not able to find the issues tab over on github so I can submit a copy of my tablets bootloader so it can be added.
Any help would be most appreciated!
Thanks!
Yeah... No.
The bootloader doesn't have anything to do with Magisk. You're thinking of the boot image. Two different things.
And by your post I assume you've tried installing Magisk and it failed. Correct? Any error messages? What about a recovery log or similar?
Sorry I have the terms confused, I also deal with Homebrew for Nintendo consoles.
Yes the error was of the installer not being able to extract the boot image.
A couple of different things to try:
Try installing v14.5 beta, if you haven't already.
Patch the boot image with the Manager and flash it to your device manually. Instructions in the release thread.
If nothing works, make sure to provide logs (recovery log, etc) and details about your device.
Alright thanks I will try to reply back when I get to it.
Hi again I did try to install magisk 14.5 and it failed though I did copy the log this time, though I also told it to copy the kernel log as well so their might be a little too much information.
[url]https://docs.google.com/document/d/1Cyq7Ofk4Dmq-SVlUhHKTU-hb04cSYTxDnIoaHgA5xuA/edit?usp=drivesdk[/URL]
Edit: P.S. It is a Barnes & Noble Nook HD tablet running AOSP 7.1 Nougat Android
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 .