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.
Related
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
GreenLanternBatman said:
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
Click to expand...
Click to collapse
It sounds like you don't have Amon's recovery flashed yet.
This is probably the easiest thing you can do.
http://forum.xda-developers.com/wiki/index.php?title=How_to_flash_Recovery_Image
or this
http://forum.xda-developers.com/showthread.php?t=742228
In either case, you need to read, and educate yourself.
Precursor - If you run a back up program like Titanium Back Up or MyBackUp Pro, now would be a good time to do that.
I think your main problem is that to get into Recovery mode, you need to hit Volume Up + Power (End). Once there, I'd suggest going to Back Up/Restore and doing a Nandroid Back Up. This will save the entire state of your phone just as it is before you went into Recovery. Exactly as is. Next, go to Wipe, and select options 1 - Factory/Data Reset and 2 - Dalvik Cache. If you don't already have the KaosFroyo-v34.zip file on the root (meaning NOT in a folder) of your card, you can go back to the main Recovery screen and select 2 - USB MS Toggle which will mount your SD card to the computer and you can drag and drop the file from there. Once you've followed these steps, now you are ready to choose option Flash Zip from SD card. Select the zip you need and let it do its thing. You didn't mention if you had apps2sd set up not. If you don't, ignore this next part, if you do, pay attention. IF and only IF you were using apps2sd then you will need to reformat your card to work with Froyo roms. Froyo already has the benefit baked into it but it utlilizes it in a different way. To reformat, you will want to copy everything from your SD card to your computer, then in Recovery, go to Partition card. For Ext and Swap sizes select "0" and then hit ok for partition the rest of the card in FAT32 format. Done. You can add back on contents from the SD card in Recovery through the USB Toggle mode or after you boot everything up, it does not matter (the only difference being that your computer will ask if you want to copy and merge folders if you do it after you boot because it will remake some of the folders for you on booting) . With that being said, now it's time to try out KaosFroyo! The first boot WILL take awhile and the phone will be very slow once it does boot as it has to Sync all of your info and applications back from the Market. Once that gets finished, then you can restore your data if you saved it through Titanium or MyBackUp. I usually like to give it a reboot after all this fun stuff, just to give it a chance to gather itself, if you will. After that, you should be good to go with learning the ins and outs of Froyo Hope this helps!
Did you make a amon backup before you first rooted you phone? I had that same problem when I flashed Kaosfroyo v34. I would boot up in recovery (Vol up+end) and I would have the android with the ! above him. I started freaking out. What I did was restore my nand backup back to 2.1. Then I re-rooted back to KaosFroyo v34. Then went into recovery and everything was good. My advice, unroot then root again. Maybe its not the best/easiest way, but it did the trick for me. And as always, search the forums, there is a post for almost anything. Hope that helps.
I know this has probably been answered, but I'm having trouble searching for it and I've looked through pages.
Basically I had Android 2.2 running great, I even did a hard reset after installing it like recommended. Everything was perfect, however today at work, my battery died out, once I got it charged up, I turned on the phone and ran CLRCAD and then launched haret.
From here, the whole process runs through and I get to a black HTC screen, but it never goes past this.
Whats the proper process I need to take in order to be able to re-launch into android instead of deleting all the android files and reinstalling it?
who said you have to hard-reset your phone after installing Android ?
you don't have to, after installing android just make a reboot and launchclrcad and haret again !
I don't recall if it said "hard reset" or simply reboot as in holding down the power button and hitting power off. However, that does not resolve my issue. I am looking for an easy way to get back to android without having to delete & re-copy files on top of setting things up again.
bump, I know I can get back to android 2.2 by deleting all the android files on the sdcard and placing them all back there from the zip file. This just doesn't seem right though, I'm sure there is a way to make this process much smoother.
After updating to webOS 3.0.4 I am unable to get ACMEInstaller to do install-reinstall Mboot or anyother zip to try and return the touchpad to dualboot status. As of now I can´t get into CM7 at all.
I´ve tried a factory reset of WebOS using webDoctor and then reInstalling CM7 but to no avail. Any advice?
What does the unit do when you reboot it?
it just boots webOS. One thing I've noticed that I think MIGHT BE different is that the HP icon flashes up on the screen right before the USB symbol pops up when holding down the vol up button.
This has been covered extensively, all you have to do is reinstall MOBOOT, and you will be able to get back to your unharmed previous installation of CM7
Yes that was done and wasn´t the problem. Thanks anyway. Figured out was was going on.
mmontanaa said:
Yes that was done and wasn´t the problem. Thanks anyway. Figured out was was going on.
Click to expand...
Click to collapse
So what was the problem and solution?
you HAVE TO re-enable developer mode on the touchpad when you have a fresh install of webos before acmeinstaller will work.
that's the solution.
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 received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.