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
Related
Credits:
@T10NAZ - who supplied the kernel and a lot of guidance/help
Compile Yourself:
Guide to compiling yourself: http://forum.xda-developers.com/zenwatch-2/help/wip-compiling-twrp-wi502q-wren-device-t3341435 *Will continue to update
Steps to Using:
1) fastboot oem unlock (erases your /data partition)
2) fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
*DON'T FASTBOOT FLASH RECOVERY* - Not tested
Download Recovery:
Compiled recovery.img file: https://joeykrim.com/android/devices/wren/twrp-v3.0.0-0.jk-v3.recovery.img
Known Bugs:
I'll be working on these, but if anybody else wants to - feel free to send a pull request: https://github.com/joeykrim/wren
Fixed (in v3) - thanks @Dees_Troy - 1) Unable to backup recovery partition - isn't visible from backup menu.
Fixed (in v2) - thanks @Dees_Troy - 2) The screen resolution is small.
Updated Android OS from LCA59B to LCB51 and boot and recovery partitions aren't available in TWRP backup menu.
Please post any feedback, comments, or questions. I'll do my best to update and fix bugs, but please feel free to participate!
Hell yea! Development for all Zenwatch 2 owners!
joeykrim said:
Credits:
@T10NAZ - who supplied the kernel and a lot of guidance/help
Compile Yourself:
Guide to compiling yourself: http://forum.xda-developers.com/zenwatch-2/help/wip-compiling-twrp-wi502q-wren-device-t3341435 *Will continue to update
Steps to Using:
1) fastboot oem unlock (erases your /data partition)
2) fastboot boot twrp-v3.0.0-0.jk-v1.recovery.img
*DON'T FASTBOOT FLASH RECOVERY* - Not tested
Download Recovery:
Compiled recovery.img file: https://joeykrim.com/android/devices/wren/twrp-v3.0.0-0.jk-v2.recovery.img
Known Bugs:
I'll be working on these, but if anybody else wants to - feel free to send a pull request: https://github.com/joeykrim/wren
1) Unable to backup recovery partition - isn't visible from backup menu
Fixed - thanks @Dees_Troy - 2) The screen resolution is small. Fixed now and in the v2 .img posted above
Please post any feedback, comments, or questions. I'll do my best to update and fix bugs, but please feel free to participate!
Click to expand...
Click to collapse
Excellent work. By the way, could you help me get the original boot.img? I flashed on a different model and got bootloop.
Can someone please make a TWRP backup and upload it somewhere? ... I tried to change the LCD density and now my whatch just shows a black screen when I try to boot.
But luckily I can still get into TWRP
AFAIK the lcd density is set in /system/build.prop
ro.sf.lcd_density=***number***
perhaps you can pull this from your watch, alter it and then push it back where it belongs...
I tried that, but still no display
luksab said:
Can someone please make a TWRP backup and upload it somewhere? ... I tried to change the LCD density and now my whatch just shows a black screen when I try to boot.
But luckily I can still get into TWRP
Click to expand...
Click to collapse
I am also in need of TWRP backup for WI502Q. I cannot get out of CSC Fastboot. Please help
I have a big problem. My watch is a WI502Q starts with TWRP 3.0.0.0. It can't boot and it hasn't got an OS on. I can'i install the Ota.zip. It is closed wit status 7 error. I need a full backup with TWRP or original (official) Boot.img, recovery.img and system.img. Could you help me, please? Thank you in advance.
Did you ever get these files?
Loop2323 said:
I have a big problem. My watch is a WI502Q starts with TWRP 3.0.0.0. It can't boot and it hasn't got an OS on. I can'i install the Ota.zip. It is closed wit status 7 error. I need a full backup with TWRP or original (official) Boot.img, recovery.img and system.img. Could you help me, please? Thank you in advance.
Click to expand...
Click to collapse
I'm in a similar situation as you and I'm not sure what to do. Were you able to find anything? Can anybody provide me with a TWRP backup?
Joeykirm now do zenwatch 3 plzkthx
momentandroid said:
Joeykirm now do zenwatch 3 plzkthx
Click to expand...
Click to collapse
Can anyone confirm that this has worked for them? The previous posts of several people with soft bricks or boot loops and no confirming comments makes me hesitant to try it... However, I just got mine today so I'm going to go home and try to boot twrp anyways, if I'm able to complete a backup I'll post the nandroid for all you guys
Hi all,
I'm happy to share my TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
caosugai said:
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
Click to expand...
Click to collapse
No tuts for the XA, you can try some kitchens like "Assayyed kitchen" to edit the rom. Try guides for MTK devices (64bits) or CM/AOSP. But nothing is made for XA, use them as base.
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
caosugai said:
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
Click to expand...
Click to collapse
For Q&A other than TWRP 3.0.2-6 release it's here:
http://forum.xda-developers.com/xperia-xa/help/qa-t-template-thread-sony-xperia-xa-t3479938/page1
Thank you
Help...
rrvuhpg said:
Hi all,
I'm happy to share my new TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
Click to expand...
Click to collapse
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
ahero123a said:
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
Click to expand...
Click to collapse
HI, it will not boot to recovery if you have a stock boot
Download the rootpack for Dual Sim and flash the boot.img first.
Fastboot commands are:
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"
without quotes.
Change the name of the .img if needed.
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
I accidentally flashed a Retail US version on my Moto Z Retail EU, and now I am having a "bad key" at the Warning on boot up. Can someone provide me with a 7.1.1 or 7.0 link for Retail EU for the XT1650-03? It's for the normal Moto Z, not Play or Force. I NEED an Retail EU Boot as I flashed a wrong one and I cannot go back to 6.0.1 to fix it, so my Boot is broken until someone gives me a proper EU one for 7.0 or 7.1.
Thanks in advance!
Note: I am getting this when trying to flash the "XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" files:
D:\MAIN FOLDER\Android\Moto Z\XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\GRIFFIN_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.078s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.805s]
finished. total time: 0.885s
So yeah, I need a boot image that isn't signed with a bad key for RETEU.
Fixed. Flashed a Retail US 7.0 STOCK ROM even though it said "bad key", and then I flashed erfanoabdi's "Stock" 7.1.1 ROM which flashed a working boot.img that doesn't cause this problem.
Thread closed.
i have same problem bro but i didn't understand your solved please help me
i have same problem bro but i didn't understand your solved please help me
anatete404 said:
i have same problem bro but i didn't understand your solved please help me
Click to expand...
Click to collapse
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
yanniclord said:
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
Click to expand...
Click to collapse
ok i will try flash it tomorrow but my phone still say bad key and didn't star i flash 7.0 with erorr and 6.0 with erorr
i see erorr bootloader not found when i flash with fastboot i mean my phone didn't boot in recovery or normal just fastboot
I am not understanding most of what you are saying, but I can prepare a little .zip with everything you need for you. I make a .bat file that you need to run which should do all the work for you.
anatete404 said:
...
Click to expand...
Click to collapse
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
i flash your rom bro when i flash i cant get recovery only fastboot please help me
try another Kernel flashing by TWRP https://forum.xda-developers.com/devdb/project/?id=17677#downloads
anatete404 said:
i flash your rom bro when i flash i cant get recovery only fastboot please help me
Click to expand...
Click to collapse
Would you please try to at least speak a little proper English and use punctuations, it's really hard to read.
i need flash for my phone i upload problem and info i am sorry about english but please help me
anatete404 said:
i need flash for my phone i upload problem and info i am sorry about english but please help me
Click to expand...
Click to collapse
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
thx bro but this https://androidfilehost.com/?fid=889964283620761640
working to my info phone i uploaded photo
Benoe said:
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
Click to expand...
Click to collapse
Hey your link doesn't work anymore. Is it for 7.0+ and RETEU? If so, please send it to me !
yanniclord said:
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
Click to expand...
Click to collapse
Hi,
I tried to unlock bootloader following instruction on Motorola website then my moto z play has "BAD KEY" and keep restarting with that message on the screen. I found and used your file but it didn't help my device out of the "BAD KEY". Please help. Thank you
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
BootLoader needs to be Unlocked and of course Usual T&C's apply. Use at your own risk don't blame me if you brick your device or lose your valuable data etc etc.
So what's different about this ROM??
Ok so I have been working on this for quite sometime during the little free time I have.
The ROM is my own preferences only and it may not be to everyone's tastes so you're quite welcome to take it, leave it, add to it, strip it, mod it, etc, etc.
The ROM ditches the not so useful stuff of Sony's but retains what I consider the good stuff like Music Album and the Camera.
Where possible I have replaced the Sony stuff with Google's Stuff which receive regular updates and keep the Rom looking fresh.
The trick to this ROM was finding a good balance without breaking anything in the process which I think I have now achieved.
This is a list of the visible apps installed, there are quite a few none visible Sony & MediaTek apps still installed that relate to settings functions and some background stuff.
Google Apps:
Clock
Calculator
Contacts
Calendar
Chrome
Drive
Files
GMail
Hangouts
Maps
Messages
Phone
Photos
Play Store
Wallpapers
YouTube
Sony Apps:
Album (Please disable this in /settings/app It will constantly search for other apps I removed otherwise. Use the pre-installed Google Photos app instead)
Camera
Music
Radio
Swiftkey (Left this in because I like it)
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Flashing InstructionsThe ROM is packaged as a TWRP Backup containing system, oem, boot and recovery (TWRP)
First you will need to install this TWRP HERE which has oem partition support and others too.
1. Install the TWRP Recovery above.
2. Boot to the new TWRP and backup oem, system and boot then move it to a safe place off device or to and external sdcard. Same goes for anything you value like pictures, music, etc, etc
3. Once you have Backed Up everything FORMAT your /data partition using TWRP. Wipe > Format Data (type yes to confirm)
When that's done choose Wipe > Advanced Wipe and select Dalvik / ART Cache and Cache after that from the TWRP menu choose Reboot and select Recovery
4. When back in recovery swipe to allow then do a quick Backup of any small partition like boot or recovery. This will just create the folders on your clean data partition unless your default backup is external sdcard.
5. Now extract/unpack the downloaded ROM from HERE and move the folder SonyXA-Android-One to TWRP/BACKUPS/Sony_XA/
6. Once done go to TWRP Menu and choose Restore and select SonyXA-Android-One
7. Once done go to the Reboot Menu and Choose Power OFF
8. Wait a few Mins and power on normally.
First boot can take a while but if you see the boot animation start everything should be fine so go have a brew while you wait.
Play Services will want to Update so allow that then most apps will need to be updated to the latest version.
Arrange the app icons and widgets on your Home screen and choose a nice wallpaper or live wallpaper and your done.
Hopefully everything will be quick & smooth. :fingers-crossed:
The ROM is not pre rooted so Root in the usual way using Magisk
PS: Ensure you check your app permissions and Default APPS the Phone app is Not the Default one even though it's the only one installed so please choose it Manually along with any others that do not set by themselves.
Thanks
Some Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
......
.....
.....
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
z4Android said:
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
Click to expand...
Click to collapse
Thanks. :good:
Be sure to let me know how you get on with it. :fingers-crossed:
I am not sure where you are from or which version of the XA you have but I am sure the ROM could be easily adapted for your own version.
All I would need would be a backup of your /oem & /boot partitions and the build.prop from your /system .
There is a modem config file in /oem which states telefonica uk I am unsure if this has any effect at all as I am sure I have flashed firmware from other European regions with no noticable effects.
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
z4Android said:
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
Click to expand...
Click to collapse
Hi, Your version should have no issues as it's identical to mine :good:
As for TWRP yes it does have issues with Unmounting /system for some reason
So if you mount /system from the Mount Menu TWRP or auto mount system you will not be able to Unmount mount it due to the "device or resource busy" error
If this happens you will need to ensure auto mounting is unselected and reboot to recovery from the Reboot menu.
I will look into the TWRP issue later to make things easier
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Bluesummerz said:
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Click to expand...
Click to collapse
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
bigrammy said:
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
Click to expand...
Click to collapse
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Bluesummerz said:
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Click to expand...
Click to collapse
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
bigrammy said:
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
Click to expand...
Click to collapse
And that is exactly why I like these forums, if you provide enough insight to a question, you'll get the full-spectrum answer, splendid!
And yes, confusing things is in my nature, also I might find it troublesome to know when I get like off topic here, so please stop me the moment, it would be better to switch to pm.
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
PS
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Bluesummerz said:
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Click to expand...
Click to collapse
Correct they are essentially a dd backup of the entire partition in question.
[Edit] To expand TWRP does not convert anything so if those partitions had the stock recovery & boot .elf format on them when the backup was performed they will still be .elf's which are not fastboot compatible. Those in my ROM have already been converted to .img format which is compatible with fastboot.
If you ever got stuck for some reason then you could simply use FlashTool to restore the Stock Recovery (fotakernel), Boot, OEM & System
Bluesummerz said:
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
Click to expand...
Click to collapse
Correct.
My Phone is restored using the F3111_33.3.A.1.97_1302-4476_R2B.ftf (FlashTool Firmware) and the ROM is based on this version.
Try to use a 33.3.A.1.97 if possible as I know that works.
Bluesummerz said:
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
Click to expand...
Click to collapse
Fastboot the recovery and the boot then You Simply need to follow the Flashing Instructions from step 2 in the first post from this point.
It is /data that gets wiped manually BTW (By The Way). TWRP will take care of the /system during it's restore tasks.
Bluesummerz said:
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
Click to expand...
Click to collapse
Yes providing you did everything correctly I see no reason why it would not work for you unless your device is a extra special Sony XA
Bluesummerz said:
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Click to expand...
Click to collapse
It stands for a Work In Progress.
The term work-in-progress (WIP) describes partially finished goods awaiting completion.
Does it has VOLTE support
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
altmash mirza said:
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
Click to expand...
Click to collapse
Not sure about VOLTE
If anyone did try this ROM nobody reported back
I guess this device is dead now as there seems to be very little activity which is a shame
drm fix working in case we use sony backups?
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
z4Android said:
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
Click to expand...
Click to collapse
Thanks for the feed back. :good:
Sorry no Oreo or Pie unless we fix the Ril issue on none Stock custom ROM's like the Lineage 14.1
bootlogo
bigrammy said:
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Click to expand...
Click to collapse
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Codetrr said:
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Click to expand...
Click to collapse
If your TWRP is not working you should fix this FIRST before doing anything else.
Warning: The logo partition is very important and as I said before it's part of the secure boot chain so if the logo does match the signature and or hash the ROM will boot loop or soft brick it did for me when I tried to change it so be very careful and make sure you can recover the phone with FlashTool.
To find partitions on Mediatek devices use this cmd.
Code:
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
This will give you a list of all partitions by-name and the actual dev block.
The logo partition is
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
So to flash the logo.img with dd you would copy the logo.img to your internal sdcard and use the following cmd.
Code:
dd if=/sdcard/logo.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
Sorry I cannot test your logo's because my wife use's this phone now as her everyday phone so she would not let me mess around with it now.
Akinimaginable said:
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Click to expand...
Click to collapse
The ROM is just stock ROM with most bloat ware removed and Google alternatives installed. I would recommend not to use the Sony "Album" app as it requires some other Sony apps which I removed and it continually looks for these apps. So just disable it in /settings/apps and use the pre-installed Google photos instead.
Also ensure you manually set the Phone app as the default dialer even though it's the only one or you will not be able to make or answer calls.
11 year girl! I would not worry they probably know more than we do at that age :laugh:
Yes it should be 100% compatible with a European Xperia XA F3111 ?
How to do this ?
I just rooted and flashed my old LG, and probably the by the "good" method. So if you have a link for the way to root and flash this phone, you'll make me very happy. I know that I have to go in adb flash TWRP as recovery, go in recovery by resetting the phone. Once this is done I have to wipe the phone, put the rom (and opengaps ?). And finally flash the rom. But previously I saw a lot of commands and warning so I'm a bit confused ?
Thanks for your attention ??