Related
UPDATE - Pixel Experience Official is out for Kenzo. Link attached below. Ongoing support for GSI users though.
https://forum.xda-developers.com/redmi-note-3/development/rom-pixel-experience-t3835648
-------------------------------------------
Disclaimer: I'm not responsible for bricked devices, flash at your own risk. I might be able to help with restoring your device though.
This is a guide to installing Android GSI on Redmi Note 3 (Kenzo)
---------------------------------------------------
What works-
RIL
GPS
Camera
Pretty much everything
What doesn't work-
Bluetooth
Hotspot
VoLTE(I couldn't test)
(NOTE - Bugs vary GSI to GSI)
---------------------------------------------------
Required files -
Grab these files first, and keep them on your SD card
TWRP Treble - https://androidfilehost.com/?fid=5862345805528059847
Android GSI(USE ARM64 A-ONLY) - for this tutorial, I'm using Phhusson's AOSP Pie GSI found here - https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
List of GSI's - https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Pie GApps (If using Pie GSI) - https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141
Vendor Image - https://androidfilehost.com/?fid=1322778262903993757
Permissive SELinux Enabler - https://drive.google.com/file/d/1KFdPH2JGtvkXwt2emxPb-k7zdv2pLd-F/view?usp=drivesdk
Magisk 16.7 (minimum 16.7, you can use 17 as well)- https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Latest Firmware - https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361/page176
Optional - Digital Well-being (ONLY FOR PIE)
Digital Well-being apk (Download latest version) - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
Digital Well-being Magisk Module - https://drive.google.com/file/d/1AAFMWbAAK-febiP9h4iZMJONEHXopmEU/view?usp=drivesdk
--------------------------------------------
Assuming you have an unlocked bootloader, and know your way in and around Android, let's begin!
How to install -
1. First, flash the Treble enabled TWRP.
2. Reboot to recovery.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file and immediately flash the Permissive SELinux Enabler.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
8. Reboot to System.
9. Reboot to recovery.
10. Perform a factory data reset, and flash GApps
11. Reboot to System, and complete setup.
12. After completing setup, reboot to recovery and flash Magisk 16.7
13. Reboot to System
14 Reboot to recovery and flash firmware.
15. Profit!
If you want Digital Well-being (ONLY FOR PIE) -
16. Install Digital Well-being apk
17. Flash Digital Well-being Magisk Module through Magisk Manager
18. Reboot
19. Profit!
-------------------------------------------------------
Tested on Snapdragon version, don't know if it works on MTK.
Screenshots are attached.
Fixes -
If you have the QS toggles moving out of the header like the screenshot attached in #1, do the following steps
1. Enable Developer Settings,
2. Find Smallest Width setting
3. Increase the value by 20. (If it's 360, make it 380)
4. Profit!
------------------------------------------
Google Camera + Face Unlock fix.
If Google Camera/Face Unlock doesn't work for you, do the following -
1. Reboot to recovery
2. Mount system
3. Flash the zip file (download link below)
4. Clear cache
5. Reboot to system
This should make Face Unlock work again, and GCam work as well.
Download patch - https://drive.google.com/file/d/17OUBxhsfeK0625_pYe8aRNr5L6doKdAK/view?usp=drivesdk
------------------------------------------
Can't find Smart Lock in settings?
1. Go to Settings < Security and Location.
2. Scroll down and click Advanced.
3. Click Trust Agents.
4. Switch on Trust Agent for Smart Lock.
You should now have Smart Lock option below Fingerprint.
-------------------++++++++++++++++-----------------------
For Changing accent colours -
Download this file - https://t.me/kenzousersglobal/1169
1. Flash it in recovery
2. Reboot to system
3. Go to Settings - Display - Advanced. Scroll down to find "Colour Theme"
4. Select colour theme and select colour of your choice.
5. Profit!
---------------------------------
Custom kernels that currently work
Radon - https://drive.google.com/file/d/1LYggpHDVph1fvWctIKY4FqQwtRb6Svh0/view
---------------------------------
Review - after extensive testing, I found this to be daily driver material, with the only exception being Bluetooth, Hotspot, and VoLTE(I couldn't test it myself)
Special thanks to - @corkiejp
Is it possible to get an Overlay Patch for Mi 8?
NielsvdS said:
Is it possible to get an Overlay Patch for Mi 8?
Click to expand...
Click to collapse
I honestly have no clue. I have only gathered all the patches and files for Kenzo and made them into one guide.
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Work on kate devices?
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
sharan565 said:
Why is it there system.img.xz should I remove .xz rename it
---------- Post added at 04:24 PM ---------- Previous post was at 03:42 PM ----------
1.flashed carlosvendor.zip
2.mounted system vendor cache
3.flshed system.img as system image
After rebooting stuck at fastboot logo
Click to expand...
Click to collapse
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
corkiejp said:
You need to extract the image file from that compressed format, use windows are download an app that will extract it.
Suggestion RAR from play: - com.rarlab.rar or alternative app that will do the same.
Click to expand...
Click to collapse
Thanks man I will try
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
3. Mount all partitions, and wipe all partitions.
4. Flash the Vendor Image zip file.
5. Clear Dalvik/Cache.
6. Mount all partitions, and wipe system.
7. Flash GSI to System partition *only*.
Click to expand...
Click to collapse
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
wxtester said:
Hey @Sid127, this is really nicely written tutorial, thank you What bothers me, why we need to mount partitions once again in step 6? Partitions were mounted in step 3 and there wasn't any reboot in meanwhile.
Second question, maybe easier... If I have existing TWRP backup for non treble ROM, is it OK to restore such backup using Treble recovery after wiping everything? Or it's recommended to flash previous recovery first?
Click to expand...
Click to collapse
1. You just need to make sure that all partitions are mounted.
2. You can restore the backup through Treble TWRP.
Happy flashing!
Hexvessel1992 said:
Work on kate devices?
Click to expand...
Click to collapse
I don't know, I need someone to test it. It should work, since the Vendor for Kenzo and Kate are the same.
corkiejp said:
Thanks for the guide: -
Digital Well-being apk (Download latest version) <<<< Links to the overlay zip and not the apk.
Sourced the beta of apkmirror: - https://www.apkmirror.com/apk/googl...wellbeing-0-2-207862754-android-apk-download/
I used Mind the Gapps found on Telegram, when flashing.
Is it possible to dirty flash open gapps?
Click to expand...
Click to collapse
I'll update the thread with the right link
I think it is possible to dirty flash Open Gapps, but it might give bugs, always go for a clean flash
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
srishant said:
Everything works for me, only thing was that at the first setup it was stuck on "checking for updates". So I tried the method of tapping all sides of the screen (from top-left clockwise to bottom-left) and it skipped the setup. The flashlight is a little wonky, but that's the only thing that was getting in my way. The audio was a little too quiet, so I installed some app on the playstore to gain it. Thanks for such a comprehensive guide! Android Pie is amazing, but development for it on a 3 year old device is even more so!
Click to expand...
Click to collapse
I had to forage through 4 complex guides, scourge through XDA and Telegram for all the patches, and hence could make such a simple guide. Apparently, devs on the Telegram channel are working on the Bluetooth and VoLTE fix I'll update once that happens!
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
amog787 said:
Bolte
Test n let me know if it works
https://t.me/kenzoromnews/1445
Modify for treble then flash
Click to expand...
Click to collapse
I did see that, but when I flashed it, it messed upy system and I had to reinstall the GSI. I don't know how to modify it for Treble, could you do it? I'm happy to test. I believe that fix is for Flashavle ZIPs, not for Treble GSIs.
Possible Gcam and stock working patch!
Posted this in AOSP Pie Rom thread, may also work for the GSI?
corkiejp said:
I found Gcam Pie Fix for another device in this thread.
Link to Gcam Pie Fix: - https://drive.google.com/file/d/1D5qvlA-QbQu6xoWpsLPyWquMkS3hxXi3/view
Gcam that I'm using: - https://androidfilehost.com/?fid=673956719939833577
^^^ From this thread, maybe newer versions available.
I was able to setup face unlock after flashing the above fix, you may also need to enable Smart Lock (Google) as a trusted agent.
It is buggy and the face option may not always trigger, plus you need to hold the phone far from you and swipe when the lock symbol appears (no fast unlock options xposed).
Another benefit of flashing another Camera (V 2.0.002) Started working as well. (Don't know if that is the default AOSP camera or something I restored from backup? Could be Snap Camera from LOS).
Click to expand...
Click to collapse
corkiejp said:
Posted this in AOSP Pie Rom thread, may also work for the GSI?
Click to expand...
Click to collapse
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Sid127 said:
Is there also an uninstaller for this fix? I'll test only if there is an uninstaller for it. Last time I tested a fix I had to format data to revert...
Click to expand...
Click to collapse
Not that I'm aware of, but this just places/replaces some Lib and Lib64 in system partition.
If your worried about it, back up your system partition, flash the this patch and wipe caches.
If you experience problems, just restore your system partition.
It was reported working by someone else here.
Hello !
October update is available.
Lets talk about it?
Confirmed, October patch rolling! Downloading!
prannoytambe said:
Confirmed, October patch rolling! Downloading!
Click to expand...
Click to collapse
That was news yesterday?
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
jcunltd said:
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
Click to expand...
Click to collapse
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Letitflow said:
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Click to expand...
Click to collapse
anyone knows why the update size is so much smaller than the beta testers got? thanks
installations fails on my phone.
Voniaak said:
Hello !
October update is available.
Lets talk about it?
Click to expand...
Click to collapse
I noticed, when scrolling, I rarely get accidental taps. I used to get them a lot with September update.
bavmouse said:
installations fails on my phone.
Click to expand...
Click to collapse
Did you restore stock boot image and not modify the system partition?
Benjamin_L said:
Did you restore stock boot image and not modify the system partition?
Click to expand...
Click to collapse
that's possible. how can i modify ? thanks.
bavmouse said:
that's possible. how can i modify ? thanks.
Click to expand...
Click to collapse
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
i bricked my device and restored it with fastboot flash.
CPU frequency stuck at 100% bug still exist. Work fine for 10 mins after reboot, after that stuck at 100% again.
yes. I can confirm, that after using FP sensor, CPU stuck at 100% load. :/
Why do we need to repeat this in this thread. Everything has already been mentioned before in other threads.. Doesn't help when someone is looking for information
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Before trying this, I suggest you to backup your files.
Verify the system version in Settings > System > About the device > Version number and download the same version installed in your device:
V9.6.10.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.14.0.ODIMIFE
V9.6.15.0.ODIMIFE
Unzip the package (7zip works perfectly to this job) and copy the files boot.img and system.img
1) Copy system.img and boot.img into adb folder
2) go to "settings > system > developer ... > USB deployment and enable it
3) plug you device on your computer, turn it off and turn it on again while holding power + volume down until your screen shows the Xiaomi bunny and "Fastboot".
4) in Fastboot, type "fastboot devices" and make sure your device is listed.
5) in Fastboot, type "fastboot flash system system.img" (without quotes) and wait it finishes.
6) in Fastboot, type "fastboot flash boot_b boot.img" (without quotes) and wait it finishes.
7) in Fastboot, type "fastboot flash boot_a boot.img" (without quotes) and wait it finishes.
8) in Fastboot, type "fastboot reboot" and unplug your device.
This works for me, maybe works for you.
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Mounting system makes otas impossible already so follow the instructions before my post
New update today...
After yesterday an update was delivered, I am now offered a new update. The installation is now running. I noticed after yesterday's update that there were significant "memory / processing delays", which had previously not occurred on my device. The update is 203 mb, yesterday only 103.5mb were delivered.
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
antoinejr1111 said:
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
Click to expand...
Click to collapse
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Click to expand...
Click to collapse
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Viva La Android said:
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Click to expand...
Click to collapse
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Click to expand...
Click to collapse
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
angadsg said:
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
At the boot logo connect to adb. Make sure its recognized and issue the following command: adb shell setprop debug.stagefright.ccodec 0
Sent from my SM-G975U1 using XDA Labs
Viva La Android said:
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
Click to expand...
Click to collapse
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
antoinejr1111 said:
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
Click to expand...
Click to collapse
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Viva La Android said:
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Click to expand...
Click to collapse
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
antoinejr1111 said:
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
Click to expand...
Click to collapse
My only dilemma there is that I've got multiple projects going right now for various LG and Motorola devices. However, I fully plan on future development for the Onn series of tablets (primarily the newer Onn Surf series due to Treble support). As soon as my schedule permits, I'm on it. Here's the beauty with Project Treble: if an Android 10 GSI will boot on the Onn Surf 10.1, it is almost certain that it will also boot on the Surf 8. Out of curiosity, what is the allocated /system partition size on the Onn Surf 8? Is it the same as the Surf 10.1? Also, I noticed recently that there are some rather slim GSI builds of Android 10 (Go Edition). Some of these might be worth looking into.
First up, shoutouts to both @phhusson and part of this thread from @YOisuPU for vital guidance throughout my first journey with super-partition devices.
A51 5G runs on Exynos 980 unlike the 4G variant which runs on Exynos 9611. People have been running into trouble rooting the 4G variant and even resorted to GSIs just for rooting, but on the 5G variant all you had to do is to patch boot+vbmeta (don't include recovery) with Magisk. If you just need root, stopping here is enough.
For me, running my LOS GSI is absolutely necessary, but Android 10's super-partition compounded with Samsung not making fastbootd available means an even harder time than what I've had with A60/M40. Below steps apply to this device and might also serve as a general skeleton for other Samsung devices with super-partition.
0) Get Linux - some tools used here just don't have a Windows version
1) On stock firmware, open shell and run
Code:
lpdump
to get some partition info that'll be used next - example output here
2) Get stock firmware
3) Extract super.img.lz4 from AP and then super.img (sparse) from super.img.lz4 with your tool of choice (e.g. 7-Zip ZS)
4) Unsparse super.img:
Code:
./simg2img super.img super.raw.img
5) Extract partitions from super.raw.img:
Code:
./lpunpack --slot=0 super.raw.img <dir>
6) Replace system.img in <dir> with GSI image
7) Repack your own super.img:
Code:
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:7549747200 --group main:7545552896 --partition system:readonly:2147483648:main --image system=./system.img --partition vendor:readonly:729890816:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Compare the command to the lpdump output obtained earlier - many of the numerical parameters here directly match. For the 3 partition declarations, assign them sizes equal to or larger than (recommended) their byte sizes.
8) Compress your super.img into a tar and flash it via Odin in the AP slot
9) Make sure that the device runs patched vbmeta (but stock boot image - somehow the patched one causes a bootloop on GSIs), do a factory reset in stock recovery, reboot
simg2img, lpunpack and lpmake binaries can be obtained online (e.g. from the aforementioned thread) or built from source.
By the way, I've fixed some sepolicy issues with PHH's Superuser, so in future builds, unlike what was described in the thread, 4G variant users likely won't need a permissive kernel to get root on GSIs (at least it doesn't here).
When i lpmake i get invalid sparse image header
blackbuga said:
When i lpmake i get invalid sparse image header
Click to expand...
Click to collapse
Can be safely ignored.
AndyYan said:
Can be safely ignored.
Click to expand...
Click to collapse
"Patched vbmeta.img " where can I find this or is it patched by magisk im assuming
I'm unsure where you are getting the sizes for the partitions, could you please elaborate on that? The rest is self explanatory.
PizzaG said:
I'm unsure where you are getting the sizes for the partitions, could you please elaborate on that? The rest is self explanatory.
Click to expand...
Click to collapse
Sub-partition sizes are arbitrary, as long as they can contain the respective content (e.g. system has to be larger than your GSI) while still fit inside super.
blackbuga said:
When i lpmake i get invalid sparse image header
Click to expand...
Click to collapse
其他型号的手机修改super.img 最后打包的时候也可以使用么？ lpmake 这个文件提取到system.img同目录执行？还是在复制system.img文件到otg\bin文件夹下执行？
并不很明白 ./lpmake ....命令各个参数的意思。
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
lpmake这个文件提取到system.img同目录执行？还是在复制system.img文件到otg \ bin文件夹下执行？
并不很明白。 / lpmake ....命令各个参数的意思。
lpmake文件提取到system.img同目录执行命令后 出现了错误.
AndyYan said:
Sub-partition sizes are arbitrary, as long as they can contain the respective content (e.g. system has to be larger than your GSI) while still fit inside super.
Click to expand...
Click to collapse
-metadata-size 65536 65536 Does the number represent partition size or permissions? Will the numbers never change?
-metadata-slots 2 The slots2 parameter will never change?
-device super:7549747200 Does this number represent the total generation of the super partition?
-group main:7545552896 What does the back number mean? The total size of the other three partitions?
Thank you
lkj00 said:
lpmake文件提取到system.img同目录执行命令后 出现了错误.
Click to expand...
Click to collapse
That's because lpmake has supporting libraries. Call lpmake by its original path.
lkj00 said:
-metadata-size 65536 65536 Does the number represent partition size or permissions? Will the numbers never change?
-metadata-slots 2 The slots2 parameter will never change?
-device super:7549747200 Does this number represent the total generation of the super partition?
-group main:7545552896 What does the back number mean? The total size of the other three partitions?
Click to expand...
Click to collapse
Check your own lpdump result for all these parameters.
AndyYan said:
That's because lpmake has supporting libraries. Call lpmake by its original path.
Check your own lpdump result for all these parameters.
Click to expand...
Click to collapse
通过执行上面命令最后得到这样错误提示 ？
Invalid sparse file format at header magic
lkj00 said:
通过执行上面命令最后得到这样错误提示 ？
Invalid sparse file format at header magic
Click to expand...
Click to collapse
At least read above?
AndyYan said:
Can be safely ignored.
Click to expand...
Click to collapse
AndyYan said:
At least read above?
Click to expand...
Click to collapse
了解 谢谢
Success!
I flashed several GSI roms on A51 4G (exynos) using this method.
Thank you for your good work!
Thanks, flashed lineage on my A71 5g
:good:
I'm very much obliged to you! Test other brands as common! !
lkj00 said:
I'm very much obliged to you! Test other brands as common! !
Click to expand...
Click to collapse
Most if not all other brands leave fastbootd intact, eliminating the need for this set of procedure.
AndyYan said:
Most if not all other brands leave fastbootd intact, eliminating the need for this set of procedure.
Click to expand...
Click to collapse
Hmm! Mainly flexible. For example, my brand division does not have the "odm" division, and replace it with my own division "product". That's it.
@AndyYan thank you so much for writing this detailed guide.
Thanks to your detailed guide I was able to create an automated bash script that performs all of these steps automatically and makes all read only partitions inside super.img (system, vendor , product, etc...) into read write-able partitions again and flash to device as a brand new super.img.
It would be an honor for me if you could please try it and let me know if it works on your device. Thanks.
Here is the link:
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
lebigmac said:
It would be an honor for me if you could please try it and let me know if it works on your device. Thanks.
Click to expand...
Click to collapse
Aww, sold my A51 just yesterday...
AndyYan said:
First up, shoutouts to both @phhusson and part of this thread from @YOisuPU for vital guidance throughout my first journey with super-partition devices.
A51 5G runs on Exynos 980 unlike the 4G variant which runs on Exynos 9611. People have been running into trouble rooting the 4G variant and even resorted to GSIs just for rooting, but on the 5G variant all you had to do is to patch boot+vbmeta (don't include recovery) with Magisk. If you just need root, stopping here is enough.
For me, running my LOS GSI is absolutely necessary, but Android 10's super-partition compounded with Samsung not making fastbootd available means an even harder time than what I've had with A60/M40. Below steps apply to this device and might also serve as a general skeleton for other Samsung devices with super-partition.
0) Get Linux - some tools used here just don't have a Windows version
1) On stock firmware, open shell and run
Code:
lpdump
to get some partition info that'll be used next - example output here
2) Get stock firmware
3) Extract super.img.lz4 from AP and then super.img (sparse) from super.img.lz4 with your tool of choice (e.g. 7-Zip ZS)
4) Unsparse super.img:
Code:
./simg2img super.img super.raw.img
5) Extract partitions from super.raw.img:
Code:
./lpunpack --slot=0 super.raw.img <dir>
6) Replace system.img in <dir> with GSI image
7) Repack your own super.img:
Code:
./lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:7549747200 --group main:7545552896 --partition system:readonly:2147483648:main --image system=./system.img --partition vendor:readonly:729890816:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
Compare the command to the lpdump output obtained earlier - many of the numerical parameters here directly match. For the 3 partition declarations, assign them sizes equal to or larger than (recommended) their byte sizes.
8) Compress your super.img into a tar and flash it via Odin in the AP slot
9) Make sure that the device runs patched vbmeta (but stock boot image - somehow the patched one causes a bootloop on GSIs), do a factory reset in stock recovery, reboot
simg2img, lpunpack and lpmake binaries can be obtained online (e.g. from the aforementioned thread) or built from source.
By the way, I've fixed some sepolicy issues with PHH's Superuser, so in future builds, unlike what was described in the thread, 4G variant users likely won't need a permissive kernel to get root on GSIs (at least it doesn't here).
Click to expand...
Click to collapse
It may sound stupid, but how do I get the lp command tools?
Hello there, I've never rooted a phone before but would love to try it with Android 12 finally coming out as stable on the OnePlus 8 Pro. So as a complete noob, can anyone walk me through it, or does anyone have a handy thread that takes me through all of it? Thank you!
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
dangtoi1993 said:
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
Click to expand...
Click to collapse
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
andylmfao said:
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
Click to expand...
Click to collapse
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
dangtoi1993 said:
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
Click to expand...
Click to collapse
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
andylmfao said:
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
Click to expand...
Click to collapse
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
xtcislove said:
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Oh wow, thank you! How do i flash it via fastboot?
andylmfao said:
Oh wow, thank you! How do i flash it via fastboot?
Click to expand...
Click to collapse
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
xtcislove said:
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
Click to expand...
Click to collapse
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
andylmfao said:
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
Click to expand...
Click to collapse
I hope it works for you now. Have fun.
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
paq1170 said:
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
Click to expand...
Click to collapse
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
omega552003 said:
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
Click to expand...
Click to collapse
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
xtcislove said:
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
Click to expand...
Click to collapse
Well that how yo'd normally do it, but for some reason when you do that on the OOS12 upgrade its get really weird.
xtcislove said:
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
Click to expand...
Click to collapse
Do you have C.20 version?
gzyms said:
Do you have C.20 version?
Click to expand...
Click to collapse
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Edit: That is the payload dumper im using.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
xtcislove said:
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Click to expand...
Click to collapse
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
You are right. I posted the wrong payload dumper.
I am using the one from here and it worked with every payload i tried.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
I guess the other one is quicker but im using this and it works. I edit my old post.
Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
Can we use this attached boot img on IN2011_11_C.20 (India)?