Database Develop

Rooting .290 JB 4.3

Hello,
Coming from a Galaxy S2 flashing and rooting is not new to me but for me there are some questions for the Xperia Z1.
When i bought the Z1 it was on 4.2.2, and offcourse i wanted root the same day
After trying numerous times with Vroot i gave up.
After some more reading i read that i had to downgrade and then flash an older version, then root and flash teh correct version and so on.....(cant find the correct topics anymore )
After doing that my phone wasnt working properly and i connected with PC Companion and it gave me the update to .290 JB 4.3 and everything was fine except foor root.
Did some more reading and found the solution,
Now I'm reading that if you are on .290 4.3JB that root isnt possible(correct me if im wrong).
I want to share how i did it because for me it went very easy.The hardest part was getting the drivers installed correctly hhaha
First i unlocked the bootloader and then i flashed a CWM with root and recovery.
I followed the steps provided on this links.
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
http://techbeasts.com/2013/12/19/in...ng-latest-14-2-0-a-290-firmware-how-to-guide/
Al of this went so easy that i'm startin to wonder if its me who did it wrong and dont understand it or if you didnt know about it,
The only thing i forgot was a TA backup :angel:
to MODS....if its in the wrong section please replace it.

Actually it is the official way. Unlock -> CWM -> Root with CWM (Notification)
Rooting 4.3 isn't impossible, but morr difficult than on earlier versions. Google wanted to improve the security of android. Most of the ways which "make" the opportunity of rooting are malware-ways too.
You don't need to backup your TA partition with .290 and above, because the camera will work after the BL unlock.

The big question is if root for unlocked boot loaders will ever be available for 4.3! I really doubt it.
Sent from my C6903 using xda app-developers app

You mean Locked Bootloader, i think?
Question about CWM, does it function the same as it did with my S2? So, back-up and restore with CWM?
sent from rooted en unlocked 4.3 Jb Xperia Z1

djg269 said:
Question about CWM, does it function the same as it did with my S2? So, back-up and restore with CWM?
sent from rooted en unlocked 4.3 Jb Xperia Z1
Click to expand...
Click to collapse
it should, why are u asking ?

Curious
Eager to try but not in the mood for a complete do over if it fails
sent from rooted en unlocked 4.3 Jb Xperia Z1

Ohh, I will be glad to rooting without unlocking BL...on 4.3..but still no way...

This works just fine, thanks for sharing this! Just FYI, this is also an interesting read about getting full root access on 4.3: http://forum.xda-developers.com/showthread.php?t=2573921

eclyptos said:
Ohh, I will be glad to rooting without unlocking BL...on 4.3..but still no way...
Click to expand...
Click to collapse
I have heard from @shem2409 that a partial root on LB for 290 (4.3) is possible, but I have not figured out how to do it yet. I think you can pull it off with the insecure ramdisk hack, but to install that, you need to install XZDualRecovery; to install XZDR, you need to be rooted; it's only possible to root 534 LB and when upgrading to 290 root is lost. So, it seems to be a chicken-and-egg problem to me at the moment. I think I must be missing something.

xasbo said:
I have heard from @shem2409 that a partial root on LB for 290 (4.3) is possible, but I have not figured out how to do it yet. I think you can pull it off with the insecure ramdisk hack, but to install that, you need to install XZDualRecovery; to install XZDR, you need to be rooted; it's only possible to root 534 LB and when upgrading to 290 root is lost. So, it seems to be a chicken-and-egg problem to me at the moment. I think I must be missing something.
Click to expand...
Click to collapse
That's why I do not rooted mine phone yet. Partial root is not worth to do, full root is what we really need but still under testing and also Unlocked Bootloader is needed. Unlock bootloader we lose the DRM keys which we need if one day we want go back to stock and not lose warranty but to do that we have to Buckup TA. To Backup TA we need root, but I updated to 4.3 and I can't. It's to early to fully rooting 4.3. We have to wait. Developers are working on that and I hope a full root come without unlock bootloader. I hope so.

eclyptos said:
That's why I do not rooted mine phone yet. Partial root is not worth to do, full root is what we really need but still under testing and also Unlocked Bootloader is needed. Unlock bootloader we lose the DRM keys which we need if one day we want go back to stock and not lose warranty but to do that we have to Buckup TA. To Backup TA we need root, but I updated to 4.3 and I can't. It's to early to fully rooting 4.3. We have to wait. Developers are working on that and I hope a full root come without unlock bootloader. I hope so.
Click to expand...
Click to collapse
If you want to backup TA now, you can - flash back to any 534 FTF, root, make your backup, then upgrade back to 290.

xasbo said:
If you want to backup TA now, you can - flash back to any 534 FTF, root, make your backup, then upgrade back to 290.
Click to expand...
Click to collapse
This is what I don't want to do. Unlocking Bootloader on 4.3 will also compromise few features like Bionz and X-Reality. I don't think I really need them but for me will be good enough to have Full Root with Locked Bootlader and Apps to SD. I don't ask to much, so I wait.

eclyptos said:
This is what I don't want to do. Unlocking Bootloader on 4.3 will also compromise few features like Bionz and X-Reality. I don't think I really need them but for me will be good enough to have Full Root with Locked Bootlader and Apps to SD. I don't ask to much, so I wait.
Click to expand...
Click to collapse
You just took those words from my fingers. The wise way here is waiting and cheering developers to figure out how things work with Z1, 4.3 just came a few weeks ago and (hopefully) we will get 4.4 soon, so for that time you'll have to do that trickery again to keep your phones rooted.

AntiDroid said:
Actually it is the official way. Unlock -> CWM -> Root with CWM (Notification)
Rooting 4.3 isn't impossible, but morr difficult than on earlier versions. Google wanted to improve the security of android. Most of the ways which "make" the opportunity of rooting are malware-ways too.
You don't need to backup your TA partition with .290 and above, because the camera will work after the BL unlock.
Click to expand...
Click to collapse
I mistakenly took the .290 update as well and I'm now looking for a way out. This whole backing up the TA thing worries me because I'm afraid I'll lose those DRM keys and bravia etc..... Are you saying that I will be fine and all the keys will be intact if I follow this guide?
Is it possible to downgrade the firmware instead?
What would you suggest?
Thanks

xasbo said:
I have heard from @shem2409 that a partial root on LB for 290 (4.3) is possible, but I have not figured out how to do it yet. I think you can pull it off with the insecure ramdisk hack, but to install that, you need to install XZDualRecovery; to install XZDR, you need to be rooted; it's only possible to root 534 LB and when upgrading to 290 root is lost. So, it seems to be a chicken-and-egg problem to me at the moment. I think I must be missing something.
Click to expand...
Click to collapse
Ok, so here is a little clarification
You need to downgrade to .534, root, install recovery and then flash a prerooted .290 rom from (http://forum.xda-developers.com/showthread.php?t=2572988) or one of the stock-based custom roms such as monxdified (http://forum.xda-developers.com/showthread.php?t=2463675) if you want a partially rooted, locked bootloader 4.3 firmware on your Z1. There is an instruction on how to install on locked bootloader in the thread.

Rooting on the newest version of Android 4.3.3 isn't impossible on the Xperia Z1, it just takes you more steps than normal to actually get full root access. I have a locked bootloader as well but I was able to get a rooted version of Android 4.3.3, specifically the iHackers 2.0 ROM running Android 4.3.3 with full root access. Here's how I got full root access on the iHackers 2.0 ROM:
1) Download the .ftf file named C6903 14.1.G.1.534 Global 1277-2880_R4A from the compiled FTF thread at this link: http://forum.xda-developers.com/showthread.php?t=2469191
This is a version of the original Stock Rom that the VROOT program will actually work on when trying to ROOT your phone.
2) Flash the ROM you downloaded using Flashtool (steps on how you can go about doing that should be in the Xperia Z1 General forum.) and now, you're ready to root your phone with it.
3) Download, install and run VROOT to root your phone. Again, more information on how to properly root your phone using VROOT can be found in the Xperia Z1 General forum. For me, I just turned on USB Debugging on my Z1, connected my phone to my computer while VROOT was running and clicked the green button until I got root access. It's extremely easy.
4) With Root Access, now you can download and install Dual Recovery for the Xperia Z1 on your phone.
5) Download the latest iHackers 2.0 ROM from the Xperia Z1 Android Development thread and copy it to your phone. This is hands down, the best ROM for the Xperia Z1 right now in terms of battery life. With the latest 4.3 update, I'm able to get over 2 Days worth of battery life on one charge. Battery life is much better on the new iHackers 2.0 ROM running Android 4.3.
6) Download the flashable Locked Dual Recovery for the Xperia Z1 here. http://nut.xperia-files.com/
The file is called XZ-lockeddualrecovery2.7.63-BETA.flashable.zip (8.48MB), download it and copy it to your phone, preferably the same place you copied the iHackers 2.0 ROM. To make things easier for yourself, create a new folder on your phone or SD Card in your phone and name it iHackers. Copy both the iHackers 2.0 ROM and the flashable Locked Dual Recovery.zip file into this folder.
7) With both files now copied to a folder on your phone, you're now ready to go into recovery to flash the iHackers 2.0 ROM. Boot into recovery and once you're there, do a Wipe Data/Factory Reset before Installing the ROM.
The rest of these steps are now taken directly from the iHackers 2.0 download thread on the Xperia Z1 Android Development forum.
8) Install the ROM and THEN Dual Recovery. Don't make the same mistake I did, once the installer is finished, DON'T REBOOT THE DEVICE. Uncheck the "Reboot Device" box and go back to recovery to install the flashable Dual Recovery.zip file that's in the iHackers 2.0 folder.
9) Switch Off Your Phone (Do Not Reboot). Select No to Disable Flash Recovery Confirmation.
10) Install Kernel.ftf for C6903 (.290) or Kernel.ftf for C6902 (.290) with Flashtool to get compatible Kernel and Baseband. To download the kernel.ftf file, go to the original iHackers 2.0 thread to download and flash the kernel using Flashtool. You should be familiar with Flashtool at this point since if you make it to this step, you've already used Flashtool once to flash the .534 baseband version of Android.
11) Reboot and Enjoy. Now you're running the latest version of Android 4.3 on your Xperia Z1 on a Locked Bootloader WITH full Root Access. Sure, it's not the stock version but the iHackers 2.0 version of Android 4.3 is just as good, if not better. This will certainly do until there's a better way to simply root the newest Stock Version of Android 4.3.
I've been looking into unlocking my bootloader to install custom kernels on my Z1 but the battery life and performance on my Z1 with a locked bootloader is already pretty impressive. I can't imagine how good it could be with a custom kernel.

deli pastrami said:
Are you saying that I will be fine and all the keys will be intact if I follow this guide?
Click to expand...
Click to collapse
No, if you Unlock Bootloader you will lost the DRM keys permanently with Bionz and X-Reality, even with Android 4.3, if you do not do a backup, but the difference from 4.2 is that your phone will still working properly.
deli pastrami said:
Is it possible to downgrade the firmware instead?
Click to expand...
Click to collapse
Yes.
deli pastrami said:
What would you suggest?
Click to expand...
Click to collapse
Nobody can suggest what to do. You have to figure out by yourself what you need. It's your own risk.
---------- Post added at 12:11 AM ---------- Previous post was at 12:00 AM ----------
x016x said:
Rooting on the newest version ..bla..bla..bla
....bla..bla..bla..bla...king my bootloader to install custom kernels on my Z1 but the battery life and performance on my Z1 with a locked bootloader is already pretty impressive. I can't imagine how good it could be with a custom kernel.
Click to expand...
Click to collapse
Thanx man. I appreciate the time you took to explain the process step by step. One step very important you forgot to mention, Backup TA, never forget to mention that. Anyway I will check if this actually get me full root and all the stuff and when I finally will lose my patient I will start follow the guide and flashing and burning my Z1.

shem2409 said:
Ok, so here is a little clarification
You need to downgrade to .534, root, install recovery and then flash a prerooted .290 rom from (http://forum.xda-developers.com/showthread.php?t=2572988) or one of the stock-based custom roms such as monxdified (http://forum.xda-developers.com/showthread.php?t=2463675) if you want a partially rooted, locked bootloader 4.3 firmware on your Z1. There is an instruction on how to install on locked bootloader in the thread.
Click to expand...
Click to collapse
Ahh, cheers, I thought there was a way to root any arbitrary ROM, that's where I was getting hung up. The pre-rooted options make total sense.
eclyptos said:
Thanx man. I appreciate the time you took to explain the process step by step. One step very important you forgot to mention, Backup TA, never forget to mention that. Anyway I will check if this actually get me full root and all the stuff and when I finally will lose my patient I will start follow the guide and flashing and burning my Z1.
Click to expand...
Click to collapse
The instructions didn't say to unlock the bootloader, which is the only sure-fire way to lose your TA partition. However, I would agree there's no good reason *not* to back it up anyway. Better safe than sorry!

xasbo said:
The instructions didn't say to unlock the bootloader, which is the only sure-fire way to lose your TA partition. However, I would agree there's no good reason *not* to back it up anyway. Better safe than sorry!
Click to expand...
Click to collapse
Ahhh, ok, so you are confirming that the guide is incomplete and we have to unlock bootloader anyway if I follow that? Hmmm...I am a bit puzzled.

eclyptos said:
Ahhh, ok, so you are confirming that the guide is incomplete and we have to unlock bootloader anyway if I follow that? Hmmm...I am a bit puzzled.
Click to expand...
Click to collapse
Sorry, no. In his instructions, UB is not necessary because XZDualRecovery can be installed on LB. The reason skipping the TA backup is okay is because the instructions do not unlock the BL.

[Q] Point me in the right direction...??

Hi there guys!
I want to root my Z1 c6906, unlock the bootloader and flash custom roms, but im kind of confused right now because i have read a lot of different guides and im not pretty sure which one to follow now. I also learned on one thread that i should do a TA and DRM Keys backup because they can be lost forever if i don't do a backup. Also the IMEI. So im not pretty sure how to do that. Also saw a thread about bricking the device, and kind of got scared. Btw, i have plenty of experience working on Android devices, unlocking, rooting, flashing roms, etc. I have used Android since the G1, but im kind of confused right now about how to proceed on this device because this is my first Sony and my last phone was a Nexus 4, which was virtually unbrickable. Can anyone help me out here?

djluis48 said:
Hi there guys!
I want to root my Z1 c6906, unlock the bootloader and flash custom roms, but im kind of confused right now because i have read a lot of different guides and im not pretty sure which one to follow now. I also learned on one thread that i should do a TA and DRM Keys backup because they can be lost forever if i don't do a backup. Also the IMEI. So im not pretty sure how to do that. Also saw a thread about bricking the device, and kind of got scared. Btw, i have plenty of experience working on Android devices, unlocking, rooting, flashing roms, etc. I have used Android since the G1, but im kind of confused right now about how to proceed on this device because this is my first Sony and my last phone was a Nexus 4, which was virtually unbrickable. Can anyone help me out here?
Click to expand...
Click to collapse
Quite simple process actually, just flash .534 ftf with flashtool and root with bin4ry or use nuts dual recovery installer. To backup your ta before unlocking bootloader, simply use the Backup TA tool

Ahki767 said:
Quite simple process actually, just flash .534 ftf with flashtool and root with bin4ry or use nuts dual recovery installer. To backup your ta before unlocking bootloader, simply use the Backup TA tool
Click to expand...
Click to collapse
Thanks. And what about the DRM keys?

djluis48 said:
Thanks. And what about the DRM keys?
Click to expand...
Click to collapse
The DRM keys are in the Ta partition

Ahki767 said:
The DRM keys are in the Ta partition
Click to expand...
Click to collapse
I see. Another question, i see that for my devices the only .534 TFT available is for Rogers. There is no problem if i flash using Flashtool?

djluis48 said:
I see. Another question, i see that for my devices the only .534 TFT available is for Rogers. There is no problem if i flash using Flashtool?
Click to expand...
Click to collapse
Yes, I'm sure there'll be no problems

Ahki767 said:
Yes, I'm sure there'll be no problems
Click to expand...
Click to collapse
Sorry for bringing back this thread. Now i got time to start trying to unlock the phone and flash custom roms, was extremely busy before with work.
New problem: After i downgraded to FTF .534, rooted and made the TA Backup, i check if the phone was "allowed" to be unlocked and surprise, it says it can't be unlocked. Tried unlocking with Flashtool and it said the same thing. Can the phone be unlocked or is there a way to flash roms without unlocking?
Right now im feeling really depressed with this phone. If i can't unlock it, i most likely will sell it and get something that can be unlocked.
One of the reasons i want to unlock is because on 4.4, Google prohibited the phone to write on the Ext.SD and i want a way to overcome that prohibition and use it like i was able to on 4.3.

If it says it cannot be unlocked then it cannot be unlocked
However, you can still sort out the issue of writing to the ext SDcard by rooting and following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2687966
In order to do that, you only need root, not to be unlocked

gregbradley said:
If it says it cannot be unlocked then it cannot be unlocked
However, you can still sort out the issue of writing to the ext SDcard by rooting and following the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=2687966
In order to do that, you only need root, not to be unlocked
Click to expand...
Click to collapse
Ok. That sucks. Thanks for the link.
Another question: How i root.757? I was able to root .534, but not sure how i need to proceed now. Do i need to download generic .757 and apply any root method? Or the root will still be there if i flash it over my current rooted .534?

1) Flash a stock 534 FTF (Ignore if you are already on 534)
2) Install dual recovery (Find files and instructions in the XZ dual recovery thread in the cross device development section)
3) Flash a prerooted 757 rom (Find files and instructions in the development section)
Done, 3 easy steps

gregbradley said:
1) Flash a stock 534 FTF (Ignore if you are already on 534)
2) Install dual recovery (Find files and instructions in the XZ dual recovery thread in the cross device development section)
3) Flash a prerooted 757 rom (Find files and instructions in the development section)
Done, 3 easy steps
Click to expand...
Click to collapse
So i can flash any rom now with that recovery? Even if my bootloader is still unlocked? Or only stock based roms?

djluis48 said:
So i can flash any rom now with that recovery? Even if my bootloader is still unlocked? Or only stock based roms?
Click to expand...
Click to collapse
If your bootloader is unlocked you can flash any rom from the development sections or the original development section
But if your bootloader is unlocked you do not need to do any of this to root.
Just flash DooMKerneL or [NUT]s XZDR kernel
If your bootloader is locked, you have to downgrade and root that way. Then you can flash any stock based rom, look in the development section for them

gregbradley said:
If your bootloader is unlocked you can flash any rom from the development sections or the original development section
But if your bootloader is unlocked you do not need to do any of this to root.
Just flash DooMKerneL or [NUT]s XZDR kernel
If your bootloader is locked, you have to downgrade and root that way. Then you can flash any stock based rom, look in the development section for them
Click to expand...
Click to collapse
Oops. Im sorry. I meant locked. Was doing something else and wrote that fast. Thanks for the answer. Will check. Got the DualRecovery installed now and will try to install a prerooted .757 later.

[Q] Upgrading to Lollipop from locked bootloader, rooted, Kitkat.

Hello all,
With news that the Z3 and Z3 compact are starting to get Lollipop today I am sure a lot of people are going to be coming to the boards asking this exact question. So I wanted to start a thread that can help people find the answer quickly. (I'll update the OP as useful info comes in.)
I am currently on a D5803 running 4.4.4, with a locked bootloader and am rooted. I used This how-to to get where I am.
What is the best way to upgrade to Lollipop for me?
Is there a way to keep root? A pre-rooted FTF file?
Will all DRM features remain?
Will I need to reinstall anything? Recovery? Busy Box? SU?
Does this upgrade require a full wipe?
Thanks for any help
If anyone wants to check if their bootloader is locked:
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked

just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?

TheTomcraft said:
just wonder...
i definitly want to root my Z3C.
Should i root with KK 4.4 or wait for Lollipop(and root later) !?
Click to expand...
Click to collapse
You root on KK then you can update to Lollipop and keep root.

The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?

Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!

gruev said:
could you please write what exactly you did to achieve this. Step by step guide would be awesome. Thanks!
Click to expand...
Click to collapse
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.

q.
frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
Did you wipe? or flash over?

newbie2006 said:
Did you wipe? or flash over?
Click to expand...
Click to collapse
I wiped it (had too much crap on the phone anyway, so worth it), restored what I wanted with Titanium Backup when done.
---------- Post added at 10:24 PM ---------- Previous post was at 10:19 PM ----------
I also tried with flashing lockeddualrecovery but recovery doesn't work. So need to wait for an update on that one I guess.

Any ideas about what could go bad if I don't wipe data?
Also, do you still have drm?

I succesfully flashed lolipop with this method without data wipe. I still have root and DRM keys. The only thing I lost was data of some app's with external data linked to SD card with Link2SD. And some root app's started to claim about busybox not installed properly. Besides that everything works like a charm

frason said:
Flashed "D5803_23.1.A.0.690_Customized_NCB rooted.zip" in TWRP.
Without rebooting, flashed "UPDATE-SuperSU-v2.46.zip" in TWRP.
Done, working root.
Click to expand...
Click to collapse
When you flash those do you have system read and write as well? Do we need to worry about the RICDefeat in doing all this for the upgrade? Is RICDefeat integrated into that?

1.Flash the tft of lollipop
2.Get the zip of XZDualRecovery 2.8.3 Advanced Stock Kernel from http://nut.xperia-files.com/ and supersu from http://forum.xda-developers.com/showthread.php?t=1538053
3.Flash the boot.img in AndroPlusKernel with cable on flashtool
4.Reboot in recovery
5.Flash XZDualRecovery 2.8.3 Advanced Stock and supersu
6.Enjoy
Sorry，it should be with UB

about not working recovery
Dont know it thats issue, but I have same clue.
On KitKat after applying all steps to root 4.4.4 rom recovery was working until I changed busybox.
Oryginaly busybox was in version 1.20.2-jb - with that recovery was working.
I need some other tools and updated busbox to version 1.22.1 and recovery wasnt working (starting recovery end up with bootloop, but could start to system).
Returning back to recovery 1.20.2-jb fixed problem.

frason said:
Recovery isn't working, but I'm happy with just root for now, which works great.
I didn't flash the stock after SuperSU, don't see any reason to and works for me.
Click to expand...
Click to collapse
Sean09 said:
The problem seems to be getting recovery working, or keeping it working. Can anyone comment on whether they've tried the below:
1) Flash pre-rooted D5803_23.1.A.0.690_Customized_NCB rooted.zip containing Lollipop 5.0.2 in TWRP
2) Flash Z3C-lockeddualrecovery2.8.3-RELEASE.flashable.zip in TWRP
3) Flash UPDATE-SuperSU-v2.46.zip in TWRP
4) Flash the stock D5803_23.1.A.0.690_Baltic_Generic.ftf and exclude system (and data/cache from the wipe section to keep settings)?
In the other recovery threats NUT seems to think his recovery should still work?
Click to expand...
Click to collapse
I was hoping by adding step 4, it would be possible the encrypt device. Sadly it still creates a bootloop.

in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?

skaarax said:
in my case I received the notification update via OTA, have Kit Kat with root if I update, will i lose root?
Click to expand...
Click to collapse
I want to know about this too.
And what is a safe process for us (locked bootloader, rooted 4.4) to upgrade to 5.02 or 5.1 in the future.
I heard that unlocking bootloader will causes the camera not working properly (at least the auto mode would be messed up)
Does TWRP requiring unlocking bootloader?
Thanks guys.

I'm resurrecting this thread as I've got the same question as previous posters and I've not been able to find an answer elsewhere on the forum.
Basically, I've got a phone with a Bootloader which can't be unlocked. I upgraded/rooted it last year. It's still on KitKat. Is there any way I can upgrade it to Lollipop or Marshmallow without going through the downgrade/flash pre-rooted ROM procedure, without losing root? In other words, can I make use of TWRP which I installed in order to flash the rooted ROM last time? If so, how? (I'm not keen on using KingRoot unless somebody can convince me that handing over my IMEI info is safe.)
Thanks in advance.

Just flash a pre-rooted 5.1 zip made with prf creator whilst still on root+recovery KK. That's how I updated my M2 from rooted 4.4.4 KK to rooted 5.1 lollipop whilst retaining my locked bootloader. No sure if it's working for mm yet though this way

[Q] why downgrade when you can flash FW with root? // backup DRM

hey guys,
why do you have to downgrade the fw to 4.4.4 if you could easily flash a new firmware with root included already?
guide I used: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
also, where are the DRM keys in the file system? I use Linux and I can't use the mentioned Windows bat file tool to back them up. And I don't want to rewrite the batch files into a shell script...

The DRM keys are raw data inside seperate partitions as far as I have understood it correctly. Maybe someone can comment on the details but you should be able to dump them using dd if you identify the correct partitions.. On the first question, I would be interested in this too.
Why would you downgrade and root if you can flash a pre-rooted image?
How come you can flash a pre-rooted image with locked BL? Doesn't the phone check CRC before flashing a firmware with locked BL? Doesn't it refuse to flash if tampered with? How does that work?

Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.

faxd said:
Regarding TA-backup
someone worked on a linux port, see
https://github.com/DevShaft/Backup-TA/issues/10
However unfortunately the original developer (Devshaft) is afk and doesn't merge it...
https://github.com/DevShaft/Backup-TA/pull/10
and
https://github.com/DevShaft/Backup-TA/issues/6
unlocked Bootloader vs Root
These things doesn't have to do with each other.
Root is "basically" when you have the su binaries in your system partition.
An unlocked bootloader you need only when you want to flash (/boot from) a non-stock / custom kernel, e.g. cyanogen mod.
Click to expand...
Click to collapse
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?

pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff? Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
I have this question too.
Maybe because pre root images can have something installed that could hazardous?

I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.

pakjebakmeel said:
Hiya, thank you for the reply. I am aware of what root is, the point is that the guides to root indicate you need to flash the old version of KitKat and use the expoit to gain root so the bootloader can remain locked. Then you should upgrade to lollipop while keeping root.
My point was that there are also pre-rooted images available, why not just flash a pre-rooted image using Flashtool instead of doing the exploit and stuff?
Click to expand...
Click to collapse
To quote someone else:
twisteroid said:
Well, because you need a recovery to flash the pre-rooted zip, and to have a recovery you have to root first. The pre-rooted SYSTEM partition cannot be flashed using Flashtool because it would not pass signature check. The only way to flash it is to use root access and a working recovery.
Click to expand...
Click to collapse
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
pakjebakmeel said:
Or does the pre-rooted image not flash on a locked bootloader because it has been modified?
Click to expand...
Click to collapse
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH

faxd said:
To quote someone else:
And here you are still confusing root with (locked/unlocked/whatever) bootloader:
Read above this doesn't has to do with the bootloader, but rather if you have access to the system partition.
HTH
Click to expand...
Click to collapse
No, no, I think I got it now but my wording is a bit off I guess. Here are my understandings:
- Flashtool flashes through Sony firmware flash mode, this mode only flashes official tft files that pass signature check. When you add root to an image it fails signature check because of the mismatching hash and it will refuse to flash.
- To flash a 'tampered' image you need to use a custom recovery as it does not refuse.
- To get a custom recovery you need to get root to be able to flash the recovery partition.
- To get root you need to downgrade and use the exploit to get the su binary on.
Correct right?
Just one more question, how does the signature check work? I would understand it if you could download images from Sony like OTA's, they'd be signed and sealed by Sony. Just like driver signing based on RSA keys and such. If you modify them they fail the signature check obviously.
But I've seen people create FTF files from their own phones and it seems to pass the signature check, how is the file signed then? What is the 'signature' check based upon? Or is the image signature included on the phone and pulled into the FTF file when the image is pulled from the phone?
So basically the question is: "Where does the signature come from if one would create an FTF file from a working phone?"
Sorry, sorry, many questions. I'm just trying to understand all details, can't stand not knowing how stuff works.. :silly: I think I at least understand the root/bootloader/recovery part now. :victory:

phre5k said:
I pulled the TA / DRM keys manually like this:
Code:
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
exit
exit
adb pull /sdcard/TA.img TA.img
Worked flawlessly. Then I flashed an image I rooted myself with Linux zip tools. Worked, too. TA didn't change, so I suspect you can flash a pre-rooted image without problems in the first place.
Click to expand...
Click to collapse
Restore goes well with this simpler method as well?

PantsDownJedi said:
Restore goes well with this simpler method as well?
Click to expand...
Click to collapse
Windows script does the exact same thing after looking at it, it does some logic for looking at the partitions a bit better is all. Hopefully nothing has changed since newer versions of Andriod.

[Q] How to make a pre-root 5.1.1 ROM?

I have downloaded .368 ROM via XperiFirm, and is there any way to make a pre-root FTF?
Thanks for reading and replying ~

Hi, I somwhere heard an application PRF Creator. I am not familiar with this app but I think it is the base of creating pre-rooted FTF. I have found some tutorial looks pretty simple use for me.
http://techbeasts.com/2015/07/26/how-create-sony-xperia-pre-rooted-firmware-prf-creator/
I am going to try to create an FTF for my Z1 with this and flash on my device and then tell if that worked for me
Edit: Found an thread on XDA about this tool here: http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904

Download PRFCreator, SuperSU, and XZDualRecovery. Point PRFCreator at the three other files (FTF, SuperSU zip, XZDR zip), click go, go have a cup of coffee. Job's done.

So I tried using this app and it made an .zip file instead of .ftf as i thought it would make. Is there anyway to make a pre-rooted .ftf?
You can make your pre-rooted firmware with that tool mentioned in other replies but if you want root on your device, you'll still need to have root or recovery if you don't have any of those you'll need to unlock yours bootloader(which I didn't want to do for my device because it wipes all data from device(It is possible to do a backup&restore from sony pc companion) in order to flash recovery and your fw.zip.
Or you can hang out a while until kingoroot or any other rooting apps will make root available for 5.1.1 xperia devices without recovery and/or with locked bootloader
Someone correct me if I am wrong at some point.

That is accurate. I have not seen any pre-rooted FTFs. Many people use the misnomer pre-rooted FTF to describe a flashable zip which has been pre-rooted.

We'll i just found out i was wrong about bootloader. You don't need to unlock bootloader instead you can downgrade your firmware check out this tut
http://techbeasts.com/2015/09/18/root-install-recovery-on-xperia-z1-android-511-146a0368-firmware/
Also the prerooted firmware you'll make with PRF Creator will be useful for this method

MrBratka said:
We'll i just found out i was wrong about bootloader. You don't need to unlock bootloader instead you can downgrade your firmware check out this tut
http://techbeasts.com/2015/09/18/root-install-recovery-on-xperia-z1-android-511-146a0368-firmware/
Also the prerooted firmware you'll make with PRF Creator will be useful for this method
Click to expand...
Click to collapse
It seems you didn't red carefully enough.
Most tutorials here already describe that you don't need to unlock your bootloader.
But now you got it.

How to create a pre-rooted 5.1.1 stock ROM?
Click to expand...
Click to collapse
ANSWER: Click here
Note: The guide is "How to create a pre-rooted 5.0.2 stock ROM" BUT the procedure on how to create a pre-rooted 5.1.1 stock ROM is exactly the same.