Hello. I am new to this subject (flasing ROMs, root..) and messed up ¯\_(ツ)_/¯. So I installed Havoc OS GSI on my Redmi 9, and it worked. The issues began when I tried to fastboot to become root. The process failed for some reason, so my phone was stuck on a bootloop but wasn't totally bricked at this point (could access fastboot, recovery [stock Xiaomi recovery], was recognized on pc...). In my ignorance, I tried to unbrick the phone with XiaoMiTools, program that also failed to unbrick the phone. This is the issue I am facing currently: After failing to unbrick the phone, XiaoMiTools restarted it, an has been since yesterday in a weird bootloop.
The phone displays the Redmi logo, some seconds later, it restarts itself, displaying the Redmi logo again and never loading any OS. Pc does not recognize it now, or at least I can't see it neither on ADB nor the Windows 10 Device Manager, as well as I can't access the fastboot nor recovery. It is a weird situation, because I am sure that the cable does work (tried with other devices) along with the phone's USB C port (it boots when I plug it), the phone also vibrates.
I have accepted that the phone is dead, but as a last option I come here to see if you guys could help me. Thank you.
Hint: Add " Redmi 9 to front of this thread's title thus people who own such a device get mainly addressed.
Related
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
I have a Coolpad F1 8297 (from Hong Kong) which is currently bricked. The problem is unique for me. Sometime back I had rooted my phone and installed custom Rom (something like ASOP don't remember exact name and probably it was for 8297w). The same was installed through TWRP recovery module. I am sorry but I must say that I was playing around with TWRP options and through mistake I deleted something and since that day my phone remained in boot-loop. I can only see the Chinese script & F1 displayed on the screen when I push the power button. I also cannot enter TWRP recovery. I tried to connect to the PC but even then it would not connect. I have installed all necessary drivers etc. Tried changing ports, cables and everything that I found on the net. When I attach the device to PC it connects and disconnects and this goes on endlessly. Please therefore help me getting a fix for my phone. Thanks.
rdcontractor said:
I have a Coolpad F1 8297 (from Hong Kong) which is currently bricked. The problem is unique for me. Sometime back I had rooted my phone and installed custom Rom (something like ASOP don't remember exact name and probably it was for 8297w). The same was installed through TWRP recovery module. I am sorry but I must say that I was playing around with TWRP options and through mistake I deleted something and since that day my phone remained in boot-loop. I can only see the Chinese script & F1 displayed on the screen when I push the power button. I also cannot enter TWRP recovery. I tried to connect to the PC but even then it would not connect. I have installed all necessary drivers etc. Tried changing ports, cables and everything that I found on the net. When I attach the device to PC it connects and disconnects and this goes on endlessly. Please therefore help me getting a fix for my phone. Thanks.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=CVh5koB5ky4&ab_channel=Chinaphonearena
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
joao.m.neto said:
Hi guys,
I got a OPO borrowed from a friend because my OP3T is going to RMA.
When I first turned it on it had 1% battery. The phone wasn't used for a month. I proceded to recharge the battery. This took almost 18h. I saw the low battery error 3 or 4 times during attempts to power on the handset.
After full charge in installed the latest build of Lineage OS via TWRP. Unfortunately as I was having some WIFI connectivity issues I read that flashing the c7 modem firmware could solve the problem.
I was in TWRP flashing this same zip via sideload with an unbeknownst to me faulty cable. I grabbed the handset mid flash, and it fails with a connectivity error. I tried repeating the process with no luck, as I could not by any means regain adb connection to the handset. And then i decided to reboot and download the zip directly to the phone, without remembering this broken flash attempt could brick the phone. After rebooting I never saw again the One Plus logo neither felt the startup vibration. I tried power cycling with no success, and I cannot by any means detect the phone in windows device manager to attempt the usual unbrick procedures via COLOR or OnePlusRecoveryTool.
Windows doesn't even try to install drivers. It's as if the phone is completely shutdown forever.
What do you think. Did I really hard brick this phone? Is it a battery issue? Any ideas. I really liked to recover the phone to return it to my friend!
Thanks in advance for your help!
Click to expand...
Click to collapse
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Mr.Ak said:
Could be a battery issue too since the device was unused for a month. Did you tried booting into fastboot mode or TWRP?
Which windows are you using?(I suggest you use winXp and win7) Did you tried the qualcomm 2012 drivers from the Color Os toolkit thread and the drivers given on Cm11s restore toolkit thread? -you should know that the fastboot(/adb) drivers will not work for qualcomm diagnostic port method(which the both toolkits are based on).
Click to expand...
Click to collapse
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
joao.m.neto said:
No success booting with volume up or down so no fastboot neither twrp. I'm using windows 10 (only one i have). I can't install the drivers because the device doesn't show up on device manager right?
I'll try finding a win XP although I'm sensing the habdset isn't powering at all...
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes,as I said, could be a battery issue but we are still not sure yet.I can give you the link for winxp or win7 if you need and then you can dual-boot it alongside windows10.You should install drivers from cm11s restore toolkit thread(executable drivers),maybe then your device will show up in device manager though it is highly advised to do this on Xp or 7 since 8,8.1 and 10 has driver signing issues.
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Hello,
First, some context:
After a factory reset of my Xiaomi Mi 10 Lite 5G (the phone is more than 2 years old, the warranty expired), the phone worked fine for a few days, but while playing a video game it suddenly crashed, then it showed up the following error: "Your device is corrupted. It cannot be trusted and will not boot."
Then the phone started displaying random white and black horizontal lines everywhere on the screen before shutting itself down again.
As of now, the screen stays completely dark, no sound, no vibration, no LED flashing, nothing shows on the screen whatever key combinaison I press.
Nothing happens when charging the phone either.
However, the device is recognized as "Qualcomm HS-USB QDLoader 9008" when plugged into my PC, so it is in EDL mode.
The phone has never been unlocked, nor flashed, and was (before this incident) running on the official MIUI 13 (Developer options had never been activated, nor ADB and it never entered into fastboot mode).
tl;dr; The device crashed without notice and put itself in EDL mode after displaying a worrying error message.
I tried draining the battery, no luck, nothing changed.
The phone is recognized by MiFlashPro (latest version: 7.3.706.21) but it shows a forseen error saying i need a authorized Mi account to flash it (but I don't want to pay 25$ a random guy on the Internet to flash it for me, knowing the device might be dead).
It is also recognized by QFIL, and I got my hands on a "patched Firehose" to bypass the authorized Mi account, but it always ends up showing the QSahara error (the error remains the same whatever firehose I select, patched or not, and whatever rawprogram*.xml too).
So, does anyone know how to flash a hard bricked Xiaomi in EDL mode using QFIL?
Anyway, I tried to be precise and concise, I hope someone has a working solution.
Thanks in advance for your answers!
PS: I tried to flash Monet EEA Global V13.0.4.0 (MIUI 13).
I have had the exact same problem happen to me with a Xiaomi Mi Note 10 Pro (tujana).it's just that I bought the device already bricked by the previous owner who flashed it with the ROM for the wrong device, namely the Redmi Note 10 Pro(sunny/mojito)I've since then succumbed to giving money to strangers online to flash it, but the flashing kept throwing an error(couple of guys tried it) and I couldn't flash it myself with QFIL as well, getting the same error messages as you. So I decided to dig a bit deeper and found out that the primary bootloader that is bar unflashable in those devices(please someone correct me if i'm wrong here) is different on the Xiaomi Mi Note 10 Pro that has version 2 primary BL and the Redmi Note 10 Pro has version 3. I do not know why and how the previous owner flashed the device to hardbrick it like that. I can't seem to figure it out. If anyone comes up with a solution I'm buying.