Hai, view days ago i got bricked my phone, after i got replacement from distributor service center, this incident was started while my cell phone always hang randomly, then the bad things happened, my phone is no longer boot up, can't access twrp too,
I tried many trick to make my cell phone wake up but nothing happens,
I tried to flash with miflash (fastboot) with option clean all or clean and lock, it says error remote erase/write partition failed
I tried to flash with QFIL Download Qualcomm Flash Image Loader failed
Can't flash with command fastboot, all write failed
I tried with oem edl got error ACK Count don't match
I tried deep cable flash failed
I tried the last option with test point also failed
all also write/erase failed,
what i supposed to do to fix my phone
did you solve the problem? I guess i had the same...
Related
On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks
We are in the same boat buddy, the same thing happened to the phone of my wife.
It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers
I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.
I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.
I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.
Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.
I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.
I was using my mi a2 and it randomly freezed, then i restarted using power button, but he didn't turned on, now it is just black screen and i can't get into bootloader mode or turn the phone on.
Bootloader was locked, never tried to unlock.
I think it got stuck on EDL mode because it shows up 'qualcomm hs-usb qdloader 9008' on device manager on windows.
Already tried to use mi flash tool to flash the last ROM, it recognize the phone but fails every time.
Neither adb or fastboot recognizes the phone.
Some errors that i had using the tool:
Failed to open the SDCC Device slot 0 partition 0 (it shows up only on version 2019.11.15.0)
Cannot receive hello packet (when i get this error, i hold the power button for a few seconds then i try again only to get the error below)
Error when flashing storsec.mbn
Can someone help me?
UPDATE
I downloaded mi flash tool 2016.08.30.0 and i can successfuly flash the rom, but still got black screen with no response.
I ve little same issue. need help too.
I have Mi A2 runnig on android8.1
but it didnt update 9.0
so I try with twrp but fail no boot anymore.
I use miFlash tool. accdently I locked phone. flashed rom didnt boot.
now I ve just fastboot mode. or open 'android one' screen and then goes black.
I try EDL mode by test point inside phone.
flash with 2018 mi Flash tool but stuck in flashing...
flash with 2016 mi Flash tool write succesful flashed afte 6min. but not boot.
I read 2 days on forums. cant find anything to do.
is there any solution?
thanks
Hi, has anyone made any progress?
Theduardds said:
I was using my mi a2 and it randomly freezed, then i restarted using power button, but he didn't turned on, now it is just black screen and i can't get into bootloader mode or turn the phone on.
Bootloader was locked, never tried to unlock.
I think it got stuck on EDL mode because it shows up 'qualcomm hs-usb qdloader 9008' on device manager on windows.
Already tried to use mi flash tool to flash the last ROM, it recognize the phone but fails every time.
Neither adb or fastboot recognizes the phone.
Some errors that i had using the tool:
Failed to open the SDCC Device slot 0 partition 0 (it shows up only on version 2019.11.15.0)
Cannot receive hello packet (when i get this error, i hold the power button for a few seconds then i try again only to get the error below)
Error when flashing storsec.mbn
Can someone help me?
UPDATE
I downloaded mi flash tool 2016.08.30.0 and i can successfuly flash the rom, but still got black screen with no response.
Click to expand...
Click to collapse
A year ago i had the same issue kinda. The only thing that worked for me was flashing mi 6x stock rom and after some trial an error it flashed and it fixed. The only problem is i have a mi 6x forever. Basically download mi 6x stock rom. Try that mi flash tool and keep hard rebooting and click flash button right after it vibrates. If lucky sometime will work and flash. If nothing try older versions of mi flash tool. Good luck.
all of you have the same problem ... you bootloop into edl mode because you have ARB4 triggered ..that means the only stock you can flash in miflash is ARB4 rom ( latest most up to date )
you also need patched programmer file since flashing ARB4 requires miui account
the fix to this problem is documented everywhere and explained lots of times ...just read ..follow this guide and one-click tool to unbrick
next time read ......a little ..
https://miui.blog/mi-6x/unbrick-mi-6x-wayne/
Hello! My phone became bricked out of nowhere and i have no idea how to get it to boot again. I am not sure what exactly could have caused it, it happened when i unlocked my phone in the morning and the phone shut off when i touched the screen, it tried to reboot for some time then it went straight into fastboot and i have tried everything i could to get it out but i didn't succeed. The phone responds to some fastboot commands, unless they involve writing, in which case it either returns: "command write failed (no error)" or gets stuck at the writing phase and does nothing. I tried QFIL and MiFlash and both failed as well (MiFlash also reads different physical memory usage in every log), i will include screenshots for refference.
Or is there any chance that the issue is caused by the flash? The phone is around 2 months old so i could try and get it repaired. The phone was running Resurrection Remix 8.6.9 with Englezos kernel and Magisk. It is the first time i faced such a severe issue so if there is any information i left out, feel free to point it out and i'll provide what i can.
Thanks in advance for any help!
Hi, same goes happened to my 9T, ive tried so many flash toos but didn't works,
Last flasher i tried is xiaomi flash tools but its required user id and password account that only available for service center.
Finally i sent my phone over, that is the best option
Hi i have a model XT1921-5. It got stuck in the logo screen and couldnt boot into recovery so i tried a rescue with the RSA, it detected the phone in fastboot and found the firmware but failed flashing it. Now it only boots into fastboot.
When flashing the firmware manually only gpt.bin fails but the phone is still stuck in fastboot (failed to validate hab image - failed to validate boot image. same with recovery image). I tried everything i could but nothing worked out.
I think my only "chance" is to try a blankflash. The problem is that my bootloader is locked (never unlocked) so i cant do fastboot oem edl, i cant find anything about test points for this model.. So im looking for a way to maybe hard brick the phone to force it boot into EDL mode and try the blankflash. Unless there's a way to set the OEM unlock option via fastboot..
I appreciate any help.
Thanks in advance.
I was able to put my phone on QDL mode via test point.
Now i tried to flash the blankflash but it throws the error "XML (0 bytes) not validated"..
Does anyone knows what this error means? If is a version mismatch then i cant find a newer version of this blankflash..
Any help is always appreciated.
For anyone interested this is the test point you need to short to boot into QDL mode