Followed absolutelygrimm unbrick/downgrade methods but made silly mistake and screen remains black after last step. the phone is stuck in qdl mode, can't spam also. So my question is, will the phone get out of qdl mode if battery is totally drained???? TIA:good::good:
Do you have another pc to repeat the process?
I had that issue as well and it was an incompatibility between ubuntu and the USB-chipset.
Raptylos said:
Do you have another pc to repeat the process?
I had that issue as well and it was an incompatibility between ubuntu and the USB-chipset.
Click to expand...
Click to collapse
It worked only once on my desktop and i was able to perform the downgrade process to the end. However, it was failure and i was unable to repeat the process on the desktop. After that I tried it on a laptop and it didn't work. I will try more on my neighbor's computer and see how it goes.
Thank you very much for your response. :good:
Confused
khampaman said:
It worked only once on my desktop and i was able to perform the downgrade process to the end. However, it was failure and i was unable to repeat the process on the desktop. After that I tried it on a laptop and it didn't work. I will try more on my neighbor's computer and see how it goes.
Thank you very much for your response. :good:
Click to expand...
Click to collapse
During enumerating section, the phone goes form Qualcomm Gobi..... (qdl) to qualcom inc. and the spamming still does not work. what am i doing wrong?
Expensive paper weight?????
Did i break it??? :crying:
Identical thing happened to mine. I'm still stuck in QDL mode myself. I have tried everything, but nothing works.
I found someone online that will restore the phone for $50, guess I will need to try that next.
I also waited 4 days for the battery to drain, it did nothing to help.
help
mycomputerisjunk said:
Identical thing happened to mine. I'm still stuck in QDL mode myself. I have tried everything, but nothing works.
I found someone online that will restore the phone for $50, guess I will need to try that next.
I also waited 4 days for the battery to drain, it did nothing to help.
Click to expand...
Click to collapse
In the same situation. Did you get it fixed? I've done this twice before and worked perfectly. Now this time I finished all the steps but the charge light never came back on. i tried to start from the begining but now it won't list the sd*12/sd*4 when i type ls /dev/sd*. i've tried holding power for 10sec, replugging, different computer, waited 2 days, etc. Is it completely bricked?
squirt22 said:
In the same situation. Did you get it fixed? I've done this twice before and worked perfectly. Now this time I finished all the steps but the charge light never came back on. i tried to start from the begining but now it won't list the sd*12/sd*4 when i type ls /dev/sd*. i've tried holding power for 10sec, replugging, different computer, waited 2 days, etc. Is it completely bricked?
Click to expand...
Click to collapse
yes, unfortunately so.
You will have to take it to a JTAG service or carrier/HTC, who might bill you for it.
Related
I need real help guys.
Last night i change my desire s to s-off and rooted it. I then decided to stop the processing and went to unroot it, by loading a stock rom back onto the phone.
Everything seemed to go fine, i switched the phone back on and everything looked fine although the superuser was still on the phone.
The phone then sporadically started turning on and off and when i tried to enter a few menus i was greeted by android.process.media has had to stop etc and there was another one.
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.
ajtaylor09 said:
I need real help guys.
Last night i change my desire s to s-off and rooted it. I then decided to stop the processing and went to unroot it, by loading a stock rom back onto the phone.
Everything seemed to go fine, i switched the phone back on and everything looked fine although the superuser was still on the phone.
The phone then sporadically started turning on and off and when i tried to enter a few menus i was greeted by android.process.media has had to stop etc and there was another one.
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.
Click to expand...
Click to collapse
Hey did you tried adb .. does it shows your device..
Check it, search forum for adb setup..
then
open cmd
adb devices - to see if adb recognizes your device
adb bootloader - to get into boot loader menu
if you successfully get into boot menu try flashing once again RUU(check in DS Delvelopment section)
else you are S-ON , i guess after flashing Stock ROM..So better to give in customer service center
I can't understand and get the adb to work
ajtaylor09 said:
I cant get a charge LED and when plugged into the laptop it makes a funny jingle from the laptop and not the duh duh that you would normally get when plugging a usb device in the laptop.
Click to expand...
Click to collapse
Remove the battery. Wait about 30 seconds and put it back in. Then press and hold the "Volume down" button. Press the "Power" button wait a little and let go. Do not let go the "Volume down"! If it works the phone will boot to the Bootloader. Then check the version (it has to something like 6.98.1002) and post it here. After that try to select Recovery from the menu. Then we will see what will come next
Nothing! Dead as a door knob
ajtaylor09 said:
Nothing! Dead as a door knob
Click to expand...
Click to collapse
If it makes a sound on connection to the PC you can try to start a RUU but most probably it will not work...
So you next step is the repair center then
Is it going to cost alot or is it worth just buying a new desire s?
ajtaylor09 said:
Is it going to cost alot or is it worth just buying a new desire s?
Click to expand...
Click to collapse
As far as I know the reapair is about 1/3 of the phone price. But you can skip the "custom software flashing" part and say only this:
At 6am this morning the phone started vibrating and froze so i turned it off, ive now tried to turn it back on to change it back to normal, but the phone now wont turn on.
Click to expand...
Click to collapse
If you are a good liar they will repair it under warranty
Since it is completely dead and probably the technicians will not bother to analyze the problem, most probably they will replace the motherboard (eMMC). Good luck...
I have now sorted the adb problem out and install the drivers onto the laptop (no more jingle)
How do i try your first suggestion?
ajtaylor09 said:
I have now sorted the adb problem out and install the drivers onto the laptop (no more jingle)
How do i try your first suggestion?
Click to expand...
Click to collapse
ok. open cmd (command prompt) and type:
Code:
adb devices
if it connects the output sholud look someting like this:
HAJ45345L35H device
you can try the same with
Code:
fastboot devices
and look for the same output
btw is your device branded?
Yes was 3 branded
im getting adb is not recognised.
ajtaylor09 said:
im getting adb is not recognised.
Click to expand...
Click to collapse
There is a guide in my signature. It is quite easy. Try it.
If you have flashed a non branded RUU to your branded phone there is nothing you can do even if you manage to connect it to the PC. It will be completely messed up. No offense but since you have difficulties with an adb setup all the advanced methods will be very hard for you. So my suggestion is to go for a repair (if you have warranty) and try with the story that is just stopped working...
But of course it is up to you to decide
completed the adb and says device not found
ajtaylor09 said:
completed the adb and says device not found
Click to expand...
Click to collapse
@amidabuddha (@ajtaylor09)
Look again like another valiant effort, although does sound like your dealing with a brick this time, as you've already pointed out there are benefits here in that the service centre should take device under warranty and either replace or put in new motherboard. No questions asked...but as long as no daft answers are given
Hi,
yesterday I pulled my One S out of my pocket, opened up the browser, made a search on google and all of a sudden, while the page was loading the screen turned off, completely black. The capacitive buttons stayed awake for 4-5 seconds, then they turned off too.
Completely dead, the phone won't turn on anymore, not even in recovery mode. If I connect the wall charger the charging led doesn't light up, although I can feel the phone is heating (as usually happens when charging).
I've tried connecting it to the pc via usb and windows after a while, detects a peripheral named "qhsusb_dload". I've read on google that this isn't any good... Anyway, even connected to the pc (for hours) the charging led doesn't light up.
No signs of life from my One S... :crying:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
There's no way I can enter bootloader. The phone shows no signs of life (no capacitive buttons, no charging led, nothing at all)...
One thing that maybe is important: for about a month, I've been experiencing a strange battery drain. The drain used to occur even if the phone was in deep sleep (I'm sure about this because I've checked with cpuspy and anyway I hadn't installed any new apps for quite a while), at a rate of 7-8% each hour. I could leave the phone on the desk with screen off and in standby (no 3g data, no wifi, not even cellular network) and the drain was still there.
By the way, when my phone died I had plenty of battery left, about 70%.
nor-ric said:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
Click to expand...
Click to collapse
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
dc211 said:
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
Click to expand...
Click to collapse
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
nor-ric said:
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
Click to expand...
Click to collapse
Think of qhsusb-dload kinda like your normal PC without windows. Your phone could not find an operating system to boot into and defaulted to qhsusb-dload mode waiting for a command. Our problem is that we don't really know the commands for qhsusb-dload nor do we have the files needed to use it only the manufactures do.
They can't swap a s4 chip for a S3 version that isn't the same product.
Most likely it the micro USB charging port that's gone toast.. happened to mine exact same symptoms. I was actually unlocked, HTC dev unlocked too, running a custom ROM as well as custom recovery and splash screen. I still sent it in repair with hope of they will never be able to turn the damn thing on to discover my deeds and will replace my phone but they didn't mind, they reflashed stock rom after repair and sent it back but I was still s-off
Send it into repair mate. Best option instead of tinkering with it lol
Sent from my HTC Sensation using xda premium
Nope, there is a solution.
http://unlimited.io/qhsusbdload.htm
Sent from my HTC One S+
Ok, thanks everybody.
I'm going to try usaff22's method and if that doesn't work I'll send the phone in.
I'll let you know! :fingers-crossed:
It didn't work. The terminal waits for the device, however it doesn't respond...
I'll have to send the phone in.
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Darknites said:
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Click to expand...
Click to collapse
Where can I find the guide you're referring to?
Thanks.
nor-ric said:
Where can I find the guide you're referring to?
Thanks.
Click to expand...
Click to collapse
Here you go, Downgrade/Unbrick.
Darknites said:
Here you go, Downgrade/Unbrick.
Click to expand...
Click to collapse
I've read that thread: do you mean I should try the 9th point?
you can open a new terminal window and run the following command IF AND ONLY IF the phone doesn't reset out of QDL mode
Code:
$ sudo ./emmc_recover -r
Click to expand...
Click to collapse
nor-ric said:
I've read that thread: do you mean I should try the 9th point?
Click to expand...
Click to collapse
No that for flashing Hboot think you want step 12 but will need to edit the file the download has but you will need to do step 3 so you can do step 12. I have no idea if it will work but its an idea and also might be best to ask about it there too before doing anything.
thanks a lot touch of jobo i was going to get crazy :laugh:
touch of jobo said:
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
Click to expand...
Click to collapse
that worked for me. thanks a lot
btw. maybe someone can answer this: how come that the phone goes in download mode?! I had the phone unused the last hours before I recognized it wasn't on anymore? Does this just happen? I am on CM11 Nightlies atm.
Hello, I was flashing cm-11.0-XNF9XBS28K-bacon-signed on my opo and something went wrong on recovery, it was like rom flashing went wrong and it didn't happen, so I went to wipe and I'm pretty sure that I selected everything in wipe section, literally everything and hit the reboot button, and my phone won't wake up, no response, tried to press buttons in every combinations for maybe 1 min? My computer won't recognize my phone, nothing happens, no vibration, no sound ;x I think I erased everything, but is it possible to delete bootloader that way? Btw my battery was charged to about 90%.
I tried charging in for about 14hs and nothing happened, phone and charger during this time were cold. I tried to recognize it by Windows 10/XP and Ubuntu but no reponse from phone, so I coulnd't use this magical method with qualcomm port and drivers, and then this Color. Is it really bad hardware brick?
Have you tried this thread by any chance? Hopefully it works. Worked for me when I bricked mine by flashing hydrogen
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
I tried, but my PC can't detect my phone in any state.
latuch91 said:
I tried, but my PC can't detect my phone in any state.
Click to expand...
Click to collapse
Can you try long pressing the power button for 10 seconds or more to turn it off. Then long press the power button and connect to a PC and see if it responds
Sent from my A0001 using Tapatalk
Ok I will try, but I tried before some combinations with buttons and connecting to PC, now I'm testing "dead battery" so 12hrs without touching and 6 hrs charging and then unplug and plug again. But I'm almost convinced that it's something with mainboard I talked to OP and they said that they will exchange my phone If it happened during flashing Cyanogen ROM.
//Still no respond from the PC and phone. Completely dead.
Dont worry, they wont know u had twrp if the phone is hard bricked. Just carry on your RMA process. Good luck...
Today's remote session went as I thought will be, did almost everything as this technician. Now awaiting RMA ticket.
latuch91 said:
Today's remote session went as I thought will be, did almost everything as this technician. Now awaiting RMA ticket.
Click to expand...
Click to collapse
hello i hard bricked my opo two days ago but its ok now plz follow this
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
malikzafar said:
hello i hard bricked my opo two days ago but its ok now plz follow this
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
:good: Used this thread twice now and it saved my phone. Give it a shot.
Hi everyone,
I've been on one heck of a journey with this oneplus one that my wife cracked the screen on. I got that replaced and had it up and running except that it was not able to connect to a network. After doing some searching it seemed like maybe corrupt OS or other software so I started trying to bring it back to stock using the Oneplus toolkit. I got it in fastboot mood but then when I tried to exit that and reboot to recovery the screen went black. The only response I can get out of it now is vibrating if I hold the power button for 10-15 seconds. The same thing happens if I do that plus vol up or vol down. The computer does not recognize the phone. I've tried on a win 8.1 and win 7 machine and I did put the comp into test mode for uploading drivers. I've tried the power+volume trick for getting it to show up and still nothing. The last time it had booted it said something like 70 some percent of battery (I know that can be wrong though).
I'm wondering if this situation is one that seems it needs 12 hours of not being touched, 6 hours of charging, unplug and replug or if this thing is beyond repair. I didn't have too high of hope for it with the no service issue but it would be nice to get at least back to where I was for further troubleshooting. Can anyone point me in the direction of getting a computer to recognize this or tell me what I'm doing wrong? Every other thread I've found people say "Oh it just recognized it suddenly" and I'm not getting that lucky. Thanks for any assistance you can provide!
Ben
Try this: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Keep trying solutions from our forums...they do work eventually
ryanmat said:
Try this: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Yeah I had seen that one too. I do have an old xp laptop. Maybe i'll give that a shot tonight. If that doesn't work should I assume the battery is low and do that procedure before continuing with the ColorOS restore option?
Okay, so I know this has been posted a lot but I am pulling my hair out!! :crying:
So this is what happened, I downloaded this app from google play. It had 4.8 rating, whatever. But it's purpose was to, keep your game playing in the background when your screen is locked. Everything was working fine, until my phone lagged and restarted, I got it to turn back on like normal. But then, random shut offs has been happening ever since.
I decided to do a factory reset on my phone, it was okay for a day, but when I played a game on the phone, it crashed
and shut off again.
Now it won't open, i tried everything! and when I say everything, I mean every basic way to restart it. Except flashing it. Because it can't even turn on on it's safe mode. it has been on a coma for 3 hours now, it is plugged now on its original power brick and chord.
My pc doesn't recognize it.
I have 2 questions, will I still be able to fix this? And, can a technician fix this. Like 100% fix it when I decide to go to a tech tomorrow?
Cheskii said:
Okay, so I know this has been posted a lot but I am pulling my hair out!! :crying:
I have 2 questions, will I still be able to fix this? And, can a technician fix this. Like 100% fix it when I decide to go to a tech tomorrow?
Click to expand...
Click to collapse
Try after few hours and check if the pc detects it. Technician can fix it but try one time on the pc tomorrow before your leave for technician. Also change the usb cable and try.
superac11 said:
Try after few hours and check if the pc detects it. Technician can fix it but try one time on the pc tomorrow before your leave for technician. Also change the usb cable and try.
Click to expand...
Click to collapse
Thanks! I already tried changing the cable, I will try again once I get home. But, if it won't work, I'll go for the tech. Do I have to go to a oneplus tech? or any mobile tech can do? I read that this is "Hard brick" and somewhat impossible to fix. I really just need something to calm me down. LOL! so you telling me that a tech can fix it for sure, made me a little less worried.
Cheskii said:
Thanks! I already tried changing the cable, I will try again once I get home. But, if it won't work, I'll go for the tech. Do I have to go to a oneplus tech? or any mobile tech can do? I read that this is "Hard brick" and somewhat impossible to fix. I really just need something to calm me down. LOL! so you telling me that a tech can fix it for sure, made me a little less worried.
Click to expand...
Click to collapse
Best will be sent to oneplus if accessible either you have warranty or not. If that's a hardbrick then you can't be sure if you local technician can fix it.
Cheskii said:
Okay, so I know this has been posted a lot but I am pulling my hair out!! :crying:
So this is what happened, I downloaded this app from google play. It had 4.8 rating, whatever. But it's purpose was to, keep your game playing in the background when your screen is locked. Everything was working fine, until my phone lagged and restarted, I got it to turn back on like normal. But then, random shut offs has been happening ever since.
I decided to do a factory reset on my phone, it was okay for a day, but when I played a game on the phone, it crashed
and shut off again.
Now it won't open, i tried everything! and when I say everything, I mean every basic way to restart it. Except flashing it. Because it can't even turn on on it's safe mode. it has been on a coma for 3 hours now, it is plugged now on its original power brick and chord.
My pc doesn't recognize it.
I have 2 questions, will I still be able to fix this? And, can a technician fix this. Like 100% fix it when I decide to go to a tech tomorrow?
Click to expand...
Click to collapse
Did you try holding key combination while connecting to the PC or you just connected it to the PC and nothing happened?
ekin_strops said:
Did you try holding key combination while connecting to the PC or you just connected it to the PC and nothing happened?
Click to expand...
Click to collapse
I tried holding the key combination for a good minute, the power button embedded on my finger LOL! But yes, the PC did not detect anything.
superac11 said:
Best will be sent to oneplus if accessible either you have warranty or not. If that's a hardbrick then you can't be sure if you local technician can fix it.
Click to expand...
Click to collapse
Well, we don't have Oneplus "store" here, just resellers, and they don't offer warranties nor fixes.
I tried opening again, but it's still not responding.
Cheskii said:
I tried holding the key combination for a good minute, the power button embedded on my finger LOL! But yes, the PC did not detect anything.
Click to expand...
Click to collapse
Not the power button. Volume buttons. You can get in EDL mode that way and maybe it will be recognized if bricked. There are 2 possibilities, it's either brick or hardware damage. If bricked only, it can be unbricked. IF damaged, well, the Service center.
Try this:
Power your device off
Maintain volume up and volume down keys to get into Qualcomm EDL mode. So, Volume Up and Down together hold and plug the cable in while holding the buttons. If you get any detection, there is hope.
Use MSM Tool, of course with corresponding ROM for flash.