Hi
I have a bricked redmi 1s stuck in EDL mode
Nothings working and after applying test point method now it just detects as Qualcomm hsusb qdloader 9008 and while flashing through mi flash tool the 9008 changes to Qualcomm diagonastics 9006. Then the mmc storage driver installed but in device manager I discovered that the 9006 port keeps refreshing as well as the mmc storage at disk management also refreshing. And this causing an error " Specified device or network resources not available" .
So my question is
What is causing the problem and how to fix it.
An early help required . Have stuck at this problem from 2 or three weeks please you guys are awesome I know one of you can give me the solution.
Try this and see if it helps https://forum.xda-developers.com/redmi-1s/help/redmi-1s-bricked-t3788482
Nope it didn't worked.
Same problem ....
I think my motherboard damaged... I got an spare motherboard
Should I give a try?
parag2001 said:
Nope it didn't worked.
Same problem ....
I think my motherboard damaged... I got an spare motherboard
Should I give a try?
Click to expand...
Click to collapse
If you wish to give a try you can, I've seen someone having this type of issue and they were able to revive their device.
I'll search that thread for you but I don't remember exactly where I saw that.
I'll let you know as soon as i find that thread or any solution if there's any.
Please help me out I have no interest to play with the hardware parts please let me know if you find!!!
Thanks for your reply!
Hi.
At last trying several ways I got that my power button got short circuited so that the button was pressed all time and after popping the button out of the motherboard the phone is in stable condition but I just can't turn on the phone itself always a computer is required for fastboot commands to turn on the phone. And if you guys have any ideas how to fix that empty space or how to create a power button to use the button.
That's all but I am so happy that I could fix my 5 years no 6 years old phone.
Related
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Same proble with mine but i bricked mines when update to lollipop and never turn on again . still waiting to some one help to revive my LG
If I come across any solution I'll post it here. In the meantime I've tried the following method on a freshly formatted laptop and I still get "Unknown Device" in Device Manager..
http://forum.xda-developers.com/showthread.php?t=2785089
same here
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
jc.delgado11 said:
same problem, someone told me that if was the board or something like that and that it only can be fixed with a complete replacement of this, also, that it could be fixed with linux using comands to install .APK or .TOT.
linux sometimes sees it as Qualcomm CDMA Technologies MSM QHSUSB_BULK, using a virtual machine of linux ubuntu, windows 8.1 sees it as unknow device
LG dead since 3 months ago.................. i wasnt using the phone at all when this happended so........... :crying:
Click to expand...
Click to collapse
I tried using a boot usb drive to see if ubuntu saw the device but it didn't. Maybe there's some things needed that I didn't do. The thing I don't understand the most is why do windows see it as an unknown device only with the battery out while if I connect the G3 with the battery on, it doesn't show anything on device manager..
Nubrig said:
So I bought a used G3 knowing about the issue it had; it didn't boot. I thought I could find a workaround to this but the phone doesn't boot, doesn't enter recovery or download mode. All the info I have is that when I take off the battery the pc sees it as an unknown device, while it's connected I press the power button for several seconds and it disconnects from the pc, reconnects after several more seconds of pressing the power button. Screen remains dead. Seller told me he had a perfectly working phone before he tried to root it and it never turned on again. One more indication is that the LED notification only flashed red a few times when I connected it to the wall charger and that was it. No LED working after that. I'm open to any suggestions though I guess I'm here for someone to tell me there's no hope reviving the device. Thanks in advance!
Click to expand...
Click to collapse
Hi there.
Please check these 2 threads out and see if any of it will help you. The one for the G2 can also be used for G3.
Here are the links:
http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091 With this technique you would have to find the software online somewhere but this method does revive dead G3 with these symptoms.
http://forum.xda-developers.com/showthread.php?t=2475045
If I helped somehow, hit the THANKS button.
Good luck!
The thing is I can only get the device to be recognized as an Unknown Device in Device Manager and only with its battery out. If I keep 'volume up' pressed nothing happens, it's only shown after I simply connect the USB cable and it pops up after 10 seconds or so. It's very consistent in the way it behaves..
A small update, sometimes when I pull and put the battery again, I connect the phone to a pc while holding down vol- and the pc makes the connected usb sound while the phone led is blinking red for a couple of minutes, then it stops. That's about all there is concerning the phone giving signs of life..
dead/bricked LG G3 help in Manchester UK
Hi,
Just wondering if there is someone confident and experienced in modding and flashing of roms and so on in Manchester UK.
Last Thursday my G3 (D855 - european 32 gb) just died by it's own. I never messed around with the software on it, never had custom roms or anything on it... I was using it as usual, left it on the table and the next time I picked it up it was dead. it hat around 30-35% of battery when i left it on the table and after like 15 mins it was dead.
tried to charge it
tried booting into download mode (not working)
my laptop recognized it as qhsusb_bulk at first, than I installed some drivers and now it shows up as Qualcomm HS-USB QDLoader 9008...
I've tried a couple of things that i've found on the forums but either i'm doing something wrong or maybe i don''t have the right files... in any case i didn't manage to fix it.
so if there is someone near Manchester UK please contact me, i'm willing to pay for your " services "
If you power on the device the led blink's on red or something?!
display show no signal?! really strange...i dont know nothing with this problem but...if you search around your city sure you find mobile stores who made repairs and give you some feedback about what they could be!
the phone does not respond to anything. the led does not blink, the screen won't turn on at all, it won't go into download mode. the only sign that there is still some life in the phone is the fact that it shows up in the device manager as Qualcomm HS-USB QDLoader 9008...
from what i read on the forum it's soft bricked. i already tried almost all the methods (tot file, lg flash tool, board diag etc.) but they don't seem to work. for example :
*LG flash tool gives the following error : Download fail ! ... model information check fail.
*Boad diag 3.99c gives AP test fail
*LG smart boot diagnostics tool v.1.3.1 gives finds no errors and does nothing
i turned to the forum as I trust this community more than phone repair shops...
Hey Guys,
I've a Samsung Galaxy S4 Mini (GT-I9192). It stopped working mid-day all of the sudden while it wasn't in use. The phone is just showing a black screen, & pressing the power button, it doesn't respond. The phone also doesn't respond when I try entering the download or recovery modes. When I connected the phone to the PC, it was identified as "Qualcomm HS-USB QDLoader 9008", & looking up on the internet for what does this mean, I found that it means that phone is bricked.
I never rooted this phone, & I tried to write two I9192 debrick images (One at a time of course ) on an external SD card using Win32DiskImager-0.9.5. However, turning on the phone with any of the two debrick images, the phone shows the following lines exactly, & no further progress takes place:
BOOT RECOVERY MODE
CHECK BOOT PARTITONS..
COPY FROM T-FLAH..
BOOT RECOVERY..
WRITE 139008 sectors..
I couldn't find a solution for this issue on the internet. So, any idea what is happening here & how can I solve this problem ??
Many thanks in advance
diaaamin said:
Hey Guys,
I've a Samsung Galaxy S4 Mini (GT-I9192). It stopped working mid-day all of the sudden while it wasn't in use. The phone is just showing a black screen, & pressing the power button, it doesn't respond. The phone also doesn't respond when I try entering the download or recovery modes. When I connected the phone to the PC, it was identified as "Qualcomm HS-USB QDLoader 9008", & looking up on the internet for what does this mean, I found that it means that phone is bricked.
I never rooted this phone, & I tried to write two I9192 debrick images (One at a time of course ) on an external SD card using Win32DiskImager-0.9.5. However, turning on the phone with any of the two debrick images, the phone shows the following lines exactly, & no further progress takes place:
BOOT RECOVERY MODE
CHECK BOOT PARTITONS..
COPY FROM T-FLAH..
BOOT RECOVERY..
WRITE 139008 sectors..
I couldn't find a solution for this issue on the internet. So, any idea what is happening here & how can I solve this problem ??
Many thanks in advance
Click to expand...
Click to collapse
My phone (Samsung Galaxy S4 mini Duos GT-I9192) is with the same problem, since 2016 October!!. But I know what happened. It was a virus!: In a day, when I turned on my wifi, an unexpected download started . . . , after about 5 seconds, several app's began stopping uninterruptedly, followed by message asking "OK". So, I forced the phone to turn off; waited some time, but when I pressed the power button, nothing happened and it remains like this until now! I have tried all of the things possible by pressing combination of buttons, but it is really hard bricked!!. I just hadn't courage to use any kind of (de/un)brick image yet, like you. I'm continuously researching in the internet and trying to learn how to solve this problem in a secure way. I have found something relating to unbrick qualcomm mobiles using QFIL, but we have to use other kind of archives other than thouse from GT-I9192 original rom, which made me with doubt if it will function.
If somebody understand better than us about it, please help us!
Thanks.
villaovb said:
My phone (Samsung Galaxy S4 mini Duos GT-I9192) is with the same problem, since 2016 October!!. But I know what happened. It was a virus!: In a day, when I turned on my wifi, an unexpected download started . . . , after about 5 seconds, several app's began stopping uninterruptedly, followed by message asking "OK". So, I forced the phone to turn off; waited some time, but when I pressed the power button, nothing happened and it remains like this until now! I have tried all of the things possible by pressing combination of buttons, but it is really hard bricked!!. I just hadn't courage to use any kind of (de/un)brick image yet, like you. I'm continuously researching in the internet and trying to learn how to solve this problem in a secure way. I have found something relating to unbrick qualcomm mobiles using QFIL, but we have to use other kind of archives other than thouse from GT-I9192 original rom, which made me with doubt if it will function.
If somebody understand better than us about it, please help us!
Thanks.
Click to expand...
Click to collapse
Qfil doesn't work with Samsung as far as I know. Even if it did you would have to have the files for your exact phone model.
But I'm going to continue researching. . .
Thank you.
hey villaovb. did you find anything or this problem?
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
1a)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
1b)goto Google and search for Qualcomm qd loader.download,install and restart your pc.
2)After restarting,Extract the file from OPPO UNBRICK TOOL and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry it isn't corrupted,just follow through↓
4)disconnect your device battery,then open the software and press start,after that connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button
5)please wait patiently as it is reflashing stock rom to your device.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
P/S:if your device is softbricked,you just should disconnect your battery,and then open the software and press start,then connect the phone to your pc/laptop (WITHOUT BATTERY) and hold volume up button.
If your device is hard bricked(like mine)only holding the power button could work as well
*UPDATE* 24/2/2019
-If you guys still have any concerns kindly contact me through twitter (0728mal)
*UPDATE* 4/7/2020
-yes it is still working guys,no worries kayy
-no you don't need internet for it to work,the software already has all the files needed to flash the device,which is why the file is pretty big.
best regards,
Akmal
Link updated :good:
akmlfhm said:
Greetings,im Akmal and today I will be sharing some helpful solution to unbrick your Oppo Find 7/7A.Short Story(myb a lil bit longer)¬
So my find 7A got soft bricked when I install custom rom without using TWRP(pretty stupid to do so)
After rebooting my phone keeps on booting to fastboot mode and no matter it happen the same if i press vol up/vol down and power button.
At this stage I knew my phone is soft bricked.So I found the solution to it through some old posts which you have to extract the ColorOS blablabla and adb thingy(I dont wanna go through it here)
But I dont realised that i forget to flash a file name "TZ.MBN"
Now that my phone wont ever boot or even to fastboot which resulted to hard brick.
No recovery screen.
No Charging status screen
No Fastboot screen
No sign of vibrating when i push the power button
-So here is the solution which make my phone came to life again-
Disclaimer-I am not responsible for what ever happen to your device after this-
-there are already some other posts like this but I make this post to let you know that its still working.
-make sure to charge the phone first even if you do not know if it charging or not
1)First,download the OPPO UNBRICK TOOL HERE
bit.ly/OPPOUNBRICK
2)Extract the file and open "Msm8974DownloadTool.exe"
3)as you may have notice,its chinese language or some aliens language but dont worry its not corrupted,just follow through
4)Connect your phone to PC and press the power button until you heard some like mounted usb alert on windows.(its ok aslong windows does not detect it on device manager but its ok if you can hear the alert sound.
5)back to the software,no need to mess around with it.Click on start until its downloading a "new life" to your phone.
6)as you may have noticed maybe your device disconnected but DONT GET PANICKED! press again the power button until its downloading again on the software.
7)If it has done downloading,some row should be in a Green colour.
8)disconnect your cable and try to turning on your device again.
That's it!Any comment or curiosity I will try helping you through the comment section but I not guaranteed everything I can answer
best regards,
Akmal
Click to expand...
Click to collapse
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
On Mac's OS, you can always install Windows on its proprietary virtual machine and get the process going that way.
babyenchantress said:
hi im having this problem as well. my find 7a is hard bricked after i flash coloros v2.1.5i without twrp. the problem is, my computer does not detect my phone at all even after i hard reset and hold power button for 30 seconds. i dont think the battery is drained because before this happened, my phones battery was about 90% and i try recharging the phone for 30 minutes, and nothing happened. so the debrick tool cannot be used. can you suggest anything for my problem?
Click to expand...
Click to collapse
hello there!I'm really sorry for not checking this that often and really sorry if i let you down because im too busy with my schools work
btw before my computer can detect my phone i have to download a driver which detect qualcomm processor for my oppo then it can be detected by my pc therefore i can do the unbrick process:good:
Shadician said:
Got excited when I read this post! Is there an Oppo Unbrick tool for Mac? I don't have a Windows machine so I can't run the .exe file... Is there an equivalent for those of us not on Windows? Thank you
Click to expand...
Click to collapse
yeah you can try WINE also but i never have any experience with mac os before so i cant guarantee that it will work considering that you're configuring your drivers,which can go wrong if not done correctly
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
true_friend2004 said:
So I have bricked my phone (X9006) while trying to install TWRP recovery. It is stuck on logo and adb/ fastboot does not recognise it anymore. I have tried the above-mentioned tool, but this program also does not do anything for a long time. Am I missing something in applying this solution?
Edit: I am an Windows 10 and I might not have the Qualcomm drivers installed. I don't know how to install
Click to expand...
Click to collapse
Hello there.have you tried downloading the "Qualcomm"
Driver software on your PC?
is it necessary to remove the battery? I don't have tools for opening my phone and it's battery is non-removable
Perhaps an important step is missing. The Qualcomm qd loader driver is may not signed. I had to boot into the extended start menu on Windows 10 and disable the driver signature check - point 7 - and could now successfully debrick my find7.
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
After a lot of trials I could solve the problem, but I dont know what I did different.
I did everything the same.
Anyway thanks to everybody who read.
Regards.
hagiwatt said:
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
hagiwatt said:
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
Click to expand...
Click to collapse
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
pavanpilot94 said:
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
Click to expand...
Click to collapse
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
hagiwatt said:
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
Click to expand...
Click to collapse
Hi Everybody!
I have just recieved the phone from service center. They fixed the vibration problem under warranity.
So binary counter did not affect the warranity status.
I dont know if they checked the counter or not.
For information to anyone who has the same issue.
Regards.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
and if the pc did not detecte the phone and i cant see any thing new in device manager ,plz help me