Related
I have a brand new stock verizon S3 and am wondering if I can use the MrRobinson root method to root for the very first time. I swear someone in one of the forums said they did but it sounds like most people are using those images to just update. I originally tried this 4.1.1/4.1.2 method and it bricked my phone on flashing the VRALEC bootchain step, everything looked good in odin, the phone looked like it tried to restart, then went black and never came back. I got a new phone and am wary of trying the same method again. If that is the method I have to use any thoughts on what could have went wrong?
I appreciate any input.
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Ryno77 said:
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Click to expand...
Click to collapse
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
idk why that happened. My best guess is if the battery was low prior to you using Odin then it may have needed charging. But that VRALEC/Odin method is proven working countless times and those files linked in the OP have been used countless times.
Just know that with mrRobinson's pre-rooted images, you'll still need to unlock your bootloader with say EZ Unlock v1.2 (available on Rootzwiki so google it) before you decide to flash custom roms/kernels.
Ryno77 said:
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Click to expand...
Click to collapse
Like I said above, may have been the luck of the draw or it could have needed charging.
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
If you want to have a 4.1.2 rooted stock version, you need to download MrRobinson, K3 full wipe image with root (http://www.androidfilehost.com/?fid=9390214368362234355), unzip it first, then use Odin to flash this, then install Voodoo OTA root keeper from the market to preserve root, then let OTA update back to 4.1.2, finally use OTA root keeper to restore root. Done, simple and risk free.
You guys rock thank you!
As a followup for anyone that may stumble upon this thread in the future, I used the method provided by buhohitor and it worked like a champ. I flashed the mrRobinson image used ez unlocker to unlock the bootloader then used ez recovery to flash the latest version of TWRP. I'm now running this Paranoid Android 4.2.2 Rom and it is fantastic!
I need some help, I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.165.XT912.Verizon.en.US with the only tool I can find to use on DROID_RAZR_Utility_Jellybean_XT912_WinMacLin
Can anyone guide me in the right direction? thanks
Did you extract tool to desktop and then open it? It will give you all the instructions you need. Make sure you have USB debugging on too.
http://www.youtube.com/watch?v=XDV_72mPt4k
http://droidrazrroot.com/droid-razr-root/how-to-upgrade-to-and-root-jelly-bean-on-droid-razr/
There are two links that might be helpful to you. Hope it helps.
I lost root upon this last Verizon upgrade to 98.72.165. I think it was 98.72.16 before this weekend's update. I am going to try and go back to the original JB (98.72.16), enable root and hopefully find some type of rootkeeper utility that will stop this craziness. I can keep you posted if this works as I don't know what else to do. I use the Tasker application and most of my tasks are not functioning.
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
98.72.165.en.US version
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Anybody have an answer?
fredlpage said:
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Click to expand...
Click to collapse
mwyarm said:
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
Click to expand...
Click to collapse
How did you go back to 98.72.16?
Can you show me the steps please?
I was able to successfully root my phone after the update without a re-flashing or a wipe with Matt's Utility.
I followed the instruction in the link below. However, once I put the phone into BP Only mode, nothing happened. I let it sit there for about 5 minutes, then rebooted it normally and finished the exploit. It rooted the phone just fine.
http://mobility.forumsee.com/a/m/s/p12-9245-0620611--root-after-ota-165.html
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk
Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
If she is rooted it will break root, If she has a custom recovery (twrp) than it will cause a boot loop.
advice: if she wants lollipop she's gonna have to follow these steps.
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
Going to pass the link on to her now.
There is no custom recovery. She used Stump Root originally to get her phone route, if that makes any difference.
martinezma99 said:
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
Click to expand...
Click to collapse
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
SGE_DEW said:
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
Click to expand...
Click to collapse
You would still lose root
2SHAYNEZ
Yep.. I went through the whole process of going completely back to stock and then rooted before updating to Lollipop hoping it would stay. It didn't and Stump Root says it's already rooted.
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Rayvin56 said:
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Click to expand...
Click to collapse
I read somewhere the LG Flashtool had to be modified at installation to avoid what you are going through.
You're right, it's just a matter of overwriting the megalock.dll file after you install the tool. It was a step I didn't miss. But good news for me, I used another pc and when I installed the flashtool it again gave me the three choices (not sure, but the title bar of the window was something like 'DMB').
This time I chose the 'global' selection and ran the tool as before and it completed for me. I'm currently DL'ing the lollipop update right now. Thanks for the quick reply, netomel.
partylikeaninjastar said:
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
Click to expand...
Click to collapse
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
hitekredneck said:
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
Click to expand...
Click to collapse
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update.
Click to expand...
Click to collapse
+1
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
Click to expand...
Click to collapse
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Lolipop upgrade
Hi iam very new on this forum . I got LGg3 AT&t version D85010f and i cannot upgrade to LOLIPOP always i have com that i have latest soft and need to wait 48h to next check ......plz help me
hitekredneck said:
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Click to expand...
Click to collapse
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Vess69 said:
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Click to expand...
Click to collapse
Call Bull**** all you want, I don't lie. To be honest, I can't even remember what method I used to root when on KitKat. Then I used TiBu to freeze a bunch of apps that I didn't want or need. Shortly thereafter the update hit me so I went ahead and let it do its thing. As stated, I did lose root afterwards but the apps I had frozen with TiBu remained frozen and everything still worked as it should. I waited patiently for a few weeks until the one click root script became available and used it to root lollipop, then installed TWRP and flashed Cloudy G3 stock ROM which is where I am happily at at this moment.
It could possibly have successfully updated due to the fact that I had not installed a custom recovery, that's the only thing I can think of that would have allowed it to happen on mine, yet not on others that were rooted.
EDIT: After reading back through this thread it jogged my memory. I used the Stump Root method to root while on KitKat.
You'd be the first person reported to be able to do this.
It would be a boon to the AT&T G3 community if you could remember the precise details of how you pulled this off as it would save loads of time and hassle for everyone else who has to restore to KK (which means a full wipe), then take the OTA to L, then root there.
Thanks in advance.
*edit
I think you're L is version 20f, not the latest 21l, based on the date of your posts above.
Further, I'd suppose that what may have happened to you, is that the deivce had already downloaded the L update (from 10f to 20f) before you pulled off the root on KitKat. Then you simply acknowledged the install, which perhaps KK would allow to continue through.
Reports are the L will not allow this. So, going forward, someone rooted on L would not be allowed to complete the install even if the package is already downloaded on the device.
Still, it is, interesting.
HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???
Same thing happened to me. Don't know why yet.
Same here. Where are you from?
Nvidia might have pulled it to fix something wait patiently it will come.
I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!
Exact same issue here.
If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.
Just wait a little. That's what NVIDIA calls "staggered rollout".
Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.
if you have "nougat launcher apk" just delete it.
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.
Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.