Restore Z2 tablet back to factory / stock after root? - Xperia Z2 Tablet Q&A, Help & Troubleshooting

Hi,
I rooted my Z2 tablet a few days ago and have found that I don't really need the advantages it brings (from what I can tell). SO - I want to get it back to the way it was when I first opened the box.
I have seen threads about different devices and how to restore them to factory or stock (??), but they seem to call for specific files or flash software. So that brings me once again to this forum to figure out whether anyone can direct me to some instructions on how to do this. I figure it shouldn't be too hard. Just being careful.
Thanks very much for the advice once again.

I think if you flash the rootable kernel again, you could use an unrooting tool to undo the root. I'm also aware that there are files that you can flash to re-lock the bootloader (I once did this with an Xperia mini pro, although I'm not sure if such file exists for this tablet) but the DRM keys are lost forever a.f.a.i.k. But at least if you manage to re-lock the bootloader you will be able to install F/W upgrades through official ways again.

degraaff said:
I think if you flash the rootable kernel again, you could use an unrooting tool to undo the root. I'm also aware that there are files that you can flash to re-lock the bootloader (I once did this with an Xperia mini pro, although I'm not sure if such file exists for this tablet) but the DRM keys are lost forever a.f.a.i.k. But at least if you manage to re-lock the bootloader you will be able to install F/W upgrades through official ways again. Anyhow, you won't be able to restore to (more or less) factory status without at least flashing a couple of files.
Click to expand...
Click to collapse
THank you for the response. Unfortunately i'm not even sure how I would go about flashing 'the rootable kernel'.... Feeling a bit foolish for getting into this actually.
From what i'm reading, it seems like I need to get the stock software and start again. So i'm looking for the 'FTF' for my tablet, which is a SGP511. Not having any luck though.

Which was the process that you followed to root it?

degraaff said:
Which was the process that you followed to root it?
Click to expand...
Click to collapse
It was on another site - can't remember which. It got the clockwork mod installed. I think? Or was that just a recovery thing? No idea.
I'm actually now just doing a factory reset to see what happens, and it said 'root access possibly lost' in the process, which I thought was a good sign. Guess i'll keep tinkering with enough caution to eventually get the warranty back in tact.
Hopefully the loss of DRM doesn't effect the warranty.

In that case I guess you will have to download a firmware ftf file of an official unmodded firmware (preferably one of your region but I think especially if you have the wifi-only version it doesn't matter much as long as it contains the interface and input languages that you need), and install (or "flash") that using Flashtool. After that the root will certainly be gone and if you could then find a file to relock your bootloader I think your warrenty will be fine. I honestly don't think that Sony service and repair personel will check for DRM keys every time before repairing a device.

UPDATE
Factory reset appears to have gotten things back to normal. My plan is now just to unroot using an unroot tool (app i guess?) and then to lock the bootloader some how as well.

fearofbirds said:
Factory reset appears to have gotten things back to normal. My plan is now just to unroot using an unroot tool (app i guess?) and then to lock the bootloader some how as well.
Click to expand...
Click to collapse
So it's certain that the tablet is still rooted at this moment? Some superuser apps have an option to do a full unroot, such as SuperSU, you could try that

That's great. I think that's sorted it out. SuperSU had the full unroot option and it looks like it's all sorted.
Thanks for the help.

Related

[Q] Backing up and rooting/unlocking bootloader question.

Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
​Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
​To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium

[Q] Firmware question

Hey guys, I've currently got some wifi issues that I believe are firmware related, I've currently got 17.1.1.A.0.402 but would like to revert back to 17.1.A.2.36 ideally without having to factory reset my phone, I'm also not sure it would go back to 17.1.A.2.36 even if I reset it, I didn't note what firmware it had before I upgraded the firmware so it might take it back to an even earlier version ideally I just want to step back one firmware update but I'm not sure if this is possible? I noticed there's an option on PC companion to reinstall all the updates again although I don't know if you can choose which updates to install or whether it'd just install all the updates so far including 17.1.1.A.0.402 which would be no good. It also said I would lose all my phone data which is not ideal. I was considering rooting my phone and getting an older firmware installed then but tbh I don't really have a lot of knowledge on the subject and I'm not sure if that's even possible. If anyone could help help me out that would be great, even if it's to conform that factory resetting is the only option as ideally I don't want to lose all my data
If you're simply looking to root the device at the .402 firmware, then have a look at this thread. I personally did the same steps on my international D6503, and now have root access, my own TA backup file, PhilZ + TWRP recovery modes, and a locked bootloader. Originally my intent was to downgrade firmwares and us a root exploit that way, however, the 'EasyRoot' method has saved a lot of trouble and my firmware version has not needed to change at all.
That said, if you're still adamant about rolling back firmwares, I'd suggest that you have a look here. Norti has posted a fairly comprehensive set of instructions, as well as a list of firmwares for different versions of the Z2. Although I haven't rolled it back, I have heard that using flashtool to jump to different official firmware versions will not wipe data if you choose to not select WIPE USERDATA, since they're performed in a way that is similar to OTA updates (might need confirmation on this one). Some of the posters in that thread have claimed that as long as your device matches the firmware, loading up a different region's firmware shouldn't have any detrimental affects (i.e. an international phone using Taiwanese/German versions), but that's another piece of information I can't confirm since I haven't tried it.
TL;DR you don't have to change firmware to root, but you can if you really want to. Neither method should touch your SD card, and flashtool should be able to choose what should or should not be wiped.
1740
First of all thanks for the informative response! I tried resetting my phone anyway and it already had 402 installed at stock so unfortunately I can't do it that way, I think I'll try rooting my phone now as I've wanted to do it for a while and I might as well now seeing as I basically have a fresh phone with nothing installed on it. I think I'll follow this guide since I already have an unlocked bootloader: http://forum.xda-developers.com/showpost.php?p=53220418&postcount=2 However I was wondering when I can flash the older firmware, would it be during of after I've rooted my phone?

[Q] How to update 4.4.2 root but no recovery

Hi!
I have the SGP311 with the 4.2.2 Version of Android. Back then I rooted it using the tool VRoot (i think that was the name).
As all I wanted was root for TiBackup I left it at that. Stock ROM, some modifications through root access, but I saw no need to go further.
I would now like to update. OTA does not work, either because I am root or because the bootloader unlock (which I think happened during the root process).
There are so many guides out there, some contradictory or rather relying on going from certain versions to the newest.
What is my best bet?
Unroot and Relock, OTA update, then re-root? Is there a Guide to that?
Or how do I get a recovery on there easily? Guide?
Then assuming I have recovery on, what do I flash. Sony has grown on me, so I am happy with a stock rom or something very close to it, if I can root it for my mods.
What is the least dangerous way to get this tablet up to date?
Thanks for your help!
Walter_White said:
Hi! I have the SGP311 with the 4.2.2 Version of Android. Back then I rooted it using the tool VRoot (i think that was the name). As all I wanted was root for TiBackup I left it at that. Stock ROM, some modifications through root access, but I saw no need to go further. I would now like to update. OTA does not work, either because I am root or because the bootloader unlock (which I think happened during the root process). There are so many guides out there, some contradictory or rather relying on going from certain versions to the newest. What is my best bet? Unroot and Relock, OTA update, then re-root? Is there a Guide to that? Or how do I get a recovery on there easily? Guide? Then assuming I have recovery on, what do I flash. Sony has grown on me, so I am happy with a stock rom or something very close to it, if I can root it for my mods. What is the least dangerous way to get this tablet up to date? Thanks for your help!
Click to expand...
Click to collapse
Vroot would not have unlocked the tablet's boot loader, so are you sure it is unlocked? And have you tried using Sony PC Companion to update the firmware? I was going to recommend trying to use Sony Mobile Update Service, which I preferred over PC Companion, but it appears Sony stopped supporting it.

[Q] Removing Root to do OTA Lolipop?

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.

Need a bit of input?

Okay,I posted recently about my old z ultra. I bought the z ultra off Craigslist and it was updated to 5.0.
Anyhow the screen got the dreaded 'hairline' Crack in the screen and Sony covered it.
They sent me a new phone international version and the first thing I checked were the hidden functions in the dialer. Rooting status says yes or bootloader rather. Also the phone is still running 4.3. I did some searching and found a root method. I don't want kingroot or any Chinese crap.
Do I need a computer? Can I root using towelroot? Install busboy? DL cwm and flash via the phone?
harley1rocker said:
Okay,I posted recently about my old z ultra. I bought the z ultra off Craigslist and it was updated to 5.0.
Anyhow the screen got the dreaded 'hairline' Crack in the screen and Sony covered it.
They sent me a new phone international version and the first thing I checked were the hidden functions in the dialer. Rooting status says yes or bootloader rather. Also the phone is still running 4.3. I did some searching and found a root method. I don't want kingroot or any Chinese crap.
Do I need a computer? Can I root using towelroot? Install busboy? DL cwm and flash via the phone?
Click to expand...
Click to collapse
Nope. Towelroot does not work on 4.3. I hope my phone doesn't force a system update. I'm still 4.3 for now.
Not a gpe edition either
Screw it. I think I'll just take the update
This is why im tempted to multi post. A moderator warned against multi post. Ive had this post up for a few days now and ive not got one answer.
I need to know about 4.3 jellybean. My phone was shipped with it. Do i have to use flashtool? Whats the first step? I haven't taken the update. Im still 4.3
PLEASE ANSWER
Hello there lonely islander! I'm randomly passing through with my ship, and I caught your smoke signals.
I can't really remember the root situation on 4.3, but there were quite a few rooting tools in the cross-development section. Not sure if those were for 4.1 or 4.3 though. I'll do some digging and I'll be back.
What's the firmware version? .290?
EDIT: Okay, so I've done some searching, and this method was the one that people used back on 4.3. It's not perfect though since it required the use of Vroot, which is/was the same type of rooting tool as Kingroot, so that's probably a no-go.
Another way of doing it would be to downgrade to a firmware that's supported by towelroot. That would be 4.1? 4.2? Find out which version is compatible and find that firmware FTF in the Dev section. You'll probably have to do some digging since a 4.x ROM thread will be quite old. Flash it using Flashtool and then root with towelroot.
But...
What's your plan now? Backup the TA partition (DRM-files) and then unlocking the bootloader, update to 5.1.1 and easily root again through fastboot since your B/L is unlocked? Or are you planning to keep the bootloader locked and live the rest of your life on an ancient Android version?
EDIT 2: Have you tried this tool on 4.3? It's based on Towelroot, but it's customized for rooting Xperia devices. I think that maybe, probably, it'll work on 4.3. I don't know, so go ahead and just try it unless you've already done it.
EDIT 3: Okay, so it looks like the tool provided in "Edit 2" should be compatible with Android versions up to 4.4.2 before being patched by Google/Sony in 4.4.3/4.4.4 (KitKat), so it should in theory work on 4.3.
EDIT 4: OKay, I have no idea what's real anymore. I just stumbled upon this post from that thread:
v 12.4 worked like a charm on my Xperia Z Ultra C6802 (4.4.4).
Did TA backup. Installed SU chainfire and updated binary in normal mode. Got write to external SD card ability on my Total Commander without any SDFix app. Thanks.
Click to expand...
Click to collapse
So... just go ahead and try it. If it fails, then you can downgrade using Flashtool if you're into that.
Build is 136. No,you are correct. King root is king crap. Im not going back there. The bootloader status says yes. Will i have to use the sony web site to unlock bootloader? Yes, i want root and i want too flash roms.
So,can i just root and install safestrap,superSU or do i have to unlock BL.
I could update to 4.4.....
Okay. Forget what i want. Tell me the steps i need to take. Im on 4.3. Build136. Yes i wanna root and i wanna rom..
harley1rocker said:
Okay. Forget what i want. Tell me the steps i need to take. Im on 4.3. Build136. Yes i wanna root and i wanna rom..
Click to expand...
Click to collapse
Alright. First step is to test and see if that root tool I linked to in my previous post works. If it does, great. If it doesn't, it'll get a little more time consuming.
But the important question here is: Do you care about the DRM files? They control mostly the camera which will be a little affected by the loss of the keys. It'll happen either way when you unlock the bootloader, but backing them up allows you to restore them later if you ever re-lock the bootloader for some reason.
So you can either:
1. Backup the DRM files, but doing that requires root, which is fairly hard to obtain with a locked bootloader, which you are currently witnessing.
2. Ignore the loss of the DRM files and unlock the bootloader right now. When you have unlocked the bootloader it'll allow you to boot and flash custom code, like a custom kernel with recovery (CWM/TWRP/Philz) which again allows you to flash SuperSU and be done with it, or flash a different ROM. It's the easiest way, but you'll lose the DRM keys. They might become handy if you have to send your device in for repairs down the road (if you have any warranty left, that is)
So what you need to decide right now is what you want to do.
Should i update? the next update is 4.4.2. I could take it then use watevr roottool. So root first then unlock bootloader
harley1rocker said:
Should i update? the next update is 4.4.2. I could take it then use watevr roottool. So root first then unlock bootloader
Click to expand...
Click to collapse
No, just try the root tool right now while you're on 4.3. If it works, it works.
Did it work?
Im going to attempt here in a min
But first my good man,in what order do i do this?
Root first,unlock BL,install recovery?
Root bootloader status says yes..do i need to mess with it?
I updated to 4.4.2. Towelroot does not work on any of them
harley1rocker said:
Im going to attempt here in a min
But first my good man,in what order do i do this?
Root first,unlock BL,install recovery?
Click to expand...
Click to collapse
Yeah, root then backup the DRM files and then unlock the BL, then install recovery.
harley1rocker said:
Root bootloader status says yes..do i need to mess with it?
Click to expand...
Click to collapse
What yes? Bootloader Unlock allowed: Yes or Bootloader unlocked: Yes?
harley1rocker said:
I updated to 4.4.2. Towelroot does not work on any of them
Click to expand...
Click to collapse
Alright, now we know.
If bootloader status says YES on unlocked, then it's already unlocked, and we've wasted a bunch of time! If it's already unlocked, then just install recovery.
Bootloader unlock allowed:yes...... So i take it,its not.
Can i use flashtool? I tried sony "official " way and i did NOT understand it. So ive read into flashtool and it seems easier.
If i get a recovery on this thing im good from there.
I dont understand the steps. On Samsung note devices its root,safestrap, SU then happy flashhing.
This device is crazy confusion
harley1rocker said:
Bootloader unlock allowed:yes...... So i take it,its not.
Can i use flashtool? I tried sony "official " way and i did NOT understand it. So ive read into flashtool and it seems easier.
If i get a recovery on this thing im good from there.
I dont understand the steps. On Samsung note devices its root,safestrap, SU then happy flashhing.
This device is crazy confusion
Click to expand...
Click to collapse
OK. Here is what you need to know and do.
1- you didn't need to upgrade. A towelroot variant would have worked.
2- you don't need to unlock bootloader.
3- you need to install, from a PC onto your phone, what's called Xzdualrecovery, which is essentially a recovery. Google it and download the latest installer for this phone. You need to enable USB debugging on the phone so it can be installed from the PC. When your start the installer there is an option to instal AND root. This tool comes with the variant of towelroot tha can properly root your phone, if your OS date is before June 7 2014.
If you need help with these steps message me.
Thank u najoor. I have only updated to 4.4.2. I tried towelroot. Didnt work. I have a c6802. So im completely stock and your saying theres a tool out there that can root and install recovery from a pc.
Flashtool? Could you provide a link?

Categories

Resources