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
Related
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
@KaiserSnorezay
XZDR is still not compatible with MM, that's why you got a bootloop...
Also you can't install the "regular" TWRP with twrp manager on a LB as there is no recovery partition... it won't work and probably will mess your phone in the process.
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
http://forum.xda-developers.com/xperia-z2/development/rom-official-6-0-1-23-5-0-486-beta-t3336770
Just did it exactly this way yesterday on my friends d6503 (minus the d6502 patch obviously) had 0 troubles MM, root and recovery working perfectly.
Thanks, will try this today. Is wiping data required or can i get by by just flashing the older one?
ptmaniac said:
The solution is to flash any KK / LP .ftf with flashtool (i would wipe everything when flashing as i have backups of my data/apps) , root it with kingroot or any other method you like, install xzdr for KK/LP and finally reboot to recovery and install the latest MM prerooted rom from niaboc which already has root&recovery (not xzdr btw) included. Since you have D6502 don't forget to install the baseband patch after the rom again
Click to expand...
Click to collapse
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
KaiserSnorezay said:
I managed to flash and root 17.1.2.A.0.314, but once again I'm unable to get any damn recovery to work. Installed XZDR, after that TWRP, in both cases it refuses to boot into recovery mode. What am I missing?
Click to expand...
Click to collapse
Weird, after you have your phone rooted it should be simple to install xzdr... just enable usb debugging in the phone and make sure you have the adb drivers correctly installed in your pc.
Download the latest xzdr from nut's thread ( http://forum.xda-developers.com/showthread.php?t=2261606 ) unzip it and run install.bat . After a successful install the phone should reboot to twrp automatically and it's done.
Okay, I fixed it..using Flashfire! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
KaiserSnorezay said:
Okay, I fixed it..using ! No idea why the recovery didn't work earlier, but now finally I'm on Marshmallow. Thanks for the help!
Click to expand...
Click to collapse
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
dodge911 said:
hey bro, just read your post. Yesterday i got an update msg in my software update menu of my Xperia Z2 D6502. After i updated i went into bootloop. i have very important stuff in my phone. i updated earlier too all the updates that sony servers inform about. so then i thought to flash with the stock file. Although i didnt knew the firmware number , i just flashed with 5.1.1 , 1st with Customized IN & later with of US. Both of them didn't work as well. Please help me out. I'm not much aware about this root stuff & all. hope to get reply soon from you or anyone in this forum.
-also i don't know the exact firmware number-
Click to expand...
Click to collapse
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
KaiserSnorezay said:
Try what ptmaniac suggested - flash an older FTF that can be rooted (more recent ones can't), root it, install recovery and then flash the newest build.
You'll have to improve your Google-fu to find a suitable firmware and a root technique for it.
Click to expand...
Click to collapse
okay. you mean flashing any old firmware ( which i did and still in bootloop ) & root it. Then installing recovery for the same firmware ?
with "recovery" will i be able to get back my whole data ?
KaiserSnorezay said:
Long story - Tried to apply the latest Marshmallow rooted package for D6503 on my 6502 that was already rooted with XZ dual recovery. It installed successfully, was rooted too...but I forgot to add the patch that would fix the radio not working. So I try to reboot to recovery...and that doesn't work anymore. I tried installing TWRP recovery from the manager app, but it wouldn't reboot. Then I ran the XZ recovery installer externally, and now my phone is ****ed. Stuck at an infinite boot loop.
At this stage the only thing I can access is flashtool and fastboot, and since my bootloader is locked I can't flash a recovery that way (nor do I want to permanently lose DRM keys/camera quality as I've heard happens with unlocking the bootloader). I have a memory card and I used the option to disable loading the recovery specified on the XZ thread by adding a 'donotload' file on the sd card.
Still no use - I get a Sony logo for about 5 seconds, the screen goes dark and back to the same. At this point probably my recovery is screwed up or non existent and a bad situation has gone worse with the bootloop.
What can I try now?
Click to expand...
Click to collapse
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
DedSec_35 said:
hey i am having same problem with my xperia Z2 , it stucked in bootloop ,i have already tried to flash new firmware from xperifirm using flash tool,but i think my usb debugging is off, what can i do ,i cant start my phone so there are no chances for turning USB debugging on,what can i do, any solution,, just want my phone back,it will be okay if I loose my all data..please
Click to expand...
Click to collapse
Sorry, I ditched my Z2 for a Oneplus 3 in August 2016. Learnt my lesson, only going to use phones with easily unlockable bootloaders.
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
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, on 33.2.B.4.70 and upper "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 Marshmallow:
2016/12/26: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware. (Works up to 33.2.A.3.123)
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
2017/03/14: From 33.2.B.4.70 kernel sources and Ramdisk from 33.2.B.4.70 MAA firmware.
https://mega.nz/#!YhREgQCL!yV8EEyhFw5Q5QUE5FGePtXW_08EecqhJHA_ppqsRka0
Releases for Nougat:
2017/07/18: From 33.3.A.0.131 kernel sources and Ramdisk from 33.3.A.0.131 FR firmware.
https://mega.nz/#!4poC2JpI!MnJEz36P0f-8g3CaXrNIi7fbR_tWfpN5uqYgwUuXQ6E
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
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.
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.
Releases:
12/26/2016: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware.
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
Click to expand...
Click to collapse
Can you please help me convert the boot.sin and system.sin into an .img file? thanks
donedos said:
Can you please help me convert the boot.sin and system.sin into an .img file? thanks
Click to expand...
Click to collapse
Hi, you can use "Assayed Kitchen" (some steps are explained in it) and Flashtool for that you need, you will need "Carliv Image Kitchen" too. I will not make a step by step guide but you can ask me if you need in private message.
rrvuhpg said:
Hi, you can use "Assayed Kitchen" (some steps are explained in it) and Flashtool for that you need, you will need "Carliv Image Kitchen" too. I will not make a step by step guide but you can ask me if you need in private message.
Click to expand...
Click to collapse
Thanks for the reply. I'll check it out. ? ? ?
Has updated 7
rrvuhpg said:
Hi,
I will release here my updated "boot.img" files for the Xperia XA Dual Sim.
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, on 33.2.B.4.70 and upper "dm-verity" is disabled by default.
They will probably not work on upper firmwares than the one they are built.
Releases:
2016/12/26: From 33.2.B.3.123 kernel sources and Ramdisk from 33.2.B.3.105 FR firmware. (Works up to 33.2.A.3.123)
https://mega.nz/#!swQwHLZR!ar3qmGKlvTTESpmsra4haUYmQB_gnpjn7arMKy3WBIo
2017/03/14: From 33.2.B.4.70 kernel sources and Ramdisk from 33.2.B.4.70 MAA firmware.
https://mega.nz/#!YhREgQCL!yV8EEyhFw5Q5QUE5FGePtXW_08EecqhJHA_ppqsRka0
Click to expand...
Click to collapse
Bro, i love you!
But, mod boot for android 7, please!
stuck in bootloop after flashing boot.img 2017/03/14 file 33.2.b.4.70 file for f3116 from the given link but still my phone doesnt boot up , please help
Is there a boot 33.3.A.1.97 for F3112? Thank you very much in advance.
jackdaniels2017 said:
Is there a boot 33.3.A.1.97 for F3112? Thank you very much in advance.
Click to expand...
Click to collapse
You tried with 33.3.A.0.131 boot before asking for a new one?
rrvuhpg said:
You tried with 33.3.A.0.131 boot before asking for a new one?
Click to expand...
Click to collapse
131st did not try. I'm afraid to get a brick.
How we relock bootloader loader in sony xperia xa ultra f3216
How we relock bootloader loader in sony xperia xa ultra f3216
Hi all,
I'm happy to share with you my new TWRP recovery 3.1.0-0 built from sources. It works for Single Sim XA only.
As before you can't wipe /cache because it is used by TWRP and I don't know how to force unmount, decryption of /data doesn't work so if you want a full backup or explore files use an unencrypted data partition.
Download link:
https://mega.nz/#!ZxBBGTbA!C2FSqJE0Xv6yQDPlmzRkmGOVxYhRMMhe3Z2TGTCvCkg
Flash it with fastboot.
Have a nice day
So works in 100%
https://zapodaj.net/c5beb966e478a.png.html
backup
When I do backup with 3.1 TWRP and when I choose partitions to backup, it says: Data (excluding data stored in internal storage) - when backup is in progress info pop-ups that data will be backed up without eg. pictures or downloaded items.
My internal memory is not encrypted (was formatted) so why is that ?
This is not a case with previous 3.0.2 TWRP. ALL was included in backup.
regards,
Feature request
Hi rrvuhpg,
Is it possible for you to add complete DATA partition backup option in your recovery ?
I mean something like Data-image, so nothing would be excluded in backup.
Also if you could add phone battery charging when working in recovery, that would be very useful, please.
I know it sounds like "feature request", but maybe you could consider adding these items.
regards,
Andrzej_Andrzej said:
Hi rrvuhpg,
Is it possible for you to add complete DATA partition backup option in your recovery ?
I mean something like Data-image, so nothing would be excluded in backup.
Also if you could add phone battery charging when working in recovery, that would be very useful, please.
I know it sounds like "feature request", but maybe you could consider adding these items.
regards,
Click to expand...
Click to collapse
Hi, sorry but I will not add the possibility to add complete DATA partition backup. I will verify on the old TWRP but it should not too, it's a decision taken by the TWRP dev team.
If you want the official answer look here: https://twrp.me/faq/backupexclusions.html
For the battery charging I don't need to add the feature, you phone is charging well throug TWRP (look at the recovery logs) it only doesn't show the battery level, it's more aesthetic than usefull but if I release an updated TWRP I will try to show it. A golden rule to know is to charge the battery before playing with backup/restore/update.
rrvuhpg said:
Hi, sorry but I will not add the possibility to add complete DATA partition backup. I will verify on the old TWRP but it should not too, it's a decision taken by the TWRP dev team.
If you want the official answer look here: https://twrp.me/faq/backupexclusions.html
For the battery charging I don't need to add the feature, you phone is charging well throug TWRP (look at the recovery logs) it only doesn't show the battery level, it's more aesthetic than usefull but if I release an updated TWRP I will try to show it. A golden rule to know is to charge the battery before playing with backup/restore/update.
Click to expand...
Click to collapse
Hi, ok I read this,and They say: "You may want to backup the internal storage as well but this is not possible in the TWRP GUI. You have to do it manually (e.g. with "tar" when your internal storage is mounted in TWRP".
Could you please explain how to do it manually using "tar", I mean how to backup Data partition manually ?
I am just curious why it is not recommnded to do full backup of Data including user data ?
Hi rrvuhpg,
Is it possible for you to make a tutorial how to make recovery TWRP for xperia xa single sim ?
What is configuration file for it and where it can be found? , how to compile it from sources ?
Which sources should one use ?
There are some tutorials about how to compile it, but not specifically related to xperia xa f3111.
What kind of tools should one use ?
You have an experience with it so based on it can you share your observations.
regards,
Andrzej_Andrzej said:
Hi rrvuhpg,
Is it possible for you to make a tutorial how to make recovery TWRP for xperia xa single sim ?
What is configuration file for it and where it can be found? , how to compile it from sources ?
Which sources should one use ?
There are some tutorials about how to compile it, but not specifically related to xperia xa f3111.
What kind of tools should one use ?
You have an experience with it so based on it can you share your observations.
regards,
Click to expand...
Click to collapse
Hi,
I don't need to make a tutorial, you can find all you need on Xda: https://forum.xda-developers.com/showthread.php?t=1943625
and some very useful threads here : https://forum.xda-developers.com/general/xda-university
rrvuhpg said:
Hi,
I don't need to make a tutorial, you can find all you need on Xda: https://forum.xda-developers.com/showthread.php?t=1943625
and some very useful threads here : https://forum.xda-developers.com/general/xda-university
Click to expand...
Click to collapse
Hi, I read those tutorials and I am learning at present a lot of new things, but it leaves me still with many to read and acquire.
I found your files on github: https://github.com/search?utf8=✓&q=device_sony_tuba&type=
and I was wondering if there were xperia xa configuration files. I figured those are for dual sim xa. So I would like to kindly ask you if you could put xperia xa single sim configuration files as when you do TWRP recovery for this phone (for which I am very grateful) anybody could use it and learn from it. Especially it is difficult to make boardconfig.mk correctly and not too many people write about xperia xa single sim building, compiling, etc. It is a not very popular smartphone I wonder.
I hope that it would be OK with you,
regards,
Andrzej_Andrzej said:
Hi, I read those tutorials and I am learning at present a lot of new things, but it leaves me still with many to read and acquire.
I found your files on github: https://github.com/search?utf8=✓&q=device_sony_tuba&type=
and I was wondering if there were xperia xa configuration files. I figured those are for dual sim xa. So I would like to kindly ask you if you could put xperia xa single sim configuration files as when you do TWRP recovery for this phone (for which I am very grateful) anybody could use it and learn from it. Especially it is difficult to make boardconfig.mk correctly and not too many people write about xperia xa single sim building, compiling, etc. It is a not very popular smartphone I wonder.
I hope that it would be OK with you,
regards,
Click to expand...
Click to collapse
You can use the same device tree for single and dual (you can change all "tubads" by "tubass") , I will push changes to Github so you will have the correct Boardconfig. You will have to download the kernel tree from Sony or modify the Boardconfig to use a prebuilt kernel extracted from the modified boot or TWRP for your device.
If you want to learn I recommend you to try to build TWRP for a device who have a lot of documentation first, after it will be easy for you to do the same for XA.
rrvuhpg said:
You can use the same device tree for single and dual (you can change all "tubads" by "tubass") , I will push changes to Github so you will have the correct Boardconfig. You will have to download the kernel tree from Sony or modify the Boardconfig to use a prebuilt kernel extracted from the modified boot or TWRP for your device.
If you want to learn I recommend you to try to build TWRP for a device who have a lot of documentation first, after it will be easy for you to do the same for XA.
Click to expand...
Click to collapse
Hi, rrvuhpg
Once again thank you for prompt reply, help and understanding.
Thank you very much indeed. Of course as my knowledge will progress please expect a lot of questions from my side.
best regards,
Andrzej_Andrzej said:
Hi, rrvuhpg
Once again thank you for prompt reply, help and understanding.
Thank you very much indeed. Of course as my knowledge will progress please expect a lot of questions from my side.
best regards,
Click to expand...
Click to collapse
No problem but if you have a lot of questions ask me in private message. I updated my Github on CM13 branch. Good luck
rrvuhpg said:
No problem but if you have a lot of questions ask me in private message. I updated my Github on CM13 branch. Good luck
Click to expand...
Click to collapse
Hi @rrvuhpg,
I've asked for your help regarding the compilation of the kernel for xperia xa in a private message. I've tried to compile the kernel from your git, but I'm not seeing any zImage after the compilation. I've also downloaded the kernel archive from sony archives and succeeded compiling this one with the default config for a F3111 (tubass_defconfig). I got an *Image* binary file in the out directory, probably this one is the zImage, but I'm not sure if I need to do something else to this binary before packing it along with the ramdisk. I figured that you're doing something additionally. I'm doing this because I want to get rid of the dynamic brightness adjustments in the kernel. Please, can you help me?
Thanks.
cojocar.andrei said:
Hi @rrvuhpg,
I've asked for your help regarding the compilation of the kernel for xperia xa in a private message. I've tried to compile the kernel from your git, but I'm not seeing any zImage after the compilation. I've also downloaded the kernel archive from sony archives and succeeded compiling this one with the default config for a F3111 (tubass_defconfig). I got an *Image* binary file in the out directory, probably this one is the zImage, but I'm not sure if I need to do something else to this binary before packing it along with the ramdisk. I figured that you're doing something additionally. I'm doing this because I want to get rid of the dynamic brightness adjustments in the kernel. Please, can you help me?
Thanks.
Click to expand...
Click to collapse
Hi, your question is a little off topic here but I will answer you
In the "out" directory, don't use the zImage but zImage-dtb. You only have to pack it along with the ramdisk. If you have any questions please use your thread https://forum.xda-developers.com/xperia-xa/help/dynamic-brightness-question-t3614808
Quote me if you need help
Hi, rrvuhpg.
I've got a little problem. I flashed the Customized RU Firmware 33.2.A.4.70 half a year ago. I had installed TWRP and SuperSU. But now I flashed the Customized CE5 Firmware with the version 33.3.A.0.131 and I tried to flash TWRP via Adb and I get this error message everytime and I also tried to boot the custom recovery via Adb. It shows the Sony logo than Black-Screen and then it start normaly. I tried also to reflash the Firmware and flash other Firmware from other Countries.
Code:
C:\adb>adb devices
List of devices attached
RQ3000F9PS device
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes sending 'recovery' (15814 KB)...
OKAY [ 0.578s]
writing 'recovery'...
FAILED (remote: This partition doesn't exist)
finished. total time: 0.583s
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.577s]
booting...
OKAY [ 0.043s]
finished. total time: 0.622s
I hope you can help me!
JustTryIt130 said:
Hi, rrvuhpg.
I've got a little problem. I flashed the Customized RU Firmware 33.2.A.4.70 half a year ago. I had installed TWRP and SuperSU. But now I flashed the Customized CE5 Firmware with the version 33.3.A.0.131 and I tried to flash TWRP via Adb and I get this error message everytime and I also tried to boot the custom recovery via Adb. It shows the Sony logo than Black-Screen and then it start normaly. I tried also to reflash the Firmware and flash other Firmware from other Countries.
I hope you can help me!
Click to expand...
Click to collapse
Hi, TWRP and boot for Marshmallow doesn't work for Nougat. You will have to wait for a new boot and recovery for Nougat (and a new guide to root it).
@rrvuhpg
Maybe you can help... I successfully flashed this on my XA MM, and flashed ultra slim MM rom, but rom will not boot. Usually just infinite boot animation, but once I got it to start 'optimizing apps', but rebooted about halfway. Do you think the recovery has anything to do with it? As you stated, I can't wipe cache, but install log shows successful cache format and system complete... Thanks
levone1 said:
@rrvuhpg
Maybe you can help... I successfully flashed this on my XA MM, and flashed ultra slim MM rom, but rom will not boot. Usually just infinite boot animation, but once I got it to start 'optimizing apps', but rebooted about halfway. Do you think the recovery has anything to do with it? As you stated, I can't wipe cache, but install log shows successful cache format and system complete... Thanks
Click to expand...
Click to collapse
Hi, did you used the modified boot for the right firmware? Did you downgraded your firmware from Nougat without wiping Data or restored Nougat Data on MM? Did you changed root method (SuperSu to Magisk)? As I know no problem with TWRP or boot. I got the same problem if I downgrade from N to MM without wiping Data.
@rrvuhpg
I question for you brother
we could help make boot.img and recover.img for xperiu L1 G3311
This is so BIG thank you very very thankxxxxxx bro
Firmare download this: https://mega.nz/#!n9pDjLob!m9_A4L4ij...8nabHmx3-1mwQA
Link: for xda this https://forum.xda-developers.com/xpe...oader-t3670750
Very Please help if you can brother
THIS POST IS EXTENSION TO
https://forum.xda-developers.com/xp...t-xperia-x-f5122-android-n-34-2-2-47-t3594502
and
https://forum.xda-developers.com/xperia-x/development/root-xperia-x-f512234-3-0-206-7-1-1-t3635595
Please read carefully and flash kernel for the LATEST UPDATE (Project SUZU )
for F5122_34.3.A.0.238 - 7.1.1 - 2 OCTOBER 2017 update
F5122 IS AT https://mega.nz/#F!7RRWEJjZ!qbotcsuXiKfXs2gwpVoBAw
F5121 .. https://mega.nz/#F!qUwV3R5Q!zpi18kKSNuS7vAHH9jOoQA (THANKs @velemas )
both f5121/5122 folders have two kernel images, if you flash the WITH SU image, the device will wakeup rooted. However if you flash the CLEAN kernel, you must flash TWRP3.1.1 (use adb fastboot commands) and from twrp you must flash SUPERSU or Magisk (whichever) -
PLEASE PROVIDE ME WORKING MAGISK (some friends have had been using) i will update my repository.
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
Click to expand...
Click to collapse
for F5122_34.3.A.0.224 - 7.1.1 - 8 SEPTEMBER 2017 update
F5122 IS AT https://mega.nz/#F!GFo1EArZ!ngb5WsZJtbmFwXk_ImN-TA
F5121 .. https://mega.nz/#F!2EQniYoZ!0Rhj15GN7nSRmrTFMC8smg (THANKs @Mikolaj612 and @velemas )
-if you don't have th 34.3 fsc script , i have included in the folder (closing Partitions takes TIME, so be Patient ! )
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
-
.
.
Click to expand...
Click to collapse
ROOT DIRECTORY (ON MEGA)
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________
for F5122_34.3.A.0.217 - 7.1.1 - 8Aug2017 update
F5122 IS AT https://mega.nz/#F!iUB00abB!N7sDP1pv33ZCEC76j3RkYQ
F5121 .. AT https://mega.nz/#F!2FI0BI4B!f-wrWGTOzhgYX-_aLEBhBg ( THANK YOU @Mikolaj612 )
Code:
[SIZE="5"]
-if you don't have th 34.3 fsc script , i have included in the folder
-also i have inclused mixer_paths_wcd9335.xml, on 98% VOLUME level, IF you think sound output is LOW,,, just REPLACE it from /system/etc folder!
- :)
[/SIZE]
base directory
https://mega.nz/#F!aZAljazZ!zNLnLxH6flBxUsaTb167Jw
____________________________________________________
for F5122_34.3.A.0.206 - 7.1.1 - july2017 update
UPDATED KERNELS
F5121 IS AT https://mega.nz/#F!HcZmTIhR!0oCiMfh9uT-AdHp-bdSqZw (THANKS TO @velemas)
F5122 IS AT https://mega.nz/#F!fRBEVS5C!QjT-TgxZc9FYwAbh-F5IgA
during past 3 days; I had to flash my X, 3 times for build 34.3.A.0.238 ,
why?
here are my findings and i want your contribution
1.
after CLEAN FLASHING OF STOCK via FLASHTOOL ... I BOOT MY DEVICE, SETUP THE GOOGLE ACCOUNT(S) sync data etc AND then i switched off the device and FLASHED KERNEL without twrp and without SuperSU, i had to FLASH TWRP3.1.1 via ADB. when I boot my device held power+volumeDOWN key and went in to recovery. I FOUND twrp3.1.1 cannot access internal storage, asked password
SO
2.
after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL, I NEVER BOOT MY DEVICE AND DIRECTLY flashed KERNEL ( version which doesn't have twrp orsupersu) LATER I flashed TWRP3.1.1 via ADB. I went in to recovery and this time twrp was able to access my internel storage. So I flashed KCAL (which later i found doesn't work for this kernel) and I FLASHED SUPERSU 2.82.zip.
I switched off my device and later boot it up, I setup all the accounts in android and sync data.
LATER I FOUND that my internal storage has only 10gb left, I got surprised and I found that my SYSTEM STORAGE is TAKING 50GB out of 64GB. I never found any such folder in the /system having files worth 40gb after android itself (10gb).
3.
again third time, after CLEAN FLASHING OF STOCKROM VIA FLASHTOOL. I FLASHED KERNEL having no TWRP but having SUPERSU. and boot my device and went thru sony setup. I found out that found out that only 15GB out of 64GB is used.
and now i am using device normally
the only explanation i can give is that when i flashed superSU via twrp3.1.1, it made partitions incorrectly, but when supersu is flashed by script, it works just fine.
any comments? who can try all above with his device?
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
Fotakernel is the option you are looking for
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
kloroform said:
If I flash latest update using xperifirm which option should I exclude to keep TWRP as recovery?
Click to expand...
Click to collapse
You may skip FotaKernel.
however you can always flash latest recovery twrp3.1.1 is out,
gaurav_15 said:
Doesn't your phone distort at that high gain(I.e 92)?? Mine starts to crackle at 86 or 88 on headphones..
With 7.1. Update Sony made our x more quite but clearer, before it was more loud but harsh too..
Click to expand...
Click to collapse
at 96, it does, I felt 86 (even 88) pretty low , special if the mobile is in bag and i am driving.
but at 92, its just fine.
also when u use the noise cancellation option ON, you get perfect quality sound on sony headphones
btw, i am using samsung earbuds, and works amazingly well!
Dominykas Only One said:
Nice work :good:
I was going to ask if I can flash your older kernel to newer one, but I guess I don't have too. By the way, do you know what's the difference between .238 and .224 kernels? Didn't sony just released security update? Sorry, I'm new to Xperia Phones. :silly:
you wrote include wrongly(probably typo)
Click to expand...
Click to collapse
welcome to Sony's complex world of kernels builds and LOST DRM KEYS
1. KERNEL USUALLY GETS UPDATE AS AND WHEN GOOGLE UPGRADES ANDROID ( for example from marshmellow to nougat )
2. on Nougat (android 7) the Linux kernel is 3.1.x.x , on this kernel sony has been releasing various builds with minor chances in security patch and/or some bug fixes in volume rockers / bluetooth / NFC connectivity etc
so technically, you CAN use android N kernel came with initial build by sony over latest BUILDS by sony.
on the booting level it will not affect your device
however I am not sure what will happen once android is loaded and it may show u older security patches or may crash
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
JukiCro said:
hey, thanks a lot for the update!
I am on .228 rooted, I got notification for system update, so after I update + flash your .238 with SU and I am good to go?
Click to expand...
Click to collapse
on unlocked bootloader, OTA fails. but you can try!
but if anyhow you upgrade to .238 via OTA, you will lose you rooting and twrp. so yes you will have to FLASH the kernel only.
kloroform said:
Prerooted Magisk Manager compatible kernel
You can flash from TWRP, just select Install then click Image File, select the kernel img file and selectBoot and flash
https://www.mediafire.com/file/40v6g55eluw7k70/patched_boot.img
Intsall Magisk Manager from here
https://github.com/topjohnwu/MagiskManager/releases/download/v5.3.0/MagiskManager-v5.3.0.apk
Click to expand...
Click to collapse
thank you! i found magisk interesting option since its system , Open source and let you install modules (including xposed) (if supported)
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
sucker for sony's said:
Does the 238 kernel include drmfix? I am still on Android 6.0.1 and am looking to jump straight to the latest 7.1.1fw note i don't have drm key's they are long gone.
Click to expand...
Click to collapse
you and update directly to 7.1.1
the kernel has drm fix
where can i download the 34.3.a.0238 tft rom ?
nova001 said:
where can i download the 34.3.a.0238 tft rom ?
Click to expand...
Click to collapse
Using xperifirm software or directly from xpericheck.com
hhjadeja007 said:
Using xperifirm software or directly from xpericheck.com
Click to expand...
Click to collapse
yee a saw, but i dont have alfa file account :S
flashtool (xperifirm ): error invalid upda information...
if i flash this kernel do i lose my drm key's? what is better version to use with SU or without? Best Regards.
Doesn't work for me. Root works just half a way. I can use root apps like adaway etc. but i can't uninstall any apps, mount /system as rw and even install busybox. Something is broken out there. 34.3.A.0.238
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.