Database Develop

Tablet Constantly Reboots

So I've come here as a last ditch effort
I've been trying to load CM9 onto my tablet for several days now and am having absolutely no luck. There are always two things that happen with it either it constantly reboots on the loading screen right after the splash screen or if I somehow manage to get past the loading screen, which has happened maybe a half dozen times it reboots after I hit one or two buttons.
Now as far as I know I've tried every single way of flashing the roms.
I've used ACMEInstaller2
I've used ACMEUnInstaller, then ACMEInstaller2
I've used cwm and twrp to flash (I wipe data, cache and dalvik everytime)
I've flashed CM7 and then ACMEInstaller2 CM9 on top
I've flashed CM7 and cwm to flash to CM9
I've used the uImage cleaner in cwm then wiped data, cache, dalvik and reformatted data, cache, and system, reflashed and wiped cache/dalvik again and fixed permissions
I've tried multiple Roms including but not limited to Classicnerd, CM9 alpha 2, and CM9 nightly.
They all end up with the same issue
Note:I've also applied the various reboot fixes, and none of them seem to make a difference.
I can get CM7 to work on the tablet in the effect that it runs smoothly once it starts up but it does do the loading screen reboot quite often and the only way Ive found around that is to wipe the cache/dalvik every time I start up the tablet.
If anyone has any ideas of where I could go next with this it would be greatly appreciated, I'm pretty much at my wits end lol.
Edit: Oh I forgot to mention I've also WebOS doctored it.

What version of WEB OS doctor did you use? And have you tried formatting the SD card option in web os?

I used webos doctor 3.0.0
Also I was told not to format the sdcard, is it just the option in cwm or do i go about doing that another way.

In web os you have the option to format the memory card. But if you doctored with 3.0 you should be fine as it re partitions the device before formatting and flashing.

Hrm, well if I got the right WebOS doc any other ideas that might work?

Have you tried a full factory reset ? Using THIS THREAD, you can wipe everything back to complete nothingness, then try reinstalling. It could be something is wrong with your boot entries, partition table, or the like. I know you've tried to doctor it, but doing it this way ensures you start with a completely clean slate (to the point of deleting all of your partitions and starting fresh).
Back up anything you wanna keep, then try that - and re-download all of the necessary files again, just to be sure. It's what I would do.

Check that its charged.
My tp will reboot at the splash screen if charge is <70%. Only booting to webos whilst connected to charger, then leaving for a day will allow it to boot reliably to cm9.
Even on the latest nightly, I have big charging issues with cm9
Sent from my cm_tenderloin using xda premium

Well I did the factory reset as you suggested and then doctored it from 3.0.0 to 3.0.4 then tried CM9 again-No Change. So I decided to flash CM7, which seems to run fairly stable it I think I've only seem it reset once and as for the rebooting after the splash screen it still does that but if you let it restart a couple times it eventually goes through. I downloaded a CPU overclocker and set the min to 384 then reflashed CM9 through ACME. It seemed to work for awhile, about half an hour, watched an episode on netflix then when I tried to open another app BAM reboot and now its back to either loading screen reboots or about 5 seconds worth of CM9 then reboot. This has got to be the most frustrating piece of equipment I've ever worked with.

That's really odd... Especially since it worked for a bit and then not. Is it getting overly warm ? That might be a sign of an overheating problem. Or you could just have a bad device. They do exist. Does it do the reboots from within WebOS as well ? Or just when you're on Android ?

No its never rebooted in webos. And it doesnt feel like it was getting hot, when I was checking the CPU stuff it was running at around 27 degrees celcius I believe I'm not sure whether thats overly hot or not.
Update: I ran the tablet again and it seemed to work pretty stable for about 10 mins then random restart I had the cpu temp up on the main screen though and it read 22 Celsius before it rebooted.

Restart Problem
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx

kenbhaji said:
I have had touchpad for 8 months after which the screen did not respond to the touch. So I sent it for RMA and received another unit. I installed the aplha2 but it kept on restarting as soon as I boot into the Android. I tried different ROMS's as well but same problem.
I downgraded the webos with webos doctor 3.0.0 but the same. No matter how I use the touchpad in webos it does not reboot.
Any help will be much appreciated.
Thanx
Click to expand...
Click to collapse
WebOS doctor back up to 3.0.5
AcmeInstaller2 to install one of the latest nightlies (alpha 2 is quite outdated which a search would have revealed)
If you still have issues you may be one of the unlucky few whose Touchpad hardware just won't tolerate Android to which there is no fix
Sent from my cm_tenderloin using Tapatalk 2

Replacement?
Thanx for replying. Is there any way that I can get it replaced since it is under the warranty of course I wouldn't say that it reboots in Android but can I make some excuse to get a replacement which may turn out to be good device?

[Q] HP Touchpad no longer booting.

A week ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?

ss0198 said:
A weekhttp://goo.im/devs/jcsullins/cmtouchpad/testing ago I installed TWRP on my Hp Touchpad, via the GooManager App.
After I rebooted into TWRP it showed a error message. I cant remember what it said. First I just let it broken, but then I wanted to update SlickleROM from Version 1 to 1.1. But i couldnt use the Recovery System, because it didnt work.
So I tried to install the Clockworkmod Recovery and the new ROM with ACMEInstaller2 and ACMEInstaller3, but ACMEInstaller3 did nothing, it just showed the HP logo. ACMEInstaller2 showed a Error Message, that /boot is out of space. So i decided to reset my Touchpad.
First I used ACMEUninstaller to uninstall Android. Then i used WebosDoctor to remove all data, but it said it couldn't reset my phone after a few minutes. My Touchpad could'nt boot. It just shutdown everytime it was booting. I stopped the endless rebooting with holding Power Button and Pressing Home Button 10 Times. After that I tried to doctor serval times with older versions and tried to find out what was happening. But then the battery was too low. WebosDoctor could charge it and in the outlet it just charged until it was booting again, so i could charge enough to doctor the device. Now I have a not booting Touchpad with a too low battery to doctor.
I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work
Does anyone know what I can try to do?
Click to expand...
Click to collapse
Try leaving the tp charging, at least overnight, till it's 100% charged. Then try the guide again. If you're having trouble with novaterm, there's a good work around on page 12.
If you're having trouble with the doctor, either the 8% or the 12%, do a search for either. Don't worry, there's a workaround. Also search the webos nation forum, you'll find answers there also.
Good luck.
Edit : use cwm. Myself and several others here have had problems with TWRP.
Here's the link for cwm : http://goo.im/devs/jcsullins/cmtouchpad/recovery
Use the 12/15 one.

AW: [Q] HP Touchpad no longer booting.
I already that, but it only charges until it tries to boot.

Are you using the cable that came with the TP?

AW: [Q] HP Touchpad no longer booting.
Yes.

AW: [Q] HP Touchpad no longer booting.
The problem is, that it tries to boot, but it can't boot.

Have you tried to power it down whilst still plugged in ?

AW: [Q] HP Touchpad no longer booting.
What do you mean with:
sstar said:
Have you tried to power it down whilst still plugged in ?
Click to expand...
Click to collapse

What I mean is you have your TP charging and it automatically boots when it has sufficient charge, while leaving still connected to the charger have /can you turn it off but leave it connected?

AW: [Q] HP Touchpad no longer booting.
I will try it now.

AW: [Q] HP Touchpad no longer booting.
I just tried it, but it instantly reboots after turning it off.

It's obviously stuck in some sort of loop, my final thought is to hold both power and volume to put it into recovery and leave it so that it hopefully continues to charge .
You said you had a problem with running chicle's suggestion with the restore your TP to factory condition, how far did you get ?

AW: [Q] HP Touchpad no longer booting.
I alreqdy tried to charge it in recovery mode, but the battery didn't charge either. I tried to reset it with serval versions of the webosdoctor, but as I said it didn't work. It just said it couln't reset the phone. In the console/log it crashed at charging. And it list connection.

When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?

sstar said:
When you say ' I already tried to restore it to factory condition with this guide. But the WebosDoctor didnt work "
Does that mean you were able to run all the instructions in command prompt and then failed with webos doctor 3.0.0 ?
Click to expand...
Click to collapse
Yes.

ss0198 said:
Yes.
Click to expand...
Click to collapse
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.

sstar said:
Well I'm at a loss ,if or when you can try the factory restore commands followed by webos Doctor 3.0.0 again. I had to do it twice with mine.
That's all i can think of. Good luck.
Click to expand...
Click to collapse
I already did it twice

Now I finally got it working. I just charged it in Recovery Mode for a long time. Then I just used Webosdoctor and now it works!
Sent from my ss_tenderloin using xda app-developers app

Cyanogen Mod Face After Mooboot, Then Black Screen Hp touchpad Cm 10.2

So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.

rootedbuddha said:
So being the airhead I am I let my hp touchpad run out of battery. I charged it and when there was enough juice for it to come on(witch it does automatically) then it went to mooboot, a blue cyanogen mod robot face came on, and after a couple of seconds the screen just goes black, the screens on but black. I let it sit on the charger for a while and then it rebooted itself and did the same thing again. It has not restarted its self since then so I do not think it is a boot loop. anyways I let it boot up in webos so it could charge up to 100% in peace hoping that would solve it, but it did not. So basically webos runs, clockworkmod recovery runs(idk how cwm got on I like twrp better) and I can boot it into the webos recovery(big ass usb symbol). It was running the latest stable cm 10.2 I believe. I actually would perfer to run cm 10.1 because it has bluetooth and is compatible with minecraft pe. If you have any suggestions I would be very graitful. Also if we can avoid phoenix suite that would be preferable because I have a windows 8 laptop that is not very friendly towards that program, if I have to use it, thats fine.
Click to expand...
Click to collapse
Get the most recent version of the TWRP zip and put it into the /cminstall folder in WebOS. If you don't have the latest version of moboot (0.3.8) then put that zip in cminstall too. Run the latest version of ACMEInstaller using the appropriate script for your ROM version from your PC. That script should uninstall CWM and install TWRP. If you still have no joy then put the latest ROM and appropriate gapps zips into cminstall and run the script again. Clear the cache before rebooting into android.
Hope this helps.

I've had this issue before. All I did to solve it was to reflash the rom from recovery menu.
That should be all it needs. Its worth trying first before acme, etc etc.
Peace

Need advice on HD+

I rooted my HD+ over a year ago, but stopped using it due to its sluggish performance. Yesterday, I decided to install a new ROM to see if things would work better. I did back up the old ROM using CWM before I started plus I had two other backups including a backup of the native NOOK ROM (so I have three sets of backup files: Original NOOK system, and two different versions of CM (probably both 10, but I'm not sure). Anyway, I was unable to get GApps to install yesterday so I decided to just recovery a previously working ROM.
So I went into recovery and recovered back to the second of my three recoveries and got the Nook to reboot, and it was working. However, I had intended to go back to the native NOOK ROM, so I reran recovery to my original back up, and it failed to work. The Nook kept cycling back to recovery mode reboot option. So I ran recovery a third time, and tried to go back to the second of my three recoveries which worked a just a few hours before. I started the recovery last night and went to bed.
When I woke up this morning my Nook screen showed a fully charged battery logo. I unplugged the Nook from the power and it failed to boot. I tried holding down the power button to reset, holding the power and "N" button to reset, took out the SD card and tried both. Tried both with SD card in and out and Nook plugged into a Windows PC via USB. The screen remains black no matter what. The only response I get is that when I hit the power or "N" button when hooked up to a PC via USB, I get a message on my PC screen that says "USB device not recognized".
Any suggestions?

New development. I unplugged the Nook and tried once more to restart by briefly pressing the power button. A logo flashed on the screen showing an uncharged battery and a plug, which I assume is telling me I need to charge the Nook. However, it showed the battery as fully charged when I unplugged it this morning. Anyway, I plugged it back into my power cord and will see what happens. I'm really not too concerned, as this device, other than as a book reader, has never performed very well for me at all. Surfing the web was always very frustrating due to slow performance, stalling, etc. I'm just hoping to make it usable so I can give it away.

Update 2
Nook has been on charger 2.5 hours screen still stays black after pressing power button. Light is orange. is it possible the battery is bad after such a long time (about 2 years) on non-use?

Update 3 - and I would still like some advice. Please.
My Nook finally booted into recovery. It behaved as if the battery was not charged, and I'm not sure why as it was plugged in overnight.
I did a wipe & factory reset then reinstalled the last working ROM I have Files were installed in this order:
1. NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14).zip
2. cm-11-20150209-NIGHTLY-ovation.zip
3. pa_gapps-modular-micro-4.4.2-20140426a-signed.zip
I then rebooted and CM11 is installed and working again. Thank you leapinair and others.
When I used this version of CM11 before (back in 2015) it eventually became sluggish and stalled at lot. It was very frustrating to use.
Can someone direct me to a source of a better ROM and Gapps? I tried installing twrp and these files:
1. cm_ovation-ota-NMF26Q.161222.zip
2. open_gapps-arm-7.1-stock-20170212.zip
but it didn't work for me. I'm assuming I have the wrong files or combo of files.
I would really appreciate some advice and download links to better ROMs and Gapps. Thanks in advance for any useful advice.

Typical response for this forum

woneil said:
...
When I used this version of CM11 before (back in 2015) it eventually became sluggish and stalled at lot. It was very frustrating to use.
Can someone direct me to a source of a better ROM and Gapps? I tried installing twrp and these files:
1. cm_ovation-ota-NMF26Q.161222.zip
2. open_gapps-arm-7.1-stock-20170212.zip
but it didn't work for me. I'm assuming I have the wrong files or combo of files.
I would really appreciate some advice and download links to better ROMs and Gapps. Thanks in advance for any useful advice.
Click to expand...
Click to collapse
I'd suggest you try the LN14.1 build lnos_ovation-ota-NMF26Q.170104 ) available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918) and open_gapps-arm-7.1-pico-2017[mmdd] (available at http://opengapps.org/).
You should be able to use your current CWM recovery to flash twrp-3.0.1-0-ovation.zip (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778), then reboot into the newly flashed TWRP to perform "wipe /data & factory reset", and then flash the LM and GApps zip files.

digixmax said:
I'd suggest you try the LN14.1 build lnos_ovation-ota-NMF26Q.170104 ) available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3480156918) and open_gapps-arm-7.1-pico-2017[mmdd] (available at http://opengapps.org/).
You should be able to use your current CWM recovery to flash twrp-3.0.1-0-ovation.zip (available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778), then reboot into the newly flashed TWRP to perform "wipe /data & factory reset", and then flash the LM and GApps zip files.
Click to expand...
Click to collapse
Thanks very much for this advice. I will give it a try.

woneil said:
Thanks very much for this advice. I will give it a try.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/nook-hd/general/how-to-updating-nook-hd-internal-emmc-t3562818 for more info/pointers.

Does anyone have a link to the image, I click on ROM link and it's starting that the link is removed.
I have CM13 installed it runs very slow sometimes unresponsive, how does LN14.1 run incomparison

DeDonKJC said:
I have CM13 installed it runs very slow sometimes unresponsive, how does LN14.1 run in comparison
Click to expand...
Click to collapse
FWIW, I've been running LN14.1 builds for the last couple months and am fairly happy with it. See this thread for issues/quirks that have been reported.

Cannot boot past the USB icon

Hi, I need some help
I have a 32G touchpad and I let it totally discharge.
Now the unit does not boot past the big USB sign.
I do not mind losing the info on it, there wasn't anything really important.
I am using the Novacom Repair Android Tool.
I did the C/Boot and the Wipe All and it always came back to the USB sign.
Finally, I decided to try "Toolbox" (the one on the left) and finally I could get past the USB sign into Touchpad Toolbox.
I tried installing Android again, loaded the ROM, Gapp and Recovery
and when it had to reboot to finish installing android it went into the USB sign again.
Right now I executed again ToolBox.
Battery reads at 12% now
I want to think that the installation failed due to to the low battery, although it has been the whole time sitting on the wireless stand (Battery should have been around 3 to 4% when I tried the intall).
My plan right now is to let it charge to 100%, it seems to be rapid charging now that it is on the Touchpad Toolbox menu, instead of trickle charging.
If I try again to install, with a full charge, and It goes back to the USB sign, what can I do? Could it be a stuck volume up button and I would have to dissasemble (I'd rather not). What else could I try to recover the Touchpad?
Thanks

HI.
Still stuck.
Touchpad Toolbox reports 100% charge on the Touchpad.
1. Verified Android install files are on ttinstall subdirectory. Executed Install. Upon reboot, I was sent to the USB sign.
2. Applied ToolBox and regained the Toolbox on the Touchpad
3. Reflashed A6 Firmware. Upon reboot, I was sent back to USB sign
Do not know what else to try!

Still stuck
ran the Complete Data Reset of the Toolbox menu and ran WebosDoctor
WebosDoctor ran well without problem but upon boot it went back to the USB sign.
What can I do?

still stuck
Downloaded Flintsmant recovery
unzipped it
ran the novacom driver (linux system)
connected the touchpad to the usb port
issued "novacom boot mem://<uImage.Recovery"
The touchpad booted in recovery mode, installed the android and gapp that were in ttinstall and when it rebooted it went into the USB sign.
Could be a worn/stuck volume up button? I t seems to work normally when running tptoolbox.
Am I going to have to open up (gasp!) the touchpad?
Really need advice here