Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-developer-os-images
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Hi there,
my shield is on stock now with several apps on it.
How can I flash without losing my data? Is it enough to NOT flash the userdata?
THX
Chaos
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
BillTheCat said:
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
I have a question, where do you find pre-root load in below link?
I only find Open source and recovery image.
you mean to modify Open source and build pre-root load?
https://developer.nvidia.com/shield-open-source
https://developer.nvidia.com/shield-developer-os-images
BillTheCat said:
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
thanks
hardwarechaos said:
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
Click to expand...
Click to collapse
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
hardwarechaos said:
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image
Click to expand...
Click to collapse
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Hi
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
IMHO if you have adb root there should be a way to install it via adb too, but I could not find one and didn't want to mess around with installing the SuperSU files manually.
THX
Chaos
hardwarechaos said:
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
Click to expand...
Click to collapse
Agreed - turns out the Dev images are no real benefit. I found that installing TWRP, rebooting the bootloader, entering recovery and then flashing SuperSU works like a champ.
Anyone else having trouble flashing system and userdata? Keeps saying FAILED (Remote: data too large)
BillTheCat said:
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Click to expand...
Click to collapse
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
jweaks said:
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
Click to expand...
Click to collapse
Yes it will kill amazon video.
BillTheCat said:
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Click to expand...
Click to collapse
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
dillfever said:
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
Click to expand...
Click to collapse
can close this got er all done.......dill
hardwarechaos said:
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
Click to expand...
Click to collapse
Hello,
Same result for me.
I've just received my Shield, I've followed the instructions given on the developers web page. I have an up-to-date 3.0.0 version, but applications don't have the root authorisations (tested with ES File Explorer).
I think I'll use the TWRP method...
i download 3.0 rooted version it came a zip with all files on it on nvidia shield.com tutorial said just ento bootloader and type comand flash-all.bat and gualahhh! but try like 1000 times and always said null error message and force close adb
can some one tell what im doing wrong please and thanks people!
bye the way gamestop its selling shield tv for 100bucks so for those who want another its the right time to get one
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
dismissthesky said:
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
Click to expand...
Click to collapse
to remove zulu rom this is easy.
just go to nvidia site and get the complete factory images for your shield.
it will come with a guide on how to flash your shield with them.
it will delete everything in your shield and it will be stock like brand new.
then you can root it if you want or install a different rom.
Nexus Noob here. As I'm still learning, I have some questions regarding the update process. I would prefer not to have to wipe data and re setup my phone, and I found several tutorials that mention flashing everything except data.img. That all I understand.
What I'm not sure on - when I got this phone and rooted it, I needed to flash a modified boot.img file. When updating to 6.0.1 or whatever newer versions come out, do I need to do that still? I found another tutorial that mentions flashing all the img files and then reflashing supersu, but no mention of the modified boot.img (http://www.teamandroid.com/2015/12/08/root-nexus-5x-android-601-mmb29k-marshmallow-factory-image/2/) That's why I'm confused.
Any help you can give is appreciated. Thanks
That guide refers to a older version of SuperSU. The latest beta version is 2.61 (SuperSU-v2.61-20151207213702.zip) which you can find here.
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This is a new method that automatically patches the boot image for you so you do not need to flash a modified boot img yourself. Versions 2.60 and later do this. That is why the guide you linked does not say you need to flash a modified boot.img.
Just make sure that you haven't modified your system partition (by rooting or otherwise) before you flash this.
I did root and put some ring tones in /system/media. Will flashing system.img overwrite that all and then I can update or do I have to go back to stock completely?
hi, I am trying to see if I can extract the launcher off of my version 2 fire tv and put it on the fire stick version one?
I do not want to root though. I did search the forums and saw of this.
thank you in advance.
kblgy said:
hi, I am trying to see if I can extract the launcher off of my version 2 fire tv and put it on the fire stick version one?
I do not want to root though. I did search the forums and saw of this.
thank you in advance.
Click to expand...
Click to collapse
From what JayDeeDaz posted over on one of the AFTVNews comment sections. It should work fine. And it should be the same for both rooted & non-rooted devices. As long as there are on some version of FireOS 5.
I wrote a walk-thru on the two easiest ways to backup an APK over here:
https://forum.xda-developers.com/showpost.php?p=70354529&postcount=2
You can also check the APK's Hash values to make sure the backup APK was correctly backed up by using the Properties option on ES File Explorer. I will add this part to the walk thru in a bit.
Thanks to @AFTVnews.com for reminding me:
The "KFTV Launcher.apk" can be found in either the official v5.2.4.0 FW update or the v5.2.4.0 FW PreRooted Rom.
Update: Still need the APK please. The original & PreRooted ROM's come with the APK's in a .DAT file. Which I can't extract or access.
Y314K said:
From what JayDeeDaz posted over on one of the AFTVNews comment sections. It should work fine. And it should be the same for both rooted & non-rooted devices. As long as there are on some version of FireOS 5.
I wrote a walk-thru on the two easiest ways to backup an APK over here:
https://forum.xda-developers.com/showpost.php?p=70354529&postcount=2
You can also check the APK's Hash values to make sure the backup APK was correctly backed up by using the Properties option on ES File Explorer. I will add this part to the walk thru in a bit.
Thanks to @AFTVnews.com for reminding me:
The "KFTV Launcher.apk" can be found in either the official v5.2.4.0 FW update or the v5.2.4.0 FW PreRooted Rom.
Update: Still need the APK please. The original & PreRooted ROM's come with the APK's in a .DAT file. Which I can't extract or access.
Click to expand...
Click to collapse
Use sdat2img to convert the .dat to .img
Then use EXT4 Unpacker and EXT2Reader to access the files.
Hi, I'm new to FireTV. I bought a 4k stick and rootet it. In most guides it was said to disable OTA updates from Amazon. For one, I couldn't find the actual reason for it. All I read is that Amazon is limiting the users more and more. From a security perspective I think its unwise to not update in longterm so if this is the only reason, you might achieve more by not buying an Amazon Stick and go for a different manufacturer. Please let me know if there are other reasons (technical ones for example)
With this said, my main question is how to update when OTA is disabled. There are various threads with stock firmwares, prerootet firmwares and what not but I couldn't find out which ones to get to update. Obviously I don't want to lose root but it's barely a hassle to reflash magisk if TWRP survives.
So how do you guys update your device?
Download 6.2 7.7
https://d1s31zyz7dcc2d.cloudfront.net/a6a58dbe9be48f241bc44e1bfce92847/update-kindle-mantis-NS6277_user_3027_0004597732228.bin
Rename bin to zip.
Push zip to sdcard.
Reboot to twrp.
Flash firmware.zip
Flash magisk.zip
Reboot
Thanks a bunch. So magisk will have to be flashed with every update? I'll keep the magisk file on the sdcard then.
The Firmware is globally the same I guess?
Rorschach1010 said:
Thanks a bunch. So magisk will have to be flashed with every update? I'll keep the magisk file on the sdcard then.
The Firmware is globally the same I guess?
Click to expand...
Click to collapse
yes as long as you remember to flash latest magisk from TWRP after you flash firmware.zip youll be okay
The latest firmware is just the same as the rest except things such as ftvlaunchx custom launcher have been patched by amazon and dont work. Thankfully this has a workaround though
Hello,
I rooted my FireTV Stick 4k (mantis) some time ago with fireISO 1.0, kamakiri-mantis 1.2 (I believe) and it worked just fine until recently. Now it often crashes, is slow or I have to reboot several times before I can use it.
The firmware version is 6.2.6.8, Magisk 20.1, Magisk Manager 7.4.0, TWRP 3.3.1-0. So everything seems a bit outdated and I hope that an update will solve the problems mentioned.
I found several threads on different websites but they are either referring to other devices, software versions or starting situations.
Can someone please show me where I can find a comprehensive guide or tell me how to do the updates, where to find the latest firmware and software versions and what to consider in general (e.g. I never had to use TWRP after the rooting and now, when I cancel the rebooting on the stick and start TWRP it asks me if I want to leave the system partition read only or allow changes. No idea.)?
Thanks for your help!
There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.
Sus_i said:
There are some threads, guides and youtube videos on how to install roms and how to interact with twrp...
but if you want to keep your device 'kamakiri vulnerable via shorting' then you want only install this prerooted rom to your stick:
Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might. First, you must be unlocked. You can follow the instructions...
forum.xda-developers.com
Make sure that you flash July 17, 2021 - 6.2.8.1.r2 first, then 6.2.8.1 r3 if you like. Don't forget to disable the OTA updates.
Click to expand...
Click to collapse
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Btw, what means keep your device "kamakiri vulnerable via shorting"?
Droidknot said:
Thanks for the link. I've already found this thread but since I don't know what "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." means I was hoping that I can flash a stock rom instead of a pre-rooted so that I don't have to be careful about that blow efuse thingy.
Click to expand...
Click to collapse
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Droidknot said:
Btw, what means keep your device "kamakiri vulnerable via shorting"?
Click to expand...
Click to collapse
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...
Sus_i said:
You can flash stock roms, easiest is to enable updates and the OTA app will install the latest...
But netflix and prime video etc won't play stuff, until you flash an updated trustzone (TZ image) to your stick (which the 6281r2 prerooted does for you).
Together with this updated TZ image, every stock rom above 6.2.8.0 burns an efuse in the SOC, which will prevent/patch the kamakiri shorting method, i.e. unbricking via short is gone forever.
Click to expand...
Click to collapse
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Sus_i said:
You may know how you did the unlock in the first place, open and short a special point...!?
PS: The prerooted was put together because the blow efuse thingy, i.e. efuse burning is disabled in the prerooted...
Click to expand...
Click to collapse
Yes, I know the shorting method but I didn't know that later firmware versions make this method impossible. The warning "NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE." made me believe that it is basically possible to (manually) flash a specific stock rom, e.g. 6.2.7.1.
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
If not, I would prefer to update Magisk, Magisk Manager and TWRP (if this can be updated separately) first and to check if this already solves the issues. If it's always possible to go back to stock mode, flashing the pre-rooted rom would maybe be the easier way.
Do I have to set up TWRP as read only or read write on system partition? I ask because some sources say this, other say that.
Droidknot said:
Thanks for the explainations, that makes it clearer. Isn't it possible to manually flash a specific firmware version (which doesn't patch the kamakiri shorting method) with TWRP? E.g. to download a stock rom zip file and then flash it with TWRP?
Click to expand...
Click to collapse
Ofc thats possible, but as I said DRM is broken because the new OS needs a new TZ
Droidknot said:
After flashing the pre-rooted rom will it still be possible to OTA update to the latest version and bring the device back to stock mode?
Click to expand...
Click to collapse
It's possible, but all new Stock will burn the efuse by default, if the new TZ is also there.
Easiest is if you just flash the prerooted 6281r2 (which updates the TZ so no DRM issues for you), then the 6281r3, done. Make sure that updates are disabled and thats it. Watch out if your issues are gone.
If you somehow/sometimes want the stick at a higher stock OS than 6281, @SweenWolf released a patch, which deletes the efuse burner for you... needs to be flashed just after the stock rom.