Related
First off this is completely from Rennat over at PreCentral
-------------------------------------------------------------------------------------
TUTORIAL: How to get the UbuntuChroot up and running for your HP TouchPad
Intro:
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.
Warnings:
I nor WebOS Internals take no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.
Step Zero:
- I have provided 2 different ways to set your device up to install the UbuntuChroot onto your device; use the meta-doctor and create your own doctor (Step 1-A) or do as Step 1-B says and contact my army of monkeys for an easier alternitive that won't take forever.
##You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so! And done hesitate to ask questions.
Step 1-A: Creating a WebOS Doctor
- We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
- Use the WebOS Internals Guide to installing and running the Meta Doctor. In Step 2 you will have to rename you downloaded webOS doctor to the name of the Bell Mobility doctor they have under Step 2'3 (webosdoctorp100ewwbellmo.jar) go ahead and add the webOS version after it like it advises.
- In Step 2'6, if you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
- Once the Meta Doctor is done, run the Web's Doctor it created under the 'builds' folder. And setup your device.
Step 1-B: Contacting My Army of Monkeys
- If you are having trouble with or are intimidated by Step 1-A go ahead and contact my army of monkeys at [email protected]. Simple.
Step 2: Mounting the new ext3fc partition on bootup
- Now before we continue we have to make sure we have the partition fully setup and mounted on bootup. To do this follow the below WebOS Internals instructions.
All of this is done on device either via novaterm or an SSH login. (simpler terms mean use WebOS Quick install by connecting you device, opening WebOSQuickInstall, and click Tools-Command Line.) If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:
Code:
mount -o remount,rw /
mkdir -p /media/ext3fs
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.
Code:
mount -o remount,rw /
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.
Code:
mount -a
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.
Code:
mount /dev/mapper/store-ext3fs /media/ext3fs
Click to expand...
Click to collapse
Step 3: Adding Testing Feeds
- Follow these WebOS Internals Instructions to add the Testing Feeds.
NOTE: These are edited slightly and will only work on a Wifi only TouchPad.
- Open Preware and wait for it to finish loading.
- Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
- Scroll to the bottom until you see the New Feed box.
- Type or paste a name (webos-testing-armv7) and URL (Right Click - Copy Address) sure the URL does *not* have a slash at the end.
- Make sure the IS COMPRESSED option is set to YES.
- Tap Add Feed and then tap Yes when the alert pops up.
- Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.
Click to expand...
Click to collapse
Step 4: Installing UbuntuChroot, Xecutah, and XServer
- Open up Preware and tap List Of Everything.
- Search for and install the following: UbuntuChroot, Xecutah, and XServer
- Now opened Xecutah and tap XServer and a new card will come up.
- Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
- Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:
Step 5: Installing Programs
- Now to have some fun after all that work you put in!
- Type the below and it will update the program lists.
Code:
apt-get update
- Now type the following to install what ever you wish!
Code:
/***type the below for AbiWord
apt-get install abiword
/***type the below for the Chromium Browser
apt-get install chromium-browser
/***type the below for GIMP
apt-get install gimp
/***type the below for Eclipse
apt-get install eclipse
/**type the below for LibreOffice
apt-get install LibreOffice
/***type the below for LXDE (a windows graphical interface) and then launch it by typing lxsession.
apt-get install lxde
---------------------------------------------------------------------------------------
agian from precentral enjoy guys
Mods please move to there thread i was in a rush (dead battery) and put it in the wrong forum
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
linkinpark4175 said:
Does anything else besides chromium, abiword, eclipse, libreoffice, lxde and gimp work?
Click to expand...
Click to collapse
anything you can compile for ARM or want to compile for ARM. there is a apt repository.
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
same thing
XDAnoobr said:
You could also find a complete guide to install Ubuntu Linux on HP TouchPad here
Click to expand...
Click to collapse
agian that is only for Chroot which is the exact same thing
Works great, now I have lxde on my touchpad.
able to get ubuntu chroot working properly, with libreoffice
now, hunting for a Bluetooth Keyboard
any one going to test if BT Mouses work? (yeah, i know theres a touchscreen)
Is multi-touch supported on this?
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
harsh3090416 said:
what version of libreoffice does it install the latest one? And if anyone has installed it the ubuntu laggy or is it normal.
Click to expand...
Click to collapse
a little laggy sometimes, but still usable most of the time without any problems
libreoffice 3.3.2... you should probably check the ubuntu ARM 11.04 repository to see what is there
top says 1gb ram, 0.90gb used.... not sure why......
EDIT: Tried pairing a BT Mouse... able to find the device via "BT->Search other", but unable to pair properly. Mouse said paired successful, but touchpad couldnt continue, kept searching for devices
Tried "BT->Search Keyboard", but couldnt find the mouse this way
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Is there a way to make that partition without meta doctor?
DJGonzo said:
Is there a way to make that partition without meta doctor?
Click to expand...
Click to collapse
metadoctor makes a partition
you could loop a filesystem ontop of the existing partition to avoid this issue, but the page below recommends against it
http://www.webos-internals.org/wiki/Chrooting
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
samvillian said:
mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
r directory
Why am i getting this error when trying to mount? It's really ticking me off as I haven't done anything different from the instructions.
I just spent an hour redoing the whole thing and guess what... i'm pissed off
same ****
Click to expand...
Click to collapse
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
kevina90 said:
Now they have Debian chroot. Works great as well. Both can coexist at once. All it is is a folder at /media/extfs
Btw, has anyone gotten gnome working? I keep getting segmentation faults.
Click to expand...
Click to collapse
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Komodo Rogue said:
Sorry, this is off topic. I'm sure Android will get here, but I really want to use my Touchpad (I haven't done much because I figured everything would get wiped anyway this weekend), so I think I'm going to give Linux a go. My understanding of Linux is rather crap. I thought Linux was the OS, and Ubuntu and other things were just GUIs to make it easier for people unfamiliar with command line. How could Debian simultaneously coexist?
I know I could go to wikipedia and look around and try to understand it, but by chance does anyone know any website that kinda describes Linux to beginners? I don't just want to follow the directions step by step on the guide (although its brilliant, looks very easy)without having the slightest effin idea what everything is, you know? Its weird, Linux confuses me, I don't know why. I've used ubuntu a number of times but it's just browsing firefox, not exactly rocket science!
Thanks if you can easily give link and press send then thanks but don't go out of your way, I can find something eventually, but I don't want someone else mucking around for my sake. Its no emergency.
Click to expand...
Click to collapse
I would just find a book on amazon about linux with good reviews made in the past 1-2 years. I would look for one that is distribution neutral.
The reason you can have webos on there and another version of linux is because it's basically installed in another partition (not really, but that's the easiest way I can describe it to you). The actual details of how chroot works are different, but that should relate enough to you to get what it it is.
Linux is the Kernel. Debian, Ubuntu, Fedora and the rest are distributions of that kernel along with a GUI, and programs to make it a fully functional OS like Windows or OS X.
The Debian and Ubuntu on WebOS is minimal pared down distribution with no gui.
I just went thru all the steps , contacting the army of monkeys, and installed all the preware stuff.
I get Service Error Unable to run command : /sbin/initctl start org.webinternals.debian-squeeze etc etc
Unknown job org.webosinternals.debian-squeeze-chroot.
I got this with the Ubuntu chroot too. any ideas?
paperWastage said:
looks like you didn't do metadoctor properly,
or you didn't make the /media/ext3fs directory,
or "mount -o remount,rw" didn't execute properly
1st problem: your touchpad should have around 10GB free(out of 16GB, or do the math if you have a 32/64gb)
2nd problem: go back to cmd prompt and check that /media/ext3fs exists
3rd problem: reinstall via webos doctor and do it again
Click to expand...
Click to collapse
I've redone webos doctor like 4 times already.
How do I check if the directory exists? Plus i'm on a fresh 32gb, so its not that.
thanks
edit: i tested to see if the directories existed and i found a possible error.
i just cd to the folder to see if it exists, and media/ext3fs existed.
but the /dev/mapper/store-ext3fs doesn't exist apparently...
would that be the issue?
is there any possible way to do this. obviously getting rid of webOS is a silly thing to think but i have installed arch on my touchpad but so badly want android as well.
i really wish webOS had a more developed app market
I dont see the problem in here?
I got webOS, cm7 alpha and archarm on my 32GB TP.
WebOS will definately get kicked if there is a safe way. cm7 will be exchanged with cm9 and i would prefer ubuntu with unity on the TP
k1l said:
I dont see the problem in here?
I got webOS, cm7 alpha and archarm on my 32GB TP.
WebOS will definately get kicked if there is a safe way. cm7 will be exchanged with cm9 and i would prefer ubuntu with unity on the TP
Click to expand...
Click to collapse
Is there a how-to out there? I see a way to get a CLI Ubuntu to boot inside of WebOS and then LXDE X on top of that but I haven't see a way to boot in to linux natively. I have seen posts talking about Moboot being worked on to accommodate. Have I missed or just not looked hard enough? I'd like to get a native Linux installation going.
Edit: May have misread your post. If you are running a chroot jail that's cool. Just not something I'm really interested in. I'm with the OP. I'd prefer an actual triple boot from shutdown.
archlinux is not a chroot....
just look at the thread and install it.
you'll be running all 3 OSes in no time.
You just have to be able to read and follow directions.
that is all.
I asked because I had webos and arch running but when trying to run cm7 it just errored out. I'm obviously thinking there was some conflict with partitions?
Sent from my Touchpad using xda premium
jonjon68 said:
Is there a how-to out there? I see a way to get a CLI Ubuntu to boot inside of WebOS and then LXDE X on top of that but I haven't see a way to boot in to linux natively. I have seen posts talking about Moboot being worked on to accommodate. Have I missed or just not looked hard enough? I'd like to get a native Linux installation going.
Edit: May have misread your post. If you are running a chroot jail that's cool. Just not something I'm really interested in. I'm with the OP. I'd prefer an actual triple boot from shutdown.
Click to expand...
Click to collapse
just take a look at the threads here in this subforum. there is chroot ubuntu and a native ubuntu. im not running a chroot arch. its a native arch which i select at start in moboot.
and really really read the instructions carefully. its no howto for noobs with 10sec. patience.
@ sissons87. the cm7 installer is programmed to find a TP with just webos and then move the partitions. that is the problem i think.
k1l said:
@ sissons87. the cm7 installer is programmed to find a TP with just webos and then move the partitions. that is the problem i think.
Click to expand...
Click to collapse
thanks for the help, i did think that but wasnt to sure. i know have take arch off the TP now and running webos and CM7. might now be able to resize the FAT partition to install arch
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
bone625 said:
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
Click to expand...
Click to collapse
Take a look at this thread. I think it could have information that could maybe help you.
forum.xda-developers.com/showthread.php?t=1508572
Thanks, bah tried all that - the problem is mounting USB recovery, can't get into androidto test anything else. I'll have access to a few other computers this weekend so I"ll see if they can find it. Going to rewipe everything tonight as well, will update... pretty annoying.
I have an idea.
What you can try is to reboot into WebOS, mount the /media drive so you can copy files to it from Windows. On that media drive, there should still be a folder called cminstall. Copy the moboot install zip back into there, and then reboot the tablet into recovery (Power+VolUp). From there, run AcmeInstaller2 again, and you should be good to go - it'll run, and force an install of the contents of that /media/cminstall folder, which'll put Moboot back in place.
At least, that's what SHOULD happen. I'm no expert, but from what I've seen and played with, that should do what you're trying to achieve.
Thanks for trying.. Not exactly what it needed to be fixed though. I have everything ready to go in uninstall, the computer (any computer I've tried so far, and its been quite a few - that all used to read the touchpad in recovery mode) won't register it and mount it as a drive so I can run ACMEInstaller in the first place.
It must have changed something on the touchpad itself, because it used to mount fine before that happened... Now every computer installs it as palm novacom booties and never mounts the actual drive, and acmeinstaller just says no device or something like that. Bah, still can't figure it out, I miss android haha.
Did you enable MTP in the advanced menu under the Storage section?
Are you trying to get the device to show up in adb? If you are having troubles with that I found a really nice guide on another website on how to get adb to read the touchpad if nothing else is working. Not sure if I can post the link or not. Send me a pm if this is something you need.
Sent from my cm_tenderloin using xda premium
Problem is I can't boot into android cause the bootloader broke and I can't get it to boot android period, even with cyboot. I know all l I have to do is run ACME again... But I can't run it cause it won't mount haha. Stuck in webOS for now, and every computer I've tried won't boot recovery mode anymore. Drivers check out and register but can't change anything to recognize it as a drive. I think I'm going to try to manually uninstall everything android, then reinstall webOS and see if it mounts then. Blah!
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
Click to expand...
Click to collapse
This trick with webOS doctor just saved my ass. I couldn't boot past the green cyanogenmod splash screen and needed to boot straight off an image from moboot on my desktop, and taking webOS doctor to that step was the only thing that would let me run the command line entry to make it where my PC would talk to my touchpad. So, thank you
Would this work for a TP that reads both ways on PC as listed by OP but is only stock?
bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
Click to expand...
Click to collapse
What do mean by run ACMEInstaller? I only know using the novacom boot mem:// <ACMEInstaller method, though that's getting stuck while on the two penguin screen.
Hp touchpad 32GB converted into Android 4.4.4.KitKat with ROM CM11
Hi My name is Ramadoss.N Recently I have converted my touch pad to Android KITKAT 4.4.4. with Rom CM11 -20140625- Snap Shot- jcsulline. I used TPtoolbox V41d to install. Everything working fine. except few observation.
1. Bottom Menu Button like Home , Return to previous screen are not working in vertical position of touchpad, where as it works in Horizontal position.
2. There are 3 dots on right hand side corner to provide dropdown menu: it works in vertical position, does not work in Horizontal position.
3. search icon ( which looks like a magnifying glass) does not work in both positions.
4.Back space key working in Vertical position, does not work in horizontal position.
5. Could not load Music via computer after installing Android in the Touchpad,
I really appreciate if any one can give me solution for above.
Regards
Ramadoss.N
email : [email protected]
HI, I am trying to update my HP tablet to 4.x.x with a data media partition. I booted to webos, used the webos quicksetup application to install preware then installed tailor. With tailor I deleted the android partitions and created new partitions. I ended up with something like this
system = 600mb
cache = 200mb
media = 600
data = 11.2
Then I rebooted WebOS and got the message "Not Enough Storage to Download. You must clear space n your drive before you can download."
I cannot install stuff with quicksetup any more. it just keeps trying forever and does not do anything. My Mac only recognizes a 600mb partition for WebOS and wants to initialize it.
Any ideas how to fix this?
Jonathan
jonawald said:
HI, I am trying to update my HP tablet to 4.x.x with a data media partition. I booted to webos, used the webos quicksetup application to install preware then installed tailor. With tailor I deleted the android partitions and created new partitions. I ended up with something like this
system = 600mb
cache = 200mb
media = 600
data = 11.2
Then I rebooted WebOS and got the message "Not Enough Storage to Download. You must clear space n your drive before you can download."
I cannot install stuff with quicksetup any more. it just keeps trying forever and does not do anything. My Mac only recognizes a 600mb partition for WebOS and wants to initialize it.
Any ideas how to fix this?
Jonathan
Click to expand...
Click to collapse
bump. Anybody? When I go to device information I see Memory 16GB Available 0.0GB There's got to be somebody out there who can tell me how to redo the partitions.
I'm assuming Tailor will not let you resize your webos media partition?
If not, the easiest way may be to use AcmeUninstaller2 to completely remove Android, and start again but leave webos a larger media partition.
I have a 16gb Touchpad and have left 2gb for webos media, seems to do the job.
Cheers
Chris
chris5s said:
I'm assuming Tailor will not let you resize your webos media partition?
If not, the easiest way may be to use AcmeUninstaller2 to completely remove Android, and start again but leave webos a larger media partition.
I have a 16gb Touchpad and have left 2gb for webos media, seems to do the job.
Cheers
Chris
Click to expand...
Click to collapse
Thanks Chris
I can't install tailor because there is not enough space to install anything. I will look at AmeUninstaller2 when I have a bit of time. I hope it is something I can do from a PC or Mac because there is no way I can install anything to that TP or even read the webos drive... at lease from my macbook.
AcmeUninstaller is used in the exact same way that you would have used AcmeInstaller to get Android into the Touchpad in the first place.
I would use AcmeUninstaller2 from here to get rid of Android partitions and Acmeinstaller4 or 5 from that post install Android again.
Cheers
---------- Post added at 02:47 PM ---------- Previous post was at 02:19 PM ----------
It seems that going straight to a data/media build from scratch is difficult, if not impossible, due to the resizing required. You have to have JB/CM10.x installed first.
However, if you want to try Kitkat, and don't want to mess around with resizing partitions, this is an excellent rom!
Cheers
chris5s said:
AcmeUninstaller is used in the exact same way that you would have used AcmeInstaller to get Android into the Touchpad in the first place.
I would use AcmeUninstaller2 from here to get rid of Android partitions and Acmeinstaller4 or 5 from that post install Android again.
Cheers
---------- Post added at 02:47 PM ---------- Previous post was at 02:19 PM ----------
It seems that going straight to a data/media build from scratch is difficult, if not impossible, due to the resizing required. You have to have JB/CM10.x installed first.
However, if you want to try Kitkat, and don't want to mess around with resizing partitions, this is an excellent rom!
Cheers
Click to expand...
Click to collapse
Thanks for the Help
Ok I ran ACMEuninstaller2 on the Touchpad. Still same problem. When I go to Settings Device Information I see I have 16GB memory but 0.0 available. This is with Only WebOS installed no other apps. I have tried resetting the TP and erasing USB drive and Full Erase too. Any suggestions now?
Strange... When its plugged into a computer and you look at the files/folders, does it still tell you there's no storage space left?
Have you used webos doctor to restore partitions?
This thread may hold some clues/answers...
Good luck, cheers
chris5s said:
Strange... When its plugged into a computer and you look at the files/folders, does it still tell you there's no storage space left?
Have you used webos doctor to restore partitions?
This thread may hold some clues/answers...
Good luck, cheers
Click to expand...
Click to collapse
The computer only sees 1.4G of space that it wants to format because it can't read it. I figure that is the webos Space.
Ok, sounds like you need to use webos doctor to restore the original partitions.
Use version 3.0.0 first, then update to 3.0.5. Its a pain maybe doing it twice, but only 3.0.0 will restore partitions properly.
Cheers
chris5s said:
Ok, sounds like you need to use webos doctor to restore the original partitions.
Use version 3.0.0 first, then update to 3.0.5. Its a pain maybe doing it twice, but only 3.0.0 will restore partitions properly.
Cheers
Click to expand...
Click to collapse
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
jonawald said:
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
Click to expand...
Click to collapse
I guess I need to do this. Quoted from the Wikki
If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).
If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.
I am stuck at this part. I tried uncompressing the .jar folder. but could not find anything I could identify as a ulmage. This is the 3.0.0 image. Could you break this down a bit for me? I am using a Mac, but should be similar to PC. Many thanks in advance.
First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):
novacom boot mem:// < nova-installer-image-castle.uImage
After it boots, run novaterm:
novaterm
Once connected to the device, type:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
then type:
mkdosfs -f 1 -s 64 /dev/store/media
Once that completes, put the device back into recovery mode and run the webOS Doctor.
"I am stuck at this part. I tried uncompressing the .jar folder. but could not find anything I could identify as a ulmage."
I think its in a zip file called webos under 'resources'.
Also look through this thread, it may help.
Cheers
jonawald said:
Ok so what's the next step? Webos Doctor failed at about 8%. The screen changed from the USB symbol to the HP logo, then just before it was supposed to get that down arrow it exited.
Jonathan
Click to expand...
Click to collapse
Did you have any version of android installed and if so did you run ACMEUninstaller 2 before running webOS Doctor?
sstar said:
Did you have any version of android installed and if so did you run ACMEUninstaller 2 before running webOS Doctor?
Click to expand...
Click to collapse
I had ICS installed. I ran ACMEUninstaller2. Thanks.
jonawald said:
I had ICS installed. I ran ACMEUninstaller2. Thanks.
Click to expand...
Click to collapse
Hi have a read of these 2 thread's (There only 6/7 pages long) http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/ , http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-4.html .
Hopefully they will be of some help , good luck.
sstar said:
Hi have a read of these 2 thread's (There only 6/7 pages long) http://rootzwiki.com/topic/14249-th...8-12-stopped-no-sd-opps-reformat-crap-thread/ , http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-4.html .
Hopefully they will be of some help , good luck.
Click to expand...
Click to collapse
Thanks. I am reading them. Will give it a shot when I have a bit of time again.
Jonathan
jonawald said:
Thanks. I am reading them. Will give it a shot when I have a bit of time again.
Jonathan
Click to expand...
Click to collapse
One more thanks to everybody. I got that Touchpad up and working perfectly again.
Jonathan
So looking into the guide posted here, https://forum.xda-developers.com/ha...ide-installing-official-chrome-os-pc-t3865697,
it looks like we have a full proof way of installing a real chromeos NOT chromiumOS..
I've actually got it installed on an external ssd, i tried with just a fast usb disk, but smartctl gave me issues
i was able to get smartclt working with
in a 2nd vt,
Code:
smartclt -d sat -T verypermissive
which made smartctl accept the usb chipset but i couldn’t seem to get this into the chormeos-install.sh script.
anyway -
so I went with the SSD, and it all installed fine. took about 10 minutes, however, I cannot get the external SSD to boot.
we have a script here written by alesimula, how might one modify it to our advantage?
https://raw.githubusercontent.com/incod3x/chromefy/master/chromefy.sh
Hi @puccaso,
Well spotted! Have you been able to boot ChromeOS on RPi3 finally?
Hello @micx_pl!
Hope this message finds you well.
I was never really able to get it working - the SSD install seemed successful, I never got it to boot in the end.
I jumped over to fydeos, but that was just too slow - something very buggy there..
Any luck yourself?