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

Moto G Power flashing guide

This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host

i cant seem to toggle to fastbootd. when i put in the code i get the really long list of codes. And if i go into recovery and use power+vol up to get to fastbootd that way, if i try to flash anything, it fails and says no file or directory found

ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple

babyj3sus said:
ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple
Click to expand...
Click to collapse
Where? Or it becomes clear as-you-go ?

mingkee said:
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host
Click to expand...
Click to collapse
is there an way without using LMSA, i cant download it cus i have linux

When flashing patched_boot.img I get this
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.420s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.428s​
I'm not new to rooting i'm familiar with rooting Motorola phones... I just can not figure out what I'm doing wrong. Please any help would be amazing.

NEVERMIND i figured it out lol

In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.

In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
abgrady said:
In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
Click to expand...
Click to collapse
Yes, same here. What's the point to post incomplete guide? It just creates more problems for those, who don't know what he's doing.
I've rooted various phones in the past, each model is a different process, so complete and exact guide is a must. I guess this guide is missing Magisk part, which could be found somewhere. But isn't it to hard to put everything in one place?

I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh! EDIT: I flashed my g power, stock 10, took the update, it's on 11 now. I rooted it, no sweat, lolinet has the firmware. Once you go root, there's no more taking updates - be cool with that, or, find a way.
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.

bronkish said:
I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh!
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.
Click to expand...
Click to collapse
How about flashing it upgraded to Android 11?

When the 11 firmware becomes available I'll do the exact same thing. Wouldn't you?

What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.

alpheus said:
What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.
Click to expand...
Click to collapse
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?

nevermind

bronkish said:
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?
Click to expand...
Click to collapse
Hey, thanks for the reply. Yes, rooting G Power is not my interest, Id rather flash LineageOS without any Gapps and fu....g shmuggle. Would you please point out the best way to flash previous Stock 10 on G Power with current 11 installed? The phone was upgraded to 11 when I got it.

See post #10. Just flash 10 ☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠, and then flash lineage 17.1. DOn't forget to flash copy-partitions before lineage. You gotta do it the 1st time you flash a custom rom over stock.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
Lineage is not official for this phone.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠

Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys

Mkami said:
Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys
Click to expand...
Click to collapse
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.

shylonite said:
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.
Click to expand...
Click to collapse
Thanks so much for your information! My phone is back to its originally stock and working 100%

Question 11.2.4.4 Update Ended Badly - Assistance is Needed on This One

Had an 11.2.3.3 Global rooted via Magisk OP9 Pro that I wanted to update via OTA to 11.2.4.4, which was offered via system update. I used Magisk to restore images before update, did the update, and then went back to install to inactive slot. Rebooted and it was still on 11.2.3.3 so I tried again. Upon trying again, my phone got to a Qualcomm debug/error mode. I experienced this before when on a different boot slot for some other diagnosis of another issue in the past so I switched boot slots.
The other boot slot is stuck in fastboot mode I come to find so I check what it shows if I reverted back to the other boot slot, which was the Qualcomm error. Now instead of a Qualcomm error, it shows language options, one of which is English, and then gives me "boot reason", "wipe data and cache" and "advanced". I believe this is the OnePlus recovery menu, which I have not needed to use before and in the past, used TWRP on other devices.
Can't I just reflash a whole system image for 11.2.4.4 (it'd have to be the European one right now since Global isn't available) via fastboot and it should be fixed, albeit unrooted and I can just re-root? I'd like to try this, but there's no "flash-all.bat" and I don't know the proper flash order for the Euro images within payload.bin as there's no xml file (I looked up a guide for directions on how to flash without flash-all.bat that I have used on other devices). Oh, and I tried to fastboot a known good boot.img and on one of the slots, it works fine, but still wont boot. The other gives error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". I'm stumped.
Wondering if this has been experienced by anyone else before. Wiping my device is the last resort and shall be avoided at all costs after how much I have configured it to my liking.
I saw the following on another guide:
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img

Followed this guide here after extracting the Europe full system image via Payload-dumper and it now boots somewhat, but after it looks like it's loading into OOS and boot is complete, I get a black screen instead of the lock screen. I get charging sounds when plugged into the computer, but just a black screen.
How to Create Fastboot-flashable Factory Image for Any OnePlus Phone
Learn how to create a factory image for any OnePlus phone and flash it using Fastboot. Useful for restoring stock OxygenOS software and unbricking.
www.thecustomdroid.com
Wondering if this has to do with the Europe 11.2.4.4 on my Global device. Going to try reverting to 11.2.2.2 Global full image now.

Geez, good luck

vibrantliker said:
Geez, good luck
Click to expand...
Click to collapse
Just tried flashing the older 11.2.2.2 images one at a time and now it's stuck in recovery...
The closest I can get it to full booting is with 11.2.4.4 Europe full image and I get a black screen only, after it boots up with the OnePlus logo. When plugged in, I get a charging sound every 10-20 seconds or so. Too bad there's no 11.2.4.4 full image for Global or I'd try that.
Also just tried fastboot boot 11.2.4.4_global_boot.img on this 11.2.4.4 Europe image and still no go. Boots and makes sounds, but black screen still.

Have you tried the MSM tool?

hadesflames said:
Have you tried the MSM tool?
Click to expand...
Click to collapse
I was considering it, but don't want to lose any data. Next step is to contact OnePlus technical support during normal hours and see if they can work with me to resolve this one. I believe I read here on XDA that people have contacted them and usually are able to resolve the issue. Trying to avoid clearing data as the device is fine as it boots, but I think the Europe image is conflicting somewhere and not allowing me into the system since it boots all the way to the lock screen, but I don't see a lock screen, just a blank screen with sounds after boot seemingly working, along with charging sounds (albeit, sounding every 10-20s like its periodically charging).
This is so odd though because I did everything as I should've and update seemingly occurred, but system version still showed 11.2.3.3. So I go back to system update and it said there was an issue and to restart again. Did that two times with magisk revert image and restore to inactive and it then stopped booting.

If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata

djsubterrain said:
If you're able to get to the recovery you can try sideloading the zip file
ADB Sideload name.zip
That should put the rom back to default, I would reboot the phone back into recovery and then do a wipe or go to fastboot and use "fastboot -w" to wipe the userdata
Click to expand...
Click to collapse
Does stock recovery support ADB? At 8 pro you needed modified one..

pyry666 said:
Does stock recovery support ADB? At 8 pro you needed modified one..
Click to expand...
Click to collapse
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).

djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
Click to expand...
Click to collapse
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though

pyry666 said:
I was just corious, not at home right now so i cant test. My drivers are fine and have no issues..I am using linux myself though
Click to expand...
Click to collapse
Yeah I'm working at the moment so not on my own PC, can't really test it out

djsubterrain said:
Yeah I'm working at the moment so not on my own PC, can't really test it out
Click to expand...
Click to collapse
Just tried. ADB with stock recovery is "unauthorized"..So modified is needed if one wants to use stock recovery with adb

djsubterrain said:
As far as I know, it should do as long as the drivers are installed properly, you can check with "ADB Devices", if you see the number returned then the phone is responding.
As for the fastboot commands above, I know there was a post on the OP7P forum that would make fastboot script packs for each build, if you use the script from those, you should able to amend it to flash the images above. Afaik the structure is likely the same anyway. The post also shows "ADB push" commands you can use to flash individual images to the phone.
I might have a look later and see if I can make a similar one although there seems to be a lot more build versions on the OP9P than there were for the OP7P.
Might just be easier to use the Payload Dumper program to unpack the images from the payload.bin file (instructions here) and then use a generic script to flash them to the phone, all the different models should have similar images although I do know there's an additional India.img for the Indian models (which I think is also shown in the global rom).
Click to expand...
Click to collapse
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).

bulletbling said:
I tried flashing all of the 11.2.4.4 Europe full system image payload_dumper extracted images (such as boot.img, system.img, dtbo.img) to the phone and I get where I am now. It goes through boot, but no lock screen, just a non-lit/black screen with sounds that the phone is charging when plugged in and is recognized by the computer (but can't see internal storage since you have to use notification center to turn on usb storage).
Click to expand...
Click to collapse
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.

djsubterrain said:
See if you can do a fastboot -w to wipe the userdata in case it's been left with unusable data.
Click to expand...
Click to collapse
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.

bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
Are there actual hw differences between AA and BA?

bulletbling said:
This is what I'm trying to avoid...
Since it mostly boots on the Euro 11.2.4.4, I feel that the Global full image would resolve this, but OnePlus never updates their darn website with the latest for Global.
Click to expand...
Click to collapse
There's a pinned post at the top of the forum with all the available latest roms. Not sure they've added Global yet tho. Best going there or Oxygen Updater (when the phone is working) than the download page tbh, OnePlus ALWAYS takes ages to add builds there

pyry666 said:
Are there actual hw differences between AA and BA?
Click to expand...
Click to collapse
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.

bulletbling said:
Not that I know of, but I have seen users use the Europe image to update their device on this forum before with the OP9Pro because they either didn't want to wait or needed to fix their device for whatever reason and the Europe version worked fine. So I don't know if this is different on 11.2.4.4.
Click to expand...
Click to collapse
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..

pyry666 said:
I know that BA is coming first than AA. Dont know reason for that but with op8p situation was same. Then was talk about googles servers or something but cant remember what that was exactly because it never affected me..
Click to expand...
Click to collapse
I wish I could go without my phone for weeks until they post the latest firmware to see if that even works, but I can't so I guess I'll have to use the msm tool and wipe all of my internal storage of documents, including taxes, and various files and downloads I've amassed over the past half decade. This really sucks. All because of a simple OTA that should've never caused this. They really should prevent this from being possible with the OTA update tool built-in to their system.

Android 11 Stock ROM for Moto G9 Plus and root with Magisk (Odessa - XT2087-1)

This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!

Gg I'll try it tomorrow

UsmanQ said:
Gg I'll try it tomorrow
Click to expand...
Click to collapse
Great! Tell me about your experience with this rom or if something goes wrong!

Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.

oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.
Click to expand...
Click to collapse
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.

christjeam said:
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.
Click to expand...
Click to collapse
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious

oscararm10 said:
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious
Click to expand...
Click to collapse
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!

christjeam said:
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!
Click to expand...
Click to collapse
Super, I will fit certain apps with the full screen option. Thanks

lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.

Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
You don't want to use the same bat file without checking the flash_file.xml commands can change with updates.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.
(Moto g9 plus Odessa xt2087-2)
Click to expand...
Click to collapse

Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
Wow, that's weird, but I see that you could solve it and that makes me happy, enjoy your Android 11!

christjeam said:
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
Click to expand...
Click to collapse
This link, don't work dude! :-(

ice.modding said:
This link, don't work dude! :-(
Click to expand...
Click to collapse
Use this: https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037

hi, what stock roms and other roms do i download? or do i just download them all?

Godfather096 said:
hi, what stock roms and other roms do i download? or do i just download them all?
Click to expand...
Click to collapse
You only download one, let it be one that aligns with your country and smartphone model

Stock rom links are broken please update

adamtarek said:
Stock rom links are broken please update
Click to expand...
Click to collapse
Links are still active, check your connection!

christjeam said:
This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!
Click to expand...
Click to collapse
I tried to use that method since I found it in a youtube video but when I used the patched boot.img file the system took too long to start and when I finished loading the device the touch didn't work, and it didn't matter if I repeated the command "fastboot flash boot" with the original boot.img file of the rom since it kept starting but at the same time the touch did not work.
(the boot.img file that I use was extracted from the "Rescue and smart assistant" program).

Question Pixel 6 Pro unbrick/recovery

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.