Check Your I/O Usage with Iotop for Android

Ever needed to check the I/O usage of apps? If so, you probably tried searching for an iotop … more

T-Mobile HTC One M8 Gets Selfie-Friendly Android 4.4.4 OTA

The T-Mobie variant of HTC One (M8) just now received an over-the-air update … more

Android L is for Lockdown

Root is, without a doubt, the (un)holy grail of the Android world. Those wonderful permissions that allow you as … more

XDA Xposed Tuesday: XHangouts Will Improve Your Hangouts

Ever since Google started supporting text messaging in Hangouts many people have … more
Post Reply

Touchpad stuck in a read only mode

OP asif9t9

2nd July 2014, 03:02 AM   |  #1  
OP Senior Member
Thanks Meter: 50
 
448 posts
Join Date:Joined: Oct 2011
I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1.

Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5.

Thanks,
The Following User Says Thank You to asif9t9 For This Useful Post: [ View ]
3rd July 2014, 06:09 AM   |  #2  
Senior Member
Thanks Meter: 72
 
173 posts
Join Date:Joined: Nov 2013
Quote:
Originally Posted by asif9t9

I have a TP with WebOS 3.0.5, Moboot 0.3.8, and CM10.1.

Whenever I reboot my device, any changes I make are reset. I can't load a new ROM. I can copy files to my SD Card and use them, but when I reboot, the files are gone. I see this is an ongoing issue. But most threads are old. Any fix for this? I just want to be able to run WebOS doctor now, but it won't work. It stops at 12% and says Unable to Reset. I have tried all the various WebOS doctor versions from 3.0.0 to 3.0.5.

Thanks,

Use jcsullins hp TouchPad Toolbox. Complete reset.
The Following 2 Users Say Thank You to Moody66 For This Useful Post: [ View ]
3rd July 2014, 11:42 AM   |  #3  
OP Senior Member
Thanks Meter: 50
 
448 posts
Join Date:Joined: Oct 2011
Quote:
Originally Posted by Moody66

Use jcsullins hp TouchPad Toolbox. Complete reset.

Cool thanks. This looks like it could be the thing. Do you recommend I do a Full Data Reset to delete both WebOS and Android, then Create WebOS Volume to prep the device for WebOS, then WebOS doctor to get back to factory? Then if all goes well, then re-install Android?

I ask because the Full Data Reset sounds scary. I hope I can still access Moboot from there, for whatever that's worth.
4th July 2014, 02:39 AM   |  #4  
OP Senior Member
Thanks Meter: 50
 
448 posts
Join Date:Joined: Oct 2011
Quote:
Originally Posted by Moody66

Use jcsullins hp TouchPad Toolbox. Complete reset.

I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode.
6th August 2014, 06:27 PM   |  #5  
Junior Member
Thanks Meter: 2
 
20 posts
Join Date:Joined: Feb 2012
Quote:
Originally Posted by asif9t9

I posted in the Toobox thread, but just fyi, can you believe, Complete Reset didn't work! It's like my Touchpad is in read only mode.


Same exact thing is happening to me. Toolbox message says:

Code:
ERROR: LVM config erase check FAILED.  Possible read-only failure.
I have tried everything, and when it reboots, it is as if nothing changed. Check this out:

Code:
root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
  11 logical volume(s) in volume group "store" now active
root@webos-device:/#
root@webos-device:/# lvm.static vgremove store
lvm.static vgremove store
Do you really want to remove volume group "store" containing 11 logical volumes?
 [y/n]: y
y

Do you really want to remove volu......
It says it's removed:

Code:
  Logical volume "cm-data" successfully removed
  Volume group "store" successfully removed
Then right after:

Code:
lvm.static vgscan --ignorelockingfailure
  Reading all physical volumes.  This may take a while...
  Found volume group "store" using metadata type lvm2
STILL THERE!! LOL this is crazy... is it a hardware problem?

NOTE: This touchpad was sitting dead for 6 months. Charged it, turned it on, read only ..
The Following User Says Thank You to camaroqqq For This Useful Post: [ View ]
6th August 2014, 06:33 PM   |  #6  
OP Senior Member
Thanks Meter: 50
 
448 posts
Join Date:Joined: Oct 2011
I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well.
6th August 2014, 06:36 PM   |  #7  
Junior Member
Thanks Meter: 2
 
20 posts
Join Date:Joined: Feb 2012
Quote:
Originally Posted by asif9t9

I'm sad but glad at the same time others are afflicted the same as me. It means others are trying to fix problem so we might get a solution. I have this beautiful touchpad sitting at home dead now. When it did work, it was in read only mode. But the battery died out again and now I can't get it started up at all. But I know the battery itself is fine because when it was working...in read only mode...the battery held charge really well.

I used a *touchstone to charge mine. I've heard that can make a difference.

There are few threads on this read-only issue, but no fixes...
Last edited by camaroqqq; 6th August 2014 at 06:39 PM.
6th August 2014, 06:39 PM   |  #8  
OP Senior Member
Thanks Meter: 50
 
448 posts
Join Date:Joined: Oct 2011
Quote:
Originally Posted by camaroqqq

I used a touchpad to charge mine. I've heard that can make a difference.

There are few threads on this read-only issue, but no fixes...

Yeah the Touchstone worked the last time for me to charge it up. But it's not working anymore. Hard to believe two charging methods have failed at the same time. Either way I need to melt down the device to dispose of it because it has personal info and photos on it.
14th October 2014, 05:22 PM   |  #9  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Nov 2010
Getting same issues, been trying to sort for ages
This is what the state of mine is

Boots up Moboot 0.3.5
Cyanogenmod does not load just loops
Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again.
tried toolbox complete wipe says read only mode
WebOS Doctor recovery dies at 12%
tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it.

now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos.

but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue.
17th October 2014, 07:54 PM   |  #10  
Junior Member
Thanks Meter: 0
 
1 posts
Join Date:Joined: Oct 2014
Mine froze on Oct. 11
Yes, somewhat comforting to know that there are a few other cases of this. My first symptoms were that apps were starting to crash. Then I noticed that nothing I did would change the bootup state. Seems like a file system problem, but how could that information get overwritten at bootup? I hope one of the experts can shed some light on this problem.

Quote:
Originally Posted by earthcoder

Getting same issues, been trying to sort for ages
This is what the state of mine is

Boots up Moboot 0.3.5
Cyanogenmod does not load just loops
Does boot WebOS but Cannot Wipe the device, it reboots and nothing has changed, even removed a app and reboot and comes back again.
tried toolbox complete wipe says read only mode
WebOS Doctor recovery dies at 12%
tried the Guide to recover and everytime I rescan, it finds the "store" yet again, even after I've deleted it.

now confused, I can charge it too 100% with no issues, but found it best not to charge it on USB recovery mode, seems to charge ok from complete shutdown or in webos.

but read only mode cant fix tried loads of stuff but seems every post with others with issues seems to go off on something else un-related from the issue.


Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes