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.
Related
Hi everyone,
First of all, I have some basic knowledge but treat me as an absolute noob please
I have a issue with my Huawei Ascend G700-U10. I tried flashing twrp recovery from the phone itself. It was either a wrong one or (I read that that could happen) something with the partition. The result is a boot loop. My PC does recognise the decive, but only for a few seconds. The flash tool does "try" flashing, but as the phone is disconnected too fast, I get an error message. Without much experience, I'd say that the only way I could flash something is making the phone stay connected longer or make the program flash faster. I have no idea how to make the phone stay connected and tried to only flash the stock recovery because I thought it would have to flash less and get it done in those two seconds that the phone stays connected. That didn't work though.
I thought about buying a new phone anyway, so if I can't solve it, it's not dramatic, but a working phone is always better than one that doesn't.
Thanks for your help in advance
Hi, thank you for issued XDA Assist. I think you're right that you need to flash the stock firmware. I'm not sure why usb would keep disconnecting but try different usb ports, the ones in the back of your pc, and cables.
Thread closed.
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
Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.
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.
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.