Database Info

Cubot Cheetah 2 Nougat Challenges

I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.

TWRP and Rooting a Cubot Cheetah 2 (Nougat)
Android_Dog_Walker said:
I have a Cubot Cheetah 2 with Nougat (7.0) [build CUBOT_6143C_CHEETAH_2_V15_20170623].
I have managed to unlock the bootloader (and confirmed it is unlocked) and was hoping to use the following
"Fastboot boot TWRP.img"
to open and use TWRP to take a pre-root copy of my phone without flashing and then proceed to flash TWRP and then Root it.
I have tried several copies of TWRP 3.0 (supposedly for a Cubot Cheetah 2) extracting image files from the zip or rar files and running Fastboot as above. In all cases I get the following message;
downloading 'boot.img'...
OKAY [ 0.931s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.947s
Understandably the time taken varies a little each time but I'm unable to understand why files intended for the Cheetah 2 do not work. If this will not work using the Fastboot boot option, I suspect it will not work with flash option.
Can anyone help me please.
Thanks.
Click to expand...
Click to collapse
I have done a lot of searching and found the following;
a) Fastboot boot recovery.img does not work on this phone, There may be some Kernel options required to be passed but I cannot find them,
b) Flashing MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 from Needrom, flashes ok by either using "SP Flash tool" or "Fastboot flash recovery recovery image", but when you start the phone or reboot using "Fastboot reboot" and enter recovery, the stock rom has overwritten it. I have tried multiple flashes and erasing the partition first with no success.
The above appear to mean that I cannot use TWRP (or other Custom recovery) and so cannot install the SuperSu.zip. I have raised this on Needrom with TWRP creator who cannot offer a solution.
Before I try using an app, I'd like to ask if anyone has a solution to stop recovery being overwritten. (I have been unable to find a pre rooted image or an image containing TWRP).
Thanks
Solution Found.....The file available from NeedROM will not work with Nougat on a Cheetah 2.
rebuilt MDSTWRP_3.0.2-7ES_Cubot_Cheetah2 using Carliv Image Kitchen and the Nougat stock rom Recovery and.... the Fastboot boot recovery.img works. I will confirm if the flashing option works during the next couple of days, but this helps understanding of why earlier attempts failed.
The Cubot Cheetah 2 gives no error messages if you are trying to start an incompatible recovery file, it just overwrites recovery with stock recovery and opens that.
This thread can now be closed
I confirm that my modified version works (flash or boot). I do not know how to modify the version info yet, so I cannot publish it.

Any idea on when you might be able to post some info on the modified build? Or even some instructions for us to try and follow your lead?

I would be happy to share my version but I am concerned that it is a ported version based on the current version in Needrom created by MDSdev and the opening screens reflect that ROM build info. If someone would advise me what the rules are regarding this I am happy to change it and then publish.
Alternatively I could finish writing out the process (already started) I went through so that I have a record and others can use it to port their own version, but each version created will also reflect MDSdev's original configuration information and this does not sit well as they did the hard bit of configuring TWRP to work with Cubot Cheetah 2 hardware and earlier Android (6.0/6.1). All I have done is get it working on a Nougat(7.0) version of the Cheetah 2. Advice from an expert in these matters would be helpful.

Gotcha, hopefully someone will
chime in, I would hope given the nature of xda, as long as those who input are acknowledged and recognised all should be well....

Cubot Cheetah 2 Android 7 Root by EpicFail2017
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017

Any idea why the IMEI might get lost? I'm aware that that can happen in mediatek stuff with custom, but is this due to a binary check of boot.img or one of the other ROMS? Or is it the spflash util acting up because of boot.img?
I've two of these phones at the min, one of them already has some issues so don't want to play with that one as of yet - power on issues and fingerprint sensor seems to act up - anyone else?
I'm already on nougat, and your procedure is exactly the same as I was thinking (already patched boot.img using magisk 14.0 but maybe I need use the beta as you did). I didn't get to the flashing of boot.img as I'm more comfortable doing flashing the partition straight from PC (adb/fastboot etc). I'm guessing mediatek can only be flashed safely with sptool? Do we need to reflash ALL partitions as IF we can, flashing boot.img to an upgraded phone should work without loss of data/imei? maybe?
What is the 'R' near the signal in your screenshots?

I'll answer my own questions with a way to root The Cubot Cheetah 2 (Nougat) in just a few minutes ..
I was already on the same version of nougat as the download before I started.
1. Download the ROM shown above and extract, grab the SPFlash too and the drivers. Ensure unknown sources is ticked, unlock bootloader - I also disabled pin security etc (dunno if this was needed).
* Note, install the drivers with the phone NOT connected via USB.
2. Transfer the boot.img to your phone and run it through Magisk (I used the beta 14.2 as documented above and manager 5.35), patch the image file (boot.img)
3. Move the patched boot.img from the magisk folder back to the computer.
4. Run the SPFlash tool load the scatter file, select DOWNLOAD and untick everything asides from boot.img
5. With phone switched off, connect it via USB
Flash
Wait until complete
Reboot
Rooted
No loss of IMEI or data.

It's good to see some responses. I seemed to struggle with TWRP and rooting for a while and now several options are apparently available. My personal opinion (I would say this wouldn't I!) is that if I can get advice on publishing/sharing the working version of TWRP on Cubot Cheetah 2, it is really simple to root the device by flashing TWRP, copy latest version of Supers.zip onto to SD card, open phone in recovery (Which is now TWRP), set English as default language (a one time action), install the Supers.zip. Job done, rooted with the best SuperSu facilities and an industry recognised backup facilities.
Unfortunately I have not yet had any advice on how to version the Nougat version from anyone on XDA yet and I am looking at trying to get MDSdev (the Cheetah 2 Marshmallow TWRP developer) to adopt the Nougat version.

That was my worry, not sure of compatibility of TWRP or boot time stuff on the mediatek devices. Rooting is now very very simple with the previous instructions, I was thinking flashfire or flashify or similar to push recovery onto the recovery partition but it's making sure TWRP is aware of the partitions. 10 years ago I'd have had a good look through the sourcecode for any possible problems but simply don't have the time these days :/
Love the phone but was put off using it as my primary phone due to lack of root. Okay I had to install stuff on the computer to flash this, but it's turned out it's very very easy and seems very safe too!

You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/

Android_Dog_Walker said:
You may like to note that MDSdev have now published a new version of TWRP that works on Nougat (this is also a later version of TWRP).
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Click to expand...
Click to collapse
EpicFail2017 said:
Hi Guys i have a Cubot Cheetah 2 Android 7.
Sorry my english sucks realy!
I found only a soulution to Root it with Magisk 14.2 beta!
1 First Step Download only PC Flash Files V14 170719 and unpack it !
http://forum.cubot.net/viewtopic.php?f=21&t=1475
The ROM this FilePC Flash Files V14 170719
https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
------------------------------------------------------------------------------------------------------------
2 Step Download and Install last version!
http://spflashtools.com/windows/sp-flash-tool-v5-1728
------------------------------------------------------------------------------------------------------------
3. Step
Download Magisk v14.2 Beta and Magisk Manager Version: v5.3.0, pu it on your SDCard!
Latest Stable Magisk Version: v14.2
Latest Magisk Manager Version: v5.3.5
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
----------------------------------------------------------------------------------------------------------------------------
4 Step
Download and unzip my Patched boot.img ,then Replace the boot.img in Folder from Step 1 !
https://mega.nz/fm/Q6YV3QrZ
http://www117.zippyshare.com/v/EiwE8p57/file.html
----------------------------------------------------------------------------------------------------------------------------
5 Step
Flash with SpFlash the Rom from Step 1 in Format +Download Mode.
Make a backup first from all your Stuff and Apps!
---------------------------------------------------------------------------------------------------------
6 Step
Start Android and make dev option enabel. Usb debug etc!
Install Latest Magisk Manager Version: v5.3.5 from SdCard!
Start and make under Options update beta kanal!
Install Magisk 14.2 Beta and rebot your Phone!
Wolla you have Root this ***** !
---------------------------------------------------------------
7 Step
Download Maui META ver 9.1724.0.00 to fix The Invalid Imei Problem after flashing!
For me this step was need after flashing root+room!
https://www.needrom.com/download/mauimeta-version-9-1724/
Mfg
EpicFail2017
Click to expand...
Click to collapse
Anyone uploading a mirror of nougat TWRP, please.
Also i´m kind of shy flashing the recovery with patched boot.img, any experience?
Someone with nougat and superSU here? Magisk seems to have some errors with some xposed moduls duo lag of "su-root-floder"
Do you password protect your recovery?

I have now tried the Magisk and TWRP routes to achieve rooting. My preference is the TWRP route because it has the fewest steps and works!.
An point worth noting is that if you are a new user on needrom, you need to register using Chrome, Firefox or other non Microsoft browser. Once registered Microsoft Edge works. I don't know why the registration with Edge fails but It is annoying when you complete the process and do not get the registration e-mail. Without registering you cannot get the TWRP download referenced above.

Hi,
Everything seems fine except if i make a wipe of dalvik cache every app stop working. The only solution is to wipe data or flash rom again with flashtool.
any can fix it on TWRP 3.1.1.1 ?

EpicFail i´m not sure, maybe security related issue. Instead of flashing rom i prefer restore backup^^
Still did not find a public nougat TWRP download
Both old 6.0 twrp freeze if timer is set and screen is going to turn off. Isn´t an issue anymore?
Today i hardly crashed system, it was in relation to magisk modul (busybox) update issue https://forum.xda-developers.com/apps/magisk/module-canstantly-module-updated-reboot-t3696943
EDIT: switched to supersu, busybox now working
Yesterday xposed appsops was getting a fix it is still unoffical
https://forum.xda-developers.com/xposed/modules/xposed-appopsxposed-appops-4-3-t2564865/page89
Edit:
updated to magisks unoffical xposed framework 3.1.4

Magisk 14.5 is officially in Beta

Just tested it this morning as all is working well. Now we are officially in the supported device (along side with Pixel 2 and 2XL). Thus means that we can now patch boot.img on the fly using Magisk Manager when there's an OTA update.
Steps would be the same as Pixel 2 series as our phones apparently using the same partition and logic method as the Pixel 2. Mentioned here : https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
I would suggest anyone who uses magisk snapshot build to upgrade to this latest version for proper magisk patching without TWRP. For minimal issue :
1. install magisk manager 5.4.1 (your current app will prompt for update usually, if not sideload from the official magisk beta xda forum.)
2. Uninstall magisk using the manager app, this will restore your boot.img backup. DO NOT REBOOT, just tap close.
3. Tap update/install magisk. It will then ask which method of installation. Choose install right now (recommend).
4. Reboot and wait, latest magisk should be installed after reboot.
Note : if the backup boot img is not stock, not available or is already patched. You'll need to boot to fastboot, flash your current build boot img. And then boot twrp to flash the magisk 14.5 flashable zip.
Full details here : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

[Umidigi One Max] Custom ROM, Modding, Rooting - Complete guide

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

System update 01/21

I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.

Bump

scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
You are on stable channel surely the notified upgrade is to version 10.0.11, so you can update and keep root and twrp working.
To do this follow the steps described by @strongst in the op7 forum and you will have no problems.
Here the steps to follow:
Optional but highly recommended, backup everything in case of issues.
Download the full rom zip file and the twrp zip installer file and place it into the phone storage memory.
Go to Magisk Manager and uninstall all modules.
Reboot phone.
Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, select the .zip file of the new firmware and wait for the installation to finish. Attention don't reboot yet!
Install TWRP within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+" select .zip file of the twrp recovery installer. Attention don't reboot yet!
Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot".
Finally reboot.
Reinstall your Magisk Modules.
Done! Your device is now updated and you keep TWRP and root.
Very important: At the moment this procedure is to be considered reliable only if used with firmware based on Android 10.

scuzzo500 said:
I've seen several posts that upgrading to Android 11 is causing serious issues with twrp and root. I have an update dated 01/21 that is ready to install and I'd like to know if I can install it and still keep twrp and root. I'm on stock model gm1925 build 10.0.9.gm27ba and as stated, keeping root is important for me.
Click to expand...
Click to collapse
As of right now there is no TWRP working some have had luck but unfortunately most havent. i have uploaded a patched boot.img that will let you root

how to install android 11 on gm 1925, if my phone does not see files via local update?????

[ROM][13][OFFICIAL][redfin][arm64] crDroid v9 for Google Pixel 5

{
"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.
Installation​After 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.
Installation​After 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.
Installation​After 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)