Related
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
THANKS!!!
Little shook that no one has replied to this awesome work! Thanks Man I have been waiting! Sent a thanks
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
Click to expand...
Click to collapse
For f3212
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
I don´t understand quite well (sorry for my ignorance, i´m new to this stuff), so i flash supersu from twrp ¨just after flashed new boot¨ to avoid boot loop.....does that mean flash supersu after flashed twrp right away? how do i avoid bootloop? my build number is 36.0.A.1.100, should i worry about it?
my model is f3213
Thanks a lot
Jazinto93 said:
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
I don´t understand quite well (sorry for my ignorance, i´m new to this stuff), so i flash supersu from twrp ¨just after flashed new boot¨ to avoid boot loop.....does that mean flash supersu after flashed twrp right away? how do i avoid bootloop? my build number is 36.0.A.1.100, should i worry about it?
my model is f3213
Thanks a lot
Click to expand...
Click to collapse
All boot released here are for Nougat only. You have Marshmallow so you are not on the right place
Why don't you update your phone to a recent MM firmware? .100 is very old and only useful for making TA backup.
can you guys work on kernel? cause charging speed is cancer and maybe you can set max cpu clocks a bit higher?
Hi @rrvuhpg
looking forward the update of your work?
Is there anyway to install or switch to magisk after flash this boot image?
I've tried but error 1 i love magisk simplicity
This kernel gives me, NVRAM Warn. error on Wifi, please fix it
NVRAM warning error on Wifi. F3213
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for all Xperia XA Ultra.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop. Not needed on 33.2.B.4.70 and upper.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file, "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases for Nougat:
2017/07/26: From 36.1.A.0.182 kernel sources and Ramdisk from 36.1.A.0.182 FR firmware.
https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
Click to expand...
Click to collapse
I have an Xperia XA Ultra single sim, I am root right now with this kernel, but I get an error on mi Wifi settings, it says "NVRAM warning error" I'm on nougat "36.1.A.1.86", I think the error is caused because of the dual kernel you made for both versions of XA Ultra (Single and dual Sim), can you please make individual kernels for individual versions?. thanx in advance.
kiukirimas said:
I have an Xperia XA Ultra single sim, I am root right now with this kernel, but I get an error on mi Wifi settings, it says "NVRAM warning error" I'm on nougat "36.1.A.1.86", I think the error is caused because of the dual kernel you made for both versions of XA Ultra (Single and dual Sim), can you please make individual kernels for individual versions?. thanx in advance.
Click to expand...
Click to collapse
Hi, kernel sources are unified for single and dual Sim models so I can't build individual kernel. I think that your problem is because you are on a newer firmware than my kernel. I will not update my work, maybe an other user can do it for you.
36.1.A.0.182 is still with error
rrvuhpg said:
Hi, kernel sources are unified for single and dual Sim models so I can't build individual kernel. I think that your problem is because you are on a newer firmware than my kernel. I will not update my work, maybe an other user can do it for you.
Click to expand...
Click to collapse
Hi, thanks for your answer, I just followed your advice, and now I can see is not the firmware, is the kernel who causes the problem. I just installed the 36.1.A.0.182 firmware version from flashtool, and installed the kernel, following your tutorial for root, but I'm still having the same problem. I must say that I successfully did root my previous phones in Nougat and marshmallow (Xa-E5-L1) and marshmallow in the Xa ultra too, but is only the Nougat version of XA ultra who gives me this problem, can you check it please?. I wanted to use another kernel from XDA, but I can't see any other, so please you are the only one person who can fix this. thanx in advance.
Hi, great work! Can you share the build script?
Hi all https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
is this working in my device please let me know before ill try it my device is F3212 running Nougat
ill try to root mine...someone can respond to me if its working or not.....?????????????
william.alovera said:
Hi all https://mega.nz/#!kgYgFCZJ!gmf6ptCwGJRdOeYwIJo3eGa-1er--yQPxjtxy6kbppU
is this working in my device please let me know before ill try it my device is F3212 running Nougat
ill try to root mine...someone can respond to me if its working or not.....?????????????
Click to expand...
Click to collapse
There are threads here that supports f3212, Be sure to read them all mate and be reminded of it's requirements like unlocked bootloader etc
Hello guys, I have few questions and hopefully someone can answer them.
I am trying to root my mate 10 pro with version:
BLA-L29 8.0.0.127(C432)
I want to root it with magisk and since twrp is not available yet,
is it possible to root by patching the boot image?
If it is possible, how do I extract the boot image without root?
This is what i found online.
Method 2: Patching Stock Boot Image
This method doesn’t require you to have TWRP in order to install Magisk 15.0 update.
1. Download the latest Magisk Manager APK: MagiskManager-v5.5.1.apk
2. Use a file manager to install the downloaded app on your device.
3. Grab the stock boot image (kernel) and it should be corresponding to the firmware installed on your device.
For Nexus and Pixel devices, you can extract it from the factory image. For other OEM devices, you might need to check it with your manufacturer’s support.
4. Copy the downloaded “boot.img” to the internal storage of your Android device.
5.Open the Magisk Manager app and tap on the ‘Install’ button.
6. Again, choose ‘Install’ and then ‘Patch Boot Image File’.
7. Navigate to the storage and select the ‘boot.img’ file you just transferred.
8. The Magisk Manager app will patch the stock boot image and place the resultant ‘patched_boot.img’ in the ‘MagiskManager’ folder.
9. Transfer the file from your phone to C:\adb folder on your PC.
10. Hold the SHIFT key on your PC and right-click on an empty space inside the folder. Then select ‘Open PowerShell window here’ from the menu.
11. Boot your Android into Fastboot mode and connect it to the PC.
Enter the following command to root your Android phone using Magisk 15.0 update:
fastboot flash boot patched_boot.img
Finally, reboot your device.
fastboot reboot
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Dagda-Esus said:
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Did you get the boot.img file ? or did you do it in another way ?
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
trackloading said:
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
Click to expand...
Click to collapse
ramdisk.img is correct. boot.img is ramdisk and kernel combined, but as of Oreo it's now ramdisk.img and kernel.img.
So patching ramdisk.img is the way to go?
yfaykya said:
So patching ramdisk.img is the way to go?
Click to expand...
Click to collapse
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
dawnc said:
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
Click to expand...
Click to collapse
Do you know your model number?
Like
xxx-CxxxBxxx
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
Did you get magisk working ?
lisa99 said:
Did you get magisk working ?
Click to expand...
Click to collapse
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the "Your device is unlocked" screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
ante0 said:
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the Your devices is unlocked screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
Click to expand...
Click to collapse
let me know if you figure something out.
ante0 said:
do you know your model number?
Like
xxx-cxxxbxxx
Click to expand...
Click to collapse
bkl-al20c00
dawnc said:
bkl-al20c00
Click to expand...
Click to collapse
You seem to have fixed it already?
ante0 said:
You seem to have fixed it already?
Click to expand...
Click to collapse
I've made a boot.img with supersu inside.
But can't fix magisk root
dawnc said:
I've made a boot.img with supersu inside.
But can't fix magisk root
Click to expand...
Click to collapse
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
ante0 said:
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
Click to expand...
Click to collapse
Have u found a way to make magisk work?
dawnc said:
Have u found a way to make magisk work?
Click to expand...
Click to collapse
It might be because loop is not fully working.
But no, haven't found any way.
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
dawnc said:
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
Click to expand...
Click to collapse
Not both at once no.
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...
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.
Hi everyone, I prefer remain with the Chinese rom for a while but I'd like to root my moto x40 with magisk.
I've tried but after flashing the patched boot.img the phone boot normally. the firmware has vbmeta so I followed the procedure suggested by the guide in this situations.
the weird thing is the patched root remain exactly with the same original dimensions.
I think this is an a type partition firmware due to boot.img presence but there is also a file called vendor_boot.img. according with this article seems an a/b type.
Vendor Boot Partitions | Android Open Source Project
source.android.com
I attach a screen of the firmware content, the log of patched boot file and the adb process.
Please, can anyone explain me how can I root successfully? thanks
Did you unlock the bootloader? Once done you need to flash a patched init_boot.img instead of boot.img through fastboot.
This guide should be useful (it's for the Pixel 7s, but should work with this phone, and of course use the init_boot.img from the original ROM file for your phone)
Hope that helps
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
vendor_boot.img
Shared with Dropbox
www.dropbox.com
This is my vendor-boot
Do you lose VPN access after bootloader unlocked?
No, I didn't lose
mikaelcbr2 said:
hi, thank you for the answer.
yes the bootloader was unlocked.
This rom is the same as my phone's. I had take by lolinet.
unfortunately magisk is unable to patch vendor_boot , I'm trying to attach it.
Is Someone able to patch?
Click to expand...
Click to collapse
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
sooyong94 said:
You need to patch init_boot.img using Magisk, and flash both init_boot_a and init_boot_b with the patched file through fastboot
Click to expand...
Click to collapse
Yes I followed the guide, thanks