yashsingh1/xdaforums huggingface dataset:
[Xperia Z Android Development] johan8:
If already flashed to .253.

The only way is full flash back to 434 or older, or unlock bootloader.

Either method will also wipe user data.

I think flash back is better, unless you have already dump your TA.

Hope that the experts will find another exploit.
[Xperia Z Android Development] j0nthn:
Soo...maybe a bit redundant, but i'm still not satisfied with this answer. Flashing with zip and my method have exactly the same results? Oh and thanks for helping me out so much, really appreciate it!
[Xperia Z Android Development] schaggo:
No, not exactly the same.

You installed it from the play store as a user application.

Flashing it moves the app to /system as a system application. The latter will survive a factory reset. The apk, that is. The su binary does so anyway.

Edit: what interests me more though is, if the system still reboots and acts up when working with root access on SuperSU.

Gesendet von meinem C6603
[Xperia Z Android Development] bpye:
Does anyone know if this works with the Sony Xperia SP?
[Xperia Z Android Development] DooMLoRD:
we have tested and it doesnt work...
[Xperia Z Android Development] Darkfunnyguy:
Are you currently looking to try to solve rooting the 10.1.1.A.1.253 firmware with the Root Kit used on this thread please?

I have rooted using the workaround another thread but it would be nice just to root this way using root kit on the .253 firmware.
[Xperia Z Android Development] maxxx_steel:
if someone can do it then there wont be any phone who can compare with ours......

hoping that someone would try....:good::good::good::good::good::good:
[Xperia Z Android Development] dhruvaz:
Wait a minute that tft is also for tablet? I thought that was just for phone.. now lemme try it then.. i've alread downloaded that and beta 6 lets see.
[Xperia Z Android Development] BADBOY1412:
Xperia tablet z

I'M stuck at the white screen on my tablet and i tried turn the screen on and off dozen times, its still the same.Help please? the firmware is 10.1.C.0.344
[Xperia Z Android Development] zippy01:
Although recommend to lose data there is no need
[Xperia Z Android Development] hush66:
It's not for the tablet. It's for C6603 (i.e. the phone).
[Xperia Z Android Development] j0nthn:
SuperSU also has an option to be installed as a system app, will this suffice? Also, what I meant was, if removing superuser with SU is enough to 'fully' remove it :p
[Xperia Z Android Development] schaggo:
This leads to the same result as flashing the zip to begin with. Good if you don't have a recovery at hand.

Most likely not, there will most likely be traces. Simple recipe: reflash firmware, this formats /system and gets rid of everything not originally belonging there. Although if root doesn't belong on an Android device to begin with is debatable :laugh:
[Xperia Z Android Development] j0nthn:
Yeah, what I could do now is:

-Install superSU as a system app

-Reflash .434

But will this not wipe SU as well (and therefore remove root). Shouldn't I just install SU with a zip and flash via recovery, isn't this easier? Also, the reason why I don't have a recovery yet is because I'm not sure about which one is the best (or dualrecovery off course..).
[Xperia Z Android Development] schaggo:
You get it all wrong. You don't really understand. I'll try to explain:

You have root access. You have SuperSU. This is all very nice, leave it this way and go to bed. Go to work. Or go where you want to go but leave this setup alone. For an indefinite amount of time. Unless...

a) you can't sleep, you can't work, all because you got root.

b) you want to sell your device all nice and green and fresh and untampered.

c) you want to show your device to Sony because for warranty purposes.

Then unroot your device. Do that by reflashing a fully stock firmware, either by, depending on your device's bootloader status...

1) Androxyde's Flashtool and an FTF file

2) Sony's EMMA tool

3) Sony's SUS/SEUS tool

4) Sony's PC Companion tool

This formats the system partition, the partition the su binary resides on and where all the other magic **** concering root access happens. This will get rid of root, su, and all traces (on /system, that is). If, on top of that, you also wipe user data (/data partition) this will remove everything and all traces and your device will be like the day you took it out of the box.

Which one is best? If you can, backing up your TA, unlocking your bootloader and flashing a kernel with recovery integrated, CWMR as TWRP is a bit buggy the last time I checked, is best. Period.

If you can't unlock your bootloader, you're a bit a poor pig. You then have to go for a half assed approach but it's the only one which works, so it has to do I guess. Same as above applies though, CWMR, as TWRP is a bit buggy on the Z at this time or at least the last time I checked.
[Xperia Z Android Development] j0nthn:
Okay, yes. Now I understand it all better, but then what's the way to remove all traces of the 'regular' superuser that gets installed with this rootmethod and just keep superSU (if this is necessary). As I said, I removed superuser with SU, but you said it probably leaves traces. Is this bad or can I sleep in peace, as you mentioned :)

Ps: I think you got me wrong, I was talking about the 'superuser app' and the 'superSU app'. Supposedly superSU is better, because it gets more regular updated.
[Xperia Z Android Development] schaggo:
Simply using SuperSU should remove all relevant parts of ChainsDD Superuser. There may be traces like logs or temp stuff left behind, they wont interfere with SuperSU operations though.

SuperSU and the 'new' Superuser by Koush (as opposed to 'old' Superuser by ChainsDD, same name yet completely different code) seem to do things differently. The older tool seems to crash under certain circumstances where the new kids on the block seem not to. ChainsDD code is quite old, several years in the meantime I believe. In the middle comes SuperSU, Koush's Superuser is newest and obviously also the one which comes with Cyanogenmod nowadays.

Gesendet von meinem C6603
[Xperia Z Android Development] j0nthn:
Exactly, now we're on the same page! So from this I get that you prefer Koush's Superuser over SuperSU? Which one would you pick for the Z?
[Xperia Z Android Development] schaggo:
Doesn't matter, at the end of the day it's the same.

I prefer Koush's Superuser though because 1) it's new and shiny, I like new and shiny :D 2) I somewhat dislike SuperSU's layout/design/UX 3) Superuser is default in CM and thus is carefully crafted 4) Superuser is opensource and thus rather actively developed and looked into by a broader audience 5) Superuser is new and thus - also due to possible bugs of course - rather actively worked at. 'Nuff for me. But as I said, all the same, all the same...
[Xperia Z Android Development] eman2001:
i hope they soon find a way to root 253 because thats what am waiting for :o
[Xperia Z Android Development] j0nthn:
I have a stock .434 generic NL rom flashed. I have root acces (OP method) with superSU installed as a system app. I haven't flashed or modded anything else, not even a recovery. Can someone tell me if I will still have root when I update. 253 OTA?

Thanks in advance
[Xperia Z Android Development] Darkfunnyguy:
No you will lose root you will have to work around.

See this thread if you want to update to .253 and keep root :- http://xdaforums.com/showthread.php?t=2282415

You will have to wait DooMLord to exploit and root .253 firmware whether they do managed it is anybody guess.
[Xperia Z Android Development] kingvortex:
You should retain root if you update OTA

Not true. Updating OTA should retain root. See this thread for people retaining root after updating - http://xdaforums.com/showthread.php?t=2298005
[Xperia Z Android Development] Darkfunnyguy:
I am locked bootloader and recently updated to. 253 and lost root. Why is a thread for a workaround as it seem lots of people have lost root when updated via ota although there are people who got lucky.
[Xperia Z Android Development] okokies:
well that's the best they can do atm because they have to find a new exploit.

I hope they find it soon i just need it to read my exfat sd card

Good luck!
[Xperia Z Android Development] DonDeyv:
root for 10.1.1.A.1.253

I hope v. 10.1.1.A.1.253 can be rooted soon.

My Tablet Z was shipped today directly by Sony with this Software version and an unlockable bootloader.

But I don't want to unlock it, because I want to keep the Bravia Engine...
[Xperia Z Android Development] zippy01:
I doubt there will be a new method since root can be achieved on a locked bootloader
[Xperia Z Android Development] parapaul:
Maybe a bit late to the party here, but I'm on the .434 FW still. I could have sworn I read that rooting meant that bootloader unlock status went from allowed to not allowed.

Now that CM 10.1 is on RC4 and presumably close to a stable release, I was planning to repair my phone via PCC to have bootloader unlock allowed again, but lose root in the process.

Following the instructions on the Sony bootloader unlock page, I checked - but to my surprise I have root AND an unlockable bootloader! My unlock key is sitting in my inbox, and as soon as I've had some sleep I'll get going.
[Xperia Z Android Development] Apo11on:
This root method and the one, made by Bin4ry as well do not work on SGP312 (Xperia Tablet Z, US WiFi only version). /Data folder is read only, and from output of the script I can see all the write and rm commands to it fail.

Superuser is installed, but doesnt seem to be functional - it denies permission for every single app besides "shell"

View attachment 2009021
[Xperia Z Android Development] Darkfunnyguy:
I am wrong and you are right about retaining root over OTA why?

This what I did :_

1,.Installed C6503_10.1.A.1.350_Generic_DE.ftf through flashtool .

2. Rooted through easy rootkit on this thread.

3. Installed OTA Rookeeper and hide the root.

4. I received a new update for firmware 10.1.1.A.1.253 notification from Update Center or OTA in which I downloaded and

installed it over OTA.

5. Restored root in OTA Rootkeeper and checked I have successfully retain my root.
[Xperia Z Android Development] j0nthn:
Anyone up for giving this a try on .434?
[Xperia Z Android Development] uwillknow:
already updated to 253, so unable to root using above method. any idea how to downgrade to earlier firmware???
[Xperia Z Android Development] kingvortex:
Yes. Grab a 434 ftf and flash it with Flashtool. There's a guide in the general section ;)
[Xperia Z Android Development] johan8:
downgrade is easy, just flash it.

But you need to wipe userdata, otherwise you will get reboot loop in NFC firmware upgrade (it is downgrade actually).
[Xperia Z Android Development] schaggo:
Cosmetic issue only. The status does not change at all, the service menu app fails at reading the correct status. That's all.

Unneeded. See above.

So? Weren't you going to flash CM anyway? What's root on stock any good for at this point?

See above. Nothing ever changed, cosmetic display error.

Don't forget to backup your TA so you can go back to fully stock, including DRM and BE2 in case you want to, eventually.

This (the .434) OTA doesn't format /system, thus you don't lose root. Expected behaviour, on .434 OTA that is.
[Xperia Z Android Development] Migliano:
Hi, I could root my xperia zl (zq in Brazil) using this method and the option of unlock bootloader is now checked with no, before that was yes. If I fix it, am I gonna lose the root? Or there´s another option to keep yes and root?

thanks
[Xperia Z Android Development] schaggo:
Its only a display error in the patched service menu app. Please read, people, don't always ask the same question. There is no need to have it back on yes, as nothing ever changed. It's, again, only a display error.

Gesendet von meinem C6603
[Xperia Z Android Development] nak89:
Help me!

Can you root for SO-02E firmware .343??:crying:
[Xperia Z Android Development] schaggo:
No. Downgrade to earlier firmware, root, upgrade using the flash-update-zip-in-recovery-method.
[Xperia Z Android Development] creison:
Stuck in rooting start

Hi folks!

Maybe some one is able to clear out this to me here comes my stuck screen!

Im on unlocked boot loader with the old 101.A1.434 verssion.

Thanks in advance !
[Xperia Z Android Development] :
There is nothing to clear here, the text clearly say what to do. Did you checked yur phones screen for further instructions ? After that, the phone should run the diagnostic program and you should tap diagnostic, than display ... Reboot phone, pc than try again... If not, re flash your phone to. 434 .

Sent from my C6603
[Xperia Z Android Development] [NUT]:
[MENTION=2784807]DooMLoRD[/MENTION]

I've finalized my remount-reboot fix, you might want to add it to the OP.

It is a replacement for the install-recovery.sh in this root method and will stop CWM from asking if you want to prevent it from flashing stock recovery :)

[Locked Bootloader] The definitive root Remount-Reboot fix!
[Xperia Z Android Development] Yellow_Racing:
Do you think there will be a way to root like .434 with the new firmware .307
[Xperia Z Android Development] [NUT]:
My guess is that goroh_kun and hunka_com will save themselves the trouble of finding a way to be honest, but who knows, maybe they will find a new way :)
[Xperia Z Android Development] lancebuks:
With [NUT]'s workaround already available I hope if there are any new exploits then they wait until 4.2.2/4.3 (or newer) is released. It would blow if any new exploits are released now just for Sony to fixed them in the next release.
[Xperia Z Android Development] [NUT]:
Yep, that's the most likely scenario. They might have found a new way but keeping it back for 4.2 or even 4.3.

You can't blame Sony for patching the bug which was used in this method, a bug is a bug and can have more, less beneficial, side effects if they don't.
[Xperia Z Android Development] fredphoesh:
under a false impression about Sony's hacker-friendliness...

OMG, I am utterly bummed. I have had a Sony Device for an hour, and for the first time since I have owned a smartphone, it cannot be rooted???

I thought this device was supposed to be the most hacker friendly one, that Sony were unlike samsung, htc and the others, and were being really co-operative?

I am bitterly disappointed... my build is 10.1.A.1.434

I know it's not the OPS fault, but I was reading this thread WHILE setting up my phone... and it said it needed a software upgrade, so I thought "why not, why would there be any problem with a xperia Z"

aaauuugghhh.........!!!

Mark
[Xperia Z Android Development] [NUT]:
Hold your horses bro, .350 and .434 can be rooted, anything from 10.1.1.A.1.253 and higher can not, you'll need .434 as a stepping stone.

Besides, you can always unlock your phone's bootloader: that is what Sony is very easy with. The community can get a bucket load of help and support from them too... THAT is what makes Sony dev friendly.
[Xperia Z Android Development] fer2503:
do you think that it's possible in the future to flash custom kernel on locked bootloader?...or the possibility to unlock bootloader without lose the bravia engine?
[Xperia Z Android Development] fredphoesh:
Ah, I was confusing rooting with unlocking the bootloader.

I have now managed to root, but the bootloader issue... I read on some major thread here on xda that if your bootloader says it is not unlockable, you are out of luck... but its GREAT you say there are ways to unlock it. I must say, so far, it has been WAY more difficult than with my samsungs.

thanks for the help

Mark.
[Xperia Z Android Development] [NUT]:
Custom kernels on a locked bootloader will never be possible, so get that hope out of your head quick :p

On the BE2 engine it might be possible, I haven't kept up but with the TA partition backup and restore unlock/relock procedure found, it holds some promise for a bright soul who manages to patch some binaries.

Yah, but the rooting process from the OP will cause your service menu to show you the same while right now it might tell you yes. There is a flashable fix though, in this thread. If you can't enable your NFC anymore after rooting, remove /data/usf and reboot :)

Rooting using Bin4ry's method might be easier for you if you can not wrap you head around it now.

I think it's a breeze for Sony, but I have no experience with other phone brands when it comes to rooting or unlocking, so i might be a bit biased :p
[Xperia Z Android Development] fer2503:
i like the doomkernel but i don't want to lose BE2 :(...very hard decision!
[Xperia Z Android Development] fredphoesh:
Hi there mate,

I have rooted the phone but have not found a way to unlock the bootloader. I assume one has to unlock the bootloader if you want a custom kernel, but there are some roms which dont require unlocked bootloader, but AFAIK, you do have to for a cm or aokp rom or paranoid android.

Do you know where/how to unlock a bootloader that says it cannot be unlocked? I have searched all the xperia z sub-forums here and have not found any answer.

Thanks,

Mark.
[Xperia Z Android Development] [NUT]:
As soon as you require a custom kernel for a ROM you do :p

And you looked with your eyes closed i think man: http://xdaforums.com/showthread.php?t=2153261 its the first sticky in this same forum :eek:
[Xperia Z Android Development] dcoloane:
Great (thanks for your work on the translation), hope there will be the FTF file to lock back the BL in the future so that I can try this method.
[Xperia Z Android Development] krabappel2548:
Re: [ROOT] Xperia Z for LOCKED bootloaders! [Exploit by: goroh_kun & huhka_com]

First recovery for locked bootloader will probably ready tonight, anyone who wants to test it tonight?
[Xperia Z Android Development] robt772000:
Hey guys my W8 computer is not finding my XZ even after I updated drivers, went into test mode and selected unsigned etc. What am i doing wrong?
[Xperia Z Android Development] sigma9988:
i can test it :good:
[Xperia Z Android Development] krabappel2548:
Re: [ROOT] Xperia Z for LOCKED bootloaders! [Exploit by: goroh_kun & huhka_com]

Setting Windows in testmode was step 1 :)

- Go to developer.sonymobile.com

- Go to downloads, drivers and Dow load the Xperia Z driver

- Extract it somewhere

- Go to device manager and search your XZ, right click update drivers

- Manually choose them from pc

- browse for the folder and install drivers, both for mtp and the other one

- Now adb etc should work properly :)

Ok, maybe it won't work, but it's worth a try :)
[Xperia Z Android Development] robt772000:
Yep I'm rooted now yes!
[Xperia Z Android Development] howan:
I'm now rooted and yes please!
[Xperia Z Android Development] Knight77:
But the ROMs that are out now, will they be flashable when the recovery for locked BL is avaiable?

Or they need some change?
[Xperia Z Android Development] torrente777:
I can test it!
[Xperia Z Android Development] sacredsoul:
I keep getting the best driver software for your device is already installed?
[Xperia Z Android Development] wojtas29:
Hi

Is possible to remove this root?

What about warranty?
[Xperia Z Android Development] marcoplo:
As long as you dont unlock bootloader you save you can easly reverse by pc companion !!:o

is there any recover to be installed so i can flash zips
[Xperia Z Android Development] snark_be:
Hi!

Worked great for me! I can now use Titanium Backup to restore apps and data from my previous device!

Congratulations to those who made it work! :good:
[Xperia Z Android Development] Kallb123:
Can someone explain how to reverse this with SEUS/PC Companion?

I tried SEUS but it said no updates found (can't see any repair/restore option)

I also tried PC Companion but I also can't see any repair/restore function.

Sorry if this is totally obvious...
[Xperia Z Android Development] RobbyTouchHD:
If I allready have an unlocked bootloader will I be able to relock it to get the bravia engine back and root it with this toolkit here? Or is that not possible atm?
[Xperia Z Android Development] nullcx:
This root method rocks! I was able to r00t in few seconds. God bless you!
[Xperia Z Android Development] antipesto93:
perfect, worked (Had to restart for SuperUser to show up)

Really good that you can restore it for warranty easily!
[Xperia Z Android Development] RenegatPL:
HI

I confirm correct operation of the Xperia T Jelly Bean Generic Trade Central Europe 1 (4.1.2) (1265-1620)

:victory:
[Xperia Z Android Development] krabappel2548:
For those willing to help me with recovery for locked bootloader, please test it: http://xdaforums.com/showthread.php?p=39051701#post39051701

it requires a rooted stock rom.
[Xperia Z Android Development] xIceCream:
What a good day!

Just got my XZ, and guess what? Root for locked bootloader, Recovery for lockedbootload. Dayummmmmmmmmmmmm. I love xda.

-Big hug hug to all the devs-

p/s. no homo.
[Xperia Z Android Development] fredphoesh:
erm, perhaps you have your eyes closed.

This thread is the thread I have been quoting on this forum because it says

"In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked."

Which means, this method of unlocking does NOT work IF your bootloader unlock allowed says NO.

Which is why I was asking how one is meant to do it if this does not work!:crying:
[Xperia Z Android Development] [NUT]:
:eek: :silly:

Well, you can have someone make it unlockable again... but it is a service that will cost some money to get that done.

:cool: <-- me being blind :p
[Xperia Z Android Development] fredphoesh:
Hi

I ignored the OPS comment that it was not possible to unlock the bootloader if the phone said NO, and followed the instructions and it is now UNLOCKED!!!

I must say, that is no thanks to this thread which copied and pasted a chunk of incorrect info from the sony site http://unlockbootloader.sonymobile.com/instructions

where it says

"In your device, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked."

THIS IS NOT TRUE!!!
[Xperia Z Android Development] schaggo:
If you would have read the relevant information, you would have found out that after rooting the patched service menu, used for rooting, always shows no, regardless of the actual state of the bootloader. It's ok for Sony to not put that rooting-related information on their site, don't you agree?
[Xperia Z Android Development] [NUT]:
:eek:

Now who's looking with eyes closed? ;)

schaggo is 100% correct, and i even warned you for it :p

Anyway, have fun with your Z, i believe you won't regret it ;)
[Xperia Z Android Development] fredphoesh:
actually, if you had read this thread and my comments from when I started this morning, you would see that the bootloader said "NO" BEFORE I rooted the phone. Anyhow, so far I am really not happy with this power munching, hard to hack device... it's been a bit of an uphill battle.
[Xperia Z Android Development] Richy99:
thanks for this, made rooting quick and painless
[Xperia Z Android Development] fredphoesh:
and now it seems to be in a boot loop at the moment, after flashing BOOT.IMG as in these instructions from paranoidandroid...

Install instructions:

If you come from a rom without CWM/TWRP recovery and don't have a recovery yet:

Quote:

extract the boot.img from the package.

put boot.img in your fastboot directory.

fastboot flash boot boot.img

fastboot reboot

did that, now all i see is the sony coloured paint animation
[Xperia Z Android Development] [NUT]:
Erh.. you tried to install a CM kernel?

If so, that will explain... hold power and vol-up to reboot, press vol-up or vol-down repeatedly to enter recovery when you see the kernel logo. Then flash the ROM.