Develop Bugs

Unlocked Google Pixel XL BOOTLOOP. Redid the latest factory image. Still nothing.

So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.

Leo226 said:
So my google pixel has been boot looping the past couple days now.
I've read that many others have had this issue, but none of that has helped. First I tired factory resetting it using the recovery mod, then I reloaded the latest factory image using my computer.
Honestly I don't know what else to try.
The cycle is usually as followers. Warning screen - logo screen - repeat.
After a few times i got the EX4 file screen but then it just repeats some more.
It is unlocked but that's it, never got around to doing anything else with it.
If anyone can help me it'd be greatly appreciated, really don't wanna have to buy a new phone ya know.
Click to expand...
Click to collapse
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.

Homeboy76 said:
Go here:
[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2018 Security Patch
Do #4 then #8.
Click to expand...
Click to collapse
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.

Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
Well first your bootloader is definitely unlocked correct? I assume it is because you did say you saw the warning screen but I like to err on the side of caution. Second, you're saying that when you plug the phone into the PC that it is recognized and you are able to run commands via fastboot right? If you can run commands, but certain commands aren't working properly, I would say that it is your version of the platform tools and that you need to make sure you have the latest version. Platform tools is the folder that usually houses ADB and fastboot along with the other files necessary. These are updated occasionally and I know for a fact that outdated versions do cause issues sometimes. The next step if you can run commands would be to try a different USB port on the PC. Some ports are different when comparing the back and front and top ports. If none of that seems to do anything I would say lastly to try a different USB to USB C plug. I'm only listing all of these things because I've had to go through all of these issues myself at one point or another, but I do hope it's something simple.
I didn't mention this but obviously the files that you're flashing with fast boot have to be in the same folder as fastboot, I don't know your level of knowledge and expertise so I don't mean to sound condescending I just wanted to make sure I added that.

Leo226 said:
For #4, Flash all command doesn't work. But I can manually run the batch file, That's how I've tried doing doing it before.
The one I've been using is "marlin-ppr1.180610.010-factory-3b90270c.zip" I assumed it was the most recent one although "marlin-ppr1.180610.009-factory-90a4fa8b.zip." seems like it is just as recent.
Am I supposed to use some how both?
For #8 Simply doesn't work, just says Error: Cannot load 'twrp.img'.
Any actual detailed guides on this stuff? Because honestly it's just a confusing mess, seems like I'm doing it right. But clearly I'm not.
Click to expand...
Click to collapse
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide

Homeboy76 said:
@Leo226;77325519
Verify bootloader unlocked: Turn phone off > Press Power and Volume Down keys (At the same time) until phone vibrates and you see 'Start'
The bottom line should read: ' device is Unlocked'
You missed a step.
Start over and take your time.
Use this factory image: marlin-ppr1.180610.009-factory-3b90270c.zip
Unless your Carrier/provider is Telus then use this one: marlin-ppr1.180610.010-factory-3b90270c.zip (Telus)
Do #4 - Install Factory Image 'keep' data
4C. Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Then do #8.
The #8 error is because you either didn't copy the twrp file to the directory/folder with fastboot in it or you typed the command incorrect.
This is a detailed Guide
Click to expand...
Click to collapse
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?

Check the properties of twrp.img and make sure it is named correctly.
Sent from my Pixel XL using Tapatalk

Leo226 said:
Sigh well everything is up to date most recent. Switched usb drives to see if it makes a difference.
Was not aware I needed to use the "09" factory image, been trying the "10".
So just flashed that, still in bootloop obviously, don't know if installing twrp would even do anything because as I said the command won't work..
It just says "cannot load 'twrp.img' . No such file exist"
The file is there, right in the platform tools folder with fastboot, adb and everything else. So not sure why it's acting like it's not.
Are their other files I need for it?
Click to expand...
Click to collapse
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.

Homeboy76 said:
So, I'm going to 'assume' after updating everything and extracting the factory image to the folder with fastboot in it. You were able to use the flash-all.bat command. Yes?
Open Windows Explorer and make sure it is set to show the extension. The default is to not show the extension. Then look in the folder with the twrp file you renamed twrp.img. Does it look like this, twrp.img.img? If yes remove the last .img.
"Are their other files I need for it?" No.
Click to expand...
Click to collapse
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.

Leo226 said:
Correct, was able to flash by double clicking the batch file.
As for the twrp, yes already had made sure that the name was correct since I have had that issue with other things before.
"fastboot boot twrp.img" still does not work. I have even tried redownloading everything, placing them in it's own folder together, on and on. Nothing.
At this point I'm not even sure if installing twrp will even do anything though.
For my boot loop problem I thought just flashing the latest factory image would fix it. Clearly I was wrong.
Click to expand...
Click to collapse
hi leo,
Have you fixed the bootloop issue yet? If yes, how?
My Pixel XL is now having same bootloop issue as yours, but my phone takes all fastboot cmds, and it just keep bootlooping.
If you just get trouble to touch the file twrp.img, I have some tips for you here:
1. I read that you are using Windows environment, so first right click the file "twrp.img", and make sure at bottom of the pop-up proprieties window, the file is not "locked", if you see it's locked, you can check the unlock box to unlock it. This is usually happen to downloaded files put in windows system partition;
2. I read that you double-click the flash-all.bat file to executive the command, please right-click on the file, and select "Run as Administrator", this way will make sure windows security policy won't prevent you from running all the cmds you intended.
3. If above 2 items you checked and not solve the twrp.img access issue, just try to download a new copy from internet again, and put in another partition folder, and repeat the above two steps. Or even try another PC/Mac.
Thanks,
Lei

GUIDE: How to unbrick your Zenfone 6 (ZS630KL)

Hello.
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Note: Unlocked bootloader is not required to do any of the actions described in this guide.
Disclaimer: I'm in no way responsible for the actions you perform and whatever happens to your device due to these actions. Proceed at your own risk.
Prerequisites:
Service firmware. Can be downloaded here. It's an older build, but it will do the trick and it's the only one I could find freely available at the time of writing. Only for WW SKU
Zip for your desired build. Can be found here.
- Note: For this guide, my desired build will be WW-17.1810.1910.63, which is a special case, as you will need to flash in the following order: Service Firmware -> WW-16.1220.1909.194 -> WW-17.1810.1910.63. In other cases, unless noted otherwise in a description of the build on the ASUS website, Service Firmware -> Desired build will suffice.
Platform tools of Android SDK. Latest package can be downloaded from: Windows | Linux. Somewhat optional but good to have.
Step 1 - Preparing the environment
This is not required but for the sake of simplicity and keeping everything in one place, create a folder and name it whatever you like, for example ASUS or Unbrick
Create a sub-folder inside the folder you've created in the previous step, call it service_firmware, download and unzip service firmware into this folder
Download files for the desired builds from the above link. For this specific case, WW-16.1220.1909.194 and WW-17.1810.1910.63.
3.a If you have microSD card, transfer zip file for the desired build into its root and insert the card into the phone.
3.b. If you do not have a microSD card, download and unzip platform tools mentioned in the prerequisites as you will need adb to flash firmware/s via sideload
Step 2 - Flashing service firmware
Connect your phone via USB
Enter fastboot mode via one of the methods:
1.1. Turn off your device, then turn it on while holding down the power and volume up buttons at the same time. Release the power button when it powers up (keep holding the volume up button)
1.2. If you have platform tools, you can do adb reboot fastboot
Open CMD (windows) | Terminal (unix)
CD into the folder with service firmware from item #2 from the step above.
Make sure your phone is detected by typing fastboot devices
Ensure battery is at least 20% charged. Aside from normal means, it's possible to check the battery charge via fastboot oem get-batcap.
Sample output: (bootloader) bat cap = 35, which means that the battery is 35% charged.
IMPORTANT NOTE BEFORE CONTINUING:
By default, flashing with one of the scripts wipes your userdata, in other words, it performs a factory reset.
It is possible to avoid userdata wipe (although not encouraged) but keep in mind, unless you flash your current build after flashing service firmware, your phone will not boot up.
If you absolutely would like to preserve your userdata, even if for the sake of backing it up before doing a factory reset, you have to edit the flashall script in the following way:
Windows: Open flashall.cmd in your favorite text editor, go to line #298 and change it from fastboot -w to REM fastboot -wand save the changes.
Unix: Open flashall.sh in your favorite text editor, go to line #275 and change it from $fastbootcmd -w to #$fastbootcmd -w and save the changes.
Once again, this is not encouraged as it can potentially cause issues later on. You've been warned.
Run the script
1. 1. Windows: In the CMD you opened earlier, type flashall.cmd
1. 2. Unix: In the Terminal you opened earlier, type ./flashall.sh
Note: An obvious note, do not disconnect your device from your PC while flashall script is running. Your device will reboot a few times during the execution.
Once script outputs format logdump... and the phone reboots, service firmware will be flashed.
Step 3 - Upgrade to your desired build
Enter Recovery mode via one of the following methods:
1.1. If your phone is turned on and USB debugging is enabled, use command adb reboot recovery
1.2. While in fastboot mode, navigate to Recovery Mode using Volume Up/Down buttons and select with a single press of a Power button
1.3. While in fastboot mode, issue one of the following commands : fastboot reboot recovery or fastboot oem reboot-recovery
Once in Recovery Mode, you have 2 ways to proceed:
A: Update from SD card
A.1. Select Apply update from SD card option
A.2. Navigate your SD card and select UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip
A.3. Confirm your choice with a single press of the Power button
A.4. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
A.5. Select Apply update from SD card option again
A.6. Navigate your SD card and select UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip
A.7. Confirm your choice with a single press of the Power button
A.8. Once you're back to the menu of Recovery Mode, select Reboot system now
B: Update through ADB Sideload
B.1. Select Apply update from ADB option
B.2. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip"
B.3. Once you're back to the menu of Recovery Mode, reboot by selecting Reboot system now and enter Recovery Mode once again via any of the above methods
B.4. Select Apply update from ADB again
B.5. In your CMD/ Terminal, issue command adb sideload "UL-ASUS_I01WD-ASUS-17.1810.1910.63-1.1.1-user.zip"
B.6. Once you're back to the menu of Recovery Mode, select Reboot system now
Note: Like I've mentioned earlier, these steps are specifically for build WW-17.1810.1910.63. If your target build does not require another build for an update, you can skip steps A.4 to A.7 or B3 to B5
That's pretty much it. If you followed the steps above correctly, you should once again have a running phone with your desired build of firmware.
If you have any questions, do not hesitate to ask.
Cheers.

Hello i've a question (sorry for my bad English). This morning my phone was bricked (red message logo), and with this tuto i remove this logo and i found my original recovery.
But when i want to install firmware from recovery with SDcard option, i've a message no SDcard found and impossible to install firmware. (even after several tries)...
If i reboot my phone i have android logo bootloop...
Can you help me???
https://drive.google.com/file/d/1GStfEgZFpb66JRaAmjeYOKmyn9d8WcPz/view?usp=sharing
https://drive.google.com/file/d/1FSRZfI1vNAyDQDZaLDGrHyiC-lImsYhr/view?usp=sharing
Thank you and Happy New Year...

Thanks for the link to that service firmware!

_Kuroi_ said:
This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like.
Cheers.
Click to expand...
Click to collapse
Thanks a lot mate, you made my day!
Please, one question: can you tell me, if both slots (A & B) are flashed by this method?

Thanks!
Thank you so much!
I've wanted to go back to stock for so long, but I haven't been able to find a stock ROM. I've even contacted ASUS support and they couldn't even get it! Thank you so much for the download and for the guide, you've made my week. I'll be smiling every time I use my phone thanks to you!

Great guide. I have a soft bricked device after flashing Lineage 16.0 recovery. Have a boot loop and can't get to recovery. I realise the mistake was flashing the recovery as should have just booted it.
Has anyone else had success with this on a Zenfone 6?

For those who need it; managed to resolve by downloading the stock firmware from Asus, extracting the boot.img and flashing it. Back working.
Didn't try the guide but this is quicker in this scenario if you have flashed a custom recovery to the boot partition. There is no separate recovery partition so this soft bricked the device, overwriting boot with recovery (I followed the guide here for LineageOS which is ill advised) . Should be booting the recovery rather than flashing, or booting into stock recovery and using the installer zip for your custom recovery.
Steps to recover:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.

Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.

This worked for me, but I'm still in CSC FastBoot Mode and when Android boots, I'm asked to insert a previous pin, which nothing works. Any advice?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
hey, did you manage to fix this? i'm having the exact same problem

sapientsaxonsaboo said:
1. Download stock firmware from Asus - make sure you use the same firmware version installed on the device or you may find it will boot but some hardware such as WiFi or others may not work.
2. Extract the archive and then you need to extract the boot.img from payload.bin - see this article and use the payload dumper
3. Flash your boot.img with fastboot flash boot boot.img
4. Reboot
Device should restart and boot up. Now to see why TWRP and LineageOS custom recoveries won't boot.
Click to expand...
Click to collapse
I tried to install latest firmware from
https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_BIOS/
everything goes fine but it shows till this moment:
fastboot flash boot_b boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.295s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed for non-official image')
any suggestions ?

kenturky said:
Hi, I followed your tutorial down to the letter, but when trying to install the ROM from stock recovery, I'm getting this error
"Eackage is for product ASUS_I01WD but expected WW_I01WD
Installation aborted"
Any fix? I'm trying to flash the latest Android 10 rom, but no luck.
Click to expand...
Click to collapse
Taylor Moon said:
hey, did you manage to fix this? i'm having the exact same problem
Click to expand...
Click to collapse
Try flashing latest image of Android 9 and then flash Android 10

Can somebody please help me with my problem?
So I was able to get my hands on a new 8gb/512gb matte black version of this. Was setting up the phone, updated to Android 10 first before transfering sms, call logs and updating apps. Went to turn off the phone to insert my SIM card and now the phone won't turn on. It vibrates every time I press the power button but then nothing. Currently it's connected to the supplied charger with the LED light lit red. It was already charging while I was using it, had about 70% battery before I switched it off. I've tried volume down + power button for 10 seconds, LED light turns off and it vibrates, and it keeps vibrating every 10 seconds when it's connected to the charger (doesn't keep vibrating when it's not connected). Can feel the area between the fingerprint reader and camera pretty hot during this. Volume up + power doesn't work either. Any ideas?
Click to expand...
Click to collapse
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.

CVonV said:
Can somebody please help me with my problem?
Also, the phone gets detected when I connect it to my laptop but I can't do an "adb reboot" or "adb reboot fastboot" as it says the "error: device is not found."
I left it on charge overnight and the LED changed from red to green too.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
When you connect it to your laptop, go to device manager and check what it is detected as.

_Kuroi_ said:
When you connect it to your laptop, go to device manager and check what it is detected as.
Click to expand...
Click to collapse
I can't seem to find any listing that would correspond to the phone under the Ports section :/

CVonV said:
I can't seem to find any listing that would correspond to the phone under the Ports section :/
Click to expand...
Click to collapse
Maybe upload a screenshot of the devices listing?

_Kuroi_ said:
Maybe upload a screenshot of the devices listing?
Click to expand...
Click to collapse
I thought it would've been listed in the Ports section but it's right at the top under "Android Device" as "Android ADB Interface". I believe I have the correct Qualcomm drivers installed.
Attached screenie also shows device not found when I try an "adb reboot" in command prompt.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hmm, I half expected it to be listed as QDLoader 9008, but then it would be under serial ports.
Try fastboot commands instead of adb and also try holding power + vol down for 10-15 seconds

Great guide @_Kuroi_ , I will be trying it out soon. The service rom you are using is pretty old. So I grabbed the last P update service firmware (WW-16.1220.1909.194) and the latest Q build I could get currently (WW-17.1810.2002.133). I have a subscription to one of the paid firmware sites for reasons like this. This way people have more options and it will simplify most people's updating because they can go from the new P service rom to any Q ota. Q firmware doesn't really make sense until it's not being updated anymore but it's here just in case someone finds it useful. If there is some incompatibility in the future or something that requires a newer update I will grab it then. If there isn't I will grab the last firmware once Q is stopped being updated.
WW-16.1220.1909.194
Here
WW-17.1810.2002.133
Here
WW-17.1810.2009.176
Here
Feel free to update your guide to incorporate these all I ask is a credit in the OP for providing it.

After running ./flashall.sh I get the following output:
Done.
target reported max download size of 805306368 bytes
File system type is raw !!!
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'userdata'...
OKAY ( 0.266s)
Sending 'userdata' (1888 KB)...
OKAY ( 0.067s)
Writing 'userdata'...
OKAY ( 0.003s)
Erasing 'metadata'...
OKAY ( 0.027s)
Finished. Total time: 0.799s
Rebooting...
(I changed square brackets to round brackets in the output because otherwise it wouldnt let me post this comment because of bbcode)
I don't seem to have a recovery partition by the end of it and "adb devices" doesn't show me anything.
Does anyone know what might have gone wrong?

Anybody is pro/has much experience with Fastboot/Mi Flash Tool/Stock Recovery?

.

Sorry to bother everybody...
I just wanna know that can we flash non carrier firmware into a verizon moto z3 (xt 1929-17) as it can not be getting its boatloader unlocked?? Please help... M new here at xda ....

How is your phone now? Is it still stucked on lockscreen lockout? Is it still containing the exact version of miui? My guess is yes but I need a confirmation.
You can't access adb from lockscreen for an obvious purposes, not even MTP.
And what is the error says?

@Osmanism.91 please ask in that particular forum before you ask it elsewhere

.

You may try from recovery flash via mi flash pro. It will need a miui account and internet connection
Second approach is by erasing every lines up to something that says "fastboot erase boot". Keep those line downwards.

.

rodagola said:
you mean delete everything but "fastboot erase boot"? probably not going to do anything because that line also shown me an error before.
Click to expand...
Click to collapse
Not everything, just every checks. It will goes like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Figure 1 : Lines to be removed​
If you specify every error messages you've encountered, it will help everyone.
rodagola said:
I loaded up mi flash pro before and hit the recovery button to go to that interface but the actual recovery interface within miflashpro didn't popup, do you recommend a specific miflashpro version and specific drivers? or is it because I haven't logged into a mi account yet? can it be a brand new mi account?
Also if I actually have the chance to download a recovery rom then go into this recovery miflashpro menu...I'm scared miflashpro might delete the personal data partition, at least on regular MiFlash there's a checkbox with "save user data"
Click to expand...
Click to collapse
You need to boot to recovery, of course. You're in vanilla, so I bet you still have the miui recovery. No need to be specific about miflash pro version, any version will do. It will work like an upgrade. It will require same level or more recent firmware. You can't revert your firmware this way: the server will refuse. I don't know about the account requirements, but it will be better to log in to your account there.
Figure 2 : MiFlashPro > Recovery Flash interface. My flash is rejected. IDK why. It's been rejected when I tried to upgrade from 12.0.6 to 12.5.1. Used first method to upgrade instead.​There is that "Wipe user data" button, pretty self-explanatory.

.

rodagola said:
oh alright, recovery method could work as long as I dont click wipe data, however, how do I get to that screen you screenshoted? Since a Mi Account is a must, if I make an account today, you think will that let me work with that?
Click to expand...
Click to collapse
Boot to recovery, select "Connect to PC Suite", the 3rd option, control selection with volume rocker and select with power button. Depending on how is your device is connected, it will automatically detects the corresponding flash method. In this case, there will be this "Flash in recovery" button in the main interface. Just click that and select your ROM directory.
I don't know about account details, since I always use my account that have permission to get a device unlocked

rodagola said:
Hi all, I've had this issue for a while.
I have a RN8P Chinese running MIUI11.0.3 stable over Android9, however, I wanted to start customizing my experience but didn't mean to go 'too far'.. the issue is:
> I've never unlocked the bootloader on it, therefore no custom recovery available on it. But didn't mean to change this and wanted to keep stock ROM
> However, within my stock ROM, I wanted to have it as clean as possible from bloatware, so I went ahead and plugged the phone to my PC, installed adb, and started running commands with adb shell pm uninstall... I managed to uninstall quite a few useless apps but also thought uninstalling a system app called something like "yman" and another like "xman" was a good idea, oh boy it wasn't a good idea...
> Now the phone has some sort of soft brick. When it reboots and goes to the lock screen (I had it with swipe), I try to swipe up but the phone doesn't respond, and I think the yman and xman apps were responsible for this function, but are now uninstalled)
> I need a way to get my phone working normally. When going back to adb to reinstall these via commands, I get "unauthorized" when checking the phone status with 'adb devices', so no commands are accepted. I also went into the stock recovery mode and tried to run commands but it now shows "sideload" and will give error for every command, so I discarded this option
> Maybe I can run these commands through the fastboot menu somehow? However I don't know how (if even possible)
> If there's absolute no way to get this RN8P to receive the command to reinstall the same package that caused the trouble, then I think I could try flashing...
> I went and downloaded MiFlash, downloaded the corresponding same exact stable ROM on same region for fastboot, plugged my phone and checked SAVE USER DATA on the botton, in order to have the data partition intact, but MiFlash throws some errors. I read somewhere just click on the desired batch file while the phone is still plugged in and it might bypass MiFlash errors, but it didn't, then I tried redownloading drivers and from 3 different PCs, looked up why MiFlash was failing and found out perhaps deleting a few lines from the batch would fix it, but I kept getting further errors related to the next line and the errors were endless.
> Still with the flashing idea on MiFlash, I downloaded the other further Chinese fastboot ROMs, as in upgraded versions to Android10 and MIUI12 (instead of the exact versions the phone still had). But now I get same thing as before, endless errors keep coming up and the flash process won't go through.
> I really want to retain my personal data, so I was suggested to try MiFlashTool v2, however, I've heard that one has no option to save the data partition, so I haven't bothered yet, and before I move on to try, could anybody with experience tell me their experience?
> In general, would there be a way still for me to fix the phone without losing user data? Maybe there's hopes the phone can receive adb commands somehow still? I'm confident I can revive the phone very quick through adb, if only it still wanted to be adb friendly...
Thanks to any pros that might be out there and would save a junior
Click to expand...
Click to collapse
You said you have a RN8Pro Chinese.
Can you give us the full MIUI ROM filename that you're attempting to flash? We have to be sure you're flashing the correct ROM.
Also check if the MIUI ROM you downloaded isn't corrupted.
Compass.

.

rodagola said:
I downloaded "begonia_images_V11.0.3.0.QGGCNXM_20200518.0000.00_10.0_cn" which is supposed to be rn8p chinese fastboot miui11.0.3 a10. And from 2 different sources to try to make sure it wasn't corrupted. I don't know any actual way to check if the ROM is corrupted or not...
Before the soft brick, the phone had this exact same version but for a9 instead of a10. So I guess this is some sort of upgrade.
I'm now going to try downloading same thing but for the recovery version within miflashpro, just like what kekesed97 said
This could have a different output, so I'll update here
If this doesn't go successful, then I guess next step is trying SP flash tool? though I have no clue how to use that one
Click to expand...
Click to collapse
You downloaded a very old MIUI but it should work. Check the link below for a newer release. The latest fastboot for MIUI 12.0.x China is V12.0.5.0.QGGCNXM (if I didn't skip a version; the list is quite big). There's also MIUI 12.5.x China if you want the latest stable (MIUI 12.5.x Global is buggy so I'd skip MIUI 12.5.x for now).
https://xiaomifirmwareupdater.com/archive/miui/begonia/
Here is a YouTube playlist that might help you: https://www.youtube.com/playlist?list=PLLy0_Q3fJ1DLjE5Cx7uCD3yTxeTaUbiIo
Be careful when you flash so that you keep your data. If I remember well that author usually wipes data in his videos.
I don't know which package manager people with Windows are using these days, but I guess WinRar is a popular choice. WinRar should have a "test file" so you could try that to check for a corrupted download.
I can't help you with the flashing process on Windows since I don't use it. kekesed97 instructions or the YouTube playlist should work (I think the YouTube author uses different software for flashing, just so you know).
Compass.

.

rodagola said:
Hi again, I'm in MiFlashPro recovery section, and have downloaded the corresponding recovery ROM, it downloaded as zip. Now should I just browse and select it as is, or do I need to uncompress and select something else? My guess is select as is but would like to confirm. Thanks a lot for your tips so far dude.
Click to expand...
Click to collapse
No unzipping. Use it as is as it will be sent over your phone and flashing is done recovery side (put it simply, it's an ADB sideload, with restrictions)
rodagola said:
Moreover, there's an option to download an incremental zip (just the ota extra files instead of full zip) would you recommend that over full zip? would that fix the brick? My guess is not because it doesn't have all the apks on it, whereas the full one has all the apks so it can reinstall the uninstalled app that caused my brick, and probably the OTA version can't, but I'm NOT sure...
Click to expand...
Click to collapse
It only accepts recovery ROMs (2 gb ones). You are only allowed to flash greater version of your current firmware from the same ROM distribution. It's works like updating your phone when incremental update fails after all.
rodagola said:
Also, to add more detail, I was looking arond and found that MiFlash Tool could not be so friendly with phones running on Mediatek so it's more for Qualcomms... instead, SP flash tool is more meant for MediaTeks (so that makes me believe that's why my RN8P was having all sorts of errors with that "MiFlashTool"). Anyway, I'll stay away from SP flash tool aswell because I read it always wipes everything. So my only real chance now seems to be the Recovery method on MiFlashPro, but I'd love if you confirmed my inquiry mentioned above
Click to expand...
Click to collapse
Not quite correct. There are 3 different flashing methods there. Recovery mode, fastboot mode, and deep flash mode.
In recovery mode, flash is using ADB sideload-like mechanics (or it is? I have no evidence, but it works similiarly that way), while in the Mi Flash program is using fastboot method. Both methods are platform-independent, which means it will work in both MTK or SD chipsets, as long as the phone permits. As for deep flash one, it will require lower level access to hardwares, and only manufacturers are having such access. Thus, flashing method diverges. MTK is using SP Flash tools, in which the mechanics behind that can be red in the CFW Megathread (CFW is quite irrelevant today, but the boot process explanation is something else that will never went irrelevant, unless another boot sequence is introduced), as for SD chipsets will use QPST over Sahara Protocol (more info on this: just dig how to ressurect xiaomi redmi note 5 pro edl 9008 that have their arb lock triggered).
It isn't that it will wipe your phone clean that to be your concern. That can be avoided by selecting "Download Only". But that there is this method requires a special account that only service centres have (but a bypass method is known recently, just dig deeper). Consider this as your last resort. Oh yes, it will need a fastboot rom, and the scatter file is available in the ROM directory.

.

rodagola said:
Hi again, I'm now in recovery mode in MiFlashPro and have attempted browsing the files I downloaded from https://xiaomifirmwareupdater.com
The files I choose were recovery roms with "stable branch" ( I don't know if weekly branch would work better?). Well, I loaded the stable ones into the menu and xiaomi servers authenticated and checked the rom... but then it throws "Sorry, flash to this stable version is not allowed" error.
What is this... I first tried with my downloaded zip package "miui_BEGONIA_V11.0.3.0.QGGCNXM_b656ebe642_10.0"
which is 1 step forward from the version I had (I had v11.0.3 with A9 but this package should update me to A10)
got the error... then tried with a little further update with another zip I downloaded "miui_BEGONIA_V12.0.2.0.QGGCNXM_972f66522c_10.0"
Same error again after xiaomi servers check it out.
There only seems to be a few more stable ROM versions for my chinese variant AFTER these. Those are: "V12.0.3.0.QGGCNXM", "V12.0.4.0.QGGCNXM", "V12.0.5.0.QGGCNXM" and "V12.5.1.0.RGGCNXM".
Before I try with these next 4 versions, from older to newer, I'd like to ask if should I rather try with BETA versions instead of stables... (since the error I was getting says: "Sorry, flash to this stable version is not allowed")
Anyways, I have read somewhere that with an authorized account it would let me install betas and stuff no problem, however those 2 that I tried to install weren't even betas. So I'm confused.
Thanks a lot again for your help dude
Click to expand...
Click to collapse
Don't do that.
Weekly is beta and doesn't mean it's better. It's supposed to be a test version and bug hunting release to device enthusiast so xiaomi can go fix it and accumulate the bug fixes to be included in the next stable version. Weekly is always newer so moving from beta to stable is considered downgrade, which require a data wipe. Btw, is your current firmware is from stable branch?
Or perhaps is it because your account doesn't hold a permission to flash since it's never been granted bootloader unlock permission? Idk about the account part.
Well, now try to use fastboot method if recovery update method fails. Mi Flash Pro have it so you don't have to download another tool. It allows broader range of firmware version, particularly for this phone.
Download a recovery rom and unzip it. Load it to mi flash, boot your phone to fastboot, and flash it there.
Figure 3: Mi Flash main interface. Choose this option to retain data​Or modify a flash batch file as I instructed in previous post and run it through command prompt.
I never flashed anything in a locked bootloader because I always unlock my phone the moment I grab it. But one thing for sure is you are bound to the same ROM region. Never flash any other ROM from another region distribution. You have been warned.

.

.

rodagola said:
Also, reading other threads, I should quote this guy called "zqm" on xda forums. From this post: https://forum.xda-developers.com/t/is-mi-unlock-really-needed-to-unlock-bootloader.4024519/
I quote his input: "This shouldn't be a concern for now. Xiaomi isn't planning to restrict unlocking the bootloader. Another thing you should consider is that Redmi note 8 pro gets easily bricked by flashing custom twrp, magisk, etc. but it's not easily recovered as it requires xiaomi authorised account."
So he's implying you need an auth account for recovery ROMs, (I think)......
I'm reposting this for you because you said you didn't know about the account requirements, maybe this brings forward a theory. However I insist I might need to borrow an authorized account now but don't know where or how
Click to expand...
Click to collapse
No, that one thing is different. What @zaqm talking about is the one to access the low level parts of hardware i.e. deep flash via SPFT, which only the manufacturers have, perhaps xiaomi engineering team and service center team to name a few. Adb sideload and fastboot is user accessible, so it doesn't need such permission, with limited access to emmc partitions (afaik no raw readback is one of its limitation). And fastboot doesn't enforce any account security measure, so does the adb sideload. That thing is implemented via mi recovery and mi flash pro. It will send an sha check to one of xiaomi server, returning if the phone is ok to be flashed. After the check returned true, it will begin to send the zip file to phone. This procedure is non-skippable. Therefore, you can only send firmwares this way. This is not happening in custom recovery, so you can send any command. But unfortunately you have vanilla.
After a quick inspection, that is indeed ADB sideload.
It refuse adb sideload command on redmi note 5 pro with vanilla recovery, unlocked bootloader (see attachment). After the command is issued, the phone immidiately restart and boot to system. It's likely won't hurt, so I think it worth the shot.
Try this :
1. Connect your phone to phone thru pc suite mode in recovery
2. Download minimal adb and fastboot or adb platform tools. Extract it.
3. Check your device by executing this in command prompt:
Code:
adb devices
4. If your device is connected, command prompt will return this:
Code:
D:\begonia\Minimal ADB and Fastboot>adb devices
List of devices attached
3d9ac49b sideload
5. Rename your firmware to something easy (something like update.zip but I don't care) and copy it to the same directory as the adb directory
6. Execute sideload command
Apache config:
adb sideload update.zip
7. See if wonder happens
8. ...
9. Profit?!
Anyway write back if this you succeed or not.

Question Unable to enter system after reboot

I am using 6 pro and got a huge problem.
My P6 pro is in fresh status and proceed a new setup with a new Google a/c. No matter in safe mode or normal mode, it always get into recovery mode - "can't load android system". Below picture is the log I capture from recovery mode. Could anybody help me? Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair

We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?

Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)

I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).

Morgrain said:
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Click to expand...
Click to collapse
I did not root or install magdisk to the phone. I just openbox, turnon the phone, everything starts normal, do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot

ecuchi said:
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
I did not root my device. Everything starts normal and i do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once the phone reboots, it goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot

Alekos said:
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Click to expand...
Click to collapse
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot

RetroTech07 said:
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
Click to expand...
Click to collapse
No, I did not do any modification. I also try the pixel repair but no use.

jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
I have seen this Scenario hours ago when I try to disable vbmeta to get the corrupted message appearing after booting.
Because I disabled vbmeta flags, wiping is necessary, therefore I choose factory data reset. issue fixed, data lost. that's all

jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.

Alekos said:
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Click to expand...
Click to collapse
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?

jozifkwan said:
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
Click to expand...
Click to collapse
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.

Alekos said:
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Click to expand...
Click to collapse
Thank you, I tried your guideline to flash, tick "wipe" and "flash all partitions", flash slot A first and then flash slot B.
The problem is still the same, once I finished the setup, reboot, goes into recovery again and said "cannot load android system"

Beginning to sound like you should exchange it for a new one, unfortunately.

Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices

Sounds like a hardware issue with the NAND.

LLStarks said:
Sounds like a hardware issue with the NAND.
Click to expand...
Click to collapse
I believe it is not the NAMD.
Last night, I test the battery to see if the corruption issue is caused by unstable voltage or ampere. I run drain app + 3D mark, my phone of course heats up but no reboot or unstable issue.
The battery test drained 60% of battery and i manually reboot the phone, no problems or errors and enter system. Then I left the phone in stanby mode for 7 hours. The battery downs to 35% and I reboot the phone again but this time unfortunately goes into recovery issue again.
This is very weired and I couldn't figure out what kind of problem is that.

stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
I am wondering if anyway to skip the recovery or corrupt checking.

stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
you have the corrupt message also? Can you try what I recommended above, updating all 4 Play Services/Play Store Apps/Security Update and Play System Update with Bluetooth disabled?
If not use the Android Flash Tool and wipe the device and flash all slots, let us know if that works.

How To Guide Asus ROG Phone 6 / 6 Pro [ROOT GUIDE/SUP]

Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)

leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?

fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.

leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.

Isn't Android Auto no more (i.e discontinued).....?

elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)

fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly

finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )

Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?

fastboot driver doesnt support win64

Will the phone do a factory reset after unlocking the bootloader?

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.

Troubleshooting​
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.

Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.