First of all, I want to apologize if I put this question in a wrong section or place. I'm a newbie around here at XDA and been following this since my eyes were opened for android stuff. I'M JUST REALLY SEEKING HELP. :crying:
It's been 6 months since I hardbricked my Huawei Y6. I only used it for two weeks but when I messed it up, it's been dead ever since. I have searched almost every corner of Google and XDA for a solution but none of them ever came up with one that is successful. I tried to recover it and sht to no avail. It's a Snapdragon 210 (MSM8909) btw, and Qualcomm. Used lots of things like QPST, EMMC DL tool, and whatever those other things are but here's really my problem..
Huawei Y6 has no firmware available online. If there is, only that ****ty UPDATE.APP. I did extract it and I don't know what to do with these files. There's no PROG_EMMC_FIREHOSE_8909.MBN, the PATCH0, and that other one which are what I am supposed to be using with QFIL. Anyway, NO DOWNLOAD MODE, NO RECOVERY MODE, NO FASTBOOT, and completely dead. I did something terrible internally to the device, I know.. messed up the partition table. I did bring it to lots of technicians around here and to the service center but all of them declined and denied me saying that it's dead and must be replaced. But if plugged in to a computer, LED will slowly blink Red. And.. it's detected as Qualcomm HS-USB QDLoader 9008.
Please help me.. 6 months = no phone = DEAD. </3 I know that this phone is not that popular because there's not that much things about this online. I really want to have this fixed.. I'm willing to do everything possible in return. Just help me. This is last resort and my only hope. HELP MEEEE. Thank you, XDA.
Update.. I somehow did something nice to it. It now can access fastboot but do not boot.
I got it in progress. Flashed system.img, boot.img, recovery.img, through fastboot flash and erased userdata and cache. If I turn it on, will just vibrate once. Can't enter recovery nor normal boot. But if plugged in, will be detected as Android Bootloader Interface. HELLLPPPPP!!!
And now.. it got even weirder. I flashed all its stock rom files (those that were extracted from UPDATE.APP) and now when booted, LED goes to RED-GREEN-BLUE cycle. What the heck is going on with this phone? It doesn't vibrate anymore and still can't go to recovery.
i also have this phone in same 9008 port condition , is there any solution to revive this ?
how to get the files to flash with QFIL ?
dear all
did you find the solution ??
Related
Hello guys, I really hope you could help me on this one, I screwed up really really bad.
Let me explain the problem, I wanted to be a smart ass, and install an unofficial version of Nougat, and I succeeded, but then I wanted to remove it because I wasn't satisfied of it.
So I went on recovery mode and "accidentally" erased everything... I said that I screwed up ok, at leat I'm aware of it haha
So now my problem is that my phone is completely empty, cant get into recovery mode, only in fastboot mode, adb and fastboot don't recognize my phone, and that's logical because there is nothing in it.
So, is my phone completely dead, or is there a way to put the original os in it?
Thank you guys so much for helping me, i'm desperate...
PS/ I know this is probably the wrong category for this topic, but since it's my firt post, I hope you could understand, appreciate
did you install all the needed oneplus drivers to your computer in order to recognize it? If that's your problem, then you could flash twrp onto your phone and get stock OOS back.
Gwennito said:
Hello guys, I really hope you could help me on this one, I screwed up really really bad.
Let me explain the problem, I wanted to be a smart ass, and install an unofficial version of Nougat, and I succeeded, but then I wanted to remove it because I wasn't satisfied of it.
So I went on recovery mode and "accidentally" erased everything... I said that I screwed up ok, at leat I'm aware of it haha
So now my problem is that my phone is completely empty, cant get into recovery mode, only in fastboot mode, adb and fastboot don't recognize my phone, and that's logical because there is nothing in it.
So, is my phone completely dead, or is there a way to put the original os in it?
Thank you guys so much for helping me, i'm desperate...
PS/ I know this is probably the wrong category for this topic, but since it's my firt post, I hope you could understand, appreciate
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page19
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page19
Click to expand...
Click to collapse
The thing is, my phone is detected by my PC, as Kedacom USB Device > Android Bootloader Interface.
I tried to follow the guide from page 1, but since my phone is not detected as Qualcomm whatever, I don't if I can follow this procedure.
And also, when I turned on my phone, I juste have the logo One plus and Power by Android. If i try a recovery mode reboot, it's same screen, over and over. The only thing I can get into, is the FastBoot mode, by holding Volume up + Power, but I don't know if I can do anything with it, because even in this mode, adb won't recognize it.
So, this is what happened, and I have no idea how to fix this, nor I am going to try something made for other devices unless it's my only choice.
I woke up one day after wanting to revive this phone, and I realise it's bricked, totally. No Charging animation, bootup, not even Fastboot Mode.
If I connect it to Windows just the way I do to activate Fastboot, I get a ton of drives on the main computer folder, which all need formatting. (http://imgur.com/hoxrbaw) Only one can be read, but it has quite some weird files. (http://imgur.com/fAHyaly).
The Device Manager shows me quite a weird driver, called QHSUSB_BULK (http://imgur.com/b9KPIVT).
I did re-flash the Factory ROM using the correct drivers, the correct ROM and Coolpad Download Assistant v1.86.
There is nothing else I know about...
http://imgur.com/a/D4QCo
Is there any way I can recover my phone?
Thanks,
-TheTNTLovers
The Only thing I managed is to do nothing because I don't have an identical phone. Can someone send me an eMMC file of Vodafone Smart 4 Turbo 890N?
-TheTNTLovers
Take out the battery and put it in again. I've got that exact phone model and it happens all the time. It was especially scary as it happened after I first backed up via FlashFire.
Unfortunately, I did this quite a lot of times, for over 20 times, and nothing.
Do you have the same phone and can you provide me a eMMC image from it? so I can re-flash it and make it work again...
Thanks!
I managed to get a red Charging LED for about 5 seconds, then it stopped. I re-plugged it in and nothing.
I took the battery out and re-plugged it in, then I got the same LED, but shorter.
Unfortunately, that is quite all I got.
I can't do much but trying YGDP, but this is all I know for now.
Is there something I am missing?
I believe that I hard bricked by trying to install another OS on it, but the cable got damaged and we got a bit of an error that hard bricked the device.
Can you guys give me any bit of advice on this specific phone?
TheTNTLovers said:
Unfortunately, I did this quite a lot of times, for over 20 times, and nothing.
Do you have the same phone and can you provide me a eMMC image from it? so I can re-flash it and make it work again...
Thanks!
Click to expand...
Click to collapse
I do, but I literally have no idea what an eMMC image is. I CAN provide you with everything else. To my understanding, there are actually no ROMs for this phone, which is disappointing.
It means a backup image made from the phone with a certain flash tool. If you make one, I need both the image AND the flash tool you used.
I already sent the phone to service, and I will have it replaced. If you can supply me with ANY info about this phone I had trouble with, then please do.
Thanks,
TheTNTLovers.
Would a *complete* FlashFire backup work? It backs up literally everything.
Can someone send me an eMMC file of Vodafone Smart 4 Turbo 890N?
Hi, we need proper loader for this device. All other files can be extracted from cpb. I have nck, umt and infinity boxes, but they don't support it. If anybody can share a loader to flash in edl mode it will be great.
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
iamkaruna said:
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
Click to expand...
Click to collapse
I think you are on the wrong forum, this is for Redmi Note 10 (mojito/sunny)
Hello People,
I was flashing the stock rom using mi flash but the flashing timed out after 2000 seconds. I rebooted the phone to fastboot but it failed and the screen went black. [Reason For Flashing: We lost the pattern lock so i flashed the stock rom and, then twrp, just in case to avoid losing the screen lock. But then i thought of keeping it stock and when i reflashed, the timeout occurred and phone went black]
Since then i have tried many different versions of MiFlash and even MiFlash Pro, however they are not successful due to authentication issues. I took it to the service center as a last resort but they are asking for motherboard replacement which i am not comfortable spending for.
I researched as much as i could and tried QPST flashing as well but learnt that a patched firehorse file is required. And that is not available anywhere on the internet.
I am not sure what options i have now or am i doing something wrong.
Could anyone please help me in reviving my phone?
NOTE:
Bootloader - Unlocked
PC Detects It as: QDLoader 9008
Regards
i will help you. pm me asap
SORRY CAN'T HELP YOU ANYMORE. Got no more credits on my Xiaomi Pro Tool account. If you want a cheap fix then it is your only choice. Anyway try any MiFlash below 2020 to flash stock rom. Good luck.
Try mi flash tool 2.0 by Francesco tescari it may help
Thank you for your replies. I had to get it fixed from a nearby shop who claimed to have some access to GSM Forum. I am not sure which tool they used but the job was done.
I wish a patched firehorse file was available. QPST would have helped in that case.
Thanks again.
bidsar.k said:
Hello People,
I was flashing the stock rom using mi flash but the flashing timed out after 2000 seconds. I rebooted the phone to fastboot but it failed and the screen went black. [Reason For Flashing: We lost the pattern lock so i flashed the stock rom and, then twrp, just in case to avoid losing the screen lock. But then i thought of keeping it stock and when i reflashed, the timeout occurred and phone went black]
Since then i have tried many different versions of MiFlash and even MiFlash Pro, however they are not successful due to authentication issues. I took it to the service center as a last resort but they are asking for motherboard replacement which i am not comfortable spending for.
I researched as much as i could and tried QPST flashing as well but learnt that a patched firehorse file is required. And that is not available anywhere on the internet.
I am not sure what options i have now or am i doing something wrong.
Could anyone please help me in reviving my phone?
NOTE:
Bootloader - Unlocked
PC Detects It as: QDLoader 9008
Regards
Click to expand...
Click to collapse
i'm having exact same situtation can anybody help? i got chimera and dftpro