Develop Bugs

[Q] Bricked and can't get into download mode.

I have a rooted Sprint G2 and got the notification to update to KitKat, but when I did it restarted and said:
Code:
[15209250] -- reset --
[15209260] -- portcharge --
[15209320] fastboot: processing commands
[15367550] -- reset --
[15367550] EP1/out FAIL nfo=40 pg0=f913600
[15367560] -- reset --
[15367560] -- portcharge --
[15367570] usb_read() trasaction failed
[15367630] fastboot: oops!
[15372860] -- reset --
[15372870] -- portcharge --
And it does this every time I plug it into the computer. I also can't access download mode. I've looked through many tutorials but haven't found success with any of them yet. Am I at a point of no return or is there hope? Any help is greatly appreciated. Thanks!

try a different port on your computer then do (also make sure you have all the drivers installed on computer) (also make sure you have adb and fastboot installed
http://forum.xda-developers.com/showthread.php?t=2477595
(make sure you use sprint files though)

gpitner said:
I also can't access download mode.
Click to expand...
Click to collapse
This is his biggest issue
jcwxguy said:
try a different port on your computer then do (also make sure you have all the drivers installed on computer) (also make sure you have adb and fastboot installed
http://forum.xda-developers.com/showthread.php?t=2477595
(make sure you use sprint files though)
Click to expand...
Click to collapse
so this is useless if he can't even access Download mode to use the flashtool
OP can you access twrp? if you can you can flash this file http://www.rwilco12.com/Files/Garwynn%20Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip (Thank @garwynn for this if this works) and you should have download mode back if not then you are beyond my knowledge and will need help from a more knowledgeable person

No unfortunately I can't. The same, or very similar thing happened two weeks ago when I was trying to flash TWRP but after the phone ran out of battery and I plugged it back in, it turned on no problem. That didn't happen this time though, so I'm really stuck.

I thought I was bricked also and couldn't get into download mode. This is how I was able to use the flash tool. Vol down and power to get into recovery. You should get an error. Then power off the phone completely. Plug into usb to connect to computer. Then vol up and power for download mode. Make sure you have already installed the driver.
Hope this helps.

kleen3r said:
I thought I was bricked also and couldn't get into download mode. This is how I was able to use the flash tool. Vol down and power to get into recovery. You should get an error. Then power off the phone completely. Plug into usb to connect to computer. Then vol up and power for download mode. Make sure you have already installed the driver.
Hope this helps.
Click to expand...
Click to collapse
I just tried your method and it keeps going back to the same screen. I forgot to mention that I only get those lines of code when I plug my phone into the computer, but when my phone restarts the only code present is:
Code:
[470] Fastboot mode started
[520] udc_start()

Jbcarrera said:
This is his biggest issue
so this is useless if he can't even access Download mode to use the flashtool
Click to expand...
Click to collapse
the point of that thread is to flash the laf partition using fastboot, (which is download mode).
here is a laf.img
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/laf.img
(might also need to flash the boot.img
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/boot.img
*in cmd prompt, go to the folder where you have fastboot (copy both laf.img and boot.img to same folder), then do fastboot flash laf.img and fastboot flash boot.img.
( cd C:\Program Files (x86)\Minimal ADB and Fastboot ) (just an example)
once flashed, you should be able to get into download mode.
Ive had the exact screen you have had before, and this is what i had to do to get download mode to work.
gpitner said:
I just tried your method and it keeps going back to the same screen. I forgot to mention that I only get those lines of code when I plug my phone into the computer, but when my phone restarts the only code present is:
Code:
[470] Fastboot mode started
[520] udc_start()
Click to expand...
Click to collapse

I have to have Android SDK tools installed right?

Yes, you will need the SDK tools installed.
Just wanted to point out something real quick here, I see up a couple posts back, you pushed the power button for D/L mode but you do not hit the power button at all to get into D/L mode, you only need to hold VOL+ and plug the USB into the computer, this starts download mode. Once you get D/L mode back.
I had a very similar problem, when I flashed D801 rom on my LS980, I believe what I did was, to flash .boot as jcwxguy suggested but I think I also flashed .recovery both in fastboot mode with ADB and that brought back my D/L mode, here is a guide, http://forum.xda-developers.com/showthread.php?t=2131284 , go to FLASHING YOUR FILES IN FASTBOOT. best of luck!

So i flashed both files, thank you by the way, and they both flashed just fine but I still can't get into download mode. Here's the corresponding output on the phone and also what command prompt showed.
Code:
[5376060] fastboot: getvar:partition-type:laf
[5376180] fastboot: getvar:max-download-size
[5376440] fastboot: download:00f00000
[5376980] fastboot: flash:laf
[5377030] partition_get_size 33554432 bytes
[5416180] fastboot: getvar:partition-type:boot
[5416280] fastboot: getvar:max-download-size
[5416490] fastboot: download:00a00000
[5416870] fastboot: flash:boot
[5416930] partition_get_size 16777216 bytes
{
"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"
}

same procedure, flash the recovery partition, http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions/recovery.img

So I have myself a little conundrum. The phone's battery is dead so when it charges enough to turn on and install the update it dies halfway through the installation. Is there anyway to keep it from installing the update so it can charge enough?

Man, wish I could help out here but not sure about that one, maybe someone more knowledgeable out there knows a way out of this?

Nevermind, I was able to use a charger at my university that has a higher voltage output for quicker charging and it worked. My phone is fully functional. Thank you too everybody who helped and provided the appropriate files, you have no idea how happy I am!

cool, glad to hear you got it worked out. Congrats :good:

Fastbooting android whose recovery is not opening.

While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"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"
}

akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.

vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?

akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.

Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader

akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.

Stuck on fastboot mode ? Check this how easy is this.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, so i was working on my p1 and acidently flash wrong file and my huawei doesnt boot so i can go only on huawei fastboot so what i do ? its easy i think the huawei update pack with do something so start downloading it and put on sd card and i try to flash but what ? its say something error i try all the flash from huawei support no one from them doesnt work on my case so i decide to make some fastboot easy commands. But for you guys i decide to make it more easy so i put all my things on one program so everyone can work with it.The firmware i used to recover or better to say the base of this room is B194 and is Stock Rom nothing modified.
Must have adb or fastbooot installed on you pc if not my program offer you to install.
The pc must know your device you have a button check on my device (in my program if is there you device than you have good chance).
A cable .
And Brain most important.
https://mega.nz/#!JA8hXKha!YAm7sDVvaX1V5zgpRX19yvSjUy_n31j0NBhA_5uQBbQ
And this problem fix issue like mine if your device dont boot, if your device dont take stock rooms from sd card, if your device stay only on fastboot mode.

I think I have no brain.
Let me explain my case first.
Somehow my phone got bricked, it was never rooted or installed a custom room or install a recovery cwm.
I tried installing the stock firmwares from Venezuela carrier, and 2 General Firmwares (with volume up + power [sd/dload] and there was an error.
So now I try your method (Volume down+power) and then your program, I think it reconize the device and it appears there was no error in the install, but when I turn off and turn on the phone is still bricked (stuck only in huawei logo).
What should I do?
Sorry for my poor english...

onlykhaz said:
I think I have no brain.
Let me explain my case first.
Somehow my phone got bricked, it was never rooted or installed a custom room or install a recovery cwm.
I tried installing the stock firmwares from Venezuela carrier, and 2 General Firmwares (with volume up + power [sd/dload] and there was an error.
So now I try your method (Volume down+power) and then your program, I think it reconize the device and it appears there was no error in the install, but when I turn off and turn on the phone is still bricked (stuck only in huawei logo).
What should I do?
Sorry for my poor english...
Click to expand...
Click to collapse
ohhh is easy if you can go on fastboot mode my friend dont worry sory about that pm i mistake with phones hahah.
here i help you just follow what i say here :
1.) go on fastboot mode (volume down + power)
2.) install this recovery is a twrp recovery ( http://www.ucagg.com/twrp-2.8.6.0-diart(UCA).zip )
** you can install it by cmd first of all extract the twrp from the zip file than click with shift+left mouse on that folder that you extracted and open the command windows and than you must type : "fastboot devices" if your device is there like this : "P1ASCEND fastboot" than you are ready to go than you must write : "fastboot flash recovery recovery.img" and uala now you have twrp installed so continue on next step.
3.) Download this stock rom : (http://d-h.st/rOX)
4.) If you want gapps you can find here (https://mega.nz/#!MZATDQBA!LwuWQEBOIgFIwRJPUF_OLRVPruN6KgAwMGveuB1_Ql4)
and you are done my friend
ps ( office link for this rom is here : http://forum.xda-developers.com/showthread.php?t=2744342 )
and sory i wasnt here so here i am a little late but here lol i hope i help you if you have any problem tell me , i am here to help you

diart said:
ohhh is easy if you can go on fastboot mode my friend dont worry sory about that pm i mistake with phones hahah.
here i help you just follow what i say here :
1.) go on fastboot mode (volume down + power)
2.) install this recovery is a twrp recovery ( http://www.ucagg.com/twrp-2.8.6.0-diart(UCA).zip )
** you can install it by cmd first of all extract the twrp from the zip file than click with shift+left mouse on that folder that you extracted and open the command windows and than you must type : "fastboot devices" if your device is there like this : "P1ASCEND fastboot" than you are ready to go than you must write : "fastboot flash recovery recovery.img" and uala now you have twrp installed so continue on next step.
3.) Download this stock rom : (http://d-h.st/rOX)
4.) If you want gapps you can find here (https://mega.nz/#!MZATDQBA!LwuWQEBOIgFIwRJPUF_OLRVPruN6KgAwMGveuB1_Ql4)
and you are done my friend
ps ( office link for this rom is here : http://forum.xda-developers.com/showthread.php?t=2744342 )
and sory i wasnt here so here i am a little late but here lol i hope i help you if you have any problem tell me , i am here to help you
Click to expand...
Click to collapse
Hi!
Dude, when I typed <fastbot devices> it shows this "? fastboot" the thing I had to do was, I extract from a official stock room some img and did a cople of erase like, fastboot erase system and then I flash them. Now the phone is working properly. I will try that room you recommended. THANKS Man :good: I really appreciated the respond.
Peace.

onlykhaz said:
Hi!
Dude, when I typed <fastbot devices> it shows this "? fastboot" the thing I had to do was, I extract from a official stock room some img and did a cople of erase like, fastboot erase system and then I flash them. Now the phone is working properly. I will try that room you recommended. THANKS Man :good: I really appreciated the respond.
Peace.
Click to expand...
Click to collapse
dont worry my friend i am here to help you , i am so happy that you fix that one and have a nice day everytime if you need something you can ask me , i can help you with anything if i can my friend bye :highfive:

onlykhaz said:
Hi!
Dude, when I typed <fastbot devices> it shows this "? fastboot" the thing I had to do was, I extract from a official stock room some img and did a cople of erase like, fastboot erase system and then I flash them. Now the phone is working properly. I will try that room you recommended. THANKS Man :good: I really appreciated the respond.
Peace.
Click to expand...
Click to collapse
hello same problems same phone from same country, what official stock room did you used, i also get the "? fastboot" but i cant flash any recovery ive tried from there =(

.Let'go

...
diart said:
dont worry my friend i am here to help you , i am so happy that you fix that one and have a nice day everytime if you need something you can ask me , i can help you with anything if i can my friend bye :highfive:
Click to expand...
Click to collapse
i try that too. but it say FAILED (remote: Command not allowed) would you help me

Flashed wrong kernel by mistake

Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.

Ow and a bit more info, i can get into bootloader and recovery.

go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img

Tried that but it won't see my device.

It doesn't apear in my devices.

go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot

ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...

install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1

SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?

This is wat happens with HTC installer.

go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"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"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.

Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...

SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.

Device manager sees the HOX now too.

go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know

Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..

go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?

SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521

go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358

SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.

Help "failed to write partition" error Redmi 5A (riva)

I had installed in this phone a custom rom a few months back for my friend. Yesterday he told me that the device froze when he was browsing the phone gallery app, and a few minutes later the phone rebooted and couldn't pass the mi logo (so the system wasn't loading I guessed, because the logo of the ROM wasn't showing). I tried to enter TWRP, but even there the phone would get stuck on the TWRP splash page and rebooted back to the MI logo. So I tried to reinstall TWRP (I have still access to fastboot mode) and, after, a newer version, but the problem was the same. I tried booting a recovery image without installing it (fastboot boot twrp.img) and the problem was similar, but instead of rebooting to the MI logo, the phone would get stuck on the TWRP logo. I tried with OrangeFox recovery too, but same problem. I read in another post that it may be a problem with the /data partition, so I (fastboot erase userdata) and tried again the above recovery installation, but it didn't work. I, then, tried to wipe all partion via fastboot, and tried the command "fastboot erase system -w", but it didn't work either. So I tried the way to restore the phone with MiFlash tool, I found the firmware I needed, I flashed it, and after ~4s it gave me the error "failed to write partiton" (see image).
Spoiler: Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried with another firmware (this time based on Oreo instead of Nougat), same error. I searched a solution for this error, but I found nothing helpful. Now I have the phone working (=it can power on) and can access to fastboot, but don't know what to do. Can someone out there, with maybe a clearer idea of what's going on, help me? Thanks in advance

Update:
I found out that the problem is flashing this file "gpt_both0.bin" (which is the partition table). Every firmware that I tried failed to flash when trying to fastboot this file. So I tried to remove the line (
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash tz error" && exit /B 1
) from the flash_all.bat and everything was flashed without errors, but the phone won't start, so this file is necessary. Flashing it separately gave me the same error (failed to write partition). So, I ask again for help, hoping that someone will come to save me

I have same issue. Did you get any working method?

amitkr.xda said:
I have same issue. Did you get any working method?
Click to expand...
Click to collapse
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work

TheMagicWafer said:
No, I'm still getting the error and trying to test all that comes to my mind. Maybe one day something will work
Click to expand...
Click to collapse
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool

amitkr.xda said:
Does your phone go in fastboot? Mine doesn't, but is recognised as QHSBULK 9008, also it's not recognised in adb devices or mi tool
Click to expand...
Click to collapse
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar

TheMagicWafer said:
Yes, my phone goes into fastboot. The name QHSBULK 9008 sounds like the phone goes in edl mode. I'm not sure, but searching around I found out it's the name of the phone when it's recognised as by it's qualcomm drivers, or something similar
Click to expand...
Click to collapse
How can I boot in fastboot? It's not going in fastboot or anything

amitkr.xda said:
How can I boot in fastboot? It's not going in fastboot or anything
Click to expand...
Click to collapse
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo

TheMagicWafer said:
Only (hardware) method possible is to hold the power button and the volume down(-) button simultaneously and wait for the fastboot screen/logo
Click to expand...
Click to collapse
Nothing works, it's just blank screen, no vibrate, no logo nothing

amitkr.xda said:
Nothing works, it's just blank screen, no vibrate, no logo nothing
Click to expand...
Click to collapse
I'm sorry, but I'm not an expert and I can't help you any further. If one day I find a solution, be sure I'm going to write it here

have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died

Avisadius said:
have u try Miui Nougat Global with clean all and lock option? if yes, looks like your emmc has died
Click to expand...
Click to collapse
Already tried, and it gave me the same error. I really hope it's not a motherboard issue, because a replacement is not worth it. Thanks anyway