I bought a Fire TV from Staples and I'm hoping it will be rootable. Assuming it is, I was planning to do the following:
Block the updates at the router.
Plug in the Fire TV and follow the rooting procedure (using Towelroot) without upgrading the firmware
Install ClockworkMod
Install latest Prerooted Stock Image.
The rooting procedure has steps for getting the firmware to the latest rootable version prior to rooting, but rather than go through all that, I'd rather get root ASAP and then flash a pre-rooted firmware using ClockworkMod.
I've got lots of experience rooting and flashing phones and tablets, so I don't think installing a custom recovery will be an issue for me. Is this a good plan?
Once you are rooted and have su installed, you should follow this guide: http://www.aftvnews.com/how-to-block-ota-update-for-amazon-fire-tv-and-keep-root-access/.
If you haven't already done so, you can't go wrong browsing thru all of the aftvnews.com guides.
jmerrilljr2 said:
Once you are rooted and have su installed, you should follow this guide: http://www.aftvnews.com/how-to-block-ota-update-for-amazon-fire-tv-and-keep-root-access/.
If you haven't already done so, you can't go wrong browsing thru all of the aftvnews.com guides.
Click to expand...
Click to collapse
Yes, disabling the service is something to do, but I was assuming the Prerooted Stock Images that I would be flashing would already have that disabled.
ASFAIK, rbox recommends doing this.
jmerrilljr2 said:
ASFAIK, rbox recommends doing this.
Click to expand...
Click to collapse
depending on the version you get and hopefully its rootable. I would do this.
Enable adb, install towelroot, disable updates and if you are on the initial version of the firmware where the menu items fit in one screen, then you are good to go. else downgrade first.
for safety disable the amazon updates through su everytime you are on new firmware.
then go up to the last version before unlocked firmware of rbox
then unlock and go to the bootloader menu along with the latest firmware
block updates and you are golden. latest and perfectly rooted.
For anyone else reading this thread, rbox made a walkthrough guide: http://www.aftvnews.com/start/
Just follow that. It does what I was planning on doing.
Related
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
soupmagnet said:
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
Click to expand...
Click to collapse
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Thibor69 said:
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Click to expand...
Click to collapse
I've tried to explain much of this a couple of times now, so here's my final attempt...
The generally accepted procedure for rooting or installing a ROM:
1) Get to fastboot mode by utilizing either...
a) a factory cable
b) fbmode
2) Install recovery and custom bootloader
3) Either root by installing su and Superuser.apk or flash a custom ROM
To get back to 6.2, you will still have to do #1 & #2 and flash the 6.2 zip package like you would any other ROM. Amazon's software will not allow you to downgrade the software through stock so you can use the BurritoRoot exploit.
It's not likely for someone to come up with a newer/easier method for rooting 6.3 because...
a) It's pretty straightforward as it is
b) No one spends the time to do it when the old way works perfectly well
I've laid out the procedure in excruciating detail here...
http://forum.xda-developers.com/showthread.php?t=1638452
I invite you to keep exploring easier ways to do this, so I can make the how-to above simpler and shorter, but I doubt you will find one. Good luck.
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
soupmagnet said:
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Click to expand...
Click to collapse
Just so everybody is on the same page and because I've done more rooting experiments the last few days than I care to admit.
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell. I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. For 6.2.x, the rooting method was to use the BurritoRoot exploit to gain root and then get to fastboot mode by using idme. Amazon closed that hole so BurritoRoot can no longer be used for 6.3.x. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... so, the process has been reversed... su -> fastboot for 6.2.x and now fastboot -> su for 6.3.x. So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Laquox said:
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
Click to expand...
Click to collapse
KFU is broken for whatever reason. It does get you su, but doesn't install the Superuser.apk... I don't know why and I'm not interested in debugging it. I'm not sure if sideloading Superuser.apk is the only thing that needs to be done after its "rooting" process, but it also installs the old versions of FFF and TWRP. That causes headaches all around for people that don't know their way around the bootloader and recovery. Otherwise, it's great!
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
kinfauns said:
...
Click to expand...
Click to collapse
Yeah, sorry about that. I was replying to his post and you beat me to the punch.
So, yeah...what kinfauns said
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
You can use the Kindle Fire Utility 0.9.5
That's what I used to root my Kindle on 6.3
You just have to sideload the superuser.apk file though
kinfauns said:
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell.
Click to expand...
Click to collapse
.....Yes that is what I want to do. I don't care about stock at all.
kinfauns said:
I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
Click to expand...
Click to collapse
.....I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
kinfauns said:
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Click to expand...
Click to collapse
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
kinfauns said:
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
Click to expand...
Click to collapse
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
I am ready to start this process now .... but I want to be 100% sure I have a recovery image in case I soft-brick somehow.
You guys are great ... and thank you for helping me !!!
Cheers
Thibor69 said:
I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
Click to expand...
Click to collapse
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
Click to expand...
Click to collapse
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
Click to expand...
Click to collapse
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Ok so to sum it up:
1) install kindle drivers, be sure PC see's Kindle and be sure adb is working
2) install TWRP
3) install latest bootloader (via link below)
4) then flash ROM ?
Cheers
soupmagnet said:
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Click to expand...
Click to collapse
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
soupmagnet said:
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Many thanks !
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!
My amazon fire tv is on a pre-rooted 5.1.3.0 and I would like to update to the latest version. What is the safest way to do this? I've read that I cannot just update to the lastest pre-rooted firmware
iHamie said:
My amazon fire tv is on a pre-rooted 5.1.3.0 and I would like to update to the latest version. What is the safest way to do this? I've read that I cannot just update to the lastest pre-rooted firmware
Click to expand...
Click to collapse
Go to aftvnews and follow the guides for custom ROMs exactly. He's very precise but I'd install them incrementally because some people report bugs otherwise. You'll definetly want to do 51.1.4.0 before going to the latest. And just make sure you install bootmenu and unlock bootloader (I believe the one after yours requires bootmenu.) Failing to do so has resulted in bricks.
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.
Hi
I have a 2015 Shield (non pro) currently running rooted 5.2.0. I am looking to update it with the latest 8.0.1 dev image to keep root. Is there any precautions or extra steps I need to take over what is in the instructions in the download centre. From what I have read I will need to ADB sideload Magisk to get full root access after installing the dev image.
you'll need to patch the boot.img in magisk canary and then flash it
https://forum.xda-developers.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
Do I need to unroot or factory reset the rooted 5.2.0 before flashing 8.0.1. Is there any benefit in flashing the dev image rather than the factory image before flashing the patched boot.img.
You should update the firmware OTA. Because you'll flash the OTA you'll need to patch then flash the dev image or this root boot image: https://forum.xda-developers.com/shield-tv/development/kernel-overclock-kernel-2-22-ghz-t3943079
But do I need to unroot etc to do an OTA.
g1dtf said:
But do I need to unroot etc to do an OTA.
Click to expand...
Click to collapse
yes unroot will happen automatically when you install the OTA. if you know how to use adb and follow my steps it's not a big deal though you can get it back quickly
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
g1dtf said:
I have just unfroze system upgrade (com.nvidia.ota) and it offers experience 6.3. I guess I have to incrementally install subsequent OTA's until I get to 8.0.1 then follow your guide to re-root using your guide, I am familiar with using ADB although its been quite a while since I last used it.
Click to expand...
Click to collapse
yes correct you need to do it incrementally--it's totally worth it Nvidia has done some great upgrades!
Got it up to 8.0.0 installing the OTA's. However the next OTA offered is 8.0.2 rather than 8.0.1 which as far as I know has no root options yet as the 8.0.2 images have not been released by NV.
yes but you don't need dev images to root, you can just patch this boot.img and it should give you root (as long as you install the latest Magisk canary and then upgrade through that)
https://forum.xda-developers.com/sh...l-2-22-ghz-t3943079/post81708169#post81708169
False double post please ignore.
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
g1dtf said:
Just a little confused as to which boot.img I need to patch. Looked at the XDA link you posted but there are quite a few different ones mentioned in that thread. I am currently running stock 8.0.2 OTA on my 2015 16gb.
Click to expand...
Click to collapse
Just boot into twrp using this https://drive.google.com/file/d/1934405D1S0lv52jZMqS-Zny62RIzGWSi/view
Then flash magisk canary in there, and you are done
Thanks! Flashed the latest canary and now rooted on 8.0.2.