Hello I have big problem my touchpad doesn't boot on web os(fortunatly I have android ics and its work perfect)
When I choose to boot on web os it says boot failed
Please somebody help me
Did you delete any of the uImage files from the /boot partition? I am guessing a web OS doctor should fix it (and wipe webOS).
Related
Hi all,
I attempted to mount the CyanogenMod andorid partitions from terminal in webOS, but
Code:
mount -t ext4 /dev/store/cm-cache /cmc
fails with "No such device" message. The same goes for the /dev/store/cm-data and /dev/store/cm-system partitions.
I noticed that neither of my /proc/filesystems or /etc/filesystems file has ext4 listed in it. Does it mean webOS doesn't support ext4 at all?
I was trying this because my cyanogenMod won't boot any more (stuck in the boot animation). I later realize I could mount the partitions in clockworkMod recovery and took a look at the log files, but unfortunately none of log files I could find provided any insight. Any suggestion on where to look is also much appreciated.
darkassain noted that the native webOS builds don't support ext4. Also I have fixed the boot issue on my touchpad. See the same topic on rootzwiki here:
rootzwiki.com/topic/84818-mount-cyanogenmod-ext4-partitions-in-webos/
I've updated to CM10.1 and following this CM11 using ACMEInstaller5. I think the partition sizes have messed up though, lvm lvscan shows cm-data as only 1.5gb (Android's Settings >> Storage shows as 1.48gb total space and only 162MB remaining), /dev/store/media is 8gb. I've got the 16gb touchpad, so something's gone wrong somewhere!
Another issue from the CM10.1 update is WebOS doesn't allow new app updates or installs - everything comes up "install failed", meaning I can't get into HP App Catalog to install Pre-Ware or Tailor. I can access novacom, adb etc, though when I try to extend2fs the /dev/store/media partition it says there's a problem with the super-block.
Any ideas or help? Much appreciated!
Update: I'm trying with PhilZ CWM 6.0.4.7 after trying 6.0.4.5 and 6.0.1.9, I'm getting the following error:
Resizing cm-data to 12288MB using free space from media
Scanning media (SD Card)
fsck.vfat media failed rc=1
>> FAILED <<
Also fails with the 2048MB cm7 resizer, same error message.
Any thoughts? Thanks!
I've managed to use WebOS Quick Install to get Preware and Tailor onto the tablet. Tailor said there was a problem with the cm-data file system, fixed it and now I can add the 2GB "unused" file space into it so I'm up to 3.5GB. The usb (media) partition however comes up with errors and refuses to repair, is there any way of rebuilding the partition without wiping everything with Web OS Doctor?
I would try acmeuninstall2 to remove android. Then at least install preware and tailor in webos.
I've tried flashing my LG 4X HD with Zaiben RC8 using TWRP but it got stuck after the LG spalsh screen. Went back to TWRP and noticed that it was showing 0MB of Internal Storage and can't mount/format the /data partition. Managed to change the recovery to CWM through TWRP's terminal but still cant format/mount it. Does any1 have any idea on how to proceed? It also doesn't appear listed in ADB...
EDIT1: Also can't mount/format /sdcard partition... I was using latest cm10.2 previous to trying to flash zaiben... :/
Update2: Managed to get it connected to ADB, but still don't know what can I do to solve this...
update3: It seems I can't get into fastboot...
Only after a few many hours I noticed that the Mounts and Storage menu in CWM 6.0.4.5 was scrollable, and the last format option in there did actually format the whole /data partition and allowed me to mount it and flash a new ROM afterwards still don't know what caused this, though.
I'm stuck at the Teamwin loading screen with the screen going dark and then back to the Teamwin screen.
Partitions are converted to f2fs. (ev_tenderloin-6.0-testing-2015.11.28 was the last upgrade I had installed and boots fine, but when I went to install a newer build i discovered this problem.)
I have used adb to reinstall twrp (its funny while it wont go past the Teamwin screen I can use adb push to try different recovery's) and get the same issue. If I install any other build (twrp / cwm) it will boot into recovery, but since none of them have f2fs support (unless there is another twrp or cwm build that has it?) it will only see the webOS partition.
tptoolbox v42 wont install android because:
e2fsck: bad magic number in super-block while trying to open /dev/store/cm-cache
/dev/store/cm-cache:
The supperblock could not be read or does not describe a correct ext2
filesystem. If the devoce os va;od amd ot rea;;y cpmtaoms am ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
esfsck -b 8193 <device>
e2fsck -fp detected error on fs on vol cm-cache rc=8
Click to expand...
Click to collapse
So I guess my question boils down to is there anything else I can try to fix this or do I need to just use tailor to reformat Android system, Android cache and Android data then tptoolbox to reinstall?
I went I used tailor to destroy and rebuild my android partitions and reinstalled, so for now at least the issue has been resolved.
Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!
Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.
Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?
CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.