Database Info

[GUIDE] [Q&A] [TREBLE] From Stock to Treble - everything you need to know!

Here I will share all the info you need to know about using Treble on the Mi A1. Everyone is more than welcome to ask questions and clarification here, I am happy to answer and will update this thread over time. Thanks!
Contents
0. Key Terms
1. Restoring to Stock
-- 1.1. Requirements
-- 1.2. Full-device backup
-- 1.3. Stock restore process
2. "Treblize" (repartition) the device
3. Your first Treble ROM install
4. Installing AIO's, GSI's, Vendors and More
-- 4.1. Install a Treble AIO
-- 4.2. Install a Treble GSI
-- 4.3. Install/update a Vendor Pack
-- 4.4. Install a non-Treble ROM
-- 4.5. Restore a TWRP backup
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
6. FAQ and Troubleshooting
----------------------------------------------
0. Key Terms
Throughout your Treble adventures, you may see lots of new terms. Here I will explain them all. This is essential reading!
Treble
Treble is the broad term of a new Android architecture model of splitting the system into two partitions:
System: where the Android OS goes, i.e. Oreo or later operating system;
Vendor, where the device-specific files go, such as drivers.
Before Treble, both the Android OS and device-specific files would live together on system. See below for a more detailed description of Vendor.
"Treblizing"
May also be called Treble-enable, Treble-conversion or some variation of that. This is the process of converting a non-Treble device to a Treble-capable one, unofficially, by changing the partition map of the device. This involves shrinking an existing partition - such as userdata or system in the case of the Mi A1 - in order to create a new vendor partition - or two vendor partition in the case for our Mi A1, one for each slot. Treblizing is just the preparation stage - you still need an AIO installation (see AIO below) before you are actually able to use a Treble ROM.
Vendor
Also known as Vendor Pack or Vendor Image. In the context of Treble, this is a standalone vendor image (either as a ZIP or usually as an IMG) that can be flashed to your Treble-enabled device for it to be compatible with a Treble system/ROM. These are similar to a kernel in the way that they are flashed to their own partition on your device and are compatible with many Treble ROM's. They are also similar to a kernel in that they are made specifically for one device to provide the low-level functionality of the system. It mostly includes drivers, but can also include apps and overlays that are automatically added at runtime to the Android OS that's living on System.
Treble developers for the Mi A1 may release standalone "vendor.img" for use on other ROM's - usually GSI's (see description of GSI below) but they are also part of an AIO (see description of AIO below).
GSI
Stands for "Generic System Image". This concept, introduced and developed by @phhusson is the creation of a System image that is device-agnostic - that is, it is a ROM that is designed to work with an existing Treble device, as long as the device has a GSI-compatible Vendor and kernel installation. For devices with official Treble support, phhusson makes the effort to try and adapt his GSI system for compatibility - but for unofficial Treble device like the Mi A1, it's our (tissot developers) responsibility to make a Vendor/Kernel that is as GSI-compatible as possible.
AIO
Stands for "All In One". This is a Treble firmware that includes a Kernel, System and Vendor image in the one ROM ZIP. This provides an all-in-one Treble experience through a device-specific Treble ROM. AIO's are designed to work well with their own ROM but should also strive to be compatible with a GSI.
An explanatory chart of Key Terms
{
"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"
}
Click here for full size image.
Ignore this spoiler (coded link to thumbnail because XDA thread edit breaks the IMG link)
Code:
https://img.xda-cdn.com/ic22y2zu5yi9EClrY11FS8FU5C0=/https%3A%2F%2Fimg.xda-cdn.com%2FU8u8IdA66PAFHOM4PsKNQbFHwSA%3D%2Fhttps%253A%252F%252Fimg.xda-cdn.com%252Fo1fMEJDyu5x7pv2B9KB323i8_IA%253D%252Fhttps%25253A%25252F%25252Fthumbs2.imgbox.com%25252Fd7%25252Fc2%25252FDxa93pOz_t.png
----------------------------------------------
1. Restoring to Stock
For the sake of consistency, I highly recommend everybody revert to a clean stock state. This ensures that as many of us are coming from the same place to eliminate inconsistency with reported bugs. If you're impatient or experienced though, feel free to skip this - but if you have issues, be sure to try again from here before asking for help.
Note that this will also restore you to the stock partition map, i.e. before "Treblizing".
1.1. Requirements
Unlocked bootloader and EDL access/drivers. See FAQ at bottom of this post for details on EDL.
Modern fastboot binary - it needs the "--set-active" option. Check with fastboot --help to see if it's listed in the usage.
Latest/recent official firmware package. Recommended "V.9.5.10.0.ODHMIFA" only because it's what I used, if you're not sure - but anything newer should be fine too.
Recent MiFlash version. I used 7.4.25 which can be downloaded from here.
1.2. Full-device backup
HIGHLY RECOMMENDED. While all this is relatively safe (as safe as device modding can be), I cannot be held responsible for any data loss or bricks. You can make a Low-Level backup with my tool here. You can use the "skip-systems-and-userdata" partition list to save time, since those can be backed up in TWRP anyway. This is here mostly as a failsafe.
Also backup your internal storage files. The Treblizing process may wipe your internal storage.
1.3. Stock restore process
Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Optional: If Wifi is broken (you can check by booting ROM), flash the "tissot_images_V.9.5.10.0.ODHMIFA___persist-only" in MiFlash under EDL, attached. Just extract the ZIP and browse to the folder in MiFlash. You can replace the persist.img from official V.9.5.10.0.ODHMIFA or another ROM if you want to be sure it's genuine. Credits to @AlexAiS for discovering this.
Remember - you backed up your original persist.img in step 1 anyway, so this is not risky.
I am not sure how this works exactly. It seems MiFlash in EDL is able to re-build a MAC address while flashing the persist. I don't know where this MAC comes from though.
----------------------------------------------
2. "Treblize" (repartition) the device
If you looked at the chart, you'll know that this is just the first step. You will need to actually install an AIO ROM after this part. This is a ONE TIME PROCESS for getting Treble capability on your device.
Repartitioning is relatively painless ever since I created TWRP with Treble Manager. Read on for a walkthrough.
Fastboot boot to TWRP with mohancm's recovery img (i.e. recovery-3.2.1-1) if you don't already have TWRP installed. Do not get the installer - we're using the one with Treble Manager instead.
Install the latest TWRP with Treble Manager (v1.2 at time of writing, but of course latest version is best) then Reboot Recovery to actually load it. Be sure to read about TWRP with Treble Manager in that thread to understand how it works. If you have any questions specifically about the TWRP and Treble Manager, please ask in that thread.
Format Data in Wipe menu (to remove Stock encryption), then Reboot Recovery again (maybe not necessary but it can't hurt).
In TWRP, go to Advanced > Treble Manager and repartition the device by following the wizard. Userdata shrink is recommended, as per the in-menu description explaining this. Just try the Treble Manager and see yourself - it will ask you one last time before repartitioning so don't worry about it wiping without warning. Alternatively, you can just check the screenshots.
After finished it will reboot TWRP. You are now ready for installing a Treble AIO (and then a GSI, if desired), but be sure to still read on, especially the next section below (there is a known issue that you need to work around - otherwise a bootloop will occur).
----------------------------------------------
3. Your first Treble ROM install
THERE IS AN IMPORTANT STEP THAT MUST BE FOLLOWED HERE WHEN INSTALLING YOUR FIRST TREBLE ROM. FAILURE TO FOLLOW THESE INSTRUCTIONS WILL RESULT IN A BOOTLOOP.
Make a note of the current slot (in Reboot menu). If you followed this guide from Section 1, you should be in Slot A. If you're not, just swap any mention of Slot A and B in these steps.
Download a Treble AIO ROM (such as RR Treble Experimental) and flash in TWRP. This is required even if you want to use a GSI, since it has the required Vendor Pack and Kernel.
Immediately install TWRP with Treble Manager again, as you usually do, to re-inject TWRP into the new ROM boot image.
Reboot Recovery, NOT SYSTEM.
Confirm in Reboot menu that the device has successfully switched to Slot B. If it is still stuck in Slot A, this is a one-time bug that must be solved now - if you do not fix this then you will just bootloop.
If it is still stuck in Slot A, you must reboot to fastboot (make sure you have a current version, as explained in Section 1.1. "Requirements") and manually run the command:
Code:
fastboot --set-active=b
...after doing this once, slot switching should work fine in TWRP again. You should never have to do this again (unless you go back to stock then re-Treblize again).
In case you didn't know, all ROMs for our Seamless device actually install into the *other* slot that isn't currently active - that's why you always need to Reboot Recovery first before installing Magisk or Gapps and such.
I advise users from now on to keep an eye on their Slot switching whenever you install an AIO ROM to make sure it worked. If it happens again after these steps, please report it to me with as much details as possible (we're still trying to figure out this bug).
After following these steps, you should be able to flash Treble ROM's just as you would a normal ROM from now on. Your Treble transformation is complete. But read on for more help and walkthroughs if you need it.
----------------------------------------------
4. Installing AIO's, GSI's, Vendors and More
Assuming you followed Section 3 above, you are now ready to install anything as usual. But some users have expressed confusion about what they can and can't do from this point, so I will give you some example choices here.
4.1. Install a Treble AIO
At the time of writing this guide, currently the only Treble AIO is the RR Experimental build. If or when others come along, you can just install them like normal ROMs. We already did this in Section 3 above, but here is a simplified summary of that process:
Flash the AIO ROM in TWRP with Treble Manager 1.2+ - do NOT reboot
Immediately reflash TWRP with Treble Manager 1.2+ so you get the Treble-compatible TWRP back
Factory Reset if it's a different ROM, as you usually would in this case.
Make a note of which slot you are on right now
Reboot recovery
Make sure your device has now swapped to the other slot by checking the reboot menu. If it has not, you will need to repeat the fastboot --set=active step as explained in Section 3. (I don't know if this is necessary again - but I just want to warn users to be aware of this known bug)
Now that the slot has changed, you can install Gapps, Magisk and/or whatever other compatible additional mods you want.
4.2. Install a Treble GSI
You may remember from earlier that the Treble GSI's are just System images that use your existing Vendor and Kernel. We already have a Treble kernel and Vendor from an AIO (Section 3 or Section 4.1. above), so this is quite simple:
Download any GSI/Phh-Treble ROM's from the Treble-Enabled Device Development section and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Flash the IMG to "System Image" in TWRP with Treble Manager 1.2+
Factory Reset if you're changing ROM's
Install any other mods (Gapps, GSI-compatible Magisk [i.e. 16.4 beta or later], etc.). You may need to boot the ROM once before installing any mods - this varies per GSI. Some existing mods may also be outright incompatible with the GSI.
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP or Reboot Recovery.
4.3. Install/update a Vendor Pack
While you're on a current and working AIO or GSI slot, you can flash a vendor.img to update the driver/device level stuff for that ROM. This could be done to e.g. fix the Camera. This is useful if you're running a GSI.
Download a vendor.img from your AIO or Vendor Pack provider (e.g. RR AIO Experimental) and copy the IMG to device
Make sure your current slot is a Treble ROM slot (i.e. existing AIO or GSI working). Unlike AIO/ROM ZIP flashing, image flashing installs it to the CURRENT slot.
Optionally make a TWRP backup of Vendor (or more) if you want to be careful and it's your daily (I always do).
Flash the IMG to "Vendor Image" in TWRP with Treble Manager 1.2+
Reboot
Note that since this is only a System image, there is no need to reinstall TWRP, Reboot Recovery or install any Mods (Gapps, Magisk, etc) UNLESS it's a Vendor mod (as of time of writing, no Vendor mods exist yet).
4.4. Install a non-Treble ROM
This is simple, same as you're used to before Treblizing. But do note that this is only possible if you chose to resize Userdata when repartitiong with Treble Manager.
Download the ROM to your device
Optional - make sure the active slot is one with a Treble AIO/GSI ROM already - remember that ROM ZIPs install to the OTHER slot, not the currently active one; so this way you can easily switch back to the Treble ROM just by doing a Factory Reset (or TWRP restore of Data) and slot switch.
Factory reset
Install the ROM as per usual procedure (Install ZIP, reflash TWRP with Treble Manager 1.2+, reboot recovery to allow slot switch, install Gapps + Magisk + Mods, etc., reboot).
4.5. Restore a TWRP backup
There is nothing special about restoring a backup. Even if your backup was from a non-Treble ROM, you can restore that backup on a Treblized device. Obviously, though, any Treble ROM backup can only be restored on a Treblized device.
----------------------------------------------
5. Mods and Extras [Gapps, Magisk, custom kernels, etc.]
After you have confirmed that TWRP is booting in to the correct slot (see Section 3), you're ready to install other ROMs (see Section 4) followed by mods. I did briefly go over mods in Section 4, but I'll go into more detailed info about compatibility here.
Any usual Gapps should work fine, just as long as you flash after the slot is correctly set. Note that RR Camera (GCam) requires Gapps to be installed. I used Nano, they worked fine.
Also note that some GSI's will require you to boot the system first before installing Gapps.
Custom kernels must be marked Treble compatible for our device. Specifically (info for kernel developers) this means adding slotselect flag to vendor entry in DTB, and disabling dm-verity (so we can inject vendor changes to system).
It is reported that standard Magisk will work in RR Treble ROM, but it does NOT work on GSI. You need Magisk 16.4 beta or later for GSI's. Also see the FAQ section at the end for more info on the Magisk situation.
Some other ZIP's might need updating for Treble, really unsure. Experimentation is welcome. Just be sure you make TWRP backups before testing anything, of course!
--------------------------------
6. FAQ and Troubleshooting
Q) I get "cannot receive hello packet" in MiFlash
A) Just reboot EDL mode and try again. Usually only happens if you try to flash in EDL twice in a row. See the Low-level Backup/Restore/Unbrick toolkit thread for more info about EDL.
Q) How to Magisk with Treble? What is the TWRP and Magisk interaction?
A) Best to use Magisk 16.4 beta or later, it's reported as working on GSI's. Also note that Magisk is installed to the boot ramdisk (the same place as where TWRP goes) and this has the following implications:
Whenever you flash the TWRP installer, you will need to reinstall Magisk *after* you Reboot Recovery
TWRP installer will flash to BOTH slots, but Magisk will only flash to the CURRENT slot. So if you flash TWRP installer, it may erase any Magisk install on the inactive slot.
TWRP survival (in my recent TWRP builds) backs-up and restores the whole ramdisk. This will include Magisk, if it was already on the boot slot that it backs up.
Q) EDL mode? Eh?
A) EDL mode, or "Emergency DownLoad" mode, is a low-level mode for flashing devices. It is entered by the command:
Code:
fastboot oem edl
EDL mode is used to read/write to the eMMC more directly. It is used by this tool, as well as flashing with MiFlash.
Other important notes:
You will need good QDLoader drivers. These drivers gave me the best results.
You can exit EDL mode by holding Power button for ~10 seconds. Hold with VolDn to reboot into fastboot again, as one might expect.
Make sure you use a good USB-C cable.
Sometimes the flashing process can freeze. It will always report success when done. If it freezes, you need to reboot EDL mode. Try a different USB port or cable if you keep experiencing freezes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?

parasnarkhede said:
can i use this persist.zip inorder to solve the wifi issue in stock rom as well as some of custom rom too?
Click to expand...
Click to collapse
Yup. Just flash a stock persist.img in EDL mode. But backup your original in case, it could erase or change your BT MAC too.

@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.

Typhus_ said:
@CosmicDan thank you so much for your work on this. Quite impressive if you ask me.
Tell me just something, every time you talk about "...do this or that in EDL mode..." you mean that we have to use your backup/restore tool, right?
I'm sorry for the noob question but, despite I'm quite familiar with Android, this is my first time using a device that has "slots" and that needs to boot to TWRP in order to flash it... there's some differences from all devices I had in the past and that's making doubt some stuff.
So, anyway, I'm currently using official BETA leaked by Xiaomi (Oreo 8.1 - OPM1.171019.019.8.5.11) so do I really need to reflash stock as you suggest? I mean...it's stock, beta but stock and I've never flashed any other custom ROM (since I've read that by doing it I could have issues with WiFi after returning to stock). So, what do you think? Is it really necessary to reflash stock? My partitions are all the original ones...the only thing different is system, right?
Thank you for your time and work.
Click to expand...
Click to collapse
EDL mode is like fastboot mode, but even lower-level.
You enter into it with:
Code:
fastboot oem edl
It is needed by my backup tool yes, but it's also used to flash in MiFlash.
Will update the guide and FAQ with this info.

How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?

Ahmed Al-Sayed said:
How to flash the persist file attached in the op in mi flash ?
You mean replace it with the one in the stock rom fastboot files and flash the whole rom again via mi flash ?
Click to expand...
Click to collapse
Just browse to the folder with MiFlash....

CosmicDan said:
Just browse to the folder with MiFlash....
Click to expand...
Click to collapse
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?

Ahmed Al-Sayed said:
Oh, you mean choose only the persist.img file then mi flash will flash it automatically to the right partition ?
Click to expand...
Click to collapse
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash

CosmicDan said:
No, you don't choose the persist.img. You choose the folder. You can't even choose a file in MiFlash, it's a folder browse.
It's the exact same method of flashing anything in MiFlash
Click to expand...
Click to collapse
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?

Ahmed Al-Sayed said:
Which folder ?
The folder that i extracted the persist.img (attached in the op) in ? Or the srock rom folder after i replace the persist.img (attached in the op) with the one in the rom's folder and execute flash ?
Click to expand...
Click to collapse
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!

CosmicDan said:
DONT REPLACE PERSIST IN STOCK FIRNWARE. That does LITERALLY nothing, the persist is already from stock ROM!
Just extract the persist-only ZIP, and select it in MiFlash! Don't insert extra steps that I never said!
Click to expand...
Click to collapse
Thanks !

Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?

Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.

sudipta08sarkar said:
Dear sir,
I have few questions
1. Do we need any vendor image to flash with it?
2. How to revert back to stock rom (And erase vendor partition) from treble custom rom?
3. Can we revert back to stock partition map through mi flash tool in flastboot mode or edl mode?
Click to expand...
Click to collapse
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
CosmicDan said:
2. Flash latest firmware (V.9.5.10.0.ODHMIFA at time of writing) in EDL mode with MiFlash. This will wipe your device (including Internal Storage) and restore stock partition map. This could take a while.
Click to expand...
Click to collapse

Ritik99 said:
Hopefully someone will make video soon, so that it becomes somewhat more easy to understand.
Click to expand...
Click to collapse
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.

CosmicDan said:
1. I don't understand the question. The vendor image is part of the Treble ROM. You can get vendor from the RR Experimental thread for example.
2. By following Section 1.1.; Step 2 alone
3. By following Section 1.1.; Step 2 alone
Click to expand...
Click to collapse
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?

Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.

CosmicDan said:
Or you could tell us what part you're having trouble with so I can make it more easy to understand?
I don't understand how a video would make it easier. You need to be able to understand the process - not just copy what some guy is telling you to do.
Click to expand...
Click to collapse
Yup.. that what make people say "i do it the same as instruction and bricked my devices." It is because u just copy what other ppl do and dont know what exactly u do lol... Fir me, what in text is more worth.. because it explain everithing. And the video just a guidline of what u read.

sudipta08sarkar said:
Ok I understand, but my query is, everytime I will flashing a new treble rom, will it flash vendor partition itself?
Click to expand...
Click to collapse
Yes. Well, depends.
RR Treble has Vendor included, because it needs it. GSI's are just a system image that use your existing vendor.
squallbayu said:
Congratulations, can't wait to test it on my a1.
One question, how about google play certified device status? Is still verified or not?
If i choose to shrink data partition, how much left for data? My a1 have 64 gb storage.
Click to expand...
Click to collapse
If you.can tell me exactly what "Play Certified" actually is, then I might be able to answer that question.
The TWRP with Treble Manager tells you the size change.

[GUIDE][20-MAY-2019]HOW TO FLASH Z010D ROMs on Z010DD (8.1 and 9.0 ROMs).

This guide is specifically aimed for Z010DD users who want to flash custom ROMs:​If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518​
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20

Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys

Patch is required for sd410 devices??

koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.

Guide has been updated. Please check.

unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl

I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?

PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.

ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.

Is it working on asus zenfone max 2016 sd 615?

Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files

james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).

Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.

TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.

james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.

TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?

unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939

Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem

Unlocking the apk no longer works

[GUIDE] Install official Pixel Expierene ROM and Google Camera Mod 7.x

Welcome to my latest Thread. Today for the Official Pixel Expierence Builds from the Official Website. This Guide does include the Installation of a custom Recovery which allows Factory Resets and flashing Updates/ROMs. Enjoy!​
1. Download and prepare everything
First of all visit: https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
And download the latest Software Binaries from Sony which You will need to flash together with the Boot Image (Kernel).
After that download the ROM File from here: https://download.pixelexperience.org/ and also download the "Recovery Image" which is a Kernel/Boot Image
Get the Magisk Manager Apk from here: https://github.com/topjohnwu/Magisk
Extract the Software Binaries to get the .img File from it.
2. Flash using Fastboot
After getting the Kernel/Boot Image do a patch with the Magisk Manager App (Your Phone doesn't needs to be rooted for that) (The Output File will get called magisk_patched,img from now)
Flash the Software Binaries from SONY with:
Code:
fastboot flash oem_a SW_binaries_for_Xperia_Android...............img
Repeat that step with:
Code:
fastboot flash oem_b SW_binaries_for_Xperia_Android...............img
Now flash the Kernel You got from the Magisk Manager with:
Code:
fastboot flash boot_a magisk_patched.img
And repeat that again for the Second Slot:
Code:
fastboot flash boot_b magisk_patched.img
3. Install using a SD Card or ADB
After flashing the Kernel. Turn Off Your Device and hold the Volume- (Lower) Button together with the Power Button until You see the SONY Logo. Release both Buttons and wait for the Recovery coming up.
Search now for the Apply Update Option and select based on Your preference the ADB or SD Card Method to flash the ROM. Connect Your Xperia to Your PC again and enter:
Code:
adb sideload filename.zip
(In case of using the ADB Method)
Your Device should now flash the selected ZIP File (In our case the Pixel Expierence ROM).
4. Profit
Wipe Your Device now using the Factory Reset of the Recovery. Install the Magisk Patched Kernel Image again using the commands of the second Step of this Guide to keep Magisk functional. Connect Your Phone to a Charger and install the latest Magisk Manager to Your Phone. That's it! Enjoy
What Works:
VoLTE
Wifi Calls
Video Calls over Carrier
Camera Button (Does not start Camera Apps)
Everything!?
Bugs:
None!?

Do you feel some animation lag

Sketch. said:
Do you feel some animation lag
Click to expand...
Click to collapse
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette

Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )

This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!

naygnosuw said:
Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )
Click to expand...
Click to collapse
Almost. Astro isn't available. 4K 60FPs Kills the App (don't toggle the 60FPS Button on 4K)
Tabike said:
This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!
Click to expand...
Click to collapse
It feels so simple but I got You. I'm still not sure how I should do it. I have a PC, a Chromebook and a Xperia 5 for recording. While the Xperia needs to get flashed (not usable as Camera). I could make a Video with My Chromebook maybe in 720p and combine it with Screen recording somehow. I'm not a YouTuber but I will give it a shot this week... Promised!

Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40 variants - what are they?
and what variant PE Rom support official?

Updated the Guide.
@JOKER.SOHA It's printed on the back of Your Xperia (Bottom). Model Numbers... Choose the right one for You. Don't understand the rest of Your question... Sorry

我没有移动数据。
未检测到SIM卡。
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I don't have mobile data.
The SIM card was not detected.

Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!

Term1nator3000 said:
Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!
Click to expand...
Click to collapse
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such

Miustone said:
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such
Click to expand...
Click to collapse
Ahh okay np. Hopefully things will smooth out.

I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.

ceplavia said:
I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.
Click to expand...
Click to collapse
It isn't possible to flash anything besides Stock in Flashmode with a locked Bootloader. That's one of the Basic Things on Android. That's why it isn't mentioned here... You should carefully learn how everything works before thinking about to flash anything on Your Device...
The Pixel Expierence Guides for Xperias are wrong and do Not Work btw. That's the reason for My Guides...
Best Regards

Miustone said:
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Click to expand...
Click to collapse
Hi, rom maintainer here, just to precise that a kernel panic would totally freeze your phone and you'll be unable to do anything except force reboot your phone.
Also, responding on another thing I saw on this thread, the only reason I don't open an xda thread per device supported is that I would have to update like 25 threads every month, respond the same questions for all those threads over and over etc
I have my telegram for that t.me/PixelExperienceSony
I might do 1 thread for all devices in cross platform dev section.
Cheers

can someone please make a step by step YouTube YouTube guide? I tried to follow the instructions with little sucess

Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.

Miustone said:
Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.
Click to expand...
Click to collapse
bro can you share the steps how to install.
do i need python to run the payload extract?
i cant flash the rom and cant use the phone, loop in the boot 5sec will restart ..

VOLTE not working in india with JIO network...

Were you able to get the Volte working on Indian networks?.

[Guide][Installation][Fix]Switching from stock ROM to custom ROMs + Installing stock ROM after a brick or other Failures ( Mi A2 Lite - Daisy)

This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.

EDL FLASHING (For windows only)​
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.

qdl flashing ( linux only )​
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA

FASTBOOT FLASHING​
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.

FINALLY! FLASHING CUSTOM ROM​
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system

MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA ​
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASH​The process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system

Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers

steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.

user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.

First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'

I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).

AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.

user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.

AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.

How To Guide [Pixel 7 Pro] [TD1A.220804.031] Root guide + Extracted Images + How to

How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila

A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot

Reserved

Thanks!

Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk

I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).

Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).

so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img

I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro

mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image

Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking

I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?

whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.

Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.

zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.

mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?

Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459

whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.