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...
Related
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
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
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
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......