I have two HP Touchpads, a 16GB and a 32GB. Both have CM installed by me. The 16 ran for about a month and then crashed & won't reboot ("unfortunately Trebuchet has stopped"). It seems that /cache is corrupted but I have tried every function of TPToolbox and TWRP to repair delete resize or wipe and each one fails due to /cache problems. Reinstall also fails. Grateful for any insight / assistance.
Same problems on my wife's old unit. Tried almost every option and no go on retreading this tire. What's sad is if WebOS Recovery was still available, this would be an easy fix, but all my attempts running this process and doing a complete reset back to webOS have also filed. WebOS partially works, but repartitioning using Preware tools (Tailor) have also failed to fix corrupt storage.
Suspect I'll need Linux to ADM and reformat the partitions, but no go with this either and would love some help from some Linux junkie who may have a suggest.
Maybe someone can help both of us and please let us know if you make progress and I'll do same.
Sorli...
webOS recovery doesn't help me - reinstall fails
I can still boot webOS but it doesn't have much space. I bought a 32GB motherboard and am going to try installing it.
BB
Related
I tried to install Blur Hero 1.5.7, it did the boot loop thing, so I pulled the battery and tried again. After that did not work, I attempted to wipe and revert back to what I had using nandroid. No luck. So I got into the console and tried to start fresh by re-partitioning the sd in the hopes that I could reinstall and try again.
NOTE: Reason for the repartition step was because I was not able to access my sd through the phone. I tried (which has worked for me in the past) to hook it up through a camera of mine. Upon doing so it said that I needed to format, so I did.
Now I am in a world of hurt. My laptop will not recognize my device, it is still on the HERO boot loop, and when I try and connect using the cam, it says that it is in a RAW state instead of a FAT32.
IF any of this sounds familiar to anyone, please help.
Thanks for your time,
LJ
this has happened to me.
my problem was that after the boot loop, the ext3 (at the time) partition became mount, while the fat32 became mount-1. it normally, and should be the other way around.
you probably have to delete your ext, and then reformat your fat32 using gparted (ubuntu). then you can make another ext partition, and they will mount in the correct order.
also, when/if you get the mounts working, install one if cyanogens (god bless him) roms to make sure everything works. then you can try for hero again
a second time something similar happened to me, and it *bricked* my ability to create an ext partition on that sd card, tried multiple ways.
good luck
Have you tried to go into recovery and parted and format your card that way?
Originally I was getting those "SD Card Removed" errors. I assumed it was from flashing a bunch of different roms.
I read a few posts saying flashing a bunch of roms will cause such a ting to happen.
So I do a full wipe in Clockwork.
I am installing the nightly, worked fine.
Then the 120dpi. smooth.
Then the Google Apps. Whenever it started to install, my touchpad would just restart. After several tries and more of the same, I do another wipe. No zip files are installing.
Just a restart when starting to install.
So I webos doctor.
So far so good.
When I try to install CM9, similar situation occurs as the zip files.
The install code starts wizzing by on my touchpad.
After a certain point, it freezes and reboots.
Several attempts; all the same.
Is there a way to fix this?
Sorry for the double post, but I figured out the problem.
This is mostly for any body if they run into this problem.
Turns out, the android partitions were corrupt, and webos doctor couldn't touch them.
In the preware beta feeds, there is an app called Tailor.
What it does is, allow you to view the partitions on your touchpad.
You can either delete the partitions or reformat them.
I choose to delete them and then doctor them back into the main drive space.
Afterwards, the install went flawlessly.
Any WebOS Doctor later than 3.0.0 doesn't touch the other partitions.
If you wish to use WebOS doctor, you can use 3.0.0 first for partitioning and then use 3.0.4 to upgrade.
Had issues like this when trying to install nightly over a cm7: a reboot immediately after the start of gapps flashing, successful flash of nightly, but a bootloop after... I guess it has something to do with compability between cm7 and cm9, because what helped me is totally uninstalling any android/moboot/cwm with ACMEUninstall and doing a fresh install with ACMEInstaller2. CWM backup and most of sdcard content remain intact, so you still can restore if it fails to. Hope it helps...
I have a 64 GB Touchpad. Originally I had created a 10 GB extf3 partition for Ubuntu on it. Then, with Android ICS working quite well, I deleted Ubuntu and recovered the partition. In WebOS the system information says 64 GB. But I cannot actually use the recovered 10 GB, Internalz Pro reports only 47 GB and so does Android. So the 10 GB are still unformatted? The WebOS Tailor app is not working for me, so how can I revover the lost space and make it usable again?
Perhaps I can do it from the terminal with WQI?
Thanks for your help
HansTWN said:
I have a 64 GB Touchpad. Originally I had created a 10 GB extf3 partition for Ubuntu on it. Then, with Android ICS working quite well, I deleted Ubuntu and recovered the partition. In WebOS the system information says 64 GB. But I cannot actually use the recovered 10 GB, Internalz Pro reports only 47 GB and so does Android. So the 10 GB are still unformatted? The WebOS Tailor app is not working for me, so how can I revover the lost space and make it usable again?
Perhaps I can do it from the terminal with WQI?
Thanks for your help
Click to expand...
Click to collapse
Try taking the card out of the phone. Use a card reader on your computer and use mini tools partition program. It should do the job.
Make a backup, in case things go South...... Good luck.
chicle_11 said:
Try taking the card out of the phone. Use a card reader on your computer and use mini tools partition program. It should do the job.
Make a backup, in case things go South...... Good luck.
Click to expand...
Click to collapse
Sorry, you misunderstood. It is the Touchpad, not the Pre. The Touchpad has no card, only the internal flash memory.
with the touchpad mounted on your PC, does it show 64?
(mount it in recovery)
does webos doctor fix it?
NewZJ said:
with the touchpad mounted on your PC, does it show 64?
(mount it in recovery)
does webos doctor fix it?
Click to expand...
Click to collapse
Mounted from Android it reports 45.2GB, connected via WebOS it is the same. How do you mount in recovery? When I am in WebOS recovery mode the PC doesn't recognize the Touchpad.
I didn't run the doctor yet, would the doctor fix this and reformat the partition?
in clockwork recovery, you can mount usb drive by entering Mounts and Storage option and choosing Mount Usb, and it will be visible to your pc. but it sounds like you might have an invisible partition, in cases of that partition being on a sdcard it took a special program on the PC to repartition the sdcard to recover the size.
you can't format the touchpad without losing everything, i don't think that would be safe but i haven't tried it. if anybody claims to have done it safely then they will hopefully chime in
you can run the webos doctor safely though and it might fix the partition, your only loss would be reinstalling Android the original way
I posted this on rootzwiki, but I'm hoping someone here will help guide me back.
I have CM9 installed, which was working great except that I kept having "not enough memory" errors when trying to install apps from the Market.
I went to the CM7 sdcard problem fixes thread, found here:
http://rootzwiki.com/topic/13277-cm7-fixes-for-sdcard-issues/
These fixes work for CM7 and 9, so there is no compatibility issue there.
I attempted to expand the data partition by 1gb by flashing the correct .zip. However, after waiting 1.5 hours, with no change in the screen, I was forced to reboot it. I don't think I was too mistaken for thinking otherwise. No error message was given.
Now:
1. It reboots into CM9 okay, except the "checking SDcard" sign is on forever. Thus no access to the SDCard.
2. It won't reboot into WebOS anymore. It stays at the hp icon. This is most concerning to me, because to me it implies that something more than then Android install is broken now.
3. In Clockwork Recovery, it won't allow me to restore! Selecting that option just freezes CWM. However, it will allow me to browse the sdcard contents when selecting "install from zip"
4. From CWM, I can mount USB access and see all contents of the SDCard.
5. I did some searching, and one post suggested removing fsck_msdos from system/bin. I did this, which allowed me to access the SDCard in CM9 as this circumvented the SDcard checking. This obviously is not the right solution, so I restored it.
Next steps please?
I've got backups so the data isn't so important.
I think the sdcard partitioning is wonky due to the aborted memory expansion attempt, so I'm not sure running ACMEuninstaller will fix that.
I'm thinking I attempt to run ACMEUninstaller first, followed by WebOSdoctor if it won't boot into WebOS?
Take a look at this guide : http://forum.xda-developers.com/showthread.php?t=1426244
Yup, ended up doing that and looks like it's doing well.
Basically jacked up the storage partition so badly there were an infinite # of errors. Because WebOS uses that same storage for some of its files, couldn't boot either.
I've had to do it 3 times already.
It's a big PITA, but it works....... If your partitions get fracked, I've found this to be the best option.
I don't know if anyone has experienced this but: I ran TP Toolbox to resize my partitions, and it performed a file system check. It ended up repair a LONG list of stuff, and now CM9 just bootloops. Is there anyway I can fix this short of reformatting? Obviously, I'd rather not if possible, as my installation is 6 years old or so and all my daughter's data is on it.