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
Related
So, has anyone tried flashing an android p image yet?
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
For flashing steps:
For ab device
unzip both. move the .img file from extracted gsi to platform-tools.
open command prompt or terminal. naviagte to above folder.
boot phone into fastboot mode.
connect phone to computer.
now,
fastboot devices
check device is detected
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
above command (-w) will wipe all your data so make sure to backup
then fastboot reboot
boom
Pie
menphis said:
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
For flashing steps:
For ab device
unzip both. move the .img file from extracted gsi to platform-tools.
open command prompt or terminal. naviagte to above folder.
boot phone into fastboot mode.
connect phone to computer.
now,
fastboot devices
check device is detected
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
above command (-w) will wipe all your data so make sure to backup
then fastboot reboot
boom
Pie
Click to expand...
Click to collapse
Any bugs?
menphis said:
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
For flashing steps:
For ab device
unzip both. move the .img file from extracted gsi to platform-tools.
open command prompt or terminal. naviagte to above folder.
boot phone into fastboot mode.
connect phone to computer.
now,
fastboot devices
check device is detected
fastboot erase system
fastboot flash system name_of_system.img
fastboot -w
above command (-w) will wipe all your data so make sure to backup
then fastboot reboot
boom
Pie
Click to expand...
Click to collapse
I did this, bootloop. I have a redmi note 5 now
Yes it works on mi a2 lite
Sent from my iPhone using Tapatalk
Agreed, it works quite well.
You guys are lucky. Lol. Hopefully some devs picks up mi a2 lite.
With treble all treble GSI ROMs an partition should work no matter The device
Yeah, its odd that i faced bootloop. I followed the steps, it was successful but it didn't boot
ouroboros12 said:
Yeah, its odd that i faced bootloop. I followed the steps, it was successful but it didn't boot
Click to expand...
Click to collapse
Enter the recovery stock and make wipe
Mi a2 lite?
ouroboros12 said:
Yeah, its odd that i faced bootloop. I followed the steps, it was successful but it didn't boot
Click to expand...
Click to collapse
What phone do you use?
yes is working fine but camera didn't work and data connection. i moved back to android one. everybody found somthing to flash redmi 6 pro miui version? also i need some help where i found the config file for daisy device features xml. for enable manual control for device. I flashed via magisk mi a2 camera with working manual exposure 32 sec. working absolutely amazing, but unfortunately the portrait is force to close the apk or hanging out.
Here's what I've learned far about the E6:
Mostly from Treble Info app from Hackintosh Five
VNDK-28
Arm32 BINDER64
It's actually AB, according to it having System As Root.
No Seamless upgrade.
Binder64-AB/A64-AB GSIs work on this device.
Quack GSI should be the first we focus on.
TO INSTALL:
Code:
fastboot -w flash system <gsiname.img>
BOOTS
Quack GSI (AOSP 10, bb)!
Will list others as I come across them.
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
LgPWN'd said:
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
Click to expand...
Click to collapse
Yes, please! it's very nice that u did that, I'll link it in the main post when u do
For a working recovery see this
https://forum.xda-developers.com/moto-e6/development/development-team-looking-testors-t4120171
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
soulmaker2207 Did you do the -w in fastboot after you installed the gsi? If you didn't it is definitely worth a try Beware it will erase all data including the internal sd
soulmaker2207 said:
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
Click to expand...
Click to collapse
Alongside the fastboot -w advice, try renaming every img you download to "system.img." I have had way more success doing that than using long img names.
Also, I noticed that for a lot of GSIs, USB Tethering does not work.
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
scottyrick2 said:
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
Click to expand...
Click to collapse
Yeah USB Tethering doesn't seem to work for ANY GSI ROMs.
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
scottyrick2 said:
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
Click to expand...
Click to collapse
How odd. I can't get any Android 11 GSI to work on my E6
Are you trying to update from Android 10? I don't think you can.
scottyrick2 said:
Are you trying to update from Android 10? I don't think you can.
Click to expand...
Click to collapse
Yes I was trying to update from Android 10
I am running phhusson aosp 11 v300.l gsi rom right now. Super fast. Amazing, really.
If you are on the T-Mobile system, you need to do 3 things in order to make VoLTE and sms work properly. Hopefully, this will not be needed in future updates, but it might be.
1. using a root file explorer (I use 3C) to locate and move the org.codeaurora.ims folder from /data/app to /system/app
2. reboot
3. using *#*#4636*#*# on the dialer to open "phone information menu", change the band to GMS/WCDMA/LTE, and close the menu.
That's it. I hope this helps you to consider moving up to gsi roms. They are truly amazing.
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile2.bat with the following and put this .bat file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the flashfile2.bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
b00ster23 said:
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile.bat with the following and put this file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the .bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
Click to expand...
Click to collapse
ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
Something to make it easier on others.
There was a link for TWRP on this post but had to remove it because the link is dead. I'll explore other options before re-updating this post
koyo said:
Some things to add to this post to make it easier
1) ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
2) I prefer doing it via this method rather than flashing stock files: - E6 AIO ToolKit Mod Release- | XDA Developers Forums (xda-developers.com)
This has a TWRP for E6 which allows you to flash things like magisk, universal encryption disabler, gapps, et cetera. Things that might not be built into the native ROM.
Click to expand...
Click to collapse
The links are all broken, and I see no TWRP available.
b00ster23 said:
The links are all broken, and I see no TWRP available.
Click to expand...
Click to collapse
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
koyo said:
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
Click to expand...
Click to collapse
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
b00ster23 said:
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
Click to expand...
Click to collapse
Telegram: Contact @Android_General_Chat
t.me
I saw a lot of outdated methods of rooting this phone that will cause a lot of bugs to the device, because of the outdate magisk_patched boot image
HERE'S AN UPDATED VERSION
REQUIREMENTS
Unlocked bootloader
Minimal ADB + Fastboot ( I use 1.4.3 PORTABLE) https://forum.xda-developers.com/showthread.php?t=2317790
Pack with required images, including the new magisk_patched.img (required_files.zip, at the bottom of the post)
INSTRUCTIONS
Extract both the minimal adb + fastboot and required_files.zip to a folder
Boot your device in fastboot mode (power if off, then press power button + volume down until you see a bunny working on a Android robot)
Connect the device to the PC via a USB cable (I suggest the one you use of the charger too)
Copy the images from required_files.zip to the folder where you extracted minimal adb + fastboot
Open a cmd/powershell window in minimal adb + fastboot folder (make sure once again that you copied the files from required_files here)
Type these commands:
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
Enjoy! Your phone will reboot (it shouldn't take more than usual btw)
WARNING!
I'm not responsable for any damaaged device, you take the risk
What I basically did is gave you guys an updated magisk_patched image because the the one seen on the internet for now is an old one that caused several problems on some devices, if you're running any other version that the one in the title you should make your own magisk_patched image
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
alpersoft said:
Does this method erase user data and do a factory reset, as other guides say?
I know there is always a risk and it's important to make a backup, but my question is if everything goes as expected, is the phone data erased?
Other guides do the command "fastboot erase userdata" before "fastboot erase cache".
Click to expand...
Click to collapse
I removed the erase data line cuz I didn't saw why it would be required since it was working great without it
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
HemanthJabalpuri said:
@Bogdi_P
Can you please share how you did modifications?
I am on MIUI Global 12.0.2 Stable 12.0.2.0(QJOINXM) which is an Indian ROM. Model is M2003J15SI.
I downloaded my firmware zip from Updater -> Download latest package.
I can take boot.img, vbmeta.img from it.
After I can patch the boot.img with Magisk.
But what I have to do with vbmeta.img?
Click to expand...
Click to collapse
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Successfully rooted + edXposed on STOCK rom and GSI roms.
Patched my own boot image (magisk_patched.img) with magisk manager.
To make Netflix & some other apps work, get the liboemcrypto disabler module in Magisk Manager
Also, to pass SafetyNet:
- Enable Magisk Hide
- Install and activate the Riru - Core and Riru - EdXposed (YAHFA or SANDHOOK, both work) modules in magisk manager
- Get EdXposed manager
- Get the HiddenCore Module and activate it
- In EdXposed Manager: Compat List, and tick HiddenCore Module
To avoid issues (Chrome crashes, potential SIM issues, etc..) with HiddenCore:
- In EdXposed Manager, go to Settings > Framework > Enable "App List mode"
- Still in EdXposed Manager, go to Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Play Store, Google Services Framework
- Reboot and enjoy, you're all set and SafetyNet should pass just fine, and you can do whatever you want.
i have question: vbmeta.img above can be used for all versions of miui or only ver 12.0.2
i am using ver 12.0.3 eea
Pls help not working 12.0.3
tanks
I have patched the image with magisk manager
ma259 said:
You can manually patch vbmeta file using an Hex Editor or you can download any already patched vbmeta file for any MIUI version for this device and flash it.
Click to expand...
Click to collapse
can i download your vbmeta and work for 12.0.4? maybe? yes? no?
New member here! Will this work also on miui 12.0.5 global?
I have not installed root and the phone is not restored
What is working for MERLIN ?
Take a look: https://forum.xda-developers.com/t/...aomi-redmi-note-9-xiaomi-redmi-10x-4g.4204873
V11.0.5.0:
MAGISK: Working.
MAGISK MANAGER: Working.
TWRP: Working.
RIRU-CORE: Working.
RIRU-EDXPOSED: Working.
EDXPOSED-MANAGER: Working.
XPRIVACYLUA: Working.
MINMINGUARD: Not tested yet.
TITANIUMBACKUP: Not tested yet.
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
accnetdev said:
Hi,
I was in 12.0.2 following your method :
fastboot devices
* Make sure that your phone it is recognized by the PC using this command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
my phone can only boot in fastboot no longer in system.
I am able to go to stock recovery using power + up but I would like to avoid to reset my phone.
Please help what's wrong, can someone help ?
Click to expand...
Click to collapse
same here
Hello
I've just ordered my Pixel 6 Pro, coming from the OnePlus 8 Pro.
I love tinkering with Root/Kernels/Roms.
So my question is, if there is always a way to get back to stock in case of emergency?
The OnePlus phones are considered as "unbreakable", because You can ALWAYS unbrick it via MSM unbrick tool.
Would be nice to know when I start unlocking the bootloader of my Pixel
Thanks!
Sorry that Pixel doesn't have that unbrick tool ...
The only one is a batch commend file - Flash-All extracted from factory full ROM ...
It is possible to hardbrick a Pixel device without hopes of getting it running again, for example if you nuke your recovery.
Most softbricks can be solved by either doing what Kris Chen suggested, or by using
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
After flashing a module that bootloops you can try this:
If it almost boots up but flashes, in a cmd window type:
adb wait-for-device shell magisk --remove-modules
It may grab that and remove all modules. If it doesn't, you can try this:
1. fastboot flash boot boot.img, reboot.
2. long press power button, then long press "power off", click ok to enter safemode.
3. Before your phone boots all the way up, boot to fastboot.
4. fastboot flash boot magisk_patched.img, reboot.
5. In cmd window type: adb wait-for-device shell magisk --remove-modules
6. Your phone will boot up with root and all modules removed.
There's a shortcut to safemode that removes everything but I'm not sure what it is.
Edit: boot.img is taken from the applicable firmware you are on downloaded from Google. Unzip the main zip, go into the folder and unzip the image zip that is inside.
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Lycidias said:
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Click to expand...
Click to collapse
Yes, correct, and yes, safest to do so each time switching kernels.
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