Database Info

[Guide] Yutopia [SAMBAR]: * Unlock * Install Custom Recovery * Root * EFS Backup *

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Warning: Rooting does not void Yutopia’s warranty, though damaging your hardware (i.e., burning up your CPU/Motherboard by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Lets begin
Index:
A. Drivers Installation
B. Unlock Bootloader
C. Install & Boot into Custom Recovery (TWRP) on Yutopia
D. Make A Nandroid Backup With TWRP Recovery
E. Root Your Stock Rom
F. Backup EFS and Other Partitions
A. Drivers Installation:
In order to Unlock, Root or Install Custom Recovery, you need to have the right set of Drivers to help your computer recognize your device. I used Windows 7 for this and it worked fine so should work for other windows as well.
Download and install Yutopia Drivers
https://drive.google.com/file/d/0B0pr-ZA5b-1pWFAwMmI4dWRGM3M/view?usp=sharing
Go through the setup, and when done, restart your PC. Connect your device to your windows and is shall recognize it
B. Unlock Bootloader:
Backup important files stored on your device before proceeding with the steps below, as unlocking the Bootloader will completely wipe/delete all files on the device.
After the installation of drivers follow the below to proceed with Unlocking the Bootloader of your Yutopia:
1. Enable USB Debugging, Uncheck Update Cyanogen Recovery & Activate OEM Unlock:
* Go to Settings > About phone, and then tap ‘Build number’ 7 times or until you get the message ‘You’re now a developer!’.
* Go back to Settings, choose ‘Developer options’. Find the ‘USB debugging’ option and use this toggle button to enable it. Accept warning by tapping on OK button.
In the ‘Developer options’. Find the ‘OEM Unlocking’ option and use its toggle button to enable it. It asks for your PIN/Screen unlock code, type it. Then accept the warning by tapping on OK button.
Also Uncheck Update Cyanogen recovery in developer options.
2. Boot your Yutopia into Bootloader/Fastboot mode. (Make sure you have backed up all important data as you’ll lose everything on phone in the steps below.)
3. Connect your Yutopia — in Bootloader mode — to PC. Let the driver install.
4. Open a command window on your PC. For this:
5. Open any folder on PC. Now, left click on empty white space inside the folder.
6. Hold shift key, right click on empty white space to get a pop-up and Choose Open command window here option from that. You will see a command window open up, with location directed to unlock folder.
7. Power off your phone then boot into fastboot mode (power + volume up).
8. Connect your phone to your windows via usb cable.
9. Confirm whether fastboot is working. With Yutopia connected to PC, run the following command in command window.
Code:
fastboot -i 0x2A96 devices
10. If device is connected you will get following kind of output:
86fsdy85 fastboot
11. If you dont get similar output it means that the drivers are not correctly installed or the device wasnt connected properly.
12. If the output is similar to above then run the following command:
Code:
fastboot -i 0x2A96 oem unlock
13. Now reboot from fastboot mode and thats it
Code:
fastboot -i 0x2A96 reboot
To confirm unlock status, reboot into bootloader/fastboot mode and you shall see the text unlocked now.
Code:
fastboot -i 0x2A96 device-info
C. Install & Boot into Custom Recovery (TWRP) on Yutopia
1. Download Modified TWRP:
https://drive.google.com/file/d/0B0pr-ZA5b-1pd2Z2YVR1cVZaeVE/view?usp=sharing
2. Enable USB debugging & Uncheck update Cyanogen Recovery from developer options once again.
3. Boot your Yutopia into bootloader mode.
4. Connect your Yutopia — in bootloader mode — to PC. Let the driver install.
Open a command window on your PC in the folder where you have the recovery.img file.
You will see a command window open up, with location directed to folder where you have the recovery.img file.
Let’s confirm whether fastboot is working. With Yutopia connected to PC, run the following command in command window. You should get a serial no. with fastboot written after it. If not, you need to reinstall the fastboot drivers from above.
Code:
fastboot -i 0x2A96 devices
(if the drivers are installed and device connected you would get the device serial number)
Flash TWRP recovery on your Yutopia by running the following command.
Code:
fastboot -i 0x2A96 flash recovery recovery.img
After that run this command:
Code:
fastboot -i 0x2A96 boot recovery.img
This will boot your device directly to TWRP
Or you can manually boot in recovery by unplugging the usb cable and then pressin POWER + VOL down until the device boots. When the YU logo shows up, relese the POWER and keep holding down VOL DOWN until TWRP boots up:
First boot into TWRP directly after flash is very important, Don't boot the OS on the phone as it may overwrite the recovery.
D. Make A Nandroid Backup With TWRP Recovery
Nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Please make this backup before you root, so that you possess unrooted system backup at all times which would come handy at the time of OTA updates.
E. Root Your Stock Rom
Download: The latest SuperSU on your device.
https://download.chainfire.eu/896/SuperSU/BETA-SuperSU-v2.66-20160103015024.zip
Reboot to recovery
Tap on Install > Browse and Select SuperSU > Swipe to Confirm the Flash
Once Done > Wipe Dalvik & Cache > Reboot System To Restart
To Confirm the root status use a root checker app from play.
F. Backup EFS and Other Partitions
1. Download Partitions Backup And Restore App from Here
2. Open the app and grant it root access.
3. Click on the Settings icon above and select preference to .img
4. Select the partitions marked in yellow and backup them by clicking on the download like button at the bottom right.
5. Go to the storage and search for the Partitions Backup folder there you will three .img files (modem,modemst1,modemst2) . Save them to your cloud and as many places as you want as they are very important files.
This way you can back up all other partitions too. (I recommend backing up all those that are not found in a factory image.
Now you possess an Unlocked YU - Yutopia with a Custom Recovery and Root Privileges
Cheers,
Funk Wizard :good:

Reserved for updates !!

Do you have make video tutorial?

I am using windows 10, 64 bit. Thease drivers are not working for me.
Sent from my HM 1SW using XDA Forums Pro.

Nevermind.

Modified TWRP link is dead
Hello,
The modified twrp link is dead. Please share a new link.

Alternate Link for Yutopia Drivers
Hi,
Can you please share an updated link for the yutopia drivers? This link seems to be broken.
Thanks a lot!

[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT

Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).

This worked great for me - thank you for the post!

Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?

I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....

Moto_Fan said:
Why would you patch the boot.img via Magisk Manager when you can just flash the Magisk v21.4 zip in TWRP?
Click to expand...
Click to collapse
Yes, that should supposedly work the same, although not personally tested.
Moto_Fan said:
I;m still confused AF why you would Patch the Boot.img with a working TWRP.img?
BTW: Are you passing safety net, not that it matters, but i figured i'd would on stock Android 10 at least....
Click to expand...
Click to collapse
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/

nor-ric said:
Yes, that should supposedly work the same, although not personally tested.
TESTED AND WORKED PERFECTLY!!!
Before flashing TWRP you need custom kernel.
Safetynet is ok, at the moment. Just need to flash this Magisk module: https://github.com/kdrag0n/safetynet-fix/
Click to expand...
Click to collapse
Yea, I already found out about the module, and it did indeed work and passed safety net after cts profile failed.
Now on too Pixel 4a #2 ON android 12 PDP1, too ROOT or NOT to ROOT??? We'll find out soon enough i guess???

nor-ric said:
Hello,
I'm posting this guide for those (like me) who can't do without TWRP on their device.
I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP: https://forum.xda-developers.com/t/twrp-3-4-0-0-for-sunfish-testing.4179101/
Credits to @Zackptg5 for his guide, from which I've started: https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
Credits to @topjohnwu for Magisk: https://github.com/topjohnwu/Magisk
DISCLAIMER: I don't take any responsibility if your phone explodes or anything... The guide is provided as is.
FIRST STEP: UNLOCKING THE BOOTLOADER
Download USB drivers for your phone here: https://androidfilehost.com/?fid=8889791610682922010
Download SDK Platform-Tools for Windows here: https://developer.android.com/studio/releases/platform-tools
Extract the SDK Platform-Tools to a directory of your choice.
Open your command prompt, change directory to where you extracted the Platform-Tools and type "fastboot". Depending on your Windows setup (I'm a linux guy, so I've used an ancient win8.1 installation in a VM...) you might receive a message of a missing dll (api-ms-win-crt-convert-l1-1-0.dll): if so, download and install the Universal C Runtime from https://support.microsoft.com/en-us...-windows-c0514201-7fe6-95a3-b0a5-287930f3560c
If you try the "fastboot" command once more, it should now work.
On your phone go to system settings -> About phone -> tap on 'Build number' several times until Developer Options is enabled.
Back out into settings and go to System -> Advanced -> Developer Options -> Enable 'OEM Unlocking'.
Switch off the phone.
Boot into fastboot by holding Vol Down + Power.
Plug the phone into a usb port of your pc.
In your command prompt type "fastboot devices". If there is no output, it means you have to install the USB driver. So, open "Device Manager" on your pc, right click on your Pixel 4A (should be on top of the list with a yellow exlamation mark) and update the driver choosing the USB drivers you previously downloaded. In Device Manger you should now read "Android Bootloader Interface", with no exlamation mark.
Now back to the command prompt, "fastboot devices" should now output a string with "fastboot" written next to it.
Now type 'fastboot flashing unlock' -> Follow prompt on the device to unlock the bootloader (note that this will FACTORY RESET the device).
The bootloader is now unlocked! You can now safely reboot (or it reboots on its own, I don't actually remember).
Note that after you unlock the bootloader you will see a reminder for a few seconds every time you reboot, reminding you that the phone is unlocked. That's normal and we have to live with that, as far as I know.
SECOND STEP: USING THE FACTORY IMAGE TO DOWNGRADE TO ANDROID 10
At present, TWRP is not available for Android 11. So we have to downgrade.
Download A10 factory image (version qd4a.200805.003) here: https://dl.google.com/dl/android/aosp/sunfish-qd4a.200805.003-factory-fac7c08d.zip
If you are paranoid like me, check the SHA-256 checksum of the download with some freeware hashing tool. The SHA-256 checksum should be: fac7c08d3d4cb92078fbcdbcc7e80fc4c438612a1a004d3d12814f51928458f3
Extract the files contained in the downloaded archive into the folder where your fastboot.exe is. To be clear, flash-all.bat should be in the same folder as fastboot.exe.
Place your phone in fastboot mode (Vol Down + Power).
Connect your phone to your PC.
In your command prompt type "fastboot devices" to make sure there is proper connection.
Double click "flash-all.bat".
The phone is going to reboot a few times. Just wait patiently until you read "Press any key to exit..." in the command prompt.
You've now downgraded to Android 10!
THIRD STEP: FLASHING A CUSTOM KERNEL AND TWRP
A custom kernel is needed for TWRP to work, because the stock kernel comes with no LZMA support. Just download the kernel provided by the same developer of TWRP (@nikamura): https://drive.google.com/file/d/1nuXc88t0Iokc0ha-AicOtZEUeGCGwQ-R/view?usp=sharing
And download TWRP, obviously: https://drive.google.com/file/d/1PZaU9PpYmdcAHlyi0zhNwEGnBsAHDW_E/view?usp=sharing
Place both the kernel and TWRP where your fastboot.exe is.
Note that since you just used the factory image you have to boot Android 10 at least once and run the first boot wizard, before you can flash the kernel and TWRP. Also, turn on "USB debug" in Developer Options (see "FIRST STEP" for how to reach Developer Options).
Now, connect your phone to your PC.
In your command prompt type "adb devices". Follow prompt on your phone to permanently allow the adb connection to your pc.
Type the following commands (without quotes):
"adb reboot bootloader"
"fastboot flash boot TKernel-sunfish_V0.1.img"
"fastboot reboot bootloader"
"fastboot boot sunfish_twrp201017-test5.img"
The phone should now boot into TWRP on-the-fly, but it's not been flashed yet.
Place TWRP file on your phone with the following command:
"adb push sunfish_twrp201017-test5.img /sdcard/"
Now in TWRP go to "Install" > "Install Image" > "sunfish_twrp201017-test5.img" > "Install recovery ramdisk" > Swipe.
Now back to the home of TWRP > "Reboot" > "Recovery".
The phone should now boot into TWRP! And this time it's properly installed (not just sideloaded).
You can now reboot into Android 10.
FOURTH STEP: ROOTING WITH MAGISK
Now, you need to grab your current boot image. To do this, boot into TWRP (Vol UP + Power) > "Backup" > flag only "Boot (64MB)" > "Options" tab > unflag "Enable compression" > "Backup" tab > Swipe.
Reboot to Android 10.
Disable "Automatic System Updates" in Developer Options.
Connect phone to PC.
If you browse your phone, in /sdcard/TWRP/BACKUPS/xxxxxxxx/xxxxxxx/ there will be a file named "boot.emmc.win". That's your boot image and you can rename it "boot.img". It should weigh exactly 64MB.
Download Magisk Manager apk (credits @topjohnwu): https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Copy Magisk Manager apk to your device.
Install Magisk Manager apk.
Open Magisk Manager. My locale is not English, so the following commands might slightly differ from what you will see, but still they should be easy to understand. Select 'Install' (Magisk) -> 'Select and Patch File' -> select your boot.img file -> 'Go!' -> it'll output the patched boot image to your Download folder.
Copy the magisk_patched_xxxxxx.img from Download folder to your pc, where your fastboot.exe is.
In your command prompt type:
"adb reboot bootloader"
"fastboot flash boot magisk_patched_xxxxxx.img"
"fastboot reboot bootloader"
You're now rooted!
Enter recovery to make sure TWRP is still working.
Reboot system.
Check in Magisk Manager the resulting installed version of Magisk is 21.4 (=rooted).
Click to expand...
Click to collapse
Would like to go this route for reasons you have stated above. Have a few questions:
1: If you use normally use Linux why did you use a Windows VM rather than simply do all operations in a Linux terminal?
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
3: Will SuperSuperuser be installed under this environment?
I have rooted several devices in the past using varied methods and things seem to have changed drastically since my previous Nexus 6p
Thanks

CarlInMO said:
2: After the above transition will SU required programs such as Titanium Backup and Adaway install and function as they have in the past? I had previously rooted current P4a and neither of the above programs would install?????
Click to expand...
Click to collapse
I did the above steps and titanium backup, root explorer and other root apps work great.
CarlInMO said:
3: Will SuperSuperuser be installed under this environment?
Click to expand...
Click to collapse
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.

JohnC said:
I did the above steps and titanium backup, root explorer and other root apps work great.
You will NOT use a separate SU app - Magisk has a built-in SU interface that will pop-up and grant SU permission when an app asks for it - just like the old SU app used to do.
Click to expand...
Click to collapse
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?

CarlInMO said:
Thanks for the quick response, again!!! I like this phone but it looks at this point as if it has a rather small following here. Are you using the stock build or have you moved on to a custom ROM?
Click to expand...
Click to collapse
Using stock android 10 image from google because TWRP and Edxposed are stable with android 10, not 11.

And what happens to root & TWRP after upgrade back to Android 11. I assume installed apps continue to operate OK

TWRP has now been modded and is working with A11! Details in the TWRP thread!

Rooting Mediapad M5 LTE/Wifi Lite

I don't like the Test Point method, so You need: Twrp - this edition works: https://drive.google.com/drive/folders/1FoRLBMyQnL1B3lU8bZCqfGL7y_mkeJfk. You need to use HCU, part of the DC Unlocker software. The Magisk.zip needs to be placed in the tablet's folder on the SD card preferably. The tablet must be set to 'transfering files' and the Background Settings, USB port setting, obtained by using the dialler * # * # 2846579 # * # * or the calculator (I believe) for the WiFi version, to Manufacture Mode. So, with the tablet in the operational mode, not Fastboot or anything else, plug it in to the PC. Buy the time-limited mode for HCU and then log in to it. Press read phone info, give it a minute or so then press unlock, after the info states that it detects the phone. The Bootloader should be unlocked, not as in the Developer Mode/OEM Unlocked with USB Debugging selected, which are also necessary. Once you have unlocked with HCU, boot into Fastboot - vol down + power buttons. You should have the minimal ADB folder on the C: drive. Place the TWRP8.img in that folder.Navigate to the ADB folder in your command prompt, something like: CD\ then CD ADB. You should now be in the ADB folder. Type: fastboot flash recovery_ramdisk twrp8.img NOT fastboot flash recovery twrp8.img. Do a reset of the phone in Recovery Mode and it should then boot in TWRP. Flash the Magisk.zip with TWRP. Restart the tablet. You may have reset the tablet in Recovery Mode again to get the TWRP recovery working. You should now have root with Magisk after the tablet re-boots. I did not flash Disable DM Verity. (Earlier, I tried using Magisk to convert the ramdisk.img from the Update.App to gain root. I flashed it with Fastboot but it did not work, it ended in a boot-loop which I could not stop by any means.)

[Guide] Android 11 on PH-1 - what worked for me

[Disclaimer: Should anyone decide to follow these instructions, they will be doing so at their own risk. Bad Things™ could happen, and you, and you alone, my fellow traveler, are responsible for your choice to follow this path, and for understanding and accepting full consequences of flashing non-OEM phone firmware. I, myself, do not have enough know-how to help you should things turn not as expected, as all the heavy lifting has been done by others, and I thank them all. Support those that support us!]
Some background; after the post [https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/] that introduced me to using GSI (Generic System Image) builds as daily drivers, I’ve tried a handful of them (as collected on P.H. Husson’s treble_experimentations page) with a varying degree of success. The build that has delivered the smoothest experience out-of-the-box for me has been the Octavi GSI [https://octavi-os.com/].
-- What’s needed --
- From this page download - Essential PH1 window drivers and The latest official ROM
- Download Android build tools, AOSP.zip given in this post, and this OctaviOS GSI build for full Google experience [some other builds are on this page. NOTE: PH-1 takes ARM64, ab (system-as-root), and project Treble (the vndk part) compatible variant.
-- The work –
- Preparations: (Refer to this page for the excellent overview on working with ROM images done by Vigasaurus, especially the section How to Flash (for Fastboot only)).
On the desktop:
- Install Essential drivers
- Create a work folder, let’s say A11, and unzip the platform tools files (from the ‘platform_tools’ subfolder) there. This folder will then have ‘adb’, and ‘fastboot’ executables.
- Unzip the content of PH1-Images-QQ1A.200105.032.zip to A11
- Unzip the content of AOSP.zip to A11 overwriting all (3) files.
- Unzip OctaviOS firmware to A11 folder
- Open command line and go to A11 folder
- connect the phone to your computer
Then type:
Code:
adb devices
(the response should be a string of numbers (the phone's serial number) followed by the word ‘device’
On the phone (if not done already):
- Tap Settings, then tap System > About phone and scroll to the bottom of the page, then
- Tap Build number multiple times until you see the pop-up message “You are now a developer”
- Go back one screen to System, then tap Developer options and enable OEM Unlocking and USB debugging.
Back on the desktop type:
Code:
adb reboot bootloader
and if not done already, type:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
then:
Code:
fastboot set_active a
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
After phone reboots type:
Code:
adb root
adb disable-verity
adb reboot bootloader
Now, edit flashall.bat to replace ‘system.img’ with OctaviOS image. In my case those two lines look like this:
Code:
fastboot flash system_a OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
fastboot flash system_b OctaviOS-v2.9-arm64_bgN-vndklite-20210918-Official.img
- Save and run flashall.bat
At this point your device will boot the new firmware. If how you use your phone does not require rooting, you are done. Go through the initial setup steps and profit!
For those who need root:
- Download Magisk Manager and put, and install it on your phone.
- Enable Developer (as above) and USB debugging
On command line in A11 folder push the Magisk app and boot.img to the phone:
Code:
adb push boot.img /sdcard/Download
adb push Magisk-v23-0.apk /sdcard/Download
On the phone, install the Magisk app and start it up.
then
Tap Install, tap Method, then select file, and choose the boot.img from Download folder
Back on command line:
Code:
adb shell ls /sdcard/Download
adb pull /sdcard/Download/[name-of-magisk-patched-image]
adb reboot bootloader
fastboot flash boot_a [name-of-magisk-patched-image]
fastboot flash boot_b [name-of-magisk-patched-image]
fastboot reboot
Then, back on the phone:
- Start Magisk app
- Tap settings icon (upper right) and activate MagiskHide
- Exit and tap Check SafetyNet to make sure it’s all good.
Now, profit!
[Final advice: I've turned off any AOD, Daydream, and PocketDetection settings, as they severly impact battery use. After that, it's been smooth sailing]

Infinix zero 5g 2023 TURBO X6815C (bootloader unlock/root/system-r/w) Ant-Man and the Wasp: Quantumania Edition

root infinix XOS 12 (Android 12)
Infinix Zero 5G Ant-Man and the Wasp: Quantumania Edition
Easy unlock
1. Enable developer options and turn on/allow OEM unlocking and enable USB debugging
2. Reboot to fastoot
Code:
Code:
adb reboot bootloader
3. Unlock bootloader via fastboot (you will be prompted to accept yes with volume up on phone.
Code:
fastboot flashing unlock
4. Setup and install MTK client Linux (fallow guide)
[GUIDE] [MTK] How to use MTKClient and set it up!
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk) I am writing this guide especially for the RM6785 community. This tool is very useful...
forum.xda-developers.com
4. backup all partitions with MTKClient/MTKTool GUI (launch the mtk_GUI with su/root)
in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
5. copy boot_a.bin to your phone internal for magisk patching manually on phone
(Time of writing latest)
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
6. Rename (magisk renames the default .bin)
patched_boot_a.img to patched_boot_a.bin
7. Copy patched boot_a back to your computer/home folder.
8. flashing.
From fresh started Android reboot to fastboot.
Code:
adb reboot bootloader
DO THE NEXT 2 STEPS AT THE SAME TIME IN FASTBOOT.
(Fastboot commands)
Code: terminal
Code:
fastboot flash boot_a /path/to/patched_boot_a.bin
Code2: (disable verity/secure boot) use vbmeta_a.bin that you backed up from you're phone.
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a /path/to/vbmeta_a.bin
AFTER flashing above you should now have root
############## system r/w#############
If you want system R/W writable (full root) fallow next steps.
1. go to system r/w website and get this version tested here.
Official SYSTEM-RW v1.41 by lebigmac for Samsung Galaxy S23 Ultra and other devices
lebigmac's software
lebigmac
www.systemrw.com
Link to file above
11.21 MB file on MEGA
mega.nz
This must be run on the phone!
Step 1
Decompress (7zip) SYSTEM-RW_v1.41.zip to this directory on device. sysrw_1.41
Code:
/data/local/tmp
Step 2 in Android terminal type
Code:
Code:
su
cd /data/local/tmp/sysrw_1.41
chmod +x sysrw
./sysrw
This will build the new patched r/w super.bin in /data/local/tmp/sysrw_1.41/IMG
Use file explorer (fx-file explorer) to copy patched_super.bin to phones internal/storage and then copy to computer to flash with fastboot.
Step 3
Code:
On computer/PC with adb and fastboot flash super. (Should be around 8gb file)
Code:
Code:
sudo adb reboot bootloader
sudo fastboot flash super /path/to/patched_super.bin
sudo fastboot reboot
########################
Enjoy system r/w[/code]

Lposed

CPU Demensity 1080, can play most emulators (dolphin/athersx2) at 30-60 FPS,a really powerful gaming phone

Phone
Infinix Zero 5G Ant-Man and the Wasp Quantumania Edition

Any help please

Can elaborate this please. Im stuck at this step

Mtk-client has a user interface see photo
Step4 in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin

Still can not change SELinux to permissive or install.... some madgisk modules..?? Assuming because the boot is reed only, wish system r/w worked on boot to as it contains the kennel..

Hi what version is your device? Is it v810? I was wondering if your device can boot into BROM mode.

Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again

notreal456789 said:
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
Click to expand...
Click to collapse
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again

Hnojohn said:
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Click to expand...
Click to collapse
This is why I don't update things, also it could be the setup Maby I'll post a Linux.iso with mtk client setup correctly

I still use Android apps from 2008 that still work on Android 12 fine