So I think I did something which I've not done before - brick my phone completely.
I got two Z3C so this is my 'spare' one which I was testing CarbonROM on. Because I want to ease my transition to a new ROM I wanted to backup my entire "main phone" and restore it on my secondary phone, with TWRP. When I tried this, it seemed like it only wanted to restore system, data (excl storage) and something else I can't remember. But it didnt include the FOTAKernel and stuff I had taken a backup of from the other phone.
Anyway, the restore failed when it came to data (excl). I gave the phone a reboot and since then it's just been flashing a red light. I can't hold down power button and vol down to simulate the battery pull. If I plug in USB while holding volup or down it doesnt enter flashmode or fastboot - it just blinks red.
The phone was plenty charged when I worked with it, 50%+ was the last battery level TWRP told me.
Other googlings bring me to people who write its a hardware fault - dead motherboard or so. Others have experienced it with waterdamage and stuff like that but my scenario is nothing like this.
Any clues ?
Kocane said:
So I think I did something which I've not done before - brick my phone completely.
I got two Z3C so this is my 'spare' one which I was testing CarbonROM on. Because I want to ease my transition to a new ROM I wanted to backup my entire "main phone" and restore it on my secondary phone, with TWRP. When I tried this, it seemed like it only wanted to restore system, data (excl storage) and something else I can't remember. But it didnt include the FOTAKernel and stuff I had taken a backup of from the other phone.
Anyway, the restore failed when it came to data (excl). I gave the phone a reboot and since then it's just been flashing a red light. I can't hold down power button and vol down to simulate the battery pull. If I plug in USB while holding volup or down it doesnt enter flashmode or fastboot - it just blinks red.
The phone was plenty charged when I worked with it, 50%+ was the last battery level TWRP told me.
Other googlings bring me to people who write its a hardware fault - dead motherboard or so. Others have experienced it with waterdamage and stuff like that but my scenario is nothing like this.
Any clues ?
Click to expand...
Click to collapse
I don't think you can restore from a different phone. That's probably the cause. However, I also have not heard of a hard-brick happening just by trying to flash the wrong thing in TWRP, (but maybe possible).
I have had the red light issue a few times, after flashing bad zip, but not on Z3c, on my XA, and I was able to resurrect it by holding down volume and power buttons while plugging it in, but for some reason, it only worked when I used a different charger/cable. All of a sudden it pops back to life with zero battery, (it was full when it died). Maybe you can try that.
I've also found that with some custom rooms / kernels, you need to hold volume and power buttons for about 10 seconds to get it to respond...
levone1 said:
I don't think you can restore from a different phone. That's probably the cause. However, I also have not heard of a hard-brick happening just by trying to flash the wrong thing in TWRP, (but maybe possible).
I have had the red light issue a few times, after flashing bad zip, but not on Z3c, on my XA, and I was able to resurrect it by holding down volume and power buttons while plugging it in, but for some reason, it only worked when I used a different charger/cable. All of a sudden it pops back to life with zero battery, (it was full when it died). Maybe you can try that.
I've also found that with some custom rooms / kernels, you need to hold volume and power buttons for about 10 seconds to get it to respond...
Click to expand...
Click to collapse
Hm. I've had it charging from USB connected to my laptop overnight - nothing different. Plugged it into a real charger when I went to work, will see when I get home.
It doesn't react to the powerbutton + voldown combo, which I've used extensively in the past. I haven't tried plugging it while holding any button. Did you plug it into a charger or computer USB port?
Kocane said:
Hm. I've had it charging from USB connected to my laptop overnight - nothing different. Plugged it into a real charger when I went to work, will see when I get home.
It doesn't react to the powerbutton + voldown combo, which I've used extensively in the past. I haven't tried plugging it while holding any button. Did you plug it into a charger or computer USB port?
Click to expand...
Click to collapse
I did the same thing for a whole day, (tried to leave it plugged in to charge), and no response, but when I changed the cable and power source, and held down the buttons while plugging it in, after a few tries with different buttons, it suddenly popped on, with zero battery, and started charging.
Also, you might try posting in a TWRP thread. See if anyone has seen this before...
Related
I was doing an Odin One Click restore to return to stock
Odin got stuck for some reason. I waited nearly 45 minutes before pulling the battery and attempting to start over.
Upon pulling the battery, the phone went off, as expected. removed Sim, SD card, replaced battery, replaced battery cover, etc etc.
The phone is 100% unresponsive.
1: Removing and replacing battery - no effect
2: VolUp + VolDn + Power - no effect
3: Plugging into any one of the 5 USB ports on the computer - no effect
4: Plugging directly into the wall - no effect
Nothing I've tried or read has given any solution to even get the phone to come on.
Last ditch effort, going to leave the battery out for an hour or so, and failing that, going to leave everything plugged in for an hour or so.
The battery on the phone had nearly 95% when I started this endeavor.
Does anyone have any hints or suggestions as to other things to try?
Thanks.
I had that happen last night. Got stuck sending "factory.rfs" or something like that.
Anyway, plug your phone to the wall for a few minutes. Maybe an hour. Then open Odin, hold Vol-UP and Vol-DOWN (dont push power), and plug the device to the computer. It should boot to Download mode.
Now, I used the version of Odin that allows you to select the firmware -- there's another that comes with JF6 preloaded. I installed JH3. Also, when I selected the firmware with the "Phone" section and flashed, it did not work (FAIL). Later I tried the "PDA" section and it did.
Let me know how that goes.
EDIT: Plugging to the wall, the screen will not turn on. But the back will get warmer. Trust me, it is charging. My battery was full after the flash.
del
Thanks for the quick response.
I figured at this point, I couldn't do anymore harm that good. Worst case, I buy a new one.
So, I started tinkering with various key combination... Lo and behold, one particular set gave me the infamous "orange dump".
From there, and a bit of searching (i had remembered seeing the bit about the orange hex dump somewhere), I found the same solution you just provided.
Worked, phone is stock and functional.
Kudos.
Dave
i too was trying to install vodoo and after installing it my phone wont turn on it just keep on flashing atnt screen and next screen i see is samsung and thts keep on repeating no luck my phone wont turn on please help me am badly stuck.
thaank you.
IF you are able to get your phone to the point of seeing the att screen then you should be able to hold down the vol up+down buttons while also holding the power button...Just to be safe, hold it till the att screen flashes twice. Then release and you should be taken to the recovery mode. If not, Try the same steps again plugging in the usb while the att screen is present. Repeat as necessary. Good luck.
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.)
I have a brand new Nexus One bought on last year April. For some reason it wasn't to be used. Yesterday, I got it out of the package and charged it for ready to be powered on. Unfortunately, it reacted nothing as I pressed the power button! I took out the battery and put it into other Nexus One, it showed the battery was 100% charged.
I took back the battery and repacked it to this new Nexus One. I tried to press the power button more and more with data cable connected pc. Nothing happened. Just one time, the sceen lighted on and the "X" in four colors appeared! I didn't know why it was powered on. Maybe I pressed the trackball or volume up/down buttons, God know it.
The X sceen lasted almost for ten minutes and then sceen was off! Yes. It shutdown! I can't power it on anymore!
It seemed the hardware was OK. It may be the locked by the outdate android system. The android prestored in this phone is version 2.1.
Any advice is welcome. Thanks.
Can u you go in fastboot? Press power button+trackball..if so then you can recover your phone by unlocking bootloader and falshing custom recovery.
Sadly, It can't be power on and go in fastboot by pressing trackball+power button.
Any more advice?
Check the battery terminals just to make sure they're not dirty.. Sadly, you MUST be able to at least be able to boot something (hboot/fastboot) in order to troubleshoot anything software related. Sounds like you've got a hardware issue that could be one of (literally) a million things.
Sell it on EBay for parts. You can probably get $50-$60
you could try pressing pwr/vol-/trackball all at same time, hold down for around 30 seconds to make sure
commonly known as 3 finger salute
try power on without sdcard by manual methods and plugging in and plugging in with no battery
I have seen a video on YouTube on how to fix the power button which is known for messing up and how to turn it on. Search YouTube
Sent from my Nexus One using XDA App
is it that the power button is not working? that would be weird for a new phone though.
have you tried to turn it on using the "jump start" method?
connect the cable. led the charging led come on. remove the battery, wait for the led to go off (while cable is still connected) then pop the battery back in.
see if you can get it to start that way
When you plug charger cable in your Nexus, does the orange or green LED go on?
If one of them does and stays (green for full battery, orange otherwise) - then your problem is most likely the power button. It may not be the only problem, but at least the one that's stopping you from turning on your phone. You can try "jumpstarting" it by inserting battery while charger is connected.
If you don't see LEDs when plugged in - your phone is done.
If you see blinking LEDs - battery terminals might need cleaning/fixing, it usually happens when the battery is out of the phone.
NOTE - I added this post here thinking the CM9 experts could help. I then realized it should be in the Q&A section. If this does not belong here, I ask a moderator to please delete it.
I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
chozyn said:
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
Click to expand...
Click to collapse
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
It's a good idea to use only stock cable and charger.
Sent from my ClassicJewel
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
Are you able to get into download mode at all?
A$$h4t said:
Are you able to get into download mode at all?
Click to expand...
Click to collapse
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
enmriley said:
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
Click to expand...
Click to collapse
This happened once to my TP when I first put CM7 on the device a while back. I woke up one morning, forgot to plug it in overnight and it had died. No response to any charger, I was getting worried but then I found a solution. With it plugged in, hold the power button and home button down together for 15 to 30 seconds. It was that or hold the power button down and keep pressing the home key over and over. Not 100% sure, but it came back to life and I remember it took me a couple tries. Try holding both down simultaneously for 30 seconds or a minute, if that doesn't work, push and hold power first then home right after and hold both for 30 seconds.
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
-SGA- said:
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
Click to expand...
Click to collapse
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
rhidalgo1973 said:
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
Click to expand...
Click to collapse
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
enmriley said:
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
Click to expand...
Click to collapse
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
sstar said:
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
Click to expand...
Click to collapse
In Tasker add a New profile and give it a name like Battery_Low
Choose State and then Power for the profile.
In Power choose Battery level and set From to 0 and To to say 8%
Set New Task and do Add give it a name like Shutdown and then pick the Misc category
Choose Reboot and set Reboot type to Shutdown
All done. When battery level drops to 8% or below then Tasker will shut the tablet down. Note it will do this without warning. I think one could probably arrange a pop up warning first but I preferred to keep it simple.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
enmriley said:
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
Click to expand...
Click to collapse
The only way I know is to put it on a Touchstone and after an hour or so it Will come back to life. All thanks to Reverand KYLE. His site is well worth checking out.
Hello. This morning I've turned off the alarm, turned on WIFI and went back to sleep. I can't tell for sure, but I think the battery was low. During the next 2 hours I checked the time several times. I don't remember accepting any OTA. Eventually I got up, tried to check the time and the phone was off. I tried to turn it on, no effect. No matter how many times and for how long I pressed and held the power button, the green LED only flashed for a split second and that's all. I plugged in the charger, and the LED stayed lit -but- there was this barely noticeable flickering. Charged it for about 30, 60, 120 minutes, didn't start plugged or unplugged. I went to work, 8 hours later (phone was unplugged) I tried to turn it on again, this time the LED doesn't even flash, but when charging there is no flickering. No combination of buttons works. Windows doesn't find the device, neither does RSD.
I've never done anything 'custom' to the phone. The last change I made was setting the alarm to turn off by shaking (yesterday, never used this option before).
Is it dead?
Try taking SD card out and holding Vol down and then Power for 20 secs, then let go of Power,
Already done that, nothing. No matter how long I charge it now, after unplugging and pressing power button the LED doesn't even flash. Could it be a battery problem (before its death, it would last for a day)? Is there any way of recovering my data without buying a new one?
Try opening and disconnect battery for a bit.
I'll do that as a last resort, on weekend maybe since I don't have the tools with me. Any other clues?
Nobody knows how to help me?
I'm going to make a factory cable. Will this alone allow me to recover the data? Or if I'll be able to flash the phone, can I recover the data afterwards?
Also, I'm not sure if I understand correctly: does the factory cable recharge the battery or not? Is there a way to recharge it when removed from the phone?
Try to use medfield unbrick script. If You have only green led it seems to be bootloader error so this script should bring Your phone to life or Your phone has broken emmc and You can start looking for a new logic board. Good luck.
I've installed the drivers, but Windows and XFSTK don't recognize my device at all. Factory cable also didn't help. I liked my phone very much. :angel:
Did You enter medfield mode using combination with camera button??
By a combination you mean holding the camera button and connecting the phone to a pc? I tried that.
Disassembe Your phone, pull out battery, push power button for a 10 sec, plug in battery, push camera button and connect USB. If it wont help You I don't see any hope for Your phone.
Well, new option to try is a new hope. I'll try that on the weekend. Could you please be more specific:
1. Pull out the battery.
2. Press the power button and wait 10 seconds.
3. Insert the battery: should I be still holding the power button at this moment?
4. Press the camera button.
5. Plug in the usb cable (factory? regular?) - should I be still holding the power and camera buttons?
Battery trick is only to discharge capacitors. Sometimes even phone is dead it can turn on in some strange mode and then You can't boot it to flash. Thats why You need to pull out battery, push power for a few sec to completely discharge motherboard and just release this button. After that You can just plug in battery and continue normal unbrick process - so hold camera button only and connect regular usb cable.
You can also try reset option instead of pulling battery out. To do that do not disassemble Your phone but just plug in regular USB, when phone starts (green led) hold power and vol- until green led goes off and then quickly start holding only camera button.
I have no more ideas.
Ok, I've tried everything. Nothing brought my phone back to life.
Thanks for all your help.