Are there any KF2 stock rooted roms out there? There are too many bugs with the two current KF2 roms out...I need YouTube to work, etc. Is there a stock rooted rom I can use until development gets a little better? Thx.
xXezmacXx said:
Are there any KF2 stock rooted roms out there? There are too many bugs with the two current KF2 roms out...I need YouTube to work, etc. Is there a stock rooted rom I can use until development gets a little better? Thx.
Click to expand...
Click to collapse
... just root the stock rom?
fmkilo said:
... just root the stock rom?
Click to expand...
Click to collapse
is there a way to get back to stock with out having to root all over again? it took me and you a while to root my kf2 lmao...btw how do you get back to stock? i should have did a backup.
xXezmacXx said:
is there a way to get back to stock with out having to root all over again? it took me and you a while to root my kf2 lmao...btw how do you get back to stock? i should have did a backup.
Click to expand...
Click to collapse
This is how you get back to stock:
http://forum.xda-developers.com/showthread.php?t=2096888
NavyLCDR said:
This is how you get back to stock:
http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
you need to buy a factory cable from what i read in that thread? thats the only way to get stock root? this is confusing as hell?
xXezmacXx said:
is there a way to get back to stock with out having to root all over again? it took me and you a while to root my kf2 lmao...btw how do you get back to stock? i should have did a backup.
Click to expand...
Click to collapse
Okay, you need to clarify really what the issue is, and what you're trying to do.
Firstly, YouTube does work on the CM10.1 rom, just not with HD.
ROMs are the Operating system for your kindle. All ROMs can basically enable root, and install the superuser app. If you have root, you're still on stock. However, using the root permissions, you can get a bootloader/recovery setup, and then install a new ROM. Most new ROMs have root already enabled and superuser installed, but they don't have to. You can get and lose root on any ROM.
This is how you restore the Kindle. Yes you do need a fastboot cable.
Depending on what state your device is in, it may be possible without the cable, but it would be more complex and/or dangerous.
iytrix said:
Okay, you need to clarify really what the issue is, and what you're trying to do.
Firstly, YouTube does work on the CM10.1 rom, just not with HD.
ROMs are the Operating system for your kindle. All ROMs can basically enable root, and install the superuser app. If you have root, you're still on stock. However, using the root permissions, you can get a bootloader/recovery setup, and then install a new ROM. Most new ROMs have root already enabled and superuser installed, but they don't have to. You can get and lose root on any ROM.
This is how you restore the Kindle. Yes you do need a fastboot cable.
Depending on what state your device is in, it may be possible without the cable, but it would be more complex and/or dangerous.
Click to expand...
Click to collapse
Sorry for not explaining myself bettter. I'm currently on [ROM] [JB 4.2.1]cm10.1/sgt7 [20130118], obviously rooted, the whole shabang, nothing is with my KF2, I can boot into the rom, recovery, restart, power on/off, etc. Anyways, fmkilo helped me root my KF2 as it was totally different for me than my original KF which was easy to root, has issues with this. He was a big help and recommended that I flash the sgt7 rom, well I didn't make a backup(not going to say why) of my KF2 when I was rooted using just stock, no rom, etc. Well the sgt7 rom is not stable for me, YouTube isn't working(which my son uses, the KF2 is basically his) along with other issues. I want to just get back to my stock KF2 until something more stable for daily use comes out. I don't want to lose root, I just want to get back to my KF2 before I flashed the sgt7 rom. From what I've read you have to buy a special factory cable to restore your KF2, correct? I don't have one so I'm curious one why I need to go through all that trouble just to get back to stock w/ root? All I need right now is the Android Market and the Google apps.
xXezmacXx said:
Sorry for not explaining myself bettter. I'm currently on [ROM] [JB 4.2.1]cm10.1/sgt7 [20130118], obviously rooted, the whole shabang, nothing is with my KF2, I can boot into the rom, recovery, restart, power on/off, etc. Anyways, fmkilo helped me root my KF2 as it was totally different for me than my original KF which was easy to root, has issues with this. He was a big help and recommended that I flash the sgt7 rom, well I didn't make a backup(not going to say why) of my KF2 when I was rooted using just stock, no rom, etc. Well the sgt7 rom is not stable for me, YouTube isn't working(which my son uses, the KF2 is basically his) along with other issues. I want to just get back to my stock KF2 until something more stable for daily use comes out. I don't want to lose root, I just want to get back to my KF2 before I flashed the sgt7 rom. From what I've read you have to buy a special factory cable to restore your KF2, correct? I don't have one so I'm curious one why I need to go through all that trouble just to get back to stock w/ root? All I need right now is the Android Market and the Google apps.
Click to expand...
Click to collapse
just flash the new hashrom until sgt7 gets updated, youtube hd works now, if you really want to go back to stock, I can guide you over on irc... details in my sig VV
The only thing a factory cable does is get you into Fastboot. If you have a rooted ROM, you can get into fastboot either using ADB commands (if the Kindle is connected to the computer): "su" <enter> and then "reboot bootloader" <enter>. Without the quotes. reboot bootloader will cause the Kindle to reboot into fastboot mode and then you can use the first aide program in the link provided to load the factory ROM, and then do the factory over the air upgrade to 10.2.6 and then root it.
Or, install Android Terminal on the Kindle, and in Android Terminal issue the commands "su" and then "reboot bootloader".
NavyLCDR said:
The only thing a factory cable does is get you into Fastboot. If you have a rooted ROM, you can get into fastboot either using ADB commands (if the Kindle is connected to the computer): "su" <enter> and then "reboot bootloader" <enter>. Without the quotes. reboot bootloader will cause the Kindle to reboot into fastboot mode and then you can use the first aide program in the link provided to load the factory ROM, and then do the factory over the air upgrade to 10.2.6 and then root it.
Or, install Android Terminal on the Kindle, and in Android Terminal issue the commands "su" and then "reboot bootloader".
Click to expand...
Click to collapse
ok so i downloaded android terminal and i also downloaded the new "update-kindle-10.2.6_D026_2630020.bin".
could someone please give me step by step directions on how to put the new 10.2.6 updat on my kf2? i saw this http://forum.xda-developers.com/showthread.php?t=2111300 (he said you can install google apps with just root, no rom needed?
so my goal is to just get on update-kindle-10.2.6, root and install google apps. any help would be much appreciated. thanks.
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 !
ok, I got stock 4.4.4 but with root, bootloader is locked..
I wanna be able to receive the OTA update what do I need to do in order to be able to receive that?
or do I need to unlock the bootloader, install a recovery and flash lollipop threw that?
If you have stock system, kernel, and recovery, (no altered system files, either) being rooted won't keep you from getting the OTA. Locked/unlocked bootloader doesn't matter. If you rooted with SuperSu, just use its settings to uninstall root (you'll lose it anyway). However, I think you have to unlock bootloader to reroot, which, of course, will wipe your device. The OTA zip is now available for adb sideload if you're interested.
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Cobra11Murderer said:
nvm got stock recovery back on, lol still learning, is it better to side load or can i use flash stock + unroot on the nexus root toolkit v1.9.3 to do the same?
Click to expand...
Click to collapse
OTA won't wipe regardless of how you get it--over the air or sideloaded. Wug's will wipe unless you tell it not to (Options>Flash Stock>Enable no wipe). He also has the LRX21P build available. IMO, one way isn't better than another.
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
You probably already did all this, but you have to specifically send command to lock boot loader. I don't get how your device wasn't recognized through stock recovery but is on NRT, but it doesn't matter. Just use the kit which is what you probably did.
What you should do is back up what you need and want, then unlock the bootloader. You're not gonna get root without it on Android L since it requires a custom kernel.
Cobra11Murderer said:
ok, I just tried to sideload and looks like i got a driver issue :\ lol followed the steps in the installation guide and did the test.. it works great up till i go into stock recovery and hit sideload lol then it disconnects and tells me no driver found...
i might just try flash stock + unroot and choosing LRX21P, that wont lock my bootloader correct? and should I be a little worried that the driver cant be found for that specific thing? thanks for all the help btw!
Click to expand...
Click to collapse
Based on this, I assumed you unlocked your bootloader since first posting. NRT recognizes the device, right? Have you gotten it all sorted out yet.
idk why adb sideloading would kick the connection out, then the pc would say nexus 7 but wrong driver?, anyways i just went ahead and flashed the factory image using flash stock + unroot since I had it all backed up anyways, and that went great now I got lollipop on it, and should be able to root no probs now
thanks everyone, I hope i dont have a issue with adb again, im not sure if it was the samsung cord or what but it kept disconnecting at that part asking for a driver.. funny thing everything from bootloader, fastboot and all worked great with the driver that I installed using the steps in the toolkit..
Glad it's all good. Root with the toolkit. Just for the heck of it, you may want to try running CMD from wug's ADB folder. I've experienced just the opposite with older versions of the kit. NRT wouldn't recognize device. I'd go to CMD and device recognized. Return to NRT, all good again.
alrighty will do!, thanks for all your help
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.
I rooted it using Kingroot, flashed LiquidSmooth, CyanogenMod, Pac Rom, and SlimKAT, but decided that I wanted to return back to stock. I noticed that none of my apps can write to the phone's internal storage (i.e. Jotterpad, Monospace). I want to be able to return my phone to it's out-of-the-box state. Are there any methods that don't require ODIN? If so, please dumb it down.
Some KitKat/Lollipop roms made before October 2015 can also be helpful. Thanks in advance.
It depends on the build your bootloader is from.
Open terminal emulator and enter this:
getprop ro.bootloader
I'm guessing it's a 4.4.2 build, in which case you can find enewman17's corresponding thread that has the stock roms. Most are in the General section I believe.
Flash in recovery as per his instructions and factory reset.
DocHoliday77 said:
It depends on the build your bootloader is from.
Open terminal emulator and enter this:
getprop ro.bootloader
I'm guessing it's a 4.4.2 build, in which case you can find enewman17's corresponding thread that has the stock roms. Most are in the General section I believe.
Flash in recovery as per his instructions and factory reset.
Click to expand...
Click to collapse
I will have to root my phone again. I'm probably going to end up flashing CyanogenMod 12.1.
--UPDATE--
tried rooting my phone again can't download kingroot, or transfer supersu.zip or kingroot.apk to my phone. now what?
Simplest method to root in my opinion would be to flash supersu from TWRP. Supersu can be on an external SD card.
Is the phone an i747 or i747m? There are stock KK ROMs for the i747m that can be flashed via Odin but not for the i747.
ZentixZaneic said:
I will have to root my phone again. I'm probably going to end up flashing CyanogenMod 12.1.
--UPDATE--
tried rooting my phone again can't download kingroot, or transfer supersu.zip or kingroot.apk to my phone. now what?
Click to expand...
Click to collapse
I dont know about kingroot. Heard of it, but I don't recall ever seeing people use it for the S3.
But aside from that if all you want is to flash a rom, you don't need root. You need a custom recovery to flash it with and that's it.
If you still need help with anything though, please give us detailed info about what you've done, what you want to do and what is the current state of your device.
Hope that helps!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I dont know about kingroot. Heard of it, but I don't recall ever seeing people use it for the S3.
But aside from that if all you want is to flash a rom, you don't need root. You need a custom recovery to flash it with and that's it.
If you still need help with anything though, please give us detailed info about what you've done, what you want to do and what is the current state of your device.
Hope that helps!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
So I can flash CyanogenMod without root? Also, I can't transfer files between phone or PC and can't download files on phone either. Now what?
Apparently, none of my installed apps can update on their own either. Neither can Google Play. The version of Google Play I'm running is very old. This is becoming very problematic for me.
--UPDATE--
I went back to a backup I made. Original problem still exists.
I have the Fire TV 1 and had TWRP and Pre Rooted 5.2.4.1 FW installed. Yesterday during a restart the FTV started boot looping. I could see the option for TWRP recovery though.
I booted into TWRP recovery and reflashed the Pre Rooted 5..2.4.1. The FTV now booted but I have lost both TWRP and SuperSu as well. When I type su into an adb shell I got su not found?
Updated were blocked through the device as well.
Anyone else experience this? What can I do now to get TWRP installed and root established?
Help anyone?
Bump ^
Did you do any factory reset or something? I don't know how you could have lost SU and twrp when installing the prerooted roms. All apps say no root? i wonder if you did a factory reset if it would help or re-installed whatever version you were on when you rooted? I'm a novice so don't blame me for bricking! lol
Michajin said:
Did you do any factory reset or something? I don't know how you could have lost SU and twrp when installing the prerooted roms. All apps say no root? i wonder if you did a factory reset if it would help or re-installed whatever version you were on when you rooted? I'm a novice so don't blame me for bricking! lol
Click to expand...
Click to collapse
Thats why I am stumped! I did not do any factory resets or wipes. I simply selected rbox's rooted 5.2.4.1 ROM, installed and rebooted. Now I dont see the initial boot screen when the fire tv restarts. Just the regular animation.
is your bootloader unlocked? I don't have any rooted FTV1's. I think you could reflash the recovery if your unlocked....
Michajin said:
is your bootloader unlocked? I don't have any rooted FTV1's. I think you could reflash the recovery if your unlocked....
Click to expand...
Click to collapse
Unfortunately I don't think my bootloader is unlocked
pspTP said:
Unfortunately I don't think my bootloader is unlocked
Click to expand...
Click to collapse
all i can think of is try to root with a USB A to A cable, i think that was possible. From appstarter do you see anything non-stock?
Michajin said:
all i can think of is try to root with a USB A to A cable, i think that was possible. From appstarter do you see anything non-stock?
Click to expand...
Click to collapse
Since I had installed rBox's 5.2.4.1 rooted ROM when I had root, thats what I am on now except without root now. I had blocked updates on the device so thankfully that is still in place. And according to aftvnews, this version cannot be rooted.
I do have a bunch of non stock apps that I had installed that are still present on the device.
pspTP said:
Since I had installed rBox's 5.2.4.1 rooted ROM when I had root, thats what I am on now except without root now. I had blocked updates on the device so thankfully that is still in place. And according to aftvnews, this version cannot be rooted.
I do have a bunch of non stock apps that I had installed that are still present on the device.
Click to expand...
Click to collapse
you ever try to sideload SuperSU? Or run a root app that requests access and seen if it just says access denied? Just throwing out ideas to try, I didn't see anyone else trying to help. If you flashed pre-rooted version then i would think some of the exploits are still in your system.
Michajin said:
you ever try to sideload SuperSU? Or run a root app that requests access and seen if it just says access denied? Just throwing out ideas to try, I didn't see anyone else trying to help. If you flashed pre-rooted version then i would think some of the exploits are still in your system.
Click to expand...
Click to collapse
I downloaded the latest supersu and sideloaded it. When I run it there is simply a blank screen and back to where I was. Nothing happens.
Now in appstarter I can see two versions of su, one from before and the latest one. Running either does not do anything.
I had Adaway installed before as well. If I run it now, it just comes back with not a rooted device
Do you still have TWRP? You should be able to flash SuperSU that way.
Sizzlechest said:
Do you still have TWRP? You should be able to flash SuperSU that way.
Click to expand...
Click to collapse
No thats the kicker, I lost both TWRP and root.
It is a long shot, but you could try kingo root and king root, see if they can get root access. I know they dont work on a firetv stock for rooting, but something must have flashed wrong and maybe they can find a way into root.
Curious though, every time you have flashed the pre-rooted OS did you always disable the updates every time?
Michajin said:
It is a long shot, but you could try kingo root and king root, see if they can get root access. I know they dont work on a firetv stock for rooting, but something must have flashed wrong and maybe they can find a way into root.
Curious though, every time you have flashed the pre-rooted OS did you always disable the updates every time?
Click to expand...
Click to collapse
I believe the pre-rooted OS has that setting disabled in the first place.
pspTP said:
I believe the pre-rooted OS has that setting disabled in the first place.
Click to expand...
Click to collapse
AFTVnews always recommends disabling updates to be sure. It almost seems like you got updated. Try running Kingroot. Worst case it fails and you are still where you are at...