Database Users

Thor & 4.5.5.2 : Easy to root and Unlock Bootloader

Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
Click to expand...
Click to collapse

just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working

BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?

BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.

kkcheong said:
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
Click to expand...
Click to collapse
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
are those instructions as daunting as they sound?
it seems if you kingroot and wipe everything it negates any malware?

barrist said:
...it seems if you kingroot and wipe everything it negates any malware?
Click to expand...
Click to collapse
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Davey126 said:
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
Click to expand...
Click to collapse
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?

barrist said:
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
Click to expand...
Click to collapse
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.

Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi

draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:

nice, instructions worked, running lineage 14.1 and no problems so far!

kkcheong said:
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
Click to expand...
Click to collapse
No problem.
Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),
you should be fine with KingRoot, it just takes much longer, but that's your choice.
The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.

kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?

xyluss0 said:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
Click to expand...
Click to collapse
Have you put both file in the adb directory?

Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".

xyluss0 said:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
Click to expand...
Click to collapse
Please print screen. Did you cd to ADB directory?

Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub

Root fails
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?

achimbub said:
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Click to expand...
Click to collapse
- TowelRoot is ineffective on FireOS v4
- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)
- device does not need an active internet connection with desktop version
---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------
bobcat131 said:
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
Click to expand...
Click to collapse
KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.

[2017] Root Kindle Fire HD 6 4th gen tutorial

Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below

I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!

Could I keep root without updating to 5.4?
---------- Post added at 06:42 AM ---------- Previous post was at 06:26 AM ----------
Also Kingroot fails. Was the exploit is uses patched?

Bricked Device(unbricked it with DoLooper tutorial) improvising,Step 9 says sideload JMZ Tools how do you do that without connection? only way i can think is es explorer which you have to have connection to install

Any news on this? Thinking of attempting

I attempted this to downgrade from rooted 5.12 to 4.53 so that I could install twrp and get to the latest load.
I am stuck on step 8. After I flashed 4.5.3 and wiped, I attempted to sideload kingroot and the jmz utility but they did not install. I imagined that it failed because they are from unknown sources and that setting is disabled once 4.5.3 is loaded. So I rebooted with wifi off, attempted to adb reboot recovery, and I got to a recovery menu with 2 options, none of which are adb sideload.
How can I proceed? If I enable wifi to download kingroot, it will attempt to update, correct?
EDIT - I enabled wifi to download kingroot apk since I can't sideload it, and surely enough an update to 4.5.5 downloaded. Damn.
RE-EDIT--I just caught my initial mistake. I used the command adb sideload for kingroot and jmz instead of adb install. Another damn. I am downloading kingroot and rooting while the update to 4.5.5 awaits installation, which I won't do.

It boot me into kids edition...?

jcarcinogen said:
I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!
Click to expand...
Click to collapse
Glad to hear! I have had a blast with a rooted kindle, including installing google and using root required apps.

demoncamber said:
Any news on this? Thinking of attempting
Click to expand...
Click to collapse
It worked great for me, considering that that the tablet cost me $60 brand new I took the risk. It is up to you whether this is something that you want.

I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?

Will this work for my hd 7 4th gen running fire os 5.6.0.1?
@marathonjon
@RobbotCC
@jcarcinogen
Please I really want to get root to install a android rom or cyanagen mod.

RobbotCC said:
Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below
Click to expand...
Click to collapse
Does this work on the Fire OS 5.6.0.1 that was sent out this year?

Provided said:
I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?
Click to expand...
Click to collapse
IDK, it has been awhile since I ran this and I have not stayed up to date on the latest firmware. As always you can try it at your own risk and post any questions here. I will do my best to answer.
I do not recommend trying this if you rely on the tablet for anything, things can go wrong and you could lose everything including the tablet.
Have Fun!

On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
edit: found a link (https://forum.xda-developers.com/hd8-hd10/general/fire-hd-8-2017-downgrade-to-5-4-0-0-5-6-t3719639) but it's for FIre HD 8. Will that work or does it need to be specifically for the HD 6?
edit2: nevermind, didn't look hard enough, found it here https://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102

liebherk said:
On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
Click to expand...
Click to collapse
Yes, that is the latest version that is still root-able I believe.

Still works with update 5.6.1.0
Still works thanks alot!

Yup, worked for me as well. Thanks @RobbotCC from another CMH kindle newbie

Stuck on step #13
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.

LeoDaQ said:
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.

Provided said:
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.
Click to expand...
Click to collapse
did you use the same files in the first thread? for hd 7 ? or should we download specific downgrade file?

TWRP not working anymore on Shield (2015) Version 7.2.1?

Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.

You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.

I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?

Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot

Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.

Downgrade from stock 8.0 to stock 7.2.3 + disable/block shield upgrade + notification

upgraded by mistake of a finger from 7.2.3 to 8.0
Is it possible to downgrade?
IF so, do I unlock bootloader and then just flash the 7.2.3 dev image from the nvidia shield site? To flash the 7.2.3 image do i do flashall.bat with the dev 7.2.3 image from the shield site?

If you unlocked the bootloader alrady so you dont need to do that again just flash the 7.2.3 the normal one not dev and do the factory reset after that do the root

So I did end up locking bootloader by error actually - my question now is whether after I unlock bootloader I should do flashall.bat or follow the command order from nvidia site itself to install stock 7.2.3 image which is:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
also i read something about needing userdata and to install that too? Is that necessary, or is essentially flashing stock recovery 7.2.3 over stock recovery 8.0 sufficient?

Like i told u flash the stock 7.2.3 over the new one when you finsh just do a factory reset and after that do the root it not need to any new instruction or new things

disable future updates?
one last question - anyway to disable system upgrade app to prevent automatic update installation? Tried titanium but it needs pro to disable and cant get that on my shield...no ton app store

There is an option in the settings somewhere to disable automatic updates

TAM1m said:
There is an option in the settings somewhere to disable automatic updates
Click to expand...
Click to collapse
automatic upgrades yes in settings, but it takes one wrong click with the invasive way the update comes each time to press UPDATE, if you catch my drift..
if there was a way to disable the system upgrade app in settings...right now clearing data works but has to be done each time you boot...

Laney88 said:
automatic upgrades yes in settings, but it takes one wrong click with the invasive way the update comes each time to press UPDATE, if you catch my drift..
if there was a way to disable the system upgrade app in settings...right now clearing data works but has to be done each time you boot...
Click to expand...
Click to collapse
Try if this works
Code:
pm disable-user -k --user 0 com.nvidia.ota
This should disable the ota app. You can reenable it at any time

TAM1m said:
Try if this works
Code:
pm disable-user -k --user 0 com.nvidia.ota
This should disable the ota app. You can reenable it at any time
Click to expand...
Click to collapse
is this how i should run that? From the usb debug on my CMD Prompt? adb shell pm disable-user -k --user 0 com.nvidia.ota
because when I do this is what i get: Error: java.lang.IllegalArgumentException: Unknown package: --user

Laney88 said:
is this how i should run that? From the usb debug on my CMD Prompt? adb shell pm disable-user -k --user 0 com.nvidia.ota
because when I do this is what i get: Error: java.lang.IllegalArgumentException: Unknown package: --user
Click to expand...
Click to collapse
I can't test it myself right now. Maybe try this instead
Code:
adb shell pm disable com.nvidia.ota
and if you already downloaded the ota, you can also clear the appdata before disabling
Code:
adb shell pm clear com.nvidia.ota

TAM1m said:
I can't test it myself right now. Maybe try this instead
Code:
adb shell pm disable com.nvidia.ota
and if you already downloaded the ota, you can also clear the appdata before disabling
Code:
adb shell pm clear com.nvidia.ota
Click to expand...
Click to collapse
I want to send you a large THANK YOU.
when i cleared the data it said success
when i tried the disable command it said disabled ! Thanks!

Disable nvidia shield update and notification succesfully!
Laney88 said:
I want to send you a large THANK YOU.
when i cleared the data it said success
when i tried the disable command it said disabled ! Thanks!
Click to expand...
Click to collapse
Furthermore, upon reboot no more notification no thing. This is the best thing - I searched the net and could not find. I wonder how to make it more available to others. But thank you @TAM1m and @rorm2010
Others: run this
adb shell pm clear com.nvidia.ota
Then this:
adb shell pm disable com.nvidia.ota
Thanks @Zeljko1234 for correction

Second command is the same as the first one
Should be: adb shell pm disable com.nvidia.ota
Sent from my CMR-W09 using Tapatalk

For anyone doing this from a PC and getting a shell error "Shell cannot change component state for com.nvidia.ota/null to 2"
You will need to send the command in the root shell.
Code:
adb shell "su -c 'pm disable com.nvidia.ota'"
P.S.: If you haven't authorized your computer to have root privileges in Magisk, you should get a pop-up on the Shield asking to grant permissions.

Problems with upgrade to 8.0.1 and with Netflix
Hi!
a couple of weeks ago I have disabled auto update follwing the procedure described in this thread, i.e., in SSH:
adb shell pm clear com.nvidia.ota
adb shell pm disable com.nvidia.ota
Since Monday, Netflix is not working anymore (Error UI-800-3) and according to their service, this is because Netflix doesn't work anymore on version 8.0.0 of the shield. I have tried to re-allow upgrade with
adb shell pm enable com.nvidia.ota (response of shield: "Package com.nvidia.ota new state: enabled"). I can find the 8.0.1 upgrade, and start installing it. It saks for reboot and upoon reboot, installation displays to continue...2%, 20% progress, then the shield reboots, but upgrade isn't installed, the shield is still on 8.0.0 and netflix keeps throwing the UI-800-3 error. My shield is rooted with magisk.
Can somebody help me getting the upgrade done? Or is there another approach to make netflix working again?
Thanks in advance!

ai5g said:
Hi!
a couple of weeks ago I have disabled auto update follwing the procedure described in this thread, i.e., in SSH:
adb shell pm clear com.nvidia.ota
adb shell pm disable com.nvidia.ota
Since Monday, Netflix is not working anymore (Error UI-800-3) and according to their service, this is because Netflix doesn't work anymore on version 8.0.0 of the shield. I have tried to re-allow upgrade with
adb shell pm enable com.nvidia.ota (response of shield: "Package com.nvidia.ota new state: enabled"). I can find the 8.0.1 upgrade, and start installing it. It saks for reboot and upoon reboot, installation displays to continue...2%, 20% progress, then the shield reboots, but upgrade isn't installed, the shield is still on 8.0.0 and netflix keeps throwing the UI-800-3 error. My shield is rooted with magisk.
Can somebody help me getting the upgrade done? Or is there another approach to make netflix working again?
Thanks in advance!
Click to expand...
Click to collapse
go to settings - about - system upgrade and delete data/cache.
After that enable developer options, then go down to the bottom of developer options and enable the setting that downloads the full image for an OTA.

mLgz0rn said:
go to settings - about - system upgrade and delete data/cache.
After that enable developer options, then go down to the bottom of developer options and enable the setting that downloads the full image for an OTA.
Click to expand...
Click to collapse
Thanks for your answer. The first part, "delete data/cache" doesn't exist in the system upgrade section of my shield, the only options are "search for update", "automatic update" and "time for update" (I have a German interface, so the actual wording in the english UI might be different). I found the "download full image section" and activated it, then I went back to "search for update", but here the shield finds the same 145 MB update file as before. Installation still fails.
EDIT: However, after rebooting, this time the shield displays "update to 8.0.1 will be performed at 2:00", and under details I could start the update again. This time, the update worked, the shield gets updated to 8.0.1 and Netflix is working again.
Thanks mLgz0rn, and my best wishes to Denmark!

downgrade stock 8.0 a stock 7.2.3
How can I make donwgrader for shield tv 2015 8.0.2 to 7.2.3? I have unlocked the bootloader which is on version 32.2019 when I do donwgrader stuck on nvidia logo. I think the reason it won't let me downgrade is because the bootloader doesn't downgrade.

El ccyd said:
How can I make donwgrader for shield tv 2015 8.0.2 to 7.2.3? I have unlocked the bootloader which is on version 32.2019 when I do donwgrader stuck on nvidia logo. I think the reason it won't let me downgrade is because the bootloader doesn't downgrade.
Click to expand...
Click to collapse
posting here, as i have the EXACT SAME ISSUE.
have a 2015 shield tv (non-pro) that was made in 2016. ( lol ) ( the internal board has a date stamp of 2016 )
i have tried multiple firmware's and they all flash, but wont work.
If i flash anything 8.0 and up , it works fine. my shield TV lost the micro-SD slot with 8.0 firmware. tried everything to get it back. All firmware's 8.0 and up , the micro-SD slot is worthless. (not sure if its just my device or others have this issue)
may i ask for anyone's help in getting the boot-loader rolled back ?
(is the android 8.0 anti roll-back feature the reason for my troubles, even with an unlocked device?)

how to root 11.0.7.7.IN11AA

Hi,
I just bought 8 pro and couldnt find a thread on how to root 11.0.7.7 and unlock the bootloader.
Could someone please guide me.
thanks

issuewith4ghelp said:
Hi,
I just bought 8 pro and couldnt find a thread on how to root 11.0.7.7 and unlock the bootloader.
Could someone please guide me.
thanks
Click to expand...
Click to collapse
To unlock bootloader here are the steps:-
1. Enable Developer options by going to settings-About Phone and then keep tapping build number until a dialogue comes saying developer options are enabled/unlocked/on.
2. Go to Developer options by :-
Settings-system-Developer options.
3. Enable OEM Unlocking.
4. Enable USB debugging.
5. Now be on ur PC.
6. Install latest adb and fastboot drivers. (U can install these):-
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
7. Make a adb folder in local disk of ur PC and paste the fastboot drivers there.
8. Reboot ur OP8T to bootloader after shutting down ur phone by holding power button+ both the volume buttons.
9. Open command prompt in ur PC and connect ur OP8T to ur PC via a USB cable and enter fastboot.
10. Enter:-
fastboot devices
11.After that Enter:-
fastboot flashing unlock
12. Enjoy! Ur bootloader is unlocked.
Steps to root without patching boot image on OOS/Custom ROMs:-
1. Unlock your bootloader.
2. Download LOS recovery from from lineage os homepage
3. Transfer LOS recovery file to your PC and reboot to bootloader.
4. Connect your phone to your PC and open cmd and do this command:-
fastboot flash recovery <filename>.img
5. Reboot to recovery.
6. Click on Apply update.
7. Click on Apply via ADB.
8. Now on ur PC download magisk apk and rename it to magisk.zip, open cmd and do this command:-
adb start-server
9. Open cmd and do this command:-
adb sideload magisk.zip
A prompt saying "Signature Verification Failed, Do you want to install" will show on your phone, click Yes and wait for the installation to complete (It'll show installation complete status 0 on your phone)
10. Reboot to System.
11. Download magisk apk on phone and install it and click ok on the magisk prompt (Your phone will reboot).
12. Voila! Your device is successfully rooted

Thanks worked! any ways to enable to "xray" camera back?

issuewith4ghelp said:
Thanks worked! any ways to enable to "xray" camera back?
Click to expand...
Click to collapse
[GUIDE][ROOT][MAGISK] Photochrom Filter Enabler
Disclaimer: you accept responsibility by flashing this magisk module to your device at your own risk. If you experience any issues with Magisk, please refer to https://github.com/topjohnwu/Magisk/issues This magisk module was created by...
forum.xda-developers.com
Maybe this

issuewith4ghelp said:
This is a easy fast way to update OOS in the future..
Click to expand...
Click to collapse
I do it this way. Due to the global not showing up... Only the incremental seems to be accessible anymore...
issuewith4ghelp said:
How to update to newest global AA build with root, There is no computer needed. Just restore stock boot img backup from exkm, then go into magisk > uninstall > restore images. Then go to OTA and it will let you install no issues. Then, before rebooting, but after OTA install, go back into magisk, click install, install to inactive slot (after OTA) option. Then reboot. You’ve successfully ota updated and kept root in the process, now remember to take a new boot img backup
Click to expand...
Click to collapse

Is it true that if I have root, mobilerm payments via NFC will not work?