Hello Guys!
I was trying to go with a Custom Rom (Cynogen 12.1) on my Xiaomi Mi4i device. Rooted the phone and also installed TWRP recovery. Got everything like Rom Zip file and GApps on the device including a special file recommended for Miui 7 users. Then I tried to flash them after factory resetting from TWRP recovery. The special file (dont know what it is called) was flashed successfully everytime..but when flashing Rom file...it failed showing "Unable to extract zip".
So I tried again..and quite a few times more but it always failed. Therefore, instead of Factory Resetting...I went to Advanced reset...And ended up in SOFT BRICK of the device accidently removing everything.
But this is not the end...I knew how to repair a soft bricked Device. So, I went for MiFlash...But in that...instead of Mi4i fastboot rom...I flashed Mi4 fastboot rom..and this resulted in HARD BRICK of my device. Now, it doesnt show any thing...No notification light when charging...Not entering fastboot mode..nothing.
So, I tried a few ways..to repair my hard bricked device..but none of them worked. When I initially connected it to my PC it showed "Qualcomm HS-USB Diagnostic 9008" in the PORT section of Device Manager and Showed as COM11 in MiFlash...but when flashed it showed error "End of code" or something like this. So, I restarted My PC...But since then WINDOWS is showing error "Unable to recognise device (Code 43). I have tried many things but none of them seems to work as PC is not detecting the Connection.
So... Plz..help...Get Me out of this...I want to see my Mi4i alive again...
Related
I bricked my MT6577-based phone. I ran an app which re-partitions the drive, and this stopped the phone from booting -- the initial boot splash screen appears (in this case an Android icon), but it doesn't get to the point where it loads the OS (which would be represented by an Android icon where the droid's eyes and 'jetpack' light up).
I have placed the phone in recovery mode (power+vol up), and connected this to my PC (Windows 7). The PC does not recognise the phone and flags up an "unknown device" (code 43), so I cannot do anything with the flash tool or MTK tools.
I'm assuming that the original ROM is still intact, but can anyone confirm: is this phone recoverable? I should point out that it appears not to be possible to get a copy of the stock ROM for this device, I have searched at length with no success.
If it's dead without the ROM, a single line to the effect will put my mind at rest at least
Reinstall the drivers and then connect your phone in recovery mode
Use yuweng's ctr recovery porting tool and get the custom recovery
Then in wipe menu, wipe data and emmc partition then try
Otherwise you'll need the stock rom to he flashed by flashtool
Press thanks :good: if I've helped :highfive:
I have an Infinix Note 3 X601, updated to Android N, Rooted and Philz Touch 6. 59, 0 custom recovery installed. Problem began when I tried to factory reset it from within the settings, the phone rebooted to recovery to wipe the data, and since then it wont boot to system again, whenever i try to boot it to system, it will go to recovery. if i connect it to pc, the pc wont recognise it, the pc will show a message that the USB device is not recodnisd, and the phone will boot to recovery again.
i tried to reflash the stock firmware using sp flashtool and it always fails as the system will not recognise the phone, even though i have the required mtk drivers installed.
i tried to flash this https://androidhq254.blogspot.com.ng/2017/04/mad-aosp-n-711-for-infinix-note-3-x601.html and http://bbs.infinixmobility.com/thread-149453-3-1.html custom roms using the custom recovery, they all fail mid way.
i will appreciate any help i can get in reviving this phone. thanks in advance
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
arn2641 said:
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
Click to expand...
Click to collapse
thanks for the reply, could you elaborate on the "qpst tool" pls, i dont know much about it
qpst is a kind of software
that enable us to use a port in the phone to install firmware and others software when something like this happens...
some manufacturers like Samsung manufacture in such a way that this cannot be used,
depending upon your manufacturer and the processor(it mainly support snapdragon i think) you may get if you search in Google.
arn2641 said:
i have a. zuk z1 i did something like this and the phone got bricked I then tried installing other roms and also backups but the phone only boots upto recovery..
i unbricked the phone using "qpst tool" see if your phone have something like that
Click to expand...
Click to collapse
when i try to flash a rom through recovery it shows:
mount system partition
mount: failed to mount /dev/block/platform/mtk-mdc.0/11230000.mdc.0/by-name/system at /system: no such file or directory
unmount system partition
unmount of /system failed: no such volume
format system partition
E:Error in /storage/sdcard/........
(status0)
installation aborted
what do you make of this pls?
Please help, a few days ago my phone decided to stop working for no reason, so I thought it was a ROM problem(I was running Android Pie AOSP Extended). So I reset it, after resetting it the phone was stuck at the LeEco logo, so I decided to use the 9008 mode flashing it, but no matter what I do it always come up with the error Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I don't know what to do, please help.
Did you tried flashing Twrp first in instead of qsahara sometime they give error
They show error also when partitions are messed up so may be u changed partition settings
So try installing Twrp and rewriting partitions then use a pendrive and mount it in Twrp and install a simple room for example AEX and try to boot otherwise try side loading the rom
If u r possible to boot into twrp format device and install any ROM zip through pendrive
I cannot even exit 9008 mode, the phone is completely dead with no respond when pressing any button combination, but it shows up as Qualcomm HS-USB QDLoader 9008 when I plugged in to my PC, and it also doesn't show up when using the ADB devices command. And thanks for replying
Can you add photos of what error it is showing when trying to boot into fastboot mode
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
MrNotJeff said:
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
Click to expand...
Click to collapse
Ok, first, dont give up, 2nd have you put phone into qfil mode as program told you? 3rd check if inside this zip is not 2nd zip, some packages are "double zipped".
MrNotJeff said:
https://drive.google.com/file/d/12jmHM0f50WFMMXeeZWxLq9LkdAg6magp/view?usp=sharing
This is the error it is giving me while trying to unbrick it, and the phone seems to be charging since my charging block is heating up.
Click to expand...
Click to collapse
I had a practically the same problem with Xiaomi Redmi Note 5 Pro (Chinese model)
Inside the zip file there is a file (or two of them) responsible for uploading the ROM. It first sends one of those files and the Qualcomm loader puts it in RAM and boots that file.
If successful, the upload continues, but if that file is wrong, it will not boot it and will not load. So the zip file you have may not be for the exact model of your phone. Try to find another one, maybe a different version...
Hope this helps.
Sent from my GM1900 using Tapatalk
Hello everyone, a couple of months now are also thanks to you in the world of modding. Yesterday (i have a Xiaomi Mi A2 Lite) during the installation of a custom ROM using ADB, typing in the fastboot command "erase system", I wrote erase a_boot for error because before I was reading a post about it and I wrote it. Yes I know, I was too stupid. Result? The phone does not start up either in recovery or in fastboot mode, and from the PC it is recognized as COM port. I have already documented about it and tried to flash everything with the Qualcomm tool after installing the drivers but nothing. I tried the EDL by activating it manually to unlock port 9008, but still during the flash gives me error. I tried everything, do it all over again in a newly formatted and clean PC from any other driver, but nothing. During the flash, even if I put the firmware in the same directory, it still gives me error. Guys I'm desperate please. I do not know what else to do. I hope to receive your answers :crying::crying::crying:
I also have same problem.. if you find some solution then tell me also.. my device is different.. but problem is same.. device basically dead & can be recognised in com port
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
have to get someone with authorized account to fix it using edl flash tool, from next time dont use miflash and just extreact the rom zip and flash it with the bat file.
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
hey
I brought mi phone for my aunt and she is facing similar issues too. If you find any solutions do let me know.
ScarletSkies1234 said:
have to get someone with authorized account to fix it using edl flash tool, from next time dont use miflash and just extreact the rom zip and flash it with the bat file.
Click to expand...
Click to collapse
Yes, today, I have been looking for solutions and I see that paying someone with authorized account is the only way to get my phone back. :C ....I didn't know you could flash without the Mi flash tool, thanks, I will try in the future....
msgranger12 said:
hey
I brought mi phone for my aunt and she is facing similar issues too. If you find any solutions do let me know.
Click to expand...
Click to collapse
Hi, I told you that I fixed my phone with the "Xiaomi Pro Tool" (it's paid but cheap). Good luck!
ajanco said:
Yes, today, I have been looking for solutions and I see that paying someone with authorized account is the only way to get my phone back. :C ....I didn't know you could flash without the Mi flash tool, thanks, I will try in the future....
Click to expand...
Click to collapse
My friend tried to flash fastboot image using official android platform tools from google, build march 2022, it didn't work. Always failed when flashing the super partition. Fortunately, he decided to flash it with mi flash build 2020 (forgot which one), and it succeeded. I didn't believe it at first. Weird indeed. I believe xiaomi put something else to their fastboot binary in the mi flash.
ajanco said:
After installing some roms I decided to flash the stock rom using Mi flash tool, but the flash tool gave many errors, I tried many times to flash it, and then I decided to reboot the phone in fastboot mode to see if that solved something, but from that moment the phone did not turn on again, and it did not enter fastboot or recovery mode.
After a moment I connected the phone to the pc and saw that a device appeared "Qualcomm HS-USB QDLoader 9008".
Then I looked for solutions on the internet and when I tried some of those solutions, I realized that the flash tool sometimes when I clicked the "flash" button did nothing, when you clicked it again it showed errors, but if you clicked the "flash" button and then the "refresh" button the flashing progress appeared, so I thought that's why my redmi note 10 was hard bricked, because I closed many times the flash tool when it was flashing.
I thank you in advance for any help. Any idea how to fix it?
Click to expand...
Click to collapse
Xiaomi Flash tool support EDL flashing too...try this version....and also install the Qualcomm driver.