Related
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
wikedbubble said:
I recently aquired a Streak 7 and am having trouble resetting it since it has all the original owners info on it.
1. I encountered a force close error upon first boot.
- android.process.acore stopped unexpectedly
2. After this error continued to appear I said F*** this and rebooted into the Stock Dell recovery(Volume + and Power)
I chose option 3 for a factory reset and erase internal tablet storage.
Rebooted and Bam same bull**** errors. I did this 3 more times powering off with the pin hole off button after the streak kept booting with this error.
I read this entire forum development and general questions to see what problems others are having, I came across a few threads all very informative on how to attempt to restore your Streak 7.
Before attempting the various methods of either NVFlash, the fastboot method and even flashing clockwork recovery through fastboot I figured I would see what I could get the Streak to do in it's current state.
*Note* I am very familiar with ADB and Fastboot but if I over looked something I will not be offended if anyone can provide some useful information.
OK, Here is my story
I put the streak on my HDMI dock and was able to succefully install the ADB drivers on Windows 7 x64. From there I launched the ADB Shell
c:/androidsdk/tools> adb shell
$
once in the shell i found I could launch the android setting using this command
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Once in the settings and periodically hitting forceclose and quit to the .acore error I was able to retrieve this information
Android Version
2.2
Baseband Version
11.809.05.02.00
Kernel version
2.6.32.9
OEM Version
GLUNB1A132433
Build Number
14394
I also realized that I can install apps through adb so I went and installed the latest standalone ADW Launcher which installs fine and allows me to actually use the device a little.
c:\androidsdk\tools>adb install launcher.apk
1307 KB/s (2533717 bytes in 1.892s)
pkg: /data/local/tmp/launcher.apk
Success
You will notice that apps install to this location
/data/local/TMP
it turns out that even installing the new launcher won't allow me to do much because the previose owner changed his google password so I have no market acces or anything like that.
I then tried doing the factory reset within the Android settings>privacy>factory data reset.
The device reboots and I again encounter the same error and the device has also not reset the user data.
So i rooted the device and found that even root was only temporary, the ADB shell returns the # sign indicating that it has root, great but when the device is rebooted it returns to the condition I got it in.
If I run ADB remount with root I get this
c:\androidsdk\tools>adb remount
remount failed: Operation not permitted
c:\androidsdk\tools>
this tells me that even though the phone has root it will not mount any file system with read/write permissions
I then installed the latest free Clockwork Rom Manger via ADB
it prompts me for root permissions I select allow and then the app closes after it downloads and tries to write the clockwork recovery image. I said fine this won't work.
I moved on to the Flashing Clockwork Recovery via Fastboot
In Fastboot I get this
c:\androidsdk\tools>fastboot devices
? fastboot
c:\androidsdk\tools>fastboot -i 0x413C flash recovery clockwork.img
sending 'recovery' (4416 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.670s
c:\androidsdk\tools>
WOW I didn't know that 4MB could be sent and flashed over usb in under a second!!!! WTF!!!!!
So obviously there is something going on here where I cannot write to the internal memory...
I decided to just use NVFlash because people seem to be having luck with it
http://forum.xda-developers.com/showthread.php?t=1018809
I Didn't.......
I spent a hell of a lot of time downloading and redownloading the different images and finally got them all downloaded successfully. I run the restore.bat file and it says everything went fine but it didn't, I tried NVFlash with and without P14.img and it just doesn't seem to do anything it always restores it to how it was when i got it errors and all.
Now for the best method I tried, the fastboot method by flashing boot_orig.img, recovery_orig.img and system_orig.img
http://forum.xda-developers.com/showthread.php?t=1011654
Flash_image is not and ADB Shell command
and I also don't beleive the images are writing to the disc that fast.
I'm tired of typing now so please if anyone has any info on how I can write information to the internal ROM memory not the internal sd card I would greatly appreciate it.
Tom
Click to expand...
Click to collapse
Bump for a resolution. A lot of folks seem to be encountering this issue; I think it has something to do with a Linux failsafe measure (from another thread), but I'm not savvy enough in Linux to know for sure. Good luck to you!
Hey Thanks for the Bump, I am tearing my hair out over thins thing.
On another note I found this post for the LG GX2 for flashing clockwork recovery through APX with NVFLASH
http://www.techofweb.com/technology/flashing-cwm-recovery-g2x.html
I hope there might be a way to do this on the Streak, but I don't know that much about NVFlash. My hope in getting the clockwork recovery is that the restore and recovery tools used in clockwork recovery will in theory allow me to format and write roms to the internal memory...... I hope
Anyway I hope someone is reading and understanding my trouble other than Z4nd4r
Tom
I've been having similar problems with my streak7. It was working fine on stock 2.2.2 then got stuck in boot loop at the "stick together" screen.
I tried to factory reset in recovery. No change.
I tried to restore with nvflash. It completed fine, but no change.
http://forum.xda-developers.com/showthread.php?t=1018809
I tried with fastboot (boot.img, restore.img and system.img). It completed fine, no change.
I tried the 2.2.2 update.pkg in recovery, but it stops at "install modem error", no change.
I tried to flash DJ_Steve's honeycomb, and it stops at:
Formatting partition 2 BCT please wait... FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) message: nverror:0x2 (0x2) flags: 0
I tried formatting all partitions with:
nvflash --bl bootloader.bin --format_all
then restore with nvflash
It completes with no errors, but still no change.
I also tried to get clockwork on the streak 7 with fastboot. Even though I didn't get any errors, clockwork recovery did not get installed. So I'm thinking it's some sort of write protect error, since nothing I write to the device seems to be sticking.
If I format all partitions, would the streak 7 even get to the t-mobile "stick together" logo? I would think it would get stuck at the dell logo. I'm stuck at this point and have no idea what to try next. Any suggestions?
Could the problem be due to previous owner(s) trying to root the DS7 and Dell had implemented some kind of security measure to prevent rooting of the DS7?
Bump for a real solution.
I found a solution and my solution was to sell it before I threw it against a wall.
What's the common denominator, here? Were these all purchased used/3rd party?
Mine was bought new and ran great till mothers day and my sis asked to use it to post pics to facebook so I unmounted my sd and gave it to her she poped in her 32 gig sd card and got tired of waiting for the the gallery to populate and ejected the card without unmounting it and handed it back to me and said it was junk an and slow .......ever since its been stuck in read only
Ive dissasymbled it formated it flashed it factory reset it and reguardless of what I do still comes back the same as though I hadnt touched it.......even tried to short the nand chip out to clear it..........its like a cockroarch thats wounded .....it just wont finish dieing
I think we need a jtag solution. Doesn't seem like anything done with current tools will help.
I've scoured the internet and turned up nothing.
My streak 7 is collecting dust and probably going on eBay soon. To hell with Dell. This is my first Dell android device and probably my last.
Edit: found information
So I found the datasheet for the NAND chip the Streak 7 uses (http://omapworld.com/iNAND_e_MMC_4_41_IF_data_sheet_v1_0[1].pdf). Aparently the NAND has a write protect feature (temporary and permanent). Tech5 from this thread http://forum.xda-developers.com/showthread.php?t=1113264 says there's a failsafe function that locks the NAND in write protect mode. I don't have the hardware expertise to dig down and see if the system is write protecting the system by locking the chip in write protect mode. If we can somehow figure out how to disable the write protect on the chip, we may have a solution. Maybe someone with good hardware knowledge can take a look and give some feedback?
I'm having this same issue over here. I've tried NVFLASH and Fastboot and it acts like it's happening and then you reboot and get back to the same image every time. Maybe time for a call to Dell on this?
Call Dell
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Dell is the only solution?
I had a same problem too. No matter what I do, the unit reverts back. It became Read-Only Mode. I guess it happens often enough DELL aware of this problem and the tech supports knows what to do. Only way to fix the unit at this point is ship it back.
I shipped back to Dell and Dell repaired it. Turn Around time: 1 Week.
This is my 1st post.
I do have Streak 5 and 7. I love Streak 5 and DJ Steve's ROM Rocks in Streak 5.
wikedbubble said:
It looks like these Streaks are all stock and having the same problem. I tried calling dell but they wouldn't help me because the streak I got doesn't have the flap for the sd card and that is where they say the Service Tag is written. Freaking BullSh!t. Anyway if someone is willing to call dell and see what they have to say that would be awesome.
Click to expand...
Click to collapse
Settings > About > Status > Service Tag at the bottom.
I'm on the phone with Dell right now about this as I can't find another solution and another user had to get theirs repaired. We'll see what they say.
Solution to write protect?
I was trying to copy some music to mine and got the write protect error message. I took out the micro SD card holder and it indeed was locked. Flipped the switch and back in business! Hope this helps someone!
I wonder if it is newer streaks that are doing this, because I think mine was in stock with Tmobile for a while. They had plenty of them there. They must be "Locking the bootloader" so to speak. If anyone wants to send one to a Dev maybe they can do something about it.
any luck with this any 1? =(
I had a similar issue last week, it looks to be the "Read-Only" Bug. I had to send mine back to Dell, and they just sent me a new unit.
Whatever you do, make sure your DS7 does NOT hit 0% battery, it seems to be the cause of this "Ready-Only" bug.
I am just about to give up any software solution and contact HP to see if they can fix this as a hardware problem.
But before I do that, i thought it might be worthwhile to post my problem here first.
My touchpad has been running fine, and operating without any problems until recently when I installed new apps or downloaded new files on the touchpad.
While the touchpad was up and running, everything was fine, the apps appeared in the menu, and the files copied could be accessed without any problems.
In terms of functionality there was nothing to suggest any problems with the TP.
However, whenever I reboot the TP (soft or hard reboot), all newly installed apps or files disappear and the TP reverts back to a previous state. Nothing that I do to the TP remains after a reboot.
So I downloaded the latest webosdoctor 3.0.5 to reset the TP but after getting to about the dreaded 12% mark, the webosdoctor fails, spewing out a lot of message about parted failure and something about the flash.
Following all the tips on using novacom to boot the uImage and accessing the TP from novaterm does not seem to work as any fix initiated is lost on the following reboot.
Even while logged in to the TP via novaterm, and using lvm.static to remove the logical and physical volume to see if I can get webosdoctor to recreate the partitions did not work.
The command lvm.static vgremove reported to successfully remove the logical drive, but on subsequent scan using lvm.static vgscan shows that the logical drive is still persistent.
Removing physical volume using lvm.static pvremove did not work.
In frustration I deleted /dev/mmcblk0p14 (and all the mmcblk0???). Consequently the lvm.static scans showed no logical drive available.... but on subsequent reboot they are all back.
Webosdoctor again failed with same problem when rebooted.
It seems like the TP is falling back to some default memory (partition) state and nothing that I do remains persistent. I can't see anyway I can force the partition tables to reset as any changes are lost on reboot.
So unless someone can suggest something different, I am resigned to having to call HP and send my TP in for repairs.
Does anyone else have similar experience?
P.S. this started after I updated to webOS 3.0.5 but I can't say this was the exact cause.
I have the same problem with my touchpad. Are there any solutions?
it looks like the only way to get it fixed is to contact HP and send your TP back for repairs.
I will be contacting them next week when I have time to organise for it to be repaired.
Have you tried to run the WebOS 3.0.0 Doctor? It will resize all of the partitions and leave you with a fresh copy of WebOS. It can be found here: "http://www.webos-internals.org/wiki/Webos_Doctor_Versions".
Here is what I did:
1.Completely shut down
2.Boot into recovery menu by holding Volume-Up button and then pressing the power button.
3.Run WebOS 3.0.0 doctor
If it halts for any reason, let me know what percentage it stopped on, and perhaps I can help you out.
As I have tried to outline in the OP, I have tried webosdoctoring from version 3.0.0 to 3.0.5
It doesn't have any effect as any changes to the partition is lost once the TP reboots.
I know webosdoctor 3.0.0 is the standard answer for all partition related problems, but I think in my case it is not a partition problem but more of the flash controller, that is hardware related. It might have gotten itself into a funny state where it is constantly going into fall back mode after every reboot.
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
colin_404 said:
I'm sure you probably read this , but the" Factory condition restoration" thread might be useful.
Click to expand...
Click to collapse
This did not work for me. There is no way to remove /store
I'm having the same problem.
Device:
HP Touchpad 32 GB
WebOS: 3.0.4
Android: CM9 A2
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
What works:
- It loops while booting to Android
- It boots to Clockwork Recovery
- It boots to WebOS Recovery
- It boots to WebOS
- Everything works inside WebOS
- I can connect through Novaterm
What I've tried so far with no success:
- Recreating the file system
- Formating the internal storage
- Running a checkdisk
- Partitioning the storage
- Reinstalling Android
- Running WebOS Doctor 3.0.0, 3.0.4, 3.0.5
narci2500 said:
I'm having the same problem.
Problem:
Every time the device is restarted, all data "magically" restores to how it was. Example: if I format the internal memory and I restart the device, all data remains as if I didn't format it.
Description:
My Touchpad has somehow gotten into a state of data lock, where I can't format it, nor recreate the filesystem in anyway.
Click to expand...
Click to collapse
Nothing worked for me. Tried every trick suggested, even mixed things a bit. In the end I had to send it back to HP for it to be fixed.
All good now, it came back all fixed.
I'm having the same issue. Did they accept the return even with Android on it?
djteiwaz said:
I'm having the same issue. Did they accept the return even with Android on it?
Click to expand...
Click to collapse
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
cychoi75 said:
yeah they accepted it with no questions asked.
But make sure you do the trouble shooting with the online chat first, it will save you time on speaking with them on the phone.
Click to expand...
Click to collapse
good to know, thanks
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
djteiwaz said:
So an update:
I sent it in and they just called saying that it has a 3rd party OS installed and that my warranty is void. If I wanted them to repair it, it would cost $239 or I could have it shipped back unrepaired. So now I have a sort of bricked touchpad. Any suggestions?
Click to expand...
Click to collapse
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
rr5678 said:
Seems like it's stuck in some read-only mode. I have some ideas but you don't have the unit back, right?
Click to expand...
Click to collapse
Not yet. Should have it back by this weekend.
I also have this problem and have tried restoring my touchpad with numerous fixes on this site but they all fail and the touchpad just reboots to its previous state.
any help would be appreciated
Received it back. Would love some recommendations for possible fixes.
djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Okay. I'll gather some information now.
djteiwaz said:
Received it back. Would love some recommendations for possible fixes.
Click to expand...
Click to collapse
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
rr5678 said:
Bear with me. Just doing research. It's kinda hard since I don't have a device affected by this in hand.
Click to expand...
Click to collapse
Not a problem. I appreciate you spending time on this for me.
Hello,
there was Android installed before. But because it didnt boot I uninstalled Android like in the guide(video).
When I now try to put something in cminstall folder or create new cminstall, there is this issue:
i can temporary(!) delete/create and everythings seems fine. But once i plug out Touchpad and plug in again, there are the same files like before.
When i try to install with ACME command i get at the end this error on the Pad:
Unable to create unique name
Unable to locate filesystem on device "/dev/store/media".
resizefat failed! Aborting! Please reboot
I have another issue with WebOS.
I can't use Preware. When starting Preware it loads some stuff first and then there is a message at the top left:
template load failed: main/main-scene.html
Thanks for your help!
Sounds like you need a webos doctor.
With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.
GuelleX said:
With WebOS Doctor it stops at 12% and says "We were unable to reset your phone. Please go to Palm Support for help."
When i reboot everything is like before.
Click to expand...
Click to collapse
This should help
http://forum.xda-developers.com/showthread.php?t=1426244
It didn't help.
Same issue, it stops at 12%. But this time on pad, there is black chip on left AND hp logo in center after that. Before there was only one of it (don't remember which).
Also this command gives an "error": lvm.static vgcreate -s 8M store /dev/mmcblk0p14
The name is invalid or something (i can try it again and tell what it says exactly if necessary).
Any other suggestions?
Have you tried the touchpad toolbox tool that JC Sullins came out with recently? I used it the other day quickly and flawlessly. It can rebuild the volumes for Android and/or WebOS (yes, you can wipe WebOS from the touchpad). Give it a whirl.
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,
asif9t9 said:
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,
Click to expand...
Click to collapse
Use jcsullins hp TouchPad Toolbox. Complete reset.
Moody66 said:
Use jcsullins hp TouchPad Toolbox. Complete reset.
Click to expand...
Click to collapse
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.
Moody66 said:
Use jcsullins hp TouchPad Toolbox. Complete reset.
Click to expand...
Click to collapse
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.
asif9t9 said:
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.
Click to expand...
Click to collapse
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:
[email protected]:/# lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
11 logical volume(s) in volume group "store" now active
[email protected]:/#
[email protected]:/# 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 ..
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.
asif9t9 said:
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.
Click to expand...
Click to collapse
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...
camaroqqq said:
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...
Click to expand...
Click to collapse
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.
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.
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.
earthcoder said:
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.
Click to expand...
Click to collapse
Well this sucks... I appear to be stuck with the same issue as everyone else in this thread.
I mounted media volume in toolbox and used windows for format the drive. When I mounted it again the data was all still there...
I'm sad to say I trashed mine. Couldn't fix it. And didn't want to sell for parts because the memory had my personal data. Still haven't replaced the tablet because I can't find a better model for the price.
anyone ?
Anyone was able to fix this ?
somehow it can't mount to /data , I've tried all commands related lvm.static ( vgremove , lvremove..... ) it shows removed but after restart still there and nothing has changed.
tptoolbox could not fix , could not remove partitions .
acmeuninstaller and acmeuninstaller2 could not remove .
is this hardware issue or software ?
What version of TPToolBox are you using?
I haven't yet run across this problem in numerous wipes on (7) TPs.
Had one that the Mobo had gone bad on - couldn't do anything on that one. Another had a video gremlin, but I was still able to wipe it.
I wonder if maybe ADB and using shell commands might work?
_Dan
*UPDATE*
It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions.
To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as :
Install Android or Resize Android Volumes
- Problem w/ vgchange -ay
Repair Android Volumes
- FAILED: rc=5: vgchange -ay
Complete Data Reset
- ERROR: Invalid partition info: end-gap greater than 1 percent of mmc
I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff.
*edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either.
CriticalComposer said:
*UPDATE*
It looks like I managed to recover from this completely. I ended up doing a second TPDebrick but I made sure I specified 32gb this time. I don't recall what I put in last time but I'm guessing it wasn't 32 and that is what wrecked my partitions.
To preface, I had bricked my Touchpad and used TPdebrick to get it to boot again. I now have access to the boot menu and can get to TWRP and WebOS recovery just fine. However, TWRP won't let me install any .zips and shows 0mb on both the /system and the /data partitions. TPToolbox gives me a slew of problems such as :
Install Android or Resize Android Volumes
- Problem w/ vgchange -ay
Repair Android Volumes
- FAILED: rc=5: vgchange -ay
Complete Data Reset
- ERROR: Invalid partition info: end-gap greater than 1 percent of mmc
I'm using the same TPToolbox v42 that I used to originally install Android on my Touchpad. Just to confirm the files hadn't corrupted somehow I redownloaded the toolbox and tried again to the same results. Any help would be appreciated. I'm pretty good with basic/intermediate Android stuff but I feel a little over my head with this stuff.
*edit* I have since tried WebOS Doctor and it has told me it cannot fix my device either.
Click to expand...
Click to collapse
So glad you posted this. This is exactly what I did. When your mind is in all this other stuff thats going on its easy to forget that it could be as simple as this. Thanks!
I've got the exactly same problem.
Had Evervolve Kitkat on my TP and I didn't charge it for a long period. After that I wasn't able to charge or wake it up again.
With TPDebrick I could end in the boot menu, bu any further TPToolbox action failed.
For me it seems, the necessary volumes are either not available or of size zero.
I would like to revive the beloved TP, but have no glue how to overcome this situation
@@@ SOLVED @@@
recreated volumes with this instructions
WebOSdoctor 3.0.0 loading ... TPToolbox next