Develop Bugs

[GUIDE]*How to install a Generic System Image (GSI) on your HTC U12+

Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (WARNING : According to 5m4r7ph0n36uru, you can't flash vbmeta via fastboot if your device isn't S-OFF, you have to use TWRP, but I don't know how, so ask someone who knows! I will update my tutorial once I see instructions.)
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!

Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello, which GSI did you tried from the list? If you tried more then one, which is the one that runs better?
Thank you

Hi!
I have tried AOSP 10.0 v206 system-quack-arm64-ab-gapps.img. v208 is out now.
I still have to try others.
Let us know if you find one working better than others!

i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.

mientus25 said:
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
Click to expand...
Click to collapse
Hi mientus25! I'm sorry if you bricked your smartphone trying to flash it. I think the --disable-verity option not working was a matter of platform tools (adb) version.

My htc have actually hard brick. I will try to send it to the service(warranty). Will tell you what comes of it.

fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked

xreeman said:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
Click to expand...
Click to collapse
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.

5m4r7ph0n36uru said:
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
Click to expand...
Click to collapse
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much

GaetanoS.89 said:
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
Click to expand...
Click to collapse
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.

5m4r7ph0n36uru said:
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
Click to expand...
Click to collapse
All right, would you please write a message over with all the steps here? Thank you

GaetanoS.89 said:
All right, would you please write a message over with all the steps here? Thank you
Click to expand...
Click to collapse
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Code:
adb reboot bootloader
Delete the system and data partition by
Code:
fastboot erase data
and
Code:
fastboot erase system
Flash the nonverity vbmeta image via
Code:
fastboot flash vbmeta nameofvbmeta.img
(the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via
Code:
fastboot flasch system nameofgsi.img
(the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu

https://www.xda-developers.com/goog...al&utm_source=twitter.com&utm_campaign=buffer
Wiil this work with the U12+???

It may work for GSIs with a fixed verity status. Thus it doesn't work for some Android 10 GSIs without flashing a noverity vbmeta as. Thus I decided long ago, to never recommend such tools, and not to help people who used one, as those using such tools most of the time didn't even care learn the basics of adb and fastboot. I can't remember anyone, who used a tool, who's ever been fully capable to identify potential problems and errors, let alone how to solve them. And the latter is the baseline to start modding a device.
Sent from my Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Delete the system and data partition by and
Flash the nonverity vbmeta image via (the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via (the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
Click to expand...
Click to collapse
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?

Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello I am trying to follow all the steps on the guode, but when I have to flash the vbmeta file from Bootloader Mode I am getting this:
C:\Users\User\Desktop\ADB2>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Not allowed on PRODUCTION device')
fastboot: error: Command failed
If I try to install the vbmeta from Download Mode I am getting this error

GaetanoS.89 said:
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Click to expand...
Click to collapse
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.

5m4r7ph0n36uru said:
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
Click to expand...
Click to collapse
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?

GaetanoS.89 said:
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
Click to expand...
Click to collapse
Which software version are you running!?
Sent from my Pixel 4 XL using XDA Labs

5m4r7ph0n36uru said:
Which software version are you running!?
Click to expand...
Click to collapse
I was running Android 9 stock. After a few trials I have been able to install and boot the Pixel Experience and the permessiver and everything seems to work without flashing the vbmeta file

(GUIDE) Unlocking bootloader, Rooting - from start to finish UPDATED.

Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the bootloader unlocking and root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods but I can confirm that this 100% works
NOTE* This guide is intended for all OnePlus 8 devices but the boot image files are for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
It is possible to extract the boot IMG from any firmware using the payload extractor tool which can be found online, then change the commands to reflect the files you obtain, for the sake of clarity I'll be using 10.5.12
Hope this helps.
Pre-requisites
A European variant of the Oneplus 8 Pro: IN2023
Running the following firmware: 10.5.12 IN11BA
ADB Access to your phone
A decent amount of charge, eg: 80%
A Windows 10 based computer
The cable that came with your phone
Obtaining ADB access to your device using your computer
1. Connect your phone to your computer using the cable that you charge it with
2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then install the driver you can obtain from the drive which will appear on screen within "This PC" (i won't detail this as it's pretty self explanatory)
3. On your phone Open settings and navigate to "About phone"
4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"
5. Back out, then click "System"
6. Scroll down to "Developer Options" and open it.
7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it, also turn on) also turn on "OEM Unlocking" in the same section and agree to any prompts.
8. On your computer Download this folder https://drive.google.com/drive/folders/1S-yNzdvOvdZzPuxhYuEuwnelzfdEd0K2?usp=sharing
This is adb and fastboot so you can talk to your phone via your PC.
9. Move it to the root of the C: drive, so it looks like this in the filepath
C:\Android
10. Navigate to the folder and perform the following:
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
11. In the window type the following command
adb devices
press enter
If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.
You should see a readout of a device followed by a code, you now have ADB access and can continue.
Unlocking the bootloader
NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO
1. Connect your phone to your computer
2. On your computer Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
3. Type the following command into the window
adb reboot bootloader
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
4. On your computer Type the following command into the window
fastboot oem unlock
press enter
NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE
5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots
You have just unlocked the bootloader to your phone
Once the device has booted, set it up again and then follow the steps to unlock "developer options" and "USB Debugging" once more.
Installing Magisk Manager and obtaining Root access
Before you begin, please follow these two steps to install the magisk manager
Magisk manager
i) On your computer download this folder https://drive.google.com/drive/folders/1VH_2Ql6L5580rVYvRZ5l8t7cX2XENEAG?usp=sharing and move the file inside to your internal storage on your phone, the file is called "MagiskManager-v7.5.1.apk"
ii) On your phone using a file manager navigate to where you moved the file and open it, this will install the Magisk Manager used to manage root access, open the Magisk Manager once, you'll see it does not have root access.
Rooting
1. On your computer Go here https://drive.google.com/drive/folders/189DlZH1NSMrgVF996S7y3q5_IG9RAFIr?usp=sharing and download the folder
2. Copy the file inside the folder which is called "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. There are two options for rooting, the first is to boot it first, this is safer as it is not permanent and a reboot will rejoice the booted image, the second is to flash it, this is a one step option but if the image isn't right then you could end up in a bootloop so id recommend the first.
Type the following into the window
To boot:
Fastboot boot magisk_patched.img
(Your phone will reboot automatically)
To flash:
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
then
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
NOTE* If you booted the image then simply click the top install option then go to install directly, this will make root permanent.
That's it, you've now unlocked your bootloader and rooted using the most current boot img at the time of writing.
------------------------------------------------------------------------------------------------------------------------------------
Please don't quote the entire thread!!!!!
If i've missed anything out or anyone notices a mistake please let me know and i'll amend accordingly.
Alternate second guide here on post #55 thanks to @flushell
https://forum.xda-developers.com/showpost.php?p=83534273&postcount=55

dladz said:
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods.
NOTE* This guide is intended for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
Hope this helps..
Click to expand...
Click to collapse
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though

pyry666 said:
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
Click to expand...
Click to collapse
Ok so by not specifying a slot you are flashing to both afaik
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.

dladz said:
Ok so by not specifying a slot you are flashing to both.
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
Also please don't quote the entire guide it makes reading threads awful, edit your post please.
Click to expand...
Click to collapse
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too

pyry666 said:
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
Click to expand...
Click to collapse
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?

dladz said:
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
Click to expand...
Click to collapse
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now

pyry666 said:
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
Click to expand...
Click to collapse
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway

dladz said:
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
Click to expand...
Click to collapse
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues

pyry666 said:
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
Click to expand...
Click to collapse
Or just follow the above guide if you meet the requirements
Command for swapping slot is
fastboot --set-active=a
Or b

Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Bootloader unlock works same no matter what model you are using. You can just boot twrp and flash magisk from there

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.

dladz said:
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
Click to expand...
Click to collapse
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So in order.
1 Download the full ROM for your device and region.
2 Open it in on a computer and extract the bin file called payload, it'll be about 2.4GB.
3 Then copy it to the payload dumper input folder and run the exe
4 You'll get the boot image as well as some other files, copy the boot image to your phone and patch it using magisk.
5 Then pull the output magisk patched.img to your adb folder and flash to slot A or B or both. I did both

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So how did it go?? All good?

dladz said:
So how did it go?? All good?
Click to expand...
Click to collapse
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!

I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file

A.Priori said:
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
Click to expand...
Click to collapse
Well done, always good to come back from the dead

N'ash said:
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
Click to expand...
Click to collapse
Yea that annoys me too.
There will be a way I'd imagine, but you wouldn't want to get that script wrong..
Might look into getting that gone, HTC had this too as do a few devices.
Possible a precious guide for an older device may work but using it to test would be a risk..

After doing this, is it still possible to install official OS builds from OnePlus whenever a new build comes out? Either via a zip or OTA?
For instance when 10.5.13.IN11BA comes out or whatever?

Question Help I made a mistake and updated something in the development settingsAnd the recovery does not workLE 2120

On the screen I get: your device is corrupted and cannot be trusted and cannot reboot

Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...

blackhawk said:
Simply disable Developer options and the any settings you altered there will revert to baseline.
If that doesn't get it then it's not Developer options...
Click to expand...
Click to collapse
Thanks for answering
The device may boot into a bootloader or an error on the screen

EranG90 said:
Thanks for answering
The device may boot into a bootloader or an error on the screen
Click to expand...
Click to collapse
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock

craznazn said:
You locked the bootloader while running modified software.
Unlock it again
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you
I have now done that and the screens are in the same condition as in the pictures
It is good? Should I keep waiting? (I don't know really what to do, I am new at this. I don't know even if the device got the commend from the pc)

We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.

djsubterrain said:
We can't really help you until you confirm what you did to get it in this state in the first place?
Did you install the OxygenOS 12 Developer Preview?
Did you try rooting by replacing the stock boot.img?
Please confirm what caused this in the first place as changing something in the developer settings alone would not cause this.
Click to expand...
Click to collapse
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper

EranG90 said:
Sorry like I said before I am new at this
I have change somting in the DSU option. I think this was the Acronyms
I believe I chosed GSI+"Somting"
then the device rebbot with qualcomm screen and then the error apper
Click to expand...
Click to collapse
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
You need to have previously allowed bootloader unlocking in your developer options (see below)

djsubterrain said:
OK, If you used DSU to try out the Android 12 Developer Preview your bootloader needs to be unlocked, try running :
fastboot oem unlock
Bear in mind it will wipe the phone though, then reboot back into the Android 11 rom, set it up and THEN try DSU.
Click to expand...
Click to collapse
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)

EranG90 said:
Thank you
I have run this command and waited 40 min with thoose screen and stop becuse I did't saw nothing in progressing.
It is good? Should I keep waiting? (I don't know really what to do, I don't know even if the device got the command from the pc)
Click to expand...
Click to collapse
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?

EranG90 said:
Thank you so mach
I fixed my Pc usb and done the command and unlock oem
now I got only bootloader in my device
the recovery and the start options reboot the phone to the bootloader only
What I need to do now do get androird 11 back to the device?
Click to expand...
Click to collapse
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.

djsubterrain said:
If you're stuck on bootloader only you can try running these commands in fastboot :
fastboot -w
fastboot --set-active=a
fastboot reboot
If the phone does not boot properly then try these :
fastboot -w
fastboot --set-active=b
fastboot reboot
"fastboot -w" wipes your userdata. The "fastboot --set-active" command tells the phone which A/B slot you want to use, "fastboot reboot" is the command to restart the phone.
If you just keep getting sent back to fastboot and it won't boot then you're likely going to have to use the MSM tool to restore the phone to factory settings.
Click to expand...
Click to collapse
Really really thank you
I have tried all 4 commands (-w, --setactive=a/b and reboot)
all of them after I turn off and back on my phone show me the bootloader
can you send me a link to how I use the MSM tool to restore the phone to factory settings?

You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.

craznazn said:
You have a LE2120 so there is no msm package publicly available yet.
In the screenshots, it shows that your fastboot drivers are not installed. Did you fix that first? The command take less than a second to run.
Click to expand...
Click to collapse
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this

EranG90 said:
Yes all the commands are run very fast it is no longer whiting for device
and the device state is unlock
what can I do to get android 11 on my phone? I am really new in this
Click to expand...
Click to collapse
try
Code:
fastboot reboot fastboot
and what shows up?

https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat

craznazn said:
try
Code:
fastboot reboot fastboot
and what shows up?
Click to expand...
Click to collapse
thank you for answring
that what show up:
Rebooting into fastboot OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Shooter7889 said:
https://forum.xda-developers.com/t/...u-via-msm-no-unlock-bin-needed.4272837/unread
You can download and take the flashall.bat from this conversion guide and download your version of oneplus9pro rom to your pc then use payload dumper to extract all images, then place the flashall.bat in the same folder as all your files you dumped then plug ur phone in(while it is on bootloader screen) and double click the flashall.bat
Click to expand...
Click to collapse
Thank you
I will try anything to fix that but I am new in all this
Where I am download the flashall.bat? where I save it? How to run it?
I have download the global version for onplus9pro. What I need to do with it?

https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat

Shooter7889 said:
https://androidfilehost.com/?fid=14943124697586337355
This is the link to the op's zip(he created for the thread for converting tmobile variants to EU). . Click the link and download the zip, put it on your pc, then u have to extract all files. The flashall.bat is one off the files in that zip.. Then Google search the Chinese version of tue latest op9pro OS11.. Get it on your pc. U have to use payload dumper(which you will need to search android get on ur pc, extracted as well). Then once u get payload dumper ready, and ur rom, take them payload.bin from ur rom folder and put it in the payload input folder. Then double click the payload.bin and it will slowly extract all your files and put them into the payload output folder. Once it's done take the flashall.bat and put it in there. Then ur ready to plug ur phone in(in bootloader mode) and double click the flashall.bat
Click to expand...
Click to collapse
And honestly, you could prob just download the zip I mentioned, the first one just to get the flashall.bat, and just extract it, plug ur phone in(in bootloader mode) and click the flashall.bat. It would put the EU version of OS on your phone. Use cld then use the loavl update in system settings to switch to ur variant after. Much easier.

[GUIDE] How to Make KonaBess Work with OxygenOS/ColorOS 12/12.1 (Preventing crashdump & boot destroyed)

First of all, i don't accept any responsibilities as rooting and unlocking bootloader is the user's own choice, if any damage or problem occurs, you are responsible for your own actions.
Before starting, i am assuming you have rooted your device. If not you can search for the guides on rooting these specific ROMs.
Anyways, get the latest KonaBess version from here.
Steps are split in THREE sections depending on how you want to get the needed images. First section is by using FULL ROM ZIPs. Second is by using Msm Tool. THIRD is the main section.
FIRST SECTION
If you have the FULL OTA zip of your rom (OOS/COS 12/12.1) then what you need is Fastboot Enhance to dump your payload.
You need to extract boot, dtbo and vbmeta images from your payload. (boot & dtbo for backup.)
Put the those 3 images inside your ADB-Fastboot tools folder.
SECOND SECTION
You need a proper working Msm Tool. Get one from here.
You need to know which slot you are currently on. Reboot to fastboot, enter the command:
Code:
fastboot getvar all
Near the end you will see "(bootloader) current-slot:a or slot:b"
Don't forget that current slot.
Now Open Msm Tool.
Select Other.
Press F8. Here in this list you need to select boot_a/b, dtbo_a/b and vbmeta_a/b. Remember the current-slot: from fastboot? You need to select those 3 partitions of a or b depending on what you get from current-slot:x.
Password is "oneplus".
There will be a new Read Back button below Target. Connect your phone in EDL and click Read Back. After it is completed, open your main drive on your pc. You will see the images there.
Put the those 3 images inside your ADB-Fastboot tools folder.
THIRD SECTION
Reboot to fastboot.
Enter this command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Now reboot and open KonaBess. It will prompt you which chipset data to use. Always select the one with "This may be the chipset data your device are using."
Then like before, use SD865 Freq Table, be sure to match your clocks with GPU Volt Table.
If you mess things up, you can use those boot and dtbo images you got from the payload/read back to restore back to stock.
(fastboot flash boot boot.img & fastboot flash dtbo dtbo.img.)
Now you won't get crashdump or boot destroyed warnings. N joy​

how to root ?my device op8 and12 c.16
<Moderator Edit>: Duplicate of this post.

Kobir_papon said:
how to root ?my device op8 and12 c.16
Click to expand...
Click to collapse
Before starting, i am assuming you have rooted your device. If not you can search for the guides on rooting these specific ROMs.
Click to expand...
Click to collapse

Hi. vbmeta to flash in both slots a and b? tried to flash konabess without disabling verification (I didn’t know about it) and caught bootloop. I restored and want to try again

How To Guide how to root redmagic 8 pro step by step

hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%

afer download frimware copy to your phone then update via ota local update

topadstore said:
afer download frimware copy to your phone then update via ota local update
Click to expand...
Click to collapse
Have u tried recalibrate fingerprint?

kaiwayne said:
Have u tried recalibrate fingerprint?
Click to expand...
Click to collapse
The fingerprint will not work. Root the device. There are other ways to fix this problem

topadstore said:
The fingerprint will not work. Root the device. There are other ways to fix this problem
Click to expand...
Click to collapse
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint

topadstore said:
hello everyone this is topic for root redmagic 8 pro easy away
Frist Step Download RedMagic Rom From here
https://rom.download.nubia.com/Europe%26Asia/NX729J/V318/NX729J-update.zip
now open bootloader from developer option
reboot your phone to fast boot then enter this commind
Code:
fastboot flashing unlock
after unlocking boot loader
need to unlock cirital
Code:
fastboot flashing unlock_critical
reboot your phone to fastboot again open fastboot cmd and enter :
fastboot flashing unlock_critical
after finished all setting install magisk apk and patch
init_boot.img and boot.img
copy patch img from phone to windows folder after patch via magisk
now reboot your phone to fastboot and open fastboot cmd enter this cmd
Code:
fastboot flash init_boot_a xxxxxxxx
fastboot flash init_boot_b xxxxxxxx
fastboot flash boot_a xxxxxxx
fastboot flash boot_b xxxxxxxx
replace xxxxx with location patch in windows
I apologize if the explanation is not clear. If you have any questions, ask them here
this way is tested and working 100%
Click to expand...
Click to collapse
You do not need to patch boot.img and flash it, only patching init_boot.img is needed.

kaiwayne said:
I already know. The problem is even passing the test, i cant input any screen lock. Everytime i tried this msg appear "Screen lock was already changed. Try again with the new screen lock". Cant pass this step so cant move to fingerprint
Click to expand...
Click to collapse
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.

ugene1980 said:
Is there this section in the phones settings
Settings > Lock screen & security or Security > Clear credentials.
Click to expand...
Click to collapse
Yes but grayed out

kaiwayne said:
Yes but grayed out
Click to expand...
Click to collapse
Did you lock the bootloader again?

Lossani said:
Did you lock the bootloader again?
Click to expand...
Click to collapse
Dont need to ask the same thing everywhere,
Locking bootloader after you rooted = Brick....

Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....

VladimiroCampus said:
Excuse guys, after root is it possible to install a module to enable Hey Google with screen off (or in AOD mode)? Owners said that you can say Hey Google with RM8Pro only with screen on, so sad....
Click to expand...
Click to collapse
The other thing that bothers me is that if you have Google Assistant enabled, it breaks voice dictation. So you can't voice text if you want Google Assistant enabled. So sad!

May be interesting testing this phone with custom roms, like CRdroid or similar... a monster of power but with an operating system with some bugs it's a real shame....

topadstore said:
after finished all setting install magisk apk and patch
init_boot.img and boot.img
Click to expand...
Click to collapse
Thanks for the detailed guide.
But I came across this guide from Mr.PvT https://forum.xda-developers.com/t/root-red-magic-8-pro-v3-18.4556901/
He mentioned "Note: Absolutely do not patch the boot file, you will have a continuous boot error"
I am no expert in this, but will patching the boot.img by Magisk causing the situation Mr.PvT mentioned above?
thanks in advance!

i only patched the init_boot and that is all that is needed

Hi
Fingerprint not work with root? Any solution?
Then which is the command to relock the phone? Uninstalled root and.....

It's pretty easy to root the phone, but it's a more finicky to keep lock screen and finger print functionality. This root guide is more comprehensive and if you read the whole thread you will have success.
What worked for me: Working lockscreen after unlocking + rooting
Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin) Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first...
forum.xda-developers.com
Took me a few tries to do it

Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)

Dont_touch7 said:
Somebody said flash boot.img and init_boot
and Somebody said no need for boot.img
Who is more accurate?
And should I flash a and b ? Or just write that command?
fastboot flash init_boot (located file)
Click to expand...
Click to collapse
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot

DarkestSpawn said:
init_boot is all you need to patch with Magisk to gain root. Just flash it to the active slot. If you dont know your current slot:
fastboot getvar current-slot
Click to expand...
Click to collapse
Based on experience, you just have to run the command:
fastboot flash init_boot <patched_file>.img
It will automatically be flashed on the current active slot.