How to flash GSI's to the OnePlus 6T
As you all know, the OnePlus 6T has treble support, so this guide will cover how to flash GSI's to fajita!
The method used is similar, if not the same to flashing gsi's on the OnePlus 6
Bugs
In-Display Fingerprint
Adaptive Brightness(Now fixed, just waiting for phhusson to merge pr)
Notch will overlay things(I'm working on it!)
Lets begin!
1: Downloading the required files
SDK Tools
Stock VBMETA.img and BOOT.img
Phh-Treble
Make sure you download the a/b version!
2: Flashing
Make a new folder and call it whatever you want
Extract the platform tools zip you downloaded into that folder and copy the boot.img, vbmeta.img and phh treble GSI
Open a Command Prompt/Terminal and cd to that folder
Now run these commands in order
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a (name of the GSI)
[COLOR="Red"][SIZE="4"]WARNING: The below command WILL erase userdata, make sure you have a backup of EVERYTHING[/SIZE][/COLOR]
fastboot -w flash system_b (name of the GSI)
fastboot reboot
Enjoy your new GSI!
Reserved #1
Reserved #2
I have a bad feeling that the in-display fingerprint scanner will never work with gsi, as it is probably a proprietary implementation from one plus.
Envoyé de mon ONEPLUS A6013 en utilisant Tapatalk
What are the benefits of this?
Sent from my ONEPLUS A6013 using Tapatalk
ledvedder said:
What are the benefits of this?
Click to expand...
Click to collapse
Run a ton of different ROMs on your op6t already, but they will most likely all be extremely buggy.
So no benefits really. But it's a good guide. Just not something I'd do with my phone personally.
I tried phh gsi last month, fp scanner ofc was not working, calling and sms broken on jio due to volte not working, also disabling dm verity gives red warning on every boot which is irritating.
Currently no advantage in flashing gsi, but the guide will be helpful when Android Q comes.
wlk0 said:
I have a bad feeling that the in-display fingerprint scanner will never work with gsi, as it is probably a proprietary implementation from one plus.
Envoyé de mon ONEPLUS A6013 en utilisant Tapatalk
Click to expand...
Click to collapse
Phh is going to try and get it working in his GSI's, don't worry!
Thanks for the write up OP. I'm just shocked at the non dev work for roms for 6t. Hoping the pixel4 doesn't have a horrendous notch. 6T is a big disappointment as far as roms are concenred.
I have been flashing gsi's for this phone since November. I simply flash the system.img to both slots. Never had to disable vb or flash vbmeta. Thanks for the guide this will help many
Now that Android Q Beta 2 GSI images have been released, anyone tried to boot them on OP6T? If yes, please share your valuable feedback.
gururoop said:
Now that Android Q Beta 2 GSI images have been released, anyone tried to boot them on OP6T? If yes, please share your valuable feedback.
Click to expand...
Click to collapse
im trying now but no luck yet. tried using the stock vbmeta and the one included in the beta still no boot
gururoop said:
Now that Android Q Beta 2 GSI images have been released, anyone tried to boot them on OP6T? If yes, please share your valuable feedback.
Click to expand...
Click to collapse
Tried ... boots but stuck on the bootanimation ....
emmmm.. my device is 6t , and it's wifi can't work on any gsi rom
bengris32 said:
How to flash GSI's to the OnePlus 6T
As you all know, the OnePlus 6T has treble support, so this guide will cover how to flash GSI's to fajita!
The method used is similar, if not the same to flashing gsi's on the OnePlus 6
Bugs
In-Display Fingerprint
Adaptive Brightness(Now fixed, just waiting for phhusson to merge pr)
Notch will overlay things(I'm working on it!)
Lets begin!
1: Downloading the required files
SDK Tools
Stock VBMETA.img and BOOT.img
Phh-Treble
Make sure you download the a/b version!
2: Flashing
Make a new folder and call it whatever you want
Extract the platform tools zip you downloaded into that folder and copy the boot.img, vbmeta.img and phh treble GSI
Open a Command Prompt/Terminal and cd to that folder
Now run these commands in order
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a (name of the GSI)
[COLOR="Red"][SIZE="4"]WARNING: The below command WILL erase userdata, make sure you have a backup of EVERYTHING[/SIZE][/COLOR]
fastboot -w flash system_b (name of the GSI)
fastboot reboot
Enjoy your new GSI!
Click to expand...
Click to collapse
Hey OP, any chance you can update this to take advantage of beta 3?
cervantesjc said:
How to flash GSI's to the OnePlus 6T
As you all know, the OnePlus 6T has treble support, so this guide will cover how to flash GSI's to fajita!
The method used is similar, if not the same to flashing gsi's on the OnePlus 6
Bugs
In-Display Fingerprint
Adaptive Brightness(Now fixed, just waiting for phhusson to merge pr)
Notch will overlay things(I'm working on it!)
Lets begin!
1: Downloading the required files
SDK Tools
Stock VBMETA.img and BOOT.img
Phh-Treble
Make sure you download the a/b version!
2: Flashing
Make a new folder and call it whatever you want
Extract the platform tools zip you downloaded into that folder and copy the boot.img, vbmeta.img and phh treble GSI
Open a Command Prompt/Terminal and cd to that folder
Now run these commands in order
Hey OP, any chance you can update this to take advantage of beta 3?
Click to expand...
Click to collapse
U don't have to do much of this at all
Fastboot erase system
Fastboot flash system system.img(gsi)
Fastboot flash vbmeta vbmeta.img (of Q) or if Google's W gsi, they have a Downloadable vbmeta for the gsi, use it. The disable verification is redundant. Just flashing the vbmeta disables it. Yes that method works but u don't have to,just flashing vbmeta achieves same exact thing.
Fastboot -w
Reboot
That is all
fullofhell said:
U don't have to do much of this at all
Fastboot erase system
Fastboot flash system system.img(gsi)
Fastboot flash vbmeta vbmeta.img (of Q) or if Google's W gsi, they have a Downloadable vbmeta for the gsi, use it. The disable verification is redundant. Just flashing the vbmeta disables it. Yes that method works but u don't have to,just flashing vbmeta achieves same exact thing.
Fastboot -w
Reboot
That is all
Click to expand...
Click to collapse
Any way you can point me to the correct vbmeta image, please and thank you.
cervantesjc said:
Any way you can point me to the correct vbmeta image, please and thank you.
Click to expand...
Click to collapse
On the Google Q gsi page. Or take the OnePlus Q zip, extract using the superr kitchen, or it's quicker to use the payload bin extractor...
Both of which exist on here
Payload bin extractor dumps everything from the bin file which is what the rom is inside.u take the OnePlus Q rom, right click it using 7zip, drag the payload.bin file into the payload bin in folder. Then double click the exe. In a few mins you have a full.image dump in the out folder.
fullofhell said:
On the Google Q gsi page. Or take the OnePlus Q zip, extract using the superr kitchen, or it's quicker to use the payload bin extractor...
Both of which exist on here
Payload bin extractor dumps everything from the bin file which is what the rom is inside.u take the OnePlus Q rom, right click it using 7zip, drag the payload.bin file into the payload bin in folder. Then double click the exe. In a few mins you have a full.image dump in the out folder.
Click to expand...
Click to collapse
Truly appreciate your help.
I dont understand why inscreen fp or VoLTE doesnt work. The whole ethos around Treble is that the vendor implementation is abstracted through the Vendor Interface, on top of which sits the GSI. So provided the GSI is coded correctly to use the Vendor Interface APIs, then all functionality should work. the fact that this or that is proprietary is [should be] irrelevant - for that is the whole purpose of Treble . It permits faster and more regular updates to be pushed to the handset, but of course Vendors won't like it because it stunts their market sales drive , i.e getting consumers to buy the next handset upgrade to get the latest features. Hardware now is reaching the nadir of function, and we are seeing software (Middleware and Apps) take the front seat - as per Pixel 3 camera shots. Hardware is comparable across devices, it is the software (principally Google's Android and to a lesser degree the Apps themselves) that are going to make the difference , for now, and of course that isnt a revenue stream for vendors. Perhaps that's where the world is going ... toward everyone not having an Apple phone, but an Android phone, and specifically a Google Phone ... takes me back to the days of Nokia world domination. Ah but evolution only has one constant, and that is that nothing lasts forever ... not even Apple or Google
Long live GSIs !!
Related
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
shouldn't you be flashing disable_encrypt zip too?
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.
Does fingerprint working on GSI?
what is gsi?
I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?
bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google
Has anyone tested RR PIE GSI on RN7? Does it work?
Is it possible to boot Android O GSI? :silly:
letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Is the. Method the same for the global version with global rom?
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?
PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?
Getting WRONG PIN error after setting up pin ???
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?
Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
any recommended gsi rom with no bug?
booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?
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
Magisk v21.0 Manager 8.0.2 Patched Root Boot Image
https://www.androidfilehost.com/?fid=10763459528675577415
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01BA 10.0.12
https://www.androidfilehost.com/?fid=10763459528675577418
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675577414
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675577413
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675577416
Combined Folders
https://www.androidfilehost.com/?w=files&flid=319531
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot
Very useful, thanks
digidude512 said:
Magisk v21.0 Manager 8.0.2 Patched Root Boot Image
https://www.androidfilehost.com/?fid=10763459528675577415
May need to install Magisk Manager manually
Full ZIP OxygenOS HD01BA 10.0.12
https://www.androidfilehost.com/?fid=10763459528675577418
Stock Boot Image
https://www.androidfilehost.com/?fid=10763459528675577414
ADB Enabled Recovery Image
https://www.androidfilehost.com/?fid=10763459528675577413
Stock Recovery Image
https://www.androidfilehost.com/?fid=10763459528675577416
Combined Folders
https://www.androidfilehost.com/?w=files&flid=319531
Usage (Unlocked Bootloader)
adb devices (give permission on device)
adb reboot fastboot
fastboot devices (to confirm that device is being detected)
fastboot flash boot path/to/patched_boot.img or fastboot flash recovery path/to/patched_recovery.img
fastboot reboot
Click to expand...
Click to collapse
need official link for Full ZIP OxygenOS HD01BA 10.0.12
thanks
jahidinbedod said:
need official link for Full ZIP OxygenOS HD01BA 10.0.12
thanks
Click to expand...
Click to collapse
One the OnePlus Software Update page they still only link to OxygenOS 10.0.10.HD01BA
The one I uploaded was from Oxygen Updater app.
Thanks a lot for this.
1) Are all the images the same in all countries? Is there something to be aware of regarding specific images and language or countries / radios?
2) May I buy you a coffee or don't you accept donations?
If you keep this up, I won't have to do that payload_dumper stuff myself.
Many thanks for the patched boot image! Managed to restored my root after mindlessly updating to 10.0.12.
t-ryder said:
Thanks a lot for this.
1) Are all the images the same in all countries? Is there something to be aware of regarding specific images and language or countries / radios?
2) May I buy you a coffee or don't you accept donations?
If you keep this up, I won't have to do that payload_dumper stuff myself.
Click to expand...
Click to collapse
1: As far as I'm aware they're all the same across the regions as long as the model number matches.
2: I would if PayPal didn't lock me out because PayPal
Uploading 10.0.13 now
IMPORTANT: This guide will not work with A11; we do not have an official working TWRP for A11 (from the TWRP team) on the 7T Pro.
OVERVIEW
The following will guide you through rooting your OnePlus 7T Pro running stock OOS using TWRP by extracting the boot.img from your own device and patching it using Magisk using adb and fastboot. This is not the only method, but it is the method that I used to obtain Magisk/Root for my 7T Pro (HD1910) running stock OOS (10.0.12 HD01AA at the time of writing). It should work for all variants of 7T Pro running any of the stock OOS. If you can follow directions, there should be no harm to your device, but use at your own risk.
A little bit of introduction (if you care)
I’ve been a member of XDA for quite a while and go way back to the Sammy S3 days. I’ve done what I can to help others out on XDA (I’m just a user), and lately, I’ve noticed that the existing guide(s) hasn’t been updated since they were created, or the information on how to root is not easily found (buried deep inside a thread).
PRE-REQUISITES
An unlocked bootloader
Working adb and fastboot (Latest platform-tools). This step assumes that your PC and 7T Pro are set up correctly (i.e. USB drivers) and adb/fastboot commands are working correctly
Latest Magisk Manager (Latest Magisk Manager) installed on your 7T Pro
A copy of the latest TWRP in the platform-tools directory (TWRP for 7T Pro)
INSTRUCTIONS
Boot TWRP
Connect your device via USB
Open command prompt as administrator and navigate to the platform-tools folder
Reboot your phone into bootloader
Code:
adb reboot bootloader
Boot into TWRP (the entire twrp filename is required)
Code:
fastboot boot twrp-version.img
Once TWRP boots up, you can "Keep System Read only?" by selecting "Keep Read Only"
Extract boot.img
The following code copies the boot.img from your device to the platform-tools directory of your PC.
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
adb pull /tmp/boot.img
Reboot your phone
Code:
adb reboot
Patch the boot.img with Magisk Manager
Copy boot.img you just extracted to your 7T Pro internal storage using MTP or
Code:
adb push boot.img /sdcard/Download/boot.img
Open Magisk Manager and tap on Install (Magisk, not Manager). You can use stable or beta, but I would recommend beta if you're looking to fiddle around with custom kernels.
Choose "Select and Patch a File"
Select the boot.img you just placed on the internal storage. Magisk will patch the image to your device's sdcard/Download/ folder as magisk_patched.img
Copy the Magisk patched image to your PC
Code:
adb pull /sdcard/Download/magisk_patched.img
Install the magisk_patched.img
Reboot to bootloader
Code:
adb reboot bootloader
Reboot your phone using magisk_patched.img
Code:
fastboot boot magisk_patched.img
Open Magisk Manager and tap on Install (Magisk, not Manager)
Select "Direct Install (Recommended)"
Reboot
IMPORTANT NOTE: I noticed with 10.0.14HD01AA, Magisk 21.4 and Magisk Manager v8.0.7, the patched image name has changed to "magisk_patched_v5XCB.img" (at least for my device). I'm not sure if the 'v5XCB' is the same for anyone else trying to root for the first time. Just make sure you use the proper filename in full (i.e. "magisk_patched_xxxxx.img") in Step 5 of "Patch the boot.img with Magisk Manager" and Step 2 of "Install the magisk_patched.img"
Retain root/Magisk after OTA update
There's a pretty good guide written already by @daveuk87 so you can check that thread.
If there are any areas within these instructions that are not clear or flat out wrong, please let me know so I can make necessary edits/changes.
Guide created: November 24, 2020
Last updated: March 26, 2021
RESERVED
thanks for this detailed root process, I've been looking for this for around 3days. (my OP7t pro is coming today will try this root method)
Anyone tried it sucesfully already on A11?
Tribux said:
Anyone tried it sucesfully already on A11?
Click to expand...
Click to collapse
No. There is no working TWRP for A11 on the 7T Pro right now.
If you've already got Magisk on A10, then follow the retain root guide above after upgrading to 11 to keep root.
Hw4ng3r said:
No. There is no working TWRP for A11 on the 7T Pro right now.
If you've already got Magisk on A10, then follow the retain root guide above after upgrading to 11 to keep root.
Click to expand...
Click to collapse
I don't have a magisk, so I need to do rollback to A10 probably. Thaks for an answer
Hw4ng3r said:
No. There is no working TWRP for A11 on the 7T Pro right now.
Click to expand...
Click to collapse
It IS working TWRP from LR.TEAM
Can't be posted here as link to the source made as picture with Chinese letters on they site - don't have Chinese keyboard to type this.
And it working! I'm use it!
Tribux said:
I don't have a magisk, so I need to do rollback to A10 probably. Thaks for an answer
Click to expand...
Click to collapse
This method (start to finish) doesn't work on A11, but you can always grab the boot.img using payload dumper or the correct boot.img from here and patch/install using the patch and install steps in this guide.
Hw4ng3r said:
This method (start to finish) doesn't work on A11, but you can always grab the boot.img using payload dumper or the correct boot.img from here and patch/install using the patch and install steps in this guide.
Click to expand...
Click to collapse
Could you please provide full guide for rooting android 11, i managed to root but after reboot i loose the root
When I get to
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
adb pull /tmp/boot.img
the window just closes with no message after 2 minutes or so with a # under the command and there is no boot.img in my platforms folder.
Potatoman31 said:
When I get to
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
adb pull /tmp/boot.img
the window just closes with no message after 2 minutes or so with a # under the command and there is no boot.img in my platforms folder.
Click to expand...
Click to collapse
Download latest magisk apk, rename it to .zip instead of .apk.
Bot twrp
adb push magisk.zip /tmp
Go to twrp, tmp folder and flash zip.
Hi everyone,
Is it possible to have an explanation about how to root the OP7T Pro one OxygenOS 11.0.1.1.HD01BA ?
Because it sound like crazy, some of the topics are old, some say it work, some it doesn't, some are for the 7T, ect...
I'm feeling lost and would appreciate some help to clarify all of this, thank you very much.
The Magisk process is the same once you obtain the boot.img for the firmware you are using. Use payload dumper to extract the proper boot.img instead of TWRP/adb
Thanks. So this topic is right for the 7T Pro as well ?
=> https://forum.xda-developers.com/t/guide-android-11-how-to-root-oneplus-7t.4253183/
If no, could you kindly provide me a link were i could start ?
gd*T said:
Thanks. So this topic is right for the 7T Pro as well ?
=> https://forum.xda-developers.com/t/guide-android-11-how-to-root-oneplus-7t.4253183/
If no, could you kindly provide me a link were i could start ?
Click to expand...
Click to collapse
Use below as a guide:
(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
Nice, thank you very much !
Hi!
I am new to OnePlus 7T Pro. The device I have is on Oxygen 11.0.11.HD01BA
Via this howto https://www.droidwin.com/install-twrp-oneplus-7-pro-android-11/ I found a TWRP from @Nebrassy that works with "fastboot boot". But I am unable to flash it. (On Slot A there seems to be an OS, but Slot B says no OS installed.)
And I am also unable to find a support thread for Nebrassy's TWRP for 7T Pro!?
So that's why I am asking here.
If you have any hint for me, I'd really appreciate it.
Tnx in advance,
Enkidu
enkidu70 said:
Hi!
I am new to OnePlus 7T Pro. The device I have is on Oxygen 11.0.11.HD01BA
Via this howto https://www.droidwin.com/install-twrp-oneplus-7-pro-android-11/ I found a TWRP from @Nebrassy that works with "fastboot boot". But I am unable to flash it. (On Slot A there seems to be an OS, but Slot B says no OS installed.)
And I am also unable to find a support thread for Nebrassy's TWRP for 7T Pro!?
So that's why I am asking here.
If you have any hint for me, I'd really appreciate it.
Tnx in advance,
Enkidu
Click to expand...
Click to collapse
[CLOSED][No longer in development] [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project (7T / 7T Pro)
Status: development dropped. If you want to pick it up, sources are available in my or twrp's GitHub. Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We...
forum.xda-developers.com
Nebrassy is not maintaining one for 7T/Pro, I am.
Hello @ all.
I need some help with my oneplus 7t pro and the new available twrp for the 7t pro.
I updated this phone now to Android 11 and stay on Oxigen OS 11.0.3.1 HD01BA now.
I loose my Root also with this update.
What I must to do for have the new version from this twrp and Root again on my phone?
The bootlocker in unlocked already.
I not find something on xda about some people do with android 11 and the new twrp for the One Plus 7t pro.
This one I hope someone can help me with this problem.
Here are all the boot.img and recovery.img of OxygenOS 11.0.0. Since TWRP isn't ready yet, I guess a lot of people need it if they didn't keep their root permissions.
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
OOS 11.0.0 EU:
boot.img
boot.img (Magisk v22 patched)
recovery.img
OOS 11.0.0 GLOBAL:
boot.img
recovery.img
OOS 11.0.0 INDIA:
boot.img
recovery.img
Please note: I'm not responsible for anything you do to your device. You use these files at your own risk. I will not provide any further .img files nor ask me for patched files. Any contribution with patched boot.img files is welcome of course. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!
Would I be able to keep my phone rooted with this after updating?
This is very useful
thanks
jman12311 said:
Would I be able to keep my phone rooted with this after updating?
Click to expand...
Click to collapse
No, unless you use the Magisk patched EU version. Otherwise always install the update, then use the Magisk Manager to patch the inactive slot and then (only then!) reboot. Then you'll keep root.
Otherwise use the stock boot.img and patch with Magisk Manager. Then flash the patched image via fastboot. There are plenty of tutorials on XDA
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Janusk22 said:
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Click to expand...
Click to collapse
1. Install Magisk manager app
2. Open the app and choose "Install to inactive slot (After OTA)"
3. Reboot!
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Janusk22 said:
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Click to expand...
Click to collapse
Use USB debugging and a PC with the code:
Code:
adb wait-for-device shell magisk --remove-modules
If USB debugging isn't enabled, flash the stock boot.img (without root), boot it, enable ADB debugging and allow the connection to the PC. Then flash the patched boot.img and execute the command above
That is assuming you have a OnePlus 7T Pro which doesn't have a decryptable recovery. Otherwise you can simply flash the Magisk uninstaller
But i have a error I think that i cannot write in system
I have always : cannot be accessible
Thanks i just had to run the command when i rebooted
Is just me or GPS takes more time to "fix" satellites?
FSadino said:
Is just me or GPS takes more time to "fix" satellites?
Click to expand...
Click to collapse
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Macusercom said:
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Click to expand...
Click to collapse
I calibrated the A-Gps again, let's see if that was it. Thank you
Hi I was wondering if you could possibly share the android 11 update file I have a Oneplus 7T Pro HD1910 currently on OOS 10.1.14 It would be awesome if you can PM me. I've tried downloading from Oygen Updater it fails at 98% also on XDA forum the download fails. I'd really appreciate it. Thanks
Macusercom said:
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
Click to expand...
Click to collapse
Hey, could you please share the payload.bin extract procedure?
Ia possible to use this files to back to stock rom from lineageos 18.1? If yes, can someone help me and give me the procedure how to do this?
For all the "EU" and "global" files, I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.