Related
so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
I'm also getting this. Tried a factory reset, d/l update and still fails.
verdikt said:
so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
Click to expand...
Click to collapse
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
babymatteo said:
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
Click to expand...
Click to collapse
no its not. i havent done much with it not even cwm.this is so gay.i hope they get it fixxed
verdikt said:
no its not. i havent done much with it not even cwm.this is so gay.i hope they get it fixxed
Click to expand...
Click to collapse
try downloading Voodoo OTA Root Keeper then redo the process of updating. This might help, as it did with many rooted users.
My bootloader is not unlocked, and I have rootkeeper. I still get the dead android, even after a full system wipe.
Did you guys install the new google play market 3.1.5? If so try uninstalling the mareket update and then install the Prime update.
Updated perfectly fine for me from .15 -> .21
Used OTA Rootkeeper to keep my root
Only thing i've done is root, everything else is stock
C10 Serial if that helps
i thought the update isn't till tomorrow? ;o
http://forum.xda-developers.com/showpost.php?p=23409128&postcount=1
i checked anyways and i don't have any updates
-- Canada
edit:
never mind there is an update now...
IT seems like the Update isn't available for German devices, maybe others are also affected
Sent from my HTC Desire using XDA
To: babymatteo
Per your previous post. How do I re-lock booloader? I have a rooted prime, unlocked bootloader, and running a custom ROM. I have HDMI out problem which have recently materialized, can you post a link for a how to in this thread? Also, do you know if you relock bootloader, remove root, and install the orginal OTA update, can ASUS tell I had an unlocked bootloader with root if I RMA due to a faulty HDMI out?
Thoughts?
Thanks in advance.
Wave.
verdikt said:
so i have no mods on my prime besides root and atp tweak and it keeps failing....tried 3 times......i restored the scheduler and all but it still is failing....what gives. anyone else dealing with this??
also im getting this image...
http://www.box.com/s/d91b69252908ff677506
Click to expand...
Click to collapse
Probably OC and ATP tweak causing the trouble, because some system files (checked during install updated) are not standard any more
If you are rooted and you changed anything like deleting bloatware or changed your systemUI the update will fail... has to be stock
I have the same exact issue down to the dead android logo during 30% update process.
Again, NOT unlocked but ROOTED.
I have not modded any of the system file EXCEPT for the AGPS patch in the dev forum. I do not have the original files before the patch...someone help please.
Thanks,
babymatteo said:
Is your bootloader unlocked? If it is, you'd have to relock the bootloader and flash the stock recovery image.
Click to expand...
Click to collapse
You can't relock the bootloader and flashing a stock recovery would brick your tablet.
experiencing the same issue here I own a C2 model with locked bootloader, ota rootkeeper, ez overclock and some debloating, so I got no idea what to do lol
Same here.
Stock, rooted, bootloader locked.
I backed up *some* of the crap arrived with the device, tried to titanium them back, no dice.
Are we forever doomed to walk the planet with .15 when everyone will flash there <something-yummy-starting-with-Z-here>.350?
Meh.
is it possible to flash a stock .15 ruu from asus which would allow us to update? although that way I'm afraid we would lose root and would need to backup our data beforehand..
I had this problem on the .14 to .15 update also. Just reinstall the .15 update manually using this method you can get the .15 update from asus site just make sure you get the right version
Then try the OTA again after redoing the .15 and it finally should worked
I did what this person did on his post.
http://forum.xda-developers.com/showpost.php?p=23039742&postcount=1
Solved
gdavis480 said:
I had this problem on the .14 to .15 update also. Just reinstall the .15 update manually using this method you can get the .15 update from asus site just make sure you get the right version
Then try the OTA again after redoing the .15 and it finally should worked
Click to expand...
Click to collapse
Dude, you're awesome as sniffing cocaine off a stripper's behind.
Per your advice, I followed asus manual update guide (would have post link, but xda says I'm too noob to do so) after which I OTA'ed like a champ.
Thx mate.
If I take a system update will I lose root? I've blocked updates but was just wondering.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
Most likely.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
If you have made any system changes, you will not be able to accept it anyways. It will just fail.
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
Best practice is to wait and see if those that have taken an update are able to Root afterwards, if so then your good!
Personally... I'm just keeping my phone on the 10B firmware until a custom recovery comes. My phone runs great right now.
If for some reason we make it to the Android L update before we get an unlock, then I'm wait and see if it's possible to Root and unlock that prior to updating.
My S4 was on 4.4.4 and really being on 4.4.2 were not missing anything.
- Tapatalked from the G3
Matt1024 said:
If I take a system update will I lose root? I've blocked updates but was just wondering.
Click to expand...
Click to collapse
You would lose root.
It's a toss up of whether you would even be able to take the update.
Depends on how they check the file system. Definitely if you are running Xposed, you won't be able to OTA unless you go back to stock.
Somewhat OT, but I was a bit surprised to see that I kept root after a factory reset (TiBu borked myself into a bootloop). Just re-downloaded and installed SuperSU, and good to go.
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.
I successfully rooted my LG L70 with towelroot, but I have a problem now. I can't update the software on my phone from ms32310b to ms32310c. It downloads, reboots and appears to install and says system is up to date, but it's still at ms32310b and a couple days later says I need to download the update again. Will it not update because my phone is rooted now with towelroot? Does anyone know how I can maybe force the update so I can stop getting these update notifications? Thank you!
I seem to have this same problem but my phone is the ls740
lil-g-gamegenuis said:
I seem to have this same problem but my phone is the ls740
Click to expand...
Click to collapse
I guess we have to use lg flash tool to manually flash the KDZ update file, but I'm not sure if updating will unroot the device since the new version in my case doesn't support root.
well on my phone i have CWM so i could probably find a zip to flash
bogarty said:
I successfully rooted my LG L70 with towelroot, but I have a problem now. I can't update the software on my phone from ms32310b to ms32310c. It downloads, reboots and appears to install and says system is up to date, but it's still at ms32310b and a couple days later says I need to download the update again. Will it not update because my phone is rooted now with towelroot? Does anyone know how I can maybe force the update so I can stop getting these update notifications? Thank you!
Click to expand...
Click to collapse
if you root your phone mostly you do not get ota updates and if you get one and install it you lose root
Crom4rtie said:
if you root your phone mostly you do not get ota updates and if you get one and install it you lose root
Click to expand...
Click to collapse
This is absolutely correct. I rooted my LGMS323 with Towelroot (which worked beautifully I might add) but weeks later made the terrible oversight of approving an OTA update without thinking which nuked the root. I've been stuck ever since. Once you update to MS32310c there is NO EASY WAY of rooting your device (as of yet). The only way to reroot is to start over and downgrade from (c) back to (b) or (a) by flashing the KDZ as you mentioned. Because I'm without a machine at the moment and unable to do this I'm TRULY stuck. Don't be me! Stick with what you've got!
jaydeedub said:
This is absolutely correct. I rooted my LGMS323 with Towelroot (which worked beautifully I might add) but weeks later made the terrible oversight of approving an OTA update without thinking which nuked the root. I've been stuck ever since. Once you update to MS32310c there is NO EASY WAY of rooting your device (as of yet). The only way to reroot is to start over and downgrade from (c) back to (b) or (a) by flashing the KDZ as you mentioned. Because I'm without a machine at the moment and unable to do this I'm TRULY stuck. Don't be me! Stick with what you've got!
Click to expand...
Click to collapse
Thank you! I probably will. Unless of course they come out with a stable Lollipop rom, then I might be tempted to install Clockworkmod and check it out.
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
That's the Android 12 GPS fix it sounds like.
Google Pixel 6 getting 'Introducing Android 12' update
Many Google Pixel 6 series users are confused due to an 'Introducing Android 12' update ahead of Android 13, here is what's happening.
piunikaweb.com
Lughnasadh said:
That's the Android 12 GPS fix it sounds like.
Click to expand...
Click to collapse
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
OTAs are arguably the safest way to update regarding any danger to bricking devices. Any hoopla you may have heard about A13->A12 or A12->A13 bricking is via flashing not OTA updates. You will have to re-root/magisk. Those guides have been (should) updated for a13. But OTA updates within android 12 and to android 13 should not brick your device and should be totally safe. But once you are on android 13, you are on it forever. No downgrading. You can only move forward (for now).
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
pleiotropy said:
Thanks, any idea how to safely install the update? Is this Magisk guide still accurate?
Click to expand...
Click to collapse
Yeah, that guide is accurate but the "Install to Inactive Slot" method has been hit and miss for some. If you are on a custom kernel you also need to return to stock kernel to make it work as well.
pleiotropy said:
Thanks, I am still quite new to this so to confirm, the A/B partition method will not work? Would I just install the OTA and then re-root? I'm using Magisk Canary 24.3 if that matters
Click to expand...
Click to collapse
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Good point. Missed that he was on that.
tom1807 said:
Canary 24.3 does matter, it won't work. You need Magisk 25.200 or higher for A13.
Cheers
Tom
Click to expand...
Click to collapse
Thanks for the info, I will update Magisk and then try it
pleiotropy said:
Thanks for the info, I will update Magisk and then try it
Click to expand...
Click to collapse
Make sure to disable any Magisk mods that may need updating as well, but since you're just making a minor update from one July build to another July build I suspect you'll be ok. But it's still good practice to disable mods when updating to avoid potential bootloops.
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
pleiotropy said:
I recently received a message on my pixel 6 that a system update will be "automatically installed" on my device in 1 day. The update is 2.02 gb in size and it's listed as a "security update". Would this be the Android 13 OTA? I've disabled Automatic System Updates, but I'm afraid this will install and brick my phone/mess up my root. Is there anyway to prevent it from installing?
Click to expand...
Click to collapse
michaelrager said:
Hi,
I have the same issue (system security update 2.02 GB) bothering me everyday and I do not want to update my phone. I am rooted but am not sure what Titanium backup should freeze to stop this. Any ideas? I appreciate it. I do not want to have to re root etc, it took me months to successfully root .
Click to expand...
Click to collapse
Did you ever figure this out? Or what happened? I have updates disabled under dev but I got the same notification.
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
tbgakaadan said:
If anyone can respond, I just have root with systemless host enabled for adblocking. If the update goes through, worst case I just have to reroot?
Click to expand...
Click to collapse
Take the update. You'll have to root again.