I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
I wouldn't completely advise removing it - maybe rename it so it's still there, but just hidden, in case you have to return to it with WebOS Doctor or anything. Especially since it's the only way to go about using ACMEUninstaller / ACMEInstaller2 / WebOS Doctor / Recovery images and the like.
Then again, I just did some looking in the /boot, and can't see anything about that recovery, unless it's tied into the WebOS one.
UnderZone7 said:
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
Click to expand...
Click to collapse
I wouldn't remove webOS, not only for the reasons ve6ay stated above, but because I find webOS very useful. It is a useful and elegant os, battery life is much better, and that's the beauty of the TP, the ability to dual boot.
The nice thing is, if you remove the Moboot entry for WebOS, you don't actually remove WebOS - you just remove the option to boot from it. BUT you also can bring it back with just a quick terminal command (I noticed this during my poke-around of /boot as I stated earlier).
Besides, if you want to skip it entirely, you can create two file in your /boot directory directly from your CM install.
I used Terminal Emulator, but you can from Root Explorer, too. Browse to /boot, mount it (hit the mount r/w button up top), hit Menu => Create New File. Call it "moboot.timeout" (without quotes). Long-press it, click Open With, choose Text Editor. In there, as the only line there, type in your timeout - (if you want it to be always super-fast, chose 1), then hit enter, back, then save.
Second file to create is one called moboot.next - which basically says "On next reboot, always choose <selection>" To use this, again, Menu => Create New File => Long-press it => Open With => Text Editor. In here, type in CyanogenMod, hit enter, back, save, and then reboot. On reboot, you should automatically go straight into Android, no options to go anywhere else.
Or, if you can stomach booting into WebOS long enough, install Cyboot from Preware, and use it to make your changes to the timeout and default boot options. I just did this, and can tell you, if you do set Next to Android, and timeout to something abysmally small, you automatically will boot into Android, no choice of anything else.
Hope that helps you, mate.
You REALLY don't want to do this, as stated above if something goes terribly wrong it's the only way to use ACMEInstaller and stuff. Even WebOS takes not much space and pretty cool, so i choose to leave it, but recovery is a must..
Related
This thread puts all the necessary steps together for sucessfully run the Android-release from THIS thread on the X1. Since many seem to have problems with that this may become handy
So lets get started!
What you need:
- latest XPEROID-release, fatsal-xperoid-20100221.7z, get it here
- 7zip to extract it, get it here
- sd-card, using fat32-filesystem with 500MB free space
What you need to do with it:
1. Extract fatsal-xperoid-20100221.7z on your computer. This will give you the following files:
- calibration, wlan-firmware
- haret.exe, runs the linux-kernel and android
- initrd.gz, initial ramdisk, needed for linux to boot (phase one)
- modules-2.6.27-00888-g339bdfc-dirty.tar.gz, linux- and android-driver for wlan
- rootfs.img, contains files needed for linux to continue boot (phase two)
- STARTUP.TXT, contains the parameter for haret.exe and boot-options for linux-kernel
- system.sqsh, contains all android system files
- zImage, contains the linux-kernel
- conf/*.user.conf, configuration files for android
- AndroidApps/*.apk, applications for android, installed during boot
2. Delete all the *.apk-files from the AndroidApps-directory. They are not needed for running android. You should keep the directory, just delete all files in it.
3. Download some essential android apps here, you will get essential_apps.zip. Extract it and put the apk-files into the AndroidApps/ folder.
4. go to conf/ and delete eclair.user.conf, then rename eclair.user.conf~ to eclair.user.conf. That will disable the swapfile.
5. open startup.txt and remove the mem-option mem=102M. This was suggested by hotlein here. That will increase the memory from 102m to 182M and improve android speed alot.
6. Copy all files and directories to the root of your sd-card. Do not create any directory, just copy them to the blank sd-card.
7. Put the sd-card in your phone if not already done. On the X1 open the sd-card and run haret.exe. You will get alot text running across the screen. During the boot-process, one file is created.
- data.img (256M). This file contains all the files normaly stored on the android-phone. Your settings, Applications, media, etc. You can always delete this file to reset android. It will be recreated.
First boot takes a while to complete, so be patient. Finally you should get the android welcome screen. Follow the on-screen-instructions and you are done!
Changing some settings
- IMPORTANT: Disable GPS in settings -> location & security -> Use GPS satellites, because it will hang the device!
- Turn off locks screen when holding red call button. Spare parts -> End button behaviour -> Nothing. That will simplify the shutdown procedure. Credits go to Reversedhex: Post
Now let's stop android
1. Press and hold the end-call-key. The phone starts to vibrate like crazy, ignore that.
2. After a few seconds a menu pops up. Dont release the button yet, keep holding it! If you changed end button behaviour, you can release it now.
3. Press down on the digi-pad. You may press it three times to go to the shutdown-option.
4. Now you can release the end-call-key. If you do not hold it, you will end up in the android lock screen.
5. Select shutdown option and confirm. Then android shuts down.
If you try another kernel-image (that is replacing zImage), the system may lock up during shutdown. Then you have to soft-reset your phone. But you should always try to shut android down.
Now you can update the linux-kernel:
1. Download the kernel-image, get the latest here. That gives you zImage_kovsky_20100325.zip.
2. Extract zImage_kovsky_20100325.zip to get zImage. This is the linux kernel.
3. Copy zImage to the root of your sd-card. You should always back up your existing zImage so you can go back.
4. Download wlan-modules, as they must match the kernel-image, get them from here. That gives you wlan-modules_20100325.zip.
5. Extract wlan-modules_20100325.zip to get modules-2.6.27-01006-ga30aafa-dirty.tar.gz. This archive contains the wlan modules. Do not extract this. Simply put this on the root of your sd-card. On android startup this file will be extracted on the modules copied for you.
As suggestet by angusmcb (post), i used for the latest kernel the latest cross-compiler.
Latest kernel from xdadev-repos with backlight control and correct battery readout, get it here. The archive also contains matching wlan-modules.
Troubleshooting
Q. Android will not boot
A1. check if all needed files are present
A2. check if you have enough free space on card. Android creates two big files during first boot, so you will need at least 384M free space.
A3. you can try to delete data.img and swapfile to reset android. This helps if you messed up settings in android.
Q. Wlan wont start
A1. check if file calibration on sd-card-root
A2. check if file modules-*.tar.gz matches kernel-image
A3. you may try to enable wlan in windows mobile before running haret.exe
Q. How to stop android from using data connection
A. go to settings -> wireless & networks -> mobile networks -> access point names and delete all apn-settings
Q. Android-screen is upside-down
A. Slide out keyboard -> android switches to landscape. Then slide keyboard in -> android switches to correct portrait.
Q. I have no ringtones
A1. Put the ringtones in the MEDIA\AUDIO\ringtones folder (post, post for folder structure)
A2. Take a look at this post. Some characters make the android media scanner crash.
Q. I can not enter pipe-symbol. Where to find keymaping
A1. Press function key, followed by shift key, followed by commer key (right hand side of space bar) (linuxtux post)
A2. For keymapping in general take a look here. That is the default android keymapping.
Q. I want live wallpapers
A. Here you go. But be prepared for performance loss.
Q. I can not send SMS
A. Check this post by jimipoh. It might help.
Done for today
reserved for future updates
also reserved for future updates
and this, too
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
What the F?
♥♥♥
Good luck~♥
Muo said:
vdelf, are you going to be taking over development for Android on the X1 as well? Or will this be instructions to get fatsal's functioning?
Click to expand...
Click to collapse
This thread is mainly about how to get android working. I am trying to speed android up by partitioning the sdcard as fatsal mentioned. If it works there will be a HOWTO for that, too.
Until then i will continue to work the linux-kernel for X1-android until it is done (or i loose my X1, too )
This is pretty consize. I hope it sums up all the main points of fatsal thread on android
With zImage_kovsky_20100313.zip system always lock up during shutdown
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
No no no! Your doing it wrong!! D:<
gbajzelj said:
i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
Unfortunately, due to certain hardware limitations of the X2, boot time of the X1 kernel on the X2 can take a little longer. About 1.2 seconds after the sun explodes and extinguishes all life on Earth 4 billion years in the future, is a good estimate.
Sorry
vdelf, will you be committing regularly to gitorious? Or do you have a scratch repo for messing around with?
vdelf said:
also reserved for future updates
Click to expand...
Click to collapse
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
i had the bin/sh error too , first time.
when simply retrying -> it booted up to the "exploding X".
however, that screen froze on me.
i seem to get more progress though than with the material from the original threads.
the material from this topic has gotten me further than ever before. as i speak i'm booting a fresh one with the new kernel (from the start). it's upside down, but i hope this one works 'out of the box'.
persistence is paramount, as time passes the chance on reaching satisfaction approaches 1. how this satisfaction is achieved is up to you; may it be through running XPEROID, purchasing an android phone or simply giving up.
I managed to get it back to the "exploding X" screen (using the first file, not the kernel update).
It seems to be stuck in the X screen though, it's looping (and stalling a little) for 20 minutes now. Last time I soft-resetted the phone after about 10 minutes of X-screen, and it mangled my sd card (meaning I had start from scratch). There is no text (or error message for that matter), so I don't know what is going on.
Is anyone familiar with this?
EDIT:
I paused my attempts for now. Same result over and over. I'm not able to find anything on this in the original thread (or possibly when I read every single post I might find something), search reveals nothing to me.
gbajzelj said:
i have tried to run this android on X2. I run the haret. the BOOTING LINUX window fils the line al the way then there is no black and white running text like on X1. the start bar apeares on the bottom end of the screen. and nothing is responding.. i have waited more then 10 minutes but still nothing happens.
Click to expand...
Click to collapse
You have to use a version of haret that supports your phone. As X1 and X2 have not identical hardware (or do they?) someone has to code X2-support to haret. Until then it will not work.
In startup.txt there is this line
Code:
set mtype 2006
This is for kovsky X1. For X2 there has to be a different value, but dont ask me about that
dawen said:
i always get an error saying mounting /dev/block/mmcblk0p1 on /sdcard failed: invalid argument
failed
failed to mount the sd card, cannot continue
/bin/sh: cant access tty; job control turned off
anybody has any idea? i am using sandisk mobile ultra 8gb mirco sdhc
Click to expand...
Click to collapse
It seems that your sd-card has no partition. If you use linux, you can check this very easy. On windows, you can try to reformat the card.
You can also try another card.
Woudnt it be possbile/smarter to put the android on your xperia's internal memory (when you have 300+mb free?) or woudnt there be any diffrence in speed?
can you install apps from the market
or do you have to manually do it (pasting the apk to the sd)
?
I'm sure I have done something stupid and if I can't get this fixed it's not the end of the world. My moboot defaulted to CM7 until I used recovery to flash CM9 nightly. Since then it has defaulted to WebOS. CyanogenMod shows up as the second option in moboot. I have tried the following directions to change the default to CM9 with no luck;
Cyboot to change to "android" - Still defaults to WebOS
Internalz pro on webOS to change moboot.default to "CyanogenMod" (with no quotes, case sensitive, which matches the Ulmage.CyanogenMod). I did this in developer mode on WebOS and saved it- Still defaults to WebOS. I confirmed in root explorer that the moboot.default is changed to "CyanogenMod" no quotes.
Used Terminal in android (can't find the link but followed directions exactly, same idea, changing moboot.default)- Nothing
Wiped everything and flashed CalssicNerd, changed the moboot.default accordingly - No luck.
Wiped everything again, flashed CM9 nightly, again tried cyboot, internalz pro, terminal, root explorer, still no luck. The moboot.default file is definitely changed to "CyanogenMod" no quotes.
Any ideas???????
Wipe clean with webOS doctor and then clean install of CM9
Sent from my cm_tenderloin using Tapatalk 2
That is not the answer I wanted but I thought it was probably going to be necessary
One more noob question, once I have wiped and reinstalled CM9, using Titanium to "restore all apps and system data" shouldn't cause the problem again should it? I'm assuming titanium doesn't mess with the boot folder? Are there things in "system data" that could be causing the problem? I guess either way I will find out shortly!
Thanks
Hey Use adb shell then:
mount -o rw,remount /
mkdir /boot
mount /dev/block/mmcblk0p13 /boot
echo Cyanogenmod > /boot/moboot.default
Should work if it doesn't you'r going to have to clean install i think its mainly because you flashed CM9 over CM7 without Wiping the TouchPad.
No luck with ADB. when I run the mkdir /boot I get "mkdir failed for /boot, File exists"
After running the rest of the commands it makes the new moboot.default file but puts it on the SD card main directory, not in the boot folder overriding the current moboot.default. (which is already CyanogenMod anyway)
Anyway, I'm just going to wipe and do a clean install. Thanks for the suggestions.
Edit: Wiped everything, started from scratch with eyeballers unofficial nightly cm9. It was still going to WebOS so I checked and there was no moboot.default. Created one with root explorer and I'm good to go. Plus I love this rom!!
Thanks again to all the people that help noobs like myself.
Glad that you resolved your problem if u need any help just ask
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
ve6ay said:
I wish I'd caught this before you wiped everything. Try adding a blank enter at the end of the moboot.default file - it's what I found fixed the error for me.
The other thing you could've done was booted into WebOS, installed PreWare from your PC, and then installed CyBoot and modified all your boot settings that way - you could set it to default to android, set the timeout to less or more than the default 5 seconds, etc.
Click to expand...
Click to collapse
I think he clearly states that he tried that on his first post
Whoops. Now I see where he said he tried the Cyboot method. My bad. But the blank enter at the end, I'm not sure he said he did or not. And for some reason, it needs that blank CR/LF at the end of the line, else it sometimes (for some people) doesn't work.
It's all good, It was a good excuse to play around with new ROMs and learn some new stuff. Truth is when everything on the touchpad is running just how I want it, I get bored. I like tweaking it more than I like using it
If I ever run into the same problem, or find someone that does, I will pass on your advice of the blank enter. Thanks
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
Is it possible to do this on our touchpad using smackmeinstaller?
Most definitely possible. Currently using it right now. I encountered a few hiccups along the road to getting it there, but the process will remain the same.
First and most important, you'll want to make a nandroid backup so it'll be easy to get back into Android without losing anything. BE SURE to move this to a computer to be safe.
After that finishes, you'll want to work towards removing Android entirely. This can be done with a CMUninstall file found from the CM10 page. Should be run in a similar manner to what Installing Android looked like. This will remove moboot as well as android.
From this point, simply install Ubuntu from the instructions they give on the page. Here's a quick rundown of that. If I'm missing something, follow their word, not mine. Start by creating a sminstall folder and placing the Ubuntu file (larger file size) and the setup file in the folder on your Touchpad. Then set (depending on if you want the alpha kernal or the standard) the uImage file in your palm directory that you uninstalled android from. If all goes well, you should boot straight into webos not seeing the familiar moboot screen. This is ok.
At this point, you'll want to follow the standard instructions to install Android. Place the following files in your cminstall folder:
Rom, CWMrecovery, Moboot(latest is 0.3.8), and be sure to snag some Gapps if you for some reason need to start fresh. Install that using the normal instructions.
Finishing should bring you to moboot with a new option of kexec. This is a "moboot" for Linux options. Use the volume keys to select Ubuntu and press power and home buttons to start it. I HIGHLY recommend a Bluetooth keyboard and mouse for it.
TL;DR - Backup. Remove Android. Install Ubuntu per instructions. Install Android per Instructions. Restore. Profit.
I used this post as a guide in more detail. http://forum.xda-developers.com/showthread.php?p=41464020
Also, I would advise against running WebOs doctor after the linux installation, as you have to do some extra work in order to get the touchpad into working order.
Sent from my TriBooting HP Touchpad using xda app-developers app
In webOS, I used cyboot and selected an option to directly boot into CyanogenMod after restarting it. Now I can't figure out how to boot into webOS without running ACMEUninstaller. Any help?
nightfireblaze8 said:
In webOS, I used cyboot and selected an option to directly boot into CyanogenMod after restarting it. Now I can't figure out how to boot into webOS without running ACMEUninstaller. Any help?
Click to expand...
Click to collapse
Yes, using a file manager with root privileges open your boot folder, in there there is a file called moboot.default then edit the text to read webOS(note the OS are upper case. Save reboot into webOS and this time with cyboot when selecting Android make sure that you have a time delay of 5 seconds which should be the last option, save and exit. Reboot and you should see all boot options with whatever Android Rom you are using highlighted and it counting down from 5 till it boots the highlighted option.
Obviously you can change the delay to what ever you are comfortable with.
Thank you for the quick reply!
nightfireblaze8 said:
Thank you for the quick reply!
Click to expand...
Click to collapse
Your welcome, i Trust you have it sorted if not feel free to PM.
All the best and have fun.