Database Develop

[Q] Bootloader question and ROMs other than CM

When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!

WoodroweBones said:
When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!
Click to expand...
Click to collapse
1) yes you have to keep dual boot. A quick search would have given you this info. But when you install android it should default to boot Android in moboot... if you have several entries then I suggest you clean moboot or wipe android from the TouchPad altogether and start off with a cleean install (the stickies have plenty of instructions on how to do any of that
2) tenderloin is the codename so to speak for the TouchPad. You need to read up on the workings of moboot to understand the dual booting method and understand the entries you see when its booting and how to manipulate it (again information readily available on the forum)
3) yes you flashed correctly but your moboot /boot folder has conflicting entries. Most wifi issues have been fixed in all the most stable ROMs. Your issue may be related to conflicts from your install and/or having one of those.devices that is.just persistently going to have android wifi issues. When i say devices I mean yours in particular. Some of us depending on our device have never had issues no matter what ROM we used
Hope that helps...
Sent from my cm_tenderloin using Tapatalk 2

As abrasive as always...
Anyways, he does have a couple of points.
1) Yes, you do have to keep the dual-boot setup. You can change the default to whatever you want, or you can clean it up. There are some nice topics that explain it all throughout the General and Q&A and Dev forums (I don't have them handy). If you want to default to one of those, I can tell you now you need a little bit of familiarity with terminal (which is easiest), or you need to boot back into WebOS, install Preware, and then install CyBoot (which changes boot options).
2) He's right, Tenderloin is the name given to the Touchpad, like es209ra is the name for the Sony Ericsson Xperia X10. It's just what it's called.
3) Wifi issues are something that are hit-and-miss with a lot of people. One thing that seems to fix a lot of peoples' issues is switching your router to one of the lower channels (1-6) rather than the upper (6-13). There's also usually a lot less chatter on the lower 1-3 than closer to 6 (which is the default). Also, set your wireless to WPA2/Personal with AES (no TKIP), and disable WPS (Wireless Protected Setup). This will make your network more secure, and work better with your TP.
3) Another thing I've noticed is that if you switch your Wifi off and then back on, it can take upwards of a minute before it's re-enabled. Not sure why, but it is something to note.
Hope that helps you with a little less attitude than our resident... person... posted above.
Cheers.

Thank you ve6ay!
I was pretty positive Tenderloin was meant for touchpad but was thinking maybe its for actual android tablets only.
For some reason with Black Ice I just could never get the Wifi to enable at all. The latest AOKP nightly wouldnt even flash but I ended up getting AOKP Milestone 5 to flash and its working great! Have definitely experienced the other "normal" wifi issues of losing connectivity and having to switch to airplane mode and back, etc. so I am used to those already

Problem when initially installing Android on HP Touchpad

Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!

The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.

Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?

What ROM are you using? Also, which gapps did you install? Please be as specific as possible.

The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far

more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?

Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.

like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.

OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.

Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync

What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...

I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.

OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.

Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.

Former TouchPad user with questions about coming back

So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.

ampharos said:
So, I've heard about the recent Lollipop ROM for TouchPad, and this made me consider getting out my TouchPad. I'm curious though, if the guides and such account for having a comparatively ancient Android/recovery installed, from ICS - possibly even a beta. Do I just reflash those with little troubles, or something else? Do the modern ROMs co-exist with webOS? I might get a small nostalgia trip from seeing how much better webOS multitasks than Android.
Click to expand...
Click to collapse
First, modern Roms can coexist with webOS, however at this point I don't how how useful webOS is anymore. You may want to give TPToolbox a try and wipe webOS altogether. You can find great tutorials for this online.
Nonetheless, if you choose to keep webOS, you can flash a newer recovery from your old recovery, which will allow you to install lollipop or marshmallow. This will coincide with webOS. Although, if you have trouble installing a new recovery through the old recovery, then you can install a new recovery through TPToolbox, and from thereon flash a new rom.

As a former WebOS user I found that I stopped using my TP after HP shut down the servers in March. For a phone I jumped to BlackBerry and enjoy it all but for a few missing appps. My TP just sat in the charger. So this week I downloaded jstoolbox and installed Lollipop on it. So far so good an I am actually using it again.
It isn't WebOS but it is being used again.

Bringing an old Nook HD+ back to life

Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Bumping my original post - can someone help please? Cheers, Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Hey, one question, are you able to boot into TWRP? If so, you can flash any rom. Also, here is the link for installing stock rom again if you want. https://forum.xda-developers.com/nook-hd/development/stock-nook-hd-nook-hd-2-2-1-2018-update-t3840163 I personally haven't tested it though.

HELP, I think I may have finally killed my Tab S2 (T710)

Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.

We have same device, but still i can't upgrade my tab in any roms. And unable to install TWRP higher than 3.1 version.

davidzvi said:
Over the past couple years and up until last week I've been able to kill and revive my tablet. This time I'm really stuck.
Setup: I have TWRP running fine, not sure if it was 3.5.2_9 or 3.6.0. I've playing around with different ROMs for the past few weeks, seeing which one I wanted to use. Friday I reinstalled LineageOS 18.1, but I click the replace/keep up to date option which now guess replaced TWRP because it was no longer there when I booted in recovery.
I've tried reinstalling TWRP, CF autoroot, etc. But the closest I've gotten is TWRP coming up, then displaying errors quickly and the system rebooting. I know just enough to be dangerous, but not enough to know exactly what I'm suppose to do in what order to get the system back up (or which versions of the files I've downloaded I should actually be using.
Any help to get back to where I can run TWRP again would be helpful, I can probably take it from there. I can get the tablet in download mode, but that's about it.
Click to expand...
Click to collapse
Have you just tried flashing stock firmware, using odin?

I was trying the CF_autoroot (and other kernels(?)) and TWRP in odin.
Oddly over the weekend I left it plugged in for a day and and when I opened the cover it was in TWRP.
I was able to wipe, format, and load a ROM. But I think I might have broken the battery connection now, it doesn't seem to want to plug into the main board. So it doesn't want to do anything now. I'll probably play around with the connector a bit and see if I can sort that out.
But I'm not sure what @rufio85 issue might be and I would be the last person to advise anyone on this stuff.