Related
RETIRED! No longer supported or being developed. @Giovix92 is now the lead dev, please use his TWRP for full compatibility with modern kernels/ROM's - https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
Old thread below:
-----------------------------------
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing, Dual boot repartitioning and other power-user tools with integrated Aroma Installer-powered GUI screens that I call Tissot Manager.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know!. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready with dual-boot ROM patcher;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Option to install a payload ROM in the current slot, rather than the inactive one;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Adds a "Tissot Manager" Aroma GUI to TWRP Advanced Menu (bottom-right button), which is the tool used to repartition the device for Treble and Dual boot, as well as some other nifty stuff:
Has the option to shrink System OR Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink System, you will keep max size Userdata - however it will be incompatible with non-Treble ROM's (they will crash on installing with Error 28 due to System being too small). It will Erase system, requiring you to reinstall a ROM or restore a ROM backup.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Dual boot requires Userdata shrink and works by splitting into userdata_a and userdata_b. The partition split size is customizable during the repartition process.
Adds a "Patches" section with the following current options:
Patch the current Vendor for dual-boot capability (only required if automatic patching wasn't possible). See the 'About Dual-boot' section below for more information.
Enable an insecure ADBD on boot for the current slot (i.e. enable debugging and remove authentication requirement). Useful for ROM hackers/porters.
Patch the current slot to enable/disable forced userdata encryption
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-boot.img-3.2.1-with-Tissot-Manager-x.x.zip:
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches (Aroma Installer powered GUI - a fully guided and interactive process).
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack. Reminder - check out my full guide for learning and instructions on all things Treble.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
About Dual-boot
Dual-boot on this device is relatively simple. As you know we have Slots - boot_a and _b, system_a and _b and vendor_a and _b (for Treble). This repartition splits userdata into userdata_a and _b too. You can simply change your Slot in TWRP reboot menu to change which ROM to boot.
This is designed for developers and testers - NOT for daily use. There are some significant issues with dual boot systems:
Any kind of security lock (PIN, fingerprint, etc.) set on one ROM will cause the other ROM to believe it has security too, but constantly fail with unlocking. This is reportedly because security info is stored on persist, which is shared between each slot (and not compatible with differing ROM's).
Because Userdata is split, so is Internal Storage. In TWRP, when changing slots, the MTP will remain mounted to the old slot - it must be manually disabled and renabled (Mounts menu) to update to the new slot.
I will not fix these issues - dual-boot is not designed to be for general/daily use and there may be more minor issues that I don't know about. It's intended for developers only.
In order for a ROM to be dual-boot compatible, the fstab file (information given to Android about partitions to mount) needs a small modification. This TWRP can try to do this patching automatically when you install a ROM, or it can be done manually in Tissot Manager's Patches menu (as well as single-boot patch to e.g. revert a ROM backup from a dual-boot state).
You will see in the install log if a dual-boot patch attempt is successful in the flash text output.
Automatic dual-boot patch occurs only if necessary when:
Flashing an AIO Treble ROM ZIP with TWRP
Flashing a vendor.img in TWRP "Install Image" mode
Automatic dual-boot patch does NOT work when:
Flashing a vendor.img via fastboot
Restoring vendor in a TWRP backup
Any other way of flashing a vendor
In any of these cases, you can manually patch Vendor for Dual Boot in Tissot Manager's Patches menu. You can also remove dualboot support the same way. It will detect the dualboot state of the current Vendor slot and present the available option. If you find that it doesn't actually change after patching, the Vendor is incompatible (please report it to me). RR AIO Vendor is tested OK.
Download
All downloads (and source code) always at:
https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
...or via DevBB Downloads section.
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/CosmicDan-Android/android_system_update_engine_tissotmanager-mod
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk. The void kernel included in RR AIO does not have this problem and can therefore be safely used without Magisk (for e.g. GSI compatibility).
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work. It will definitely not work if you have shrunk system.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ROM ZIPs with a shrunk System (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Credits and Thanks
- @mohancm for the original TWRP port, I used some flags from his DT
- @ghpranav and @mountaserhalak for the RR device tree that this is built with (and random help)
XDA:DevDB Information
TWRP with Tissot Manager (Treble & Dual boot support), Tool/Utility for the Xiaomi Mi A1
Contributors
CosmicDan
Source Code: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot
Version Information
Status: Stable
Created 2018-05-29
Last Updated 2019-11-24
Reserved
Screenshots (click for slightly larger non-cropped version)
Screenshot of new TWRP button:
_______________
Main menu (stock partition map detected):
_______________
Repartition choice type when coming from stock:
_______________
Repartition wipe warning/disclaimer if chosing to shrink Userdata for Treble:
_______________
Main menu (Shrunk Userdata type Treble partition map detected):
_______________
Repartition wipe warning/disclaimer if chosing to restore Stock from Shrunk Userdata Treble mode:
_______________
Example of Repartition processing screen:
Good job! :good:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Omg, you are the best man. @mohancm also huge thanks to u man, great devs in our XDA.
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Chikoow1 said:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Click to expand...
Click to collapse
This is just the repartition part, one step of Treble. You still need a Vendor pack. But yes, this enables Treble ROMs and the ROMs require repartition.
ddaggebi said:
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Click to expand...
Click to collapse
1. If you do, it will wipe partition map back to stock. So you will need to repartition with Treble Manager TWRP again. But you can make a backup of stock ROM in TWRP and just restore it after the repartition. It should work.
2. Don't know. Needs testing.
3. Yes! I forgot to add this to the FAQ.
Has this tpwr f2fs support and working?
Since Los support It i would like ti have
@CosmicDan
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Filip013;76586434 [user=1844875 said:
@CosmicDan[/user]
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Click to expand...
Click to collapse
It's indeed not intended to be compatible with stock ROM, but your mileage may vary, and as @CosmicDan said, it might work good enough or it won't. You can only try to see the results yourself.
This whole Treble thing is meant mainly for custom ROMS, since stock will never be Treble compatible (still, anything could happen)
I've just updated the TWRP with Treble Manager to 1.1 which fixed a semi-important bug.
Also, I've released a guide for those who find the Treble conversion/install process confusing - check it out. If you can, keep TWRP and Treble Manager specific questions in this thread, but ask your general questions and help over there - I will update the guide as I get feedback
CosmicDan said:
FAQ
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) Untested. Please report your results. But Treble is really not about Stock, you will likely encounter more problems down the line or it may turn out to be completely incompatible.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest/only way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (untested - if you get bootloop when using stock, it means you do) or Magisk (also untested, may still get bootloop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ZIP's on ROM's with a shrunk Userdata (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Unable to mount '/vendor' (Invalid argument)" red error in this TWRP
A) You can safely ignore it. It just means you have not repartitioned your device for Treble yet, so it can't mount the /vendor image.
Click to expand...
Click to collapse
Ay!
Have just finished testing about OTA on stock after Treblizing!
Result?!?
OTA works perfectly on stock after shrinking data to Treblize! Hurrah! ???
Process I followed:
1) Treblize by shrinking data
2) This is important: flash stock ROM in fastboot using MiFlash! When flashing for the first time, select "clean all and lock"! No other standard options working! I couldn't even boot stock using other options!
I've tested by fastboot flashing April build and then updating it to May OTA!
*** On a note: clean all will erase everything on your phone including your personal data!
If you use "save user data" then stock can't even boot! This may caused by the encryption!
BTW, after everything I just restored my non-Treble RR backup and everything works perfect! Just Treble Check app can't check that it's Treblized!
But don't worry! Treble partition table still remains! Fastboot flash can't touch that and can't recognize that it actually exists! Which to me is a good thing!
@CosmicDan, give me a thanks buddy! I deserve this!
SomratMJX said:
-snip-
Click to expand...
Click to collapse
Don't quote the whole OP and please use a smaller font size.
Change slot doesn't work... Others are okay as far as i have seen
dback31 said:
Don't quote the whole OP and please use a smaller font size.
Click to expand...
Click to collapse
Just thought it's too important to highlight! Nothing else!
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Reboot to fastboot and change the slots with
fastboot set_active b
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Use the latest TWRP 1.1! Works fine for me!
SomratMJX said:
Just thought it's too important to highlight! Nothing else!
Click to expand...
Click to collapse
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
dback31 said:
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
Click to expand...
Click to collapse
Ha ha ha! It's related to OP buddy!
Anyways, I am too lazy to quote a certain part of the OP!
This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now
iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.
Great work guys!! Waiting for vendor partition, for some tests!
Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.
fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition
can i flash android q gsi images using treble recovery.
Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.
Can i flash android Q gsi image using this recovery on ze520kl
About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
Note: This guide is for users who have already flashed custom ROMs (not necessarily GSI) to their phone. If you're new to this or are coming from any MIUI ROM, please see other tutorials.
Click to expand...
Click to collapse
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).
Has someone tried oui ??
Great guide! Thanks a lot, your way was the only way I could get a treble rom working on the device! I wasn't able to flash the vendor in fastboot coming from miui 10.2.2.0, but it worked from twrp. Now got Havoc booted successfully
has anyone tried q gsi?
xeodm said:
has anyone tried q gsi?
Click to expand...
Click to collapse
If you want to use it, try it out. There's no reason it shouldn't work ?
Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!
djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
I'm going to try it later. I will update if it works.
djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
Unfortunately, it doesn't boot. I want to try it too !
salahmed said:
Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!
Click to expand...
Click to collapse
I remember someone saying u need to use permissiver 3 or 4
gsser said:
I remember someone saying u need to use permissiver 3 or 4
Click to expand...
Click to collapse
Do you have a link?
Regards
salahmed said:
Do you have a link?
Regards
Click to expand...
Click to collapse
I dont have any unfortunately, it might be in erfano's telegram group or mix 2 aosp group.
I'm Stuck Help!
I'm stuck on AOSP EX Boot Animation, What to do now?
I did all right!!
Why is this happening
Fix for the audio problem
andythedev said:
About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).
Click to expand...
Click to collapse
https://github.com/hmuny99/GsiSystemAudioFix
Use this flashable zip to fix the audio stuttering issue.
Someone tried it with the Q GSI's from Erfan? I can't get it to work....
pattagalix said:
Someone tried it with the Q GSI's from Erfan? I can't get it to work....
Click to expand...
Click to collapse
Not with Efran's gsi's but I've tried a few times on other 10's and had no luck on my end. I Used the 10 gsi Aonly 64 bit and I've formatted data and decrypted using Zach's force encrypt removal zip and magisk su zip and I've tried without removing encryption and no luck. It hangs on mi boot logo every time. I saw a DerpFest gsi on telegram that's when this whole gsi mission began for me. lol. Maybe we need a different boot.img and vendor.img for 10 idk? ? I tried with and without flashing the boot and vendor, decrypt and not decrypt and no go. ?
Sent from my moto g(7) power using XDA Labs
I booted RR v7.03 from Luke's GSI thread using vendor and boot in op but tried a few more 10 GSIs and they either hang on mi screen or bootloop forever. This RR is bad ass!! V7.03 wasn't made for Chiron and blows 7.02 off the map. Although security patch is from November 2019 I'm going to rock it a while. Sure will miss RR now that main dev stopped. Talk about a bad ass ROM!!! If anyone wants to use it its here. Just click the top link and you'll see the A only 64
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
We all know flashing ROMs got a lot more complicated with the advent of A/B partitions.
This is not my work, the aim here is only to highlight a process which simplifies the task.
Original post on the OnePlus 6 forum can be found here:
https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
It makes use of a script which copies the flashed firmware to both slots without having to reboot recovery and do it a second time. Also by not having to reboot recovery you avoid the issue where internal storage becomes unreadable.
Credit for this goes to:
LineageOS @erfanoabdi @filipepferraz @Prakyy @drpradsms
Download by prakky (hit the thanks button on his post below):
https://androidfilehost.com/?fid=8889791610682890605
The following posts detail it's usage which you follow at your own risk.
Clean Flashing a new ROM
Disable lockscreen security
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Format data; type 'yes' (backup as this wipes phone)
6) Boot System
Reboot recovery to flash additional zips.
Updating OOS base whilst on a custom ROM
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Boot System
Reboot recovery to flash additional zips.
Updating a custom ROM (nothing fancy here)
Boot TWRP 3.4+
1) Flash ROM
2) Flash TWRP installer
3) Boot System
Reboot recovery to flash additional zips.
Reverting to OOS
WARNING I've yet to test this!
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash Finalize.zip
3) Format data; type 'yes' (backup as this wipes phone)
4) Boot System
Note: this will revert you to stock recovery as well.
Tip:
Chain install the zips by selecting 'Add more Zips' after selecting the first zip.
Only 'Swipe to confirm Flash' once all zips have been queued.
I recommend numbering the zips in the order they need flashed.
Note: this issue is now resolved as of 09/08/20 as per https://forum.xda-developers.com/oneplus-6t/how-to/guide-rom-flashing-easy-t4143701/post83241857
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Deleted. Think maybe I'm getting altimeters. ?
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Edited first post to make it clearer this is your work.
mitchst2 said:
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Click to expand...
Click to collapse
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Prakyy said:
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Click to expand...
Click to collapse
Good question.
Is 'Android Development and Hacking / General' the right place? There are some all device guides with a lot of views in there.
https://forum.xda-developers.com/android/general
mitchst2 said:
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Click to expand...
Click to collapse
As of 09/08/20 build and this commit all is well with OMNI and TWRP again. No need to edit the ROM zip anymore.
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
brajesh.sharma87 said:
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
Click to expand...
Click to collapse
No when switching ROM formatting data will be necessary. Not used it myself but others recommend Migrate to restore apps and data.
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
brajesh.sharma87 said:
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
Click to expand...
Click to collapse
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
flash713 said:
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
Click to expand...
Click to collapse
I had to mandatory format data when I wanted to move from evolution x to aospa.
brajesh.sharma87 said:
I had to mandatory format data when I wanted to move from evolution x to aospa.
Click to expand...
Click to collapse
And I've also had to format data before as well but not lately. Could it be because I format both slots coming from OOS or because I use Canary Magisk or the recovery I use.. No idea but next time you are on EvoX backup system, data and boot and try and restore it using that recovery that comes with EvoX and see what happens. These last few weeks I've stayed on AOSiP and PixeN and I flashed Omni once I think but restoring from AOSPA to Pixen was flawless for me and also restoring Pixen to Pixen was also fine, which I do because I always mess around with sound mods.... I'm on AOSiP now and soon as I get more charge on my phone I'm going to try and restore to something I have a backup already made on one of my USB drives and I'll edit this post and report what the outcome is...
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.