Database Develop

[Q] Any changes to the sdcard files will not take

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

Can't recognize in usb-mode

I have been running 4.0 for a long time, so i thought it was about time to get a newer version. so i ran the acmeuninstaller and was about to upload a new rom when i encountered a strange problem. i'm asked if i want to initialize the disk when i select mass storage mode. I have tried from webOS and from CWM, have also tried two usb cables, both my macbook pro and my windows 7 laptop. the original usb cable doesn't seem to be working anymore so i haven't got to try with that.
I didn't have any problems using recovery to transfer using nova com or preware. just the mass storage part that seem to be out of order.
any help is appreciated.

I'm starting to suspect something seriously wrong with the tablet.
i had ran a acmeuninstaller, but still booted into android. so i downloaded a rom and a file manager, and then a problem i've been having started to occur - processes dying etc. usually fixed by a reboot. which was one of the reasons i wanted to try something else.
so i took a reboot, and well - everything i had downloaded was gone. so i did the opposite thing, started deleting everything i've downloaded.
next reboot - everything was back in place.
More of this and i'll just use webOS which seem to work well. beside the usb connection that don't work.

I have never used any uninstaller to flash a new ROM. All I do is do a factory reset, clear cache, clear Dalvik cache then install new Rom and Gapps. I did this when I went from 10.1 to 10.2 to finally 11.0. Also, I have found that having the most current recovery installed will help also. For example...CWM version 6.0.4.7 is needed to install CM 11.0 because datamedia support is required to properly support emulated sdcard storage in 4.4. I also use CacheMate to regularly clear my caches.

This is a known occurrence with the touchpad.
DO NOT, if prompted, format the disc when connected in USB mode.
If you google your problem, there is a solution out there.
If you don't find it, let me knownand I'll try and find the link for you.
Your touchpad is not fubar !!
Peace

[Q] More questions about HP TPToolbox provided by jcsullins

Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?

anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?

[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.

sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)

Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??

[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp

Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.

shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5

mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?

mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65

Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!

Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse

shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.

issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
"

Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.

Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)

chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.

chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.

No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1

HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.

HP wont let me in after partial wipe.

I havent used my Touchpad for a year or so but took it on holiday to Portugal. I tried getting my GMAIL to work and it would not. So I did a partial wipe. Now it lets me say what country I am and what language then goes to wifi screen. It shows its picking up my wifi and lets me sign in then an error message comes up and it goes no further I understand Webos is not supported any more so was wondering how to load a new software package ( Android?) and start again. Help please?

Install Android and you're good
rose28454 said:
I havent used my Touchpad for a year or so but took it on holiday to Portugal. I tried getting my GMAIL to work and it would not. So I did a partial wipe. Now it lets me say what country I am and what language then goes to wifi screen. It shows its picking up my wifi and lets me sign in then an error message comes up and it goes no further I understand Webos is not supported any more so was wondering how to load a new software package ( Android?) and start again. Help please?
Click to expand...
Click to collapse
Android would be the way to go, WebOS is no longer supported. Jcsullins TPtoolbox with make it happen, have fun.:highfive:
[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way

RolandDeschain79 said:
Android would be the way to go, WebOS is no longer supported. Jcsullins TPtoolbox with make it happen, have fun.:highfive:
[ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way
Click to expand...
Click to collapse
I had a look and think I can do that. But couple questions. How can I get past the screens I mentioned in my post and secondly how can I download if I cant get on internet on the TP?

rose28454 said:
I had a look and think I can do that. But couple questions. How can I get past the screens I mentioned in my post and secondly how can I download if I cant get on internet on the TP?
Click to expand...
Click to collapse
You'll need to connect the touchpad to a PC prior to using the toolbox. It'll let the PC read the touchpad as a USB mass storage device and you can migrate your ROM, GAPPS, etc. onto the device and let the toolbox work its magic .

rfoster2009 said:
You'll need to connect the touchpad to a PC prior to using the toolbox. It'll let the PC read the touchpad as a USB mass storage device and you can migrate your ROM, GAPPS, etc. onto the device and let the toolbox work its magic .
Click to expand...
Click to collapse
I tried for 4 hours last night and eventually downloaded the Novacom but it would not work. Any ideas?

Instructions start with step #1
rose28454 said:
I tried for 4 hours last night and eventually downloaded the Novacom but it would not work. Any ideas?
Click to expand...
Click to collapse
It took you 4hrs to get to step 1? Further explanation is needed here, the steps are in an order for a reason.
If you're having issues getting the novacom drivers installed disable any antivirus or spyware protection that might be preventing the program from downloading the correct drivers for your system. Also make sure you have java installed and reboot after installing everything.
1)Getting started, Requirements and Preparation:
A)You must have the novacom software installed on your PC before running Jcsullins Touchpad Toolbox.
Download and run the Universal Novacom Installer 1.4.1. Click here:
Note:You will need to have Java installed to run the Universal installer. Click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS. Click here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.

Unable to mount Touchpad USB to PC after installing Android 4.4.4

I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.

1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.

Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay

1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:

Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J

1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next

Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?

Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.

1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...

That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!

1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...