Develop Bugs

[551ml] flashboot FAILD (remote: flash_cmds error!) Im stuck in fastboot

HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.

I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!

Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk

This is not so, I sideloaded MM fine straight on .184
No problem sideloading

kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site

Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.

timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.

timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.

So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[

quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.

sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.

quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery

sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery

sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?

quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.

sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.

Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.

Possibly Bricked Pixel XL

Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.

Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot

parakleet said:
Doesnt looked bricked to me
maybe your factory image is incomplete.
Flash the parts individually see what happens.
Commands i use. note you need to use your own paths or copy mine
) Execute fastboot commands
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot-bootloader
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip <--- if you want to root.
5 Still in twrp flash verifiedboot signer.zip
6 Reboot
Click to expand...
Click to collapse
No offence but i am lost by what you said, I am trying to get back to completely stock. Is part of my issue the fact that command prompt didn't detect my device? or no?
I'm not exactly sure what to do with the information you shared, sorry
I the tutorial i found it says to make sure the command prompt sees your device but doesnt say what to do when it doesnt see it.
Also, I downloaded the may factory image, i believe it was version O

Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble

jreink01 said:
Am I suppose to use the O image or the L image (verizon). I am on tmobile. I used the O image when i ran into trouble
Click to expand...
Click to collapse
If you did not get your phone from Verizon use this
7.1.2 (N2G47O, May 2017)
Download the zip
unpack all the zip files some are nested so unzipping one creates more keep unzipping until there are no more then gather the following img files
bootloader.img
radio.img
boot.img
system.img
system_other.img
vendor.img
modem.img
Some of those names are cut down as i hate typing long strings, jsut rename them as such.
Create a folder on root of c:\_PIXEL_XL_
put all the files there.
You will use way less files than you unpacked
once you have done that run the following commands
copy and paste
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
After last reboot just wait and you will be back at stock
if that doesnt work
Download latest version of TWRP place it in C:\_PIXEL_XL_
rename it twrp.img, again i hate typing long strings
from bootloader run
fastboot boot c:\_PIXEL_XL_\twrp.img
This will take you into twrp
you might need to wipe system and cache and data,
From memory the fourth entry at bottom is internal memory or user data, in any event if you do not check that your data stays on the phone.
Once you have wiped the other 3 rerun the fastboot commands and you will be back at stock
add the twrp and supersu commands from earlier to add root.
dont forget the signatureverify.img if you are doing that.
good luck.
you arent bricked
you just need to find the correct combination of steps to get your phone where you want it to be

Thanks for the response. I am having a hard time with this, the zip file i downloaded from the google website, when i open it, there are only 6 files, 1 of which is a zip file (marlin). When I open marlin it shows a bunch of files, none of which you mentioned. I am confused, was wondering if you would be nice enough to walk me through this over the phone, i would be really grateful.

Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!

jreink01 said:
Is there anyone that can walk me through this this on the phone, the more i try to understand this, the more cofused i get. pLeASE!!!!
Click to expand...
Click to collapse
Yes, i sent you a PM.

HALV0RS3N said:
Yes, i sent you a PM.
Click to expand...
Click to collapse
thanks, sent you my #

Okay so I had the exact problem yesterday. To to the Google developers site and download the official Google pixel or xl 7.1.2 nougut ota update. Once that's downloaded, go to your phone, I had all the exact same screens on my phone so it should work. Hold down the power button until it completely shuts down. Then hold the power and volume down to go to recovery mode, if it goes back to the ext 4 screen, try it again until it goes to recovery mode, then on command prompt type, fastboot boot twrp.img then once it's in twrp, go to advanced-then adb sideload and click both boxed and then swipe to enter sideload. Then on your computer, type adb sideload "file name for Google update" and hit enter. That should do the trick. Like I said, I had the exact same problem yesterday
---------- Post added at 06:56 PM ---------- Previous post was at 06:50 PM ----------
Also, I forgot to mention, download the twrp image file from the Internet. Shouldn't be hard to find just make sure it's the latest. Put that file in the adb file on your computer same with the Google update for your phone. Do not unzip either file. That's very important. DO NOT UNZIP THE UPDATE File. When you type in the twrp.img make sure you type img. And when you flash the update, make sure at the end of the file name you put
.zip ex( marlinpixelxl7.1.2.zip)

jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
Looking at your screen shot you didn't let the file finish flashing. It sticks at the "does not contain" for a bit before it continues.
You were doing it right. You just didn't wait.
If it wasn't going to work it would eventually give you a failure and jump to the command prompt.

jreink01 said:
Hi, I am i dire straits. I have a pixel xl running pure nexus, rooted and on tmobile. I am trying to get back to completely stock. i tried followig the instructions but somewhere I messed up. Currently phone will just bootloop. I went into cmd, typed adb devices, nothing came up so stupid me, I continued anyways with flash-all.bat, something went wrong in command prompt, then i proceeded to reboot from fastboot, this is where i am now. I have attached pictures of the command prompt screens and of the folder in adb fastboot on my pc that I think contained all the files. I do't know where I went wrong. If you can help, it would be greatly appreciated. I can only correspond via pc. Please, I hope someone can help me.
If someone has the time to walk me through step by step, it would much appreciated.
Click to expand...
Click to collapse
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.

RedBlueGreen said:
i had the same issue and this worked
https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3
dont follow it word for word as that its not the XL version in the post.
Click to expand...
Click to collapse
OP was flashing to stock. Didn't let it finish though.

GSIs that work on the E6

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

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.