Related
Let me start by saying, Power + Home does not work. Yes, really. I know there are a dozen threads about Touchpads not turning on, and they all have "Hold power and home for 20s" as the reply. Please don't respond with "Hold Power and Home for 20s". I have tried it.
Background
I took my Touchpad with me on a road trip. I did not have an official car charger, but I had one rated at 1 amp. I used this charger with my Touchpad, and it said that it was not powerful enough (as expected). I figured I would let the Touchpad at least get some juice while it was not being used. The battery steadily drained over the next couple of days, to the point where the screen did not come on. I assumed this was because the Touchpad was completely drained.
Once I got to a location with an actual outlet I used the original Touchpad wall adapter and let it charge for a few hours. The screen still did not come on, and there was no response (sound/light/vibration) from any buttons. I let the Touchpad continue to charge over night with the same result.
The Touchpad has alpha 2 on it.
What I have done
I have tried:
Power + Home for 15s
Power + Home for 30s
Power + Home for 1min
Power + Vol Up for 15s
Power + Vol Up for 30s
Power + Vol Up for 1min
Power + Vol Up + Home for 15s
Power + Vol Up + Home for 30s
Power + Vol Up + Home for 1min
All of the above with and without the Touchpad being plugged in to the wall and PC.
Trying WebOS Doctor (does not recognize a device)
Trying novacom directly (does not recognize a device)
Letting the Touchpad charge for > 1 day and repeating all of the above
Letting the Touchpad sit on the Touchstone for > 1 day and repeating all of the above
Verifying that the AC adapter is secured properly and repeating all of the above
Changing the USB cable and repeating all of the above
Changing the AC adapter and repeating all of the above
Results
The only time I have gotten any indication that the Touchpad is actually doing something is when using Power + Vol Up (and Vol Down) with the Touchpad connected to the PC. Vol Up has the Touchpad recognize as Palm. Vol Down has the Touchpad recognize as QHSUB_DLOAD. If I have the Touchpad connected to the PC in one of these states, Power + Home will reset the device (and Windows will not recognize it until I use Power + Vol Up/Down again).
That is the only response I get from the Touchpad. Anything else I have tried results in nothing.
My current plan is to attempt to let the battery completely drain, and then charge it again. I was previously under the impression that my Touchpad was out of power, but the testing with Vol Up/Down has shown me otherwise. My hope is that losing all power will truly "reset" the device.
Does anyone have any advice on anything else I should try? Is there a way to recover the Touchpad via booting it as Palm or QHSUB_DLOAD?
Volume Up + Power while connected to PC, then run WebOS Doctor?
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Another method
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
DJ_SpaRky said:
Volume Up + Power while connected to PC, then run WebOS Doctor?
Click to expand...
Click to collapse
It may not have been clear since it came after the list, but I did try this. WebOS doctor does not recognize the device in any mode. I do not know if this is simply because I lack the necessary drivers when it is in one of the other device modes. On the off chance that I didn't I will try again when I get home.
Dbarker 2 said:
You may have done this, but have you tried pressing home first and then holding it and power together? I couldn't get mine to start by pressing power and then home, but when I held home first and then power it came right on. If you have done that then disregard this, but if not I hope it helps.
Click to expand...
Click to collapse
I do believe I have tried this, but I will try again when I get home.
FishDoc said:
Try power and Volume down. Hold for a minimum of 30 seconds before giving up. It has worked twice for me when all else failed.
FishDoc
Click to expand...
Click to collapse
It is my fault for leaving it out, but I tried this after exhausting the other options.
chrischoi said:
That was very thorough. Once my TP died completely. I plugged it in and it didn't do anything. When I held Power + hitting home 15 times, it would give mea low battery indicator.
I plugged it in and left it over night. By the morning it was on 100%.
Click to expand...
Click to collapse
I really wanted to avoid the slew of "Hold power and press home!" comments and the followups telling me to hold it longer, hold volume, and all of the other normally recommended fixes. I know how to write a bug ticket or two. I'm also the type of guy who posts a followup with what actually fixes the problem (No "nm, fixed it" from me).
It sounds like my current plan of action is going to mimic what you did. I originally thought the Touchpad was getting no power, so I kept trying to charge it. Now I am waiting for it to lose all power, so I can repeat the process after the device (hopefully) resets. I'm not sure how long that will take since I cannot actually use the device to drain the battery.
Thanks for the responses. Some replies are better than no replies.
So i had a similar situation and tried everything you had mentioned and all the suggestions in the thread. Nothing. No power, completely dead. I even left it
overnight on the charger... nothing. For sure i thought I bricked it. Then, I read online that someone tried the following:
Press and hold Power + Volume Up and click the card (menu) button a thousand times.
Wow! It worked! The TP is alive! In actuality, it only took about 30-50 times (not a thousand) of pressing the menu button while holding power + volume up.
I then got the white USB icon in the middle of the screen and then pressed and held the power + menu button to reboot.
What I did find interesting though is the battery was almost discharged even after having it on the supplied charger (not touchstone) overnight.
Anyway, hope this resolves your issue as well.
No go with Home + Power, Power + Vol Down, Power + Tapping Home
suremail said:
No go with Home + Power, Power + Vol Down, Power + clicking Home
Click to expand...
Click to collapse
Just making sure you read it right since you didn't list it above.
Power + volume up + clicking home button repeatedly.
All 3, same time. Just trying to help.
^ worked for me..thanks
Sent from my HTC Inspire 4G using XDA App
Well this is a really strange one...
Touchpad was completely non-responsive, I'd tried everything above about 5 times and it just wasn't showing any signs of life. I have left it charging all day today.
Assuming it was completely dead, I sat it down. 5 minutes later, it inexplicably just started booting up.
Wish I knew what I did, if anything to make it boot.
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Phillip Fry said:
I am having the same issue but what got me there was trying to restore my Touchpad via WebOs Dr. It would restore to like 60% or 80% and then say we were unable to reset your device. It kept failing and no ROM was on my the device anymore. When I hold Power+Vol Up+ Home I can hear my PC detect it but that is all it does.
When I get home tonight I am going to try some of the things in this thread.
But what if I cannot get it into recovery? I read that it is near impossible to brick a Touchpad. How can I still recover without getting into recovery?
http://forum.xda-developers.com/showthread.php?t=1394061
Click to expand...
Click to collapse
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
menting said:
not near impossible. I actually bricked mine and had to send it back for RMA.
it got to the point where the hp screen will show, and webos doctor will detect it, but it'll fail when trying to reinstall at about the same percentage as you (maybe less).
Click to expand...
Click to collapse
Well I installed Android uninstalled it. Then installed it again and forgot mboot then uninstalled it. So I belive I am back to stock but I wanted to upgrade to 3.0.4 then install Alpha 3.5 as I has having problems with the Touchpad rebooting in both Android and WebOS.
So when do I know if it is bricked. And what do I say to customer support to get it fixed? I just bought the Referbed ones off ebay the other day.
Here's an update...
No luck with anything so far. I caved and decided to take the Touchpad apart to disconnect the battery. I did this and still no screen response. The only changes have been it's a bit more difficult to get it into Palm mode (if it does at all), and now it seems that I can get into QHUSB mode just by repeatedly pressing the vol- button (no need to hold anything else). I do not know if the QHUSB thing was like that before disassembly, or if it is a result of me mucking around.
Unless anyone has any great ideas it looks like I will have to hope HP fixes it in order to tell me it is out of warranty for having Android.
If you send it to Hp and If they can't power it on, I'd say they would definitely replace it. Problem is, I doubt they have any more TP's in stock. Not sure how the warranty would work now being that its a discontinued product.
Hopefully after toying with it enough you'll figure it out and get it powered.
Mine is stuck in download mode too. Still no success.
Here's my experience so far.
Black screen.
When connected to PC :
Home + Vol UP - Device Manager shows PALM (with yellow exclamation) - no driver found.
Vol Down (no need to press home or power) - Device Manager shows QHSUSB_DLOAD (with yellow exclamation) - no driver found.
WebOS Doctor fails to detect device (palm ! in device manager)
I tried forcing novacom drivers on the Palm device (both novacom and novacom-bootie) and then running WebOS Doctor, still refuses to enable next button.
Tried connecting with novaterm, cannot find device. (both novacom and bootie driver).
Power + Home for 15 - 20 secs always resets and clears device from device manager.
I installed QHSUSB Drivers.
now when I Vol Down it installs as a com port (Qualcomm HS-USB QDLoader 9008).
I installed QPST_2.7.323 and am able to see the device as Q/QPC-XXX - ESN=*Download* - Phone Number=*Download* - Banner=*Download*.
I tried resetting the device with QPST, fails to complete the command.
I think I need a new boot.hex to flash to the TP, or a way to force it to charge (if that is the problem).
My Touchpad was low on power when I put it away in the car while on a road trip. I plugged it in to the wall the next day when it wouldn't turn on. After charging overnight, it still refused to power on. That's when I started combing the web for possible solutions.
Please stop posting irrational solutions, such as Power + tap home 5,000,000 times as the few times this did work for others, it was merely coincidence, and power + home would have worked also.
Any rational solutions are welcome.
I may just send it in for warranty. Although I bet that at HP, they will just hook it up to a machine with "special" drivers and re-flash it with Web-OS. I wish they would just let me do the repair myself with the appropriate files.
Who knows, maybe it is a hardware issue, but I doubt it.
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
skiinginstead said:
I'm having the same problems too. What happened on mine is that my webOS was crashing doing random things like watching videos so I figured I'd just reflash the whole thing. I rebooted and went into the webOS recovery and that's when I think I bricked it. All I got was a USB cable symbol and the touchpad was unresponsive. I couldn't make it do anything and I tried all the appropriate button holding combinations and so I let the power run out over night.
Now when I plug it into the wall all I get is a low battery charging symbol. If I hold the home+power button down the screen will turn off after about 20-30 seconds of holding it down. But when I try to boot into recovery by holding the power+volume up buttons, all I get is the same low battery charging symbol. I'll add that I have had it charging for most of the morning so I don't think it is low battery still. And when I unplug it from the wall I get a symbol of two pronged plug that shows for about 5 seconds and then disappears.
Now when I plug it into the computer, I get the low battery charging symbol for a quick second and then it flashes to the message telling me "To reliably charge, use the cable and power adapter that came with your device" in 5 different languages. When I run webOS doctor I get to the screen where you connect your phone to the usb but it doesn't recognize anything and doesn't let me click next. I was able to have my computer recognize the power+volumedown button as the weird Qhusab thing but my computer said it couldn't find any drivers for it. Now I am not able to reproduce that.
I'm not sure what else to try so if anyone has any suggestions, that would be great. Otherwise I'm going to have to try my luck with HP support.
Click to expand...
Click to collapse
Having the EXACT same problem....anyone have any solutions to this? WHy is this happening?
It's a long shot, but it might help if you are getting to the USB symbol on the Touchpad .
I spent hours trying to connect with no luck with the Touch pad in that state. I rebooted my PC and it connected to the TP right away. (I was using a Win 7 64 bit PC.)
Hi.
So I deleted gmail apk and put inverted gmail apk in system apps. Powered off the phone. Tried to power it back on, nothing happens.
Battery was almost full, about 95%. If I hold power button (tried for like 30secs) nothing happens. No LED, no vibrate, screen is black non-stop.
I also tried power& VOL-, power& VOL+, power & both volume... Nothing.
If I plug it into USB cable from PC, nothing. If I plug in the mains charger, nothing.
Tried holding VOL- (and later VOL+) and plug in USB cable from PC to get into download mode, nothing. Flashtool doesn't see the device.
What the HELL just happened? And what can I do?
Sony update service
tipsek said:
Hi.
So I deleted gmail apk and put inverted gmail apk in system apps. Powered off the phone. Tried to power it back on, nothing happens.
Battery was almost full, about 95%. If I hold power button (tried for like 30secs) nothing happens. No LED, no vibrate, screen is black non-stop.
I also tried power& VOL-, power& VOL+, power & both volume... Nothing.
If I plug it into USB cable from PC, nothing. If I plug in the mains charger, nothing.
Tried holding VOL- (and later VOL+) and plug in USB cable from PC to get into download mode, nothing. Flashtool doesn't see the device.
What the HELL just happened? And what can I do?
Click to expand...
Click to collapse
JUST DOWNLOAD THE UPDATE SERVICE FROM SONY , CHOOSE YOUR DEVICE AND FOLLOW THE INSTRUCTION AND MAYBE IT WILL GET YOUR PHONE WORK .
UPDATE SERVICE LINK
http://www.sonymobile.com/gb/tools/update-service/
Tried Sony Update Service, also PC Companion and flashtool.. The phone appears to be completely dead, like the battery is empty or not even connected. I don't think it's possible that the battery is empty since it had 95% of power when I switched the phone off..
Now that I think about it, it might be possible, that I turned the phone off, didn't wait for it to vibrate and immediately tried to turn it back on.. Does this somehow put the phone in "hard off mode" or something? I mean I'm just guessing here, because I really have no idea what to do :crying:
Hold power button plus volume until u feel 3 vibrates either the phone will come back on or at least u should be able to connect it to the pc opinion.
Sent from my C6603 using xda app-developers app
dante501 said:
Hold power button plus volume until u feel 3 vibrates either the phone will come back on or at least u should be able to connect it to the pc opinion.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
if your computer does not recognize your phone or vice versa your phone is hard brick (reinstall sony driver just to be sure), no other way to revive it unless you can get into recovery.
I had the same problem this morning. Itwas on charge overnight from the GPO and this morning, Nothing.
I tried two things. One was the update as suggested here (which is happening as I speak) and the other was to hold the button and the lower volume switch. I was doing these concurrently, with it plugged into my laptop and something worked. THANKFULLY.
I only got the phone about three weeks ago and this is the second time something like this has happened. First time it was totally dead and I had it swapped one for one. Worst part was I had spent some time updating my phone list etc which was subsequently lost (making me think I was working on my phone memory not the sim....)
I've just updated my NFC firmware, whatever that is, and it has gone into sleep mode. But at least it's working.
My longwinded explanation preceeds a short question.
Is this a common occurence with the Xperia Z?
My wife has exactly the same model only exception being hers is white, mine black. She has had no probs. Knew I shoulda gone the white one.
tipsek said:
Tried Sony Update Service, also PC Companion and flashtool.. The phone appears to be completely dead, like the battery is empty or not even connected. I don't think it's possible that the battery is empty since it had 95% of power when I switched the phone off..
Now that I think about it, it might be possible, that I turned the phone off, didn't wait for it to vibrate and immediately tried to turn it back on.. Does this somehow put the phone in "hard off mode" or something? I mean I'm just guessing here, because I really have no idea what to do :crying:
Click to expand...
Click to collapse
you have to wait at least 30 sec until you switch it on .leave the phone on the charger atleast for 3 hours try to uninstall and reinstall sony drivers . and then try to flash a stock rom using a flash tool
OK, the phone has been charging overnight (no led indication, charger was cold, so was the phone, so I doubt it's even been charging) about 10 hours. Reinstalled drivers, PC Companion, Update service and flashtool.
I tried these 4 options with 3 different variables (for 12 total combinations) 30 seconds each.
1) No cables connected
2) Mains charger connected
3) USB cable from PC connected:
hold [PWR] 30 secs
hold [PWR] + [VOL-] 30 secs
hold [PWR] + [VOL+] 30 secs
hold [PWR] + [VOL-] + [VOL+] 30 secs
After that, I also tried connecting the phone to USB cable to PC, each time with only 1 open program. First with flastool, then PC Companion, then Update Service with 3 different variables (for a total of 9 combinations). 30 seconds each:
without pressing/holding any buttons
hold [VOL+] while connecting
hold [VOL-] while connecting
Also tried a different USB port and cable, but it's 100% not the PC/drivers/USB cable.
No matter what I tried, nothing happened. Screen on the phone is dead all the time, LED light is dead, no vibrations, no sounds, nothing. Also when trying the PC connected options, no sounds, indications of drivers installing/failing, no activity in my computer, NOTHING on PC.
Are there any more options to try? Or must I send the phone in for repair?
And once again, does anyone know if turning off the phone and NOT waiting for it to vibrate and immediatelly trying to turn it back ON, somehow causes this "dead phone"?
No more ideas? Am I the first one to have this issue?
tipsek said:
No more ideas? Am I the first one to have this issue?
Click to expand...
Click to collapse
Seems like you have tried every known possible way to revive it, I think its time you sent it to Sony to have it fixed... I doubt anyone else can help you from here... Good luck.
Sent from my GT-N7100 using xda premium
I'm afraid to send it because I rooted the phone and my country service centres are known to deny warranty repairs for pretty much any reason they can find.. Sometimes they even make up something.. That's why I was hoping I could somehow fix it.. But yeah, seems there is no way I can do it, so I will have to send it in. Will report what happened.
To be fair, if it wont show on computer or boot up, short of them fixing it then checking, there is no way for them to see it has been rooted?
Xperia Z
That should be correct, but thats exactly what im afraid of. Lets say the battery died for instance. They replace it boot up the phone see its rooted and send me a bill. I hope this wont happen, we shall see..
tipsek said:
That should be correct, but thats exactly what im afraid of. Lets say the battery died for instance. They replace it boot up the phone see its rooted and send me a bill. I hope this wont happen, we shall see..
Click to expand...
Click to collapse
Pff, you think technicians are gonna bother opening superuser app to check for root?
I sure hope they wont. Phone has been picked up by delivery service today, that means it will arrive in repair centre by friday, and that means they will start looking at it next week maybe wednesday. Then before they figure out whats wrong, order parts and all, about 2-3 weeks and I can report what was wrong.
Got the phone back today. No idea what they did, no detailed description only "reset of program module SL4". Anyways, phone is working, I didn't have to pay anything, so all is good!:angel:
Hi there. I really hope someone can shed some light into this big problem I'm having.
I'm running CM11 with TWRP as my custom recovery.
Earlier today, I was streaming a video with flash. Then the video hanged but the kept playing. Nothing happened when I pressed the back button, menu or power. So I pressed and held the power button until the phone turned off. Then it wouldn't turn on again. I thought that the phone just locked and got stuck so I removed the battery. But it still wouldn't turn on. I can't even go to recovery or download mode. I tried plugging it in to a charger just to see if by some miraculous reason the battery completely drained, but still nothing. So that's what happened. It was working perfectly fine until it hanged.
I hope someone can tell me what happened to my phone...
Thanks,
Harold
update: I tried plugging my phone into a my laptop and I keep hearing the usb connect/eject sound. It seems like the phone is trying to turn on but can't. I removed it, removed/reconnected the battery, tried to go to download mode, but nothing happened, then I connected it again to my laptop but I can't hear the usb sounds anymore. So I removed/reconnected the battery again then plugged it in my laptop, and the sounds are there again.
I don't know what this means. I really hope someone can help me...
My tip would be to remove the battery for 15 minutes, then try to put it back and turn on.
ashus said:
My tip would be to remove the battery for 15 minutes, then try to put it back and turn on.
Click to expand...
Click to collapse
Already tried it.
I don't think it's the battery, it would at least turn the screen on for a while.
Try to put the battery in, and connect to charger (don't turn on).
I guess there is nothing else to do here, send it to RMA. :crying:
Can't you get into download mode?
LuqmaanMathee said:
Can't you get into download mode?
Click to expand...
Click to collapse
I can't get into any mode. And as I've mentioned above, when I plug it in my computer, it makes the usb sound, like I'm continuously plugging and unplugging it.
Odin is not recognizing it, even Kies.
hleotangco said:
I can't get into any mode. And as I've mentioned above, when I plug it in my computer, it makes the usb sound, like I'm continuously plugging and unplugging it.
Odin is not recognizing it, even Kies.
Click to expand...
Click to collapse
Try using a jig.
I own a Htc One (m7) and I was making a backup of my sistem in CWM recovery and my phone suddenly turned off and i couldn't turn it on since then. About half day passed phone was 2hours on wall charger and about hour connected on my pc and nothing happens. Im really freaking out, is my phone dead or there is something i can do? It doesnt show any sign of life. When i try to power it up while connected to the PC by using volume down + power button i hear quick sound of usb connecting and disconnecting. Im helpless, if anyone knows anything please help...
pavo122 said:
I own a Htc One (m7) and I was making a backup of my sistem in CWM recovery and my phone suddenly turned off and i couldn't turn it on since then. About half day passed phone was 2hours on wall charger and about hour connected on my pc and nothing happens. Im really freaking out, is my phone dead or there is something i can do? It doesnt show any sign of life. When i try to power it up while connected to the PC by using volume down + power button i hear quick sound of usb connecting and disconnecting. Im helpless, if anyone knows anything please help...
Click to expand...
Click to collapse
look here > http://forum.xda-developers.com/showthread.php?t=2770684
I'll give it a shot, thanks!
Hello,
I was transfering some files from my OP3T to my laptop with usb cable, and the screen went freeze-blur and then shut down.
Now it does not turn on, does not vibrate or charging, no led turning on and the pc does not find it anymore. It is dead =/
Do you know why this happened and how to turn it back on?
Thank you in advance
Hi buddy,
This is really strange that your phone is hard bricked after some data transfer.
The only advice I can give is try to search for: "hard bricked oneplus 3(t)" and follow the instruction.
If your phone is not seen as a qualcomm device when you follow the instruction than it could be that you phone is 'dead' by damage from the cable! It's just a guess from my side.
Mnarijnm
Edit: did you tried power + volume up/down?
A battery failure can do that. I would leave it for a few hours and the see if it turns on. If not, try charging it for a few minutes and then try turning it in with the power cable still connected.
Sent from my OnePlus3T using XDA Labs
Try leaving it plugged in for a couple hours, and then holding Power and Home. Weird, but worked for my. Hold it for like 20 seconds or so.
Hello,
thanks for your answers and effort to help me with my bricked phone.
I have managed to find my OP3T on pc under Devices ->ports -> Qualcomm HS USB QDLoader 9008 com3.
Now I am trying to unbrick it with OP3T Unbrick Tool but when I Run MsmDownloadToolV3.0 and press Start , I get a mesaage on 'Communication Status' that say ""Firehose Communication handshake Failed"' and stops, also this message "Sahara communication failed£¬please try again after power off the phone,".
Do you know how to resolve this issue?
Thank you again.
sxizofrano said:
Hello,
I was transfering some files from my OP3T to my laptop with usb cable, and the screen went freeze-blur and then shut down.
Now it does not turn on, does not vibrate or charging, no led turning on and the pc does not find it anymore. It is dead =/
Do you know why this happened and how to turn it back on?
Thank you in advance
Click to expand...
Click to collapse
Try press and hold the power key for like 20 seconds after it vibrates release the power key and press it again when the soft keys light shows up... Hope it'll help.
Make sure your device is properly turned off first of all. You can do that by turning off the device via fastboot menu.
After that, when you are sure device is turned off... make sure to hold 30 seconds... do a little longer even, and plug it in to the USB that is connected to the PC.
I personally did that and it worked well. I also just rebooted my PC and it literally had been on for a couple of seconds, maybe 30 seconds. Started MSM in administrative mode and pressed start. Connected and installation went through.
Had same issues like you before that.