So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
CavyS said:
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
Click to expand...
Click to collapse
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
scott500 said:
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
Click to expand...
Click to collapse
Yeah that might as well have been written in Arabic. I think that might be one of the methods I tried though?.. Except when I put the Nandroid backup in TWRP/backups then rebooted my phone into recovery the backup wasnt showing in there no matter what I did, and the other way just got an error.
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
CavyS said:
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
Click to expand...
Click to collapse
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
redpoint73 said:
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
Click to expand...
Click to collapse
Lol I know, idk why I have to have to OTA either. Its just an OCD thing. I think its because I know that what I'm getting from OTA is clean and is a 100% working squeaky clean release by Android. Opposed to a ROM that someones put together themselves. I'm sure there is nothing wrong with the ROM or that there is any kind of malware or viruses in it. But its just an OCD thing were I would never stop thinking about it. And first thing my phone crashes or runs into a bug regardless of the problem I would blame it on the ROM. Lol now I sound like a sociopath
CavyS said:
now I sound like a sociopath
Click to expand...
Click to collapse
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
redpoint73 said:
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
Click to expand...
Click to collapse
Quick question. I put the Nandroid backup in the TWRP/backups/ folder. It doesnt show up in "Restore" but it shows up in "Install" in TWRP Recovery. When I click on it in "Install" it asks me "Swipe to Confirm Flash" Is it okay to flash Nandroid backup from the "Install" location or does it have to be done through "Restore"?
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
twiggums said:
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I just updated with RUU, I'll re-root again once 4.4.4 gets pushed out.
Related
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
You can flash a ROM and keep your apps and whatnot. Just don't format the /data directory.
Sent from my ADR6400L using Tapatalk
Also some ROMs provide OTA updates through ROM Manager.
No, thats not a storm. Its just my Thunderbolt layin down this post.
But I'd expect issues when changing roms from different devs for sure
Sent from my ADR6400L using XDA App
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
If you are rooted & want the stock rom, you can go here, http://forum.xda-developers.com/showthread.php?t=1042004 you can flash the update without losing anything. I did it. All I had to do was delete the bloatware again...
Also there is a seperate file to flash the new radio. all works well for me... The version numbers were changed to show the original stock info, but that was to protect the leaker..
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
OTA updates don't wipe DATA or Cache.
You can do the same on any ROM (basicly) as long as it is JUST a update.
___
Sent from my HTC ThunderBolt 4G LTE on XDA Premium.
mike.s said:
What is it about OTA updates that allows them to be applied without losing apps/data/settings, but a "ROM" or downloaded update can't?
Hasn't anyone figured out how to apply an update equivalent to an OTA (but "root" safe) without losing settings?
Click to expand...
Click to collapse
Also some of the dev's add in a script that wipes prior to the install. If your flashing a new version of the same rom just remove the script before you flash the rom and don't wipe. But it's done to reduce errors/force close issues.
OTA updates can be a multiple of things.. It can be applying a patch, it could be a radio update, it can be a firmware update aka OS. There can be an OTA that will require a data wipe. Usually you would see something like that let's say for example not that this is happening right now but let's just say we were on the Thunderbolt 2.2.1 Froyo and they updated us to Thunderbolt 2.3.1 Gingerbread then most likely it's going to be a full data wipe because it's more then a minor patch it's a whole OS and the file system would be changed example libs etc.. So you can't have old data mesh with new data that calls for certain things in the phone differently then Froyo did opposed to the way Gingerbread would.. Hope this helps!! On custom ROM's every ROM is different or unique in it's own way... Some have things that others don't, the DEV adds stuff or removes stuff and that will play a role in how the ROM itself will run or react... I'm trying to make this sound as simple as possible.. lol Anyways again hope this helped..
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
DroidVicious said:
OTA updates can be a multiple of things.. It can be applying a patch, it could be a radio update, it can be a firmware update aka OS. There can be an OTA that will require a data wipe. Usually you would see something like that let's say for example not that this is happening right now but let's just say we were on the Thunderbolt 2.2.1 Froyo and they updated us to Thunderbolt 2.3.1 Gingerbread then most likely it's going to be a full data wipe because it's more then a minor patch it's a whole OS and the file system would be changed example libs etc.. So you can't have old data mesh with new data that calls for certain things in the phone differently then Froyo did opposed to the way Gingerbread would.. Hope this helps!! On custom ROM's every ROM is different or unique in it's own way... Some have things that others don't, the DEV adds stuff or removes stuff and that will play a role in how the ROM itself will run or react... I'm trying to make this sound as simple as possible.. lol Anyways again hope this helped..
Click to expand...
Click to collapse
That's not necessarily true. My Mom's Epic went from 2.1 to 2.2.1 without wiping anything.
On top of that, these updates are coming from manufacturers that know every single thing (I hope!) about the software they worked with/designed. It's easier for them to ensure minimal to no complications without wiping.
06ms6 said:
That's not necessarily true. My Mom's Epic went from 2.1 to 2.2.1 without wiping anything.
On top of that, these updates are coming from manufacturers that know every single thing (I hope!) about the software they worked with/designed. It's easier for them to ensure minimal to no complications without wiping.
Click to expand...
Click to collapse
Droid Eris went from 1.5 to 2.1 and wiped everything...... At least mine did.. if you follow a RUU read some instructions for some older devices that are on the Verizon Wireless site they talk about backing info up... I guess it comes down to how you update or upgrade..
You can also use Titanium Backup or if you don't want to wipe modify the install script. Most devs have people wipe with new roms just to prevent issues from older versions of software. Really, no custom apps should be installed in the data folder but some devs put them in there. Just something to expect with custom roms unless the dev spends a lot of time and effort into it like CM7.
No, thats not a storm. Its just my Thunderbolt layin down this post.
Yeah, with an RUU I can see that happening. Never have with an OTA though.
The short answer to the OP's question is that they spend many thousands of dollars pay teams of developers for many hours to make the upgrade as seamless as possible for users. Our devs just don't care enough, and rightfully so. Would you rather avoid a wipe or get 5x's as many features?
Sent from my ADR6400L using XDA App
Jaxidian said:
The short answer to the OP's question is that they spend many thousands of dollars pay teams of developers for many hours to make the upgrade as seamless as possible for users. Our devs just don't care enough, and rightfully so. Would you rather avoid a wipe or get 5x's as many features?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
We care, but people do other mods beyond custom roms. This makes it unpredictable.
jcase said:
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
Click to expand...
Click to collapse
So, the file you posted at http://forum.xda-developers.com/showthread.php?t=1041514 isn't really the same as the OTA, since it installs as an RUU and wipes everything?
Do we have to wait for someone to grab the actual OTA file before we can have a "root safe" upgrade which doesn't wipe data?
jcase said:
OTA updates are patches, and do an inplace update.
RUU Rums do a complete reinstall.
Think of it as an update to windows 7 v/s a new install
Click to expand...
Click to collapse
Well said; think of it as an upgrade to Service Pack 1 instead of re-installing Windows from scratch. Excellent analogy
mike.s said:
So, the file you posted at http://forum.xda-developers.com/showthread.php?t=1041514 isn't really the same as the OTA, since it installs as an RUU and wipes everything?
Do we have to wait for someone to grab the actual OTA file before we can have a "root safe" upgrade which doesn't wipe data?
Click to expand...
Click to collapse
Dude its an ruu, its been said over and over, it says it in the title of that thread, so of course it installs as an ruu.
You do not want to install the OTA over a rooted device. At best it will disable root (if it flashes, which it shouldn't) at worst it will brick.
jcase said:
Dude its an ruu, its been said over and over, it says it in the title of that thread, so of course it installs as an ruu.
Click to expand...
Click to collapse
Yes, I understand that.
You do not want to install the OTA over a rooted device. At best it will disable root (if it flashes, which it shouldn't) at worst it will brick.
Click to expand...
Click to collapse
The RUU you posted wipes data, but keeps root. The OTA doesn't wipe data, but would loose root. What does it take to have an upgrade file that keeps root and doesn't wipe data?
This goes to my original question - what is it about an OTA that allows it to keep data? Why can't there be an update file with the new release, which keeps data and root?
Does an RUU format a partition before copying files? Or does it simply have a partition image which is flashed in bulk? How does an OTA-type update differ? I'm not asking for a simple "Win install vs. SP1" answer (which answers "what it does," not "how it does it"), but is there a flag in the upgrade file which is set, or what - how is this actually controlled?
Ota is done with recovery and a n update.zip, it applies patches to the system to bring it current. With non rooted devices you know what the firm ware is and can safely do this. Rooted devices, you don't know with certainty what the firmware is, and patching can cause problems.
While I could make one for rooted user, I don't have time to deal with the complaints and requests for help that will come with it.
Sent from LG Revolution HD Pro
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.