Hi, I have tried to root new Nexus 7, but seems bricked it.
Now I can't turn it on. I see "Qualcomm HS-USB QDLoader 9008 (COM 15)" in the devices list when tablet connected to the PC.
My steps to brick:
1. Unlock bootloader
2. Flash TWRP
3. Boot to the bootloader using "adb reboot bootloader"
4. Select "Recovery Mode"
After this step I had android logo with red triangle. I have tried to exit this mode and pressed Up + Power for few seconds.
That's all.
Are there ant ways to resolve this issue?
I'm not in the USA and not sure that our service centers can help me in the nearest future. No warranty, tablet was bought from the private person, not in the shop.
I'm programmer and know what is soldering, so any solutions are acceptable.
Solution:
swagstr said:
Try holding power only for a minute. Then try again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2220775
I think with past devices when you get the qualcomm loader device it means either the bootloader is corrupted or the raw partitions are corrupted.
You can probably recover, but it would take some effort to figure out specifics.
I think I remember you can use qpst to do some diagnosis.
Maybe try flashing the factory images
They are located here:
https://developers.google.com/android/nexus/images#razor
SplicedX said:
Maybe try flashing the factory images
Click to expand...
Click to collapse
I can't. My bootloader is broken, I need to restore it first.
Will try to play with QPST.
Okay. One step at a time. Use Vol Down + Power to attempt to get to bootloader. What happens?
Sent from my Nexus 7 using Tapatalk 4
swagstr said:
Okay. One step at a time. Use Vol Down + Power to attempt to get to bootloader. What happens?
Click to expand...
Click to collapse
Tablet not connected to the PC - nothing, screen is black.
Tablet connected to the PC - nothing, screen is black, no changes in the device manager.
I have tried both cases - Vol Down first, Power next; Powewr first, Vol Down next; both buttons at one time.
pls help me, i just received mine today, did nothing, only configured google account, google account just started download few apps and system updated once. then when i check "about phone" it restarted or crashed itself, and now i can't pass through flashing X logo. I tried volume down+power i can get in bootloader mode, but unable to use recovery mode, says no command. How to recover or factory reset it? somebody help me
Thanks for posting reply. Try holding power only for a minute. Then try again.
Sent from my Nexus 7 using Tapatalk 4
swagstr said:
Thanks for posting reply. Try holding power only for a minute. Then try again.
Click to expand...
Click to collapse
You are genius!
It is fully working.
ViSoR42 said:
You are genius!
It is fully working.
Click to expand...
Click to collapse
Excellent. Glad it worked.
Sent from my Nexus 7 using Tapatalk 4
---------- Post added at 12:44 PM ---------- Previous post was at 12:29 PM ----------
I switch the title of your thread and add [SOLVED] for people of the future.
Sent from my Nexus 4 using Tapatalk 4 Beta
Help!
swagstr said:
Excellent. Glad it worked.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I'm having the same problem. Neither of those solutions worked. Any ideas?
ViSoR42 said:
Hi, I have tried to root new Nexus 7, but seems bricked it.
Now I can't turn it on. I see "Qualcomm HS-USB QDLoader 9008 (COM 15)" in the devices list when tablet connected to the PC.
My steps to brick:
1. Unlock bootloader
2. Flash TWRP
3. Boot to the bootloader using "adb reboot bootloader"
4. Select "Recovery Mode"
After this step I had android logo with red triangle. I have tried to exit this mode and pressed Up + Power for few seconds.
That's all.
Are there ant ways to resolve this issue?
I'm not in the USA and not sure that our service centers can help me in the nearest future. No warranty, tablet was bought from the private person, not in the shop.
I'm programmer and know what is soldering, so any solutions are acceptable.
Solution:
Click to expand...
Click to collapse
Hi ViSoR42,
I'm a newbie. I had problem somehow the same as yours.
When I was using Nexus 7 2013, it hang up. I press and hold Power button to shut it down. It went down. Then I cant not turn it up.
Nothing happened when I tried to turn it up.
I connected it to the computer. It appeared "Qualcomm HS-USB QDLoader 9008" as well.
I think I can not do anything, for example, "adb", "fastboot", ...
You said that the way of swagstr worked for you. I have tried but failed.
Could you please tell me exactly what you did step by step?
Thanks a heap!
Tu.
tund6789 said:
Hi ViSoR42,
I'm a newbie. I had problem somehow the same as yours.
When I was using Nexus 7 2013, it hang up. I press and hold Power button to shut it down. It went down. Then I cant not turn it up.
Nothing happened when I tried to turn it up.
I connected it to the computer. It appeared "Qualcomm HS-USB QDLoader 9008" as well.
I think I can not do anything, for example, "adb", "fastboot", ...
You said that the way of swagstr worked for you. I have tried but failed.
Could you please tell me exactly what you did step by step?
Thanks a heap!
Tu.
Click to expand...
Click to collapse
its like watching a good 2 hour long show that gets the last half hour cut by a breaking news report just to come back to the rolling of the credits and the 10 o clock news starting off with the breaking news report when you were watching a recorded show on your dvr
It worked for me too.
Why must it be depressed for a minute? what is the secret?
ViSoR42 said:
You are genius!
It is fully working.
Click to expand...
Click to collapse
Sorry for the really late reply, but since this happened to me and I fixed it this way; has it ever happened again ever since?
LittleConfucy said:
Sorry for the really late reply, but since this happened to me and I fixed it this way; has it ever happened again ever since?
Click to expand...
Click to collapse
It was only one time issue for me. But I'm not rooting my tablet every day
mrsnaa said:
pls help me, i just received mine today, did nothing, only configured google account, google account just started download few apps and system updated once. then when i check "about phone" it restarted or crashed itself, and now i can't pass through flashing X logo. I tried volume down+power i can get in bootloader mode, but unable to use recovery mode, says no command. How to recover or factory reset it? somebody help me
Click to expand...
Click to collapse
https://support.google.com/nexus/answer/4596836?hl=en
What you have is normal. You have to go one step more to get to recovery. I've tried to insert a picture, but Tapatalk keeps crashing when I try. Must be L 5.0.1.
Whoa! I did not realize how old this post was. Maybe the hold power button worked for this one, too.
Sent from my Nexus 7 using Tapatalk
swagstr said:
Thanks for posting reply. Try holding power only for a minute. Then try again.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This did not work for me. I have tried it while it is plugged into the PC, plugged into a charger or not plugged in. While plugged into the PC the "Qualcomm HS-USB QDLoader 9008" device on COM3 disappears periodically and then comes back so I can tell there is some life in it. This is extremely frustrating. The device froze while inside a game. The last image rendered stuck on the image for about 15 minutes until I did a hard reset by holding power down and the power button. The device has never turned back on since.
The only thing that happens is I get the device as a Qualcomm QDLoader when I plug it into a PC.
Please help and thank you in advance!
have you solved it?
codahq said:
This did not work for me. I have tried it while it is plugged into the PC, plugged into a charger or not plugged in. While plugged into the PC the "Qualcomm HS-USB QDLoader 9008" device on COM3 disappears periodically and then comes back so I can tell there is some life in it. This is extremely frustrating. The device froze while inside a game. The last image rendered stuck on the image for about 15 minutes until I did a hard reset by holding power down and the power button. The device has never turned back on since.
The only thing that happens is I get the device as a Qualcomm QDLoader when I plug it into a PC.
Please help and thank you in advance!
Click to expand...
Click to collapse
i've got the same problem, how did you fixed it? i can't get to the recovery mode. only when i plug it to the computer shows this "Qualcomm HS-USB QDLoader 9008" device on COM3.
please help
Related
I went to flash a kernel via fast boot it was going all good till i tried to boot it up since then ive tried 3 computers they dosent recognise it the charger won't charge it wont go into fastboot and the only thing it dies is vibrate and show blank screen it dosent show any light from the power switch not even a red one any fixes i no about Alejandrissimo but idk if he can fix this one I think my play is dead does anyone have anything I could do and if I took it the pace I got it from what would they say would they repair it or what or maybe replace it on the spot the bootloader was unlocked BTW running ics
what happens if you hold search when plugging in the usb cable?
chevyowner said:
what happens if you hold search when plugging in the usb cable?[/QUOTE
Nothing I wish it did then i could fix the fu***** thing
Click to expand...
Click to collapse
try taking the battery out and replace the hold search and plug in usb cable but never touch the power button
tried that
if i too
k it to the local store i got it from would they give me a new one???
Use flashtool to restore to default firmware. Then re try
IMO it is not bricked, BUT you need to reflash the kernel or flash a different kernel. not sure if this applies to the R800 but do you have a charge only cable?
chevyowner said:
IMO it is not bricked, BUT you need to reflash the kernel or flash a different kernel. not sure if this applies to the R800 but do you have a charge only cable?
Click to expand...
Click to collapse
Computer dosnt recognise it and it dosent enter fastboot and already tried flashtool
extremetempz said:
Computer dosnt recognise it and it dosent enter fastboot and already tried flashtool
Click to expand...
Click to collapse
Did you download the proper ftf file for your phone and place it in the "firmware" folder?
This happened to me. Get flash tool and do not connect t until it prompts you. So select the file you wanna flash and such and at the end then connect your phone itll work. Just take your battery out each time you fail to make sure your phone is off. Believe me I was worried to but for some reason that trick worked.
Sent from my Play using xda app-developers app
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
Oh I forgot... hold the back button to make it enter flash boot (different that fastboot when you are holding search) flash the stock firmware so you can start over.
Sent from my Play using xda app-developers app
I know you mentioned Alejandrissimo, so I just want to ask, how long did it take for him to get your Google Talk invite? I contacted him by the website and it told me that it cost 24 USD and to add him on Google Talk, I sent him $24 through paypal, the transaction completed according to the site so I'm sure he got it, but I've been waiting on Google Talk for about 3 hours now. I'm sure he's probably busy right now though. Just curious.
Okay, but the computer doesn't recognize the PHONE!
When I connect the phone to the computer, the LED flashes red and the computer says there is something plugged, but not identified, preventing the flash boot.
Now i can connect the phone to the PC, but only lights up the green LED (charging, i guess), even if i hold the "back" or the "search" button while plugging the USB.
This LED is the only proof of, at least, it is receiving energy.
Konae said:
Now i can connect the phone to the PC, but only lights up the green LED (charging, i guess), even if i hold the "back" button while plugging the USB.
This LED is the only proof of, at least, it is receiving energy.
Click to expand...
Click to collapse
I still can't figure out what's happening. Please someone help me!
Konae said:
I still can't figure out what's happening. Please someone help me!
Click to expand...
Click to collapse
plug in phone holding search button if pc recognize it and if you have adb drivers installed flash any kernel you want
creative_md said:
plug in phone holding search button if pc recognize it and if you have adb drivers installed flash any kernel you want
Click to expand...
Click to collapse
>>
Konae said:
Now i can connect the phone to the PC, but only lights up the green LED (charging, i guess), even if i hold the "back" or the "search" button while plugging the USB.
This LED is the only proof of, at least, it is receiving energy.
Click to expand...
Click to collapse
THANK YOU!
MGSBigBoss said:
This happened to me. Get flash tool and do not connect t until it prompts you. So select the file you wanna flash and such and at the end then connect your phone itll work. Just take your battery out each time you fail to make sure your phone is off. Believe me I was worried to but for some reason that trick worked.
Sent from my Play using xda app-developers app
---------- Post added at 03:12 AM ---------- Previous post was at 03:08 AM ----------
Oh I forgot... hold the back button to make it enter flash boot (different that fastboot when you are holding search) flash the stock firmware so you can start over.
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
FINALLY. Your advice worked. I did the same thing the OP did, flashed a kernal from cm9. I couldn't even get the charger to recognize or do anything. After taking battery out and starting flashtool process first, It took 4 times with flashtool. Thanks again.
Beanerman said:
FINALLY. Your advice worked. I did the same thing the OP did, flashed a kernal from cm9. I couldn't even get the charger to recognize or do anything. After taking battery out and starting flashtool process first, It took 4 times with flashtool. Thanks again.
Click to expand...
Click to collapse
It is not working for me. Could you guys give some more details of how you did it? I have tried already like 15 times and no luck. Also, is it happening to you guys that the phone will ONLY go into flashmode? I can flash anything into it but it will not boot, it will just stay in flashmode.
What I am doing is basically have the phone without battery and then start flashtool until it asks me to connect the phone. At that point I place the battery and connect the phone to the usb without pressing the BACK key, as it is not needed in my phone. Once the flashing is done, the phone goes into flashmode again.
Did this happen to you too?
Cesarramson,
Yep, sounds familiar. Is your phone unlocked? Is it r800x or another?
Sent from my DROIDX using xda premium
I got this problem too when i'm flashing doomkernel. Will try this when i got home. i hope it will fix my problem.
Today I rooted my T-999, which had been running 4.3. Used saferoot to do so, then installed SuperSU, then flashed CWMR. All reported success, and there were no immediate indications of a problem.
After a couple hours, I manually commanded the phone to reboot. It shut down, but never rebooted. I let it go a few minutes, and then tried to boot it with the power button. No luck.
I've since played around with removing the battery, plugging it in without the battery, and a couple other combinations. In all cases, the phone won't boot. No light, no recovery/bootloader, nothing at all.
Any new ideas about how to restart, what order to remove the battery, plug in, etc. that might help? THANK YOU.
After some searching, I have not been able to find a situation quite like mine. I'm sure I've just missed it -- if the new post annoys you, sorry. I need help.
Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.
Perseus71 said:
Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.
Click to expand...
Click to collapse
Thanks for the reply - Haven't been able to get it to boot in DL or recovery mode unfortunately.
Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk
serio22 said:
Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, nothing when I plug it in on USB. Can't get adb to recognize it either.
buzban said:
No, nothing when I plug it in on USB. Can't get adb to recognize it either.
Click to expand...
Click to collapse
Try the unbrick thread
Sent from my SGH-M919 using Tapatalk
hello friends. i flashed tethered cyanogen mod 11 with bumped twrp recovery. dont know what happened. the installation was smooth. however after i wished to flash another custom rom i couldnt get into recovery. it gave me oot sector verify secure boot error. i tried download mode to flash stock with lg flash tool 2014. but it is also not detecting the device in any com41.. adv is detecte but nothing else. i researched and could make it that i accidentaly deleted my "laf" partition. so i need a link to any guide of how to restore that.
thanks all. but in need of help :crying::crying::crying::crying:
[email protected] said:
hello friends. i flashed tethered cyanogen mod 11 with bumped twrp recovery. dont know what happened. the installation was smooth. however after i wished to flash another custom rom i couldnt get into recovery. it gave me oot sector verify secure boot error. i tried download mode to flash stock with lg flash tool 2014. but it is also not detecting the device in any com41.. adv is detecte but nothing else. i researched and could make it that i accidentaly deleted my "laf" partition. so i need a link to any guide of how to restore that.
thanks all. but in need of help :crying::crying::crying::crying:
Click to expand...
Click to collapse
I think you flashed the boot.img instead of just booting it. have you tried doing the button thing to get into recovery
powerdown(pull out battery)
press and hold volume- and power untill you see the lg logo, then release and press and hold volume- and power, then chose yes and yes(with volume+, volume - and the power button) and you should be in twrp
Yeah tried the button combo. But instead of twrp or factory reset it gives boot certification error. Secure boot verify.
same thing what did you do to fix this??
[email protected] said:
Yeah tried the button combo. But instead of twrp or factory reset it gives boot certification error. Secure boot verify.
Click to expand...
Click to collapse
markslo112 said:
same thing what did you do to fix this??
Click to expand...
Click to collapse
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
suljo94 said:
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
Click to expand...
Click to collapse
can't do neither of that, if i try download mode the phone shows the same error and turns off. The PC recognizes the phone as "Qualcomm HS-USB QDLoader 9008(COM5). The screen on the phone however is turned off.
markslo112 said:
can't do neither of that, if i try download mode the phone shows the same error and turns off. The PC recognizes the phone as "Qualcomm HS-USB QDLoader 9008(COM5). The screen on the phone however is turned off.
Click to expand...
Click to collapse
you are screwed because you need to send it in(not really fixable)
suljo94 said:
try to get to download mode or fastboot
vol up while inserting usb cable and quote be next time I can't check every answer individually
Click to expand...
Click to collapse
suljo94 said:
you are screwed because you need to send it in(not really fixable)
Click to expand...
Click to collapse
Yeah I know...I will send it in tomorrow, but I doubt they will repair it for free because I messed with it and they will probably see I did something I shouldn't do to the phone. What should I say when I turn it in? Probably best if I say I tried to update it and something went wrong?
First things first, NEVER RESTORE A TWRP BACKUP YOU CREATED IN ONE VERSION IN ANOTHER VERSION.
Now coming to my situation, I installed the Deodexed Stable Zui Oreo ROM but as usual got bored with the zui and wanted to go back to my fav Pixel experience Rom so I clean flashed it from the unofficial hendibudi recovery but I couldn't use my internal storage and I once earlier read in another thread that installing 3.0.3 decrypts it so I installed that recovery and clean flashed AEX5.2 Rom this time and same internal storage problem continued so my lazy ass thought I'll restore the TWRP backup I created when I unlocked the bootloader instead of flashing through qfil and that was my mistake.
I created the backup on 3.1.0 but now I was on 3.0.3 so as soon as I restored the backup and rebooted, my phone didn't turn on, no zuk logo or led or anything, if I long press the power button it just vibrates and the led flashes for a sec, that's all.
Edit: feels like this thread belongs to the News/Discussions section than here but meh
Edit2: Solution in Post #4
It seems like qfil, mi flash method is last as your bootloader is also corrupted, and this happens because there are many critical hidden partition on our device so it mess up, when you install first twrp releases, you will notice there are 7 8 partition and in latest one they all are hidden.
narshi shukla said:
It seems like qfil, mi flash method is last as your bootloader is also corrupted, and this happens because there are many critical hidden partition on our device so it mess up, when you install first twrp releases, you will notice there are 7 8 partition and in latest one they all are hidden.
Click to expand...
Click to collapse
well if it's that easy I wouldn't be worried at all but unfortunately my situation is a bit different, I can't flash anything as my phone is recognized as 900E, to flash anything the phone should be recognized in 9008(edl) mode and for that I have to strip the cable and short circuit with it and all that, which is really a hit or miss kinda situation so kinda worried!
But seems like I have no other choice so let's see what happens, I tried stripping the stock usb cable and it got split into half lmao
now I'll buy another cable and will try the copper wire method instead of splitting it
Edit: yeah ik that different versions of TWRP are different but I wanted to restore only the data partition and my data was already encrypted so I thought I have nothing to lose, I was like if it doesn't work I'll flash the full firmware again but didn't expect it to fully brick the phone
Okay the primary reason for me creating this thread was to let y'all know how I bricked my device so that y'all won't repeat my mistake but I saw some people here and there recently asking how to resurrect their device so thought I'll share how I got mine working wishing it'll help such people.
My phone was completely dead, the hardware buttons weren't doing anything, the phone doesn't power off but all I could see was a black screen, so I had to follow THIS GUIDE.
But the above situation is a rarity, I guess most of you ppl could get to the zuk logo or your led keeps flashing and you can use your hardware buttons, in such situations, follow THIS GUIDE.
The above links are for you to get your phone to 9008 mode to be able to flash the stock firmware, but if you don't know how to flash,
refer THIS GUIDE.
Flashing problem
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
seetharam55555 said:
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
Click to expand...
Click to collapse
Only one solution is there.. after u get sahara error.. disconnect your phone and cable, then again turn your phone on. And then turn it off... After that press volume up+ power button simultaneously while connecting to the usb port, if you are successful, within 2-3 seconds you have to press the download button on QFIL.. then it should work... You can try 2-3 times... For demo, but thia is the only way out of this hard brick
.. i suffered in the sahara error for 3 days since i flashed OOS on my z2 , till today i finally got the solution
sidS6 said:
Only one solution is there.. after u get sahara error.. disconnect your phone and cable, then again turn your phone on. And then turn it off... After that press volume up+ power button simultaneously while connecting to the usb port, if you are successful, within 2-3 seconds you have to press the download button on QFIL.. then it should work... You can try 2-3 times... For demo, but thia is the only way out of this hard brick
.. i suffered in the sahara error for 3 days since i flashed OOS on my z2 , till today i finally got the solution
Click to expand...
Click to collapse
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
seetharam55555 said:
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
Click to expand...
Click to collapse
Not 2 minutes but i think 30 seconds at max.. and by successful i mean that you get into Qualcomm 9008 qdloader mode in qfil
---------- Post added at 05:13 PM ---------- Previous post was at 05:11 PM ----------
The main thing is you have to immediately press the download button(within 2-3 seconds) after reconnecting into 9008 mode
Briked my phone flasing oos, solved it in the first go usimg qpst method.
Rahil4321 said:
Briked my phone flasing oos, solved it in the first go usimg qpst method.
Click to expand...
Click to collapse
You didn't got Sahara error?
seetharam55555 said:
thanks for response.What do u mean by "succesfull".and other thing to turn off the phone it takes me nearly 2 min constant pressing of power button, is this normal.
Click to expand...
Click to collapse
Were u able to unbrick?
Thanks
sidS6 said:
Were u able to unbrick?
Click to expand...
Click to collapse
yes it worked but as u said we have to hit download button within 2 sec....thank you very much u nearly saved 1000 rupees for me.
seetharam55555 said:
yes it worked but as u said we have to hit download button within 2 sec....thank you very much u nearly saved 1000 rupees for me.
Click to expand...
Click to collapse
Congrats bro! But i lost my 3 cables in ths process.. that equals 700 rs.. but i learned a great lesson? no probs
seetharam55555 said:
i got phone into 9008 port following ur guide and installed qfil everything went good problem is after hitting download buton in qfil after some time it says error "sahara failed".
Click to expand...
Click to collapse
dude just cut the cable and make intersection betwwen vlack and gree wire and put the cable into phone , got edl mode simple ways
sidS6 said:
Congrats bro! But i lost my 3 cables in ths process.. that equals 700 rs.. but i learned a great lesson? no probs
Click to expand...
Click to collapse
Why did you wasted 3 cables for?
seetharam55555 said:
Why did you wasted 3 cables for?
Click to expand...
Click to collapse
Coz while spliiting, one got split into half ? and the other one got bent so it was unusable.. i had buy the third one
sidS6 said:
Coz while spliiting, one got split into half ? and the other one got bent so it was unusable.. i had buy the third one
Click to expand...
Click to collapse
Ohh you tried that method i did like this
sidS6 said:
You didn't got Sahara error?
Click to expand...
Click to collapse
You don't need to flash via qpst when you see logo but device wont boot it mean you locked your bootloader so all you need to do is unlock it again that's all
Nirmal0001 said:
You don't need to flash via qpst when you see logo but device wont boot it mean you locked your bootloader so all you need to do is unlock it again that's all
Click to expand...
Click to collapse
Unfortunately learnt this after unbricking my device
I had installed RR mix rom in my Zuk Z2 plus. while trying to enter fastboot mode, it went off. Now it is completely dead. not being recoganized in my PC.In device manager it is not shown. Tried to deep flash through Qfil, but didn't recoganize port.If i plug in charger also no LED indication, If I disconnect battery & plug in for charging, white LED slowly blinks, in the same mode if I connect charger blinking white LED continues. But once I remove charge & reconnect it shows nothing. again if I remove battery & reconnect, again white LED starts blinking. Apart from this nothing is shown, phone completely dead. Can anybody help please. I tried through Qfil, tried by shorting black & green cable, all types of key combinations.
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF