[Q] Upgraded to .244 and never lost root? - Xperia Z Q&A, Help & Troubleshooting

This isn't an issue, but I thought it was odd and I'm wondering if anyone else has seen this?
I got the OTA to upgrade my 6602 to .244 firmware (only 45.1 MB) so I bit the bullet and upgraded after reading DooMLoRD's method of rooting .244. I started Flashtool and plugged in my phone to start the whole process, only to see my phone screen show the SU message asking if I wanted to grant access. I'm looking under About phone and it says "Your device already has the latest available system updates" and the Build number is 10.3.1.A.0.244. Titanium works and SU says I have several apps that have SU access.
I'm certainly not complaining, but I thought the .244 upgrade broke root? Or am I completely missing something here?

when upgrading by OTA, keeping root is normal. you loose the root when upgrading with PC comp for example.

sensei_sai said:
when upgrading by OTA, keeping root is normal. you loose the root when upgrading with PC comp for example.
Click to expand...
Click to collapse
Ahh, OK, thanks!

Related

[Q] How to perform OTA 4.2 update to a rooted Nexus 7?

I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
hinsdale1 said:
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Click to expand...
Click to collapse
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
volarchico said:
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
Click to expand...
Click to collapse
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
2) I would like to know more about how you avoided this issue described in this thread here with stickmount not functioning with v4.2 because of the new mulituser framework that causes it no longer to see files in the mounted folders.
Thanks for your help and to anyone else that chimes in... any help is appreciated. Again sorry for being stupid.
hinsdale1 said:
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
Click to expand...
Click to collapse
i tried with OTArootkeeper app. but it don't update.... at restart for installing, it gave a black screen with android in the middle, with a RED icon inside it...... then it restart and 4.1.2 is always there
Perhaps these questions are so rudimentary that they hardly seem worth bothering with - but for some of us, these hacks and the info being thrown around in here are pretty confusing at times. I would be very grateful to anyone with some insight willing to help out?.
i found that this could be a problem with recovery mode... infact if i tr y to restart in recovery, it gave the same error...
i rooted with toolbox, and i'm thinking that it could have removed my recovery... now i'd like to try to recover the stock recovery with the same tool... but i'm not sure about that.
We seem to have veered off topic a bit here (at least for me)... so let me re-post the questions and beg again for mercy from any kind soles who can offer some advice?
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet?
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Bueller...... Bueller...... Bueller?
Hi! Last month I did the 4.1.2 OTA update. I was rooted but on stock. It updated with no problems. I used Voodoo OTA rootkeeper, restored the root, and either renistalled super su, or just updated the binary. Can't remember.....But I did lose my custom recovery. Didn't realize it till tonite when I went to do the 4.2 update.
So to your question. I forced the OTA 4.2 update. And it downloaded. I made sure voodoo rootkeeper was set to save the root. Then let it install. It rebooted. I opened voodoo, restored root, was asked to update super su binary, accepted. Still not rooted till I rebooted.
So far I have root, and am on 4.2 JB. So my goal was to get my custom recovery back on. Install goo manager from market. Open it, go to the settings button top right, it will give you the choice to install open recovery script. TWRP- Then it will ask you twice are you sure you want to do this and reboot? Say yes. Mine did not reboot and it looked like it did nothing. So, I flipped into recovery and Teamwinn recovery was installed. I made a backup, and rebooted.
Good luck!
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
hinsdale1 said:
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
Click to expand...
Click to collapse
Hi hinsdale,
Have you tried updating to 4.2 yet? Also i heard that if you update SuperSU to version 0.98 the latest version it could cause issues and you will have to reflash the device.
Thanks,
JBIRD
Thanks,
JBIRD
4.2 OTA already loaded, lost root
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Hi hinsdale! I am not a techie- I just learn as I go and read, read, read.
So, my voodoo app has 4 checks in the boxes. I seem to remember only 3 boxes checked when I did the update, but I'm not sure. It would make sense that all are checked.
After I updated, I opened the voodoo app first, and there is a box that says restore root. Then it asked if I wanted to update the su binary. Did that, still not rooted according to Tit. BU. Rebooted, then I was rooted. Good luck with your update.
I'm sorry I can't tell you how to run the initial save root on voodoo. I did it a while ago and don't remember, but it was not hard. Very easy.. Just make sure you Read, re- read, and read again before you do any modifications to your tablet. Know the possible bad outcomes, and be prepared to trouble shoot. This site is very good about helping you out if things go wrong. That's why it's a very good idea to be aware of the possible bad outcomes. The only way to know is to READ-READ=READ!
Did I mention READ??? lol. That's how I figure stuff out. If you read about others mistakes, you can avoid them. I also wait a day or 2 to see how it goes for others before I attempt modifications. That includes new roms. You never know what goes wrong until someone is the guinea pig! I am not techie enough to be the guinea pig!
paulie7880 said:
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Click to expand...
Click to collapse
same thing here...I tried to use TWRM to flash SU but it seems that after going into recovery using TWRM I can't see any any file or folder on my SD except 3 folders???? Can someone please help us....
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
sashusmom said:
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
Click to expand...
Click to collapse
Nexus Root Toolkit
The OTA update downloaded to my cache folder, I moved it to my sdcard. Wouldn't install since I had to fix a couple of files I had edited. So once those 2 files were fixed it installed just fine. Haven't had any issues yet.
The same on here...
But I guess it is better until they fix all this bugs they are reporting.
I'll wait until then.
Sent from my Nexus 7 using xda app-developers app
Updated to 4.2
Hi have updated the nexus to 4,2 and used Voodoo OTA Rootkeeper to keep my root followed the instructions as I did when updated to 4.1.2,my Nexus appears to be rooted superSu is working also stickmount sees the usb but it will not show any files on the sd card any help here please to get it to see the files on the sd card, thanks for your time
Nick
i dont post often as i am usually here looking for help. this time i get to help
i just downloaded and installed 4.2 OTA.
if your nexus was previously unlocked and rooted, it will download and install just fine. however you will lose root, but KEEP the unlocked state.
to root it again, you must goto "about tablet" and tap your build number 7 times to become a developer, this is not a troll, i got this info from another thread on xda.
then using the nexus root toolkit 1.5.4 with modeltype set to "android *.*.* any build", just do the root procedure.
reboot and ur in business, no need to update supersu, and busybox will still be installed already.

Will ota update lose root?

So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Sent from my LT25i
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
yuskhayru said:
So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Click to expand...
Click to collapse
I don't know about the latest update but I've previously done OTA updates before and kept root (I've got a Xperia T not V).
This thread was helpful at the time - http://forum.xda-developers.com/showthread.php?t=2021150
ci6i said:
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
Click to expand...
Click to collapse
I also had no OTA available so used PC Companion to go from 9.1.A.1.140 to .141 on my Xperia T. I don't know the differences between XT .141 and XV .145 but was able to regain root using Bin4ry's Root Many Android method
http://forum.xda-developers.com/showthread.php?t=1886460, it might work for you.
ci6i said:
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
Click to expand...
Click to collapse
since u has already update to .145, try this bin4ry method : http://forum.xda-developers.com/showthread.php?t=1886460 and i think it might work. i dont have time to test it yet.. im outstation doing my work:angel:
yuskhayru said:
So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Sent from my LT25i
Click to expand...
Click to collapse
if you perform OTA update (via PHONE), you won't loose anything, actually USUALLY you don't loose anything, and of course, using root keeper...
that's totally obvious when you use PC Companion, you will loose root..
And for regaining root access, use DoomLord EasyRootKit, which is now available in Android Development Section, it actually covers ALL devices, including V
wish you luck
ok. ive try update it via OTA, while keep the root access using voodoo rootkeeper, but no success. the main problem here is ive installed CWM. i for got about this "Keep in mind that at the moment installing CWM will broke OTA updates, even if you unroot and/or remove CWM." so there is no chance to update it via OTA anymore right?:victory:
yuskhayru said:
ok. ive try update it via OTA, while keep the root access using voodoo rootkeeper, but no success. the main problem here is ive installed CWM. i for got about this "Keep in mind that at the moment installing CWM will broke OTA updates, even if you unroot and/or remove CWM." so there is no chance to update it via OTA anymore right?:victory:
Click to expand...
Click to collapse
CHANCES are always CHANCES, so you have to try them
otherwise we wouldn't call them "Chance"
but, in theory, with aforementioned conditions, it's hard to believe that you will be able to update via OTA...

[Q] Update Broke Root, Note 3 is now not rooted, but root is installed

So, the situation is a bit weird. About a week and a half ago, some update came out for my AT&T Note 3, and after declining, later it forced me to install it. After installing, it seemed to have disabled root, but I still had the custom icon show up when it booted, and root functions were disabled. It was as if root was not uninstalled, but disabled. I've tried re-rooting the normal way, but that gives a fail when I try to use the OneClickBin application. I haven't tried skipping that and installing root for fear of bricking the phone on some incompatibility. If someone else has this problem or has solved it, please let me know what you did or give any advice you can. The ideal result would be for my phone to end up back in the stock firmware, updated and ready to root as if nothing was wrong. I'd also appreciate it if anyone can give me info on the update that broke it, so I can check for a root method which is compatible with it. Thanks in advance.
Ralkero said:
So, the situation is a bit weird. About a week and a half ago, some update came out for my AT&T Note 3, and after declining, later it forced me to install it. After installing, it seemed to have disabled root, but I still had the custom icon show up when it booted, and root functions were disabled. It was as if root was not uninstalled, but disabled. I've tried re-rooting the normal way, but that gives a fail when I try to use the OneClickBin application. I haven't tried skipping that and installing root for fear of bricking the phone on some incompatibility. If someone else has this problem or has solved it, please let me know what you did or give any advice you can. The ideal result would be for my phone to end up back in the stock firmware, updated and ready to root as if nothing was wrong. I'd also appreciate it if anyone can give me info on the update that broke it, so I can check for a root method which is compatible with it. Thanks in advance.
Click to expand...
Click to collapse
You got the update to MJ5, try using Kingo Root.
I'm noticing that Kingo Root's version page does not list the SM-N900A model. We're sure it's supported, right?
Yup! I used it on mj5 update
Solarenemy68 said:
You got the update to MJ5, try using Kingo Root.
Click to expand...
Click to collapse
Thanks, that worked.

[Q] XT1068 OTA Lollipop update failing

Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
I can confirm that ota update can be performed on rooted phone .I was thinking that is not possible but I was curious and tried.
I was on unlocked bootloader and rooted KK , german firmware 21.85.23 with instaled xposed framework and gravity box.
Update was successful without any error and for now everything work ok.
Loganberry said:
Today my XT1068 offered me the 22.26.1.en.GB update, but it's failing to install.
The phone reboots and attempts to install the update. The progress bar gets to approximately 1/4 to 1/3 of the way across before a red triangle appears and the phone reboots back to KitKat.
My phone was rooted (using SuperSU), but I used SuperSU's built-in clean-up feature to unroot my phone before applying the Lollipop update.
The bootloader is unlocked, but the recovery is stock; I did not install a custom recovery but instead booted TWRP temporarily to install SuperSU.
I'm comfortable fiddling with adb and fastboot, and with digging around the filesystem. Any suggestions of where I can look to find any error messages which might shed some light on why the update failed? Could the failure be related to the previous rooting of my phone, or could something else be breaking the update?
Click to expand...
Click to collapse
flash the GB 4.4.4 in my signature then try to update OTA again
dpdp73 said:
@Loganberry
Have you modified /system files in any way?
If yes you have to restore them back.
If nothing helps, with unlocked bootloader it's propably much faster to just flash your stock firmware again and do ota than to search why it doesn't work.
Click to expand...
Click to collapse
reefuge said:
flash the GB 4.4.4 in my signature then try to update OTA again
Click to expand...
Click to collapse
Yeah, I'd forgotten about Busybox and a couple other apps which modifed /system. Reflashing from scratch was the easier option.
I flashed GB 4.4.4 as advised and the Lollipop update then applied without any problems. Thanks for the assistance.

July 2015 OTA update concern.

I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
fleggett1 said:
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
Click to expand...
Click to collapse
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
dirtydodge said:
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
Click to expand...
Click to collapse
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
fleggett1 said:
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3149146
If you want root, go to the OP in that post, scroll down to step 4 or the notes section and download the "downgrade to nce.zip" flash that in odin "ap" slot. Then root with towel root. After that you can either download titanium backup and fees the ota's or use that same thread to upgrade to the OF2 version and keep root.
Edit:
If you want to just take the OTA's and not root your phone then still download the "downgrade to nce.zip" flash in odin but don't root. The ota's will push through with no problem then. But you won't be able to downgrade and root if you take the OTA's all the way up to oc4 i believe.

Categories

Resources