Related
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?
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
Like an idiot i thought it would be a good idea to format my system. Well, now no OS is detected and backups gone. I still have access to TWRP and files are still on my touchpad (weird?), but when i go to flash a rom, it starts to flash, then goes blank, then reboots into TWRP. I cannot get an OS to install. Also, i've tried to boot into WebOS and it just stays at the glowing HP logo.
I was going to try Acmeinstaller3, but every single link in the known universe seems to be down. I have no clue how to restore my system. Ive also never used ADB either. Please help.
Most links point to goo.im which is being rebuilt at this time. Try this one //d-h.st/eFr
Well regardless if goo is being rebuilt...how would I exactly go about getting an OS back?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
That link was for Acmeinstaller3
does anyone have a valid link for the acme uninstaller
How about this one http://www.mediafire.com/?cmmw89di1q7bsps
I webOS doctored it...got webOS functioning and booting. However, I've tried countless times to get Android back on and it keeps erroring and says no OS found. Btw, I have a cm rom file loaded on the TP and im using the ADB method to push the stuff. Nothing works. Any other ideas? Ive since purchased a note 10.1, so its not critical...But I would like to get Android back on it.
Sent from my GT-N8013 using Tapatalk 4
Anyone?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Hi!
Device Info:
I have a rooted Kindle Fire HD 7" running CM11 with TWRP 2.7 running as a recovery. I have had the tablet for approximately a year and a half, so hardware issues from age wouldn't be overly unexpected, but not necessarily expected either.
Background Knowledge:
(Note: The following has happened before in CM10.2, but disappeared upon updating to CM11)
One week ago...
-Fully functioning tablet running CM11 with TWRP 2.7 recovery set up.
Four days ago...
-Device begins to randomly shut down about once an hour
-Later in the day it begins to shut down soon after I reboot it (as soon as 5 minutes)
Two days ago...
-Death
-Not really, but the device shut down a couple seconds after fully turning back on
My Response:
My first discovery upon looking into this problem was that fastboot was fully functioning and seemed to be unaffected by the shutdowns (I assume they were caused by maxed out RAM). I attempted to boot into recovery, only to find that it was unavailable, and booted into system instead. I then decided to flash TWRP again. I made the stupid mistake of deciding to use a brick-fix tool instead of just doing it myself. Unfortunately, I just opened the first file that looked right in my Android directory, which happened to be a tool designed for Kindle Fire HD 1st gen. I am not entirely sure what happened, but I assume it wiped everything it could get its hands on and put in an incorrect replacement.
The Actual Issue:
The kindle is now throwing a fit. Now,when I turn it on, it launches the stand Kindle Fire logo, shifts to the Fastboot logo, then turns off.. or at least the screen does. When I press the power button after this, nothing happens. I must hard shutdown in order to even activate the pathetic turn on and fade action. Next, I plugged it into the computer, planning to fall back on my amateur knowledge of fastboot, only to find that the fastboot logo means nothing (probably). When I plug the device into the computer, I head the plugged in chime, then exactly 3 seconds later, the disconnect chime. This is the only indication I have that anything is happening, as the screen is off. The fastboot logo either means nothing, or the three seconds is not long enough to establish a connection to the computer.
Help? Anyone?:
I apologize to come on here acting like a noob who panics the moment he feels discomfort and does no research of his own.
Before I posted I searched the best I could to find any issue similarish to my issue and come up with two, only one sounding similar at all:
http://forum.xda-developers.com/showthread.php?t=2729536 - Similar issue, but not really the same symptoms. The only real similarity is the device.
http://forum.xda-developers.com/showthread.php?t=2421487 - More similar, even kind of used my same description. The symptoms are not the same, the major problem is that I cannot establish fastboot connection. (And device is not the same)
Thanks for any help that can be offered!
I would save a "fastboot -i 0x1949 flash boot boot.img" and flash the boot.ing from the cm 11 zip, it should attempt to flash as soon as the kindle kicks into fastboot. If anything it might help fastboot from freaking out.
Sent from my LG-P769 using Tapatalk
Thanks, I'll try that. I'll update after I try it.
Update:
Thanks! That worked perfectly! It stops the device from fading, allowing me to flash a new ROM. To note to anyone else who might have this issue, the command will only send upon the initial boot. Any of the following connects/disconnects will not work.
Sent from my Nexus 5 using Tapatalk
Follow-Follow Up:
Flashing the boot img from CM11 works great at pausing the bootloop allowing me to communicate with fastboot. Unfortunately, upon flashing stock amazon system img and TWRP recovery, I am still unable to launch into either of them. Whenever the kindle reboots, the "extreme bootloop" begins again, forcing me to flash the boot img again.
Should I be trying to get a hold of the stock bootloader from Amazon? (And if so, would you have any suggestions as to where I can grab it? I have thus far been unable to find it)
Thanks for any help!
Sent from my Nexus 5 using Tapatalk
Its probably from the selinux xattribs left over on /data from cm 11, Amazon's kernel doesn't have selinux support and crashes/freaks out when it sees them. You would have to do a internal storage wipe to get rid of them if flashing back to amazon os.
Sent from my Amazon Tate using Tapatalk
Would erasing userdata/system effectively remove it?
(Sorry for my ignorance)
Sent from my Nexus 5 using Tapatalk
No need to wipe system, only user data hence why I said if twrp is still acessable to do a internal storage wipe, it wipes userdata.
Sent from my Amazon Tate using Tapatalk
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.