Database Info

Unable to flash recovery.

HI.
Fresh install of the latest Android 6 on to my N5.
I used Wug and everything has gone well apart from I don't have a recovery.
I've booted to the bootloader and tried the following..
Code:
fastboot flash recovery twrp-3.0.2-0-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14524 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 1.125s]
finished. total time: 1.813s
Rebooted to Android, rebooted to recovery and nothing.. little green man on his back
I've also tried stock recovery with the same results.
fastboot flash recovery recovery.img
Code:
target reported max download size of 1073741824 bytes
sending 'recovery' (10008 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 0.841s]
finished. total time: 1.397s
I've tried flashing, rebooting to bootloader, then rebooting to recovery I still get the same.
Any ideas ?
Thanks

Panic Over
I've just done this again and after the flash finished, I rebooted to recovery swiped to allow modifications and now it's taken !

How can i flash the factory image without encrypting?

Hi all,
I recently rooted my Pixel and was plagued by the 15% battery issue. I found in the Pixel XL forum to fix it i should flash boot_a boot.img but that erased all my data.
I figured I'd start fresh and looked up a few websites who had instructions (androidcentral being one of them) and it seems like any other google phone, except i started getting FAILED to flash. so i ended up doing the following and now my device is encrypted.
fastboot flash bootloader bootloader-img
fastboot reboot bootloader
fastboot flash radio radio-img
fastboot reboot bootloader
fastboot flash boot_a boot.img
fastboot flash system_a system.img
fastboot flash userdata userdata.img
fastboot flash vendor_a vendor.img
fastboot format userdata (have to do this in order to get phone to read as 128GB)
---
so now when i boot up, it goes through the setup but it's encrypted.
I guess my question is, with the way Pixel's will be handling updates, what are all of the extra .img files from the factory image and should i be flashing them in a particular order?
here are the contents:
aboot.img
apdp.img
boot.img
bootlocker.img
cmnlib32.img
cmnlib64.img
devcfg.img
hosd.img
hyp.img
keymaster.img
modem.img
pmic.img
rpm.img
system_other.img
system.img
tz.img
userdata.img
vendor.img
xbl.img
Any assistance would be greatly appreciated!
Thanks!

EDIT #1: I just locked and then unlocked the bootloader to see if that allows me to setup as unencrypted. It's taking a while to boot so I doubt it.
EDIT #2: Still encrypted after set up.
Wellp... i wonder what flashing these after the initial order above will do...
EDOT#3:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
... still encrypted, it booted up a bit quicker (or maybe i'm going nuts)
EDIT #4:
lock / unlock botloader
fastboot flash system_a system.img
fastboot flash system_b system_other.img
fastboot flash keymaster_a keymaster.img
andddd.... still encrypted... can anyone help out?

updating android sudio/sdk

So on the newest SDK, the fastboot flash system system.img will automatically detect and erase system_a.
probably a good idea to be on the latest sdk platform-tools

lockd / unlocked bootloader
bash update-all.sh
CRUD... still encrypted.
here's the output if anyone would like:
Code:
Marcs-MacBook-Pro:sailfish-nde63p root# bash flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32820 KB)...
OKAY [ 1.404s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
OKAY [ 1.040s]
finished. total time: 2.444s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
sending 'radio_a' (57048 KB)...
OKAY [ 2.457s]
writing 'radio_a'...
OKAY [ 0.869s]
finished. total time: 3.326s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: NOPE :)
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.051s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (25073 KB)...
OKAY [ 0.982s]
writing 'boot_a'...
OKAY [ 0.600s]
erasing 'system_a'...
OKAY [ 1.201s]
sending sparse 'system_a' 1/4 (518936 KB)...
OKAY [ 29.084s]
writing 'system_a' 1/4...
OKAY [ 5.336s]
sending sparse 'system_a' 2/4 (506887 KB)...
OKAY [ 28.523s]
writing 'system_a' 2/4...
OKAY [ 13.352s]
sending sparse 'system_a' 3/4 (491777 KB)...
OKAY [ 28.733s]
writing 'system_a' 3/4...
OKAY [ 6.808s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 1.732s]
writing 'system_a' 4/4...
OKAY [ 0.619s]
erasing 'system_b'...
OKAY [ 1.181s]
sending sparse 'system_b' 1/4 (517263 KB)...
OKAY [ 30.183s]
writing 'system_b' 1/4...
OKAY [ 4.555s]
sending sparse 'system_b' 2/4 (513954 KB)...
OKAY [ 25.261s]
writing 'system_b' 2/4...
OKAY [ 5.386s]
sending sparse 'system_b' 3/4 (523846 KB)...
OKAY [ 33.335s]
writing 'system_b' 3/4...
OKAY [ 4.485s]
sending sparse 'system_b' 4/4 (88422 KB)...
OKAY [ 7.907s]
writing 'system_b' 4/4...
OKAY [ 1.348s]
erasing 'vendor_a'...
OKAY [ 0.520s]
sending 'vendor_a' (234137 KB)...
OKAY [ 7.342s]
writing 'vendor_a'...
OKAY [ 6.647s]
Setting current slot to 'a'...
OKAY [ 0.400s]
erasing 'userdata'...
OKAY [ 28.688s]
sending 'userdata' (145102 KB)...
OKAY [ 4.998s]
writing 'userdata'...
OKAY [ 2.393s]
rebooting...
finished. total time: 282.030s
Marcs-MacBook-Pro:sailfish-nde63p root#

tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/

spunks3 said:
tried factory reset and flashing some of the other images... no luck, still encrypted. guess i'll need to wait for TWRP to come out and figure out how to decrypt :-/
Click to expand...
Click to collapse
Thanks friend!:laugh:

Modifiy the kernel

omegear said:
Modifiy the kernel
Click to expand...
Click to collapse
How?

Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!

Oface82 said:
Hey spunks, I'm in the same boat with you. Cant decrypt. I don't even remember encrypting in the first place!
Click to expand...
Click to collapse
I think it'll just be a waiting game... This happened to me when I flashed the original boot image using an out of date SDK.

Can you point me in the direction of the factory images? I need to start over

Why are you so desperate to decrypt? It's encrypted by default, and stops you from nothing at this moment, and likely won't be a road block in the future either.
Sent from my Pixel using Tapatalk

I had a similar issue. I tried to unroot in order to install the new OTA, because it failed. So I tried to flash the factory boot image via
Code:
fastboot flash boot boot.img
fastboot flash boot_b boot.img
After the next boot I got the nice "erasing" screen...
My phone was unencrypted before (dunno why) and now all my data is gone and it is encrypted... Maybe there are some devices, which are not encrypted by default and factory resetting after updates...

Unable to update to 8.1 in anyway

Hi all. it's been a while since I've posted on xda
I'm having a problem with my newly acquired Pixel,
Today, I received an OTA notification for Android 8.1, tried to have it install but the when the phone restarts to install, it just flash to google logo like 3 times and them boot back to 8.0.
I looked it up on google, people say I should factory reset before restarting and install 8.1. Tried that but same thing happens.
Then I decided to download the factory image and flash it myself. With OEM unlocking and Android debugging enabled, the 8.1 image flashed successfully. However, the phone doesn't boot, it shows a dead Android and a "No command" error. Same thing happen when I try to sideload the OTA file...
I had to flash the 8.0 factory image for the phone to boot successfully again...
Now I have no idea how to get 8.1... Do you guys have any idea of what can be done or what's happening?
Thanks in advance!

Did you update your fastboot tools? That is needed for 8.1

TonikJDK said:
Did you update your fastboot tools? That is needed for 8.1
Click to expand...
Click to collapse
I used the latest version of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
It flashed successfully without any error, so I assume my fastboot is fine...

If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.

Thanks, I'll try and report back

roirraW "edor" ehT said:
If 8/28/15 is the latest minimalist platform tools, it's too old. I don't have the link handy but Google provides a direct link to the latest at all times now, so you don't have to install the developer tools or download someone else's repackaged to get the latest.
They updated it yet again the day they released 8.1.
Edit: here it is
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
The link stays the same and is always the latest version. Just extract it to where the firmware is extracted to.
Click to expand...
Click to collapse
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.

cnkhanh said:
Just tried the latest platform tools, and the same issue persists... any idea?
Edit: Tried sideloading 8.1 OTA from 8.0, however, it boots back to 8.0 eventually.
Click to expand...
Click to collapse
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...

nine7nine said:
how about not doing an ota update but using the full firmware image instead?
you would have two options;
1. edit the flash-all script, removing the -w flag, so it doesn't wipe your data partition
2. or do a full system wipe backup anything important first...
Click to expand...
Click to collapse
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...

cnkhanh said:
I already tried flashing the 8.1 factory image, wiping data, still have the same issue though...
Click to expand...
Click to collapse
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...

nine7nine said:
I don't see how that would be possible, if u had run the flash-all script it would've replaced the bootloader, all of your devices partitions with the new firmware...
there would be no 8.0 to boot back into, at all.
please write your steps down and some of thevrelevant output you see on your phone, when the script runs...
Click to expand...
Click to collapse
Sorry, I meant the issue was that in my original post, the phone doesn't boot and stuck on the "No command" screen...
When the flash all script runs, my phones was on fastboot mode, rebooting to bootloader several times during the process (this is expected i guess). When the script finishes successfully, the phone tries to boot into the OS, but it shows a google logo and turns off, several times (like a bootloop), then eventually shows the "No command" screen.

Currently, I'm on 8.0, build number OPR3.170623.013

cnkhanh said:
Currently, I'm on 8.0, build number OPR3.170623.013
Click to expand...
Click to collapse
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs

Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Click to expand...
Click to collapse
Sgace said:
Are u using the right firmware package for your model?
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Thanks for pointing out, but the version I was trying to flash was correct, sailfish 8.1.0 (OPM1.171019.011, Dec 2017)
I'll try another PC and cable later, I'm running on Windows 10 Fall Creator Update.
I don't think warranty is a viable option for me

Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...

roirraW "edor" ehT said:
Just to clarify, there's only one 8.1 firmware package for the Pixel Sailfish, but I think @Sgace is pointing out that you could've downloaded the full firmware for the Marlin (XL) or any of the other Pixels.
Last ditch effort is a different PC and/or cable.
I'm out of ideas otherwise. Is it under warranty?
Click to expand...
Click to collapse
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
cnkhanh said:
Here is the cmd lines when installing 8.1, seems fine with me.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32248 KB)...
OKAY [ 0.888s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 2.059s]
finished. total time: 2.951s
rebooting into bootloader...
OKAY [ 0.051s]
finished. total time: 0.052s
target reported max download size of 536870912 bytes
sending 'radio_a' (57320 KB)...
OKAY [ 1.499s]
writing 'radio_a'...
OKAY [ 0.486s]
finished. total time: 1.989s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.051s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (28 MB) to disk... took 0.410s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (1751 MB) to disk... took 18.393s
archive does not contain 'system.sig'
extracting system_other.img (551 MB) to disk... took 6.660s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (250 MB) to disk... took 2.662s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6509568 4k blocks and 1630208 inodes
Filesystem UUID: 657305e6-e288-11e7-8b52-538b74cf9ac7
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: 8996-012001-1710040120
Baseband Version.....: 8996-130091-1710201747
Serial Number........: FA6960306426
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.048s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
erasing 'system_a'...
OKAY [ 0.320s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.651s]
writing 'system_a' 1/4...
OKAY [ 3.451s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 13.604s]
writing 'system_a' 2/4...
OKAY [ 3.488s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 14.015s]
writing 'system_a' 3/4...
OKAY [ 3.446s]
sending sparse 'system_a' 4/4 (220660 KB)...
OKAY [ 5.700s]
writing 'system_a' 4/4...
OKAY [ 1.494s]
erasing 'system_b'...
OKAY [ 0.261s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 13.702s]
writing 'system_b' 1/2...
OKAY [ 3.451s]
sending sparse 'system_b' 2/2 (40660 KB)...
OKAY [ 1.083s]
writing 'system_b' 2/2...
OKAY [ 0.355s]
erasing 'vendor_a'...
OKAY [ 0.142s]
sending 'vendor_a' (257004 KB)...
OKAY [ 6.358s]
writing 'vendor_a'...
OKAY [ 1.758s]
Setting current slot to 'a'...
OKAY [ 0.088s]
erasing 'userdata'...
OKAY [ 1.705s]
sending 'userdata' (4412 KB)...
OKAY [ 0.196s]
writing 'userdata'...
OKAY [ 0.100s]
rebooting...
finished. total time: 89.845s
Press any key to exit...
Click to expand...
Click to collapse
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs

cnkhanh said:
sending 'boot_a' (28945 KB)...
OKAY [ 0.750s]
writing 'boot_a'...
OKAY [ 0.296s]
Click to expand...
Click to collapse
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Click to expand...
Click to collapse
You're welcome, hey, you can up with the good suggestion!
Another idea is at least on 8.0 with SuperSU, I was able to flash the entire 8.1 firmware with @Chainfire 's FlashFire app, every partition.

Sgace said:
Oops, yes that's what I meant.
Thnx for pointing that one out. I had to be more clear.
Cheers
Sent from my Google Pixel using XDA Labs
---------- Post added at 07:51 PM ---------- Previous post was at 07:47 PM ----------
Looks ok to me too. Are u able to manually boot to stock recovery after the flash and from there do a factory reset?
Cheers
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
nine7nine said:
I would have to re-flash the firmware to check (which I'm not doing), but shouldn't the boot.img be flashed to both the slot_a and slot_b partitions?
your issue of it ending boot with the recovery "no command" makes me think that something isn't right with the flashed boot images....
one thing you could try is unzipping the fimeware update zip and manually using fast boot to flash the boot images, after flashing the firmware....
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
you could also try using twrp to manually flash the boot.img and system image (you would need to copy them to your device though).... I've bumped into the error you speak of; but not when doing a full flash of system firmware.... that _shouldn't_ happen.....
Click to expand...
Click to collapse
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues

cnkhanh said:
Yes, I still can boot in to stock recovery, I tried factory reset many times though...
Hmm, I think it only flashes the active slot. Mine is "a", shown in bootloader mode.
Btw, my device shows the OTA update is about 566 MB while the OTA zip for sideloading is 900+MB, is that normal?
Edit: Just tried flashing both boot slot "a" and "b", changing active boot slot to "b" still have the same issues
Click to expand...
Click to collapse
My theory is that it is updating the secondary system partition but failing to switch partitions. I could be wrong.

[Guide] How to flash stock ROM on Redmi Go

If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM.
Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error.
But, there is a way!
Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time)
CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device.
Requirements
- Unlocked Bootloader
- Xiaomi USB drivers installed on your PC
- PC/TWRP
- microSD Card
- Minimal ADB & Fastboot (If using PC)
- V10.2.6.0.OCLMIXM ROM zip file (Download here
-V10.2.7.0.OCLMIXM (Download here
At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later).
Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card.
Steps, if you're using PC
1. Install Minimal ADB & Fastboot (Download here)
2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed.
3. Run "cmd-here" and type fastboot flash recovery recovery.img
4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together.
5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Steps, if you're using TWRP
1. Copy the "recovery.img" file that you extracted earlier, to your SD Card.
2. Boot TWRP
3. Select Install
4. Select Install Image
5. Locate the "recovery.img" file in your SD Card and install it.
6. Go back to main menu and reboot into recovery.
7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Your device should now be running clean stock ROM and recovery.
Don't forget to hit Thanks Button if you found this useful.

As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot.
The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one.
Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried).
Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html
This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ):
Boot Image Patching
This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead.
In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image.
Copy the boot image to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot image file
Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices:
fastboot flash boot /path/to/magisk_patched.img
-----------------
Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html
Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA).
https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/
And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction.
I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever.

Actually tried an easier way:
Just download the tgz file from mi website tiare_global_images_V10.2.6.0.OCLMIXM_20190218.0000.00_8.1_66cc42a821.tgz
If you are on linux it is easy tar xvf filename
Code:
tiare_global_images_V10.2.6.0.OCLMIXM_8.1$ ls -R
.:
flash_all.bat flash_all_except_data_storage.sh flash_all_lock.sh flash_gen_crc_list.py flash_gen_resparsecount md5sum.xml
flash_all_except_data_storage.bat flash_all_lock.bat flash_all.sh flash_gen_md5_list.py images misc.txt
./images:
adspso.bin crclist.txt gpt_both0.bin NON-HLOS.bin prog_emmc_firehose_8917_lite.mbn sbl1.mbn userdata.img
boot.img devcfg.mbn gpt_main0.bin partition.xml rawprogram0_BLANK.xml sparsecrclist.txt vendor.img
cache.img elf_path.txt keymaster64.mbn patch0.xml rawprogram0.xml splash.img
cmnlib_30.mbn emmc_appsboot.mbn keymaster.mbn persist.img recovery.img system.img
cmnlib64_30.mbn gpt_backup0.bin lksecapp.mbn prog_emmc_firehose_8917_ddr.mbn rpm.mbn tz.mbn
$ chmod +x flash_all_lock.sh
$ ./flash_all_lock.sh
tiare Fastboot Tool Ver 3.0
product: tiare
target reported max download size of 535822336 bytes
sending 'partition' (33 KB)...
OKAY [ 0.004s]
writing 'partition'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.010s
target reported max download size of 535822336 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.002s]
writing 'crclist'...
OKAY [ 0.006s]
finished. total time: 0.009s
target reported max download size of 535822336 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.002s]
writing 'sparsecrclist'...
OKAY [ 0.006s]
finished. total time: 0.008s
target reported max download size of 535822336 bytes
sending 'tz' (1503 KB)...
OKAY [ 0.055s]
writing 'tz'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.062s
target reported max download size of 535822336 bytes
sending 'sbl1' (342 KB)...
OKAY [ 0.014s]
writing 'sbl1'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.020s
target reported max download size of 535822336 bytes
sending 'rpm' (180 KB)...
OKAY [ 0.009s]
writing 'rpm'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.015s
target reported max download size of 535822336 bytes
sending 'aboot' (559 KB)...
OKAY [ 0.024s]
writing 'aboot'...
FAILED (remote: Critical partition flashing is not allowed)
finished. total time: 0.030s
target reported max download size of 535822336 bytes
sending 'tzbak' (1503 KB)...
OKAY [ 0.056s]
writing 'tzbak'...
OKAY [ 0.064s]
finished. total time: 0.120s
target reported max download size of 535822336 bytes
sending 'sbl1bak' (342 KB)...
OKAY [ 0.015s]
writing 'sbl1bak'...
OKAY [ 0.024s]
finished. total time: 0.040s
target reported max download size of 535822336 bytes
sending 'rpmbak' (180 KB)...
OKAY [ 0.009s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.030s
target reported max download size of 535822336 bytes
sending 'abootbak' (559 KB)...
OKAY [ 0.023s]
writing 'abootbak'...
OKAY [ 0.034s]
finished. total time: 0.057s
target reported max download size of 535822336 bytes
sending 'devcfg' (60 KB)...
OKAY [ 0.004s]
writing 'devcfg'...
OKAY [ 0.014s]
finished. total time: 0.018s
target reported max download size of 535822336 bytes
sending 'cmnlib' (208 KB)...
OKAY [ 0.010s]
writing 'cmnlib'...
OKAY [ 0.022s]
finished. total time: 0.032s
target reported max download size of 535822336 bytes
sending 'cmnlib64' (262 KB)...
OKAY [ 0.012s]
writing 'cmnlib64'...
OKAY [ 0.023s]
finished. total time: 0.035s
target reported max download size of 535822336 bytes
sending 'keymaster' (265 KB)...
OKAY [ 0.012s]
writing 'keymaster'...
OKAY [ 0.023s]
finished. total time: 0.035s
target reported max download size of 535822336 bytes
sending 'devcfgbak' (60 KB)...
OKAY [ 0.004s]
writing 'devcfgbak'...
OKAY [ 0.014s]
finished. total time: 0.018s
target reported max download size of 535822336 bytes
sending 'cmnlibbak' (208 KB)...
OKAY [ 0.010s]
writing 'cmnlibbak'...
OKAY [ 0.023s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'cmnlib64bak' (262 KB)...
OKAY [ 0.013s]
writing 'cmnlib64bak'...
OKAY [ 0.023s]
finished. total time: 0.036s
target reported max download size of 535822336 bytes
sending 'keymasterbak' (265 KB)...
OKAY [ 0.012s]
writing 'keymasterbak'...
OKAY [ 0.025s]
finished. total time: 0.038s
target reported max download size of 535822336 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.584s]
writing 'dsp'...
OKAY [ 0.550s]
finished. total time: 1.134s
erasing 'boot'...
OKAY [ 0.016s]
finished. total time: 0.016s
erasing 'apdp'...
OKAY [ 0.013s]
finished. total time: 0.013s
erasing 'msadp'...
OKAY [ 0.013s]
finished. total time: 0.013s
target reported max download size of 535822336 bytes
sending 'modem' (86016 KB)...
OKAY [ 3.050s]
writing 'modem'...
OKAY [ 3.022s]
finished. total time: 6.072s
target reported max download size of 535822336 bytes
erasing 'system'...
OKAY [ 0.160s]
sending sparse 'system' (502636 KB)...
OKAY [ 19.755s]
writing 'system'...
OKAY [ 17.618s]
sending sparse 'system' (523260 KB)...
OKAY [ 20.561s]
writing 'system'...
OKAY [ 18.747s]
sending sparse 'system' (115276 KB)...
OKAY [ 4.530s]
writing 'system'...
OKAY [ 4.084s]
finished. total time: 85.454s
target reported max download size of 535822336 bytes
erasing 'cache'...
OKAY [ 0.011s]
sending 'cache' (140 KB)...
OKAY [ 0.008s]
writing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'userdata' (192 KB)...
OKAY [ 0.009s]
writing 'userdata'...
OKAY [ 0.023s]
finished. total time: 0.033s
target reported max download size of 535822336 bytes
sending 'recovery' (20207 KB)...
OKAY [ 0.717s]
writing 'recovery'...
OKAY [ 0.670s]
finished. total time: 1.387s
target reported max download size of 535822336 bytes
sending 'boot' (15547 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.581s]
finished. total time: 1.135s
target reported max download size of 535822336 bytes
sending 'splash' (10802 KB)...
OKAY [ 0.380s]
writing 'splash'...
OKAY [ 0.366s]
finished. total time: 0.747s
target reported max download size of 535822336 bytes
sending 'vendor' (278000 KB)...
OKAY [ 9.794s]
writing 'vendor'...
OKAY [ 9.957s]
finished. total time: 19.751s
...
OKAY [ 0.057s]
finished. total time: 0.057s
rebooting...
finished. total time: 0.061s
System fresh as NEW.

Note that there is a newer version: 10.2.12

Sadly the phone even AOSP with just whatsapp and email becomes very slow. Flashed stock return to retailer!

hello.
weareinwarwithbugs said:
As I am writing here, Redmi Go doesn't yet have any official, nor nonofficial custom recovery that doesn't have major bugs. The easiest way to root Redmi Go, as I found, is to do it without custom recovery with Magisk, with adb and fastboot.
The problem I personally faced was that I installed the OTA updates, and in such case the stock rom's boot.img does not match with the new updated/altered rom that is installed through OTA update. So before patching stock boot.img with magisk, and flashing the patched boot.img, which is based on that stock rom, you have to have stock rom, instead of OTA updated one.
Before doing you probably have to also install xiaomi usb driver, and of course you have to unlock redmi go bootloader (as instructed here in xda forum in this redmi go section , - simply doing it by going to fastboot mode and typing a few words to cmd window through adb - meaning that can ignore any official long time-consuiming instructions that are actually obselete or doesn't work without possible bugs on the way for this particular device, as I tried).
Here are official stock roms: https://en.miui.com/download-365.html or search "go" here https://en.miui.com/download.html
This is the procedure (from official Magisk installation guide, source here https://topjohnwu.github.io/Magisk/install.html ):
Boot Image Patching
This is the “cool” way to install Magisk on your device. Either your device does not have proper custom recoveries, your device is using the A/B partition scheme and you don’t want to mix recovery and boot images together, or you have other concerns (e.g. OTA Installation), you should use this method instead.
In order to use this method, you are required to obtain a copy of the stock boot image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, someone on the Internet might share it somewhere. The following instructions will guide you through the process after you have the copy of boot image.
Copy the boot image to your device
Download and install the latest Magisk Manager
Press Install → Install → Select and Patch a File, and select your stock boot image file
Magisk Manager will install Magisk to your boot image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched boot image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot image to your device and reboot. Here is the command if using fastboot on most devices:
fastboot flash boot /path/to/magisk_patched.img
-----------------
Here's some slightly longer guide: https://c.mi.com/thread-1444861-1-0.html
Here is if you want to know how to easily restore stock rom (like in case of flashing boot.img that doesn't match with the rest of the rom like I did getting stuck at booting up, or you simply don't have stock rom currently for whatever reason, like having already updated through OTA).
https://www.foldertips.com/en/unbrick-all-xiaomi-snapdragon/
And after installing XiaoMiFlash and before flashing, have to reboot computer as well which was not said in the above instruction.
I would have made separate thread on how to root Redmi Go, here in this forum section, as it is obviously most secure way to rooting Redmi Go (secure, as for using official/legit tools instead of potentially installing something shady somebody has altered in ways of unfavorable to you, as well as secure that it is not really possible to hard brick it even if not following instructions properly) but I don't have enough posts in this forum to make thread here in this section so whatever.
Click to expand...
Click to collapse
Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry

a rdz said:
Hi, I have a doubt. My phone has the update of May 1, so I decided to do it root. Now unlock the bootloader, install twrp and flash magisk. the apps recognize me as root and everything is normal, so I did the right thing? or am I at risk of a problem? sorry for the question, what happens to understand your comment I had to translate in google and really only understood 80%, do not finish understanding why you had problems with your computer. could you help me? I already worry
Click to expand...
Click to collapse
I didn't use twrp at all.
I used Miflash instead of twrp as I told above, in order to restore previous state of the device.
If you did update, as one of the ways I see then, is to replace it with stock rom from which you are going to take the boot image from, to patch with magisk. Do no update. Root first. I have not updated so I don't know how the updating after rooting is going to work. No twrp needed if you just want root.
---------- Post added at 10:58 AM ---------- Previous post was at 10:07 AM ----------
There's slightly different address now: http://c.mi.com/oc/miuidownload/index. Going mi.com or https://en.miui.com/ and clicking downloads if doesn't get there.

RafiAhmed said:
If you're reading this, you must've messed up with your device or you don't want to use custom ROMs anymore and want to revert back to stock ROM.
Going back to stock ROM is not easy on Redmi Go as Xiaomi is not providing the right ROM files. The one (Version: V10.2.6.0.OCLMIXM) that is available on their ROM download site is not flashable on Mi Flash Tool or via fastboot. It will give you an error.
But, there is a way!
Follow the steps below and you can surely get back to stock ROM. (At least it worked for me every time)
CAUTION! Please proceed at your own risk. You are solely responsible for what you're doing. I will not be responsible for any kind of damage to your device.
Requirements
- Unlocked Bootloader
- Xiaomi USB drivers installed on your PC
- PC/TWRP
- microSD Card
- Minimal ADB & Fastboot (If using PC)
- V10.2.6.0.OCLMIXM ROM zip file (Download here
-V10.2.7.0.OCLMIXM (Download here
At first, unzip the V10.2.6.0.OCLMIXM zip file. You will find a folder named images. Open it and look for "recovery.img". Copy it to a safe place (you will need it later).
Then, copy the V10.2.7.0.OCLMIXM zip file to your sd card.
Steps, if you're using PC
1. Install Minimal ADB & Fastboot (Download here)
2. Copy the "recovery.img" file that you extracted earlier, to the directory where your "Minimal Adb & Fastboot" is installed.
3. Run "cmd-here" and type fastboot flash recovery recovery.img
4. Turn on recovery mode on your device by pressing and holding Volume+ and power button together.
5. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Steps, if you're using TWRP
1. Copy the "recovery.img" file that you extracted earlier, to your SD Card.
2. Boot TWRP
3. Select Install
4. Select Install Image
5. Locate the "recovery.img" file in your SD Card and install it.
6. Go back to main menu and reboot into recovery.
7. Once you see a "No command" screen, hold power button and press volume+ button and you should be on the recovery menu.
6. Select apply update from SD Card and locate the V10.2.7.0.OCLMIXM file.
7. Select "Yes"
8. Reboot system.
Your device should now be running clean stock ROM and recovery.
Don't forget to hit Thanks Button if you found this useful.
Click to expand...
Click to collapse
Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update?
edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader.

Request for miui custom ROM for Redmi go
Can anyone built new miui custom ROM port for e
Redmi go:good:

Like it, thank you

matador84 said:
Note that there is a newer version: 10.2.12 ?
V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/
Click to expand...
Click to collapse

fmcgorenc said:
Thank you, this really saved me. A couple of days ago the hotspot stopped working properly after a security update (September 1, 2019). My computer would connect to my phone but it would say "No Internet, Secured". USB tethering also didn't work. I tried restoring to factory defaults, didn't help. So I figured I need to reflash it. The app used to unlock the bootloader didn't work, had to do it manually. The app used for flashing also didn't work, tried a manual approach - almost bricked the phone. Then I found this and it totally worked, thank you. PS: Now after the reflash it shows there's an update available with the size of 183,7MB. How safe is it to update this, since the original firmware(V10.2.9.0.ocleuxm) got screwed up by a security update?
edit: I have installed both updates 10.2.13.0.oclmixm and 10.2.14.0.oclmixm. It's working great. And locked the bootloader.
Click to expand...
Click to collapse
Glad to know that it helped you. And yes, you can update every time after restoring by using this method. It actually takes you to 100% stock condition.

JonnyTech said:
matador84 said:
Note that there is a newer version: 10.2.12 ?
V10.2.13.0.OCLMIXM - https://mirom.ezbox.idv.tw/en/phone/tiare/
Click to expand...
Click to collapse
The one I mentioned is targeted to take the phone back to the state it was in, after you purchased it.
Click to expand...
Click to collapse

Failed to installing
while applying update from sd card it's failing to install. Anything can i do?
plz help if there is any idea

How out of date this guide really is?

dustojnikhummer said:
How out of date this guide really is?
Click to expand...
Click to collapse
It still works.

Hakhim said:
while applying update from sd card it's failing to install. Anything can i do?
plz help if there is any idea
Click to expand...
Click to collapse
I'm sorry, I might've been busy or didn't notice when you posted this. Did you manage to fix it?

Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP

Sid160706 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Guys, download the Firmware from here. And if you have TWRP installed, just flash this. If TWRP is not installed, try using fastboot and boot to TWRP
Click to expand...
Click to collapse
this worked perfectly. i cleared system, dalvik, cache, data in twrp, then flashed latest V10.2.25.0.OCLMIXM, phone rebooted and showed encryption unsuccessful, i clicked on erase everything then it encryted and booted successfully.

Stuck at fastboot mode..

Idk if I searched longg enough. But I didn't see it yet. Is there any way to go back to stock when stuck at fastboot mode. Is there a firmware flash all bat ... I cannot get to recovery, I cannot boot in OS. Doesn't matter what I do. But I do know I need to see how fastboot flash the stock firmware.
If anyone has a clue or some info it would be GREATLY APPRECIATED!

Look for ADB sideload...

In fastboot? I didn't think you could do anything with adb in fastboot mode?

So if you are in fastboot mode this means you should still be able to fast boot flash.
When in fastboot don't select anything (on the screen with the option to start your phone), plug your phone into your computer and move (cd) to your platform tools folder. Open a terminal or ADMINISTRATOR powershell at this location.
You will need to download the TWRP fastboot image from on of the ROM threads below, it doesn't matter which one you get they both work. It may be easier to download the IMG from the unofficial twrp thread because there is a download link on the front page.
Now you want to run sudo fastboot flash boot twrp.img if you are using terminal or .\fastboot flash boot twrp.img if you are using powershell.
After that completes you should now select recovery mode on your screen and you SHOULD boot into twrp. My advice (it worked best for me) is in twrp complete wipe your phone then get the new TWRP installer zip and flash that. Then reboot to recovery and flash the stock ROM you download from asus.
Everything should work fine, feel free to ask me if you need more clarification. (Obligatory not responsible for bricks)

@Grom8 thank you for your detailed response. But I have tried multiple time to boot twrp. But it won't allow me to just goes right back to fastboot.. I will try to flash the official twrp tomorrow. My theory is that the partitions are messed up and won't allow me to do anything until they are sorted out. But I really don't know lol.

I had the same problem, try flashing the stock boot and system.img, then boot into twrp again

0Null0 said:
I had the same problem, try flashing the stock boot and system.img, then boot into twrp again
Click to expand...
Click to collapse
I will try tonight after work. Thank you

Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol

This was my solution
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
st3wart said:
Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol
Click to expand...
Click to collapse
i posted how i fixed mine in detail

My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?

dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
Click to expand...
Click to collapse
Thank you so much! I thought I just bricked my new phone.

st3wart said:
My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?
Click to expand...
Click to collapse
My phone shows up as "Qualcomm HS-USB QDLoader 9008" in the device manager, which I think means it is stuck in edl mode similar to your situation?
Did you manage to find a fix for that?

Nope not yet. Still looking and waiting to see if anyone has a fix.

st3wart said:
Nope not yet. Still looking and waiting to see if anyone has a fix.
Click to expand...
Click to collapse
I've found this thread: /zenfone-6-2019/how-to/qdloader-brick-t3980165
But as I am a complete noob, I don't know whether I should just run a script, of which I have no understanding of what it does.
Don't even know for sure if it could fix the issue.

Thanks man I'll check it out when home from work. I'll shoot you an update if I can get it fixed!

Yes yes YES! It fixed the phone and brought it back to life!!!! Amazing ...thank you thank you thank you.
Follow the instructions as he put them. Works like a charm!

Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?

Hello dperez2010,
your method seems to work, but i get the following error
fastboot flash system_a system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/5 (773136 KB) OKAY [ 17.209s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Do you or does anyone know whats going on here?

/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Here's a hint

file size too big, can't flash or boot Into TWRP
dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
i posted how i fixed mine in detail
Click to expand...
Click to collapse
"file size", basically our system.img is not being downloaded by the phone due to the large (3.6G) filesize
"fastboot flash system_a ./system.img
Sending 'system_a' (3670016 KB) FAILED (remote: 'requested download size Is more then the max allowed')
feastboot error: command failed