Related
WARNING FOR DEV ONLY AT THIS STAGE
hey all here recovery based from xd.bx but with touche screen Option and more features is just fresh and wana share it with all Galaxy S III Mini user just flash as PDA with odin but have boot only to recovery i try to flash back and report here if any one can try and feedback are good
WE have more feature
1- you can no only backup but also creat flashable.zip image and share rom with every one
2- have many option not tested just feed if have problem for all other feature just flash and see by ur self is beter than explain here
Credit
xd.bx for working CWM and config files
Me :silly:
Flyhalf205 soon make this recovery working
blackknightavalon for test
OliverG96 for tip's and also sharing his work
Now if any dev have know about why the phone boot only to recovey when i choos reboot system i have samsung gt xxxx galaxy s III mini and after recovery no boot to system why ? :good:
Dont forget is colaborate work all user here have credit
Hi,
Make sure you have both j4fs and param loaded. Mount /mnt/.lfs before loading param. Also you must patch kernel (patch is in the other thread)
For sure you're building this from the cwn builder yeah?
Wich recovery are you using as base?
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
For sure you're building this from the cwn builder yeah?
Wich recovery are you using as base?
Enviado desde mi GT-I8190 usando Tapatalk 2
Click to expand...
Click to collapse
Hi used xd.bx recovery and also grafic.c and fstab i any one can try show me dmesg (grep -i param grep -i j4fs)
this solve that issue via modifying param and j4fs drivers
Any one can flash this recovery and give me
dmesg (grep -i param grep -i j4fs) log in .txt and PM me this is for resolving the problem thank you
Flashed this via Odin. Every time I try to reboot it just reboots straight into recovery. Good first attempt, though.
blackknightavalon said:
Flashed this via Odin. Every time I try to reboot it just reboots straight into recovery. Good first attempt, though.
Click to expand...
Click to collapse
yes need fix into j4fs driver i need dmesg (grep -i param grep -i j4fs) if any one can give me this in txt format is great
Testing New Build tonight if is OK and booted normaly I post it Here ^^ waiting ... backing up .... if booted change thread from for dev to fix
some result boot only to recovery
spawk said:
some result boot only to recovery
Click to expand...
Click to collapse
Hi,
Make sure you use the kernel from my recovery and that your recovery.rc mounts /mnt/.lfs before inserting param.ko. Afaik these are the only two requirements to fix the "reboot into recovery loop" problem.
in half of February I go back to my 2nd pc it works better that the dinausaure I have between hand actuely I look has its place once the meantime if one wants to devote himself to advance the project is the welcome actualy I run pc with some hardawre lost ( no keyboard , and have big problem with java and flash
PS: why in half of february because my 2nd pc are in another country ( africa )
First of all congrats in the devs for this achievement.
I'm getting pms about people that are flashing this custom recoverys and messing their devices pretty good ,some of them thinking that this is just root!
Once you install this recoverys the device will not be be same, you will loose your warranty etc, it will always show System status As Custom!
So far there is no clear way of reverting to original status.
Also after installing custom recoverys some users end up with a soft-brick after going back to official and is not easy to the average user to bring it back to life.
Make sure you post a proper description of this files and what they will to to users devices,allot of users do not understand what this is and just flash it anyway!
Also for those devs that are working in custom recoverys ,Try to find a way of reverting the device to a proper working state and post such info,after all you know more about it that me.
People are assuming that this is like older devices that you could just flash the custom kernel to acquire root,well this aint just a custom kernel.
Regards
faria
I have briked phone by instaling rom and not this recovery this recovery don't brick any device you have bootlop to recovery now user talk about brick by installing recovery is another one just see in thread dev section and find is non complet recovery now in this thread need only i decompile recovery.img and aplying patche into boot.sh now the recovery see only 1 boot ( into recovey ) when patch are done get reovery like CWM but diferance are in touche I have used corect files now in first post we have WARRNING IN RED and also in BIG letter and the warning talk about this recovery at this stage is only for devlopper user know how to etc etc
spawk said:
I have briked phone by instaling rom and not this recovery this recovery don't brick any device you have bootlop to recovery now user talk about brick by installing recovery is another one just see in thread dev section and find is non complet recovery now in this thread need only i decompile recovery.img and aplying patche into boot.sh now the recovery see only 1 boot ( into recovey ) when patch are done get reovery like CWM but diferance are in touche I have used corect files now in first post we have WARRNING IN RED and also in BIG letter and the warning talk about this recovery at this stage is only for devlopper user know how to etc etc
Click to expand...
Click to collapse
Did you post how to backup the original recovery ? No
You really expect users to know how to recompile the recovery image!? Did you post such info? No
My statement stands.
I never said that recovery's bricked the devices,I said that it modefys the device in a manner that is causing problems.
faria said:
Did you post how to backup the original recovery ? No
You reallyexpect users to know how to recompile the recovery image!? Did you post such info? No
My statement stands.
I never said that recovery's bricked the devices,I said that it modefys the device in a manner that is causing problems.
Click to expand...
Click to collapse
I have posted original recovery yes is in dev thread and is flashable by odin here is http://forum.xda-developers.com/showthread.php?t=2093727
and I have open thread for make ONE thread with all referance to rom CWM and Tweak this is more clear when user come in forum he see first sticked thread wirh all link to tool rom custom rom but i can't make it for my bad english this need good writer
OK now I have 4 week to learen how to fix this now if any one have link explain from A to Z how to mod make compile decompile .... relative to Recovery just PM
Here is the last version at the moment of the Maze alpha ROM (tested only in 4GB version)
It's a complete ROM, not an OTA update, it can be flashed using the provided TWRP 3.2.1 version, I ported from a Jemmini (many thanks) version for Bluboo S1.
Unfortunately, the TWRP cannot be flashed (issue with the touch panel), only launched by fastboot.
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
There is also a SPFlashTool clean version of this ROM, useful in case of troubles (as official: no root, no busybox)
1- Reboot you phone in fastboot mode : adb reboot bootloader
2- Flash the provided TWRP : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3- Reboot to TWRP recovery
4- copy in your SDCARD and install, in the running TWRP, the downloaded ROM V09 : Maze_Alpha_4GB_v09_TWRP.zip
The first boot take some minutes so be patient.
Here the SPFlashTool versions :
MAZE_Alpha_4GB_V09_SPFT.zip
Here, if needed, my V09 TWRP backup (new one from 21/04/2018) :
TWRP_BACKUP_MAZE_Alpha_A_V09.zip
Credits to Jemmini and Magisk team.
Can you make this for the 6 gb version?
many thanks gonna ty it soon
Nautilus99 said:
Can you make this for the 6 gb version?
Click to expand...
Click to collapse
I do not have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
dreambo said:
I do note have the 6GB version
If I can download a stock ROM and a recent OTA update, I will do that.
Maze do not help us unfortunately
No complete stock ROM, No kernel source nothing !!!!!!!!!!
Click to expand...
Click to collapse
Yes i know its sad, i did a backup of mine and root it but it didnt work the backup i had to do clean flash, if we can manage to have a twrp and a source of the stock roms we could make a deabloat and put update apps ( menssages, calendar etc) and put mods for awsome features i dont see RR or lineage putting thier hands on this phone
Thanks for this Rom.
Is there any root for the maze alpha x?
here
WiddleyScudds said:
Is there any root for the maze alpha x?
Click to expand...
Click to collapse
read
The ROM is the same as the v8 official one except that it is rooted using Magisk 15.2 and busybox 1.27.2 (thanks to osm0sis) is installed in /system/xbin
Click to expand...
Click to collapse
thorfr said:
read
Click to expand...
Click to collapse
I have an alpha x, not alpha.
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
rzoli71 said:
Thanks for ROM
When I install this ROM, from TWRP, i need install anything for root (Supersu)? Or when I install this ROM, I have root?
Click to expand...
Click to collapse
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
thank you
After I installed this rom, and freezed the hot knot, baidu_location FM Radio, etc, the BT connection did not break.
dreambo said:
No it is already rooted.
Reboot your phone to android, and then install MagsikManager.apk
I am editing my post to give you a 100% working TWRP 3.2.1 for our beloved Maze Alpha 4G :victory:
Click to expand...
Click to collapse
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
ahorntaler said:
Hi dreambo,
do You know if there's a stock rom for download from maze alpha x? I think it's important for normal users and developers to get one. For normal users it's important to have an option to reinstall stock version and for developers I think it's the source for custom roms (e.g. Lineage Os).
If You know a source, can You please give us a link?
Click to expand...
Click to collapse
No I not have any source, I am just a simple user like any other.
If I have any source or if I can make a ROM for MAZE Alpha X, I will do it and I will share it with every body, as I do until now for the MAZE Alpha 4/64
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
iBolitN said:
Hi
Sorry for stupid question, but is flashing with SP Flashtool an option to get root without wiping all data (unlike all other methods involving bootloader unlocking)?
Click to expand...
Click to collapse
Unfortunatly no. As you will see repeated times in the forum, people have issue with phone not booting after changing from stock recovery to twrp. This is do (most likely from) to verified boot setting. And by unlocking bootloader we can bypass verified boot. So without unlock you might get a successfull load into twrp, but android will not boot.
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
stargazer78 said:
Hello to all and please help if you can.
After unlocking the bootloader and flash the rom I'v got orange state with bootloop. Then after trying to fix it (wrong way) and relock bootloader and got red state with bootloop. I read that flahing back to stock fix the problem but I have no success with the rom provided in this post, the v5 from maze, the latest flash tool and the maze alpha flash tool... in all cases I get DA error(maze flash tool) or DA MISHMATCH (sp flash tool). I also tried different pc and cable with no result and finaly can't get fastboot. If that helps I've got the same flash tool error before the procedure. Every help will be appreciated.
Click to expand...
Click to collapse
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Thanks a lot for your reply....
the problem is that i cant boot into fastboot to unlock bootloader....
the phone bootloops all the time, shows the red state alert and even with vol+ pressed the menu to choose recovery or fastboot doesn't apear... thanks again.
dreambo said:
First unlock again your bootloader and use fastboot to flash boot, recovery and system partitions:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.
Those partition images can be found in the ROM for SPFlashTool I have provide.
After that you can boot android normally.
If you any TWRP backup, you can restore it after flashing the TWRP.
Click to expand...
Click to collapse
Is there any way to unlock the bootloader in my situation or/and enter the fastboot mode in order to follow your steps... thanks.
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 ??
https://mega.nz/folder/spBwXZoL#D1Wf8xLl1WacstfVnLnKhA
Any chance of some info on how to install?
TYIA.
what is this
Can you give a bit more details where you got this? Did you compile it? Was it pulled from another sony device? Do you have a github link?
Once again @M-Rom ! First TWRP for the Xperia 2019 Flagships and now the 2020 Series...
Same as for the Xperia 1 II:
-Download and extract the ZIP File to Your fastboot Location and rename it to recovery.img (for ease use)
-Use:
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
-Disconnect Your Device from USB and wait for it to turn off
-Press and hold VolumeDOWN & the Power Button together until You see the TWRP Logo (or use the reboot recovery option)
Miustone said:
Once again @M-Rom ! First TWRP for the Xperia 2019 Flagships and now the 2020 Series. Guide:
-Download and extract the ZIP
-Rename the file inside to boot.img
-fastboot flash boot_a boot.img
-fastboot flash boot_b boot.img
-Disconnect from USB and wait for the Device to run off
-Press and hold VolumeDOWN together with the Power Button
-TWRP should Start (in Chinese again!? lol)
Happy testing!
You can join My Discord Server if You need help with that... Ask Jayram which has successfully booted and used TWRP on his Xperia 5 II
MOD EDIT: Link removed, please read the STICKY!
Click to expand...
Click to collapse
Tried these steps and it worked perfectly, it is in chinese by default.
Updated My Instructions since 2020 Xperia Devices have a seperated recovery partition against the boot image/ramdisk ones on the older Devices. That's a huge win for Android Devices! Happy flashing Dear MARK II Users!
This installs successfuly, but it's kind of useless with the storage encryption. I tried wiping, but after restarting the device it becomes encrypted again. You need to change the language every time too. Is there any way to keep the internal storage decrypted? like the disabler .zip for samsung devices?
palamosteliaro said:
This installs successfuly, but it's kind of useless with the storage encryption. I tried wiping, but after restarting the device it becomes encrypted again. You need to change the language every time too. Is there any way to keep the internal storage decrypted? like the disabler .zip for samsung devices?
Click to expand...
Click to collapse
Doesn't TWRP support decrypting? On my previous devices it wasn't a problem, I never had an urge to decrypt the device.
Nezorflame said:
Doesn't TWRP support decrypting? On my previous devices it wasn't a problem, I never had an urge to decrypt the device.
Click to expand...
Click to collapse
Different TWRPs support different features. To get this one to support decrypting it will have to be worked on by the dev.
Unfortunately the internal storage decryption is broken since the December security patch update (58.0.A.28.51)...
OhayouBaka said:
Unfortunately the internal storage decryption is broken since the December security patch update (58.0.A.28.51)...
Click to expand...
Click to collapse
I recently got a 5 ii, currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification. Should I not update if I want root?
mtshure said:
I recently got a 5 ii, currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification. Should I not update if I want root?
Click to expand...
Click to collapse
You can still update if you want root via Magisk, but you will need to patch the boot img instead of flashing the Magisk zip in TWRP.
That would be soooo great to get TWRP or OrangeFox for Xperia 5 ii turning on Android 12!
Yoannjap said:
That would be soooo great to get TWRP or OrangeFox for Xperia 5 ii turning on Android 12!
Click to expand...
Click to collapse
Soon
King081 said:
Soon
Click to expand...
Click to collapse
No... Really?
But untill when could we hope for that?
Whoever is trying to adapt OrangeFox for X5ii_A12... Thanks a million!
Yoannjap said:
No... Really?
But untill when could we hope for that?
Whoever is trying to adapt OrangeFox for X5ii_A12... Thanks a million!
Click to expand...
Click to collapse
Yeah I'm being serious, we have it in private testing currently
Can somebody please confirm both recoveries (twrp / orangefox) currently available for (x5ii / pdx206 / XQ-AS52) only work on android 11 or prior? I tried both and they bootloop.
go0 said:
Can somebody please confirm both recoveries (twrp / orangefox) currently available for (x5ii / pdx206 / XQ-AS52) only work on android 11 or prior? I tried both and they bootloop.
Click to expand...
Click to collapse
Yes it will not work, new one will be out real soon
m
View attachment 5472077
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
FLASHING GUIDE
you must need to unlock your bootloader
Click to expand...
Click to collapse
1. adb reboot bootloader
3. fastboot flash boot twrpname.img
4. fastboot reboot recovery
note! will ask a password to decrypt or to see internal storage just put the password (optional if your device have a password or pattern,pin)
5. flash magisk-v23.0.zip (optional)
6. then reboot system. done!!
Click to expand...
Click to collapse
INFORMATION!
- device is shipped as android 11 , and device don't have recovery partition meaning its virtual A/B its use recovery as boot check here (for more info)
NOTE FOR FLASHING!!
- If you face wifi Problem use twrp_a or twrp_b .
- If you want to root your device flash magisk already included in *.zip (Don't use official one because you will face bootloop)
DOWNLOAD
download twrp_a
download twrp_b
MAGISK FOR ROOTING
credits: to topjohnwu
DOWNLOAD MAGISK
WHAT WORKING ?
- Decryption
- flashing payload.pin / recovery rom (note! if you want to flash rom or modify your device just back up your imei please)
- fastbootd
- etc.
- for the bug just tell me.
DEVICE TREE
DEVICE KERNEL SOURCE
CREDITS
- TEAM WIN FOR RECOVERY
- TESTER'S FROM INDONESIA
- TOPJOHNWU for magisk
- @osm0sis for the A/B installer script
BUILD BY:
t.me/myusernameiswhat @mastersenpai05)
link of b not working
Abdullah.Csit said:
link of b not working
Click to expand...
Click to collapse
Done sir
thanks!
Thanks sir. Does it only need unlocking bootloader? Doesnt need mi unlocking?
How we can determine which (a or b) twrp should be used?
symbuzzer said:
Thanks sir. Does it only need unlocking bootloader? Doesnt need mi unlocking?
How we can determine which (a or b) twrp should be used?
Click to expand...
Click to collapse
If you got unlocked bootloader device then you ready to go.
try "a" if you got wifi issues then use "b".
symbuzzer said:
Thanks sir. Does it only need unlocking bootloader? Doesnt need mi unlocking?
How we can determine which (a or b) twrp should be used?
Click to expand...
Click to collapse
You need tool to unlock your bootloader, you can use a mi unlock tool you need to wait 7days, or if you want to unlock that instantly you need other tool
TWRP will be updated after I successfully done my experiment
is just need flash a or b anyone is ok ? or need flash both ?
How to backup imei?
Is there any way to flash TWRP permanently?
"With the new TWRP 3.6.0, things will be a little different. After you temporarily boot the TWRP image using the ‘Fastboot boot’ command, you will be able to see a Flash Current TWRP in the Advanced section of custom recovery."
Is this working?
symbuzzer said:
How to backup imei?
Is there any way to flash TWRP permanently?
"With the new TWRP 3.6.0, things will be a little different. After you temporarily boot the TWRP image using the ‘Fastboot boot’ command, you will be able to see a Flash Current TWRP in the Advanced section of custom recovery."
Is this working?
Click to expand...
Click to collapse
Will not
why not?
Hi. Thanks for the development
I have a question. Assuming that I've flashed this twrp, how do I properly backup the entire phone, I mean which one will be selected in backup option . I want to flash some custom roms and restore the created backup if something goes wrong
09kkthxbb said:
Hi. Thanks for the development
I have a question. Assuming that I've flashed this twrp, how do I properly backup the entire phone, I mean which one will be selected in backup option . I want to flash some custom roms and restore the created backup if something goes wrong
Click to expand...
Click to collapse
NO advisable, Do not try this way!
I have a bad experience with this method, I have a Note 8 pro (Begonia), i did a rom backup with twrp, then flashed other custom roms, after few tested on various roms, i decided to get back to Miui rom, thinking of the easy way, I restored its Miui backup images via twrp, the phone bricked. In the end, I had to sent to xiaomi service center for repair.
I believe that was due to different version of Preloader of rom crashed with TWRP.
Of course, with some "MTK auth bypass softwares" available today, you may take the risk if you wish.
Could anyone provide here any already backup of Chopin stock recovery share it here, please?
Edit: Since there is no recovery partition, You had just re-flashing "boot.img" by twrp then you will restore stock recovery and that operation will also let you lose your root.
Is this compatible with x3 gt global 12.5.7 update?
koolkattt said:
Is this compatible with x3 gt global 12.5.7 update?
Click to expand...
Click to collapse
Hi man, we tried this as well.
We rollback to the old version for now just to have a working root access.
являетсяIs there any localized firmware on this device? will they?
koolkattt said:
Is this compatible with x3 gt global 12.5.7 update?
Click to expand...
Click to collapse
Sure, im runnign this version and works good with magisk
folken2003 said:
Sure, im runnign this version and works good with magisk
Click to expand...
Click to collapse
how to make work? I try many way also bootloop, can share step by step to success ? thanks