Related
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.
Welcome to this guide, where I will guide you through rooting, flashing custom roms, and more, on our little Umidigi One Max !
WARNING : I am not responsible for your phone breaking or exploding during the night under your pillow. Please advice. If you cannot boot anymore, keep reading, your phone is NOT dead.
OFFICIAL ROM (Android 8.1)
The Umidigi One Max comes with Android 8.1 Out of the Box. Manufacturer has no plan on having 9.0 on the phone. That's why we root then ! Let's get into it.
Rooting the phone without unlocking it, or installing TWRP
Everything you'll do on this phone will NOT require a bootloader unlock. Note that this method is only in case you don't want to have your data wiped, or don't have access to an SD card (thus you cannot flash .zip in TWRP, except for ADB Sideloads)
What you'll need
Download the latest ROM from Umidigi's website : https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
Choose the ".rar" file
"E" ROMs are for European versions. It doesn't really matter what you choose.
Download SP Flash Tool on the same thread you opened for the ROM. It's "SPFT" for short
Unzip both
Install Magisk Manager on your phone : https://github.com/topjohnwu/Magisk/releases/
Steps
IMAGE COURTESY OF bencebacsi @ Umidigi forums
In the unzipped ROM folder, find boot.img
Copy it to your phone storage using an USB cable or any other method
Open Magisk Manager, press install
Choose "patch boot image file"
{
"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"
}
Let magisk do it's job
Find the boot.img file you just copied
Copy the patched_boot.img back to your computer
Open SP Flash Tool
Open the "Download" tab
In "Scatter-loading file", press the folder icon and browse to the downloaded ROM folder. Choose the only file that shows up
Untick every box except for boot. There is a column called "Location" with a path, click on it to change to file.
Choose patched_boot.img
MAKE SURE YOU UNTICKED EVERYTHING EXCEPT BOOT
Click the "Download" button
Turn off your phone (not reboot) and connect is via USB
wait for the flash to succeed. Once done, unplug, boot, voila ! You got magisk !
Credits to topjohnwu for Magisk, what a great piece of work
Installing TWRP
Note that if you want to access the /data partition (internal storage), you'll have to wipe it ! If you do not need it, keep going, it won't wipe unless you want to.
What you'll need
Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html
Magisk.zip installer (NOT the manager) : https://github.com/topjohnwu/Magisk/releases/
SP Flash Tool : http://www.mediafire.com/file/wxlld9dfywk67jl/SP_Flash_Tool_v5.1916.rar/file
This method is shorter and requires less downloaded files.
Steps
Turn off your phone
Run SP Flash Tool
Load the scatter file (see pictures above) you downloaded from the latest ROM (see above as well)
Untick everything except recovery
Change path to recovery.img to be the TWRP image
Click "Download" and plug your phone
After it's done, unplug, and press Power + Vol Up
You'll see three options appearing. That's how you'll get to the recovery. Use Vol Up to scroll, and Vol Down to select. Choose Recovery Mode !
TWRP should boot by now
EXTRA STEP : Make /data readable. You will need to format data (YOU'LL LOSE ALL YOUR DATA) (Wipe > Format Data > Type "yes") and after that, flash this zip : https://androidfilehost.com/?fid=1322778262904004415
You can now proceed to flash zips, including Magisk.zip. If you made /data readable, you can send it to your internal storage. If not, use an SD CARD or ADB PUSH / SIDELOAD.
Returning to stock to fix issues / brick
Use SP Flash tool but instead of unticking everything, tick everything. Note that USERDATA, if ticked, will clear your data.
Ticking only certain partitions may work if you got issues with magisk or system mods and are still on Official ROM. Flashing boot and system will remove Magisk. If you are on custom ROM, you can flash their system again to fix issues as well. Make sure to choose the right system.img in SPFT !
OTHER ROMS
Installing GSI (Generic System Image) to get Android Pie 9.0
GSI takes advantage of Project Treble to create one system image that will work on most devices without issues due to a separate "vendor" partition. The One Max is Treble-compatible, but only up to 9.0 (No 10 Q for now)
This will allow you to get an AOSP experience, with it comes easy modding and theming, and less bugs, less chinese-spying (that's a thing apparently, but who cares really ? Not me to say the least)
GSI List
You can find a GSI List including bugs and download links in my other thread here : https://forum.xda-developers.com/android/development/gsi-gsi-experiments-t3941194
WARNING : DOWNLOAD GSIs WHICH ARE ARM64-AONLY AND NOT AB !
Installing a GSI
You will need TWRP Installed. Check above if it's not done yet. You'll also need the Magisk.zip, and I highly recommend you getting the disable-force-encryption zip
Start up by wiping /data in twrp (Wipe > Swipe the bar). It will not wipe the files in your internal storage (Music, Download, etc...). If you want to get access to /data in TWRP (which I highly recommend), you'll need to do a full format (Wipe > Format data > type yes).
Download a GSI (.img) and send it to your phone (Either using an SD Card, or adb push [file on computer] [destination folder]). Send Magisk and the disable-force-encryption zip at the same time.
Flash that system image using Install > Install Image > Browse to the .img file
Flash disable-force-encryption if you formatted /data (don't flash it if you didn't do that !)
Flash Magisk.zip
Reboot and profit !
Note that there might be some issues with the GSI you choose. Most GSI suffers issues regarding Wifi Tethering/Hotspot. Other than that, check for my thread for issues regarding GSIs.
Some GSI require installation of GAPPS (Google Apps). Download a GAPPS zip and flash it at : https://opengapps.org/ (Choose ARM64 and 9.0)
If Installation fails, saying that system size is too small, go to (Wipe > Advanced Format > Tick "System" > Repair or change file system > Resize File System) and try flashing again.
INTERESTING MODS FOR ALL ROMS
Magisk FDE.AI
A great system manager. Saves a ton of battery without a performance hit. You need magisk installed. XDA Thread : https://forum.xda-developers.com/apps/magisk/beta-feradroid-engine-v0-19-ultimate-t3284421
Fix SafetyNet not passing on custom ROMs/GSIs
SafetyNet will not pass by default on custom ROMs / GSIs.
Use Magisk Hide Prop Config : https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Run 'su' then 'props' in a terminal emulator. Edit Device fingerprint, choose Pick a certified fingerprint. I recommend using Xiaomi Redmi Note 7, as it changes the status-bar to be notch sized.
Note that you may need to do this next fix to make 'su' work :
Root request not working with Magisk
On some GSIs, root requests will not show up. You need to move some vendor files over to system.
Use TWRP's File Manager (Advanced > File Manager) or Adb shell to copy theses files :
Code:
/vendor/lib/libdirect-coredump.so
COPIED TO
Code:
/system/lib/libdirect-coredump.so
Code:
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
This will fix this issue until GSI / ROM creator fixes it in their ROM;
Enjoy your new phone ! Don't forget to say thanks to all the developers behind every project (not me ! I didn't do anything )
If you have any issues, feel free to ask questions !
See you on the other side
Downloaded phhusson's AOSP ROM
Extracted compressed image. Then...
Wiped Phone from TWRP w/ all three options Swipe, Formatted (Type "Yes"), and advanced wipe.
From TWRP went to:
Install > Install Image > Selected system-arm64-ab-gapp-su.img > Select Partition to flash image
From this screen it lists these partitions for selection:
-recovery
-nvram
-uboot
-boot
-logo
-tee
-System Image
I select System image. It starts flashing. After it has finished, I go to reboot, and that is when TWRP states "No OS installed".
Am I downloading the wrong image file?
*********************EDIT****************************
Nevermind. I downloaded system-arm64-aonly-gapps-su.img.xz and it boots fine with gapps included
Exactly, you downloaded A/B image, not A-only.
Using phhusson's AOSP ROM. I got the root requests show up. However the superuser app is blank. Nothing shows in the list.
Request for a video to install GSI
Hello
I'm using Umidigi One Max Android 8.1 and want to upgrade to 9.0 . Can you please make a YouTube video showing how to install the GSI version I'd gladly appreciate it.
Over the last month or so, I've tried multiple GSI ROMs, and stock. I've rooted stock, and everything runs nicely, I just can't stand the lack of features. Even rooted on stock, Google Pay still works. If I install a GSI ROM like Havok, root it, gpay will not work. Not sure why it works on stock rooted with magisk, but not with other ROMs.
I'm looking for a hacked stock rom for the one max that:
A.) Can be rooted.
B.) Can still run gpay.
C.) Has a advanced restart option to boot directly into recovery.
D.) Displays the battery in the status bar as a percentage rather a symbol, and a clock with seconds option.
If I had those options, I would stick with stock. I can accomplish all those options with Havoc GSI ROM, I just can't get NFC/gpay to work.
su
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
@ _cab13_
thanks for tutorial
some comments/questions
Image shows MT6739 in phone image and scatter file of mt6739
My phone is MT6363 and appears to agree with online specs site such as
https://www.gsmarena.com/_umidigi_one_max-9525.php
Am I looking at the wrong tutorial or umm have you grabbed images from another phone and forgot to say so?
w1lh3lm3d said:
how did you repair su binsaries after flasing (in twrp the vendor folder is empty)
everything else works
Click to expand...
Click to collapse
You have to mount the folder system and vendor for reading and writing and you can copy it, this is in recovery mount
Very helpfull, thanks)
Has anyone tried dual SIM and SD hack on this phone? I cant get my to work. When I do the hack, phone does not see any sim cards nor SD card.
However if I put only two sims, or sim and SD everything works well.
It is almost like issue w Samsung but no warning message
can i use this process on umidigi one as well
q1. Can i use this process on umidigi one as well?
When i visit "Official TWRP recovery.img by chankruze : https://twrp.me/umidigi/onemax.html" and search on devices they don't have umidigi one or one pro only the one max option. Other than screen size all three are pretty much spec'd the same. The umidigi one just doesn't have wireless charging or nfc that one pro and one max have and one max has 6.3 waterdrop vs one/one pro 5.9 notch display but all 720x1520 9:19 aspect ratio configurations. I found a umidigi one and one pro twrp recovery image here _https://unofficialtwrp.com/umidigi-one-umidigi-one-pro-root-twrp-recovery/ so if i have that are all the other downloads for doing non-rooted device upgrade to 9 pie non-device specific downloads?
q2. Nice to see this process covers a way to get form 8.1 to 9 w/o rooting device. Having never done so i'm curious why other search hits cover steps that require rooting device if the upgrade can be achieved without doing that, any insights?
q3. Would you say the likelyhood of bricking my device, if trying to follow these instructions using umidigi one vs one max, very low? Trying to determine if i should first line up and have on hand backup phone to use if the chance of that happening is high.
does magisk install allow me to upgrade to android 9 pie?
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
myusrn said:
does magisk install allow me to upgrade to android 9 pie from the default android 8.1 oreo on my umidigi one or do i have to use the twrp recovery setup option to enable installing gsi arrowos or pixel experience android 9 pie update?
Click to expand...
Click to collapse
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
drkiro said:
Yes, with the single installation of magisk you could upgrade to Android 9, but you would have many more functions through TWRP. how to remove encryption, backup, etc.
Click to expand...
Click to collapse
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
myusrn said:
Thanks for reply. I was trying to see android 9 pie in magisk modules listings reviewed elsewhere and wasn't seeing what looked like a full android 9 install but rather options that themed and existing android 8.1 like android 9.
q1. If i complete the spft application of magisk_patched.img version of boot.img and try the android 9 module update option that's a one way street correct?
q2. Can one disable magish_patched.img version of boot.img by using spft to put the oem boot.img back in place?
q3. Sounds like twrp is the best way to put the official pixel experience android 9 [ or 10 ] custom rom on my umidigi one device. Your article shows how to get twrp enabled without bootloader unlocking the device. Any insights as to why there are so many articles suggesting that you have to bootloader unlock device to get twrp custom recovery image installed?
Click to expand...
Click to collapse
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
drkiro said:
Magisik, is used so that android 9 can boot, (now 10), in the system update to android 9, you only update the System partition, everything else remains as the manufacturer installed it, when you install twrp, you only change the partition recovery, and when you install magisk you change the boot partition, all this can be reversed, if you install the original versions.
Click to expand...
Click to collapse
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
myusrn said:
just to clarify, with the magisik patched boot.img i'm then able to apply a module that enables access to android 9 [ or 10 ] in the system update UI at which point i will carry out a standard issue android 8.1 to 9 [ or 10 ] upgrade process vs twrp where it appears you directly apply a gis custom rom like the mainstream pixel experience or arrowos options?
Click to expand...
Click to collapse
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
drkiro said:
No, there is no custom rom, which can be installed from the system update, all are images of the system partition, which are called GSI, which are installed by means of fastboot, or by twrp, all of them can be found here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
myusrn said:
interested in what makes a gsi [ generic system image ] custom rom an official vs an unofficial image given the pixel experience is listed as unofficial and aosp, arrowos and resurrectionremix offerings i've seen referenced in many places are listed as official.
i'd like to try the only official android 10 q aosp listing on my umidigi one to get off the dated android 8.1 experience and onto the more current one. This article suggests i can get twrp onto my device without bootloader unlocking it and with ability to revert back to the factory oem image setup currently running on it, if that update causes me to loose functionality or stability, using twrp recovery.
Is that a correct interpretation of the instructions in this article, and your clarifications in our exchange? I'm interested in experimenting but would like to not loose ability to go back to non-bootloader unlocked factory oem image in the event i need to exercise device hardware warranty or sell it. Thanks for your clarifications and additional insights.
Click to expand...
Click to collapse
You can return, to the Originate flashing state, this image, https://community.umidigi.com/forum.php?mod=viewthread&tid=18692&extra=page=1 , can experiment with any image and return it to the original state, the pixel experience does not work with this phone, in Android Q the NFC does not work, and the videos in whastapp, do not work. Android 10 image comes without gapps, you have to flash them. If the twrp you can flash it through fastboot
What is GSI?
GSI stands for Generic System Image and will allow you to install an alternative ROM on your Galaxy A20?
No longer will we be restricted to the Samsung ROM.
These ones worked for me. If they don't work for you, go to the list of all GSIs. There are plenty to choose from. Select arm64 ab files.
Q GSIs
1. AOSP 10
https://github.com/phhusson/treble_experimentations/releases
2. Pixel Experience, EvolutionX & Havoc
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
3. Crdroid
https://sourceforge.net/projects/amber-gsi/files/crDroid v6.1/crDroidAndroid-10.0-20200104--v6.1-arm64-ab-vanilla.img.xz/download
Custom Android 10 boot screens
https://forum.xda-developers.com/galaxy-a20/themes/a20-custom-splash-screen-android-10-gsi-t4019693
List of all GSIs
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
Before you Start
1. Make sure your phone is rooted
For A20: https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
For A30: https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
2. Install TWRP and remove data encryption.
For A20: https://forum.xda-developers.com/ga...p-samsung-galaxy-a20-custom-recovery-t3955271
For A30: https://forum.xda-developers.com/galaxy-a30/development/recovery-twrp-galaxy-a30-t3968085
Quick root and TWRP together for the A20: https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
3. Backup only 3 parts: boot, data & system (not system image) onto external SD or usb-otg. If something goes wrong you should be able to restore the phone using TWRP.
4. Also use SMS Backup and Restore so you don't lose your messages or calls.
5. Make sure your Ext SD card is Fat32. I've noticed that GSIs don't recognise ExFat.
Android 10 (Q)
1. Installation
1. Begin with stock ROM
2. Reboot into TWRP ( then mount product - system - vendor)
Back boot data and system
3. Wipe both caches, data & system
4. Install GSI
5. Flash Magisk and physwizz GSI kernel from here https://forum.xda-developers.com/t/kernel-physwizz-kernel-for-the-galaxy-a20.4180107/
6. Reboot.
2. Installing GApps
Some GSIs come with GApps. If you're doesn't and you want to have GApps, then use this method.
a.-Resize system partition so you can install OpenGAPPS, go to wipe, advanced wipe, select system, select repair or change file system and select resize file system. If you get error 1 unmount and mount the system partition and try again
b. Install GApps
3. Fixing Navbar
As soon as you boot up. Run Magisk and install this module.
View attachment navbar-enabler.zip
4. Android 10 Backup
Backup Data only (EvolutionX and Havoc 3.0 will do boot/data/system backup and restore),
5. Android 10 Restore
1. Reinstall GSI (a - h above)
2. Restore Data
3. Install GApps (if needed)
Reboot
To Access larger SD cards
Unzip the file below
Use TWRP file manager to copy this file to
/system/system/bin
Tap on to file
Press chmod755
Reboot system
Android 11 (R)
wIP
Some interesting links.
https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199
phhusson treble releases
https://github.com/phhusson/treble_experimentations/releases
GSIs for A50
https://forum.xda-developers.com/galaxy-a50/how-to/guide-guide-how-to-flash-gsi-t3934005/page1
AOSP GSIs
https://source.android.com/setup/build/gsi
GSI for the A70
https://forum.xda-developers.com/galaxy-a70/how-to/gsi-testing-thread-t3956230
List of all GSIs
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Project Treble
https://forum.xda-developers.com/project-treble
Lolinet mirror
https://mirrors.lolinet.com/firmware/gsi/
Only this one for install? I Will Search another gsi
alexHdz said:
Only this one for install? I Will Search another gsi
Click to expand...
Click to collapse
It looks like this one comes with GApps and su built in.
physwizz said:
It looks like this one comes with GApps and su built in.
Click to expand...
Click to collapse
WiFi not working I guess
alexHdz said:
WiFi not working I guess
Click to expand...
Click to collapse
I thought that problem was only for Android 10
I tried to install GSI today but it didn't work.
Had to do a factory reset.
physwizz said:
Possible Installation Instructions (they will become more precise as more information becomes available)
1. Make sure your A20 is rooted (https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4)
2. Backup with Titanium Backup
3. Install TWRP
https://forum.xda-developers.com/showpost.php?p=80028118&postcount=2
4. Backup system onto external SD or usb-otg (exclude data)
5. Install GSI from TWRP.
a. Download the desired GSI (it MUST be A/B_arm64 Variant)
-One GSI can be found here (https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199)
b. unpack it if it wasn't in .IMG format
c. Go to TWRP , Install , Install IMAGE
d. Pick your GSI and select SYSTEM IMAGE
e. Reboot to TWRP Recovery
f. Flash "GSI_Fix_boot.zip"
View attachment 4815497
If you can't get TWRP you may need to install via Odin.
I'm not sure of any of this at the moment.
Click to expand...
Click to collapse
Hi guys! I try to install android 10 gsi, however when I go into twrp mode not recognizing the rom img what can it be?
I rooted and twrp A205G
physwizz said:
Possible Installation Instructions (they will become more precise as more information becomes available)
1. Make sure your A20 is rooted (https://forum.xda-developers.com/showpost.php?p=80021195&postcount=4)
2. Backup with Titanium Backup
3. Install TWRP
https://forum.xda-developers.com/showpost.php?p=80028118&postcount=2
4. Backup system onto external SD or usb-otg (exclude data)
5. Install GSI from TWRP.
a. Download the desired GSI (it MUST be A/B_arm64 Variant)
-One GSI can be found here (https://forum.xda-developers.com/showpost.php?p=80177833&postcount=199)
b. unpack it if it wasn't in .IMG format
c. Go to TWRP , Install , Install IMAGE
d. Pick your GSI and select SYSTEM IMAGE
e. Reboot to TWRP Recovery
f. Flash "GSI_Fix_boot.zip"
View attachment 4815497
If you can't get TWRP you may need to install via Odin.
I'm not sure of any of this at the moment.
Click to expand...
Click to collapse
i tried install any GSI on my A205F , but it's keeps bootloop , any suggestions to fix ?
hwp_2804 said:
i tried install any GSI on my A205F , but it's keeps bootloop , any suggestions to fix ?
Click to expand...
Click to collapse
I have the same problem on 205yn.
which method did you use to install twrp. there are some 205f users having trouble installing twrp
physwizz said:
I have the same problem on 205yn.
which method did you use to install twrp. there are some 205f users having trouble installing twrp
Click to expand...
Click to collapse
i use methods 1 and 2 , both also the same
twrp is working , but my internal storage seems like corrupted .
hwp_2804 said:
i use methods 1 and 2 , both also the same
twrp is working , but my internal storage seems like corrupted .
Click to expand...
Click to collapse
So method 1 have you the same result as method 2
Can you backup with either method?
Method 1
For the SM-A205YN
Download the A205YN custom recovery from here
https://forum.xda-developers.com/sho...&postcount=169
No need to patch it. Just flash it with Flashify.
If this first method works for a different version, please let me know.
Method 2
For the SM-A205G,
Download the composite recovery from here.
https://forum.xda-developers.com/sho...&postcount=198
Install to ap slot using Odin.
I haven't tested this yet so be wary. I'm going to try it today.
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Install GSI from TWRP. : Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"View attachment GSI_Fix_boot.zip
Flash this zipView attachment Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Reboot
That didn't work.
Reinstalling now ?
physwizz said:
I haven't tested this yet so be wary. I'm going to try it today.
Format data (this is NOT the same as Wipe data) (In TWRP: Wipe -> Format Data)
Reboot back into recovery
Install GSI from TWRP. : Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
Flash "GSI_Fix_boot.zip"View attachment 4815771
Flash this zipView attachment 4815767
Reboot
That didn't work.
Reinstalling now
Click to expand...
Click to collapse
Try this:
Links donwload:
ROM: Android 10 GSI Treble (A-Only):
https:// enrt.eu/ FpMD
FixZygote V2 and Permissiver v5
https://androidfilehost.com/?w=files&flid=279429
Instalation:
1- Into TWRP mode
2- Wipe/ advanced wipe/ system. data and cache
3-Install/ select internal storage/ search rom image and install
4-Install/ FixZygote and Permissiver v5
5-reboot
PS: I haven't tested it yet on A205G as my twrp doesn't recognize any img rom!
Theus01 said:
Try this:
Links donwload:
ROM: Android 10 GSI Treble (A-Only):
https:// enrt.eu/ FpMD
FixZygote V2 and Permissiver v5
https://androidfilehost.com/?w=files&flid=279429
Instalation:
1- Into TWRP mode
2- Wipe/ advanced wipe/ system. data and cache
3-Install/ select internal storage/ search rom image and install
4-Install/ FixZygote and Permissiver v5
5-reboot
PS: I haven't tested it yet on A205G as my twrp doesn't recognize any img rom!
Click to expand...
Click to collapse
How did you install your TWRP?
physwizz said:
How did you install your TWRP?
Click to expand...
Click to collapse
I rooted for magisk and twrp used method 2 of the post!
Theus01 said:
I rooted for magisk and twrp used method 2 of the post!
Click to expand...
Click to collapse
I just changed method 2
physwizz said:
I just changed method 2
Click to expand...
Click to collapse
I did the twrp process again by the new method 2 but still the same error, the internal storage is having problems it does not appear the folders or files! and to install a GSI rom it must be the internal memory because the SD card does not work!
Theus01 said:
I did the twrp process again by the new method 2 but still the same error, the internal storage is having problems it does not appear the folders or files! and to install a GSI rom it must be the internal memory because the SD card does not work!
Click to expand...
Click to collapse
did you go to mount and mount everything
Requirement:
Gsi Download arm64-ab or bvN (on some download page)
For ColorOs Base
Twrp COS
Gsi Flash files
Stockboot.img
For RealmeUi Base
Twrp RMUI
Gsi Flash files
Stockboot.img
Installation
1.Reboot to Twrp
2.Factory reset device from Wipe >> Slide>>>
3.Format data from Wipe >> Format data>> Type Yes
4.Flash RMC2decryption.zip
5.Go to Advance wipe & wipe
dalvik, data, cache, internal storage & system
Do Not Wipe Vendor partion
6. Goto install & select install image from bottom right
7. Flash stockboot.img as boot
8. Flash (gsi filename).img as system image
9.Flash vbmeta.img as vbmeta (Download as per base)
10.Flash Deletebootanimation.zip (Read Note First)
11.Flash keystore.zip
12.Format data from wipe bottom right
13.Flash permissiver.zip (skip for RMUI)
14.Reboot System
Note:
only some gsi boot with bootanimation if device bootloop from bootanimation flash deletebootanimation.zip
if deletebootanimation.zip doesnt work delete file manually
System/system/media or system/system/product/media
Optional
For Root flash Magisk 20.3
(in phh based gsi Normal magisk.zip doesn't works)
Rooting on Android 11
make sbin folder in /system & /system_root/system then flash magisk zip
For discussion join
https://t.me/RealmeC2Community
For Gsi Fix follow #gsifix
For Modified Bootanimation #gsibootanimation
realme c2 color os v9.
what will I press in the last step 'do not install twrp' or 'reboot system' only ??
GSI AOSP Android 10
I've tried to open the GSI list you provided.
And I got confused which one do I have to download/pick and which file.
Do you have any recommendations for Android 10 stock AOSP?
Thanks in advance.
Cheers. :fingers-crossed:
Rj clno said:
what will I press in the last step 'do not install twrp' or 'reboot system' only ??
Click to expand...
Click to collapse
always do not install twrp app
Shinnosuke Nohara said:
I've tried to open the GSI list you provided.
And I got confused which one do I have to download/pick and which file.
Do you have any recommendations for Android 10 stock AOSP?
Thanks in advance.
Cheers. :fingers-crossed:
Click to expand...
Click to collapse
arm64 a/b or arm64 bvn/bgn v=vanilla g=gapps
I’ve downloaded the arm64 a/b gapps and go. I’ll try it later. Then I will tell you if I find any bugs and then upload the logs. Where should I upload it?
I am using :
system-roar-arm64-ab-gapps.img from here
TWRP 3.5.0_9-1 SIDDK
ColorOS GSI
adb version Version 30.0.5-6877874
I can't make it run. It loops in opening screen RealmeME (white logo) not Yellow font..
I still can boot to fast-boot mode and call twrp recovery.
Somebody can help me?
many thanks in advance
hey i am using the stock color os 9 on my rmx1943 it similar to rmx1945 yiu think i could use the old stockboot file for it on sourceforge
i'm getting an error whenever i'm trying to flash keystore for rmui. what should i do @Siddk
patrickbusto081302 said:
i'm getting an error whenever i'm trying to flash keystore for rmui. what should i do @Siddk
Click to expand...
Click to collapse
everything fine with keystore make sure u using latest recovery & using A10 keystore
Ahh...booting into recovery even if i press system
@arksolitude is that because you are trying to install android 10 for realme c2? if yes...
1. download stockrecovery.img (or get the recovery.img from the zip file you've downloaded)
2. reboot to bootloader/fastboot
3. type in your computer "fastboot flash recovery (name of the file).img"
4. reboot (this will take you to stock recovery)
5. wipe data and reboot
this is from my experience but this should work
The phones keeps getting updates and the procedure to install GSI ROM might change. There are a bunch of guides in here but none of them worked for me.
If you managed to run GSI ROM on the latest Samsung firmware please share how you did it. Or is it even possible now?
this method was tested on my SM-A750F with lineageOS 17&18 (android 10&11).
1. download the AB VNDKLITE variant (should be called something with arm64-ab-vndklite.img or arm64_b??-vndklite.img)
2. if the image is in a .xz format, extract it using xz or 7zip/winzip
3. download the zip file i attached to this post
4. copy the zip and the extracted image into a SDCARD, then move the SDCARD into the phone.
5. install a custom recovery (for SM-A750FN, use TWRP by ashyx; for SM-A750F or SM-A750GN/DS, use PBRP)
6. boot into the custom recovery by holding the power button + volume up while restarting.
7. swipe to allow modifications
8. click install
9. on TWRP, you will need to click Install Image
10. navigate to your SDCARD folder
11. click on the .img file
12. it should ask you where do you want to install this image. click system
13. wait for it to flash.
14. click install again, then select the zip file you downloaded from your SDCARD.
15. click flash
16. after you finished flashing it, click install, navigate to /data/tmp and install Magisk.zip (you can delete this file after flashing it).
17. Click wipe > format data, then format data
18. After formatting data, click reboot>reboot system. you should now boot into your new OS!
Thank you for the guide!!!
It booted to Lineage OS 18 but after rebooting it's stuck at the lock screen: Screen Lock, Fingerprint and Camera are not working. Is this to be expected for Lineage OS 18?
did you make sure to wipe data before you installed the new OS?
what do you mean by screen lock? password?
What model do you have? (e.g. SM-A750FN, SM-A750F, etc)
can you send me the logs when the camera crashes/when setting password? (to get logs, run adb logcat -f logcat.txt, then upload logcat.txt)
What model do you have? (e.g. SM-A750FN, SM-A750F, etc)
Click to expand...
Click to collapse
Device: SM-A750GN
Tried: GSI - Lineage OS 18 [arm64-ab-vndklite]
did you make sure to wipe data before you installed the new OS?
Click to expand...
Click to collapse
Yes I made I sure I followed your instructions. Question: Is it enough if I format the data partition once? If first attempt failed and I want to flash another ROM will I have to format data partition again? I am doing this everything just to be sure for now.
what do you mean by screen lock? password?
Click to expand...
Click to collapse
During the initial setup if I try to set a PIN or Fingerprint it bootloops or the setup crashes.
Outcome of each ROM:
Lineage OS 17: Bootloop = The logo keeps moving.
Lineage OS 18:Camera, GPS not working. Error when setting PIN for lockscreen.
Please check attachments for logcats and screenshots.
Can you send me a logcat of the boot proccess? (start logcat when powering up the phone, close it after camera crashed/pin setting crashes)
itmr said:
Can you send me a logcat of the boot proccess? (start logcat when powering up the phone, close it after camera crashed/pin setting crashes)
Click to expand...
Click to collapse
I have tried for days and given up. Sorry. Maybe I will try later.
u need to downgrade to the oldest same sw bit firmware, no other options works
I did install treeui 0.95 gsi on my a750f device,how can i install other android 11 gsi on my phone?