VRALG7 Update Question - Verizon Samsung Galaxy S III

I am relatively new to the rooting experience but am a big fan of the benefits. I only do basic stuff and am too paranoid to try flashing ROMs or anything too advanced. I recently downloaded the most recent update and it didn't go as I had anticipated.
I was taken to the reboot screen as if I was using Clockwork Mod. It asked me questions that I had to answer in order to proceed but the choices were strange. It would ask me, "do you want to install this unfamiliar zip?" and the answers would be, "No, No, No, No, No, No, Yes, No, No, No, Go Back." I picked yes for the 3 different choices and it completed the install.
After the phone rebooted there was a message saying that the update had failed. I called my brother who has an unrooted phone and checked to see that I in fact do have the update. I am wondering if this is what will happen each time I get an update and if there is anything I should be worried about. The phone is still rooted and I don't notice anything different, but I am just paranoid that rooting my phone will make it so I am unable to install the jellybean update next month. Thanks for the advice in advance!

that sounds like CWM or it might be the factory download mode but either way i dont think you should have to do that for a factory update

So you are on stock, but rooted? Usually the rule of thumb is not not accept the OTA updates, but rather flash one of the stock, rooted roms when an update comes out. You might wnat to try something like the root66 rom, if not somehting like Synergy or CleanRom, which are still stock-based.
As far as this particular issue, as far as I knew, the OTA updates will usually always install. The problem is that they will sometimes revert back to un-rooted, and sometimes will even block the root exploit so you're stuck.

update will fail if you are using a custom recovery, i.e. cwm

wwjdd44 said:
update will fail if you are using a custom recovery, i.e. cwm
Click to expand...
Click to collapse
Is there any way to remove clockwork mod? I don't really need it.

Related

[Q] A700 rooting question

Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
ianrobbie said:
Hi guys,
I've searched everywhere and can't get a definitive answer on this so here goes -
I'm a noob when it comes to Android, having recently defected from being an Apple Disciple (I got hacked off with iTunes and bored in general with the Daycare Centre which is iOS) and have recently acquired an Acer A700 tablet.
I have installed the JB update OTA and everything is working fine and am chomping at the bit to get it booted, but most of the posts I have read regarding unlocking the bootloader and rooting it relate to ICS.
My questions are -
Does the bootloader process apply regardless of Firmware? (Are there different versions for different Firmwares)
Can anyone point me in the direction of a decent tutorial on how to do this?
What happens regarding a future update? Do I have to revert back to stock and update from there or can i jump from one ROM to another? (I'm assuming that I can't use the OTA updates any more)
Sorry for the long OP and thanks in advance for your answers.
Click to expand...
Click to collapse
No problem. Seeing you are on JB, then you have a JB bootloader.
You need to go here http://forum.xda-developers.com/showthread.php?t=1953917
And download Vorbeths easyroot2.0. It's for the 700.
You have to unlock your bootloader first, which shouldn't be an issue for you. Easy instructions for that.
Then download his package to a folder on your PC. (not sure, but you may have to download each file individually) Open a command window (shift & right mouse click) and type in whatever his instructions say. Should be painless.
Make sure USB Debugging is turned on first in your tablet (Settings/Developer Options/USB Debugging), and make sure you have the Acer Drivers installed on your PC.
Then connect, wait 30 seconds, and run his batch file.
You should be ok.
MD
Oh yes, one more thing, once you unlock your bootloader, chances are you will not be able to get OTA. And the only way to re-lock the bootloader is to install a stock rom.
Thanks!
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
ianrobbie said:
Thanks for the reply. I am now the owner of a fully rooted A700!
Had a few issues during unlocking the bootloader. That thing timeouts quick! Also, didn't realise you had to run the .bat file while the tablet was on the Bootloader USB protocol screen. I thought you had to wait until it booted fully into JB.
Anyway, took the plunge and thanks again for your help.
Click to expand...
Click to collapse
No problem. I thought I mentioned it timed out in about 5 seconds These days I don't remember much
Yeah, I haven't looked at Vorbeth's script, so I don't know which screen he launches it from. With mine for the 701, you can be when the tab is running normal. No difference in the end result though
Happy Hunting!
MD
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
ianrobbie said:
One last question - do I have to install Clockwork Recovery for re-flashing the stock images or is it just a case of renaming it update. zip and putting it on an SD Card? Any chance you can point me in the right direction of the most recent/stable build? Is it easy to install?
Thanks again.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Moscow Desire said:
Well, this is a trouble spot.
If you wish to install a custom rom, then you will need to install CWM. The most recent version.
If you want to try your luck at installing a stock rom, my opinion, is to leave the stock recovery inplace. I haven't had luck in installing stock update.zips, as Acer has made them very specific. So I can't be much help to you in that.
However, you can always flash back to CWM or a stock JB recovery pretty easy. Personally, unless you plan on flashing a custom, I would just leave the stock recovery.
MD
Sometimes "leaked" update appear here in the forums. They are unofficial. And you never know if they improve things, or make things worse. So be careful.
Click to expand...
Click to collapse
So, just for future reference, how would I go about re-flashing the stock image? I'm assuming it's saved on the tablet in a separate partition?
I've decided to stick with the stock rooted ROM but would like to know how to re-flash for when Key Lime Pie and future updates are released.
And, seeing as how you haven't steered me wrong so far, I though I'd pick your brains one last time.
Hope you don't mind!

Questions regarding OTA and being rooted

Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
wouldn't you know, that as soon as I submit this post I find another thread dealing with the same thing... Sorry for the clutter.
Here is the thread I found http://forum.xda-developers.com/showthread.php?p=49249510
Sithlyone said:
Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
Click to expand...
Click to collapse
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
buhohitr said:
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
Click to expand...
Click to collapse
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Sithlyone said:
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Click to expand...
Click to collapse
No issue with tethering for me, just root then install wifi tether router.

[Q] OTA Lollipop update

So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Rey0 said:
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Click to expand...
Click to collapse
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
jagreci said:
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
Click to expand...
Click to collapse
Sounds cool then. Thanks
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
crucialcolin said:
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
Click to expand...
Click to collapse
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
beekay201 said:
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
Click to expand...
Click to collapse
I've actually been spoiled by nandroid on the HP TouchPad with CM. Really nice to have a complete backup image. Wish I would have thought about unlocking and rooting before I got a bunch of stuff on my Nexus setup the way I like it. Sort of stuck since you have to unlock the boot loader for a custom recovery. Thus is life though.
I haven't tried it yet but it looks like Adb can do it on a stock device.
ex: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
I'm actually extremely torn on the OTA thing. I find it just so damn convenient with the admission I've gotten lazy of late Otherwise I have a tendency to never update.

[Q] Moving SCH-I535 Verizon S3 from 4.1.2 rooted to 4.4.2 rooted

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

Urgent problem with ota update 5.0

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.

Categories

Resources