[Q] Z1 Compact lost root during Lollipop upgrade - Xperia Z1 Compact Q&A, Help & Troubleshooting

I have just upgraded my rooted Z1 Compact to Sony's Lollipop and have found that it lost root during the process. I have tried rerooting using newroot.rar as previously and all I get is an error message "error: only position independent executables (PIE) are supported." Have tried a clean repair but still get the same error. Have already looked here for a way to do this. I Found "Z1C-lockeddualrecovery2.8.14-RELEASE.installer.zip\lockeddualrecovery%" which I thought might solve the problem, but just get an installation failed message saying adb is not recognised as an internal or external command. Really have no idea what to try now. Have spent hours searching to see what the problem is, but can not find a solution that works. Any ideas please?

You lose root when upgrading, you need to flash a prerooted rom from this thread(via TWRP). First you need to go back to 4.4.4 and root it all over , then install custom recovery. Find a prerooted lollipop from here( I use prerooted RU).Flash it from recovery and you're done. Good luck.

Look here for full instructions: http://forum.xda-developers.com/son...lp/rooting-z1-compact-stock-lollipop-t3090021
With PC Companion you could even use your very own firmware, simply follow the instructions here

Related

Unlocking Sony Xperia T 9.1.A.1.140

Hello people,
I am a newbie here, and I would like to root my Sony xperia T build 9.1.A,1,140
I have tried bin4try rooting system and it all went through fine, but after starting the phone I downloaded rooting checker and it said that my device was not rooted. This was also confirmed when trying to use lucky patcher. I did have however the SuperSU app installed.
Then I withrew that root just in case from the removal option, and tried to do it through the DoomLord method. Whilst installing it said that my device was not supported. Since then I have been reading and trying to figure out how to upgrade my build version to 141 in order to root it through DoomLord method, and I have the boot.img from the stock .141 kernel. I am just a bit confused and don't know how to play it safer.
Also, I have tried installing the CWM but since I don't have a rooted phone it didnt let me install. I now have a stock Xperia T with android JB 4.1.2 build 9.1.A.1.140 and would really like your help to see what I can do.
I will now head to bed, as my brain hurts from so much information, I hope to get this sorted soon.
Thanks a lot to you all for your time and effort!
Sincerely,
Jose
UPDATE
I forgot to mention that I tried to install CWM but it didn't let me because the phone was not rooted. Also there is apparently no way to unlock my bootloader.
This morning I donwloaded the 141 tft file, a polish version, and decided to flash it into my phone. After flashing and starting the phone, the sony wave colour thing did several loops for about a minute or two. The the phone started as usual and everything works fine except for internet data.
AT THIS POINT
I do not know where to proceed, I go in mind to now try rooting my phone through Doom's method but I am afraid that maybe I can screw it up more or root it but still have no mobile data which would be almost useless to me.
Please I would really appreciate the help of anyone.
THANKS!
barceloneru said:
Hello people,
I am a newbie here, and I would like to root my Sony xperia T build 9.1.A,1,140
I have tried bin4try rooting system and it all went through fine, but after starting the phone I downloaded rooting checker and it said that my device was not rooted. This was also confirmed when trying to use lucky patcher. I did have however the SuperSU app installed.
Then I withrew that root just in case from the removal option, and tried to do it through the DoomLord method. Whilst installing it said that my device was not supported. Since then I have been reading and trying to figure out how to upgrade my build version to 141 in order to root it through DoomLord method, and I have the boot.img from the stock .141 kernel. I am just a bit confused and don't know how to play it safer.
Also, I have tried installing the CWM but since I don't have a rooted phone it didnt let me install. I now have a stock Xperia T with android JB 4.1.2 build 9.1.A.1.140 and would really like your help to see what I can do.
I will now head to bed, as my brain hurts from so much information, I hope to get this sorted soon.
Thanks a lot to you all for your time and effort!
Sincerely,
Jose
UPDATE
I forgot to mention that I tried to install CWM but it didn't let me because the phone was not rooted. Also there is apparently no way to unlock my bootloader.
This morning I donwloaded the 141 tft file, a polish version, and decided to flash it into my phone. After flashing and starting the phone, the sony wave colour thing did several loops for about a minute or two. The the phone started as usual and everything works fine except for internet data.
AT THIS POINT
I do not know where to proceed, I go in mind to now try rooting my phone through Doom's method but I am afraid that maybe I can screw it up more or root it but still have no mobile data which would be almost useless to me.
Please I would really appreciate the help of anyone.
THANKS!
Click to expand...
Click to collapse
from what i understand you can't flash a custom kernel unless ur bootloader is unlocked!! You may have to flash an appropriate firmware with flashtool that is rootable and then try to protect root and then try a fota but don't use seus or pc companion!! Someone correct me if i'm wrong!!

[Q] Rooted with .434 firmware (4.1.2), Upgraded via OTA, Now Unsure on Root Status?

Hello,
I recently got myself an Xperia ZL C6502 with unloackable bootloader. It came loaded with the .434 firmware (Android Version 4.1.2.), and so I rooted using this method here: ROOT MANY ANDROID v31 by Bin4ry. (link: http://forum.xda-developers.com/showthread.php?t=1886460&highlight=434)
Then I updated via OTA to the .244 firmware (4.2.2) thinking that root would hold through the OTA update. I ran a factory reset afterward, hearing that is good for performance.
The strange thing is, now that I've updated, I'm unsure on root status.
For starters, AVG says I am operating in higher permission mode, aka root is enabled. However, Titanium Backup can't get root access permissions, and when I try to manually update the binary of Superuser 3.1.1 (it's the most current version but I tried anyway), it told me root access failed.
Even stranger is that when I load up Flashtool (latest version as of this date of posting) it tells me Root Access Allowed.
Can anybody help shed some light on this issue I'm having? Apps that require root aren't given permission, Superuser doesn't seem to detect the fact that my device is rooted, yet AVG and Flashtool are telling me that it is.
Thanks in advance.
Any ideas?
CedricFP said:
Any ideas?
Click to expand...
Click to collapse
This may not be the answer you want to hear but if I was you, I would flash a clean 244 build with Flashtool and then root. No more mysteries about whether or not root is there or not ... or if it's a broken root.
You will have a fully rooted latest build of 4.2.2.
Its really easy, only takes 15 min.
Crash338 said:
This may not be the answer you want to hear but if I was you, I would flash a clean 244 build with Flashtool and then root. No more mysteries about whether or not root is there or not ... or if it's a broken root.
You will have a fully rooted latest build of 4.2.2.
Its really easy, only takes 15 min.
Click to expand...
Click to collapse
Thanks for your reply
Yes I had considered that, but I was wondering if I had encountered some kind of show-stopping bug or what-not. Ultimately, doing a clean flash is a last resort, but definitely an option. If anybody else has any idea why this might be, or has encountered this issue before, please do respond!

Unlocking Bootloader and root

YES, I have read as much as I can in the forums (all day today, rather nice way to spend a holiday though).
I have a Xperia Z1 Compact D5503 handset (FR SFR version, from eBay). I have recently updated it to Android 5.0.2 via XperiFirm tool. I flashed the Customized_IN version (D5503_Customized IN_1281-0184_14.5.A.0.242_R3D). It WAS NOT rooted and I don't remember if I had unlocked the bootloader.
[I have a laptop running Windows 8.1 x64, with latest versions of XperiFirm, FlashTool x64, Android Studio (with Google USB driver), PC Companion. My laptop detects my phone as MTP (or MSC when I choose so), but in the Device Manager, it never shows as android adb device (always MTP, or USB stick). I tried Update Driver option but to no avail, it says the Google USB driver or the downloaded Z1 Compact driver (from Sony site) is not supported (either by the phone or the PC). But the phone shows debugging connected, even prompts my authorization (first time only). Flashmode and Fastboot modes are detected well enough.]
Now, it says I am not allowed to unlock bootloader (via "*#*#7378423#*#* > Service Info > Configuration" menu). It shows the following:
------------------------------------------------------
Rooting Status:
Bootloader unlock allowed: No
------------------------------------------------------
I am unable to unlock the bootloader (or root, yeah, that's the ultimate goal) via the following methods:
1. Official Sony Method,
2. ZergRush
3. TowelRoot,
4. Easy Root Tool,
5. Newroot (by Doomlord),
6. Flashtool (that BLU option),
7. Fastboot via cmd.exe,
8. Flashing pre rooted zip files (cannot open stock recovery option, does this have any? I used the stock recovery a lot on my old Samsung).
Flashtool, cmd and Newroot showed variants of this same error: "only position independent executables (PIE) are supported."
Sony gave me a code, but that also yielded another variant of the same.
Now, as far as I have understood, what I need is one or more of the following:
1. a pre-rooted ftf file (someone said that is impossible as for Sony's encryption, is that right?)
2. some way to root without unlocking bootloader (Newroot does that, but did not work)
3. some way to override that crazy arrogance of Sony and unlock the bootloader and be my white knight...
Can anyone provide me with a guide or some example? It is not at all fair of Sony to create these non-allowance nonsense.
P.S. Please do not mind my tone, I am usually very docile but a whole day (literally; 6 AM to 6 AM next day!!!) in front of my PC without any result have mutated me a bit.
BTW, I am fairly proficient in following complex instructions only if they are conclusive (I don't want to spend another day figuring out how to follow them)
i cannot contribute in any way, i just wanted to tell you you´re not the only one with the problem. if i find a solution i will get back to you
Flash .108 firmware, root with "rootkitxperia", install dualrecovery, use prf creator to make a flashable rooted zip of lollipop (if that's what you want) and flash in recovery. Job done
I'm actually relieved to see someone else experiencing the exact same problems, I've already spent several days figuring out how to unlock the bootloader and get my phone rooted, but to no avail. However my device does state that the bootloader can be unlocked, but can't be found through cmd prompt when connected in fastboot mode and get's the same error: 'only PIE (position independent executables) are supported when trying to unlock the bootloader with flash tool.
White knights on problem solving horses would be greatly appreciated indeed!
I got a Z1C recently from eBay but have also done this on a Z Ultra and Z2, because of the cross development Sony stuff this is very similar for all of them.
You only need to unlock the boot loader if you want to flash a custom kernel or ROM. You don't need to unlock it to get root access, however to get root access you'll have to flash an old version of Android. You're flashing an old version from before they patched the exploits you want to use to get root.
So the steps are:
1. Get an old version of the official Sony ROM.
2. Flash the old ROM.
3. Exploit it to obtain root access.
4. Install a custom recovery.
5. Make a custom flashable zip of the firmware you want to use with root included.
6. Enter custom recovery and flash the zip you created in step five.
The files I used to do this are:
From XperiFirm I download "1280-5440 Netherlands T-Mobile NL 14.4.A.0.108 / R9C".
Using Flashtool I made an FTF from it and flashed it.
Then I used "EasyRootTool v12.4" to get root access.
I installed "Z1C-lockeddualrecovery2.8.21-RELEASE.installer.zip" from Nut's site.
Then you go back to XperiFirm and grab the version of Android you want to use. I used the 5.0.2 Customised AU one as I'm in Australia, you probably want the Indian one.
Use PRFCreator to make a flashable zip with a custom recovery and SuperSU, for that you need the "Z1C-lockeddualrecovery2.8.21-RELEASE.flashable.zip" not the installer.
There are posts with this info around, it's almost 5am for me so I'm not going to go looking for the links to the posts, you'll have to do that yourself. If you read for the day you've probably found them already.
First of all, I would advise against unlocking your bootloader unless you have a backup of your TA partition. Otherwise you risk losing your DRM keys and might criple your camera. This is irreversible damage without a backup. Second, on the official Sony unlock page it states specifically that not all devices are allowed to unlock the bootloader. If it doesn't, though luck then I guess but I could be wrong.
Now to backup the TA partition you need to be rooted which is not possible up to now with Lollipop unless your bootloader is unlocked. So this is a bit of a problem. Luckily flashtool (make sure to use the older 0.9.18.6 version at the bottom of the download page) allows you to flash a previous version without unlocked bootloader or being rooted. Choose one from the list at the bottom of this link but make sure to use a .108 one from the "KitKat [Old]" section (I chose Generic UK unbranded => link points to UA version, UK FTF here). Then root it through one of your preffered methods, backup TA partition and install a recovery.
Then create your own stock FTF with flashtool. Use this method with PC Companion or just download it through flashtool's built-in Xperifirm with this method.
Then create your own pre-rooted flashable zip with PRFCreator with part 2 from this guide. Continue with part 3 from the same guide (maybe skip the 3 big cups of coffee), exhale and get on with your life.
Maybe check out this one and this one (basically the same process) too.
It's the same procedure as written above but with some links I used to gather the information. I just went through this myself so still had all the tabs open. These were most of the useful ones I believe. It really is a PITA to gather all the bits and pieces from miscellaneous posts scattered all over this forum.
Why flash a 108 kk and then root? Just create lollipop rom with prf creator and flash that.
spudata said:
Why flash a 108 kk and then root? Just create lollipop rom with prf creator and flash that.
Click to expand...
Click to collapse
PRFCreator doesn't make FTF's but flashable zips. From the PRFCreator thread:
To flash a pre-rooted firmware, you need a recovery menu
Click to expand...
Click to collapse
To install a recovery you need to be rooted (at least as far as I know) or have an unlocked bootloader. The point is not to unlock the bootloader at all (like when it is not possible) or maybe only after taking a backup of TA partition if not already done so (which again needs root access).
You're absolutely right, my mistake. Think i had a memory lapse

Failed Root, Stuck in Fastboot.

I'm rather new to the whole android thing and screwed my phone more than I could hope. When the new firmware version came out I thought I needed to unroot to install it. (I wanted it for the WiFi fixes). After installing it I went to reroot and of course the one click root doesn't work, so after trying to find a new method I tried this: http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23 failing to realize it's for D855. My device is a D852 and is stuck in fastboot now. Attempts to continue give error "Unable to find suitable device tree for device (194/0x00010001/121/0)". Just wondering if there's a way to fix this without losing everything or a way to recover my files before resetting. I don't really care about the root at this point.

DESPERATE!!! Need help rooting HTC Desire 816 (710c) VM Single sim.

I have an HTC desire 816 (710c) Virgin Mobile. I have tried the following: King Root- APK and PC. KingoRoot- APK and PC, Framaroot APK, iRoot APK and PC, Towelroot APK, Z4Root APK, RootMaster APK, One click root APK and PC, Baidu Root APK, And none have gained full root permision. I have had Temp roots with both King Root and KingoRoot, but it seems to only last minutes and then my phone reboots on its own and its back to no root. I have my bootloader unlocked which I thought was supposed to prevent this sort of thing? Im running 5.0.2 stock. I'm fairly versed on this subject so this is becoming very frustrating for me, ive been trying for over a week now. I know i could flash a rooted rom but i have tried literally at least 12 different ones for every variation of my phone possible, from CM 11 up to CM13.. and when I go to flash it says (roughly) "this file is for A5, A5DUG, A5.., This phone is A5dug"......How is that possible? I dont know if this is relevant or not but when im in recovery mode up top it says "A5chl" in the specs area... but thats not what it seems to think it is? I have managed to successfully flash once but it was for a dual sim variant of the 816, needless to say it was jacked up and i had to go back to stock. I must be missing something.. Anyways, im rambling on now. Im desperate, PLZ help me. I have run out of ideas and losing hope quickly.
Cheers,
Mikey
SirMurkAlot said:
I have an HTC desire 816 (710c) Virgin Mobile. I have tried the following: King Root- APK and PC. KingoRoot- APK and PC, Framaroot APK, iRoot APK and PC, Towelroot APK, Z4Root APK, RootMaster APK, One click root APK and PC, Baidu Root APK, And none have gained full root permision. I have had Temp roots with both King Root and KingoRoot, but it seems to only last minutes and then my phone reboots on its own and its back to no root. I have my bootloader unlocked which I thought was supposed to prevent this sort of thing? Im running 5.0.2 stock. I'm fairly versed on this subject so this is becoming very frustrating for me, ive been trying for over a week now. I know i could flash a rooted rom but i have tried literally at least 12 different ones for every variation of my phone possible, from CM 11 up to CM13.. and when I go to flash it says (roughly) "this file is for A5, A5DUG, A5.., This phone is A5dug"......How is that possible? I dont know if this is relevant or not but when im in recovery mode up top it says "A5chl" in the specs area... but thats not what it seems to think it is? I have managed to successfully flash once but it was for a dual sim variant of the 816, needless to say it was jacked up and i had to go back to stock. I must be missing something.. Anyways, im rambling on now. Im desperate, PLZ help me. I have run out of ideas and losing hope quickly.
Cheers,
Mikey
Click to expand...
Click to collapse
Truly, no offense meant but you're evidently not that well versed because you didn't need to flash any of those exploits to obtain root on the 816 a5_chl VM version because I didn't do any of that and I have root on this same device using V_ Superuser's XDA tutorial thread.
Unlock bootloader through HTCdev then flash current TWRP version for the A5 using ADB/fastboot then download the SuperSU flashable zip file from it's website to the root of your internal SD card then install/flash the zip file using the newly installed TWRP custom recovery. Wipe cache and Dalvik cache then reboot system and you're device is rooted.
After this you can S off with the Sunshine app (my preference) or flash the lollipop WP_ mod.no write permission mod to be able to use root apps like Link2SD and you're done again.
Edit: I've also flashed all of these same custom roms with little issue so something else must be going on there as well. I would get your stock recovery reinstalled ( there are several links to it here in XDA ) ,relock your bootloader and flash/run executable of the stock RUU for the VM A5 found on HTC's download page then start over because I assume you don't have a backup to the stock firmware saved somewhere ?
http://forum.xda-developers.com/desire-816/general/ruu-t2952058

Categories

Resources