Related
Hello, recently purchased a asus tf701t laptop/tablet hyrbid and the device itself is perfect. Powerful cpu, good storage and an insane 2k resolution for a 10' inch screen which I don't think has been done before.
However I absolutely hate android (no offense to android developers) and decided to try installing Linux Mint 17 which can be installed on any regular laptop easily. Essentially, I want to get rid of both android bootloader and the OS itself and replace that with Grub bootloader and Linux Mint 17 OS. But android is fighting me every step of the way trying to prevent me from doing just that I unlocked the bootloader so my warrenty is void now.
But beyond that I can't install linux iso because the android bootloader isn't registering the usb stick (with linux iso on it) so I can't launch the linux live iso at all. I tried using cdrom iso using disk to launch through usb and still doesn't come up in the bootloader options. I know its possible to use linux on these devices because I've seen people have done it before on the internet.
I am now at this point starting to consider android itself as malware as the very definition of the word, ....lets start with the fact that they locked the bootloader, prompting me to give ip address just to enable me to unlock the bootloader (malicious and very dodgy). No root access therefore, third party programs are required to enable root which further my belief that android os is more malware than it is a legitimate operating system. Lastly, either possibly no usb driver for bootloader or usb port is locked out by design at bootloader (either way, might explain why I can't use usb linux iso).
What I can't understand is, why google can lock down a device tighter than fort knox on a Asus brand device. This is like buying a brand new car and not being able to open your own car even though you purchased it. What google has done is borderline illegal and I'm abit astonished how they can get away with it...
Sorry for the rant guys I'm abit fustrated atm. Can anyone please help me? I really love linux mint and if its possible to format android and install linux mint on this device I would be eternally grateful
Update: I attempted to flash the device with the command: fastboot -i 0x0B05 flash recovery recovery.img which works...but when I reboot and push power and down volume into bootloader...and try to get into recovery...the screen looks like its about to load into it but then resumes boot of android.
I'm really puzzled by this. So cannot flash a custom recovery for some strange reason
Its not so simple I dont think. You might want to watch whats happening on this thread for now.
http://forum.xda-developers.com/transformer-tf701/general/native-linux-asus-tf701t-t2973119
I would think you would have to completely replace the bootloader with something like uboot maybe if you wanted to wipe the tablet. But I dont think anyone knows. Then you could end up with some permanent brick. There would be no recovery or fastboot option if you were somehow able to get some kind of boot loader on this thing. I have no idea.
Edit: Also there is no arm based Linux Mint afiak.
YayYouFixedIt said:
Its not so simple I dont think. You might want to watch whats happening on this thread for now.
I would think you would have to completely replace the bootloader with something like uboot maybe if you wanted to wipe the tablet. But I dont think anyone knows. Then you could end up with some permanent brick. There would be no recovery or fastboot option if you were somehow able to get some kind of boot loader on this thing. I have no idea.
Edit: Also there is no arm based Linux Mint afiak.
Click to expand...
Click to collapse
Thanks I appreciate the reply. I understand this won't be easy but I'm stubborn that way
Can you give me some advice on where I can start learning how to place a native linux os on the device? Would grub bootloader work with tf701t?
have you considered returning your tf701 and replacing it with the tf700 infinity? you can replace the OS with ubuntu.. theres much more support for that model than the tf701
tf701mega said:
have you considered returning your tf701 and replacing it with the tf700 infinity? you can replace the OS with ubuntu.. theres much more support for that model than the tf701
Click to expand...
Click to collapse
Out of curiosity, have you used the tf700t? it is good for development, but it could run pretty slow at times. It might of been because of the tegra 3 processor, because the tf300t also had this performance issue. I was barely able to type up documents on a CM Rom because the tablet would lag when typing out and would then force close and corrupt my document.
atleast for me, that was the reason why I went with this one rather than the tf700t. This is just my 2 cents about getting the tf700t. I would suggest trying it out before getting it.
Sent from my K00C using Tapatalk 2
Just how stubborn are you?
How much work do you want to put into this? There are two options, the easy route that you probably will consider imperfect, and the much more complicated route that I'm not certain will work. I'll do my best to explain both.
The method I use is to install a linux distro (in my case, ubuntu) inside a chroot. There are several apps on the android market to help you set this up. The one I used sets up an Xvnc server, so you can view your linux desktop by using an android VNC viewer -- but it's just connecting locally, not going over the network.
This works nicely out of the box, but it's slow, partly because it's using the VNC protocol and partly because there's no 2d hardware acceleration. I tinkered with my setup and installed XSDL, a native android X server with hardware acceleration. I had to modify the linux startup script to skip starting Xvnc and instead connect to XSDL (which is on :0.0 like a normal X server).
This works great and is fairly fast. For me, this is a good compromise between a full-fledged linux laptop and the convenience of android apps written specifically for a multitouch screen. I generally do most of my stuff in Android, but I can drop into my Ubuntu desktop whenever I need more power.
The really big downside is that it's hard to prevent Android's low-memory killer from sacrificing XSDL when I haven't used it for awhile. I've mucked about with various solutions involving oom_score_adj and such, and that helps, but android still ends up killing my X server sometimes.
So, that's the easy method. For the more complicated method, I'm just theorizing, and this stuff may not work. You're going to need to either already have somewhat deep linux knowledge or be willing to learn Here goes.
In this post, I described how I managed to boot my tf701t after the internal memory card died a horrible death. The important bit here is that I learned how to boot any initrd/kernel combination using fastboot, and how to roll that combination into a boot.img so that the tablet always boots it. This is what you'll need to do both for the installation and for future boots into your Linux install.
First off, choose your Linux distro. I don't think you'll be able to use Mint, since, as someone pointed out above, there's no ARM build of Mint. However, there is an ARM build of Debian and Mint has the "debian edition", so maybe there is an ARM version. It may be, though, that the Mint folks only built their special stuff (Cinnamon/mate/whatever) for x86 platforms. I'd recommend Ubuntu as a compromise since I know it runs on the tf701t.
For the initial installation, put the contents of the install ISO onto an SD card -- just copying your bootable USB drive over should work. Now for the tricky bit: you'll need to pull the kernel and initrd ("ramdisk", "initial ramdisk" -- usually initrd-<something>.gz) off of the usb drive and into a working directory on a Linux laptop or desktop (let's call it the "host"). You might get away with just fastbooting this kernel/ramdisk directly. Install the fastboot package for your distro (Ubuntu has one, anyway). Connect up your tablet, put it in fastboot mode (I think that's done by booting with volume up and down held) and do 'fastboot boot <your kernel> <your ramdisk>'.
This will boot the kernel and load up the initrd, which is a tiny little linux filesystem stored in memory. The kernel runs a program called init inside the ramdisk and init takes over and boots into the actual installer. The question in my mind is how it goes about finding the ISO contents. If it searches by filesystem UUID, and there's a good chance that it does, then it will find your the ISO contents on the SD card just fine and the installer will start up.
If not, well, things will get a lot more complicated. Normally what one would do in a case like this would be to pass kernel command-line arguments (you do this in the SYSLINUX bootloader for distros like Ubuntu) telling it where to find the installation media. We can't do that because fastboot doesn't let you pass command-line arguments. Instead, you'd need to extract the initrd on the Host machine, modify the init script in some way to tell it where to find the installation media (probably /dev/block/mmcblk1p1), and then repackage it. I went into somewhat shallow detail on how to do the extract/repackage parts of this, but this is where either prior linux knowledge or a willingness to do some research comes in. Hints: gunzip the initrd, then use the cpio tool to extract it.
Okay, so let's say that you get the installer booting. The next big question is whether it's going to work at all. In theory the graphics chip inside the tf701t is supported by linux, but in practice, maybe it's only supported by a kernel module that Samsung built. Maybe you'd need to substitute the stock kernel. The next question is whether X has a module that will work with the graphics chip. But maybe even if it doesn't you can use a text-mode installer. That would at least let you get a system installed that you could then hack on to try to get X running.
So, let's say you do get linux installed (probably onto the internal SD card, /dev/block/mmcblk0). Now you want to boot it. You'll need to look into the installed system and steal its kernel and ramdisk, and get them onto the Host machine. Or maybe you could just extract them from the debian packages, since I'm not sure how you'd get things off of that internal SD at this stage. As a hint, these may well NOT be the same kernel/initrd as in the installer.
Once you've got the kernel/ramdisk, you can try to boot into them with fastboot. If that works (big if), then you'll want to be able to boot them without fastboot. That's where the 'fastboot flash:raw' command comes in. It takes a kernel/ramdisk, builds an android boot.img out of them, and flashes it to the device. From then on, the device will boot that kernel and ramdisk by default.
So, in theory this could work. The biggest potential stumbling block is whether X is going to natively support the graphics chip. If it doesn't, you may be stuck using the basic framebuffer driver, or maybe that won't even work at all. ...or you could just settle for the chroot method and be done with it
Good luck. I'm very interested to hear whether this works. I'm probably not going to try it myself since I like Android enough that I want to keep it around. I also can't walk you through this in finer detail because of external limits on my time, but I'd be happy to answer theoretical questions and specific technical questions, so long as you're willing to do the legwork of reading manpages and such I hope this works out for you!
Oh, one thing just occurred to me: skip the part in the installer about installing grub. It's not going to work on this device and may cause problems. You'll take care of the bootloader part yourself with the fastboot flash:raw command.
Oh, I see there's already some decent progress in this thread. Also it looks like I totally missed the -c option in fastboot that lets you pass kernel command-line arguments... that'll definitely be a time-saver. Given what I see over in that thread, it looks like we may actually get a reasonable native linux on our TF701t. Not sure how far the OP has gotten on things like mouse/keyboard input, though.
I have to say, I'm pretty excited! It'd be super cool to be able to dual-boot native linux and android on this tablet. Best of both worlds.
lexelby said:
How much work do you want to put into this? There are two options, the easy route that you probably will consider imperfect, and the much more complicated route that I'm not certain will work. I'll do my best to explain both.
The method I use is to install a linux distro (in my case, ubuntu) inside a chroot. There are several apps on the android market to help you set this up. The one I used sets up an Xvnc server, so you can view your linux desktop by using an android VNC viewer -- but it's just connecting locally, not going over the network.
This works nicely out of the box, but it's slow, partly because it's using the VNC protocol and partly because there's no 2d hardware acceleration. I tinkered with my setup and installed XSDL, a native android X server with hardware acceleration. I had to modify the linux startup script to skip starting Xvnc and instead connect to XSDL (which is on :0.0 like a normal X server).
This works great and is fairly fast. For me, this is a good compromise between a full-fledged linux laptop and the convenience of android apps written specifically for a multitouch screen. I generally do most of my stuff in Android, but I can drop into my Ubuntu desktop whenever I need more power.
The really big downside is that it's hard to prevent Android's low-memory killer from sacrificing XSDL when I haven't used it for awhile. I've mucked about with various solutions involving oom_score_adj and such, and that helps, but android still ends up killing my X server sometimes.
So, that's the easy method. For the more complicated method, I'm just theorizing, and this stuff may not work. You're going to need to either already have somewhat deep linux knowledge or be willing to learn Here goes.
In this post, I described how I managed to boot my tf701t after the internal memory card died a horrible death. The important bit here is that I learned how to boot any initrd/kernel combination using fastboot, and how to roll that combination into a boot.img so that the tablet always boots it. This is what you'll need to do both for the installation and for future boots into your Linux install.
First off, choose your Linux distro. I don't think you'll be able to use Mint, since, as someone pointed out above, there's no ARM build of Mint. However, there is an ARM build of Debian and Mint has the "debian edition", so maybe there is an ARM version. It may be, though, that the Mint folks only built their special stuff (Cinnamon/mate/whatever) for x86 platforms. I'd recommend Ubuntu as a compromise since I know it runs on the tf701t.
For the initial installation, put the contents of the install ISO onto an SD card -- just copying your bootable USB drive over should work. Now for the tricky bit: you'll need to pull the kernel and initrd ("ramdisk", "initial ramdisk" -- usually initrd-<something>.gz) off of the usb drive and into a working directory on a Linux laptop or desktop (let's call it the "host"). You might get away with just fastbooting this kernel/ramdisk directly. Install the fastboot package for your distro (Ubuntu has one, anyway). Connect up your tablet, put it in fastboot mode (I think that's done by booting with volume up and down held) and do 'fastboot boot <your kernel> <your ramdisk>'.
This will boot the kernel and load up the initrd, which is a tiny little linux filesystem stored in memory. The kernel runs a program called init inside the ramdisk and init takes over and boots into the actual installer. The question in my mind is how it goes about finding the ISO contents. If it searches by filesystem UUID, and there's a good chance that it does, then it will find your the ISO contents on the SD card just fine and the installer will start up.
If not, well, things will get a lot more complicated. Normally what one would do in a case like this would be to pass kernel command-line arguments (you do this in the SYSLINUX bootloader for distros like Ubuntu) telling it where to find the installation media. We can't do that because fastboot doesn't let you pass command-line arguments. Instead, you'd need to extract the initrd on the Host machine, modify the init script in some way to tell it where to find the installation media (probably /dev/block/mmcblk1p1), and then repackage it. I went into somewhat shallow detail on how to do the extract/repackage parts of this, but this is where either prior linux knowledge or a willingness to do some research comes in. Hints: gunzip the initrd, then use the cpio tool to extract it.
Okay, so let's say that you get the installer booting. The next big question is whether it's going to work at all. In theory the graphics chip inside the tf701t is supported by linux, but in practice, maybe it's only supported by a kernel module that Samsung built. Maybe you'd need to substitute the stock kernel. The next question is whether X has a module that will work with the graphics chip. But maybe even if it doesn't you can use a text-mode installer. That would at least let you get a system installed that you could then hack on to try to get X running.
So, let's say you do get linux installed (probably onto the internal SD card, /dev/block/mmcblk0). Now you want to boot it. You'll need to look into the installed system and steal its kernel and ramdisk, and get them onto the Host machine. Or maybe you could just extract them from the debian packages, since I'm not sure how you'd get things off of that internal SD at this stage. As a hint, these may well NOT be the same kernel/initrd as in the installer.
Once you've got the kernel/ramdisk, you can try to boot into them with fastboot. If that works (big if), then you'll want to be able to boot them without fastboot. That's where the 'fastboot flash:raw' command comes in. It takes a kernel/ramdisk, builds an android boot.img out of them, and flashes it to the device. From then on, the device will boot that kernel and ramdisk by default.
So, in theory this could work. The biggest potential stumbling block is whether X is going to natively support the graphics chip. If it doesn't, you may be stuck using the basic framebuffer driver, or maybe that won't even work at all. ...or you could just settle for the chroot method and be done with it
Good luck. I'm very interested to hear whether this works. I'm probably not going to try it myself since I like Android enough that I want to keep it around. I also can't walk you through this in finer detail because of external limits on my time, but I'd be happy to answer theoretical questions and specific technical questions, so long as you're willing to do the legwork of reading manpages and such I hope this works out for you!
Oh, one thing just occurred to me: skip the part in the installer about installing grub. It's not going to work on this device and may cause problems. You'll take care of the bootloader part yourself with the fastboot flash:raw command.
Click to expand...
Click to collapse
Very stubborn
Sorry I didn't respond sooner as I was away with family for Christmas.
Thank you for the guide, it was extremely helpful. I am still working on getting the device ready so I'll update as I progress.
Thanks again
Just a general remark:
The new Win10 update from microsoft wich is rolling out as of today solves a lot of issues on the x98 tablets.
For example networking issues on mobile plans are solved, battery indicator fixed, no more flashing of notification shade, overall response much faster. And that's just at first glance.
This looks pretty cool!
Sent from my LG-H815 using XDA Premium HD app
Hi !
If you could tell me how to upgrade to new build 586 ? I want to upgrade from build 240 to build 586 . That always freeze on 68%
.
I do not how to upgrade it
It just upgraded with windows update on both my teclast x98 tablets, don't know how to fix your problem, sorry...
Sent from my LG-H815 using XDA Premium HD app
try running the update without the sd card installd
gbaz1 said:
try running the update without the sd card installd
Click to expand...
Click to collapse
Thanks ! it is workable when remove SD card . they could upgrade to 586 successful .
What about the orientation problem with the new update!
Orientation is all messed up again and the reg file from the drivers pack does not work any more!
No problems on both x98s. Came from original bing 8.1, upgraded to 10 and now to the new build without issues. C5j6 and c8j6.
On c8j6 cameras not working
3g, wifi, screen rotation, gps all ok
on c5j6 all is working: camera, gps, 3g, wifi, screen rotation, sd card etc.
Sent from my LG-H815 using XDA Premium HD app
I'm having the same issue. Had to lock the screen into the correct position. Have not found a solution. I think I will need to mess around with the registry to fix it.
I tried the update twice on my dual with no success. I had removed the SD as I'd been warned about it : the first time it shut down, maybe because the battery was low (despite of the power supply being plugged). When I rebooted it said I needed 14Gb to start the update, so I plugged a OTG USB Key and gave its path. Then it started and downloaded the update again, and failed (I don't know when). Now I'm confused about how to do this update.
dafunky said:
I tried the update twice on my dual with no success. I had removed the SD as I'd been warned about it : the first time it shut down, maybe because the battery was low (despite of the power supply being plugged). When I rebooted it said I needed 14Gb to start the update, so I plugged a OTG USB Key and gave its path. Then it started and downloaded the update again, and failed (I don't know when). Now I'm confused about how to do this update.
Click to expand...
Click to collapse
You need the SD and USB drives removed for it to update. Delete stuff to make room or go the reinstall route.
I still have issues with touch screen rotation after the update...
Thank you for your help. My windows partition is almost mint, I just installed the Window 10 pro from this forum, office, Kodi. There is 3gb of free space, afaik I can't do much better. I'll check wether there is to clean files from windows update, and I'll try again without SD/USB
Did you delete the previous Windows installs?
Old versions of Windows will be left on the drive in case you want to revert back and they take up a lot of space.
You can do drive clean and use the advanced or admin only option and check how much is in the old windows file.
I don't have my tablet with me or I could give you the exact path
With a 32 Gb partition you should have close to 16 Gb free... at least... I'm sporting windows 10 November update...
It failed again and again, I give up.
Questions to those who succeeded :
- how much free space did you have?
- did you have Windows 10 normal or PRO?
dafunky said:
It failed again and again, I give up.
Questions to those who succeeded :
- how much free space did you have?
- did you have Windows 10 normal or PRO?
Click to expand...
Click to collapse
my teclast is original partitioned and the windows partition is 37.5GB in size.
at the moment I have over 16GB free space, this is with libreoffice, adobe première elements, utorrent and several small tools installed. all these were also installed before the november update.
I am using windows 10 home as official upgrade from 8.1bing
Hi,
I'm wondering: On Win10 (pre1511) my x98 (c5j6) always tries to install a new graphics driver - but always fails. ALso, I can manually start this process in the device manager, same result.
What else can I do?
Best wishes
n14
dafunky said:
It failed again and again, I give up.
Questions to those who succeeded :
- how much free space did you have?
- did you have Windows 10 normal or PRO?
Click to expand...
Click to collapse
Hey, I succeeded to get it to work on air II. I had to do the following:
- change the battery mode to never turn screen / power off when plugged
- cleaned c: drive - deleted system files (including windows updates to force redownload)
- ran the update and this time it worked
The other alternative is download the Microsoft Media Creation tool, create a new USB installation media (include updates), and then do a "clean" install (reinstall windows 10). This will install windows 10 with the 1151 build.
It's worth it as it now allows us to use the SD card to install apps!
Thank you for your feedback.
As I can't get more free space, I'll wait the next W10 big update. At this time, I'll format all partitions to get more space for windows, by reducing the android one.
I tried the media creation tool but not chosing a fresh install, only update. Failed.
djmvt said:
On c8j6 cameras not working
3g, wifi, screen rotation, gps all ok
Click to expand...
Click to collapse
same here on a C9J8 ?
would love to have a working camera for video calls. Any way to fix that?
oh, and the CPU seems limited to 1.6GHz?
Last night I installed an update for Windows 10 version 1511 (KB3124200) and everthing seems to be smoother. The only problem I have is that the battery stays at 7% for a long time. Tried to completely discharge it but doesn't work...
Hi there,
I have a nearly three year old Lumia 1320 that I have as my daily driver, and have been using the Windows 10 DP since early days. Recently, the W10 release it had was the one that stuffed up SD card storage (and was getting random reboots) so I decided to go back to 8.1 and updated it to the Update 2 release.
So far so good. However, the newest W10 release came out so I decided to give it another go (especially as SD card issue resolved) so ran the appropriate software, it downloaded, and applied the image, then it failed. It said to try again, so I did and then started saying things like I didn't have enough storage. The Storage app wouldn't load, nor would Store, Phone, Messages etc. so tried the recovery tool to reflash it back to stock 8.1
This tool failed during the process and said it couldn't flash the device.
Tried various reset techniques and they all failed to get a good result. The symptom was to get the red NOKIA screen for a split second then it loaded the OS.
Now I'm getting concerned and bring out the big guns! Read the XDA tutorial on Windows Phone flashing, downloaded the tools, installed the unsigned driver, downloaded the appropriate image for my phone and went to flash.
Got to 2% and failed:
Sorry! Your device could not be flashed with the image you selected.
Please correct the following error and try again:
Failed to flash with device error { 0xd, 0x0, 0x0, 0x2, 0x0, 0x0 } : Status: 0x80000008
I looked up this 0xd code on the MS site and the error is this:
0xD While applying the image to disk, a block write operation failed.
So now to the ultimate question - does this mean my phone has a hardware error that prevents flashing, or can anyone suggest a workaround to get past this?
The model is RM-994 - the image is 059V5K2 (Australia/NZ Vodafone)
PC I am flashing with is a Core i7 2600, 8GB, Windows 10 Pro x64 with latest November update.
Any advice much appreciated.
Darren
No one?
Really no replies? Anyone on here know more low-level details or tests I can perform?
Even if someone confirms my suspicions that there is a hardware fault that simply can't be overcome, I can move on.
The phone is still running, alarms work, lock screen works (even updates Bing photo), but no Store, Storage Sense, Messages, plus many others and if I delete apps listed as unavailable, or even current apps, such as Tweetium, they disappear and return after a reboot of the device.
I have even tried remote wipe from the web and the device reboots and goes straight back to where it was.
Regards
Darren
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...
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
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)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
jamesking420 said:
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
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)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
Click to expand...
Click to collapse
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
DoubleStuff said:
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
Click to expand...
Click to collapse
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
jamesking420 said:
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
Click to expand...
Click to collapse
I am curious to what install process you have used to install the Dirty Unicorn Pie? Please respond, its nice to see what install processes some users are using....like what speed of Universal swap settings did you install?, did you use ROM reducer?
In the meantime since you have Novacom and TPTB installed try this process to install maybe Nougat, Oreo or Pie ( with /swap ) or KitKat or Lollipop. Once you read the OP it will direct you to the key Android versions to install on HP_TOUCHPAD's page.
I currently use KitKat and I am fine with that.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
jamesking420 said:
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
You don't have to do a Complete Data Reset anymore with the TPToolbox if your going to run TPTB_WireAll_TWRP_02_win.bat or flash Automatic_Wipe_All_and_Create_Android_with_Swap_Partition, it almost seems like your combining three different methods of installs, because TPTB_WipeAll_TWRP_v02_win.bat actually flashes Automatic_Wipe_All_and_Create_Android_with_Swap_Partition in the background and that actually does a complete data reset and creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Only use TPToolbox to flash A6 firmware, or look at partition sizes.
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
How are you copying zips to your touchpad if your PC does not work? Once you
flashed Automatic_Wipe_All_and_Create_Android_with_Swap_Partition it should get you to a
TWRP Recovery install screen, and you can then flash your zips, no need to use TPToolbox as I said before. Essentially TPToolbox is an "old school" method now. And flashing from TWRP Recovery you don't need compatible zips, that is a bug of TP Toolbox that has not been fixed.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
I am curious, even if we point you to a set of such files, how are you going to copy them from a broken PC?, and see above for another way of doing this than from TPToolbox, if you can get into TWRP recovery and have zips on your Touchpad your all set.
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
Your PIE version above is the latest version, good. But the TWRP 2.8.3 version above is "old school" we are currently at this version FLINTMAN-TWRP-3.2.1-0-03-15-2018, and like I said above the "Wipe All" methods automatically install this latest TWRP version, so no need to flash an "old school" TWRP's afterwords.
Click to expand...
Click to collapse
I made comments above in blue. Here is my summary.
Because your PC broke, like you said "blue screen of death, RAM corruption". This is the very reason that @HP_TOUCHPAD is thinking "outside the box" trying to create an environment that users will not be dependent on a PC anymore. He is in the process of creating this environment, but lets give him time. For by his own admission he is just a regular user, he is learning, experimenting, creating and testing. He is also documenting his findings for all of us to read, learn and apply. So let us do our due diligence and do the best we can.
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
jamesking420 said:
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
Click to expand...
Click to collapse
This appears to be working to install a KK ROM so I will see if it comes up and I can then run the various flashes.
PS - yes - I did think that running Complete Data Reset and the "TPTB_WipeAll_TWRP_v02_win" was probably unecessary but I'd already run Complete Data Reset before I realised that it probably was overkill. Since this process worked I decided to do it again on the second touchpad, but the Windows PC died before I got the chance. But I had already run the process to load TPToolbox on to the tablet. So I'm now flashing TWRP v2.8.3.0 (data media), a KK ROM, and some KK compatible GApps using TPToolbox.
I hope that after that I can use the recovery I have loaded to install a new ROM, Rom Reducer, SU, Optimiser, GApps, and a more recent Recovery.
jamesking420 said:
snip...
My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
...snip
Click to expand...
Click to collapse
I learn something new everyday, I just googled Raspberry Pi and its some sort of tiny, dual-display, desktop computer. At first I thought it was some sort of "Rogue ROM", I guess we can always learn something new everyday, like last month I learned to play Run Race 3d and I am not even a gamer.
And yesterday I wrote a program in a UNIX language called "AWK"
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
As per your comment recovery ( again?! ), only flash recovery if you want a different version than what the Wipe all zip flashes ( currently flashes TWRP 3.2.1 ), lets say in the future nobody is updating the Wipe all zip, and it still flashes TWRP 3.2.1, but you see a newer version of TWRP 4.1 compatible with the touchpad, then you can flash that at the tail end, or if your fond of an older version like TWPR 2.8, same thing.
Thanks - yes - I want sure if Wipe all Zip was flashing or just into TWRP so I flashed it again just to be on the safe side. Because it was called wioe ask I thought maybe it wasn't actually flashing anything new, just wiping and booting.
Anyway, thanks for your help it was very useful.
jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
The HP Touchpad Novacom Repair Android guide:
Click HERE for the Guide and File
A live Linux CD, just boot it from any PC, no installation is need it and have full control of the Tablet for ever !
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
jamesking420 said:
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
That is very unfortunate, but there is nothing to worry. The Tablets can be found for $10 anywhere and you maybe surprise to find in a dumpster somewhere.
But it can be revive to its full working conditions and all the files are posted on here, it only takes a click and is done!