Database Develop

Brick - No OS, Recovery and fastboot problems

Hey Guys, I was wondering if any of you could help me with this....
Background - My HTC One was having issues with the touchscreen, and I was going to hand it in to EE to get it repaired tomorrow. But *naturally* I need to restore it to stock settings first...
What did I do?
1) Installed a ZIP file with the stock recovery/ROM via an AROMA installer from TWRP
2) Tried to relock bootloader, succeeded, but somewhere something went wrong and my ROM got corrupted
3) managed to re-install TWRP via fastboot, but I couldn't get system to mount so I couldn't install any ROM at all
4) Used fastboot to try to wipe system and reformat it, didn't work
5) Managed to remove the tampered flag (still S-OFF at this point though) so my plan was to S-ON and then give it to HTC being all "durr it no werk" and get them to sort everything out on it
6) S-ON'd the phone, only to have the tampered flag appear at this point, so I can't hand it back in and protest my innocence anymore
7) Can no longer S-OFF, install any ROM because I get a remote: signature invalid error for any stock ROM or recovery that I try to install despite my CID being HTC__001 which is the same as the stock ROM I'm trying to push via fastboot
8) Can no longer get into TWRP either
Bottom line - phone is S-ON, bootloader is locked (and won't accept my Unlock_code.bin), tampered flag is on, fastboot won't let me install anything because of a file signature error, No operating system, no working recovery.
If you can help me in any way at all, I'd be eternally grateful!
Dropbox link to potato-cam photos

Da Vikster said:
Hey Guys, I was wondering if any of you could help me with this....
Background - My HTC One was having issues with the touchscreen, and I was going to hand it in to EE to get it repaired tomorrow. But *naturally* I need to restore it to stock settings first...
What did I do?
1) Installed a ZIP file with the stock recovery/ROM via an AROMA installer from TWRP
2) Tried to relock bootloader, succeeded, but somewhere something went wrong and my ROM got corrupted
3) managed to re-install TWRP via fastboot, but I couldn't get system to mount so I couldn't install any ROM at all
4) Used fastboot to try to wipe system and reformat it, didn't work
5) Managed to remove the tampered flag (still S-OFF at this point though) so my plan was to S-ON and then give it to HTC being all "durr it no werk" and get them to sort everything out on it
6) S-ON'd the phone, only to have the tampered flag appear at this point, so I can't hand it back in and protest my innocence anymore
7) Can no longer S-OFF, install any ROM because I get a remote: signature invalid error for any stock ROM or recovery that I try to install despite my CID being HTC__001 which is the same as the stock ROM I'm trying to push via fastboot
8) Can no longer get into TWRP either
Bottom line - phone is S-ON, bootloader is locked (and won't accept my Unlock_code.bin), tampered flag is on, fastboot won't let me install anything because of a file signature error, No operating system, no working recovery.
If you can help me in any way at all, I'd be eternally grateful!
Dropbox link to potato-cam photos
Click to expand...
Click to collapse
The correct steps to Getting back to stock are here >> http://forum.xda-developers.com/showthread.php?t=2541082

Sunshine Soff...

I can't use either of those because I don't have a working OS and I can't flash one via bootloader because of a file signature verification error

Da Vikster said:
I can't use either of those because I don't have a working OS and I can't flash one via bootloader because of a file signature verification error
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
can you post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
{
"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"
}
here you go

Da Vikster said:
here you go
Click to expand...
Click to collapse
Since you are now S-ON and LOCKED, you need to use signed RUU
for PN0710000 + HTC__001, try this one:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://androidruu.com/getdownload.p...31.27_10.31.1131.05_release_310878_signed.exe
remember to check MD5 of the download to make sure it's not corrupt
let me know how that goes
oh, and charge your battery

writing 'recovery' FAILED (remote: command not allowed)

Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do:
Code:
fastboot flash recovery twrp.zip
It returns me
Code:
writing 'recovery'...
FAILED (remote: Command not allowed)
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)

Akioru said:
Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do:
Code:
fastboot flash recovery twrp.zip
It returns me
Code:
writing 'recovery'...
FAILED (remote: Command not allowed)
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Click to expand...
Click to collapse
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped

ConradP said:
It returns me
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped
Click to expand...
Click to collapse
Oh, thanks. Im gonna try

ConradP said:
Hm.
I think I know
fastboot flash recovery twrp.zip not zip but img, and the recovery in ADB folder needs to be img not zipped
Click to expand...
Click to collapse
Doesn't work, here's a screen of my cmd
{
"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"
}

Akioru said:
Hi o/
Since I have formatted the system of my NEM-L51, I re-installed the stock rom at the last version, but it appears that I have to reinstall TWRP and re-root my phone. But when I do: It returns me
My bootloader is unlocked.
Any solution?
(and sorry if my english is bad)
Click to expand...
Click to collapse
Just unlock ur bootloader again, and it will work.

also you should run cmd as admin, it might help

Shubho20 said:
Just unlock ur bootloader again, and it will work.
Click to expand...
Click to collapse
Doesn't work, i still have the failed (remote: command not allowed

Akioru said:
Doesn't work, i still have the failed (remote: command not allowed
Click to expand...
Click to collapse
Have u enabled oem unlock in developers settings?

thelous said:
also you should run cmd as admin, it might help
Click to expand...
Click to collapse
Doesn't work

Maybe my experience can help : https://forum.xda-developers.com/showpost.php?p=71730671&postcount=106

romroro said:
Maybe my experience can help : https://forum.xda-developers.com/showpost.php?p=71730671&postcount=106
Click to expand...
Click to collapse
So if I understood well, I should put the recovery image into the dload folder?

Akioru said:
So if I understood well, I should put the recovery image into the dload folder?
Click to expand...
Click to collapse
No, you need to put update.app in dload folder. Also have you installed the hi suite app on your computer/laptop? It contains the drivers you need to communicate with your device. I think this might solve your error message when tying to use adb or fastboot.
Sent from my NEM-L51 using XDA Labs

iantechie1979 said:
No, you need to put update.app in dload folder. Also have you installed the hi suite app on your computer/laptop? It contains the drivers you need to communicate with your device. I think this might solve your error message when tying to use adb or fastboot.
Click to expand...
Click to collapse
Hisuite is installed but I don't have an uppdate.app file, just a twrp.img

Akioru said:
Hisuite is installed but I don't have an uppdate.app file, just a twrp.img
Click to expand...
Click to collapse
get the .zip file from here
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
and extract it you will have update.app in it .
By the way did you accept permission prompt in the phone when connected to PC? for RSA key?

miststudent2011 said:
get the .zip file from here
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
and extract it you will have update.app in it .
By the way did you accept permission prompt in the phone when connected to PC? for RSA key?
Click to expand...
Click to collapse
But why about the rsa key ?

gopinaidu77 said:
But why about the rsa key ?
Click to expand...
Click to collapse
What is the prompt you get when you connect your device for pc while using ADB?
Its RSA prompt.

miststudent2011 said:
What is the prompt you get when you connect your device for pc while using ADB?
Its RSA prompt.
Click to expand...
Click to collapse
Yeah , but why about it ?

gopinaidu77 said:
Yeah , but why about it ?
Click to expand...
Click to collapse
because if you dont authorize you get remote command not allowed or something like unauthorized error you will get.

Oh my ****ing god, first of all you have to fastboot oem relock 0123456789(your code), and then unlock.

SCUZZY1337 said:
Oh my ****ing god, first of all you have to fastboot oem relock 0123456789(your code), and then unlock.
Click to expand...
Click to collapse
Did he unlocked his bootloader before ?

Soft Brick on HTC One (m7)

Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot

TRenghia said:
Hi everyone,
I have an HTC One (m7), carrier H3G Italy, unlocked, tampered, S-ON, wtih TWRP 3.0 installed. I had CyanogenMod installed (version 12.x). Recently my phone stopped working without any reason and when I tried to reboot it simply didin't work.
Following some guides I found in this site, I tried to flash a new recovery (the update of TWRP) and the stock recovery, I also tried to flash a new ROM with adb sideload, but nothing worked.
Please help me :angel:.
Thank you a lot
Click to expand...
Click to collapse
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...

alray said:
can you please post the output of "fastboot getvar all" (hide your imei and sn)?
What do you mean by "stopped working" and "tried to reboot it simply didn't work"
The phone doesn't boot in the ROM or it doesn't boot at all (i.e not even in bootloader) ?
Please post a link to the rom you are trying to flash and to the twrp version you are using.
Also you don't need to use sideload anymore when using recent twrp version. TWRP now support MTP so you can simply boot in twrp with your phone connected to your computer and you'll see your phone internal storage from your computer (like a usb thumb drive). Simply drag and drop the rom.zip from you computer to your phone then use the "install" menu of twrp to flash it. From my experience, adb sideload isn't always reliable...
Click to expand...
Click to collapse
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
{
"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"
}

TRenghia said:
Hi alray,
Thank you for your help. With "stopped wroking", I mean that the phone doesn't boot in the ROM, and when I said "reboot", I mean just switch off and on. I can boot in the bootloader and the recovery .
Now I am using TWRP version 3.0.0-0 and I'd like to flash this ROM.
Click to expand...
Click to collapse
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot

alray said:
Are you sure your phone wasn't running a newer version than 7.19.771.1? Like maybe 7.19.771.21, 7.19.771.31 or 7.19.771.51? Hard to know since your version-main is blank
Better to edit your version-main to 7.19.771.1 to be 100% sure the RUU will work.
Boot in twrp main menu then open a command window on your computer and type:
Code:
adb shell
echo -ne "7.19.771.1\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
Make sure there is no typo in the long command (copy/paste if needed)
When back in bootloader mode check your version-main is now 7.19.771.1
Code:
fastboot getvar all
Then re-lock your bootloader
Code:
fastboot oem lock
and flash the 7.19.771.1 ruu (make sure the RUU zip file is in the same folder where you have fastboot on your computer. You MUST use the fastboot version linked in the OP of the ruu collection thread to flash the RUU https://androidfilehost.com/?fid=95916177934539737. The "regular" fastboot from the android sdk tool won't work.
Code:
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed.zip
fastboot reboot
Click to expand...
Click to collapse
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got

TRenghia said:
Hi alray,
I've done what you suggested, but I couldn't change my version-main (I copied the command) and, when I tried ti flash the new ROM this is what I got
Click to expand...
Click to collapse
I don't really understand why you jumped to step 3 if step 1 didn't worked... Now that the bootloader is relocked you can't boot in twrp anymore to write the correct version-main (might be problematic). What was the problem when changing the version-main? Why not posting it and waiting for help instead of jumping to step #3?
After doing "fastboot oem rebootRUU" did your phone rebooted in ruu mode (a black screen with silver HTC logo on it)?

Hard reset. What to do now?

So frist i did a usual factory reset and it just went recovery and like what happend before didn't do a clean reset, just apps gone and that's it. So i did it manually by checking all "partitions" including "Cache, Data, Internal Storage, System" and all. Now TWRP is all i got on my phone. I didn't know what i'm doing and it was a noob move, i know. But now i managed to copy a custome ROM (Viper One 9.0.0) to my sdcard via adb push command.
Now all i need is to flash it.
TWRP says "This operaion may install incompatible software and render your device unusable"
Is it safe to do so?
I also wanted to go back to Stock ROM and actually downloaded one from HERE. It's the one provided in METHOD 2 .
The only reason i want to flash Viper One again is that i flashed it before without any problem.
If i make sure that it's safe to flash the Stock ROM i'd do it. Please let me know what should i do. Thanks.

Harry_ei8ht said:
So frist i did a usual factory reset and it just went recovery and like what happend before didn't do a clean reset, just apps gone and that's it. So i did it manually by checking all "partitions" including "Cache, Data, Internal Storage, System" and all. Now TWRP is all i got on my phone. I didn't know what i'm doing and it was a noob move, i know. But now i managed to copy a custome ROM (Viper One 9.0.0) to my sdcard via adb push command.
Now all i need is to flash it.
TWRP says "This operaion may install incompatible software and render your device unusable"
Is it safe to do so?
I also wanted to go back to Stock ROM and actually downloaded one from HERE. It's the one provided in METHOD 2 .
The only reason i want to flash Viper One again is that i flashed it before without any problem.
If i make sure that it's safe to flash the Stock ROM i'd do it. Please let me know what should i do. Thanks.
Click to expand...
Click to collapse
-Post your "fastboot getvar all" output (hide your imei/sn)
-What is your twrp version?

alray said:
-Post your "fastboot getvar all" output (hide your imei/sn)
-What is your twrp version?
Click to expand...
Click to collapse
Here it is sir
{
"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"
}
TWRP is 3.0.2-2
and btw, seems like i can't flash anything with twrp now. keep saying "zip signature failed"!

And please guide me through on how can i go back to stock rom safely.
Of course i can find tons of articles about it but there are few confusions and since it can end in a brick i can't risk it. For example is THIS ONE legit? for flashing RUU, is the one i mentioned above will do it? I mean THIS ONE
or if there's any better guide here (sure there's, i know!) please link it here. Thanks

Harry_ei8ht said:
And please guide me through on how can i go back to stock rom safely.
Of course i can find tons of articles about it but there are few confusions and since it can end in a brick i can't risk it. For example is THIS ONE legit? for flashing RUU, is the one i mentioned above will do it? I mean THIS ONE
or if there's any better guide here (sure there's, i know!) please link it here. Thanks
Click to expand...
Click to collapse
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.

alray said:
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.
Click to expand...
Click to collapse
Thanks a ton, alray. I'll let know you how it goes

alray said:
Linked guide is for M8 and does not apply to your situation.
reflash the stock recovery, relock the bootloader and flash the 7.19.401.51 RUU
Code:
fastboot flash recovery M7_UL_Stock_Recovery_7.19.401.51.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
fastboot reboot
You must use this fastboot version at least for the "fastboot flash zip" command.
Click to expand...
Click to collapse
So it went all good till the "fastboot oem rebootRUU" command. It reboots and then htc logo shows up and nothing after that. I have to reboot it by Power+V- in order to go in bootloader again?
Is something wrong? Or should i run the next command there in bootloader?
P.S: Bootloader is relocked, by the way.

NVM. Just ran the command again and it's working now!

It worked man... AWESOME!!

Alright just one more question. If i ever want to root my device again, it will be ok?
And if you have the time, please link the right thread for it. Your work is much appreciated mate. Thanks a billion!

Harry_ei8ht said:
Alright just one more question. If i ever want to root my device again, it will be ok?
And if you have the time, please link the right thread for it. Your work is much appreciated mate. Thanks a billion!
Click to expand...
Click to collapse
You're welcome
Unlock your bootloader again htcdev.com/bootloader
flash latest TWRP for M7
Flash latest Supersu.zip or Magisk

Brick my MI A2

After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"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"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?

https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188

minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)

Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.

use ./fastboot flashing unlock_critical

Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.

djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.

Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.

djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).

behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.

meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?

Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img

Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.

Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!

people try:
1- Another usb port
2- Another usb cable
3- Another PC

I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs

woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?