Any Idea to root the 4.3 on XTZ? - Xperia Tablet Z General

Does anyone have an idea how we can root 4.3? So far everything failed ...
Testing:
1 root Bin4ry
2 VRoot
3 Kingo root
All to no avail ...

I need this too. And with out unlocking bootloader.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

wait tomorrow ... today i don't think they upload the files to work root on our xperia tablet z 4.3

Root .67 with vroot, protect it with SuperSU survival mode/OTA root keeper and the update with OTA. Presumably you will get 4.3 with root.

I agree with Rootk1t. If your current firmware does not have root access, then use the Vroot tool to gain root access. After gaining root access, install SuperSU and turn on its Survival mode and Install SuperSU into /system settings. Make sure the Install SuperSU into /system setting is greyed-out before updating to 4.3 via OTA. Do not update via Sony PC Companion, Sony Mobile Update Service, or by flashing FTF -- doing so will likely cause you to lose root access. That is what happened to many people during the last firmware update. People who had root access with SuperSU installed as described above and updated via OTA, retained root access. People who had root access but updated via Sony PC Companion, Sony Mobile Update Service, or by flashing FTF, lost root access. Luckily, the Vroot tool became available and allowed those people to regain root access. There is no guarantee that the Vroot tool will work with the 4.3 update. Of course, I could be wrong.

Ther's no OTA update yet. Maybe in January or so. So not root OTA at this time
Sent from my C6603 using xda app-developers app

Cat McGowan said:
That is what happened to many people during the last firmware update
Click to expand...
Click to collapse
it happens because Pc-companion and other software clears system folder where SU binary is kept. OTA update only updates files needed for new firmware to work thats why root is preserved.

worf_1977 said:
Ther's no OTA update yet. Maybe in January or so. So not root OTA at this time
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
My XTZ is working fine with 4.2.2 and updating to 4.3 is not going to increase my income or improve my love life, so waiting for the OTA is not a problem for me. :laugh:

Cat McGowan said:
My XTZ is working fine with 4.2.2 and updating to 4.3 is not going to increase my income or improve my love life, so waiting for the OTA is not a problem for me. :laugh:
Click to expand...
Click to collapse
I always keep a backup of a rootable firmware, just in case

worf_1977 said:
I always keep a backup of a rootable firmware, just in case
Click to expand...
Click to collapse
In an effort to maintain root from 4.2.2 to 4.3, I've been waiting for the OTA for 10.4.B.0.569 which is now live for me (I'm coming from 10.3.1.C.0.136 in North America using a SGP311)
However I experience an update fail -- is this due to unlocked BL??? I can update via FTF to 10.4.B.0.569 but I obviously lose root..

Cat McGowan said:
I agree with Rootk1t. If your current firmware does not have root access, then use the Vroot tool to gain root access. After gaining root access, install SuperSU and turn on its Survival mode and Install SuperSU into /system settings. Make sure the Install SuperSU into /system setting is greyed-out before updating to 4.3 via OTA. Do not update via Sony PC Companion, Sony Mobile Update Service, or by flashing FTF -- doing so will likely cause you to lose root access. That is what happened to many people during the last firmware update. People who had root access with SuperSU installed as described above and updated via OTA, retained root access. People who had root access but updated via Sony PC Companion, Sony Mobile Update Service, or by flashing FTF, lost root access. Luckily, the Vroot tool became available and allowed those people to regain root access. There is no guarantee that the Vroot tool will work with the 4.3 update. Of course, I could be wrong.
Click to expand...
Click to collapse
Yes, I updated trough pc, lost root and can not root again (yet), tried booh vRoot and the other one click root tool..

Couldn't someone who has updated through ota and kept root, create a zip of the Rom with cmw recovery? This feature has been available a long time now, and it does not transfer any personal settings to the zip.

Or maybe we can try to flash thru flashtool the previous kernel.ftf of 4.2.2 then root it via vroot...after that flash again the 4.3 kernel.ftf thru flashtool.. Some guys from the z1 forum i think managed to root the 4.3 through this method..

donedos said:
Or maybe we can try to flash thru flashtool the previous kernel.ftf of 4.2.2 then root it via vroot...after that flash again the 4.3 kernel.ftf thru flashtool.. Some guys from the z1 forum i think managed to root the 4.3 through this method..
Click to expand...
Click to collapse
very small chances that 4.3 will work with 4.2.2. kernel cause even firmwares within 4.2.2 didn't work with each other kernels

donedos said:
Or maybe we can try to flash thru flashtool the previous kernel.ftf of 4.2.2 then root it via vroot...after that flash again the 4.3 kernel.ftf thru flashtool.. Some guys from the z1 forum i think managed to root the 4.3 through this method..
Click to expand...
Click to collapse
Rootk1t said:
very small chances that 4.3 will work with 4.2.2. kernel cause even firmwares within 4.2.2 didn't work with each other kernels
Click to expand...
Click to collapse
you have to flash the 4.2 rom, get the root and create a CWM flashable zip of 4.3, flash it over 4.2 then flash the Supersu fix. Don't reboot, power off and flash the 4.3 kernel only via flashtool... this way we can maintain the root, this is how Z foum ppl are using..
i'm trying the method now, it's bootlooping after flashed the 4.3 kernel(last stage).. [NUT] has updated our recovery files.. will try that one and see if able to boot

`SBR` said:
you have to flash the 4.2 rom, get the root and create a CWM flashable zip of 4.3, flash it over 4.2 then flash the Supersu fix. Don't reboot, power off and flash the 4.3 kernel only via flashtool... this way we can maintain the root, this is how Z foum ppl are using..
i'm trying the method now, it's bootlooping after flashed the 4.3 kernel(last stage).. [NUT] has updated our recovery files.. will try that one and see if able to boot
Click to expand...
Click to collapse
Sounds good, what about sgp311 WiFi only?

nick2crete said:
Sounds good, what about sgp311 WiFi only?
Click to expand...
Click to collapse
i have posted the steps for SGP351, someone can edit the file for yours also

`SBR` said:
you have to flash the 4.2 rom, get the root and create a CWM flashable zip of 4.3, flash it over 4.2 then flash the Supersu fix. Don't reboot, power off and flash the 4.3 kernel only via flashtool... this way we can maintain the root, this is how Z foum ppl are using..
i'm trying the method now, it's bootlooping after flashed the 4.3 kernel(last stage).. [NUT] has updated our recovery files.. will try that one and see if able to boot
Click to expand...
Click to collapse
did you clear the dalvik before powering it off and flashing 4.3 kernel?

donedos said:
did you clear the dalvik before powering it off and flashing 4.3 kernel?
Click to expand...
Click to collapse
No..I haven't
Sent from my SGH-M919 using Tapatalk

`SBR` said:
No..I haven't
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
have you tried this last step from z1 thread...? by the way, thanks for the time for doing this..
Do not reboot but go back to the main menu in TWRP, then 'wipe' -> 'advanced wipe' -> tic dalvik-cache and swipe to wipe
it.

Related

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

Root and ota update

Hello guys I'm sorry it's really noop question
I have note3 n900 with Kitkat 4.4.2,
Is there a way to root it and still capable to get update by wifi? I know when the system been rooted will be modified and never receive update by wifi
I hope there's a way now.
Regards [emoji4]
Still no workaround.
You have to update via Odin.
Damn it ?
Thank you bro for your response
I download zip file from sammobile/firmwares , flash via Chainfire's MobileOdinPro. (its only a £$¥ and he deserves every cent) enable everroot, have all necessary files on external sd ie custom recovery ( CWM,TWRP,PhilsTouch) backup of last usable system, kernel and data.
towelroot.
gotta big-up Chainfire:good:
-GingeR_NutZ- said:
I download zip file from sammobile/firmwares , flash via Chainfire's MobileOdinPro. (its only a £$¥ and he deserves every cent) enable everroot, have all necessary files on external sd ie custom recovery ( CWM,TWRP,PhilsTouch) backup of last usable system, kernel and data.
towelroot.
gotta big-up Chainfire:good:
Click to expand...
Click to collapse
And now your phone receive update through wifi after been rooted or what?
IRNOTE3 said:
And now your phone receive update through wifi after been rooted or what?
Click to expand...
Click to collapse
Don't think so.
That solution is just for keeping root while flashing an update.

[Q] OTA 5.0 and Root

I just received the notice about the OTA update for android 5.0, if I install it will I keep custom recovery and able to install SuperSU for root access or do I lose complete root access and custom recovery?
If you have enabled ota survival in supersu you won't lose root (not 100% sure). Custom recovery will stay as is.
I think ota will fail quite surely as this time the script looks whether the complete system partition was tampered with which you have done by rooting
So either you first flash a fresh stock system.img or, which would be quicker and what i have done, do a fresh flash with lollipop factory img
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Masrepus said:
this time the script looks whether the complete system partition was tampered with which you have done by rooting
Click to expand...
Click to collapse
The KK-to-L OTA update for Nexus 4 works the old way - by validating signature for every file to patch.
tom.stanis said:
The KK-to-L OTA update for Nexus 4 works the old way - by validating signature for every file to patch.
Click to expand...
Click to collapse
Not true, it patches the entire system block directly so OTA will fail in the OP's case.
venu123 said:
Not true, it patches the entire system block directly so OTA will fail in the OP's case.
Click to expand...
Click to collapse
In attached file there is updater script from "LRX21T-from-KTU84P" OTA update. There you can see that it verifies files on system partiton.
Hmm strange..
How come all over the internet people tell you not to do 5.0 ota cause it checks the whole partition hash??
Well.. For me it's too late anyways xD and a fresh install feels really nice (sorry for OT )
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Masrepus said:
Hmm strange..
How come all over the internet people tell you not to do 5.0 ota cause it checks the whole partition hash??
Well.. For me it's too late anyways xD and a fresh install feels really nice (sorry for OT )
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Click to expand...
Click to collapse
I discovered that the stock rom was available in the development section, I'm up to date.
Masrepus said:
How come all over the internet people tell you...
Click to expand...
Click to collapse
Do you believe in everything what people tell you? It's always better to check by yourself.
tom.stanis said:
Do you believe in everything what people tell you? It's always better to check by yourself.
Click to expand...
Click to collapse
Well.. If quite a few different sources say that the ota mechanism is different this time, i believe it, yes.
And manually downloading the ota wasn't really sensible to me as my internet speed is really slow.
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Has it been confirmed possible to download & install the OTA successfully on a rooted device running 4.4.4?
edfernandez2 said:
Has it been confirmed possible to download & install the OTA successfully on a rooted device running 4.4.4?
Click to expand...
Click to collapse
Yes, but you have to unroot (use the clean-up function of SuperSU) and reflash stock recovery (use flashify and transfer recovery.img to your phone from the official 4.4.4 factory image from googles own download page). Also, uninstall all apps that modify your system files, like Xposed framework and mods, BetterBattery etc. I'm not sure if you have to re-lock your bootloader too - I don't think so, but i did it to be sure anyway.
I did all that, and applied the OTA without any problems when the update notification appeared on my phone. You loose no data, but you do loose root.

[ROOT] 23.0.1.A.0.167 [LOCKED BL] No recovery needed

Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!
Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?
Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.
But ist same method, if u use this or this tool.
This post doesnt deserve an original development section!
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.
This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.
remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?
rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.
Going to give this a try. Thanks
Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!
Will the Phone be wiped during this root method
ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.
ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.
Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app

[q] how to unroot

I have a que devs i hv unlocked my bootloader installed philz recovery and rooted. My question is that will i b able to recieve OTA updates. If not how to unroot than...... thanx in advance
Sent from my AO5510 using XDA Premium 4 mobile app
bijju123 said:
I have a que devs i hv unlocked my bootloader installed philz recovery and rooted. My question is that will i b able to recieve OTA updates. If not how to unroot than...... thanx in advance
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you will get OTA updates.. it doesn't matter if your phone is rooted or not..
The new update just released...
But those who were rooted weren't allowed to install it...
N'ayam Amarsh'e said:
The new update just released...
But those who were rooted weren't allowed to install it...
Click to expand...
Click to collapse
Well then you will be surprised to know that the people with root can update via OTA, it's just that they will loose their root privileges after updating.
The only requirement for the updates is that you need to be on the stock CyanogenMod recovery to take the benefit of the updates also you need to make sure that the apps or zips that you flashed might not have tempered with the core framework of the system as the update checks the signatures before updating and if they don't match installation fails.
As for the OP, make sure you flash the stock rom and that's it. You don't need to unroot in order to get the OTAs. But if have missed it you can always flash the update manually
hkm93 said:
Well then you will be surprised to know that the people with root can update via OTA, it's just that they will loose their root privileges after updating.
The only requirement for the updates is that you need to be on the stock CyanogenMod recovery to take the benefit of the updates also you need to make sure that the apps or zips that you flashed might not have tempered with the core framework of the system as the update checks the signatures before updating and if they don't match installation fails.
As for the OP, make sure you flash the stock rom and that's it. You don't need to unroot in order to get the OTAs. But if have missed it you can always flash the update manually
Click to expand...
Click to collapse
Please guide me to install the update.I have rooted my phone and have installed Philz recovery.How to install stock recovery so that I can install the OTA update?
maddydilip said:
Please guide me to install the update.I have rooted my phone and have installed Philz recovery.How to install stock recovery so that I can install the OTA update?
Click to expand...
Click to collapse
I'd recommend to go and watch this thread on YU forums, it's not mine, but it's the first post that came on how to get the update manually.
But still in short all you need to do is :
1. Download the OTA's .img file from here : https://drive.google.com/file/d/0B5qkmXkPr5WyMy1FUm9rNGdZZ2c/view?usp=sharing
2. Download the stock CyanogenMod Recovery from ere : https://drive.google.com/folderview?id=0BwVitsnY-WxvRVNYcnhRM05vX2c&usp=sharing
3. Download Flashify from app store if u r sure that you r rooted.
4. Open Flashify >> select "Recovery Image" >> select "choose File" >> browse the Recovery .img file that you downloaded and flash it.
5. Open Custom recovery, go to "Update" browse and select your ota update .img file and flash it.
It'll take about a min to flash it and if all goes well, you will have the updated build and the proximity issue fixed !
unrooting
bijju123 said:
I have a que devs i hv unlocked my bootloader installed philz recovery and rooted. My question is that will i b able to recieve OTA updates. If not how to unroot than...... thanx in advance
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
well i am not sure will work with you or not or work without any harm, i rooted with updated supersu but option in it for uninstalling not workng so i read online thread but it suggesting to reinstall stock rom, i am in cm12
i treid root genius in pc a tiny software which has option to unroot i clicked on that and within second i unrooted , i reboot the super su software was not there, agian reboot mobile working normal then i locked my bootloader .

Categories

Resources