Bootloader unlockable - Sony Xperia 10 II Guides, News, & Discussion

Bootloader unlockable - Sony Xperia 10 II Guides, News, & Discussion

Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/

I've done it but i'm facing a problem with rooting could you help me with that ?

hq8aus said:
I've done it but i'm facing a problem with rooting could you help me with that ?
Click to expand...
Click to collapse
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.

serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?

hq8aus said:
Thank you for the tutorial i will try it after few hour
I have one question : my phone refuse to enter recovery mode once the recovery mode boot the phone restart and start normally so i'm surprised do u know if this a common problem?
Click to expand...
Click to collapse
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).

serajr said:
You're welcome. Xperia devices are not provided with a recovery, you need a custom one (by the way not yet available for this model).
Click to expand...
Click to collapse
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"

hq8aus said:
Thank you very much the method u wrote worked
now i'm free to install mods ? " i know it's stupid question but i'm beginner in rooting"
Click to expand...
Click to collapse
Glad to know that.
Sure you are! You can flash EdExposed and, for e.g., install my xposed modules ( Home Xposed for Q and Call Recording ).
Also any other hack you want to (my debloat script >> here << may also work).
Just a warning: due the lack of a recovery, if you face a bootloop after mess with something, you'll need to disable all the installed magisk modules to be able to boot up device, and to do so, you'll need to create a Core Mode Only magisk (google it) and fastboot it.

sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it

hq8aus said:
sorry to bother you .. but is there anyway to mount the "/system" to r/w ? because i'm having problem in moving file into it
Click to expand...
Click to collapse
First of all ensure all your installed magisk modules are disabled (disable them all and reboot).
Magisk bind-mounts /system/* (specific modules folders) to do its initial mount logic, so changes into those system folders at runtime won't be allowed (if that specific system folder is used by a magisk module).
I don't know if this is your case, but I drop here this warning.
adb commands to mount system (rootfs)
rw:
Code:
mount -orw,remount /
ro:
Code:
mount -oro,remount /
You could try also to disable the vbmeta params by fastbooting vbmeta*_.img (vbmeta_*.sin > unsin.exe > vbmeta*_.img) with command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta*_.img

hi everyone,
after rooting with the boot.img patch method is there a good way to de-google the stock rom? i've seen twrp scripts for this but obviously those don't apply here, and i'm not exactly sure what is safe to remove and what is not, as a few days ago when i did this (via the /d/gapps app from f-droid) the system got stuck in a bootloop.
any ideas?

Ber7az said:
Sony's bootloader unlock page added the xperia 10 II to the list.
It's wrongly listed as "Xperia X10 II", so it's near the middle of the list, but gives the code with the IMEI
Edit:
Can't post link yet, the unlock page is: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Click to expand...
Click to collapse
Hi, is it possible to relock the bootloader?

Supercharlie25 said:
Hi, is it possible to relock the bootloader?
Click to expand...
Click to collapse
You could try and confirm. Xperia 1 and Xperia 5 are lockable but is not the Xperia 10, maybe the Xperia 10 II could be lockable, try on your own risk

serajr said:
As long as BL is unlocked, you may be able to root your device using XperiFirm, UnSIN and Magisk.
- XperiFirm > Download fw
- UnSIN > Get the boot_XXXX.sin file from the downloaded fw folder, and drop it over unsin.exe (you'll get boot_XXXX.img file).
- Move the boot_XXXX.img file to the device's internal storage (or sdcard).
- Install Magisk Manager app
- Magisk Manager app > Install > Uncheck 'Keep AVB 2.0/dm-verity' > Next > Select and patch a file > Choose the boot_XXXX.img (you'll get /Download/magisk_patched.img)
- Flash magisk_patched.img with fastboot with command:
Code:
fastboot flash boot magisk_patched.img
- Reboot
If something goes wrong, you'll need to flash original stock boot img file (boot_XXXX.img) with fastboot (or even flash whole fw again).
Try it at your own risk.
Click to expand...
Click to collapse
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.

Thapsus-cz said:
Hi, is possible flash custom Rom without recovery? I saw that it is already available for download Pixel Experience for our device. Thanks for replay.
Click to expand...
Click to collapse
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).

serajr said:
I have no idea (I've never played with custom roms - stock only).
Pay attention to the 2020/08/19 build, it has a recovery image file available (as per I could see).
Click to expand...
Click to collapse
Thank you, I'd rather wait, maybe we'll see TWRP soon.

Has anyone installed LineageOS on this?

xdauserart said:
Has anyone installed LineageOS on this?
Click to expand...
Click to collapse
The only custom ROM for our device I found Pixel Experience here https://download.pixelexperience.org/xqau52 But unfortunately I failed to flash the their recovery and twrp is not yet.

Thapsus-cz said:
The only custom ROM for our device I found Pixel Experience here ... But unfortunately I failed to flash the their recovery and twrp is not yet.
Click to expand...
Click to collapse
That doesn't sound great. I'm looking for ways to de-google it, remove tracking apps, etc. Looks like now only way is to remove apps manually via `adb`. But I'm not sure what apps to remove.

Will installing AOSP for Android 11 with Sony image be without Google apps (like Google Play and other bloat)? Did anyone try installing this? Sony has added Xperia 10 II to Open devices program recently.

@xdauserart, @Thapsus-cz, Do you know if after Unlock BL of xperia 10 II, boots with the message "Your device can't be checked by corruption. Please lock the bootloader '? And if its available some method to backup TA before, for this model? Thanks......

Related

[stock 8.0][Unlocked bl][34.4.A.2.19; ...32; ...85] Root and Recovery (3 clicks)

Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)

I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...

Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.

levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?

maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.

Op updated for 3-click root...

SuperSU,Xposed

Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.

Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...

Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).

I was able :laugh::good: Xposed release link

levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.

Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks

Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed

I created boot.img and everything works Thanks a lot!

I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...

Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793

hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!

I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).

Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...

Android Pie Treble Project DP3 DP4 DP5 PR1 Guide

Android "P" is the upcoming ninth major version of the Android operating system. It was first announced by Google on March 7, 2018, and the first developer preview was released on the same day. The second developer preview is expected to be released at the next Google I/O developer conference.
Requirements :
Qcom fully treblized device with 8.1 vendor
Global Bugs :
VoLTE
Device specific Bugs :
Mi5 = Reboot Loop into TWRP (Fixed by restore files)
ANDROID P DP3
installation :
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot
When flashing POST-sGSI untill incall shown error in twrp, Go back to TWRP Home > Mount > check vendor and system
After bootup, you need to install Google Play services 12.8.72 (100400-202717283) HERE
If you are facing with bug Reboot Loop(always reboot into TWRP) you need to restore this backup file from me.
Unzip and put that folder at TWRP/Backups
Goto TWRP > Restore > Check system and vendor only > Reboot.
SECOND METHOD : Restore before 1st boot.
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP3-sGSI.img HERE
- Flash POST-sGSI_1_v0.9.zip HERE
- Flash POST-sGSI_2_v0.12.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2101MB).
- Flash P-lag-fix.zip file below thread
- Flash incall2.zip HERE
- Reboot (If stuck at google logo about 3-5mins, try to force shutdown your phone, and turn it on again... it should be work.)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
ANDROID P DP4
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP4-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.11.zip HERE
- Flash POST-sGSI_2_v0.14.zip HERE
- Flash POST-sGSI_3.zip HERE
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash p-lag-fix DP4.zip file below thread
- Reboot
If your device become reboot loop into TWRP, like in DP3
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
Click to expand...
Click to collapse
ANDROID P DP5
CLEAN FLASH IS HIGHLY RECOMMEND
- Flash [JDCTeam][TREBLE][v4][Gemini] The Full Treble support project HERE
- Unzip and Flash P-DP5-sGSI-Aonly.zip HERE
- Flash POST-sGSI_1_v0.13.zip HERE
- Flash POST-sGSI_2_v0.16.zip HERE
- Flash POST-sGSI_3 v0.2.zip HERE
- Flash lag-fix-DP5 attached below.
- Mount Vendor on TWRP
- Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
- Reboot to System
IF YOU STILL REBOOT INTO RECOVERY AFTER 1ST BOOT.
after flash POST-sGSI_3 v0.2.zip
- Restore this backup file
(Make sure choose System and Vendor only, Dont choose boot, system image, or vendor image and the size is 2180MB).
- Incall.zip already included. Dont need to flash it.
- Flash lag-fix-DP5 attached below.
- Reboot
Click to expand...
Click to collapse
Android P Public Release 1 (PR1)
1. Flash JDCTeam Full Treble Support Project
2. UNZIP and flash Pie A-only as System Image.
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1_v0.14.zip
5. Flash POST-sGSI_2_v0.17.zip
6. Flash POST-sGSI_3_v0.2.zip
7. Mount System and Vendor on TWRP
8. Flash p-lag-fix.zip (Attached Below)
9. Mount Vendor on TWRP
10. Go to TWRP Advanced - Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
11. Reboot to System
12. Install Google Play Services Apk, reboot and proceed normally.
Click to expand...
Click to collapse
REBOOT LOOP THIRD METHOD by mlira1 and Maixf
1. Flash JDCTeam Full Treble Support Project
2. Flashi DP3/DP4 System Image
3. Mount System and Vendor on TWRP
4. Flash POST-sGSI_1
5. Flash POST-sGSI_2
6. Flash POST-sGSI_3 (skip if going to flash custom kernel)
7. (only if going to flash custom kernel) Flash fix.zip (attached below)
8. (optional) Flash custom kernel
9. (optional) Flash Magisk
10. Mount System and Vendor on TWRP
11. (only if flashed custom kernel) Flash POST-sGSI_3
12. Flash p-lag-fix DP3/4/5.zip
13. Mount Vendor on TWRP
14. Go to TWRP Advanced->Terminal, type the following and press enter
echo persist.sys.disable_rescue=true >> /vendor/build.prop
15. Reboot to System
16. Install Google Play Services Apk, reboot and proceed normally
Click to expand...
Click to collapse
TIPS
Mi5 'Fingerprint Always On' On Android P (Unlock when screen off, and without press any button. Just touch it FP)
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Fingerprint as Home by rmrbpt
- Root your Mi5 with 16.4/16.6 Treble version
- Install Karnel Auditor
- Go to Tab, Select Custom Control
- Press "+", and import this .json file
- Press 3 dots at there, check 'on boot'
- Reboot
Click to expand...
Click to collapse
Mi5 Double Tap to Wakeup Android P
- Root your mi5 with 16.4/16.6 Treble version
- Open Karnel Auditor
- Go to Tab
- Find 'Wake'
- Turn it on, and apply on boot
- Reboot
Click to expand...
Click to collapse
Disable backlight button
Flash Disable Backlight.zip from Magisk !
Attached below.
Click to expand...
Click to collapse
Fix Battery Drain Issue
Still working on it
Alternative for it
- Dissable Dev Mode in Setting
or
- Try custom karnel
Click to expand...
Click to collapse
Get Blue accent / Pixel theme
Add this to your /vendor/build.prop, save and reboot:
Code:
ro.boot.vendor.overlay.theme=com.google.android.theme.pixel
Click to expand...
Click to collapse
MTP Not Detected
- Goto Setting
- System > Advanced > Dev Options > Choose File Transfer at USB Default Configuration
Click to expand...
Click to collapse
How to flash custom kernel on P GSI
FLASHING CUSTOM KARNEL CAUSING YOU CANNOT ENABLE MTP FORVER AND CHARGING FROM PC/LAPTOP
- Follow instruction from flashing JDC untill POST GSI 2, dont flash POST GSI 3.
- Flash Custom Karnel
- Reboot
- Clean Flash is the only way to fix it for now
Click to expand...
Click to collapse
Fix/Solution Arnova/BSG/other dev Gcam lag when changging between front and back camera on P
- Flash Camera Switch Lag Fix.zip, attached below.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Terribly sorry but at what point did you make that "backup file"? I couldn't fix bootloop without your backup. Just wondering, since it's so large and probably mi5-only maybe you could just give us instructions how to make a working system without using someone else's backup?

After restore, have been stuck in G logo for 25 minutes, just followed the instruction

mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
Try select system only. goodluck.

mansonstein said:
After restore, have been stuck in G logo for 25 minutes, just followed the instruction
Click to expand...
Click to collapse
dont choose system image and vendor image.
but system and vendor only

bukandenny said:
dont choose system image and vendor image.
but system and vendor only
Click to expand...
Click to collapse
Yes, exactly, and I tried just system and just vendor, all stucked in G logo. Someway else to try? What causes reboot loop? Thx

If anyone successed, please let me know how you did it.

mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
3 times i used that way, and always work.
asking someone to do that, its work.

mansonstein said:
If anyone successed, please let me know how you did it.
Click to expand...
Click to collapse
try second methode above.

https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.

Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
Click to expand...
Click to collapse
Start from beginning.
you need to FORMAT DATA (not wipe data)
then start from beginning dude.

Santosh Kolur said:
https://drive.google.com/open?id=1VryExVHI-14NfgIcBPp2dFiN-rzhOeNO
I've tried both the methods , but I always end up at this error, please help.
It asks for password and then just reboots into recovery.
There's also a pop up stating "There's internal problem, please contact manufacturer for details"
The above link has the images of the issue.
It would be really helpful if someone can help me boot this rom up. Thank you.
Click to expand...
Click to collapse
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png

bukandenny said:
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
Click to expand...
Click to collapse
Thank you. I got it to boot using your solution.

Santosh Kolur said:
Thank you. I got it to boot using your solution.
Click to expand...
Click to collapse
Decrypting internal storage fixes reboots?

Yes it did for me.

First method did it for me, too. I had the bootloop after first reboot and it did the trick, everything is working fine, a bit laggy, but Android P is running smooth on my phone!! I think that's very importat that after first boot you install Play Services as stated in OP and let Google finish its whole Pixel Configuration and updates, then you can try and reboot the phone, if you're hit by the bug, just follow what's in OP.
Few things if you install the GSI and have these issues:
- for Magisk, install version 16.4, just install that after you have set up the phone and stuff, you reboot to twrp and flash it, that's the way it works for me;
- if you have missing network on SIM, just go and configure your apn manually, it'll do the trick;
- for MTP, it's not working for me out of the box, the trick is to enable developers options, go to "Default USB Configuration" or something similar (I have it on italian, so I think that's how it's in English) and select the first one option;
Edit: also there's fingerprint that cannot wake the device, I've read in Telegram groups that some fixes are around for fingerprint, I'll check it out later and report if I find something interesting.

I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI

g33k0 b3lk0w said:
I've suceeded but my FP isn't working, already sent the logcat to the main xda page of GSI
Click to expand...
Click to collapse
Cool! So I think there's no solution to this issue at the moment?

aittamattia said:
Cool! So I think there's no solution to this issue at the moment?
Click to expand...
Click to collapse
wait ill upload, u can see my chat on group

[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

Help me root Z5C.

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

Root k20/mi9t without twrp

this guide help you to root k20/mi9t by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader( its one time requirement)
.magisk patched boot img
patched boot img is created using stock boot img that is different for every miui version,so create your own patched boot img according to your miui version by this easy process https://forum.xda-developers.com/mi...dian-rom-v10-3-6-0-twrp-t3958566/post80163818
just to be on safe side remove all types of lock, u can use lock after all steps completed
NOW FOLLOW THE STEPS
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the blank space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: fastboot devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [step 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE

Is bootloader unlock is required because you didn't mentioned that....

if u debloat xioami apps in miui roms & do some customization with magisk module .its become quite useful rom for a while now until stable custom rom available for use

RSM10 said:
Is bootloader unlock is required because you didn't mentioned that....
Click to expand...
Click to collapse
yes bootloder unlocked is required this is basic
u can do very little customisation like debloating with locked bootloader

Thanks I knew that bl unlock is required but since you didn't mentioned it here I thought you found a way out without unlocking bl. This patched boot.img is for 10.3.6.0 What if there is new update, then we will lost root.

i will try to provide patched boot img for future updates

rkview37 said:
this guide help you to root k20 by using magisk patched boot img
this guide is for users who likes to be on stock with magisks modules customisation
advantage
[no data loss in whole process]
[safety passes okk]
[install modules like dolby,viper4android after root to improve sound quality]
REQUIREMENTS
.unlocked bootloader
.magisk patched boot img (download from link below)
.must be on miui v10.3.6.0
just to be on safe side remove all types of lock, u can use lock after all steps completed
download magisk patched boot img provided by me
https://mega.nz/#!CpUz3KwB!76fE3z30gngG282mA9DzS05AZyjG6RuQFs5-STg2kXE
now follow steps carefully
install latest magisk manager apk
place the downloaded magisk patched boot img to adb folder or platform tool folder whatever u call in pc
1.boot your phone into fastboot by holding power menu &volume down button togethor
2.connect your phone to pc using original cable
3.Go to adb folder & open command window by clicking shift+control+right key on the black space (command window appear in option)
4.now check your devices by if its properly connected by typing
code: adb devices
if it shows attached devices then proceed
5.now flash patched img by typing command
code: fastboot flash boot magisk_patched.img
finally boot your phone to system by typing command
code: fastboot reboot
6.now open magisk manager it show some recommendation just reject that option(important steps)
7.click on install in magisk manager then select direct install recommended option
let it install &reboot [steps 7 is neccessary otherwise you cant install module in magisk)
this is 100% tested method
need any help or confused comment down below before attempting this
hit THANKS BUTTON IF U LIKE
Click to expand...
Click to collapse
Thank you keep updating as and when stock updates are received.
Sent from my [device_name] using XDA-Developers Legacy app

If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?

manan001 said:
If we receive ota update. How should we install? Will magisk stay?
Sent from my [device_name] using XDA-Developers Legacy app
Can i do magisk update regularly?
Click to expand...
Click to collapse
1)as we all know k20 is single partition device.so we cannot perform ota whiile preserving magisk,i will update op with all info once i figured out a way to save effort of installing all modules all over again
2)magisk can be updated regularly,no issues at all

Finally installed magisk. Thanks for the detail steps. It works well.
Sent from my [device_name] using XDA-Developers Legacy app

10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Sent from my [device_name] using XDA-Developers Legacy app

manan001 said:
10.3.8 OTA update available.
Patched boot.
https://drive.google.com/folderview?id=1-3QhAjIH5JmrlZaYgsCjr92XjcUv90nN
Click to expand...
Click to collapse
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet

manan001 said:
10.3.8 OTA update available.
Patched boot.
Do you have the stock recovery.img ?
How to update via OTA when i am on twrp ?
Can you confirm if root working after flashing your patched boot image ?
Click to expand...
Click to collapse

rkview37 said:
from where did you extracted stock boot img
afaik latest 10.3.8.0 stock rom not available on any site yet
Click to expand...
Click to collapse
In phone update we get option to download full rom ota. I downloaded and extracted boot.img, rest you know the process.
If you like my work do hit like button.

Dear Rkview31
If the flash install of the patched image fails, can we reinstall de rom with miflash? Or, is enough to reflash by fastboot command line the original fastboot rom image?

Can any one provide stock recovery (10.3.6) please.

neek619 said:
Can any one provide stock recovery (10.3.6) please.
Click to expand...
Click to collapse
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0

Guys
This procedure wokrs with eea device?

mauriciocardoso said:
Guys
This procedure wokrs with eea device?
Click to expand...
Click to collapse
guide is okk but stock boot img of every rom is different so patched boot img in this thread will not work for u

rkview37 said:
go here
download from my mega account
https://mega.nz/#!Ok8yBYaB!N9CnTLSfpvoakHiQGDyyIxDvEL0MUmUsxAQqj3nhSu0
Click to expand...
Click to collapse
Thanks for the file, was able to update to 10.3.8
Patched boot image by @manan001 in the link above do not work and reboots phone in recovery mode.
Patched my own boot image works fine with 10.3.8
https://drive.google.com/file/d/1-odNizuv4HlEw92O8tl_X13aQxdFwbGe/view?usp=drivesdk

Better Mobile App

welcome