Hello community, I have decided to root and install a custom rom to my xzp,
I have followed j4nn guide downgrade my xzp G8141 from 9.0 to 8.0 for temp root and TA backup before unlocking the bootloader, I have saved all 3 copies well, things have gone wrong after unlocking the bootloader, installing the latest fw with newflasher, in the menu service has changed, now I have these errors. I have the eXistenZ pie on my xzp, the video enhancement not working.
Here are 3 screenshots in comparison
1 first of all, with stock 9.0 fw,
2. the one after downgrade to 8.0 without modifying anything,
3. 8.0 fw after unlocking the bootloader
4. after installing custom rom and with TA-locked.img restored. a hide unlock kernel flashed, continue with ERROR
Thanks to all in advance
Related
Hi!
In february I unlocked by bootloader and rooted my Z5 following thsi guide.
As you can see on the screenshots I am on version 32.0.A.6.200.
My phone is branded by the "Deutsche Telekom".
Now I have seen (in XperiFirm) that there is a version "Telekom.de DE 32.1.A.1.185" available.
I cannot figure out how to update an already unlocked/rooted device with stock rom to the newest firmware without loosing the root/unlock status and without wiping all the data.
Ikarisan said:
Hi!
In february I unlocked by bootloader and rooted my Z5 following thsi guide.
As you can see on the screenshots I am on version 32.0.A.6.200.
My phone is branded by the "Deutsche Telekom".
Now I have seen (in XperiFirm) that there is a version "Telekom.de DE 32.1.A.1.185" available.
I cannot figure out how to update an already unlocked/rooted device with stock rom to the newest firmware without loosing the root/unlock status and without wiping all the data.
Click to expand...
Click to collapse
yuo can update with flashtool but you have to root again flashing a recovery and flashing supersu after that another way will be a flasheable zip but i think even you have to flash the kernel with flashtool.
if you don´t want wipe anything ensure unchek all marks on wipes part in flashtool.
People,
Before anything else, all the links cited are links from XDA
I got a Z3 D6643 (Similar to the D6603 but with Digital TV) completely stock, MM .291, no ROOT, no Bootloader Unlocked, no nothing. I am reading all posts about Rooting and Unlocking Bootloader, but unfortunately the information is very diluted. Each thread has its own method, some let me understand that I can flash Custom Roms that will be fine, others let me understand that I can only install mods (Cyberian Camera, or some SystemUI Port for example).
And then when I decided to try something, like install a Custom Recovery (TWRP), It says in the instructions that it is necessary to unlock the bootloader (which causes the DRM keys to be lost).
So, I discovered that there is a tool that backs up DRMs (TA Backup), and guess what? It needs Root.
So let's try to do rooting... Hmm nah, just for old firmwares.
Let's try another method then... Nope, just for Unlocked Bootloader.
And there's this thing about Upgraded Bootloader, which is not clear if I (in the last stock version) need to do it.
Well, I would be extremely grateful if some good person could point me posts/videos ~whatever~, about what I can do, I'm sure it would be helping not only me, but others who search the forum. :good:
You kind of answered your problem yourself. The root without BL unlock needs an older firmware, so just flash the older firmware with flashtool or EMMA and you can root, make your TA Backup etc.
But to be honest it is not worth the hassle. I did a TA Backup when I got the device (the year it came out) and I never restored it.
In the beginning of development for the Z3 it was a problem because the camera was far worse without the DRM protected features.
The new roms (LOS 14.1 for example) have close to stock camera quality, though.
And the other few DRM features aren't really worth it either in my opinion.
So my suggestion would be:
- Unlock your bootloader (Official Sony Link)
- Flash the .291 firmware through EMMA to get the upgraded bootloader (EMMA DL Link)(EMMA Instructions Link, Important!)
----You won't need to if you already have the .291 firmware installed through EMMA before (check Device Settings), the "normal" (OTA) update to .291 doesn't work, because it won't update the bootloader
- Fastboot flash a recovery (preferably TWRP 3.1.0 by naylik) (XDA Link)
- Flash the latest LineageOS 14.1, besides some minor bugs it is daily driver material (XDA Link)
- Flash GApps (right after flashing LOS, don't boot into the rom), I use OpenGapps (XDA Link)
- Flash your preferred SuperUser Mod if you want to (Magisk, SuperSU etc.) or roll with the LineageOS one
You won't be able to flash any up-to-date custom rom without unlocking your bootloader.
The confusion about the upgraded bootloader is another topic, I would upgrade it as it
doesn't hurt in any way and gives you a way easier accessable, persistent recovery.
But please always follow the instructions in the threads
Be aware that you can lose your data, so backup anything important, and that you will probably lose your Digital TV, as it is variant specific.
Omario-242 said:
You kind of answered your problem yourself. The root without BL unlock needs an older firmware, so just flash the older firmware with flashtool or EMMA and you can root, make your TA Backup etc.
But to be honest it is not worth the hassle. I did a TA Backup when I got the device (the year it came out) and I never restored it.
In the beginning of development for the Z3 it was a problem because the camera was far worse without the DRM protected features.
The new roms (LOS 14.1 for example) have close to stock camera quality, though.
And the other few DRM features aren't really worth it either in my opinion.
So my suggestion would be:
- Unlock your bootloader (Official Sony Link)
- Flash the .291 firmware through EMMA to get the upgraded bootloader (EMMA DL Link)(EMMA Instructions Link, Important!)
----You won't need to if you already have the .291 firmware installed through EMMA before (check Device Settings), the "normal" (OTA) update to .291 doesn't work, because it won't update the bootloader
- Fastboot flash a recovery (preferably TWRP 3.1.0 by naylik) (XDA Link)
- Flash the latest LineageOS 14.1, besides some minor bugs it is daily driver material (XDA Link)
- Flash GApps (right after flashing LOS, don't boot into the rom), I use OpenGapps (XDA Link)
- Flash your preferred SuperUser Mod if you want to (Magisk, SuperSU etc.) or roll with the LineageOS one
You won't be able to flash any up-to-date custom rom without unlocking your bootloader.
The confusion about the upgraded bootloader is another topic, I would upgrade it as it
doesn't hurt in any way and gives you a way easier accessable, persistent recovery.
But please always follow the instructions in the threads
Be aware that you can lose your data, so backup anything important, and that you will probably lose your Digital TV, as it is variant specific.
Click to expand...
Click to collapse
And then a hero appears, I'm very thankful sir! :highfive:
Hello there,
I hope someone can help me. I got a Sony Xperia XZ today and I wanted to have it rooted of course. That I got to work pretty easily, but I now have the problem that in the Service Info almost everything is "Unknown". Also in the Developer options "OEM unlocking" is disabled (which I find weird) and when I want to enable it it jumps back to disabled. Not sure any of it will cause problems, but that's also why I posted this Thread.
Here's what I've done:
Downgraded from Oreo / 41.3.A.2.99 to Marshmallow 6.0.1 with Flashtool
Created a TA-Backup using Guide: TA Backup v2 | Universal (Dirtycow-based)
Downloaded and flashed to Oreo / 41.3.A.2.107 through Flashtool
Pulled fstab.qcom, init.qcom.rc and init.target.rc
Unlocked Bootloader through Flashtool
Created Kernel.elf from the downloaded Oreo Firmware through Flashtool Sin Editor
Created boot.img as it's decribed in [GUIDE][Oreo 8.0] Stock Kernel + ROOT + TWRP + DRM Fix | 41.3.A.2.99 with my TA.img
and flashed everything as described in the [Guide] above and in Rootkernel V5.23 (UNOFFICIAL 2.5) - OREO - Xperia X, X Comp., X Perf., XZ and XZs and with help of Install TWRP and Root Xperia XZ on Android 8.0 Oreo [DRM Fix] | ThemeFoxx:
Reflashed Oreo 41.3.A.2.107 through Flashtool with checked everything in "Sin"
Flashed my created boot.img through "fastboot flash boot boot.img"
Flashed TWRP through "fastboot flash recovery twrp-3.2.1-0-kagura.img"
Wiped data and formated userdata through TWRP, because TWRP was asking for decryption code
Skipped "Step 6" / flashing DRM-fix_System_Mode.zip through TWRP, because I used munjeni's TA PoC option (But tried it the 2nd time with the DRM-fix too)
Flashed Magisk Magisk-v14.5(1456) through TWRP (Edit: Also tried with v16.1 now)
Installed TWRP app as System App and rebooted normally
Now phone is rooted as I want it, but in *#*#7378423#*#* almost everything in Sercive Info is now "Unknown". When I click the menu "SIM Lock" the Service Menu App crashes, though I don't have inserted a SIM Card yet (but it worked before at the very beginning before I downgraded to Marshmallow)
I've done all this 3 times already, always the same result.
I've searched through this forum and googled for a solution, but I didn't find anything that matches my case/problem.
Screenshots added.
I flashed a Telecom branded 41.3.A.2.99 now with all the files in the Google Drive link from [GUIDE][Oreo 8.0] Stock Kernel + ROOT + TWRP + DRM Fix | 41.3.A.2.99 and now everything looks fine in the Service Menu.
I compared the files. fstab.qcom, init.qcom.rc and init.target.rc are binary indentical as well as kernel.elf. And when I creating the kernel with the files from the Google Drive link (and with DRM-fix instead of my TA.img) it creates a boot.img that is binary different to the one from the Google Drive link.
So every boot.img I have created causes my problem, so it looks like I create wrong boot.img files... I guess I'll post my problem in [ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
I'll leave this thread open for a few days in case anyone has any idea what I can do or until my problem got solved in the meantime.
Edit: I also tried to create a working boot.img with the files from Rooted Kernels F8331 & F8332 41.3.A.2.107 OREO 05APRIL2018, tried with and without my TA.img - both didn't work.
After many tried I'm now just using the KERNEL_F8331_41.3.A.2.107_CLEAN.img from that thread and followed the instructions. I'd like to use my TA.img backup so that under "FIDO KEYS" it doesn't says "not provisioned, provision failed" anymore.
PS: Did a post here now
I had to downgrade to Nougat, because of too many other problems occurred (which still haven't all been solved with Nougat. On Marshmallow they would all be solved, but I don't really want to stay on Marshmallow...)
So this Thread can be closed. If I can help solve that problem, I'll post it in [ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
Hi Everybody,
the last days I was reading several threats and posts about backing up TA-Partition (using iovyroot), repacking the Stock Kernel (with RootKernel) and how to root my Z5 Dual (E6633). But I still have some questions.
First of all: I backed up my TA-Partition, my BL is still locked and my phone isn't rooted till now.
Now my questions:
1) What is the difference between including the TA-Partition into my repacked Kernel and flashing it with FlashTool (creating a FTF from my TA-Partition with Top-RootKernel)? And what is the better option?
2) If the TA-Partition is included in the repacked Kernel (created with RootKernel), do I still have to flash the TA-Partition (as a FTF) afterwards? I think “no“ but I'm not sure.
3) Is there any way I can root my Z5 Dual using a repacked Kernel and flashing my TA-Partition back without losing SU-Privileges and/or BL getting relocked? If yes, ... how can I do this?
Would be great if someone can help me
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
Checked this?
What I previously did ...
Let me show you, what I previously did.
I downgraded to Lollipop and backed up my TA-Partition using iovyroot. After backing up my TA-Partition, I upgraded again to Android Nougat 7.1.1 using Flashtool.
Afther this, I made my own Kernel for Android Nougat (32.4.A.1.54_1309-3895) using the latest Version of RootKernel (which I downloaded from here).
Everything worked fine up till now. But when I was reading the following threats, I got confused.
iovyroot - (temp) root tool
[ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
As far as I know, the Bootloader will be relocked and I will loose Root-Privilegs if I flash back the TA-Partition. If I flash back the TA-Partition using Flashtool as described in the RootKernel-Threat, do I still have unlocked Bootloader and Root-Privilegs?
I am also not sure, when I have to flash back the TA-Partition. If I am using this guide to root my phone, do I have to flash back the TA-Partition as the final step (after flashing the kernel, twrp, and rooting my phone)? Or do I have to flash back the TA-Partition after flashing the kernel and twrp but before rooting my device?
https://twigstechtips.blogspot.com/2016/04/sony-z5-compact-root-without-losing-ta.html?m=1
Check this. You did it right.
I've done it many times
Duvel999 said:
https://twigstechtips.blogspot.com/2016/04/sony-z5-compact-root-without-losing-ta.html?m=1
Check this. You did it right.
I've done it many times
Click to expand...
Click to collapse
Tanks for the link. Now everything has become clear to me and I know what I have to do
Nevertheless I still have some questions.
I know that RootKernel gives me the option to include SuperSU and TWRP directly into a patched kernel.
However, I wonder what would be the better option (perhaps for performance reason or whatever). Is it better to include SuperSU/TWRP into the patched kernel using RootKernel? Or is it better to flash SuperSU/TWRP separately? And what exactly is the difference between the two methods (apart from the obvious)? Anyone who can explain it to me?
Hello
I have a doubt. I am going to buy an xz2c and I want to root. I don't want the black camera. Then my doubts:
1.- To unlock bootloader, do I do it from oreo or from P?
2.- If I buy it already updated to P, then I will have to upgrade to oreo for root with xperifix?
3.- Is it better to buy mobile in Oreo or does it matter? after P upgrade to Oreo and root without problems?
I want to have root and I don't mind staying in oreo or in P, and I want to know what the recommendation is for not having a black camera and the least risks.
Unlock from oreo or P?
Root from oreo or P?
Better to buy oreo or does it matter P and then upgrade to oreo for unlocking?
Thanks and sorry for my English
Please
Hi, I wonder the same. Some post I have read indicate the described problem, but it is unclear if this still applies.
I would love to root, but a broken camera would be a no-go for me.
Can anyone shed some light, please?
Regards UV
P.S: doubt -> question
Simple and easy:
Unlock on oreo -> Preview is black, you need xperifix to get it back working.
Unlock on pie (if i remember right, not the first 2 or 3 pie versions) -> Preview is fine, you don't need to fix it.
Getting root is the same on oreo or pie: flash magisk 18.1 from twrp recovery and install Magisk Manager in Android Os.
If you buy it with oreo or pie does not matter. You can flash up and down (also with locked bootloader) with newflasher as long as you have the firmware files.
old.splatterhand said:
Simple and easy:
Unlock on oreo -> Preview is black, you need xperifix to get it back working.
Unlock on pie (if i remember right, not the first 2 or 3 pie versions) -> Preview is fine, you don't need to fix it.
Getting root is the same on oreo or pie: flash magisk 18.1 from twrp recovery and install Magisk Manager in Android Os.
If you buy it with oreo or pie does not matter. You can flash up and down (also with locked bootloader) with newflasher as long as you have the firmware files.
Click to expand...
Click to collapse
So, unlocking on pie, with first or last firmware?
Enviado desde mi D5803 mediante Tapatalk
I would say, better last than first. But, as i said, it also depends on which firmware is available.