[Q] Help with dead/bricked TP - TouchPad General

My TP will not turn on. I have tried several button combinations for varying lengths of time.
Series of events leading to current issue:
-Last night I decided to install CM7.1 Alpha 2.1, I followed the guide on this forum
-I was unhappy with the performance of Android so decided this morning to remove CM7
-Used the Acme uninstaller to remove CM7, every seemed to go well, I left the room for several minutes and came back and then it looked not so well, the uninstall grinded to a halt. The touchpad was erasing and renaming file after file from what seemed to be Android apps, I waited about an hour with no progress, still slowly erasing bad files and renaming them.
-I sensed something was not right so I turned off the TP and back on, now I could not boot into anything, i got to moboot screen but could not boot into either Android or CM7, would just hang on their loading screens. So I put back in HP recovery mode and ran Acme uninstall again.
-This time it finished fairly quickly, only a couple of minutes. But upon reboot it freezes/sticks at the HP logo and will not boot into webOS.
-My next step was to try webOS Doctor 3.0.4 so I put back into recovery mode and ran Web Doctor, web doctor will only progress to 12% and then freezes there indefinitely.
-I have tried several times, I have installed the Palm webOS SDK, still stuck at at 12%.
-Turned TP off once more and now it fails to even turn on at all, when I press power nothing at all happens, it seems dead or worse, bricked.
Any suggestions? (I am running Mac OS X Lion)

I have it turning on now, it just goes to a boot image of a triangle with an acclamation mark, or if I hold the volume up button it will go into USB mode.
But no luck webOS doctor...and it will not turn off either now, it reboots to the exclamation symbol every time I shut it down.
Anyone help?

I don't know exactly what hapened to you, but there were another thread about webOSdoctor stuck at 12% with link to this precentral tread, http://forums.precentral.net/webos-internals/295881-webos-doctor-12-issue-fixed.html
You might give it a try

Ok solved!
What I did was remove webOS SDK using the provided uninstaller and removed all nova com stuff, rebooted my MacBook and reinstalled novacom only (not the SDK) and started novacomd manually then started webOS Doctor and success.

Help! stuck at 12%
HEY ... Same thing happened to me . i cant boot into neither webos or android.
..
i was using windows 7 and not Mac. So could you please give me a step by step solution..pls..m stuck with the screen for about a week..

Solved!!
Thanks...I've got my TP alive again...thanks..

Related

Help...Won't Power On After Boot Looping

Hi,
My device started boot looping while trying to restore to stock ROM to update to a new ROM.
I wen't through the nvflash process successfully (meaning nvflash wrote the images to the device) but it continue with the loop.
Eventually, it powered down and now it will not power up at all. Battery is fully charged.
Any ideas?
Thanks.
OK, so I figured out that the device was stuck in APX mode.
nvflash doesn't seem to be fixing the problem, so I'm trying adb. It doesn't seem to see the device at all. I'm sure I'm missing step on how to work with adb.
Can anyone point me in the right direction for getting adb connected properly?
Thanks.
I'm trying to get adb working following this guide:
http://forum.xda-developers.com/showthread.php?t=902860
but it cannot see the device. The drive is installed fine but the device does not show up.
I know that if I can get into the device I can put it in debug mode, but I'm not sure how to do this now. I'm thinking this could be my problem, that the device is not in the correct "mode"
Any ideas?
Thanks.
did you get this resolved? i'm having the same problem.
williec30 said:
did you get this resolved? i'm having the same problem.
Click to expand...
Click to collapse
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
pgonza02 said:
Nope, still playing with nvflash.
Trying this now:
http://forum.xda-developers.com/showthread.php?t=974422
Click to expand...
Click to collapse
i was able to get the device back into apx mode and run the nvflash utility again.
williec30 said:
i was able to get the device back into apx mode and run the nvflash utility again.
Click to expand...
Click to collapse
I've been able to do that a couple of times, but after nvflash completes, just get into a TapNTap logo loop and eventually just powers down. When I am able to turn it back on, it goes straight into APX mode.
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
kostyamat said:
http://forum.xda-developers.com/showpost.php?p=12089833&postcount=92
Click to expand...
Click to collapse
Do you mean to install CW from external micro SD?
Thanks.
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
This is Where I Stand
1. nvflash from TNT lite post
2. Completes and reboots, goes into GTab screen, no Viewsonic screen
3. TapNTap screen and then to n animation
4. Reboot and go to #3. Haven't counted but at some point it just powers off.
I have tried installing CW from the external SD card but cannot get to it.
Have tried adb but cannot get it to connect.
I'm totally out of ideas...I'm thinking that if I just let it sit there, it'll just work
Finally Worked
I have no idea what made it work.
I decided to just take a break and left the tablet connected to the computer through USB but powered down. Came back a couple of hours later and when I turned it back on, I got the Viewsonic screen.
After that, I was able to reboot and go into CW and do a factory reset, which put it in a really old version. It was all easy from there.
pgonza02:
As I understand, you can now power off and reboot you GTab.
Can you recall what were your steps to get to this point?
I'm stuck in APX mode for almost a month! I don't know what else to try...
Thanks in advance.
I tried many things, including:
Install CW by replacing the image for partition 9 with the update.zip for CW (basically rename update.zip to whatever the img file is called)
Add CW to external SD card and attempt to reboot.
Eventually I just left the tablet alone and when I came back I turned it on I saw the Viewsonic birds (this seemed to be the key, when it was not working I never saw it)
I read a thread somewhere that mentioned that nvflash has the ability to redirect output through the HDMI out so you would not see it in the main screen. My guess is that what's happening is that the output of something, that is taking time to complete, is going out that way and I just could not see it. By leaving it alone, whatever it was, completed. This is just a guess, maybe someone with more knowledge can confirm.
Sorry I couldn't give you more details.
Boot loop and black screen
I'm having the same problem. In fact, I'm unable to boot into APX mode.
I have the cover off and read about a hardware reset button. I tried pushing the
reset button (k2) but nothing happened. I also read that I can disconnect
the batter. But, I don't see where the battery wire can be just disconnected
without soldering.
Any ideas?

CM7 Problem HARD Brick, webos doctor fail 1%

Hi guys, first post!
I really need help as I think I've tried everything.
I installed CM7 but it was low on battery while installing. Midway through the install process the screen said I need to plug into the charger that came with my device. Then it instantly went to the screen with an exclamation point and says
www dot palm dot com/ROM
Power+Center just gets it back to the same screen.
WebOS always fails at 1% and says it could not be reset.
I've tried ClockworkMod but it is unable to reinstall the .zip files.
I ran WebOS through command prompt and it said the required files were locked by an unknown file.
PLEASE HELP, my touchpad is useless now and I don't fully know what to do in ClockworkMod, which seems to be the only thing that works right now.
Here is what I Did
This is what worked for me....good luck
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if this helps. You won't be the first or the last to get this issue.
Wait... it died while installing?
Part 1: breathe
Part 2:
IF you can get into cwm right?
In CWM, you can mount the tablet as a USB drive, then copy the update cm7.zip file to it... and install it.
DO you have the blue text boot menu?
If not you need to install moboot again...
you can do that AFTER you've fixed cm7...
IF all else fails, and you can't install cm7 via CWM, then doctor it.
If you don't know how to use CWM, google it... it's pretty straight forward.
Lesson: Don't update when battery is low?

Galaxy Tab 10.1 Wifi P7510 stuck on battery screen

Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!

[Q] DOPO d7020 stuck in loop with mysterious issues

I bought this tablet exactly a year ago, never modified or rooted it, and suddenly a lot of apps started having issues. Went to reinsall a few of them then suddenly the whole OS froze.
Rebooted and the Dopo splash would show, then the android logo showing movement like it is trying to boot but gets stuck there.
Tried going into recovery by holding the power and volume button, that *worked* but when selecting factory reset then it crashed again.
So I repeated the process and now it won't even boot into recovery using the power and volume button!
Tried running the battery dead and restarting, tried using the reset button pinhole. Nothing worked.
I installed adb and fastboot (I use linux) and went through most of the simpler procedures.
adb connects and I can run its shell and view my files that are on the tablets. Ran the command to see its debugging output and noticed that the boot loop was because the filesystem turned everything except userspace to read-only!
Now here is what is real odd.. when I try pushing a file onto the tablet using adb, it instantly becomes corrupted when reading it back.
Like if I make a simple text file called hello.txt with some text in it saying "Hi there!", when I push that file onto the tablet, then read its contents it is gibberish.
This leads me to believe the whole filesystem somehow became corrupted and can no longer write files properly.
There doesn't seem to be a way to run fsck or anything alike and I can not put any files on the tablet because they instantly become garbled.
No use in running fastboot when the tablet no longer can go into the recovery screen either by vol+power pressing or by adb reboot recovery. Both simply just try to boot the tablet normally now, unlike the first time I tried
Assuming I have the factory .img file is there any way I can fix this?
Or does this sound like the hardware got damaged?
I fear the worst at this point.

Q88 bricked itself

Hello,
I have a tablet that looks similar to Q88 A13. CPU is wm8801, OS - Android 4.1. So I had stopped using it and left it sit for like 1 year. Now I charged it and tried to turn on, but it wouldn't get past first logo(the one that appears first, not the os loading one) and would attempt to go into recovery itself, but then the android with exclamation mark would appear for a while and then device would reboot and so on and so on...
Then I triggered a hard reset with a button combo, but it didn't really help. Tablet stopped trying to go into recovery and simply kept getting stuck at logo.
I can't access recovery, and neither ADB nor fastboot is working. PC with win 7 reports it as unrecognized device and other PC with win xp doesn't even see that anything is connected to it.
I've tried unsoldering the battery, completely discharging tablet without it, soldered it back on, but didn't help.
Help?
bump
Try Livesuit 1.11.
I've used it to load several ROM's
I'm currently running FaaastJB v2.5 found at http://forum.xda-developers.com/showthread.php?t=2447819

Categories

Resources