I am trying to unbrick my Touchpad at present. I was trying to wipe to sell and made a bit of a hash on things.
It won't boot and just hangs on the HP logo and WebOSDoctor hangs at 8%. I tried to run the ACME Uninstaller which crashed and seems to have knocked all sense out of my touchpad.
I am following these instructions for fixing :
http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/
The question I have is that when I run the ACME Installer on that it gets to a stage where I get a scroll of messages :
Bad File Name
Auto re-naming it
Yesterday I left this running for about 4 hours (maybe more) and it got to renaming about 6000 files before the battery went flat. I have started again this morning after leaving the Touchpad charging all night.
Any advice from anyone? I have no interest in any data on the Touchpad, I just want it wiped and booting back into WebOS.
Tried to repartition the touch pad...
Sent from my cm_tenderloin using XDA
I actually managed to fix this.
I was getting lots of trouble with Novaterm. I tried using it on my Mac and on my Windows machine. I was getting errors saying "command not recognised".
I actually managed to find one solution. I can't find where it was now but I just loaded up Novaterm and entered a single command which I believe reformatted the tablet. I was then able to use WebOS Doctor 3.0 and restore.
Related
Okay, I think I'm completely hosed. But I thought I would ask if anyone has a solution. Here's the deal.
I was running the new stock 5274 on 1.2, went to turn on the tab and it wouldn't power up. This has happened before so I cracked the case, pulled the battery connector and plugged it back in then shorted A4 and powered up into APX. I ran NVFlash for the stock 4349 based image, figuring that I could then update it again after I loaded Clockwork. I've done this a bunch of times before, never had a problem. Until this morning.
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks. I also tried to run the Format tool, which I've also done before, and get the same error at the same place. In fact, no matter what flash and try to run, 1.1 or 1.2 BL, NV bombs out at part7.img.
I'm at a loss. The only way to get the tab to power on is to short A4 into APX, but I can't flash anything. Any advice would be greatly appreciated.
Ronin916 said:
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks.
Click to expand...
Click to collapse
Looks like you've developed some bad blocks on the NAND flash. Just skip loading that part7.img, then.
On most gTabs, partition 7 is the /misc (MSC in nvflash) partition which is not used by most ROMs (GtabComb uses it to create a single log file). So, it doesn't matter if this partition is not written by nvflash.
On some gTabs (like mine), partition 7 holds the .bmp file for the first splash screen (VS's 3 Gouldian finches). This, too, is not important. You'll just not get that first splash screen.
Just erase the partition, if you can, using the erase_image program in CWM after you restore the remaining partitions using nvflash.
Thanks for the tip. I tried removing part7.img from NV, but now it bombs on part9.img with a NvError 0x30012. So, that's a no-go, and now I can't even get into APX. Maybe the battery died, so I'm going to charge to full and see what happens. Still could use suggestions, though.
EDIT: Well, color me confused. The battery was dead, so I gave it a good 4 hour charge to full. Then I cracked the case and was able to get back into APX. I have NVFlash and the 1.2 4349 load here, so I figured I'd give it a shot. Sure enough, it ran through NV without an issue, and I'm back to stock 4349. Not one hint of an error. Dunno....maybe the tablet gods decided to smile down upon my today. All I know is, I'm back up. Don't know how....don't know why....just is.
so im pretty much a noob to this website and my g tablet but heres my problem
i was stuck at the bootloader (those frickin birds) so i decided to nvflash to get it back to normal, i followed the instructions step by step and it seemed to work, it booted normally and i thought all was good untill it randomly turned off, so i plugged it back into the computer and held the power button and i heard it connect so i nvflashed again and the white writing popped up, it finished, it got to the g tab screen then turned off again. i let it die last night and i just went to turn it on and nothing. help please
Sgt,
You may have to crack open the case and pull the power connection for a few seconds and then plug it back in. Seems like every tab is a little different, but you can reference this thread:
http://forum.xda-developers.com/showthread.php?t=1118087
Maybe that gets you back up into APX at least.
thanks for the help unfortunantly it didnt do anything, i think im stuck in apx mode because i can still nv flash, every time i do it goes straight to gtab screen then shuts off, i turn it back on and i can flash but nothing else
You may want to try this:
http://forum.xda-developers.com/showthread.php?t=1030042
It shows you how to NVFlash Clockwork. If you can then get into that, you could repartition and format you GTab, then load the ROM of your choice.
Posting here in hopes to expand help request.
deleted...
10char..
ok i nvflashed cwm and i believe it worked but i still cant get into it, the moment i turn on my tablet i dont get any load screens it just goes into apx mode thats it
New problem: is there a way to backup your Memo (stickies notes) without booting into webOS?
where are the text data files located?
Is there a way to restore/revert webOS system while leaving my Android portion untouched?
So after updating to 3.05 and installing a custom IME (which worked for 3.04) I've bricked the webOS portion of the touchpad.
The Android system still boots fine, and I don't want to wipe that just to get webOS working.
BTW this is what I don't like about HP, I never intended to update 3.05, simply left my touchpad charging overnight, then woke up in the morning & found out the bad news.
dindin223 said:
Is there a way to restore/revert webOS system while leaving my Android portion untouched?
So after updating to 3.05 and installing a custom IME (which worked for 3.04) I've bricked the webOS portion of the touchpad.
The Android system still boots fine, and I don't want to wipe that just to get webOS working.
BTW this is what I don't like about HP, I never intended to update 3.05, simply left my touchpad charging overnight, then woke up in the morning & found out the bad news.
Click to expand...
Click to collapse
It sounds like you have to doctor your TP.
Search 'doctor', there are several how to threads that should guide you through the process.
Mine too
My install of 3.0.5 did not complete, in the process it wiped out Moboot 0.3.4 What I did to recover is download the latest Doctor from the HP site and ran it. That updates the OS correctly. Then I looked at the files and found that all of the Android mods/files were still there.
So I just installed the new version of Moboot using ACMEInstaller and then I did the same thing for Clockwork recovery. Rebooting into Clockwork recovery, I reloaded Xron 2.9.1 from the zip file which was still on the Touchpad.
Everything Android is working fine right now.
I suspect that there is a better way, but I don't have 10 posts to ask in the developers section.
Using the "Doctor" wipes out WebOS settings and Apps so you have to reinstall those just FYI.
Thanks for the valuable information, it's good to know that I don't have to reinstall all the android apps.
Now I'm trying to find a way to back up my memo files in webOS...
Yeah, the doctor resets your device to factory...I used it often during my pre- days. Make a nandroid next time so if something does go wrong, of will be easier to restore what you had. Just copy the backup to your PC before using the doctor.
Sent from my GT-i9100 using Tapatalk
If u still have android and can boot into cwm , then make a nand.backup so you can restore your cm7 / xron exactly as it is.
now webosdoctor 3.0.5
then if needed install moboot0.3.5 and cwm with ACMEInstaller
IF Android not present in Moboot , restore nand.backup in cwm.
As long as u have a Nand.backup u can wipe Android as many times as u want.
I really must learn to type faster
They should be backed up automatically. They will restore after you set your account back up in web os. I had to run the doctor to fix my 3.0.5 update and all my stickies are still there.
I'm in the same boat as you guys here except that it worked fine yesterday (I needed it for work) and I forgot to charge it last night. I went to work and before my office meeting started I plugged it in, figuring it would have enough juice for me to use. Well... I realized it wasn't charging at all and its not the charger. No matter how long I held the power button I couldn't get anything to come on. I came home and placed it in the touchstone charger and nothing either. It seems like I'm screwed with a bricked 32gb touchpad. I did buy it direct so I guess I'm going to try to send it in (hopefully I'll get lucky, I'm going to deny any tampering with) to HP. I haven't connected it to my pc yet but if I get nothing there's no way to run Doctor, right?
Any constructive thoughts would be appreciated.
Update: You are not going to believe it, after messing with different combos of button pressing (which did nothing) all the sudden it just powered up (all I did was plug it back to the wall). And, as I was typying this it rebooted it self with boot screen which started CM7 again. Do you guys have any suggestions? Should I update the moboot?
The doctor does not erase your cm7/9 partition. It fixes the hp webos partion and sets it back up to what it auto saved. You just have to run the acme installer to get cwm and moboot back. even if you install android agian, if you don't wipe all your data should be there. That's what happened when I did it.
can't get into usb mode
I noticed that my hp touchpad was shutting down while in standby. I immediately thought it was a autoupgrade and so when it booted up and started installing the new webos I panicked and hit the power and home buttons to prevent the upgrade because I have CM7 alpha 3.5.
When I booted it up again I could only see a battery icon with a question mark in the middle. I can't make my win7 pc recognize the tablet and nor does the hp doctor for the same reason.
Does anyone have a clue how I can fix this? I know that some people in the past had this same issue that was caused by faulty usb cable or not having the battery correctly inserted (for other webos devices) but this is not the case. Just before I canceled the upgrade I had 20% battery and I had it plugged in and charging.
Thanks.
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
I recently updated my Touchpad to 3.0.5 which was a terrible idea. Somehow it messed up my android side, so I decided to doctor the Touchpad. Unfortunately when I did, it would not boot up. It is stuck on the palm.com/rom screen and now when I try to doctor it, it gets stuck on 12%. I'm running OS 10.7.3. Can anyone help? I've googled solutions but none of them seem to help.
You should run ACMEUninstaller, that will remove Android.
Then run Doctor again and you might be lucky, if not it gets slightly more complicated.
the webos doctor will hang at 12% for a while , so give it time.
You may have to doctor with 3.0.2 to get the correct partition resizing, then re-doctor to 3.0.5, and then re-install android. I believe that 3.0.2 was the last doctor that adjusted the partition tables prior to installing, but check google/xda first on that, as it has been discussed before.
Can you still get into the usb loader screen when you power on/reboot and hold the volume up key?
pikeco94 said:
I recently updated my Touchpad to 3.0.5 which was a terrible idea. Somehow it messed up my android side, so I decided to doctor the Touchpad. Unfortunately when I did, it would not boot up. It is stuck on the palm.com/rom screen and now when I try to doctor it, it gets stuck on 12%. I'm running OS 10.7.3. Can anyone help? I've googled solutions but none of them seem to help.
Click to expand...
Click to collapse
Do you have a Windows virtual machine?
I just got the Gtab (UPC300-2.2) but it fails to load anything.
It does not boot and gets stuck. I do not know the boot version of it or any versions of anything because I can't access it.
When I try to put it in recovery I only get the following 2 messages:
Recovery Key Detected
Booting recovery kernel image
Thats it. i took the SD out of it and same bit when I tried to access it I seen Update and recovery files and roms folder so looks like someone tried to mod it but failed.
Is there a way I can recover it to working state to ether restore it to factory or any recommended rom...
I kind of need instructions because I never messes with this type of issue yet, as in I haven't bricked a device to this state before.
I also need to find a charger for it. looks like connecting the USB does not charge the Gtab
Id prefer recovering it to FACTORY SOFTWARE.
Im just not sure where to get the Factory software and how to go about recovering it...
So far I found out that this unit possibly has Bootloader v1.2 but recovery that was loaded onto the device was for bootloader v1.1
I do know know what the previous owner tried to do to it but failed and screwed up the device. Im just trying to fix it back to working condition.
It does not matter if its factory rom or a modded rom, as long as its stable.
Also I read up I need NVflash or something like that to recover the units bootloader ignorer to get it to work.
Any help is welcome, and I thank you all in advance.
Well I did the stuff from one of the posts here using nvflash.
Nvflash —bl bootloader.bin —getpartitiontable p.txt
Returned the SOS partition to be 11
Then tried the:
Nvflash —bl bootloader.bin —download 11 recovery.img
Finished successfully but I still have the message while trying to enter recovery:
Recovery key detected
Booting recovery kernel image
Then just sits there with the birds background.
When I try to normally boot it it does boot but I can’t open settings or anything and I constantly get this error message:
The process Android.process.acore has stopped unexpectedly. Please try again with force close button.
It constantly pops up, like once every 3-5 sec.
when i got mine it was messed up too, sounds very similar. When I got to the Viewsonic birds logo I let it sit forever and i thought it was done for, but after sitting for literally hours it actually booted up and i've been using ever since. that was about 6 months ago. just find a charger for it, i cut the end off one with the wrong voltage and attached it to an adapter with the correct voltage and amperage. It says on the back of my device "dc 12V 2A" then get it to the birds logo and set it down. Go have a day at the park or let it sit overnight, go to work for a day, out for dinner. do something so you're not sitting there looking at it every five minutes. Good luck!
Would it be possible for anyone to provide me with either the files or operational links to the files needed to recover this device?
I've scoured this forum and found nothing but dead links to NVFlash and the like. Thanks in advance!
Seems like there are a few of us still rocking this piece of hardware, me included. I"m stuck in the same dilema and the links to all the restore files haven't been preserved. Is it best to just concede that the tablet is ancient history and go purchase a new one or are the nvflash files available somewhere on the web?