I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Thanks, Iambedook. Every experience helps. Kingoroot got me into trouble once before in the past.
Can you flash back to 4.4 from 5.1.1?
iambedook said:
I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Click to expand...
Click to collapse
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
GigaSPX said:
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
Click to expand...
Click to collapse
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
pvcdroid said:
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
Click to expand...
Click to collapse
You may root, but I would advise against anything else. the Z5 Camera is most likely not compatible for our phones on 5.1.1, and neither is the FM Tuner. It's a whole lot I can't touch base on yet.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
I was able to flash back to 4.4.4 after i messed things up, but after going back to 4.4.4 i am struggling to get back to 5.1.1. The updates are not appearing, stating I am at the latest version.
I would also like a confirm if this. Because I'm sitting around and waiting for a rooted 5.1.1 copy for the phone. Im on 5.0.2 right now and all is working good but still waiting. Thanks all.
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Just uploaded a rooted twrp backup with real superuser ++++much more
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow!!! That sounds great, thanks Tiger
thals1992 said:
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Click to expand...
Click to collapse
Just an FYI, after I needed to revert to 4.4.4. I was struggling to receive updates to get back to 5.1.1. I had to use the Flashtool, 3-5 times to get the correct update prompts to appear. If anyone else had similar issues when reverting back, let me know, but re flashing repeatedly worked for me.
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow,
Download url please
immtu said:
Wow,
Download url please
Click to expand...
Click to collapse
Just scroll down to the z3v dev section.
I was actually able to flash the stock ftf coming 5.0.2. I had to flash it with default options the first time with it failing. I then found that I have to basically flash noting to clear the error on the phone by checking everything in exclude and the other exclude box where it shows its not displaying any files in the middle of the window.
Once that went through, I was able to upgrade from stock to .44 and then the the two updates for 5.1.1. After all that I reset to factory again to test on rooting the phone. I was too, able to obtain root with King Root. I was able to install zxrecovery and xposed with no problems. I'm actually used to King Root as I had to use it on the Verizon branded 7" tablet that didn't have any other possible methods previously. I also found that Busybox was slightly out of date (difference of 2.0) and installed to /sbin which wasn't too big of an issue.
Beyond that my phone seems to get pretty warm and typically complains about not charging even on a 2 Amp charger.
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Zandermc3 said:
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Click to expand...
Click to collapse
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
thals1992 said:
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
Click to expand...
Click to collapse
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Zandermc3 said:
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Click to expand...
Click to collapse
Thats why then. This is only for the Z3v the Verizon variant.
Hi there,
New to the forum. After several hours of reading and searching, I became bewildered enough to decide to register and post .
This thread looked promising. I'm currently on rooted 4.4.4 with this phone. I also have a custom recovery installed. Im trying to get to 5.1.1. As of right now, I assume my only option is to wait for a 5.1.1 ftf so that I can update, because the OTA updates won't work (phone reboots into the custom recovery and the update is interrupted).
Is there an easier way to get the OTA? Or am I stuck waiting for an ftf?
To be clear, my goal is to be on 5.1.1 with root. But at this point I don't think I can get to 5.1.1 at all.
Related
https://doc-0k-1o-docs.googleuserco...009/*/0BzrP5DWIlpplYjFOY1MwOXFNLWc?e=download
here is the ota zip
if we flash this can we flash 4.5.141 with rsd?
any answers?
I wouldn't count on it. The ZIP seems to contain what looks like the bootloader, or at least a piece of it (ap20bl.img). Who knows what might happen after that. Motorola said a downgrade is not possible.
I would just wait for the .145 fruitcake. Then switching back and forth should be safe and painless.
ok thanks for answer
Installed 4.5.145 for fun
blttalas said:
ok thanks for answer
Click to expand...
Click to collapse
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
sn0wba11 said:
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
Click to expand...
Click to collapse
Did you do this via the standard update or by flashing that zip yourself?
vikingarcher said:
Did you do this via the standard update or by flashing that zip yourself?
Click to expand...
Click to collapse
Standard
Su ota survival
Has anyone tried to install the update after activating the superuser ota survival option
Root after sys 4.5.145 update?
fdaconta said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
This response is from the developer thread. I would respond there but the policy for members with less than 10 posts is silly.
None of the existing preinstall methods (e.g. atrix-4g-moto-fastboot or superoneclick 2.3.3) work with 4.5.145.
sn0wba11 said:
Standard
Click to expand...
Click to collapse
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
vikingarcher said:
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
Click to expand...
Click to collapse
Came across a link at Android Central that used Voodoo OTA RootKeeper to restore --> Forgot I installed this awhile back; reinstalling app restored my superuser access
Re-rooted 4.5.145 after OTA
I successfully re-rooted mine last night using the pre-install method.
Read my topic here:
http://forum.xda-developers.com/showthread.php?t=2153422
From 141, to 145, back to 141.... and finally ended up with a working (and rooted) 145.
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Chimpdaddy said:
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Click to expand...
Click to collapse
you can try ot yourself,.but i reckon it will give you error while applying update.
Rootk1t said:
you can try ot yourself,.but i reckon it will give you error while applying update.
Click to expand...
Click to collapse
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Chimpdaddy said:
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Click to expand...
Click to collapse
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
bjrmd said:
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
Click to expand...
Click to collapse
I know, so lazy, if I wait long enough 4.4 will come around and that might keep root!
Nobody's read a successful account of this working then? I may as well just try it and see...
Possibly
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed.
I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root.
If you have CWM or TWRP installed then it won't let you update.
adielee said:
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed. I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root. If you have CWM or TWRP installed then it won't let you update.
Click to expand...
Click to collapse
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Cat McGowan said:
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Click to expand...
Click to collapse
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Rootk1t said:
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Click to expand...
Click to collapse
I would also recommend to flash a pre-rooted 4.3 from scratch for performance and less issues, but if you have a lot of apps installed and everything set up the way you want it can be a pain in the a$#.
Also the OP doesn't want to flash. But if he can it means that the OTA won't install because he has a custom recovery.
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2)
It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
adielee said:
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2) It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
Click to expand...
Click to collapse
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Nope
Cat McGowan said:
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Click to expand...
Click to collapse
Well, I tried it, thinking the worse that could happen is that it would abandon the install, but unfortunately it went right through and upgraded to 4.3 and I lost root
I'd put it into OTA survival mode but not into system/apps. I had no xposed or recovery anything, just root.
So there we go. Thanks for the discussion guys, hope this is useful to someone else.
How do I root it in 4.3? Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?t=2703774
Sent from my SGP311 using xda app-developers app
Hi all,
I'm a bit of a n00b at this, so please forgive me.
I started with Android 4.1.2, Kernel 3.4.0-g298631f-02047-gec59411, build 10.1.C.0.370.
I rooted it using Doomlord's easy-root and then when attempting to flash custom recovery, I accidentally flashed some other .img and the tablet wouldn't even turn on. I cried. Like, a few good tears.
Went online, found out I wasn't screwed, and figured out how to flash SGP312_10.4.B.0.577_VMo DE_1273-3719_WIFI312G.
But, as I said, I lost root, and am confused about how to downgrade back to 4.1.2 properly without bricking.
Here is my current info:
Version 4.3, Kernel 3.4.0-g1b44cd5, build 10.4.b.0.577
In this thread, under "Downgrade your rom" and "back to 4.1.2 and rooting" it says "if you're in 4.3, Flash this SGP 351 4.1.2 FTF using Flash Tool and it will be booted in 4.1.2. if you have different Variant downgrade to your Variant FTF file"
What is a variant FTF file? Can I just use any SGP 312 4.1.2 FTF? Does anyone know a safe one to use?
Thanks!
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
worf_1977 said:
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
Click to expand...
Click to collapse
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
UberBaumer said:
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
Click to expand...
Click to collapse
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Cat McGowan said:
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Click to expand...
Click to collapse
THANK YOU, SIR.
I really appreciate it!
Back onto 4.1 and just rooted again. Now I just need to manage not screwing up installing CWM like I did last time!
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
UberBaumer said:
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
Click to expand...
Click to collapse
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Cat McGowan said:
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Click to expand...
Click to collapse
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
UberBaumer said:
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
Click to expand...
Click to collapse
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Cat McGowan said:
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Click to expand...
Click to collapse
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
UberBaumer said:
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
Click to expand...
Click to collapse
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Cat McGowan said:
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
Damn, maybe I was a bit too hasty in rooting my tablet; why is it that I can no longer to OTA updates? If I were to buy SuperSU PRO (for survival mode) is there any benefit to me? I see that it allows for OTA updates.
I am currently rooted via Superuser (by clockworkmod).
When you say I'll need to install 4.2.2 by flashing, you mean through Flashtool, right? Which build should I get (and where, one of the development forums)?
Is the reason why one is advised to install custom roms via recovery mode in order to maintain root access (which I'm assuming doesn't happen if you flash through Flashtool)?
Something I forgot to mention earlier is that I did unlock the bootloader. I'm not sure if that helps or hinders me at this point.
Thanks again for taking the time to answer all my questions. I really love this new toy, and I'm so terrified of bricking it.
Cat McGowan said:
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
UberBaumer said:
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
Click to expand...
Click to collapse
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Cat McGowan said:
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Click to expand...
Click to collapse
Thank you again my friend.
Is there a list of apps that are safe to uninstall, or, rather, a list of apps that I shouldn't tinker with (for fear of uninstalling an app that has a dependency on something critical)?
Also, I'm on the Google Play store and I see both Titanium Backup Pro and Rom Toolbox Pro. Should I buy both? If you had to buy just one, which would it be?
My main goal is to just make the smoothest experience possible. I want to take maximum advantage of the hardware in the tablet and have as few unnecessary programs running as possible.
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.
Ok.. so.. I keep seeing people saying there is a way to root still if you are on GOC1.. but I can't find anything that says what that way is. I also see 5.1 roms for this phone, but nothing that says how to install the bootloader it requires to install them. On my old phone, a Droid X2 you had to root before you could install a bootloader before you could install a rom. I am not seeing any straight up guides on here for working with this S4.
What I really want is just a basic root, so I can uninstall all the hardcoded crapware on this phone (NFL Mobile, Trip Advisor, etc..)
Short of that I want to install CM 12.1, which is probably a better route anyway, but the page for that says you must be on so and so bootloader without telling you how to INSTALL said bootloader. I'm totally lost here, things were a bit more straight forward on that old phone.
Edit: Yeah, I think what I really want to do is install CM 12.1, but I don't even know where to start.
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
skepticmisfit said:
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
Click to expand...
Click to collapse
Kingroot doesn't work. I don't know what its saying in the orange text after I run it since its not in english, but it doesn't work.
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Try getting KingRoot desktop version 3.0 I just used it on Version I545VRUGOC1 that I did the OTA update with and got it rooted I can use Titanium Backup to remove all samsung Knox and other bloat wear.
bangdosa said:
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
Click to expand...
Click to collapse
I gave kingroot another try since I had rebooted a couple of times since making this post, it worked this time! Huge thanks for that tip.
XxD34THxX said:
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Click to expand...
Click to collapse
Thank your for that. Flashfire is in the process of installing the rom. We'll see how it goes.
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
DallasDave said:
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
Click to expand...
Click to collapse
Just use the KingRoot app to root. It worked for me on first try.