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
I have a Twrp backup with the boot img patched with Magisk/Twrp boot to recovery boots GSI with magisk boot to recovery hold volume up while rebooting to recovery will boot twrp for this boot img to work u have to be on the vendor of the boot img which is also in the backup so the phone won't bootloop this vendor is modified to work with GSIs pass the magisk environmental setup and notch fix so swiping down is like swiping down on stock.... to implement notch fix go to developer settings hide display cut and choose the first hide option and your notch will be fixed...
Thanks @Spaceminer for the twrp for without this none would of been possible
please note twrp will only boot with a android 9 vendor and your GSI will only boot with magisk and twrrp with the vendor in the backup cause it matches the boot img, GSIs only boot when the vendor and boot img match
the boot img & vendor img in the backup is from Channel/Retail (PPY29. 105-160-4)
Instructions
If on android 9 stock
1. Boot to bootloader
2. fastboot - w
3. fastboot GSI of your choice
4. fastboot boot twrp.img
5. format data
6. Place the twrp folder you downloaded from the zip into your devices internal storage which will be available after u format data
7.Resize system
8.Flash gapps zip if gapps is needed
9.wipe dalvick
10. go to twrp restore boot and vendor
11. reboot to recovery and phone will boot after boot is complete install magisk manager it will do the environmental setup phone will reboot and u will have magisk.... ( if u want the best experience with magisk on this device I recommend that you use havoc cause with the lineage GSI magisk doesn't play nice but with havoc its stable also when making a backup it's boot, system image, vendor image, data if u chose system instead your backup will bootloop your device upon restoration)
Download (twrp img is in twrp folder remove it and place it in ADB folder)
https://mega.nz/file/7t03DLhL#jjS9vgrJMlDS-_-hsApyx4uJ6L8wXCN8HtjSqJrg2ds
if u wanted to do this manually to install the latest canary or stable version magisk need to patch twrp to the recovery flash phh root boot up install magisk manager give it root permissions with phh superuser from apk mirror now with elevated permissions the option patch directly will be avaliable cause u got root (it's the recommended option ?) chose recovery and leave the other 2 unchecked patch the img and reboot to recovery the phone will reboot os with magisk and u hold up while booting recovery will boot twrp after that backup that boot img in twrrp for future installation of the GSI of your choosing....
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
xcode22 said:
Hello,
Already figured it out.
Is there any way to flash a Android 10 ROM (treble) without loosing magisk ?
thanks for your help!
Click to expand...
Click to collapse
Everytime u flash a GSI just use the vendor and boot from the twrp folder and your android 10 GSI Will have magisk and twrp no need for data disabler zip cause my backup already has the vendor and boot patches enabled for decryption so twrp will be accessible via boot to recovery
([emoji88]Havoc GSI[emoji88])
Also have edxposed for Android 10 since the one in the repo won't work cause it needs a custom magisk with merged patches for xposed to work on android 10 this version has the patches in the edxposed so having to use a custom magisk won't be an issue cause as ya know obtaining magisk and twrrp in this device was unknown into this OP was made
([emoji88]Havoc GSI[emoji88])
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
xcode22 said:
Thanks so much for the instructions, only way i could install on G7 play.
The only thing is I always have to boot in recovery mode to start the system.
If I boot normal it starts again. Any way to solve this ?
I think somehow I flashed my ROM to the recovery partition ?
thank you!!
Click to expand...
Click to collapse
Your on a GSI go in your system settings and activate advance boot and when u have to reboot just put reboot to recovery and you don't have to worry about manually rebooting to recovery everytime u have to reboot also no way u installed the rom to the recovery partion our device doesn't have a recovery partion the recovery lives within the boot img
([emoji88]Havoc GSI[emoji88])]
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
xcode22 said:
thanks, not sure if I can do this with my Treble gsi (phhusson).
The other thing is that some things got messed up after instalation for example I cannot put in a passcode for the phone.
Is there no other way to install magisk on the G7 play ?
Maybe this has to do with the vendor and boot beeing different model than mine wich is XT 1952-2 (latin american model)
thanks
Click to expand...
Click to collapse
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
PoochyX said:
The reason the lockscreen doesn't work is cause the device is decrypted which is essential for the device to be able to reboot to twrp my vendor has the decryption patches for the full functionality of twrp however if u don't care about twrp and just want magisk just patch a fresh version of your boot img in magisk manager with the patch a file option and fastboot that boot img to your device install fresh GSI with your vendor so it will boot encrypted since your vendor doesn't have the decryption zip patches in the vendor... However with this method to have full functionality with magisk u will have to remove from vendor/bin/init mimi hab if this file isn't removed your magisk won't pass the environmental setup... U be given root privileges with magisk before u have to do the environmental setup so u can remove that file...
([emoji88]Havoc GSI[emoji88])
Click to expand...
Click to collapse
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
PoochyX on telegram dm me I walk you threw it
([emoji88]Havoc GSI[emoji88])
xcode22 said:
Yes I understand, sounds logic. I tried to follow your guide but it didn't work.
I did the following:
1. Followed your first instructions with restore vendor and boot in the end to have magisk twrp (Now on Android 10).
2. patched the boot.img (stock one Android 9) with magisk and pulled via adb on computer
3. fastboot flash boot boot.img (patched)
4. Fastboot flash system gsi.img (android 10)
After that I get a bootloop if I go via normal boot and recovery doesn?t boot either.
In the end I tried to flash the stock vendor.img but everything stayed the same.
Not sure how to remove the file in the /vendor/bin, with twrp ?
Click to expand...
Click to collapse
The easiest way I know of is from the stock OS using termux and root.
Code:
su
setenforce 0
mkdir /mnt/x && chmod 0755 /mnt/x
mount -o loop /dev/block/by-name/vendor_a /mnt/x
Now navigate to /mnt/x and everything from vendor will be in there. Find the file and delete it with a root explorer. Then unmount the partition and the changes will be permanent. Doing it this way gets around FEC, which is what prevents you from changing anything in vendor.
Code:
umount /mnt/x
If you need to work on the other vendor partition just change out vendor_a with vendor_b
Any recommendation about what GSI to choice for XT1952-6 variant?
mickem said:
Any recommendation about what GSI to choice for XT1952-6 variant?
Click to expand...
Click to collapse
Chaos GSI Bluetooth works without disabling audio effects (so u can use viper with bluetooth headset) it's clean stock with minimum stuff added to it and works with gravitybox then you got havoc that has the majority of stuff gravity has off the rip so it's not as minimum so more memory usage is needed and Bluetooth only works with the phh disable audio effects work around also magisk works good on both of these lineage is good also if you don't care about magisk working cause with our device magisk has issues on lineage don't know if it was fixed on a recent bulid however if lineage is your preference there is a phh root for it so u can be functional
([emoji88]Havoc GSI[emoji88])
My device is xt1952-4. I downloaded the latest firmware (PPYS29-105-160-4-8), and installed it to both slots. I am currently using Resurection Remix Pie. Is your patched boot.img and vendor compatible with the newer firmware or will I get a downgrade error?
Hi,
Phone : Realme 5 Pro EU version 4GB/128GB.
As the title says, I am trying to install LineageOS then MicroG on my Realme 5 Pro. So far... I've been at this for a couple of days and I've learned a lot, but that was worth it. Still have to see after a couple of days if this install is stable enough.
Usual disclaimer that this is not because it worked for me that it'd work for you etc...
What files are necessary to follow this post?
-> vbmeta.img & twrp.img here : https://drive.google.com/drive/folders/1MUEJkl25gL7zUPXNKFx_I5HLHyfCAzz7 as posted in this guide : https://forum.xda-developers.com/t/...install-twrp-and-install-custom-roms.4177511/
-> C12 Stock ROM from realme : https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_1120_all_s0mRvUGlCJAI.ozip
-> the Lineage 17.1 ROM provided by @kemo12533 here : https://sourceforge.net/projects/myholly****/files/ROMs/RMX1971/LineageOS/
-> the NikGApps Core for Android 10 ARM64 : https://sourceforge.net/projects/ni...ps-core-arm64-10-20210130-signed.zip/download
-> Magisk : https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
-> NanoDroid-patcher : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-23.1.2.20210117.zip
-> NanoDroid-MicroG : https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-microG-23.1.2.20210117.zip
What I have done so far that works (after tons of FAIL)?
-> Unlocked the device
I managed to unlock the device without too much issue following the guide (link to the guide on this forum is provided above).
-> Installed TWRP
rebooted into bootloader.
"fastboot flash recovery twrp.img"
then proceeded in recovery to TWRP.
Lesson Learned: when "fastboot flash ..." behaves funky (as in not the expected result which is OK), change cable/usb port/computer and don't bother trying to troubleshoot it (I spend a day on this for no result). I have to go on my parents windows computer to fastboot flash but hey it works.
-> Installed latest version of RealmeUI OS (C12 from late march 2021)
TWRP wiped (Dalvik, Cache, System, Vendor, Data)
TWRP format data.
TWRP installed RealmeUI OS C12 without issue
(I did boot it without problem and enabled debugging but I don't think it is required)
-> reinstalled TWRP that had just been overwritten by C12 install.
rebooted in bootloader
"fastboot flash recovery twrp.img"
"fastboot flash vbmeta vbmeta.img"
then booted in recovery to TWRP.
-> Installed LineageOS 17.1 with NikGApps.
TWRP wiped (Dalvik, Cache, System, Vendor, Data) and then formatted data.
TWRP installed LineageOS 17.1
TWRP Install NikGApps.
TWRP installed magisk (which roots the OS).
Rebooted and LineageOS booted without issue.
Note 1 : I tried to install this LineageOS on its own to do a clean MicroG install but on its own it wouldn't boot (same with OpenGApps pico). BitGApps and NikGapps Core both make Lineage Boot, but I settled on NikGApps because it seems automatically 'removed' afterwards when installing MicroG, see later.
Note 2 : The magisk app says that the realme5pro does not have ramdisk. It seems that this is wrong: Magisk does say that phones from 2019 & 2020 are a mess to detect and that the RAMDISK test (Yes or No) is unreliable for those. I followed the manual for No Ramdisk and it corrupted my recovery partition. I followed the manual for yes and it works without issue since.
-> Installing MicroG.
I am now in LineageOS
Magisk Installed Magisk from the same apk and follow instructions to install Magisk properly.
Magisk Installed NanoDroid-patcher & rebooted
Magisk Installed NanoDroid-MicroG & rebooted
at this point the play store icon and app have disappeared (most probably removed by the NanoDroid-MicroG install) and the MicroG Settings app is installed. You still have some permissions to give MicroG and configure it properly, but the following video does a good job of that so I'll leave is at that.
Learned along the way :
It seems to be really hard to brick that phone (good stuff). As long as you can still boot in fastboot you can recover, even if system and recovery don't work.
when "fastboot flash ..." commands don't work when "fastboot devices" lists your device, find another computer, don't waste your time trying to fix this with no result.
write down what works for future reference. I am now documenting every step that works.
Edit 1 : Added Magisk bit. Reorganised post and added details.
Edit 2 : Added MicroG bit. Reorganised post and added details. I guess it's a sort of a guide now...
Hi there!
Does anyone know if it is currently possible to install LineageOS+MicroG on a Samsung Galaxy S20FE Exynos with OneUI 4.1 and Android 12 (SM-G780F/DS)?
Or is there another OS that would allow me to have a degoogled and privacy-friendly smartphone?
Thank you all for your help!
Search for "Lineageos with microg". LineageOS with microgn and f-droid already installed
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (Download from here)
(OPTIONAL)GApps (Download from here)
First time installation:
Make sure you are running Android 13 firmware
Flash vendor_boot.img and boot.img to install crDroid recovery using fastboot
Reboot to recovery
Press "Apply update"
Press "Apply from ADB"
Use
Code:
adb sideload
on your PC to flash the crDroid zip
Update installation:
Can be done via OTA using the built in updater in Settings
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/LineageOS/android_kernel_google_redbull
Download:
ROM https://crdroid.net/redfin
Changelog: https://crdroid.net/redfin/9#changelog
Known issues:
You tell me
Visit official website @ crDroid.net
Support chat on Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Please note that this ROM is 64 bit only!
Like the Pixel 7 you cannot install legacy 32 bit applications. For most people this is fine, and brings several benefits. However, if you require older 32 bit applications (like Flappy Bird) please do not install this ROM.
For more information, read this Android Developers Blog post: https://android-developers.googleblog.com/2022/10/64-bit-only-devices.html
Reserved
Thanks, I've been waiting for this version.
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Raz0Rfail said:
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Click to expand...
Click to collapse
Thanks for the info. Was about to make a jump tonight, guess i need to postphone since this my only device.
saxmydix,This is my only Device as well. But with enough time and a good backup and you are good to go .
Raz0Rfail said:
saxmydix,This is my only Device as well. But with enough time and a good backup and you are good to go .
Click to expand...
Click to collapse
I need to use root and the modules tho. You think this related to 64 bit only ?
saxmydix said:
I need to use root and the modules tho. You think this related to 64 bit only ?
Click to expand...
Click to collapse
I think I found the reason why my phone crashed after installing Magisk modules.
I installed the "Magisk bootloop protector" module and installed it directly into the boot image. After re-flashing the patched boot image with Magisk and installing all the other modules I used before and skipping the bootloop protector module, the phone has not crashed in the last few hours.
I also installed 5 lsposed modules and so far the phone works without crashing.
I have tested it out after I wrote the long wall of text at 03:39 am.
Thanks.
Raz0Rfail said:
Hi,
I tried this ROM and had some problems installing it to make Magisk work and also the Google Apps.
The exact problems are in the body text of the spoiler.
Spoiler: My problems with the installation of the ROM
I tried this ROM on my p5 and had some trouble getting it to work with Magisk and Gapps.
Previously I was on the Evolution ROM (https://forum.xda-developers.com/t/...lution-x-7-2-unbound-tp1a-221005-002.4501629/) before I made the switch to CRDOID.
The aforementioned ROM is at the November 2022 security patch level with Android 13, and CRDROID with build date 2022-12-25 is based on the December 2022 security patch level.
The info is important because I could not boot the patched boot.img with Magisk with the November patch level. It just got stuck at the google logo.
After my phone was at the December level, I was able to flash the patched boot image with Magisk, as well as the vendor_boot image without the phone getting stuck in the google logo. Because if it's stuck in the google logo, you can't even boot into recovery to install the ROM.
And the patched boot image with Magisk is needed immediately, because without it I could flash the Mind The Gapps, but after booting into the Android OS they were not findable. Only with the patched boot image were the Google Apps available in the Android OS after flashing of mind the gapps. Other Gapps variations like LiteGapps, NikGapps or BiTGApps didn't install in the first place.
To identify that Magisk was present in the boot image, I had to manually install the Magisk app and in it I could see that the boot image was patched. As well as the Google Apps.
In the next step, I was able to log into the Play Store, but then I got a persistent message that I was offline in the Play Store and could not use it.
To fix this, I booted back into recovery, did a factory reset, and after booting, the Google installation setup came up, which I did, and then I could use the Play Store.
In the next step I wanted to install Magisk modules, installed a few, like the Universal Safetynet Patch and LSPOSED via Zygisk and restarted the phone.
After restarting, the phone ran for a minute and crashed completely. This happened until I removed all Magisk modules (disabling them also crashed the phone). As soon as a magisk module is installed and activated on reboot, the phone crashes after a minute. So far I have no idea what the problem is, so I currently have no modules installed and the phone works.
What I noticed is that the app com.android.hbmsvmanager drains some battery even with the ROM. In the Evolution ROM I had accordingly provided a tutorial on how to disable the app to kill the battery guzzler.
[ROM][13][UNOFFICIAL][redfin] Evolution-X | 7.3-Vengeance |TD1A.221105.001
I am not affiliated with the official Evolution-X team. link to kernel source: https://github.com/HubertVonJass/vendor_google_redfin_13 my other repos for the device and vendor are there as well. downloads...
forum.xda-developers.com
If you still want to install the ROM on your phone after reading the Wall of Text, and you are coming from another ROM, follow these steps.
ROM Issues with this appraoch: You can't use magisk modules. If you use them the phone crashes unless you removed all of the installed modules.
Prerequisites
Spoiler
Patch the boot image from the first post with magisk. Without magisk, you can install the Google Apps, but you will not be able to see them in the Android OS and thus will not be able to use them.
If you don't want Google Apps or magisk, you can skip this step.
In short, install the Magisk App, copy the file boot.img on your phone via usb cable. In magisk click on install, select a file -> choose the boot.img. Afterwards copy the patched magisk image from your Downloads Folder to your PC.
Check your Android security patch status in the current ROM. It is necessary that you have the same patch level as the current build version of CRDROID (Build 2022-12-25 = December 2022 Security Patch).
To do this, open the Settings app. Under Phone -> Android Version -> Security Patch Level.
So when there are future ROM updates from CRDROID, make sure you patch your device to the same security level (easiest to install the Google Factory Image for the patch level) and then install the CRDROID ROM.
If you don't want to use magisk or Google Apps you can skip this step.
Backup your data from the phone (if you have root, use Swift Backup to backup all app data). The best way is to copy your data to your PC.
Backup all folders and files in the first step, but leave out the Android folder for now, as the copy process will be interrupted when copying the Android folder. Then, in the backup directory, create the Android folder and the data, media and obb folders inside it.
You should be able to copy the media and obb folders to your PC without any problems. For the data folder, I recommend skipping any folders that contain android or google as these are the problematic folders. You can then backup these folders once you have backed up the rest. For the problematic folders, I would recommend ignoring them, but if you still need them, copy them over one by one."
If you don't have a backup and want to start from scratch, you can skip this step. But you will lose all your data if you haven't backed it up to a cloud service or somewhere else, so be warned.
If the device is based on the security level like CRDROID or you don't need magisk and Google Apps, you can skip this step.
If your device is not based on the security level of the CRDROID version, you will have to update your phone to that version first.
Download the Google Stock ROM, based on the security state:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
13.0.0 (TQ1A.221205.011, Dec 2022) for CRDROID Build 2022-12-25.
Download the current adb tools for your PC OS:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Extract the downloaded Factory image zip file. Copy all the adb tools files for your OS inside the extracted folder.
Boot your phone into fastboot. Reboot your phone and then hold power + volume down while the phone reboots. Connect your phone to your PC while it is in fastboot mode.
Execute the flash-all.bat / flash-all.sh (regarding your PC OS). With this the entire phone gets updated to the needed security patch and all your data on the phone got wiped.
InstallationAfter all the prerequisites are done, we come to the ROM installation.
Spoiler
Download all the files from the first post [(if you don't already have them) vendor_boot image, Rom zip file and mind the gapps for Android 13 in arm64]. Move them all to the folder where the adb files are already located.
Move the patched magisk boot image to this folder
Reboot your phone to fastboot mode, connect your phone to your pc while it is in fastboot mode.
execute the following commands
Bash:
fastboot flash boot <magisk_boot image name> --slot all
fastboot flash vendor_boot vendor_boot.img --slot all
After both files got installed on your phone navigate the fastboot menu with the volume keys to the point recovery and click the power button to navigate into it.
In recovery mode go to "factory reset" -> "Format data/factory reset" after the click the entire phone data got wiped.
In recovery mode go to Apply Update -> "Apply from ADB"
On your PC execute the following Commands:
Bash:
adb sideload <crDroidAndroid-13.0 zip file>
After an succesfully ROM installation reboot the phone into ANDROID OS.
Go trough the First setup and skip most of the parts.
Reboot your phone again into recovery mode. You can hold the power button -> Restart -> Recovery to go into it.
In Recovery mode go to Apply Update -> "Apply from ADB"
Connect your phone to your PC and execute the command:
Bash:
adb sideload <MindTheGapps-13.0.0-arm64 zip file>
Afterwards reboot phone again into Android OS and validate that the play Store Icon is available and reboot again into recovery mode. if not install the magisk app https://github.com/topjohnwu/Magisk/releases/ and check if magisk is installed. if it is installed on your phone and the mind the gapps installation was successfull, I don't know why it didn't worked.
Inside the recovery mode go to factory reset and execute again an data Format
Afterwards restart phone again and now you should be able to execute the google install setup. Go trough all steps.
Afterwards install the magisk app and validate that it is installed and check if the play store is working.
After the Installation
Spoiler
Copy your backupped files from your PC and reinstall all the needed apps or use swift backup (when you have an swift backup backup) to restore all the needed apps.
You can try to install magisk modules and hope that your phone won't crash after you rebooted it.
Click to expand...
Click to collapse
wow Thank you for the detail.
Now I got to know why lineage OS shows play store offline when I install it.
I may try it after a few later.
Ian getting this error every time I try to install could help me and tell what ism doing wrong I can install the boot but the vendor boot fails and side loading the rim fails ism on stable 13
hunfatal said:
Thanks.
Click to expand...
Click to collapse
And thank you for all the work on V7 and V8
mike9976 said:
Ian getting this error every time I try to install could help me and tell what ism doing wrong I can install the boot but the vendor boot fails and side loading the rim fails ism on stable 13
Click to expand...
Click to collapse
Check if the adb Version matches this version or higher:
execute in command line: adb.exe version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
If it's lower download the latest adb tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Secondary check if you have adb drivers installed for google devices. If you haven't install them before you need them to install.
If you don't know if there are installed download this:
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
extract the usb_driver folder from it and on the .inf file do an rightclick and click on install. Afterwards reconnect your phone while it is in fastboot mode.
Raz0Rfail said:
Check if the adb Version matches this version or higher:
execute in command line: adb.exe version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
If it's lower download the latest adb tools.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Secondary check if you have adb drivers installed for google devices. If you haven't install them before you need them to install.
If you don't know if there are installed download this:
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
extract the usb_driver folder from it and on the .inf file do an rightclick and click on install. Afterwards reconnect your phone while it is in fastboot mode.
Click to expand...
Click to collapse
Thx I'll try that
I'll keep an eye on it but so far I didn't managed to install both root and gapp. Still a huge thanks to @00p513 and @Raz0Rfail for providing and experience/method sharing!
Looking forward to giving this a go!
eSIM is not working for me also I can't install gapps. I installed the magisk boot.img and also magisk app, flashed the image 2 times and also factory reseted a few times. tried different combinations - not working.
OttoUsualConsumer said:
eSIM is not working for me also I can't install gapps. I installed the magisk boot.img and also magisk app, flashed the image 2 times and also factory reseted a few times. tried different combinations - not working.
Click to expand...
Click to collapse
I can't say something regarding eSIM as I don't use it.
hmm did it say in magisk app that magisk is installed not the app?
If not flash the boot partition with the magisk_patched img file.
If you did it already. I recomend an dirty flash of the Rom in the recovery. reboot the phone into Android OS. Go back to the recovery and install magisk the gapps again.
If it didn't helped, do an factory reset and do the entire Installation process again as I described.
Hello all. I am aware of the eSIM and Google Apps issues and will investigate why MindTheGapps is failing to install. As far as I can tell, the lack of eSIM is due to Google Play Services not being present, however I have been unable to get an eSIM until today.
If I install the eSIM on the previous ROM, and then enable DSDS in the phone developer menu, it sometimes works, however this is a far from perfect solution.
I will keep everyone posted in this forum and the support chat on Telegram (the pizza cafe)