Develop Bugs

Stuck in Bootloader Fastboot Mode

Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked

Help Required - Soft brick - Stuck in bootloader
Dear All, Would really appreciate if you can help me with this thread..
Thanks
Regards
Tarun
TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse

Try to switch the slot to B and then boot

Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.

amusing_ankesh said:
Download qfil,
Scrap fz*.mbn from CSC_8.02 and put to raw file of your interest. Ifu don't do so, it will throw error as that file is required and only available in CSC_eng_8.02 version. Never ever touch any other file in CSC 8.02 , it will make it impossible to run any fastboot and adb command and entering EDL is a bit tricky.
Extract the firmware, make sure to have system,vendor,userdata in root path as if u don't remove last few line of Python extraction code it will be deleted.
Go to TWRP Recovery, and reboot to EDL from there.
select all raw program XML and Patch xml and begin Image download.
Doesn't matter whether anything is accessible or not u get new image of ur choice.
If u get sahara error you are not immediately beginning download as ur phone enters into EDL.
Suggestion: Once u get back image sell the [email protected] quarter of cost as it's impossible to run the device in the way you want. The tools are not supported for open source development. The device is fragile, a little tweak and you lose IMEI,SN and soforth your phone network. This is not a device to temper, if u still do so, you will never come out from situation your stuck now.
Click to expand...
Click to collapse
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.

same
ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that

ashok20205 said:
I also struck in the fastboot mode, All i have done is flashed android q image from asus official site , worked fine with few bugs, then i thought return to stock stable rom, downloaded image from the same page and tried the procedure given, but i got some error initially and struck in fastboot. Iam able to flash latest firmware by connecting to PC in fastboot, all files are able to flash and after restart, a message is appearing with red exclamatory symbol that my device is no longer boot, its not trustable etc and after few seconds restated to fastboot mode. I have tried this in both active slot A and B. I tried to flash android q image too. same error popping up. and iam struck in fastboot now, no recovery nothing, phone doest even switched off, if i longpress power key, restarts again to fastboot.
I want to try your solution, but iam not so expert in sdk things, i did't understand few points in your reply, can you please elaborate step by step procedure, which tools should i download how should i proceed etc. please iam going nuts wasting time behind this phone. or please refer any guide or website to unbrick my asus zenfone 5z.
Thanks in advance.
Click to expand...
Click to collapse
same problem any solution for that ?

TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
fastboot --cmdline "lge.kcal=0|0|0|x" boot customrecovery.img

I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked

kristoff07 said:
I also have the same problem. Tried installing TWRP but got stuck in Fastboot mode. Says phone is corrupted and cannot be trusted.
Product Name: ZS620KL
Bootloader Version: WW_user_100.10.107.70
Secure Boot: Yes
Active Slot: b
Device State: locked
Click to expand...
Click to collapse
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.

TG87 said:
Dear All,
I was trying to install a customer ROM in my Asus Zenfone 5z. I was able to unlock the bootloader using official asus app. Then i managed to install a TWRP recovery. there was some partition issue so i flashed recovery in both partitions. the recovery worked fine and i managed to install the pixel rom. after that i wiped dalvik cach and some other items throgh recovery and restarted the phone.
After restart, it is stuck in bootloader. If i select start, recovery mode or power off, it gets rebooted and come back to bootloader again. Seems like a brick scenario.
So i tried the following:
1. Downloaded AFT tool and tried to flash the latest firmware version.. It gave a FPT error and then error on unable to load into recovery mode
2. Tried to run flashall_aft.cmd in directory containing latest firmware.. it said to internal/external command exists
3. Sideload using adb sideload command.. the error was could not read the file..
I am not sure what i can try next.. could you please help.. The details on bootloader screen are:
Fastboot mode
Product name _ ZS620KL
Bootloader version - WW_user_90.10.138.157
Secure Boot - yes
Active Slot A
Device State Unlocked
Click to expand...
Click to collapse
secure boot yes? you may have vertified boot, you can try flash patched magisk boot.img to disable that

jjgvv said:
Your bootloader is relocked, and vertified boot is enabled, if I had not misunderstanded the information you have given. Try unlocking your bootloader first.
Click to expand...
Click to collapse
I checked the info and it gave me 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"
}

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?

Installing Custom ROM on Cubot KingKong Mini

UPDATE 2021
The original post was for the first King Kong Mini, for instructions for the King Kong Mini 2 go to page 9 in this thread:
https://forum.xda-developers.com/t/...-on-cubot-kingkong-mini.4050815/post-84445303
======================
The Cubot King Kong Mini was released in Q4 2019. It is one of the smallest Android phones on the market with a 4" screen. Like many cheap Mediatek devices, one cannot be sure of how "safe" or "secure" these devices are, so the security/privacy conscious may want to consider installing a custom ROM. Here are the instructions for installing Android AOSP on the Cubot King Kong Mini. Note: I am not responsible for any bricked devices.
Download the Stock Rom from here and SP Flash Tool just in case you need to reinstall Stock. Download a system image, note you need to use an A/B arm32 image with 64 bindings. For example AOSP 9 is here.
This process probably can be done with SP Flash Tool but I wasn't able to manage it due to the disable-verification flag required.
Unzip the stock ROM and reboot the device to bootloader, connect via USB and unlock via:
Code:
sudo fastboot flashing unlock
Note this will erase all data. Then on your computer navigate to the folder with the unzipped ROM (for me was NA_mt6761p_d936p_9101cmp_chuanqi_cc_256gbitp24d3_p_lte_3m-fdd-cs_mul_20191121-210020_songlixin_PC) and type
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you do not do this it seems to work without it but then it will bootloop when you try to switch it on. From here on it's standard.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Unzip the .xz image file you wish to use and type:
Code:
fastboot flash system SYSTEM.img
where SYSTEM is the name of whatever image downloaded.
Root
For root install magisk manager and you have to patch the recovery to get root (not just boot as flashing boot alone doesn't give you root). So in magisk get it to patch you boot and recovery images and then put those on your computer, go to bootloader and use:
Code:
fastboot flash boot magisk_patched_boot.img
fastboot flash recovery magisk_patched_recovery.img
You can read more about magisk from recovery here.
To get root then you need to reboot to recovery, hold power button + volume up and select Recovery. This will appear to boot as normal but you will have root when you do it this way and not when you boot normally. Unfortunately I do not have reception when I do this but do have root, other users have this problem but I have not found a solution.
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
What doesn't work
Battery usage doesn't work, this can probably be fixed following this guide. If I get time I will attempt this.
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
The battery life is definitely worse using AOSP GSI than stock, maybe that vendor overlay would help with that though.
I hope that helps others.

TWRP+Encryption Disabling+Magisk Root
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.

well well, finally and serranoltexx successor?
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]

moctir said:
Other things to note, there is no TWRP yet so I don't have decent recovery options, this also makes it harder to use certain ROMS as you can't flash things like gapps if you install a ROM without it.
Click to expand...
Click to collapse
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/

robrazil said:
I saw 2 places talking about TWRP in King Kong Mini but I don't know if is safe:
- https://unofficialtwrp.com/unofficial-twrp-3-3-1-root-cubot-king-kong-mini/
- https://www.getdroidtips.com/twrp-recovery-cubot-kingkong-mini/
Click to expand...
Click to collapse
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!

Tom Mix said:
i ordered one yesterday and am looking forward to get an suiteable replacement for my S4 MiNi [serranoltexx]
Click to expand...
Click to collapse
I did it to replacement my old Samsung J1 ace, very similar of S4 Mini, and I'm not regretful for that.
---------- Post added at 01:37 PM ---------- Previous post was at 01:08 PM ----------
moctir said:
Based on the second poster here and someone else who sent me a pm, I believe the TWRP is safe, I haven't tested it myself yet but I plan to at some point and will post here when I do. When I'm using it as my primary device and everything is working okay it's hard to justify messing with it more at the moment!
Click to expand...
Click to collapse
I understood but the point is if the TWRP source is confiable. I asked the official TWRP Team about the unofficials TWRP on websites in my last post, and they answer: "Hello, we do not run that site, so I cannot confirm the validity of their images."
So, I wonder how safe the unofficial TWRP images are.

moctir said:
Note that I thought I bricked my phone a few times before getting this as nothing would happen after a failed boot and I couldn't switch it on, however what happens is you can't do anything until the battery has almost completely discharged, then when you hit the power button you'll get the no battery sign and when you plug in you can get to Recovery again. This is quite annoying if you've charged it quite high as you'll have to wait a long time to discharge and be tapping on the power button a lot!!
Click to expand...
Click to collapse
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:

robrazil said:
This is a very important information. When I did a update firmware the usb cable disconnected and the mobile died. Black screen. The side buttons died too. Only blue led turn on when the usb cable is connected on PC. The windows 10 only recognized the mobile as "unknown usb device (device descriptor request failed)". I thought that had lose the mobile. A few days later when I connect the mobile in the PC, the battery image was showed on screen with 18% of charge and I saw in that moment that I could flash the firmware again.
I flashed official firmware and the mobile worked again but now it died again... because I did a wrong recovery boot. I will wait discharge the battery again. :crying:
Click to expand...
Click to collapse
Yes, indeed there were three times I thought I had totally bricked and each time I was so annoyed with myself! The key is to not charge it much until you are happy with the ROM you put on.
The amount of drivers I tried to use for different OS' when I got that "unknown USB device" on Windows and Linux didn't detect it was all a waste of time!

Well... the battery image appeared again and I uploaded firmware again. I installed the Magisk in the boot recovery, because this only way to install the Magisk on devices that are using system-as-root, but the Magisk disable my 2 SIM cards. When I boot without Magisk, all back to normal.
I serched for any solution for that but I didn't find.
So, my conclusion is that the Magisk not works to Cubot King Kong Mini. How can I stay with a phone with no SIM card?
I give up.

For me I can only get root when I patched Magisk to Recovery and then boot to Recovery and it doesn't see my SIM card but I have root, so I reboot every time I need root which is a bit annoying...

It is very complicated everytime when need "root", to have power off and on the mobile in recovery boot mode. Besides that, run out of SIM card working is not an option.
I will try to get support of this issue with Magisk Team.
Thank you for share your experience.

Ce3apyc said:
Actually there is TWRP for this model ported from alcatel by NickyNS. You can pick up it from here.
You can flash it with fastboot along with the patched lk which is to disable the "Orange state" message. After flashing it you should enter TWRP right with the next step (without booting to OS). On this stage you might want to disable encryption in order to have full-fledged backup-recovery option in TWRP next time you use it. To do so you will have to format data partition. After that step you will loose all you applications and user data for them, so you should backup it previously. After you format the data, flash Magisk first, then flash encryption disabling script from this post. Now you can boot to OS.
Note, that attached TWRP is only valid for firmware CUBOT_KINGKONG_MINI_9101C_V06_20191121. Cubot has released a new one and you can try to use the TWRP with it, but there is no guarantee it will work correctly.
Click to expand...
Click to collapse
Hello,
Does anybody can confirm, that this is working with the new firmware?

I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?

Ce3apyc said:
You will not be able to mount and/or use the backup feature of the TWRP until you disable an encryption by formating the data partition and running the script (just press "Cancel" in the TWRP to be able to do that when it asks for the password). Read my original post very carefully. There is a complete sequence of steps in it. Have you tried the TWRP with the last firmware? How did the rest of the system work?
Click to expand...
Click to collapse
I'm using treble AOSP Android 9 so not the latest firmware. I thought disabling the verification when installing that would be enough but maybe I do need to do those other steps. I can see the /system directory through TWRP so that's probably because that's the one I flashed, but I can't see the internal storage otherwise.

moctir said:
I tried the TWRP a few days ago and was able to boot to it but I couldn't mount it to see my files, it asked for a password and I tried "default_password" and creating a password for the phone but that also didn't work. A possibility is to change the file format to ext2 and then to ext4 but I didn't want to try it when I couldn't back it up.
Click to expand...
Click to collapse
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
{
"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"
}

robrazil said:
You need to put the "Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip" file into SD card or internal memory to install by TWRP. This file disable the asking of password. Worked for me.
Click to expand...
Click to collapse
Thanks, I'll check it out!

Anyone else having problems with sensors on this phone? Rotating and compass do not work for me. That's what you get for buying a cheap Chinese phone, I guess.
EDIT: Downgrading firmware back to CUBOT_KINGKONG_MINI_9101C_V06_20191121 seems to fix some problems, rotation works, but compass is still buggy.

Never tried compass but haven't had any problems with rotation.

Tried to install root on a friends kkm but I can't get it working in the os. Is there any chance to get it working there? I am only able to get root access in twrp. Maybe an gsi with root is that possible?

Hard bricked my device on my first flashing attempt, what did I do wrong?

Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.

...

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.

mrmazak said:
The system destroyed message is a common one. It's a result of avb (Android verified boot).
Simple solution is to disable this verity. Done by flashing in fastboot. It should have been part of the unlocking/ twrp guide. But it's not. This makes many people have this error.
Click to expand...
Click to collapse
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
mrmazak said:
Now as for the other issue. That sounds like the hard-brick error that comes from flashing ginkgo firmware on a willow device.
Ginkgo = note 8
Willow = note 8T
Afaik, this brick is not consumer repairable. I have not found any posts saying they had fixed this problem without service center.
Click to expand...
Click to collapse
Yes, I think this is what happened with the MiFlash. My device was probably Willow. I sent it back to repair but I don't know yet if they will be willing to fix it.

douteiful said:
I could flash and boot TWRP first; I could adb push things too. Everything broke after I wiped the partitions. It's like everything became non-writable and I couldn't even boot TWRP recovery. adb push would say "Permission denied" and fastboot boot would say "Invalid command (Too many links)"
.
Click to expand...
Click to collapse
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.

Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks

mrmazak said:
The "too many links" is a message you get when you type wrong commands..
Like example:
Fastboot flash flash boot boot.img
See There are too many commands/ links.
Let's hope the service center will fix you up.
Click to expand...
Click to collapse
Thanks, but I'm pretty sure I entered the command correctly and it was among the lines of "FAILED (status read failed (Too many links))". I have searched for the error but nobody seems to know the cause.
LoadOP2 said:
Hello, I just wanted to know was your device in Warrenty?. And how much did the mi service center charged you? Thanks
Click to expand...
Click to collapse
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.

douteiful said:
I bought it only 1 week ago. It was new, so it's under warranty. But I haven't received a response from the service center yet. I don't know what will happen. I'll keep you posted.
Click to expand...
Click to collapse
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.

OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
I don't know if they changed it of it's because I had already unlocked a bootloader before (my previous Redmi Note 5) but it only asked to wait for 168 hours (7 days).
{
"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"
}

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
-You don't reboot to recovery after flashing twrp, it wont stick if you don't reboot it
-No problem for wiping system as ive done full wipe before, it will delete your os (needed for converting to cusrom)
-Tried to copy files into sdcard through twrp is not stable in my experience as i couldnt do it as well (not responding), i turned off device as well but it boot back to recovery quickly by it's own (im using latest twrp official), i dont force myself using adb anymore and just use external sdcard, copied rom directly with sdcard reader, install rom and got bootloop (back to recovery automatically, i format data and boot properly)
-You don't have system so turning off and try booting would be worst decision and because your twrp not stick, you can't go back neither
-Too many links is because adb commands is wrong
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
i think you dont need to wait anymore, im unlocking my redmi just a few minutes, maybe because new added verification at latest miui unlock

OliveReeve said:
How can you unlock it so fast? I have read that It should take 30 days to unlock bootloader in official way.
Click to expand...
Click to collapse
lol no.. it's 168 hours usually if you do everything correctly

you should rebout to twrp after flashing it , also you didn't flash vbmeta (i don't know what it does,but mine was fixed once i flash it)

douteiful said:
Hi everyone,
I know this is posted a lot and I'm really sorry. But I couldn't find similar experiences to mine. Can someone spot my mistake?
1. I unlocked my bootloader using Xiaomi's official process
2. I used fastboot to flash and boot TWRP (twrp-3.4.0-0-ginkgo-willow-mauronofrio.img)
3. I wiped system, sdcard, cache partitions.
4. I tried to copy the crDroid zip from my PC to my phone but it wouldn't transfer. I tried adb push but I would get a Permission denied error.
5. I turned off the device (big mistake here) thinking I'd be able to boot TWRP recovery again. But trying to get into recovery (vol down+power) would give me a "System destroyed" screen.
6. I tried to re-flash and boot TWRP through fastboot but it would give me the error "Too many links".
7. At this point the device was soft bricked but I made a worse mistake. I tried to flash an official MIUI 11 image using MiFlash but after it finished the device would show a black screen and shut down after 1 second. Fastboot shows the fastboot logo but it also shut downs after 1 second. Computer doesn't recognize it.
Why did this happen? I sent the device to Mi's service center, but I want to know why it went so wrong so I don't make the same mistake again.
Sorry for the common question. Thank you all.
Click to expand...
Click to collapse
On step 5, you can still boot into recovery, the button is Vol up+power, but you press voldown+power(as you mentioned) will bring you to fastboot and get into System is destroyed screen. System is destroyed screen is normal. You just need to flash VBMETA. Your biggest mistakes and caresless is you dont do your research thoroughly. Risk is yours.
Make an habit to place your file to sdcard and always flash DMVERITY after anything you have done inside TWRP. DMVERITY is a must. In your case, vbmeta itself disable that force encryption and if you flash this, youll be able to enter fastboot mode.
Too many links means you dont enter the command correctly.
On steps 7 eventually will bring your phone back. I guess you got the indian version of RN8 where many people experiencing and posted on telegrams about this issues that they are unable to flash miui stock roms when that System is destroyed screen happen and end up bricking the phone. The only way and safest way to prevent this is, to flash VBMETA if you got the System is destroyed screen. Do not ever flash miui roms using miflash until you flashed that VBMETA. Then you are good to go flashing any roms using miflash

Update, something weird happened. I just got a message from the service center telling me that the phone had no issues, and they even showed me a video of it working (same IMEI). Which is weird because I'm pretty sure I hard bricked it. My guess is that they unbricked it and didn't tell me for some reason. Either way they didn't charge me any money so I'm happy. I'll get my device back next week and I'll check the things that you told me, particularly the model (ginkgo/willow).

Got my phone today. It's working. I don't know how they fixed it, and it's also unlocked. Just for the record, the Xiaomi ADB tool identifies it as a ginkgo, and the model number is M1908C3JH which is apparently ginkgo as well. If so, why did this all happen then?

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.