Help me root Z5C. - Xperia Z5 Compact Q&A, Help & Troubleshooting

Hello. So basically my friend has a xperia Z5 Compact phone and he wants to get magisk 19.1 on it. I am new to the phone and do not know how to root it etc. so I need help on getting TWRP and magisk on it. The bootloader is already unlocked because I tried to get TWRP on it but it ended in frozen boot screen. I have since flashed the phone and now need help to actually do something with it.

Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.

casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Alright Im going to try that in the next few days.

casouzaj said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Code:
fastboot flash FOTAKernel twrp.img
Now, to enter TWRP, disconnect it from the computer and hold both the power and the volume down buttons. When the phone vibrates (as if it was being booted up), release the power button; when the screen lights up, release the volume down button. TWRP should come up.
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt

I_did_it_just_tmrrow said:
Hope you have made a backup of the phone's TA partition prior to unlocking its bootloader. Anyway, once it is already unlocked, put it in fastboot mode (hold the volume up button whilst connecting it to the computer, util the led remains lit in blue color), either copy or move the TWRP image file (twrp.img from now on) to the directory where the fastboot tool is present, then enter the command (attention: it's case sensitive):
Can you tell me why you told to flash the twrp to FOTKernel and not to recovery?
At the moment I am on Android 5.1.1 (Kernel 3.10.49 , Build-Number 32.0.A.6.200). I followed this guide here to backup my TA-Partition and my bootloader is unlocked.
But when I came to the step to flash the boot.img and the twrp the E5823 does not start anymore.
Any idea?
Greetings by Idijt
Click to expand...
Click to collapse
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs

casouzaj said:
Which files, exactly, from which threads, have you flashed, to which respective partitions?
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
Code:
fastboot oem device-info
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
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.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with:
Code:
fastboot flash recovery the-name-of-the-twrp.img
With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot C:\Users\idijt\Downloads\twrp-3.0.2-0-E5823-20160417.img
downloading 'boot.img'...
OKAY [ 0.392s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.459s

I_did_it_just_tmrrow said:
THX for reply.
I do the steps:
-How To Backup TA Partiton
So I flashed the "E5823_32.0.A.6.200_R4B_Australia Generic_1298-7260.ftf" from here , from this thread.
-Backing Up TA Partiton
This step was a success . So I was able to run the script from the iovyroot_v0.4.zip , from this thread.
-Unlocking The Bootloader
I do this and I got the unlockcode from sony but when I run:
I got an error. He did not know this cmd. But when I do this, I got "Bootloader unlocked -> Yes"
*#*#7378423#*#* to access the service menu.
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.
-Rooting The Device
And this step my journey ends. I can flash a twrp, for example this one.
I do this with: With no errors. The howto from here told that I should flash the boot.img from here before flashng the twrp but when I do this I am not able to boot into anything else then the fastboot (vol+ and plugin the cable) anymore.I try the boot.img from Z5C_AndroPlusKernel_v31.zip and from Z5C_AndroPlusKernel_v43.zip but both giving me the same result as mentioned before.
Perhaps my problem is that I am still on 5.1.1. At the moment I try to find a compatible E5823 ftf-File to latest stock-rom (should be 7.0.1?)
Greetings by Idijt
EDIT:
The result when I just try to boot a twrp recovery:
Click to expand...
Click to collapse
In your computer, run Flashtool and click on the XF icon (the last one in the line of icons on the top part). XperiFirm will be downloaded and run. On it, under : Smartphone 2015'', click on 'Xpetia Z5 Compact' and on the specific model. Now clock on 'Check All'. Select a ROM bearing 'Customized' in its name and with version 32.4.A.1.54, which is Android 7.1.1). The list of available files appear on the right. Click on the most updated one and on 'Download'. Wait until the ROM is downloaded and unpacked. When the progress bar gets blank and says 'Downloaded successfully', click on 'Close'. Then, click on the X in the XperiFirm window to kill it. Flashtool will resume its work, which will culminate with the creation of the ftf file in the right directory.
To flash the ROM, click on the bolt icon, in Flashtool , select 'Flashmode', click on the little arrow at the left of the model name. The same for the specific model and for the ROM name. Finally, click on the ROM to be flashed. Mark all the boxes in the upper 'Wipe' section and click on 'Flash'. While it is preparing the files, turn the phone off. When an animated window requesting connection comes up, hold the phone's volume down button whilst connecting it to the computer. Release the button when the animated window goes away. Wait for the process to completely finish. Disconnect the phone from the computer
The ftf is located in C:/Users/your_username/.flashTool/firmwares. Copy it to anywhere you wish and change the copy's extension to zip.. Double click on it and extract 'kernel.sin'. In Flashtool, click on Tools > Sin Editor, and click on the tree dots on the right. Navigate to the location of the kernel.sin file, select it and click on 'Extract data'. File kernel.elf has been created.
Do you know rootkernel? (https://forum.xda-developers.com/xp...t-automatic-repack-stock-kernel-dm-t3301605). Copy the kernel.elf and the phone's TA.img to the rootkernel directory. In a terminal window in that directory, enter:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
The TWRP I use is this one: https://forum.xda-developres.com/z5-compact/general/twrp-twrp-3-3-0-z5-compact-t3929320, which I fastboot'ed to the FOTAKernel partition.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs

casouzaj said:
In your computer, ........
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as well.
This is getting too extense. As you progress, I will write other stuff.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
EDIT:
I flashed Magisk v19.3 and it wokred... Yes, as you told me :/
Can I simply flash Berni LineageOS now and did I need to flash the new-boot.img, the DRM-Fix_System_Mode.zip and Magisk always after flashing a new rom?

I_did_it_just_tmrrow said:
Wow, thx for this guide!
I came now to the point to start twrp. The only thing I did not was installing Magisk. Then I hit reboot to system. Sadly at the moment it just stuck in the first white Sony-Logo screen.
The only chance to came out of this is to press all buttons in the same time.
My target is to have twrp and Berni's LineageOS build.
Do you have some last tips for me, I fell very close
Click to expand...
Click to collapse
At any state the phone is in, in order to turn it off, hold both the power and the volume up buttons, until it vibrates thrice.
Then, enter TWRP by holding both the power and the volume down buttons. When the phone vibrates (as if it was being turned on), release the power button. When the screen lights up, release the volume down button. Then, under TWRP, install the new-boot.img, the Magusk-V19.3.zip and the DRM-Fix.zip.
Sent from my Xperia Z5 Compact using XDA Labs
---------- Post added at 05:39 PM ---------- Previous post was at 04:42 PM ----------
Regarding Berni's LineageOS builds, I'm running his 14.1 firmware. It has some issues. I don't go back to the stock ROM because I would have to wipe my data in the process, and, at the moment, it's not an option for me. The big advantage of the stock ROM is that you can have all your DRM keys active, although the bootloader is unlocked. The big disadvantage is to have outdated security updates. Berni's 15.1 build has more bugs than the 14.1 one,, and with his 16.0 build, the phone doesn't even boot up.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Sent from my Xperia Z5 Compact using XDA Labs

I too am trying to root my Z5 Compact E5823
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
flash_dk TA.img DK.ftf
Copy the DK.ftf file to .flashTool/firmwares directory. Flash it in flashmode, just like you did when you flashed the ROM.
Click to expand...
Click to collapse
should I still answer these this way?
Back to the terminal window, enter:
rootkernel kernel.elf new-boot.img
In the script which runs, answer yes to disable Sony RIC' and to DRM fix. Answer no to things like dm-verity, busybox and TWRP. Copy new-boot.img to the phone.
Click to expand...
Click to collapse
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
Click to expand...
Click to collapse
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
Click to expand...
Click to collapse
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
In TWRP (with the phone off, hold both power and vol-, remember?), click on 'Install' and on the flash img button. Select the new-boot.img file and the boot partition. Click on the flash zip button, select the Magisk v19.3 file and install it. Install
DRM-Fix_System_Mode.zip as wells
Click to expand...
Click to collapse
One last thing as you mentioned above
By the way, in my Z5C phone I use the stable Magisk 19.3 version, along with the MagiskHide Props Config, Busybox for Android NDK, and Systemless Hosts (this one is found in Magisk Manager settings) modules. This way my phone passes both Safetynet tests, and it shows as certified by Play Store.
Click to expand...
Click to collapse
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)

gnostisus said:
Could you help me clarify a few things, I followed another Z5 compact guide for MM and wasn't able to get SU installed without the bootloop I have my Z5 compact E5823 working after flashing 32.0.A.6.200_Australia_Generic firmware. I came across this thread and you gave such good instructions I thought I'd try Magisk which seems to be the standard now. I only got the Z5 compact to replace a broken Z3 compact, I needed a compact phone with ANT+ and the Z5 compact is the most advanced of the Sony's that offer it I never was able to get my Z3 rooted, I want to be able to rid the phone of bloatware I'm not sure the ANT+ works with Lineage so I'm stuck with Stock, at least if I get TWRP installed I can maybe experiment too.
As part of the guide I followed ( I can't post link because I joined just to ask for help, but it's titled "Sony Z5 Compact: Root without losing TA partition (DRM features) on Marshmallow") the part for the TA partition was as follows:
"Copy your TA partition backup to the rootkernel folder.
Open up a command prompt to the rootkernel folder and type in the following:
flash_dk TA-####.img restore-drm-keys.ftf
In Flashtool, click on the lightning bolt icon
Select flashmode
Select "DeviceKey" and click Flash
Hold "volume DOWN" and plug in USB cable.
Unplug and restart phone when instructed (read the activity log)"
do I have to repeat your instructions to:
should I still answer these this way?
I can't find the DRM-Fix_System_Mode.zip, is it necessary? Where on the phone do I copy it?
In the rootkernel thread there's an attachment called DRM-Fix_System_Mode.zip. Download it and copy it to the phone.
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
You mis-spelled the link but I found the thread. Are you using "20190514-TWRP-3.3.0-suzuran-recovery.img" or the newer one "20190517-TWRP-3.3.1-suzuran-recovery.img"
I do this with the code you have above?
fastboot flash FOTAKernel twrp.img
The TWRP I use is this one: which I fastboot'ed to the FOTAKernel partition.
is Magisk v19.3 still the one to use? When in TWRP can I install new-boot.img , and then Magisk v19.3, right after or do I need to reboot.
One last thing as you mentioned above
Are these all installed through Magisk Manager settings, or installed separately?
I hope all this isn't asking too much.
Thanks in advance for any help you can offer.
P.S. ( I am also getting the NFC firmware failed error when first booting after flashing firmware, I tried about 4 times different things, LL, MM, and Nougat. I was able to install Boot.img when SU wasn't in the rootkernel folder but the after booting to TWRP the bootloop happened.)
Click to expand...
Click to collapse
Magisk modules are installed by the Magisk Manager app. Tap on the menu button (the 3 bars at the top left) and select 'Download'. Tap on the search button and type in at least part of the module's name, and tap on 'Install'. The only module that is installed differently is the systemless hosts one. Tap on 'Menu > Settings > Systemless hosts'. After all the modules you wanted get installed, reboot your phone.
By the way, in my Z5C phone I'm currently running the latest stable Magisk v20.4. In its Menu > Settings part, I turn on the 'Magisk Hide' key.
Regarding flashing the Dk.ftf file, I do it whenever I flash a full ftf, because I guess the alternative partition it is flashed to gets overwritten.
Sent from my Sony E5823 using XDA Labs

Berni's LineageOS
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
casouzaj said:
]Regarding Berni's LineageOS builds, I'm running his 14.1 firmware.
By the way, the new-boot.img file doesn't fit any of the LineageOS builds. It's the kernel which holds the pointers to the DRM keys you flashed (DK.ftf). It is to the be used either with stock firmwares or ROMs based on it only. An indication is that the stock boot image is some 14+MB long, whereas LineageOS' boot images lenght is some 9MB only.
Click to expand...
Click to collapse
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.

gnostisus said:
I managed to get everything working and set up. Unfortunately I couldn't get the ANT+ working, it is disabled or buggy above LL, I tried the ANT+ Enabler app with no luck, the app claims to work on LineageOS so I want to give that a try but you wrote above
So would I be able to flash from TWRP In a similar manner and what files would I need, or do I have to flash the Berni's LineageOS firmware with flashtool and install a different TWRP build to install Magisk? Otherwise I'm stuck with stock 5.1.1 which I had tried to get rooted with no luck.
Thanks for the reply.
Click to expand...
Click to collapse
I've never used ANT+. I can't help you with that.
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP. .If you need the Google stuff, install a Gapps package, also from TWRP (I use to get the most updated mini one from opengappsI.com). Wipe all your data and caches. To get root access, install Magisk (the stable v20.4, I guess).
Good luck!
Sent from my Sony E5823 using XDA Labs

quick question about Berni's build
casouzaj said:
Berni's builds (like practicality all custom ROMs) are flashable zips. Install them from TWRP..
Click to expand...
Click to collapse
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
Wipe all your data and caches.
Click to expand...
Click to collapse
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again

gnostisus said:
All I have to do is put the Berni's build zip file on my phone and In TWRP click on 'Install' and on the flash img button. Select the zip file. There's nothing I need to do to prepare the phone first?
How do I do this?
I guess most important do I need to install the DRM-Fix_System_Mode.zip or anything else other than Magisk again?
Thanks again
Click to expand...
Click to collapse
You can either copy the zip files to your phone (or SD card), select the storage where the files are located and tap on ' Install', or keep them on your PC and, in TWRP tap on 'Advanced > add sidelioad', slide the bar, connect your phone to your PC, launch a command window, navigate to the folder where the files are located and enter:
add sideload filename.zip
Wait until the sideload process is finished (TWRP returns to the normal adb interface).
To clear your data, tap on the 'Wipe' softbutton and slide the bottom bar to factory reset.
Sent from my Sony E5823 using XDA Labs

Related

[Q] Best way to update to 23.1.A.1.28

Hi folks,
I'm looking for advice to update to 23.1.A.1.28 Lollipop, I would prefer to do a nice fresh install with the 23.1.A.1.28 UK unbranded FTF file. I updated from 4.4.2 to 4.4.4 using the PRFCreator flashable zip. I have unlocked bootloader & would prefer to keep everything stock including kernel.
1. Can I do a full wipe in the dual recovery including wiping the entire internal SD & then flash the flashable zip? Or will the full wipe including formatting the internal SD wipe the recovery?
2. Just flash the 23.1.A.1.28 UK unbranded FTF file using flashtool & check all the wipe options before the flash & then use King root (even though Bitdefender flags it as possible virus when it has never ever flagged any other root exploit before) to root device & then run the latest NuT dual revovery?
3. I only use a couple of xposed modules that as far as I can read are compatible with xposed-sdk21-arm-20150430.zip & the correct steps to install xposed for Lollipop are
I. Flash xposed-sdk21-arm-20150430.zip in recovery after rooting with King root.
II. Install XposedInstaller_3.0-alpha2.apk to manage modules
III. Install Play store fixes & youtube adaway modules in the xposed app. I would like to use Lollipop Navigation Bar module but don't think it is compatible as yet.
The reason I want to do a fully clean install is due to the fact I have found the phone to run a bit slower since updating from 4.4.2 to 4.4.4 with the PRF creator flashable zip. This mainly shows in the apps screen which shows the loading bars for about 5-6 seconds & then takes another 10-15 seconds to list the apps & app sizes etc.
Sorry for all the questions, my previous devices were all Samsung so I'm used to full wipe including internal SD & then installing custom Rom.
Cheers in advance for any help given.
If you have unlouck bt you can just flash stock in flash tool and flash recovery after that because this best way you didn't have a problem
Cheers for the reply copra11
How would I flash recovery after flashing the FTF file with Flashtool? Can I use flashtool to flash recovery or just use the installer version of NuT's dual recovery?
Would I need to be rooted first before installing NuT recovery?
Another question I have is I still got app updates through the sony update centre app on 4.4.2 with unlocked bootloader but when I updated to 4.4.4 I never got any app updates through update centre at all, had to get them from here or xperiablog. Would relocking the bootloader allow me to get app updates again?
Can anyone else offer some advice? Would like to get this done today\tonight if possible.
Cheers.
on unlocked bootloader :
- Flash ftf using flashtool, once done unplug device
- Get twrp from here : http://dl.twrp.me/sirius, download *.img file - rename file to recovery.img for later use
- go in folder C:\Flashtool\x10flasher_lib (assuming you installed flashtools in the default place), paste recovery.img in this folder (from previous step)
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash recovery recovery.img
you'll get a short message about the flash being successful, then you can disconnect your phone.
Reboot your phone, once the let light is on during the first Sony screen press the power button multiple times, then you can enter recovery.
This is for Unlocked Bootloader ONLY, I also recommend using @AndroPlus awesome kernel, which includes its own recovery, in this case you can simply flash the kernel and not mess with the recovery, to do this :
- download latest @AndroPlus kernel from here http://dl.androplus.org/Xperia Z2 D6502_D6503_D6543/
- open zip file and extract boot.img from it
- copy boot.img to C:\Flashtool\x10flasher_lib
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash boot boot.img
Hope this helps
Cheers for the reply ticktock666
Thanks for the guide you posted, I assume once recovery is installed I can then just flash SuperSU or just flash the flashable zip I created with PRF Creator? Would just flashing SuperSU root the phone?
Again many thanks for your help
@ticktock666
Followed your first set of steps.
- Flash ftf using flashtool, once done unplug device
- Get twrp from here : http://dl.twrp.me/sirius, download *.img file - rename file to recovery.img for later use
- go in folder C:\Flashtool\x10flasher_lib (assuming you installed flashtools in the default place), paste recovery.img in this folder (from previous step)
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash recovery recovery.img
you'll get a short message about the flash being successful, then you can disconnect your phone.
Reboot your phone, once the let light is on during the first Sony screen press the power button multiple times, then you can enter recovery.
Click to expand...
Click to collapse
When I power on the phone there is no LED light & despite spamming the power button it just boots up normally into the first run wizard. The fastboot flash recovery recovery.img command says it flashed it ok as shown in image.
Do you have a D6503 model ? my friend does and his unit does not show the purple led light when booting like my unlocked D6502 one does, no idea why.
Have you tried spamming the vol-up OR vol-down button on reboot ? try this first then go down the kernel road, do the kernel steps, this way you'll 100% get the recovery (I never flashed the recovery image alone before). Once you install the kernel you simply need to press vol-up and you get the recovery.
a couple of things :
when flashing xposed, flash the zip from recovery, wipe cache/dalvik, boot into system, install apk, then from the xposed app do a Soft-reboot, and immediately enter recovery and do a cache/dalvik wipe, then reboot. This is how I usually do it and it's been working for me since .690, so I though I'd share, also I've tried the 2 navigation bar modules from the xposed repo at some point and they both worked, also gravitybox offers many navigation bar mods among other things.
just flashing SuperSU zip from recovery is enough for root, no need for the prerooted zip, you'll just just be reflashing the rom you already have.
@ticktock666
Yeah mate it's a D6503 model, have tried the steps several times & the cmd window shows the recovery as being installed but no LED light when booting & the power & volume up & down buttons have no effect either. Ended up flashing the Andro kernel you recommended & the LED was purple when booting & spamming power button got me into recovery.
Even tried adb reboot recovery before I flashed the kernel but still nothing, also for some reason when going through the first run wizard it didn't restore my google backup when I entered google account details.
Starting again from scratch using your guide so fingers crossed
BTW do you know a good sound boosting mod, I was using Sound Mod v3.1 For Z2 Normal.zip on 4.4.4 from this thread or this thread
Will follow your steps for installing xposed framework & app, bit surprised that dalvik would need to be wiped as Lollipop uses ART runtime instead but will play it safe
Cheers again for all the help mate, really appreciate it
guess the led thing is kernel related, but I have unlocked the bootloader only 3 days after getting the device, and have been using a custom kernel ever since, so this might be the issue.
I just wiped my device, since I somehow managed to royally fudge it up after the 1.28 update (maybe because I dirty flashed 690, 726, 1.28 on top of each other )
I did excatly what I told you, and i'm now doing a backup before testing some stuff (deodexing app & priv-app, bloatware removal script).
I never use any sound mods, since I mostly listen to audiobooks, so there's not much bass involved , as for dalvik I'm sure the folder exists (under "/", which is the root directory of the device), maybe to use with older apps that are not optimized for ART ? not sure really but better safe than sorry.
Also I recommend entering recovery using vol-up since you have Andro's kernel, since this one is optimized for our device (extra backup options and stuff)
Yeah mate, after flashing the FTF file & then going into fastboot mode & flashing the kernel the LED is purple & pressing volume up gets me into recovery.
I thought I had bricked the phone as I tried to use flashtool in fastboot mode to try & flash the recovery but phone was stuck on the sony logo screen, after panicking for a few mins I used the tiny reset button where the sim card goes & it vibrated a few times, was then able to reflash the FTF & use the Andro kernel
I needed the sound mod on 4.4.4 as I found the ringtone & notification volumes too low & kept missing calls etc when out & phone was in pocket. The mod added back xloud feature that helped boost the volume a good bit. From what I have read here about sony lollipop one of the biggest failings was volumes.
Sure I read somewhere that Lollipop removed the dalvik runtime completely but better to be safe than sorry & wipe cache & dalvik with xposed.
BTW is it ok to use streicson busybox installer to get the latest busybox installed, I know when I uses NuT's dual recovery you couldn't install it as it broke recovery?
Cheers again for all your help with this mate, hopefully I can help you out in future
All the best
The reboot button combination for the Z2 is Vol-up+power button, keep holding them until phone vibrates 3 times, better than looking around for something to push the tiny reset button with
as for busybox, I usually flash a zip, but the busybox app by streicson does the same thing.
I'm off to sleep now, and hope everything works for you nicely with no more issues

[GUIDE] (C6833) (Maybe Others?) New Bootloader + Recovery

Installing the new Sony Bootloader and Recovery
THIS IS FOR ALREADY UNLOCKED DEVICES!
DO NOT TRY THIS ON A GPE!​Since a lot of people seem to have problems keeping their recovery when flashing Lollipop-ROMs i decided to put up this little guide...
You can also Skip this whole guide, by just flashing the newest stock-FW at least once!
First off, as already said, this is for already unlocked devices. You can use this Guide until "Install Custom ROM", except the rooting part, for rooting use this, if you haven't already!
Don't do it if you don't atleast somewhat know what you are doing.
I am not responsible for bricked devices, or whatever you might end up with.
So, lets get started.
1. Download Sonys FlashTool "EMMA" and install it: http://developer.sonymobile.com/downloads/tool/flash-tool-for-xperia-devices/
In the .zip file from the FlashTool you'll find a File "customization.ini"
Copy this file to the installation directory of EMMA, usually "C:\Program Files (x86)\Sony Mobile\Emma"
If you don't copy that file, Emma will ask you for a login, don't create an account there, you will NEVER get any activation-email!
2. Open EMMA and boot your Phone into FlashMode (Power off your device -> Press and hold volume DOWN -> while pressing volume DOWN insert USB-Cable)
3. Emma should now recognize your device, but you have to select it manually tough. Select your EXACT model number. Again, I am not responsible for any bricked devices or whatever you end up with!
Now select the "(Open Devices) TA update" and click "Apply Service"
It should take a few seconds and should then display SUCCESS.
You can now close Emma
4. If you haven't already download FastBoot and Drivers: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
(Run as Administrator!)
5. Download the newest version of twrp and put it somewhere:
New Inoffcial twrp-3.0.0 build by me: http://forum.xda-developers.com/xperia-z-ultra/development/togari-twrp-recovery-3-0-0-t3314440
Old official versions: https://twrp.me/devices/sonyxperiazultra.html
6. Finally boot up you Phone in FastBoot-mode (Power off -> press and hold volume UP -> while pressing wolume UP insert USB-Cable
Your LED should now light up blue
Shift+Rightklick in the Folder where you have put TWRP recovery, and select "Open Commandprompt here"
Now write "fastboot flash recovery FILENAME_OF_TWRP_FILE"
You can now unplug your USB-Cable and boot into recovery and continue from there.
Your recovery will be permanent, meaning you won't loose it or replace with any other recovery that might come with your ROM.
I hope this was somewhat helpfull
Any one can flash this to C6806?
jacklau2000 said:
Any one can flash this to C6806?
Click to expand...
Click to collapse
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
alia5 said:
You can try, just select your modelnumber in emma
If the "Open Devices (TA Update)" show up, you're fine. If not just don't do anything.
But do not try this on a GPE!
Click to expand...
Click to collapse
tried, but no luck. thanks.
It's really weird, I used emma, and installed their latest ta update. Now I can get into fastboot mode, all commands execute successfully, but the recovery never takes. The vol down + Power doesn't work, nor does 'adb reboot recovery'. Am I missing a step somewhere? This isn't my first android device, but from where I sit, it seems like something is up with my xzu.
If I try and install the 14.4* update through emma, it goes through the whole process, completes "successfully", then boots into 14.5. Something is clearly not working here.
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
teddy74eva said:
The TA update only unlocks the ability to boot to recovery, it doesn't install one. And no, flashing official TWRP to recovery partition doesn't work, it must be compiled again to work on normal recovery partition and not in FOTAKernel, where it must be flashed to work.
Regards
Click to expand...
Click to collapse
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Hermann1222 said:
I´m on CM 11 M12 (looking forward to 12) + the new sony bootloader without any custom Kernel stuff.
Sadly, you are right. It´s not done with downloading twrp-2.8.5.0-togari.img and fastboot flash recovery yourfile.img.
The last offical TWRP release for Xperia Z Ultra is from february 2015, any chance they release an updated version for the new Sony bootloader?
Click to expand...
Click to collapse
I will try to compile one because, you know, summer holidays and no school however I don't know if I will make it.
Regards
Is there any (wish for TWRP) recovery for togari, which use the new bootoader?
FYI:
My device is a brazilian c6843.
Emma recognizes the device automatically and indicates with an exclamation point that there is no services available to the unit.
In the case someone doesn't know, it's basically the c6833 with DTV 1seg. It's totally compatible with c6833 firmware, losing TV, of course.
You sir are the real hero! Thank you!
I have a xzu running cm12.1, and I have 2 quick questions for those with more knowledge than me
Is it possible to flash the new bootloder using the open source FlashTool?
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
pbgapski said:
If I have to use emma, is it possible to just apply the open device ta update *without* installing stock firmware first?
Click to expand...
Click to collapse
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
missing clues on new recovery partition
alia5 said:
You can totally do that, BUT, the newest stock firmware also has some firmware updates regarding nfc, also having the newest stock rom flashed at least once will be kind of a requirement to get everything properly working on marshmallow roms.
So I would say flash the newest stock rom at least once!
Click to expand...
Click to collapse
I followed your advice, but it seems I am missing a few clues.
My sirius was on cm12.1. I backedup and flashed D6543_23.4.A.1.232_1281-5466_R6C.ftf with flashtool on linux. I tried to use emma (several times) afterwards to check for any TA updates, but all I got was "no services matched this device" or something like that. Google tells me I am not the only one with this issue with emma
Then I used fastboot to install twrp 3 from twrp.me to recovery partition, but I could not access twrp.
I fastbooted recovery again with twrp 2.8.7, and this time I could enter twrp and reflashed CM.
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
pbgapski said:
Now I can access twrp using the button combinations while booting, but rebooting to recovery from CM leads to a bootloop. Has anyone experienced this as well?
So it seems I am still missing a few clues to using the recovery partition. Is any build of twrp supposed to work on both FOTAkernel and recovery partitions?
Is there a TWRP 3 build that works from 'coldboot to recovery' and 'cm reboot to recovery' with the new bootloader? Any pointers?
Click to expand...
Click to collapse
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
why it said my phone have no available service, i am on c6833
alia5 said:
Well, booting to recovery on separate partition from os, requires the rom to have a patch... the "new" mm-roms (when they finally hit aka. are ready to be shared in public) will have that, so no worry, just wait.
Click to expand...
Click to collapse
I have the same problem but not bootloop just stuck at starting apps screen,BTW did you have a TWRP scripts for flashing TWRP 3.0 into FOTAkernel
hi .. after this update can i relock my phone and restore drm functions?! or phone go to unlocked forever?!
pls help i need answer
erfanzz said:
pls help i need answer
Click to expand...
Click to collapse
Search the forums on how to backup TA partitions. I have mine but never tried to restore them

[GUIDE] Full root with Magisk and DRM fix [UNMAINTAINED]

Prefix: my xz1 died on me so I was forced to buy a new phone and therefore I won not be maintaining this thread any further. The guide should be relevant even without my help but I just won't be answering any questions regarding this thread or anything to do with the xz1.
YOU DO NEED TO UNLOCK YOUR BOOTLOADER AND THEREFORE WILL LOSE YOUR DRM KEYS!
NONE OF THIS IS MY ORIGINAL WORK BUT MY PROCESS IS ORIGINAL. YOU CAN THANK @modpunk FOR HIS PORT OF TWRP TO THE XZ1 AND YOU CAN THANK @janjan FOR HIS HARD WORK IN CREATING THE FIRST FULLY FUNCTIONAL KERNEL THAT SUPPORTS MAGISK AND STILL OFFERS A WORKING CAMERA AND SONY FEATURES
Here we go.....
1: Download modpunk's port of TWRP from this thread: https://forum.xda-developers.com/xperia-xz1/development/recovery-twrp-3-2-1-t3727602
Make sure to check the dates on the files and always download the latest version.
2: Download Janjan's kernel and DRM package here:
https://forum.xda-developers.com/xperia-xz1/development/kernel-sony-xz1-23-january-2018-t3739586
Make sure to check the dates on the files and always download the latest version.
3: Enable developer settings and enable ADB Debugging. I shouldn't have to say this part but something tells me if i don't then i'll get loads of questions about not being able to connect to the phone, lol.
4: Connect the phone to your pc and copy the 3 zip files contained in the janjan download to your phone. You don't need to copy the boot.img to your phone.
5: Open a cmd window on your pc and type the following:
adb reboot bootloader
6: Once the pc recognizes the phone in bootloader mode then type:
fastboot flash boot path/to/the/boot.img (I usually just type "fastboot flash boot " and then just drag and drop the boot image into the cmd window.
7: Once the boot image is flashed unplug the cable from the phone then reboot it. Once it's running then make sure the kernel info has changed to say "[email protected] #1
8: Once again, boot into bootloader by running the adb command
adb reboot bootloader
9: Once in the bootloader type into the cmd window:
fastboot flash recovery path/to/the/recovery.img
10: Reboot to system and then power off the phone.
11: Once it's off, boot into TWRP manually by holding the power button + the vol down button until the phone vibrates once, then let go and it'll boot into TWRP.
NOTE: It will ask you for your password to decrypt the data partition. This password is whatever your pin number or password you use on your phone lockscreen. If you don't use any lockscreen security then the password is: default_password.
12: Once in TWRP flash 2-Patching_drm_Su and 3-Magisk and then reboot to system and check that magisk is installed.
13: Finally open magisk and open the Modules section then tap the + icon and locate and flash the last zip 4-kernel_permissive and then reboot the phone and open magisk and check the modules section to ensure the Magisk SELinux Permissive Script is active.
Now you have a fully functional XZ1 with Magisk root and a properly functioning camera and Sony features.
Enjoy!
N1ghtr08d
Sorry.You forgot to flash SR5-SuperSU-v2.82-SR5-20171001224502.zip in TWRP recovery after step 13
Posting not relevant anymore!!!
1:st posting fixed by N1ghtr08d
Thanks bro. I had edited it and I must have missed putting that back in. Fixing it now
Any try to use Magisk instead of SuperSU ? I need to use some apps witch don't work with root phone.
If you turn the phone off, press and hold 'Volume Up' and attach a USB Cable from your PC it will boot into the bootloader. The LED will be blue then ...
Thanks modpunk, that is very true. I guess my preference is just to use ADB.
As far as magisk is concerned, I believe that none of the magisk releases work with this device. I would prefer to use magisk also so if anyone figures out how to install it successfully without putting the phone in a bootloop, please share it here and I will update this guide. I'd rather have SuperSU than no root at all.
Does anybody have any tips for installing Viper4android? I renamed the audioeffects file in System/Vendor/Etc and installed the Nougat test io fix version and when I opened the app and allowed it to update the drivers, everything went well and looked successful, however upon reboot and opening the app to set it up, it just tells me to update the drivers and reboot again and even doing that just lands me back at the same point.
Does anybody know how I can get it installed and running properly?
Coincidentally V4A installs and runs perfectly now that it can be installed through Magisk Manager!
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
trevorftard said:
What FOTA kernel.img are you referring to? There wasn't one linked in the post, and Sony's fotakernel files are in .sin formats. Flashing just the boot.img linked in your post results in a brick. Flashing the fotakernel_X-FLASH-ALL-C93B.sin included in Sony's firmware also results in a brick. Has anyone got this to work?
Click to expand...
Click to collapse
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
pergoteborg said:
Flash boot.img to both boot partition and FOTAKerner partition
fastboot flash boot boot.img
fastboot flash FOTAKernel boot.img
Click to expand...
Click to collapse
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
trevorftard said:
What FOTAKernel boot.img though? Am I supposed to download one from somewhere? It's not in OP or in the Sony firmware that I've downloaded.
Click to expand...
Click to collapse
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Thank you for the help Pergoteborg. I thought the guide was fairly self explanatory.
I pointed out in the op that the one boot image I provided in the download is to be flashed to 2 different partitions.
If you follow my instructions as provided you will have success. It's really easy to follow along if you read it properly.
pergoteborg said:
Can I use the aledoom's port of the Andro+ kernel at https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U for the new 47.1.A.8.49 release?
Click to expand...
Click to collapse
I tested myself and answer is NO. Therefor no magisk for 47.1.A.8.49 yet since we do not have kernel support. Root achieved by SuperSU
So I :
Got phone in flash mode (Vol- when putting in computer USB cable, Green light). Ran NewFlasher with 47.1.A.8.49
Booted phone, turned it of and set it to fastboot mode (Vol+ when putting in computer USB cable, Blue light)
Flashed TWRP: fastboot flash recovery twrp-3.2.1-0-poplar-patchlevel-2017-11-05.img
Booted phone, Uninstalled Magisk manager, Installed SuperSU App from Google Play.
Turned off phone, booted into TWRP (Vol- and pwr, release pwr button when phone vibrates, hold on the Vol- button)
Installed Magisk-uninstaller-20171123.zip to get rid of Magisk. Installed SR5-SuperSU-v2.82-SR5-20171001224502.zip to get SU
HIPP!!!
pergoteborg said:
The link https://mega.nz/#!00l3mABT!RCuCfvwxROggim9D_GwfdhZDTPQJomNrfWZy_lsq0-U is the download link for boot.img
fastboot flash FOTAKernel boot.img
The parameters is:
fastboot - An Android SDK command and library used to communicate with a connected android device
flash - The fastboot command you wish to execute. "fastboot flash" takes two parameters, which are:
FOTAKernel - The partition on the connected phone you want to flash and
boot.img - The file you want to flash into FOTAKernel partition.
In this case is the same file (boot.img) flashed into BOTH boot partition(fastboot flash boot boot.img) and into FOTAKernel partition(fastboot flash FOTAKernel boot.img)
Click to expand...
Click to collapse
Thanks for being actually helpful. I wasn't familiar with the FOTAKernel partition. I though it was a typo that was supposed to be the name of some boot.img. I'm familiar with everything else about fastboot. I'm still getting a glitchy display after flashing the boot.img to the boot and FOTAKernel partitions. I think I'll just check out and give up on this one.
Hi There
Thank's to my hero aledoom who ported XZ1 (G8342) FW47.1.A.8.49 to Androplus we can now enjou latest FW and Magisk
Download the patched kernel here (aledoom´s direct link here)
If you currently have root with SU, get rid of it by flasching UPDATE-unSU-signed.zip in TWRP
Then follow the OP, but use kernel from here instead of OP boot.img.
I currently testing MAGISK 15.0 and it's working fine except there is no modules ported to the new template just yet,
Hi all, do you think that TWRP, Androplus kernel et Magisk work on a XZ1 Dual ?
I don't know. To be honest, you'd need to check with modpunk and aledoom if their recovery and kernel are compatible
So this is actually my first official post as a new member on this site but have been a long time user of the guides here. I have a question but I want to root my xz1 to optimize the performance and what not and just cause haha. My question is about what's being lost. I noticed something called xreality or something won't be accessible. What is this? Reason I'm asking is that I playmobile legends and this phone and only this phone I've found has an in game option for. "high frame rate" mode.. I'm not interested in rooting it if all I'll do is make it perform less rather then the opisite anywho Sony's alot different then most android im finding so I figure what the hell better make an account finally and ask.
I have no idea what xreality is. Is it a Sony app?
As far as what's lost, you lose the DRM keys so the camera stops working correctly, as in when you take a photo it just turns out as a green image instead of the picture you intended.
Now with that being said, someone over on the root bounty thread apparently discovered a fix for this that allows the camera to function fully as before. I have tried flashing this fix on my personal device and it didn't work as expected however I'm using magisk for root instead of SuperSU like the poster stated so I'm waiting on a reply from him regarding the usage of magisk Vs SuperSU with his fix.
Here's the thread in question. He posted right at the end of the thread just before me.
https://forum.xda-developers.com/xp...z1-compact-lb-root-drm-backup-t3672176/page16

[GUIDE] [EMUI 9] Magisk Root Honor view 10 BKL-09 for Android PIE

Requirements / Downloads
Honor 10 view BKL-09 with unlocked bootloader (I not tested in other version)
Minimal ADB & Fastboot
Patched Recovery_Ramdisk BKL
Rooting your device
1. Unzip Minimal ADB & Fastboot to any folder of your PC
2. Download the patched file for your device and copy it to Minimal ADB & Fastboot folder.
3. Start your smartphone in fastboot mode pressing [Vol-]+[Power] and connect it to your PC.
4. Open a Powershell window in your Minimal ADB & Fastboot folder by [Shift]+[Rightclick].
5. Flash the Recovery_Ramdisk:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
Adjusting Magisk Manager and patching files by yourself
1. Download Magisk Manager canary build to your phone and install.
2. Change in Magisk settings the update channel to "custom" inserting this URL. https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
3. Check "force encryption" and "AVB 2.0" boxes.
To patch yourself recovery_ramdisk:
4.a) Patch your *.img, that you have copied in any folder to your smartphone by pressing "Install" --> "Install" --> "Patch boot image" in Magisk Manager.
ORIGINAL RECOVERY_RAMDISK BKL-09 PIE version 9.0.0.162 C432
5. Transfer the patched file (You will find it in your download folder of your smartphone. It will be called "patched_boot.img".) to your PC, start Smartphone in fastboot mode and flash:
Code:
fastboot flash recovery_ramdisk name_of_your_patched_file.img
(You must adapt the file name to the real name of your file, e.g. patched_boot.img)
To actualize Magisk:
4.b) Choose in Magisk Manager: "Install" --> "Install" --> "Direct Install (Recommended)" --> Restart
Thanks
Thanks a lot for this great guide!
Hello, will this also be on my bkl-l09c432? I have rom
blazios said:
Hello, will this also be on my bkl-l09c432? I have rom
Click to expand...
Click to collapse
If your device is on pie ?, yes
What should I use twrp?
blazios said:
What should I use twrp?
Click to expand...
Click to collapse
OP never mentioned anything about twrp. That is not needed
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
BlueMan_86 said:
I Have same version as you Android Pie and everythin firmware and region... But no matter how i try i get UNABLE TO UNPACK BOOT IMAGE... Instalation failed... why is that? i have TWRP installed... and everything as is your phone firmware and version 9.0.0.162 C432...
Click to expand...
Click to collapse
Flash in bootloader mode. Not in twrp.
Android pie not work with twrp for now.
I am on ROOTED EMUI 8.0 (BKL-L09 8.0.0.130). How do I update to pie and then root? First unroot than update than root? or just update and root with the instructions in post#1?
Sadly it does not work for me. Tried it with your patches bootimage and with my own. Flashing the ramdisk works fine but after restart I don't have root.
I dont need Magisk installed if I use the pre patches bootimage right? Nevertheless I tried with Magisk installed and without. In the Huawei Mate Forum I read that one might need to shutdown the phone after flashing and then to start it with Volume Up and Power Button pressed. But this also does not work. Or any Idea how exactly to start with this Key combination?
Any other suggestions?
Today I updated from OREO with root to PIE same version as you have in pictures 9.0.0.162(C432E4R1P9). Tried both steps (with your patched file and me patching file) to root my phone but even I always got OK in fastboot mode I still have no root
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
I get the same error
any advise ?
Worked like a breeze for me. Shoutout to @ante0 and @shashank1320 who kept their calm in guiding me through and suggesting me this method.
@ante0 made things easier for me and it worked excellently for me. The steps are-
Download and install Magisk canary builds from the mentioned link. Change in Magisk settings the update channel to "custom" inserting*this*URL.*https://t2m.io/wuAFCrwO
Magisk Manager now will find the canary builds.
Check "force encryption" and "AVB 2.0" boxes.
Transfer stock recovery ramdisk to phone, open Magisk Mnager and hit install - > patch boot image, select recovery_ramdisk.img. Take patched_boot.img from /sdcard/Download/ and transfer to computer, reboot to fastboot and flash patched_boot.img to recovery_ramdisk. Unplug USB, holv vol up + power to reboot to recovery, which will now boot phone with Magisk. If you reboot and don't hold vol up it will boot to system without root.
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Huge thanks @fabio84
Finally have root privileges on Pie.
resdano said:
Hello,
Sadly applying the guide does't not work for me to. I tried with the given patched bootimage and with my own one. When flashing the ramdisk image in fastboot mode, i got this error :
"FAILED (remote: partition length get error)".
Please help!
Click to expand...
Click to collapse
davidsiv said:
I get the same error
any advise ?
Click to expand...
Click to collapse
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Not flash ramdisk. Need flash recovery_ramdisk!
worked, thanks
fabio84 said:
Not flash ramdisk. Need flash recovery_ramdisk!
Click to expand...
Click to collapse
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
ankan1993 said:
@ante0 has been helping me get root access and we still are working on it.
@fabio84 did you by a chance experience issues in using root applications especially root explorer or root Uninstaller? For some reason they won't just work for me, just titanium and root checker works. On further scrutinising, I found the su binary files missing probably why the applications won't load for me. Any help?
Click to expand...
Click to collapse
Update: @ante0 helped me yet again to figure it out. Apparently was because of pie's aggressive background restrictions. Root is now working full fledgedly. Thanks everyone. Big cheers to @ante0
Hello,
It finally worked for me. Thank you so much!
ante0 said:
Emui9 doesn't have a ramdisk partition. You flash to recovery_ramdisk, then when you reboot hold volume up to get to recovery (unplug USB as it will take you to erecovery if you have it plugged in).
This is the only way to get root on Emui9, currently.
It will not boot to recovery, it will boot to system with Magisk.
Click to expand...
Click to collapse

How to root with Magisk Lenovo M7 (TB-7305F) / Android 9

Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to

Categories

Resources