[Treble]Flash some (GSI) on the Razer Phone with wifi fix - Razer Phone Guides, News, & Discussion

[Treble]Flash some (GSI) on the Razer Phone with wifi fix - Razer Phone Guides, News, & Discussion

How to Flash Any Generic System Image with WIFI 100% working on Razer Phone
You have to follow exactly step by step or it will not work. But don't worry, all these step very easy & work if you don't miss any step.
Here some photos proof proving this all features and WIFI works:
{
"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"
}
As we know, actually there are some guides how to install any GSI on razer phone such as linuxct's guide (Link: https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684) and HO-COOH's guide (link: https://forum.xda-developers.com/razer-phone/how-to/treble-how-to-install-9-0-gsi-razer-t3883586), some of them can't not boot in GSI or wifi not work after root with magisk.
Follow this way, I'm sure after flash GSI, all feature work, special wifi 100% working.
Special thanks and credit to @linuxct, with lots of help from other members.
Working Features: GSI Image for Razer Phone
Almost all the important features are working perfectly fine with the GSI Image for Razer Phone.
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
ROMs GSI can be booted & root:
arrowOS - 9.x (crash for the first time)
Lineage OS 15.1 (most stable, recommend)
Resurrection Remix
HO-COOH and linuxct suggested Wifi still not work on these below GSI yet after root, so I'm not sure it
AOSP Android 9.0 Pie (if you choose this, it need flash a ndroid 9.0 Pie Gapps Package or you can download OpenGapps 9.0.)
AOSPExtended ROM (if you choose this, it need flash a ndroid 9.0 Pie Gapps Package or you can download OpenGapps 9.0.)
Pre-Requisite
flash_all.bat back to stock image from razer factory images [url]https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip[/URL]
SHA-256 Checksum: cf63490e488a49832da861693d070e01f78c62ebe7d0f0aa5568ed83739173bc
When restore original factory images complete. Connect the usb cable, boot into system, enable USB debugging and tick "Always allow from this computer" after pop up "Allow USB debugging?"
1.) Obtain boot.img from the latest Razer factory image. (If you are not already on the latest, best to just flash it using Razers guide to restore using factory image.) https://developer.razerzone.com/razer-phone-dev-tools/factory-images//
2.) Obtain TWRP.img and TWRP.zip from https://dl.twrp.me/cheryl
3.) Obtain Magisk from: https://github.com/topjohnwu/Magisk/
5.) Push 4 files to /sdcard by ensuring all 4 files are inside of your platform-tools folder, and following command: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v18.1.zip /sdcard"
Instructions to flash GSI
1.) Type: "adb reboot bootloader "
2.) Type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
3.) Once in TWRP, DO NOT SLIDE to allow modifications, but tap on Read Only. Go into Reboot, then make sure you're on partition A.
Now back, go Install, tap on 'Install Image' choose the boot.img you, and flash it as boot image.
Back into Reboot, move to partition B and repeat the step above.
Set the partition A as active, tap Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
4.) Go into Reboot, press on Bootloader.
5.) Razer phone, you should choose Image for ARM64 A/B device. Copy file GSI image, paste to folder Platform tools adb and flash the GSI system image onto your system_a partition, example you want flash Lineage 15.1 (system-arm64-aonly-gapps-su.img),
type: "fastboot flash system_a system-arm64-aonly-gapps-su.img "
6.) When flash finished. Type: "fastboot erase userdata && fastboot reboot ". If you skip this step, it will stuck boot into system with decrytion message or force enter password. Wait about 5 ~ 10 minutes, it will boot into system.
Root GSI with wifi 100% work.
After boot into system, you must enable "Android debugging".
You have to reload again 3 files to /sdcard with the following command: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v18.1.zip /sdcard"
1.) Type: "adb reboot bootloader " and "adb reboot recovery" or type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
2.) Once in TWRP, DO NOT SLIDE to allow modifications, but tap on Read Only. Go into Reboot, then make sure you're on partition A.
Go back, go in Install, tap on 'Install Image' choose the boot.img , and flash it as boot image.
Back into Reboot, move to partition B and repeat the step above.
Set the partition A as active, tap Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it. When finishes, do the same with the Magisk zip file.
3.) Reboot and check wifi, I guaranteed WIFI 100% work, if you stuck in TWRP, just type: "fastboot flash boot_a boot.img && fastboot reboot"
4.) Download newest Magisk direct in the phone, and install it. Don't install through adb.
Bonus how fix ctsProfile: false
1.) Open Magiskmanger, tap on Download, type: " MagiskHide Props Config", tap install".
and also download Busybox by type: "Busybox for Android NDK", tap install wait unstill finish. Now reboot.
2.) Open play store, searching: "Terminal Emulator", install it.
Run it, and
type: "su" enter, "props" enter, "1" enter, "f" enter (choose what kind of your devices from list, example me razer phone) I type "13" enter, "y" enter, "y" enter.
Done, now reboot and recheck SafetyNet status, all passed.
Watch this video more clear:
Now your phone fully Root and all main feature work. Thanks again for a lot help from many other forum's members. Every times, SafeNet status fail or broke,zero just repeat above steps then reboot.

I don't know whether it's my guide's flaw or something, there are indeed some GSIs just won't boot following my guide. (But some others boot just fine)
I will be very appreciate it if you can help testing the Pixel Experience Pie GSI here: https://github.com/EnesSastim/Downloads/releases
And sorry, I followed your guide exactly from stock, and latest Magisk v18.1 still breaks wifi on Android Pie. You can test it out yourself. (Because I see your post are the screenshots of Android Oreo with Magisk) linuxct replied to the issue in my guide by the way.

I tested Lineage 15.1 (system-arm64-aonly-gapps-su.img), ArrowOS 9.x, it worked like charm both of them with WiFi fix and not stuck logo boot or force enter passwords

bexiu said:
I tested Lineage 15.1 (system-arm64-aonly-gapps-su.img), ArrowOS 9.x, it worked like charm both of them with WiFi fix and not stuck logo boot or force enter passwords
Click to expand...
Click to collapse
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.

HO-COOH said:
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.
Click to expand...
Click to collapse
don't forget this command after flash arrowOS, you have to type exactly "fastboot erase userdata", don't try
Code:
fastboot format:ext4 userdata
fastboot format:ext4:0xc72dd3000 userdata
fastboot format:ext4:0xC72DD7000 userdata
, becuase it's not work in this case.
Rom Lineage 15.1, I tried this (system-arm64-aonly-gapps-su.img) from https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690

bexiu said:
don't forget this command after flash arrowOS, you have to type exactly "fastboot erase userdata", don't try
Code:
fastboot format:ext4 userdata
fastboot format:ext4:0xc72dd3000 userdata
fastboot format:ext4:0xC72DD7000 userdata
, becuase it's not work in this case.
Rom Lineage 15.1, I tried this (system-arm64-aonly-gapps-su.img) from https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
Click to expand...
Click to collapse
No luck. I followed the exact same steps on Arrow OS. Still breaks Wi-Fi. Can you post a screenshot with Magisk working on any Android Pie roms? I believe it's really like what linuxct said.
Oh, Arrow OS has serious bugs too. System UI is always crashing. And the NFC icon on the status bar seems fake.

HO-COOH said:
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.
Click to expand...
Click to collapse
HO-COOH said:
No luck. I followed the exact same steps on Arrow OS. Still breaks Wi-Fi. Can you post a screenshot with Magisk working on any Android Pie roms? I believe it's really like what linuxct said.
Oh, Arrow OS has serious bugs too. System UI is always crashing. And the NFC icon on the status bar seems fake.
Click to expand...
Click to collapse
I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS.

bexiu said:
I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS.
Click to expand...
Click to collapse
Yes I am talking about ArrowOs. I can't get Wi-Fi with Magisk on it. It's Android Pie and I think you can't install Magisk with any Android Pie roms.

HO-COOH said:
Yes I am talking about ArrowOs. I can't get Wi-Fi with Magisk on it. It's Android Pie and I think you can't install Magisk with any Android Pie roms.
Click to expand...
Click to collapse
Yes, I'm not try AOSP Android 9.0 Pie, as you said, I think wifi will not work on them.
I think you should clean first by WIPE advanced, tick: Dalvik/ ART Cache; System; Data; Internal Storage before rom back factory images. After finish flash factory images. you follow from this step: Instructions to flash GSI and Now root GSI with wifi 100% work..

bexiu said:
Yes, I'm not try AOSP Android 9.0 Pie, as you said, I think wifi will not work on them.
I think you should clean first by WIPE advanced, tick: Dalvik/ ART Cache; System; Data; Internal Storage before rom back factory images. After finish flash factory images. you follow from this step: Instructions to flash GSI and Now root GSI with wifi 100% work..
Click to expand...
Click to collapse
Then you should really change the title, because you still can't use Magisk to root Android Pie, but only Oreo. I would be very excited if Magisk could root Android Pie on Razer Phone, but still no.

sorry about that. I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS both work.
Ok, I changed title. I'm just happy, enjoy and share something when I can still custom flash some GSI 9 pie base on factory images razer phone. thank you anyway.

thank you so much!
this works great! however, i have an issue with my date and time when i reboot. whatsapp complains my date and time is incorrect (and microg crashes on boot, but i'm not sure it's related). sometimes it stays wrong and the date is set to 2018 (i then have to correct it manually because the internet doesn't work if the date is drastically wrong), but sometimes it corrects itself. it's not a major issue, but it's still annoying. and no, i do not have gapps installed and will not install gapps. thanks!

:good:
Great review, you made my day after trying other how-tos. Everything works like a charm, thx again

Related

[Treble][Pie]A full guide on how to install 9.0 GSI on Razer Phone on both A/B

I found linuxct's guide (Link: https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684) need to be modified to get 9.0 GSI working (at least in my circumstance). I haven't tried any Oreo Gsi but to my case, I can't properly booted to 9.0 Gsi by following exactly to this guide. That's why I want to write my own processes of getting it works. Hope it's useful to some of you.
0) I strongly recommend you to flash back to stock image from razer, if you have messed up with the partitions. !!THIS WIPES YOUR DATA, PLEASE BACKUP THE INTERNAL STORAGE!!
Code:
(Link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip)
After flashing to stock, it should automatically reboot into the system.
/*To your convenience, please put all the required file under the adb tool folder*/
1) Enable USB debugging, reboot to bootloader by command:
Code:
adb reboot bootloader
2) Flash the prebuild boot image in linuxct's guide by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
(Link is mentioned above)
This boot image has TWRP and Magisk built in.
3) Reboot into TWRP by command:
Code:
fastboot reboot
4) In TWRP, tap Wipe and do a factory wipe. DON'T CHANGE THE DEFAULT WIPE SETTINGS.
5) Flash the GSI you have, then reboot to bootloader.
6) Extract and copy the stock boot image from Razer to the adb tool folder, and flash the boot.img by command:
Code:
fastboot flash boot_a boot.img
7) Reboot to the stock recovery, and do factory wipe, then reboot to bootloader.
This will decrypt the /data. (I am not sure why if I do it under TWRP, I can never boot into system, but that's the case.)
8) Flash the prebuilt image from linuxct again by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
9) Reboot to the system by command:
Code:
fastboot reboot
And whola, you should be able to boot into system without any decryption message. And you will have a partially functional TWRP.
If you need to flash any other GSI next time, you should first copy the GSI image through MTP in system. Because the TWRP doesn't support adb command and can't be mounted as MTP.
Once you have copied the GSI image, you can reboot into TWRP and flash image as usual.

Here are the photos proving this works. I flashed Pixel Dust first through the command and booted. Then I reboot into TWRP and flashed PixelExperience through TWRP and get it booted.
{
"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"
}

Can't image I figured out to flash the second system_b so quickly lol.
0) In system_a, reboot to bootloader by command: adb reboot bootloader
1) Flash the GSI you have to system_b: fastboot flash system_b [The GSI you have]
2) Flash the stock boot image to boot_b: fastboot flash boot_b boot.img
3) Set active partition to B: fastboot --set-active=b
This is where I found linuxct's guide tricky because it should be 'b'.
'_b' doesn't work.
4) Reboot to stock recovery: fastboot reboot
5) Do a factory wipe, then go back to bootloader
6) Flash the prebuilt image to boot_b: fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
7) Reboot to the recovery: fastboot reboot
And it will brings you to TWRP on B partition, and you can reboot to system_b now.
And whola, and now you can have both AB system with different GSI. And you can switch to any partition by going to TWRP on either partition and switch as you like!
Here are the photos proving I have Pixel Experience and Pixel Dust working seperately on two partitions.

I also found that the prebuilt boot image from linuxct is breaking the wifi. Till now, you should have the TWRP patched boot image on both AB partition. So fixing that is pretty straightfoward.
1) Copy the stock boot image and TWRP installer zip to your phone in system.
Link: https://dl.twrp.me/cheryl/
I used the 3.2.1 version.
2) Boot into TWRP by command: adb reboot recovery
3) Flash stock boot.img on both A/B partition.
You can do this by first flash it to Slot A, and switch to B in TWRP. NO NEED TO REBOOT, SIMPLY SWITCH SLOT IN TWRP!!
4) Flash the twrp zip file.
This should fix your wifi.
DON'T FLASH MAGISK! I found flashing even the latest magisk v18.0 breaks wifi again.

So could you have stock on slot a and another GSI on slot b?

Magisk still breaking WiFi and 4g? I played around with 9.0 gsi's ages ago and that was the only thing stopping me from using it. Have anyone tried the latest canary builds of magisk also?

askylitangel said:
So could you have stock on slot a and another GSI on slot b?
Click to expand...
Click to collapse
Since A/B systems are using a common /data partition, I think you can at most flash an 8.1 Oreo on another slot because the stock image is 8.1. And this breaks the OTA of stock, so pretty meaningless.

It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting

parky169 said:
It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting
Click to expand...
Click to collapse
Follow the guide on #4, it will certainly fix Wi-Fi.

Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either

Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.

BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Pixel Experience, Pixel Dust, Aosp extended 6.1

BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Reboot after first boot fixes it.

parky169 said:
Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either
Click to expand...
Click to collapse
To clarify, you only installed on partition A, and installed magisk without breaking wifi?

Apologies for not clearing one thing up,I installed android 8.1 and it all
Worked I didn't realize at first it was android 9 that was having WiFi breaking,I haven't tried that one yet.sorry if I was misleading anyone
With my post.

All I had to do was flash the GSI image via fastboot and that seemed to work fine with no other flashing needed

What gsi ROM did you flash? And have you flashed magisk on it ?.

HO-COOH said:
I also found that the prebuilt boot image from linuxct is breaking the wifi.
Click to expand...
Click to collapse
Using an MR0 image on MR3 is not recommended, and using Magisk will break RIL (data connectivity) and WiFi.
If you want to run Pie GSIs, forget about using Magisk and run phh-su. Lastly, if you want your front camera and Bluetooth A2DP to work, use latest phh-gsi image v109. Using older versions than v108 is discouraged for breaking the mentioned.
Current status:
1. Cheryl specific overlays are not yet merged into phh source code because I'm a lazy assh*le. If you want your device to have Adaptive brightness, gestures, and fix the strong vibration, place the following apk inside /system/overlay or /vendor/overylay
2. Razer Power Service and NFC are faulty and will spam your logcat, which may, in the end, reduce your battery life. You need to extract [email protected] from both /system/lib and /system/lib64 from Razer's stock ROM and place them respectively into /vendor/lib and lib64. I've conveniently extracted them for you (Folder named 32's file should be extracted onto /vendor/lib and folder named 64's file should be extracted onto /vendor/lib64).
To kill NFC until we find a proper solution, go into your GSI's filesystem path /system/app/NfcNci and delete or change NfcNci.apk's filename into anything else, like NfcNci.bak.
3. Common to MSM8998, and I believe several other Qcomm based smartphones, Bluetooth In-Call audio is not working, and audio gets redirected to Earpiece.
4. Everything. Else. Works.
Please thank @phhusson for his amazing job in this project!
---------- Post added at 09:16 ---------- Previous post was at 09:13 ----------
As an extra, if you would like to erase your data/userdata partition without messing up with recoveries, you could just issue the following fastboot command:
Code:
fastboot format:ext4:0xc72dd3000 userdata
Where 0xc72dd3000 is the userdata partition size with FBE enabled.
If you are running a bootimage without FBE, the partition size might be 0xC72DD7000, so the command would be:
Code:
fastboot format:ext4:0xC72DD7000 userdata
--------------------
As a result, a summary of OP would be:
0. Flash latest cheryl fastboot image just like explained in OP.
1. Download the Android 9.0 GSI of your preference.
2. Reboot into fastboot.
3. Wipe your userdata partition with:
Code:
fastboot format:ext4:0xc72dd3000 userdata
4. Flash the system image you downloaded with:
Code:
fastboot flash system IMAGENAME.img
Where IMAGENAME goes your system image name. In our bootloader, you don't need to specify the partition you want to flash, and fastboot flashing into just "system" will flash the current slot.
5. Follow the steps from 1 and 2 from the Current status section above to get all the perks to work.

Tried multiple android 9 GSI roms and some boots but no wifi and data (some don't even boot).
Wifi fix (works on Arrow OS) on post #4 doesn't work. After flashing twrp 3.2.1.0, the phone does not boot on any android 9 GSI roms. Anyway thanks for your work trying to make GSI work on Razer phone.

Hello, I followed your instructions in post 4 to the letter, I've got 4g but no wifi. Any ideas what I'm doing wrong?

[Guide] [NO ENCRYPTION] TWRP with Magisk on a Pie GSI (RR)

THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
{
"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"
}
Grab these two files (Big Thanks to @mac12m99, @33bca (Offain on AFH) XDA Profile
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
Code:
adb reboot bootloader
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2. Boot up that TWRP.img file you downloaded above in this color
Type:
Code:
fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP
2a. Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Code:
fastboot flash aboot aboot_9.6.4.img
Then type:
Code:
fastboot reboot
4. Afterwards you shall go back to bootloader quickly
Type:
Code:
fastboot erase system
Type:
Code:
fastboot erase userdata
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
Code:
fastboot flash system GSI.img
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
Code:
fastboot flash userdata userdata.img
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .

reserved

Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks

GaryFisher88 said:
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
Click to expand...
Click to collapse
Not yet released to do so. Try the one from the dump.

Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter

It worked out the way you did.
only does not work for gcam and fingerprint reader

junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first

If you have goodix fp yes need to install daisy_global_images_V9.6.11.0.ODLMIFF first but If you have fpc fingerprint no need , work in pie base stock
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse

Flavien125 said:
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
Click to expand...
Click to collapse
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Everything works for me on RR at least

InfinityXDA said:
Everything works for me on RR at least
Click to expand...
Click to collapse
yes, for me too now
Except the notch

When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?

Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner

Ithao said:
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Click to expand...
Click to collapse
You must completely erase system with
Code:
fastboot erase system
and
Code:
fastboot erase userdata
and then flash the new version of RR
Code:
fastboot flash system “rr.img”
and reflash the userdata.img
Code:
fastboot flash userdata “userdata.img”
Otherwise you can’t update the stock version of the ROM that came with the device unless you provide a full store of 10.0.4.0 and test RR from there
The stable version of the stock ROM for RR is 10.0.3.0.

rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
Did you switch to RR from 10.0.4.0

rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
InfinityXDA said:
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Click to expand...
Click to collapse
try Genom kernel
i had included autofix for wifi)

eremitein said:
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
try Genom kernel
i had included autofix for wifi)
Click to expand...
Click to collapse
I have no problems what so ever I went to RR from 10.0.3.0!

can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader

barumbads said:
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
Click to expand...
Click to collapse
Use the 10.0.3.0 userdata file.That's what i used too
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
InfinityXDA said:
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
Grab these two files (Big Thanks to @Zerovoid from 4PDA, @Seryioo, and @mac12m99)
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Original Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2.Boot up that TWRP.img file you downloaded above in this color
Type:
It would boot into TWRP
2a.Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Then type:
4. Afterwards you shall go back to bootloader quickly
Type:
Type:
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
Click to expand...
Click to collapse
I have installed the gsi and it's working perfectly but now i wabt to get twrp on the phone how do i do it(i don't have encryption)?

a lot of thank for that.... iam waiting for that...lots of thank you admin...

If something goes wrong can we flash stock ROM and get the phone fixed? Does resizing the system/data partition affect the process of recovering the phone?

[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

My experience - PIXEL EXPERIENCE PLUS (A11) - GSI-Unofficial

Stable enough to be used as your daily driver.
This rom is not developed nor maintained by me!
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk
Download arm64-ab-11.0-xxxxx
or arm64-ab-vndklite-11.0-xxxxx
Download: Link
Extra tip: try Lawnchair launcher
Install like any other GSI Rom including the Nfc patch.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Quick and easy way to install GSI & NFC :
1. Extract the ROM .img file from the compressed file.
2. Flash extracted ... .img in fastboot , use command
fastboot flash system (file_name).img
3. In fastboot flash TWRP over eRecovery (!) - guide:
https://forum.xda-developers.com/t/rom-official-anne-9-lineageos-16-0.4151163/post-83603363
4. Run command fastboot reboot , enter TWRP (press and hold Volume Up)
5. In TWRP unmount all except SD Card , Vendor and System (unmount and mount again if needed) and flash NFC patch
6. Go back to the TWRP's main menu, select Reboot > Recovery.
7. Now you can perform factory reset in stock Recovery.
Note: the TWRP will remain instead of eRecovery.
MAGISK ROOT :
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1 - Guide
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
1. In TWRP flash Mount-fix .zip file
2. Reboot into TWRP
3. Select 'Install Image' and flash
patched recovery_ramdisk
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
over recovery_ramdisk.
4. Go back , select Reboot > Recovery.
5. Install Magisk manager apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
(SafetyNet
Contactless payments with Magisk v23.0 )
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset, also you can use dload method).
ROOT WITH SUPERUSER:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
Not working: VoLTE, LED notification (at least for me)
Screenshots:
{
"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"
}

-Alf- said:
Stable enough to be used as your daily driver.
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk for "arm64-ab" (not vndklite!)
or EMUI 8 for "arm64-aonly"
Download: here
Install like any other GSI Rom including the Nfc patch.
Not working: VoLTE, LED notification (at least for me)
Screenshots:
View attachment 5350493View attachment 5350495View attachment 5350497View attachment 5350499View attachment 5350503View attachment 5350505View attachment 5350507View attachment 5350509View attachment 5350511View attachment 5350513
Click to expand...
Click to collapse
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?

Fjord1 said:
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?
Click to expand...
Click to collapse
On Pixel Exp. some things work easier and more flexible . And I don't think it's just a placebo

Thanks so much I've been looking for an android11 pixel experience for the p20 lite
Can you use magisk with this?

joenuts2124 said:
Can you use magisk with this?
Click to expand...
Click to collapse
GSI rom is not related to recovery_ramdisk, so it is possible to use the Magisk root on any GSI roms .

I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?

Incomtus said:
I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?
Click to expand...
Click to collapse
Try this method
https://forum.xda-developers.com/t/migrate-custom-rom-migration-tool.4252863/
There are several options, I do not remember exactly, but I think that the best results I had with Flasher & Helper

Tried it but magisk is not working....

Incomtus said:
Tried it but magisk is not working....
Click to expand...
Click to collapse
...not at all, or for Migrate only ? And what about SuperUser?

DSU Loader not working, phone don't support?

joenuts2124 said:
DSU Loader not working, phone don't support?
Click to expand...
Click to collapse
DSU loader requires a/b partitions (two different system partitions).

-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
Doesn't emui 9.1 have ab?

joenuts2124 said:
Doesn't emui 9.1 have ab?
Click to expand...
Click to collapse
-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
It should be clear, hm?
"AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( on EMUI 9.1).
P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).

-Alf- said:
...not at all, or for Migrate only ? And what about SuperUser?
Click to expand...
Click to collapse
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann

Incomtus said:
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann
Click to expand...
Click to collapse
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.

-Alf- said:
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.
Click to expand...
Click to collapse
Very strange i made a clean install,
I went back to stock 9.1.0.132 with DLOAD
I unlocked bootloader and flash the rom with fastboot, i flashed TWRP (9.1) for nfc,
I made a wipe with stock recovery, I booted again on TWRP , i flashed magisk mount fix reboot again on TWRP flashed patched recovery on recovery, and exactly same issue,
I used the same twrp for nfc and magisk. Magisk aint working on last andy Yann build either but works on Emiritein Lineage Os build ( but this one is older)
Did you tried with last build?
For Pixel I tried superuser app on fdroid but doesnt work

Incomtus said:
Did you tried with last build?
Click to expand...
Click to collapse
9.1.0.257
Incomtus said:
For Pixel I tried superuser app on fdroid but doesnt work
Click to expand...
Click to collapse
And why not the superuser linked in OP? Okay, your choice bro...
I'm afraid I can't help you anymore.

I did not see there were an Superuser app in op I was confused with Andy yann forum I made a mix with that two posts
But it is strange that magisk doesn't work if it works for you
Do I have to flag magisk AND superuser ZIP file ?

Incomtus said:
flashed patched recovery on recovery,
Click to expand...
Click to collapse
Then you need boot Recovery to get root permissions (due to patched ramdisk)
Incomtus said:
I did not see there were an Superuser app in op?
Click to expand...
Click to collapse
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"

-Alf- said:
Then you need boot Recovery to get root permissions (due to patched ramdisk)
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"
Click to expand...
Click to collapse
Yes I know that I have to reboot on recovery that's what I did, as I use to do it with other GSI. But I did not understand I have to root with phh also

[GUIDE] Pixel 5 "redfin": Unlock Bootloader, Update, Root, Pass SafetyNet

If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"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"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

V0latyle said:
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Boot Verification.
On Android 12, disabling verity and verification will require a data wipe if it hasn't been done before. What seems to "lock" the state of boot verification is booting into system; so, if you perform an update, or flash vbmeta without the disable flags, then reboot into Android, you have essentially enabled boot verification and will require a wipe to disable it again. Confusing, I know.
Here is the appropriate update process. DO NOT take the automatic OTA if you are rooted. If you allow the phone to reboot after an update without disabling boot verification, you will have to wipe in order to disable it again, as you would need to for a patched boot image.
***Note***: The boot image doesn't have to be patched before you perform the update. Some have found it works better to update, THEN patch the boot image.
OTA Sideload:
1. Download both the OTA and the factory zip.
2. Extract vbmeta.img and boot.img from the factory zip.
3. Patch the boot image and copy it back to your computer.
4. Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
5. When the OTA completes, you will be in recovery mode. DO NOT REBOOT TO SYSTEM. Select "Reboot to bootloader".
6. Reflash vbmeta to disable boot verification:
Code:
fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img
7. Flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
8. Reboot to system.
Factory update:
1. Download the factory zip.
2. Extract boot.img
3. Patch the boot image and copy it back to your computer.
4. Reboot to bootloader.
5. Apply update:
Code:
fastboot update --disable-verity --disable-verification --skip-reboot image-codename-buildnumber.zip
6. Flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
7. Reboot to system.
Android Flash Tool:
1. Download the factory zip.
2. Extract boot.img
3. Patch the boot image and copy it back to your computer.
4. Reboot to bootloader.
5. Follow the instructions on the Android Flash Tool to update your device. The ONLY boxes you should check are "Disable Verity" and "Disable Verification"
6. When the update completes, the phone will reboot to system without root.
7. Reboot to bootloader and flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
8. Reboot to system.
REMEMBER: The most critical part of this is making sure verity and verification are disabled during the update process before the phone reboots. If you forget to patch the boot image, that's OK - you don't have to flash /boot right after update.
If you have trouble with the patched boot image, simply flash /boot back to stock and allow Android to boot, then re-patch and re-flash the boot image.
You can also, if you want, boot the patched image instead of flashing it:
Code:
fastboot boot magisk_patched-23xxx_xxxxx.img
This is considered "temporary boot" as it loads the image from your PC rather than from device storage. You can use this to confirm root works, and if you so desire, you can then perform Direct Install in Magisk.
Click to expand...
Click to collapse
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.

@V0latyle can you link me to a web page that would list every adb and fastboot command that we as android modders would use. What I mean is I couldn't find a Google search that listed the fastboot command with --slot=all among other adb and fastboot commands

Krsmqn said:
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.
Click to expand...
Click to collapse
I agree with @Krsmqn, @V0latyle THANK YOU FOR YOUR SERVICE !!!!! in the military and for your service in the xda community

I used the Android Flash Tool method to update to the November build, and followed the instructions precisely. It worked flawlessly. My deny list is exactly the same in Magisk, and all my modules are working perfectly. I didn't even have to disable them. I think I will use this method from now on.

Krsmqn said:
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.
Click to expand...
Click to collapse
elong7681 said:
I agree with @Krsmqn, @V0latyle THANK YOU FOR YOUR SERVICE !!!!! in the military and for your service in the xda community
Click to expand...
Click to collapse
Thanks guys, I appreciate it.
elong7681 said:
@V0latyle can you link me to a web page that would list every adb and fastboot command that we as android modders would use. What I mean is I couldn't find a Google search that listed the fastboot command with --slot=all among other adb and fastboot commands
Click to expand...
Click to collapse
Boy, I wish I had that handy, because I could sure use it too! I don't have your answer but hopefully someone else does, because believe me I'll be bookmarking it!

Will this work on Android Pixel 5a?

Rafiul Bari Chowdhury said:
Will this work on Android Pixel 5a?
Click to expand...
Click to collapse
Yes. The root process is exactly the same for the 4a 5g, 5, and 5a. The update process is the same across all Pixel devices.

I patched the boot.img. Magisk 23 did not report errors. But size of the patched file is zero. This looks not promising...

nostromo12 said:
I patched the boot.img. Magisk 23 did not report errors. But size of the patched file is zero. This looks not promising...
Click to expand...
Click to collapse
What version of Magisk did you use?

The stabil one

Will this work on Android Pixel 5a?
V0latyle said:
Yes. The root process is exactly the same for the 4a 5g, 5, and 5a. The update process is the same across all Pixel devices.
Click to expand...
Click to collapse
Okay. But Should I Remove Magisk Fully before upgrading through ADB/Fastboot/AFT?

H,
I'm on Android 11 pixel 5, can I use this tutorial ?

I think it's safer to unroot/remove Magisk and modules when going from 11 to 12 right? Some modules might not be compatible with 12 causing bootloops.

thecompany said:
I think it's safer to unroot/remove Magisk and modules when going from 11 to 12 right? Some modules might not be compatible with 12 causing bootloops.
Click to expand...
Click to collapse
You're going to have to wipe /data anyway if you intend to root on Android 12. Unless you're willing to try an idea I have.

Thanks V0latyle !!
I follow the flash tool method for update from october to november on my pixel 5
Perfect update, no issues and all data ok

nico22320 said:
Thanks V0latyle !!
I follow the flash tool method for update from october to november on my pixel 5
Perfect update, no issues and all data ok
Click to expand...
Click to collapse
Did you use Magisk canary? It is not necessary to check wipe in the android flash tool?
I use standard Magisk and can not change the update path to canary

nostromo12 said:
Did you use Magisk canary? It is not necessary to check wipe in the android flash tool?
I use standard Magisk and can not change the update path to canary
Click to expand...
Click to collapse
No i use the beta version of magisk.
You need wipe only for update from Android 11 to Android 12.
Just follow the guide for update to november and enjoy

nico22320 said:
No i use the beta version of magisk.
You need wipe only for update from Android 11 to Android 12.
Just follow the guide for update to november and enjoy
Click to expand...
Click to collapse
I want to upgrade from 11 (oktober) to 12
In the first message from this thread concerning the flash tool there was no wipe mentioned.
I want to update keeping my data ! How to proceed?

The best way: save yours photos etc with your Google account and make a fresh install with Factory image on Android 12 ( with disable verity and vérification)
It's long for set up device but 100% of chance of work with no issues for futurs update
Sûre you Can try to update without wipe and disable verity and vérification but maybe bootloops or not

Database Info

welcome