Related
Downloadable Fire HD 6/7 2014 ROMs:
Lollipop 5.1 based
5.6.3.2 (latest, upgrade to it via TWRP)
https://fireos-tablet-src.s3.amazon...ss3/update-kindle-20.6.0.5_user_605485620.bin
5.6.0.1
https://kindle-fire-updates.s3.amaz...aC8/update-kindle-20.5.9.5_user_595550320.bin
5.6.0.0
https://fireos-tablet-src.s3.amazon...nab/update-kindle-20.5.9.5_user_595457320.bin
5.4.0.1
https://fireos-tablet-src.s3.amazon...Maw/update-kindle-20.5.7.9_user_579279320.bin
5.4.0.0
https://fireos-tablet-src.s3.amazon...ekw/update-kindle-20.5.7.9_user_579225620.bin
5.3.3.0
https://fireos-tablet-src.s3.amazon...7Ca/update-kindle-20.5.7.0_user_570208620.bin
5.3.1.1
https://fireos-tablet-src.s3.amazon...woE/update-kindle-20.5.5.4_user_554207020.bin
5.3.1
http://kindle-fire-updates.s3.amazo...t9p/update-kindle-20.5.5.2_user_552153420.bin
5.1.2.1
http://kindle-fire-updates.s3.amazo...Wt5/update-kindle-20.5.4.2_user_542169020.bin
5.1.2
http://kindle-fire-updates.s3.amazo...HBV/update-kindle-20.5.4.2_user_542168620.bin
5.1.1
http://kindle-fire-updates.s3.amazo...aZE/update-kindle-20.5.4.1_user_541113320.bin
5.0.1 (last 5.0.1 ?)
http://amzdigitaldownloads.edgesuit...kindle-full_ariel-20.5.2.2_user_522055720.bin
5.0.1 , Sept 2015, update-kindle-full_ariel-20.5.2.2_user_522053520.bin
https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
5.0.1
http://rootjunkysdl.com/files/Amazo...-devpreview_ariel-20.5.2.2_user_522041550.bin
5.0.0 - the original preview, could be Lollipop 5.0 based
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
KitKat based
4.5.1 (can root directly by Kingroot)
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.1_user_451004420.bin
4.5.2 (can root directly by Kingroot)
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.2_user_452004220.bin
4.5.3 (can root directly by Kingroot) - best version to root
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
4.5.4 v1 (no root directly, but can upgrade to this and keep root)
http://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006020.bin
4.5.4 v2 (no root directly, but can upgrade to this and keep root)
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
4.5.5 (no root directly, but can upgrade to this and keep root)
http://kindle-fire-updates.s3.amazo...13N/update-kindle-20.4.5.5_user_455001420.bin
4.5.5 v2 (no root directly, but can upgrade to this and keep root)
http://kindle-fire-updates.s3.amazo...2bo/update-kindle-20.4.5.5_user_455001820.bin
4.5.5.1 (no root directly, but can upgrade to this and keep root. Warning!!! 4.5.5.1 bootloaders will brick the device if one requests FireOS 5 after running 4.5.5.1 unrooted, however, can run this ROM with 4.5.3 bootloaders without issues)
http://kindle-fire-updates.s3.amazo...UUc/update-kindle-20.4.5.5_user_455002120.bin
For 4.5.5.1, follow the respective safe upgrade procedures via TWRP :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
bibikalka said:
Downloadable ROMs for reference :
. . .
4.5.5 (no root directly, but can upgrade to this and keep root)
http://kindle-fire-updates.s3.amazo...13N/update-kindle-20.4.5.5_user_455001420.bin
Click to expand...
Click to collapse
We don't have updater-script and modified bin for 4.5.5. I see 4.5.4 and 4.5.5 updater-scripts are identical, so presume we can use your edited 4.5.4 script and create 4.5.5 update.zip per instructions for 4.5.4: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
If this is correct I can create a 4.5.5 update zip and post if you don't have time. Let me know. Thanks!
EDIT: or maybe you want to change upgrade-to-4.5.4 to upgrade-to-4.5.5?
DoLooper said:
We don't have updater-script and modified bin for 4.5.5. I see 4.5.4 and 4.5.5 updater-scripts are identical, so presume we can use your edited 4.5.4 script and create 4.5.5 update.zip per instructions for 4.5.4: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
If this is correct I can create a 4.5.5 update zip and post if you don't have time. Let me know. Thanks!
EDIT: or maybe you want to change upgrade-to-4.5.4 to upgrade-to-4.5.5?
Click to expand...
Click to collapse
Ha-ha, very true! Now that I've tried 4.5.5, I've posted a simpler set of instructions where there is no need to mess with the update file at all (and the tweaks can be done post upgrade):
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
xd
Trouble after upgrade to 5.3.1.1
After upgrade to 5.3.1.1 I lost TWRP/GApps/Root. From what I can see, it wiped and did fresh install. I was able to get root back. I have installed TWRP manager which shows I still have TWRP still installed but I am unable to access it. any help or answers would be appreciated.
* I had 4.5.3 bootloader and was previously running 4.5.5.1
thanks for these. after holding on for what seems like ages for a fully working cm machine I've given up and gone back to fireOS & handed my hd6 to the girlfriend who's a keen paperwhite reader & her hp slate stopped playing fair with bbc iplayer & that's about all she's after - books & stuff that works in fireOS natively. so no desire for a nearly working device. I've had fun flashing, bricking & re-flashing but time moves on.
i'm grateful to have returned this often busted machine back to stock. god bless xda & all those who sail in her!
@bibikalka Can the latest Fire OS (which is version 5.6.0.1 not 5.6.3.2 like mentioned in thread) be updated with twrp and rooted?
[email protected] said:
@bibikalka Can the latest Fire OS (which is version 5.6.0.1 not 5.6.3.2 like mentioned in thread) be updated with twrp and rooted?
Click to expand...
Click to collapse
I downloaded it, changed the extension from .bin to .zip, flashed it, and then flashed SU to retain root. Restarted, took a long while, but it booted up with root just fine.
[EDIT Oct. 25] Here's what I did--cleaned up and corrected for bootloaders--to install the official 5.2.2 update (build date September, 2015) on myrooted tablet running Developers Preview, build date July, 2015.This is only for those who rooted and installed the dev preview before the upgrade/downgrade troubles. It let's you keep all your stuff.
Few important things:
If you don't reset/wipe in TWRP you can keep most of your stuff, including homescreen layout, play store and all apps. However . . .
Google framework, account manager, contact sync and calendar sync get deleted with the update.
I didn't flash Gapps and got bogus insufficient space error [130 Mb free] when I tried later. Restoring framework fixed everything, but it may be best to flash new Gapps (although that can cause problems when update doesn't completely wipe /system, like this one). Up to you.
Oct 26 Update: Based on reported "insufficient space" flashing Gapps--plus testing and researching contacts and calendar--I suggest not flashing Gapps but simply backing up Google services framework before you upgrade and restoring it after. The other google system apps that get deleted don't seem to be needed; if you want to sync Google contacts & calendar on the Fire you can add your google account(s) in Settings, same as on any Android. If you don't want Amazon's stock calendar or contacts, get another from the Play Store. I've updated the instructions to reflect this.
.
HDXposed module is no longer needed for working Play Store.
Xposed Framework: The update doesn't support the version we used with the July dev preview. You must either flash the latest version or flash the uninstaller if you don't want Xposed anymore.
Stock launcher now = com.amazon.firelauncher
Home key now defaults to stock launcher until you pm disable it. (No prompt anymore)
Backup Google Services Framework.
Turn off wifi (airplane mode) and plug in.
Download the zips:
* September 5.2.2 update (thanks @Hariiiii !) and rename extension from bin to zip.
update-kindle-full_ariel-20.5.2.2_user_522053520.bin: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
* Latest Xposed Installer or Uninstaller from here: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Installer = Xposed-v74-sdk22-arm-by-romracer-20150911.zip
Uninstaller = xposed-uninstaller-20150911-arm64.zip
* Gapps (if using)
tk_gapps-modular-pico-5.1.1-20150920-signed.zip: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
* 5.2.0_stock_recovery_only.zip
Attached to bibikalka's lollipop post: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Get latest SuperSU apk (?) Don't know if it's required, but I installed it.
- SuperSU 2.52 Beta: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
Follow Step 1 of @bibikalka's guide to temporarily install TWRP and while in TWRP:
a. Flash the update
b. Flash Xposed (installer or uninstaller)
c. Flash 5.2.0_stock_recovery_only.zip
d. Choose boot to recovery and install SuperSU when TWRP prompts you.
Confirm you're in recovery, then boot to system and press Exit at "Welcome to Fire OS 5!"
In OS, see if SuperSU is still managing root access. If it's not or you want to update, install the new SuperSU apk and update binaries.
(Wait to reboot unless you can't get su access at next step.)
Block OTA:
a. Disable dcp or otaverifier (whichever you prefer)
b. Rename system/priv-app/devicesoftwareota/devicesoftwareota.apk extension to apk_
Restore Google Services Framework and reboot.
Turn on wifi and sign in to playstore.
Thanks for the guide!
deleted
putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
As far as I understand from my experience of going from unrooted september 5.2.2 to rooted 4.5.3 to rooted september 5.2.2, it should work fine if you go via that route.
putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
This is only for rooted tablets. Follow the steps Hariiiii describes here. There are guides for what he did.
[How To] Upgrade Rooted Developers Preview to Official 5.2.2 Release
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
I order a replacement. What i have to do to have fire os 5 final with root, play store and other launcher?
Thanks
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Could we possibly get a video tutorial on how to do this?
(May be easier for some.)
Ooh, I don't do video and doubt anyone will for this, but that would be kind. You can pm me with questions.
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
bibikalka said:
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Hdxposed is not necessary
cm11noob10 said:
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Click to expand...
Click to collapse
Think we have some confusion. I'll need to make this clearer: This guide is only for people who already have the rooted developer preview--people who did the downgrade/upgrade using the July build. There is no longer a way to use the developer preview to gain root; the latest version (September) ends up causing bricks, as you learned the hard way. Fortunately, it looks like the official 5.2.2 update that Amazon is now OTA distributing can be successfully used in the downgrade/upgrade operation. I'm sure guides for that will be out soon.
Then I'll look for a guide on that and go from there.
Thx for the replies.
bibikalka said:
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Good feedback, thanks. HDXposed is indeed not needed, which of course means Xposed isn't required. If you don't install the new Xposed, though, I suspect the old, non-working one will stay on system even with factory reset. Your thoughts?
(Edit: NVM. Yes, they'll still have old Xposed, so will need new.)
Yeah, Gapps <sigh> It's such a personal thing. (Thinking about how to handle.)
DoLooper said:
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Click to expand...
Click to collapse
But my first time i update and i didn't flash 5.2.0 recovery and work perfectly and i haved root. This mean that it isn't necessary flash 5.2.0 recovery?
Enviado desde mi SM-N910F mediante Tapatalk
davigar said:
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
Click to expand...
Click to collapse
I'm looking into this again. When you flashed "5.2.0 recovery" which zip did you use, 5.2.0_stock_recovery_only.zip or 5.2.0_stock_recovery_uboot.zip? Thanks.
I flashed 5.2.0_stock_recovery_uboot.zip
davigar, you got the developer preview in order to downgrade to OS 4.5.3 and root, is that right? If not, what OS were you on and how did you install it?
EDIT: @davigar Wait a minute--did you not root? Did you just use this tutorial to install the update and that's when you forgot recovery? This will make a difference. Thanks.
I upgrade my kindle to developer preview then i downgrade to 4.5.3, root and upgrade it to 5.2.2 developer with gapps. I followed the newbie friendly tutorial when i bought it. Sorry for my english [emoji16]
Enviado desde mi SM-N910F mediante Tapatalk
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Edit: see following post by @zippy411. Appears a rollback to FireOS 5.3.1 (rootable) is viable.
Davey126 said:
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Click to expand...
Click to collapse
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
great news that we can downgrade without issue.
P.S: Maybe my HD 10 5.3.1.0 will never see the light of getting root as Fire 7" as Amazon is pushing another update already
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Orbiting234 said:
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Click to expand...
Click to collapse
Quite likely you can retain 5.0.1 bootloader while 'upgrading' to FireOS 5.4.x (when released) using the time proven procedure in this thread yielding the best of both worlds. Backup your existing CM install in TWRP so you can revert back after grabbing the Alexa components. You could do the same with the FireOS build and toggle between the two (awkwardly) via TWRP backup/restore. Can do the same thing with recent FlashFire builds although I would always retain a true nandroid (ie: twrp backup) of CM as a fallback.
zippy411 said:
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
Click to expand...
Click to collapse
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
ManWithCamera said:
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
Click to expand...
Click to collapse
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Apart of the NEW Alexa, does anyone here has noticed something NEW or any improvements with the latest FireOS 5.3.2 update?
Can we root it after the update with dirty cow?
just4u32 said:
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Click to expand...
Click to collapse
Hi - this forum is for 5th gen Fire (released fall 2015); you'll want to ask you question here. While 5th and 6th gen devices often run similar builds of FireOS there are some differences attributable to hardware variations and software release cycles. What works on one type of device may or may not on others. Rollbacks can be especially dangerous as bootloaders/kernels generally differ across device types. A failed rollback attempt typically yields a bricked device with no recovery options. In short, I would not generalize across device types.
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
To my knowledge there is no indication Dirty Cow has any meaningful relevance on this device. Although the underlying vulnerability may exist there is no evidence it has been successfully exploited on FireOS.
OK I thanks
Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
5.3.2 > 5.3.1 downgrade IS possible
Good Afternoon,
I recent purchased a Kindle Fire 7 (11/11/16) and it was upgraded to 5.3.2. I was able to downgrade the OS to 5.3.1 using the ADB sideload method and then root using Kingroot (11/18/16). Be sure to block OTA updates once completed. Have not seen any issues yet and will report if i do.
Good Luck everyone.
ManWithCamera said:
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
Click to expand...
Click to collapse
Thanks
Tried to disable lockscreen ads using adb (com.amazon.kindle.kso), but when I touch the special offers icon on lockscreen, I get a window that says Selected Offers. Is there another package that I should be disabling? I'm on Fire OS 5.3.2.
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Onlye root, not recovery modded or other rom.
Thanks
p.s.: not use slang with me, thanks
Palux said:
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Click to expand...
Click to collapse
Yes - 5.3.1 can be reloaded again if pure stock is desired. However, this is not generally required for warranty exchanges (the only type of hardware assistance Amazon provides) as they do not perform a detailed inspection of returned devices.
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
br
Arret said:
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
Click to expand...
Click to collapse
Something went wrong; the Amazon Logo should display for <30 sec. You will need to reload FireOS 5.3.1 from the stock recovery menu and start over. Guidance here, here. Once recovered post back for further assistance loading CM 12.1.
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.
Ahhh... so it somehow got locked back and need to redo the procedure?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?
treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????
As title, do we have any way to root it with magisk yet?
I'm wondering myself. I tried to root with "magisk_shieldtvpie_r2.zip and although it seemed to have installed, after restarting I still didn't have root
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
dovedescent7 said:
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
Click to expand...
Click to collapse
u might want to check before anything.. i got the 2019 pro dev os firmware and it was actually just regular firmware lol
but i rooted with latest magisk.. not sure y anyone would have issues rooting
tha kid2012 said:
I'm wondering myself. I tried to root with "magisk_shieldtvpie_r2.zip and although it seemed to have installed, after restarting I still didn't have root
Click to expand...
Click to collapse
i just fastboot boot twrp then flashed latest magisk on my 2019 pro 8.2.0
Maybe I'm doing it wrong, haven't flashed anything in a while and the place I use to get step by step guides from (nvidiashieldzone) shut down. Mind telling me the steps that you used to root?
tha kid2012 said:
Maybe I'm doing it wrong, haven't flashed anything in a while and the place I use to get step by step guides from (nvidiashieldzone) shut down. Mind telling me the steps that you used to root?
Click to expand...
Click to collapse
just check the twrp thread or the many other root threads
elliwigy said:
u might want to check before anything.. i got the 2019 pro dev os firmware and it was actually just regular firmware lol
but i rooted with latest magisk.. not sure y anyone would have issues rooting
Click to expand...
Click to collapse
Did you lose Dolby vision and got Netflix issues when rooting with the dev os image on the Nvidia Shield 2019?
I'm installed the magisk but bootloop in nvidia logo, I have 2017 with 8.2 developers firmware so I can get root privileges any help?
baba702 said:
I'm installed the magisk but bootloop in nvidia logo, I have 2017 with 8.2 developers firmware so I can get root privileges any help?
Click to expand...
Click to collapse
I successfully root on normal firmware 8.2.0 with the lastest magisk. I dont know about the developer firmware.
1. I disable all magisk modules and restart
2. Boot to fastboot mode
3. Download and extract the firmware .
4. Run flash all.bat to flash the 8.2.0 firmware
5. Reboot after complete(let the shield completely boot up)
6. Use magisk manager which previously installed to patch the boot.img
7. Reboot shield to fastboot mode and flash the patched boot.img
8. Rebbot
9. Now i enable modules.
question to you guys who have rooted.
Did you get AFwall+ to work?
I have both 2017 Pro model shield and 2019 Pro model. I would like to root so I can uninstall all the crap, and then install AFwall+ firewall and just enable outgoing twitch, spotify, youtube, and some small services I use..
elliwigy said:
just check the twrp thread or the many other root threads
Click to expand...
Click to collapse
rogeriskira said:
Did you lose Dolby vision and got Netflix issues when rooting with the dev os image on the Nvidia Shield 2019?
Click to expand...
Click to collapse
Also curious.. Did you loose any of these functionalities when using dev image and rooting .. ?
I had developer image 8.2.0 installed on the Nvidia 2017 16gb, updated via Ota to latest 8.2.2 but lose root, how do I root again? Thanks
Has anyone found a way to root 8.2.2 yet?
dovedescent7 said:
I know you said you wanted magisk but have you tried the Nvidia Sheild developer only OS images?
Those come with included root.
https://developer.nvidia.com/shield-developer-os-images
My problem is I don't know if I can update my developer only OS image 8.1 to 8.2 without losing all my apps. I left the bootloader unlocked. Wondering why I couldn't simply flash developer os 8.2 over 8.1 if bootloader is unlocked?
Click to expand...
Click to collapse
flash develop rom
tinhsoftware said:
I successfully root on normal firmware 8.2.0 with the lastest magisk. I dont know about the developer firmware.
1. I disable all magisk modules and restart
2. Boot to fastboot mode
3. Download and extract the firmware .
4. Run flash all.bat to flash the 8.2.0 firmware
5. Reboot after complete(let the shield completely boot up)
6. Use magisk manager which previously installed to patch the boot.img
7. Reboot shield to fastboot mode and flash the patched boot.img
8. Rebbot
9. Now i enable modules.
Click to expand...
Click to collapse
I just got Shield the other day and it came with 8.2. Would flashing with rooted firmware wipe it clean? Same for just rooting it?