Database Develop

[Project Treble][v1.1][Android PIE + OREO][GSI][A-only]

View attachment 4567426
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI. You can find a GSI here: Phh-Treble
ZTE Axon 7 hardware vs Treble implementation:
Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images
What's Packaged in the zip:
A boot image (kernel)
A compressed vendor image (vendor)
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part. How to flash a Generic System Image (GSI) on Project Treble supported devices
- Reboot
Alternative Instruction
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
Audio (Record and Playback)
Video Playback
Sensors
Broken:
Encryption (format data or remove encryption when coming from a non-treble rom)
Sepolicy is still permissive
Nothing else? Otherwise please report it!
Download:
- TWRP 3.2.1-8 TREBLE
- AXON7_GPT_ADD_VENDOR_800MB
- Project_Treble_v1.1-Axon7-by-NFound
Available GSI images is here
Android Pie Release 1 and other (video proof on Axon 7)
Fixes:
- More fixes for Treble ROM by @Kranoner
Credits:
@djkuz for add part. /vendor
@NFound for the fact that this dude did this for us real
Contributors:
@NFound
OS Version based: 8.X Oreo
ROM Kernel: Linux 3.18.71
ROM Firmware Required: Official BETA B12 Oreo
Version Information
Status: Testing
Source-Code Vendor
Created 2018-08-08
Last Updated 2018-08-12

Reserved

Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?

Waancho said:
Thank you very much @NFound, i will test this asap. Does the gapps need to be flashed after install?
Click to expand...
Click to collapse
Any ARM64 with opengapps.org for 8.x, in GSI 9.x Gapps included

Dear friends! Do not forget to backup before installation, this is a test version. It's time for me to sleep, write. As time will be, I will read your comments. If you find bugs - be sure to specify the version of GSI Android 8.x or 9.x
Thank you!

Hey need fast answer! In this guide is talking about a Vendor 8.1 and 8.0 and 8.0 does not work with this rom, so my question is does this rom support your treble? https://forum.xda-developers.com/pr...development/aosp-9-0-android-9-0-gsi-t3826357

Source code vendor blobs in OP

NFound said:
Source code vendor blobs in OP
Click to expand...
Click to collapse
I am a bit confused: how would non-standard hardware like our famous DAC be used in a treble ROM? Would the vendor partition make specific APIs available for such non-standard hardware?

Thank you for this. Maybe its a stupid question, but does the DAC properly function even when we install a GSI?
I have a feeling that a proper fully functional treble will make the other custom ROM thread for Axon 7 obsolete.

so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed

Zobat said:
so no EDL needed? I'm so happy because i dont have a windowscomputer.
*edit: i think i did not read good and windows is still needed
Click to expand...
Click to collapse
You dont need a windows-pc. Only twrp

Do we need to install the project treble zip in the OP if we already enabled treble by EDL?

Let me see if I got this whole treble situation straight :cyclops:
I'm running the latest AEX but I assume this guide contains a more updated "treble" so to speak, is that correct? In order to try the GSI's do I need to follow this guide and wipe everything or will the next AEX release update treble and contain the new fixes?

https://sourceforge.net/projects/resurrectionremix-oreo/files/arm64aonly/
Arm64 and A only. Should be working right?

BaamAlex said:
You dont need a windows-pc. Only twrp
Click to expand...
Click to collapse
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
troy5890 said:
Do we need to install the project treble zip in the OP if we already enabled treble by EDL?
Click to expand...
Click to collapse
You will need to install this again Project_Treble_v1.0-by-NFound
it contains bug fixes

bornlivedie said:
He DOES need a windows pc since in order to enable treble he needs to flash a file via EDL
Click to expand...
Click to collapse
For this zip here he dont need a PC. For the EDL package yes.

Just wanted to thank you and talk about my experience.
Converting the device to Treble was a breeze. Can be done in under 5 minutes with no issues at all. I'm currently running Android P PR1 with no major problems.
However, when trying to install the GSI (totally not related to your work, but wanted to comment on this so everyone can enjoy treble) I ran into a small problem (error 7) when flashing the POST sGSI zip files. I resolved this by doing the following:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
This worked out fine for me.
Again, thanks a million times on your epic feat. This is no small task, and is very welcome. It marks a before and an after.

You, sir, are heaven-sent. Thank you for your good work.

bornlivedie said:
Install the treble zip
Install the GSI
Install the treble zip again
Install the 3 zip files in order
Click to expand...
Click to collapse
Why a second time?

Dear friends!
In the video I am used Release 1.
1. Flash Project Treble
2. Flash GSI
3. !!! In Mounting - UNMOUNT and MOUNT system and vendor!
4. Install patches 1,2,3
5. Reboot
Android Pie Release 1 (Download A-only and patches): https://androidfilehost.com/?w=files&flid=280192
Work GCam: https://github.com/AospExtended/platform_vendor_aosp/blob/8.1.x/prebuilt/common/apk/Gcam.apk
NOTICE: If during a call on Android 9 you do not hear the subscriber. (thx @atakan33 )
PS Here is another list of available GSI ROMs, use the translator!
9.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-2
8.x https://4pda.ru/forum/index.php?act=findpost&pid=75394613&anchor=Spoil-75394613-3
Thank you!

Treble/GSI Megathread

About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
Note: This guide is for users who have already flashed custom ROMs (not necessarily GSI) to their phone. If you're new to this or are coming from any MIUI ROM, please see other tutorials.
Click to expand...
Click to collapse
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).

Has someone tried oui ??

Great guide! Thanks a lot, your way was the only way I could get a treble rom working on the device! I wasn't able to flash the vendor in fastboot coming from miui 10.2.2.0, but it worked from twrp. Now got Havoc booted successfully

has anyone tried q gsi?

xeodm said:
has anyone tried q gsi?
Click to expand...
Click to collapse
If you want to use it, try it out. There's no reason it shouldn't work ?

Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!

djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
I'm going to try it later. I will update if it works.

djmanri3 said:
Has someone tried oui ??
Click to expand...
Click to collapse
Unfortunately, it doesn't boot. I want to try it too !

salahmed said:
Anyone successfully flashed Android Q beta 5 GSI?
I tried my best, but it is not booting up!
Click to expand...
Click to collapse
I remember someone saying u need to use permissiver 3 or 4

gsser said:
I remember someone saying u need to use permissiver 3 or 4
Click to expand...
Click to collapse
Do you have a link?
Regards

salahmed said:
Do you have a link?
Regards
Click to expand...
Click to collapse
I dont have any unfortunately, it might be in erfano's telegram group or mix 2 aosp group.

I'm Stuck Help!
I'm stuck on AOSP EX Boot Animation, What to do now?
I did all right!!
Why is this happening

Fix for the audio problem
andythedev said:
About
I've found information about flashing GSI's on this phone to be fragmented so here's a collection of resources that have worked for me.
If you have any suggestions or issues with popular GSI ROMs, drop them here and I'll do my best to update the thread.
GSI Installation
1. Flash TWRP
The current latest version (as of the time of writing v3.3.0) supports for flashing GSIs.
2. Update firmware (optional)
I'm currently using the latest global firmware (as of time of writing v10.2.2.0) which seems to work fine. Download the zip from xiaomifirmwareupdater and flash in TWRP.
3. Flash treble BOOT and VENDOR partitions
Download the below image files (source).
boot.img
vendor.img
Install the images by using the following command or optionally using TWRP.
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
4. Flash your GSI ROM
Pick a GSI from the Treble forum and be sure to download an ARM64 and A-Only variant. If the downloaded file is an archive (not an *.img file) you will need to extract the contents.
Go into TWRP
Copy the GSI image to your phone
Wipe "Dalvic/ART Cache", "Cache", "System" and "Data" paritions
Install the GSI image to the System Partition (Install -> Install Image -> yourimagefile.img - System Image)
Reboot back into TWRP
Resize the system partition (Wipe -> Advanced Wipe -> check System -> partition options -> Resize FS)
Install Magisk & OpenGapps (both optional)
GSI ROMs
Pixel Experience 9 (2019-03-24)
Source: XDA
Status: Working.
Additional info: Everything works as expected.
AospExtended v6.2 (20190313)
Source: aospextended
Status: Working.
Additional info: Everything works as expected.
Ressurection Remix v7 (19/04/16)
Source: XDA
Status: Unusable.
Additional info: Everything works aside from video playback (which creates a loud popping/static sound regardless of audio levels).
Click to expand...
Click to collapse
https://github.com/hmuny99/GsiSystemAudioFix
Use this flashable zip to fix the audio stuttering issue.

Someone tried it with the Q GSI's from Erfan? I can't get it to work....

pattagalix said:
Someone tried it with the Q GSI's from Erfan? I can't get it to work....
Click to expand...
Click to collapse
Not with Efran's gsi's but I've tried a few times on other 10's and had no luck on my end. I Used the 10 gsi Aonly 64 bit and I've formatted data and decrypted using Zach's force encrypt removal zip and magisk su zip and I've tried without removing encryption and no luck. It hangs on mi boot logo every time. I saw a DerpFest gsi on telegram that's when this whole gsi mission began for me. lol. Maybe we need a different boot.img and vendor.img for 10 idk? ? I tried with and without flashing the boot and vendor, decrypt and not decrypt and no go. ?
Sent from my moto g(7) power using XDA Labs

I booted RR v7.03 from Luke's GSI thread using vendor and boot in op but tried a few more 10 GSIs and they either hang on mi screen or bootloop forever. This RR is bad ass!! V7.03 wasn't made for Chiron and blows 7.02 off the map. Although security patch is from November 2019 I'm going to rock it a while. Sure will miss RR now that main dev stopped. Talk about a bad ass ROM!!! If anyone wants to use it its here. Just click the top link and you'll see the A only 64
https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457

[SHARE] LineageOS 19/18.1 android 11 and 12 Combined galaxy tab A 10.1 (2019)SM-T515/SM-T510

First of all this is not my work is just tried this rom and its preety stable. Thanks to developers @phhusson @Magendanz
DESCLAIMER :use it your own risk.
So finally this rom booted on galaxy tab SM-T515 everything thing is working with small bugs as mentioned below.
Download files given below:
Bugs :
1)voLTE: not working tried phh treble settings to solve the issue but no luck.
Other networks, data calling works perfectly
2)MTP: mtp not working but you can transfer files after booting device in TWRP mode
3)audio not recording in videos use open camera app and go to settings and set default audio as a source.
4)For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Reverting to Samsung oneui:
For Linageos 19 android 12 twrp internal storage nonaccesible so to restore back to stock ROM just falsh latest Odin firmware using
ODIN app
Download firmware using this app:
Download link for Android/Linux/Mac/Windows:
Releases · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Linageos18.1 user restore your oneui backup using twrp or use ODIN firmware.
Except these you can check and tell me I didn't found anything till now
Download this gsi fileonly this is compatible)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20211010-UNOFFICIAL-treble_a64_bvS-vndklite.img.xz/download
Download arm 32 android 11 gapps :
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Linageos 19 android 12Gapps included)
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.0-20220114-UNOFFICIAL-treble_a64_bgS.img.xz/download
Download magisk zip:
https://dl.magiskapp.com/MagiskZip/Magisk-v23.0.zip
If you gets device certification error follow this post:
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
XZ file extractor android app:
GZ & XZ Extract - File Opener - Apps on Google Play
Extractor tool for tar, tar.gz, gz, gz2 & xz files. Just few taps for result
play.google.com
Process :
1)Download all files given first extract xz file gsi file using xz extractor you gets img file.
2)Now transfer gsi.img, gapps and magisk file in tablet.
3)boot tablet to TWRP MODE
4)Now first select wipe >advance wipe>select system> slide
5) now go back click install click install img you will see your file click on it and select system partition and enter.
6) now we have to install gapps but we need to first resize system partition so
First click mount and mount system Partation now go to wipe>advance wipe>select system >clcik repair >click resize
7)now click install and. Select gapps and flash.
8)now go back install magisk and hit reboot.
After reboot you may face device certification error so to solve this go to magisk and install magisk hide props configuration module and reboot your phone.
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Follow this video i will update thread soon
Android 11 Linageos 18.1
Android 12 lineageOS 19

How's the battery life?

works offline charge?

Pinage said:
How's the battery life?
Click to expand...
Click to collapse
Best battery life

Spawacz_Reduktor said:
works offline charge
Click to expand...
Click to collapse
Yes

@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!

Sukrith said:
@pankspoo
Have you tried LOS 19? I saw your video on aosp 12 build but from your video it seems that it sucks! Lineage I feel will be miles better than aosp so if you can try and get back it'll be really helpful!
Click to expand...
Click to collapse
Yes same time but that has grafix shutter issue same like gsi

pankspoo said:
Yes same time but that has grafix shutter issue same like gsi
Click to expand...
Click to collapse
There seems to be a new build, can you maybe try? It's based on 6th November build.

Sukrith said:
There seems to be a new build, can you maybe try? It's based on 6th November build.
Click to expand...
Click to collapse
Ok

In January I installed 17.1 using this ROM. Do I need to go through the whole process of resizing the partition, since I already did it for 17.1?

Never mind! I went ahead and installed it following the instruction . It works, thanks!

bedwere said:
Never mind! I went ahead and installed it following the instruction . It works, thanks!
Click to expand...
Click to collapse
Are you happy with this ROM?

Krekle said:
Are you happy with this ROM?
Click to expand...
Click to collapse
Yes, it's very stable.

I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards

This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....

Shawnashley said:
This is confirmed to work on the T-510? Curiosity will brick the tab, like it kills the cat....
Click to expand...
Click to collapse
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.

HansMampf said:
I have one issue and some questions.
When using a Bluetooth Headset, I have no sound in apps like Jitsi. Mic on the Bluetooth Headset is working in Jitsi, the others can here me. When using e.g. youtube in Chromium I can hear sound via the Bluetooth Headset.
I checked "Force-disable A2DP offload" and restarted, still the same.
Any Ideas?
And some Questions:
- Is magisk only needed for root? I don't need to root, do i still have to install magisk?
- in twrp I can't mount the system partition, so I cant fix it, but the rom is working. So how to mount system?
- I don't want gapps, is it ok to use the roms without gapps? so eg this one ...treble_a64_bvS.img ?
- in the description downloadlinks you are using: 18: treble_a64_bvS-vndklite but 19: treble_a64_bgS, so should one use vndklite for 18 but not for 19? Or also for 19? What is better? ...
Regards
Click to expand...
Click to collapse
I can only answer some of your questions:
- Magisk is only used for root. It's not required.
- Mounting /system in TWRP or in a File explorer doesn't seem to be possible.
- GApps is built in to roms with "...bgS.img.xz". For vanilla roms without gapps download the "...bvS.img.xz"file.
- For LOS 19, I flashed treble_a64_bgS and didn't have an issue. I can't comment on the vndklite version or what it's used for since I never tried it.

betacrypt said:
Yep. It works. I previously had the latest Nexus rom flashed on my SMT-510, so in TWRP I just flashed Lineage 19.1 to system, formatted data, rebooted and it loaded successfully. With Magisk 24.1. It all runs surprisingly well. No issues so far other than no USB file transfer or ability to mount System partition.
Click to expand...
Click to collapse
Any idea about success of I am running Megadanz 11.0 ROM?

Shawnashley said:
Any idea about success of I am running Megadanz 11.0 ROM?
Click to expand...
Click to collapse
It's a good rom and works very well. I was using it before I upgraded to LOS19.1.

Hey there!
I Installed this a couple of weeks ago, but has to reinstall nexus stock 11.0 pretty quickly, as after spending an evening trying to fix issues, it just wouldn't work.
Issues:
1) App crashes are constant. I cannot open Chrome, YouTube, Google Podcasts, Twitter - they all crash to launcher. - Cache, dalvik and data was cleared, still nothing
2) Gesture Navigation is missing - is it meant to be?
3) Magisk installs successfully,, but is then not recognised by the app, meaning no modules. - Is that normal?
Does anyone have any idea on how I could fix these issues, so I can install again?
Many thanks

How To Guide (Guide) Rooting, payload dumper, magisk_patched guides NE2213

Hi all,
Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU NE2213 but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
NE2213_11_A.12
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.13
Magisk Manager v24.3 (24300) Stable
NE2213_11_A.14
Magisk Manager v25 (25000) Stable this version retains root after a restart, more stable version over previous iterations.
NE2213_11_A.16
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_20
Magisk Manager v25.2 (25200) Stable
NE2213_11_C_21
Magisk Manager v25.2 (25200) Stable
NE2213_13.1.0.520 (EX01)
Magisk Manager v26.1 (25200) Stable
Oxygen OS NE2213_13.1.0.521 (EX01)
Magisk Manager v26.1 Stable
1st
Extracting a boot.img using Fastboot Enhance
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
An unlocked bootloader.
The local System Update Installer : normal local system update will not allow a reboot during installation, the one I've linked will.
Process
On your computer
1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.
Download from here: https://github.com/libxzr/FastbootEnhance/releases
2. Download the firmware of your choice (always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.
3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip
4. One of the files will be called boot.img, this is the file we'll be patching, click extract then copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, do this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" which will be output into the Downloads folder)
You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.
I would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone will bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed, so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch it twice but it won't hurt if you do.
2nd
Update from XX stable to XX+ stable whilst retaining root
Guide
**NOTE- Although this may work, the system may be unstable, especially when changing bases, eg: Android 11-12 or 12-13, so if you encounter strange behaviour then a factory wipe is advised.
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Install the OnePlus local install apk listed below in downloads. Click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
3rd
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Bootloader unlock
Boot to the bootloader with adb reboot bootloader
type fastboot flashing unlock
Agree to unlock - allow to boot.
If you can't see the device using ADB
Make sure USB Debugging is turned on
Connect your cable to your phone and computer, when asked what you want your phone to do, click on transfer files, a driver will be installed.
After this reconnect your phone and it'll prompt you with a disclaimer with a check box, check the box and click ok, ADB / Fastboot should now work.
Files:
Local System update APK, this must be used as the local OnePlus 10 Pro one will not allow a reboot during the installation, so you cannot install the Magisk boot image during an upgrade, the android 13 local update apk is also required for rolling back to android 12.
Android 13 local update apk
3.27 MB folder on MEGA
mega.nz
Android 12 local update apk
3.27 MB folder on MEGA
mega.nz
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Oxygen OS NE2213_11_A.12 Stock boot image
0 byte folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.12 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.13 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.14 Stock boot image
384 MB folder on MEGA
2 files
mega.nz
Oxygen OS NE2213_11_A.14 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_A.16 Patched boot image
192 MB folder on MEGA
mega.nz
Android 13
Oxygen OS NE2213_11_C_20 Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_20 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_11_C_21 Stock boot image https://mega.nz/folder/LNVxTDYA#yly9xpjFjQhe4De_jqyzbw
Oxygen OS NE2213_11_C_21 Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.520 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Stock boot image
192 MB folder on MEGA
mega.nz
Oxygen OS NE2213_13.1.0.521 (EX01) Patched boot image
192 MB folder on MEGA
mega.nz

Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers

galaxys said:
Glad to see you here bro with the 10 Pro and helpful guide's!!
Cheers
Click to expand...
Click to collapse
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB

UPDATE: First patched boot image is up, using the latest stable Magisk v24.3 (24300)

dladz said:
Slowly coming around to this phone mate, we desperately need a few custom ROMs..
EvoX on this would be phenomenal.
Nudge nudge @AnierinB
Click to expand...
Click to collapse
Yeh, it's early but hopefully a few Developer's will get this badboy device!

Thank you thank you THAAAANK YOOOOUUUU

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
Lol welcome mate

meowmeowpewpew said:
Thank you thank you THAAAANK YOOOOUUUU
Click to expand...
Click to collapse
I honestly hope so..
I'm having a few issues isolating the correct files to make the center clock Magisk mod, but that's in the works. Will have it done soon hopefully.
OnePlus thought it would be a good idea to get rid of OPSystemUI.apk in place of systemui.apk so maybe more in line with stock android. But we'll see

@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
Hey that's great news and something to definitely look forward to!
Cheers

Very happy to see guides! Nice, thank you so much !

dladz said:
@galaxys as if my prayers were answered, joined the Evo X TG group and there is now a OnePlus 10 group so it's in the works, seriously hope it's AnierinB, he did so well with the 8 pro.
Literally cannot wait
Click to expand...
Click to collapse
I cannot find that Evo X 10 Pro channel, have you got a link?

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
If you have telegram just search for evo x up the top, you'll see the main channel.
The the other is in that, i'm just in the middle of something, i'll send it once i'm done.

kouzelnik3 said:
I cannot find that Evo X 10 Pro channel, have you got a link?
Click to expand...
Click to collapse
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me

Macke93 said:
Evolution X - OnePlus 10 Series
Telegram: Contact @EvolutionXOnePlus10
t.me
Click to expand...
Click to collapse
Oh I've found it.

Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?

kouzelnik3 said:
Oh I've found it.
Click to expand...
Click to collapse
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.

Lynxy0 said:
Hello All,
Very many thanks for your guide. It really helped me root my OP 10 PRO
I was wondering if it is possible to flash my OP ColorOS with OxygenOS EU/UK version you have uploaded?
I copied the 02b0d1b2508744e3a41115aeb274cccf.zip to the root folder and I tried installing via Oxygen Updater using the automatic method, but it fails every time.
If I try installing it manually, I have to download the Oxygen Updater via oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk.zip and rename to .apk. - I then launch System Update , click on settings and it says 'Move installation package into root directory' (which it is).
Have I missed a step?
Click to expand...
Click to collapse
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.

dladz said:
Ah was just about to post it mate.
Glad you found it, it's only new but that fact that it's here is brilliant . I'm hoping AnierinB is the dev who makes the rom for the 10.
Click to expand...
Click to collapse
I am hoping too, because in this state oxygen os in this device is bad. Yeah, it is quite new, but hey, it is halfly baked. And not only evo x, but other ROMs I hope will come.

dladz said:
Honestly mate i'm not sure, you're essentially changing region.
Have you looked into fastboot enhanced?
You can obtain the firmware from oxygen updater (it's 4.15GB the one i uploaded is only the boot image and patched boot image)
Then copy it to your computer and allow it to flash to your phone.
This isn't without risk mate and i've not done this before myself.
Click to expand...
Click to collapse
Thanks for your swift reply. I will wait until there is a verified method. For now, I will tread lightly with the rooted version hehe

Question Twrp on samsung a33

Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do

I've rooted through Odin by following this post https://forum.xda-developers.com/t/are-these-rooting-guides-for-the-samsung-a33-5g-good.4475163/ but I'm waiting for TWRP to install custom rom too...

ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os

Is TWRP the onl way to install lineage OS?

yes i guess

Dryfty said:
ive rooted my phone with magisk by using odin and a patched ap file by magisk, i installed my official software back because magisk kind of slowed down my devices, but now im waiting for twrp so i can install lineage os
Click to expand...
Click to collapse
how do you want to install Lineage OS? There is still not version of Lineage for A33

you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp

Dryfty said:
you can only get lineage on a33 if you have twrp but a33 doesnt "support" twrp
Click to expand...
Click to collapse
there is an experimental version of TWRP working, I am using it

Arcangel3 said:
there is an experimental version of TWRP working, I am using it
Click to expand...
Click to collapse
on the a33? can you explain how to install it

Dryfty said:
on the a33? can you explain how to install it
Click to expand...
Click to collapse
attached to you here. Bear in mind it is experimental, but it might work
EDIT: deleting it because it is unstable version, a stable version will be released soon by @Zillion (no pressure )

Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!

vovaxxxx said:
Hey, thanks for sharing! Could you say what's the best custom ROM for this device for the moment? Or where is the list of ROMs? thanks!
Click to expand...
Click to collapse
there is none yet.
But some poeple said that stock ROM for A33 is good enough to not need a custom ROM.

Arcangel3 said:
attached to you here. Bear in mind it is experimental, but it might work
Click to expand...
Click to collapse
Give credits to the guy that made it

Zillion said:
Give credits to the guy that made it
Click to expand...
Click to collapse
I am not sure who made it, was it you? hehe

Dryfty said:
Ive been searching for ages and still havent found how to install twrp on my a33, is it even possible? Im trying to root my a33 with magisk but i need twrp. Im stuck and i dont know what to do
Click to expand...
Click to collapse
bro try this way to root
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
I want to root my A12 but it not work for my phone.please send me a latest version for A127FXXU7BVI1 isBaseband version
forum.xda-developers.com

Arcangel3 said:
I am not sure who made it, was it you? hehe
Click to expand...
Click to collapse
Yup, it got its reasons to not be released.

Zillion said:
Yup, it got its reasons to not be released.
Click to expand...
Click to collapse
should I delete it?
Do we have any better version now?

@Zillion any progress with a relesable version???

Arcangel3 said:
@Zillion any progress with a relesable version???
Click to expand...
Click to collapse
I don't own A33 and I don't know how to make any progress on this :c

I managed to get the Lineage OS "Light" GSI version by AndyYan https://forum.xda-developers.com/t/gsi-13-lineageos-20-light.4509315/ and it works well, but the process to install it is pretty involved and if you do anything wrong, you can easily soft-brick your phone. This process should also work for other gsi roms
First Download the Latest Version of Lineage OS "Light", of which the download link can be found in the thread above or here https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-light/ (There are three versions, vS "Vanilla with Superuser installed" vN "Non-SU Vanilla" and gN "Non-SU with GApps") If you want root, I suggest choosing one of the Non-SU versions and patching the stock AP tar with Magisk before starting this process as the Superuser version provides you a generic superuser app and installing magisk with it greets you with a abnormal state message every time you launch the Magisk Manager.
Second: Unpack the downloaded tar file using 7zip if on windows or with the tar command on linux, and then rename the unpacked .img file to system.img
Third: Get the stock firmware for your device using samloader or some other Samsung firmware downloader and unpack the archive file you get to a directory
Fourth: Unpack the AP tar file, you should get a bunch of files in .img.lz4 format.
Fifth: Find the super.img.lz4 file and decompress it using https://github.com/lz4/lz4/releases and this command
Code:
lz4.exe -d super.img.lz4 super.img
From this point onwards you are better off on linux (I've only tested this on Ubuntu WSL so far), if you're on windows 10+, I suggest enabling Windows Subsystem for Linux and downloading and running the Ubuntu distro from the Microsoft store, you can google how to do that.
Sixth: Within Linux (Ubuntu in my case), install the "android-platform-system-core" package using your preferred package manager (I know that package is available on Ubuntu, but I haven't researched whether any other linux distro has that package available). The main thing we want from that package is the shell script "simg2img" as the super.img is currently sparsed (compressed using the Android Sparse image format).
Seventh: If you already did the steps so far in Linux, just go to whatever directory you have the super.img stored, otherwise if you did everything in windows and have a Ubuntu WSL distro ready, you can copy the super.img directly into the ubuntu distro by going into file explorer and scrolling all the way to the bottom of the navigation pane till you see Linux, of which you can expand to find a Ubuntu network share folder, expand that and drag and drop the super.img into your root folder, as well as the system.img file (renamed gsi rom file).
Eighth: Unsparse the super.img using the command:
Code:
simg2img super.img *whatever*.img
This will give you a raw disk image of super.img that's about 9-10 gb. You can name the output file to whatever you want as long as you can discern which img is which, in fact after running the command you can delete the original as you no longer need it.
From here is where the process gets a bit tricky and I fully recommend reading through this guide: https://forum.xda-developers.com/t/...are-binary-3-may.4053065/page-4#post-82241115
Ignore the fact that the thread is for the Galaxy a51 as the steps work for the a33 as well. When you get to the point where you've unpacked the Super.img, copy the GSI system.img over the stock one.
Now the part that can easily cause you to mess up is that when repacking super.img, you have to get the size of each file, including the unsparsed super.img and input the size in bytes of each file in place of what is given in the long command used to repack the image. The numbers you have to change are as follows:
--device super:4294967296 (Change to the file size of super.img)
--group main:4293513600 (Calculate the sum of the size of each of the .img files that were contained in the super.img, minus product.img as that's not needed)
--partition vendor:readonly:342155264:main (Change to the byte size of your vendor.img, same goes for system, odm and vendor_dlkm. Not sure if vendor_dlkm is required as it's not shown in the guide, but just to be safe, I'd recommend adding that in the same format as shown above for vendor just change vendor to vendor_dlkm)
File sizes can be acquired using the command:
Code:
ls -l
Another thing to note is that all of the file sizes must be divisible by 512 as that's the block size the img uses, if they all are, then you're good to go, if one or more aren't you're probably dealing with a corrupt file or that one of the img files is sparsed or compressed in some way. Once you've confirmed the file sizes are good, run the command. You can ignore the "Invalid sparse file format at header magic" message as it doesn't seem to mean anything bad for the process. You don't have to worry if the sparsed image file size is divisible by 512 as it more than like won't be evenly divisible as the file is compressed now.
Once that's done you can take the new modified super.img (make sure it's named that) out of the linux distro and back to windows.
Recompress the super.img back into super.img.lz4 using the command:
Code:
lz4.exe -B6 --content-size super.img super.img.lz4
Now package the super.img.lz4 file with all of the other files from the AP back into a tar file, I suggest using the tar-md5-script-tool.zip from this thread https://forum.xda-developers.com/t/...sing-odin-without-twrp-phh-lineageos.4114435/
At this point, you can skip to step 24 on that guide and continue from there to install the custom rom, just remember to use super.img.lz4 instead of system.img.ext4.lz4, also ignore the .ext4 part, I think that's a device specific thing and the a33 from what I know doesn't have that.
Once you're done and you've booted up after flashing with ODIN, you should be greeted with the lovely Lineage OS Boot Screen
Bare in mind this is a barebones rom and many features may not work as intended since it's an unofficial build of Lineage OS and is intended to work with many devices without too many issues.