I was following these instructions http://forum.xda-developers.com/showthread.php?t=1305891
And under step 3 section where it says create a folder called cminstall, I was unclear if that was on the TP or on my PC. I created it on my pc. I follwed the rest of the steps and when I ran novacom my TP did it's install thing and then at the very end there was a message
"no cminstall dir found, nothing to install.
Power off when ready"
I guess cminstall was supposed to be on the TP. No I can't turn it off. I tried the power button, I tried the power and volume up button, and the center button and the up button, nothing.
Am I hosed? If I can't turn it off how do I web doctor it to get back to webOS?
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
justfor4 said:
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
Click to expand...
Click to collapse
Yeah I just found that button combo on the webos nation forum. Dammit I just made a useless help me thread.
Well, though that this its true, the issue is solved.
And this is thankfully a good thing...
Great
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
lvpre said:
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
VGSmatt said:
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
Click to expand...
Click to collapse
Why don't u test the xronified version? U will be happier
+1 happy user of xronified version
klear72 said:
Why don't u test the xronified version? U will be happier
Click to expand...
Click to collapse
What makes xron better? After only one day, I like cm way more then webos!
Leoisright
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
Too many..or only...Leoisright !!! I've never known anyone who works much as he did and now with the help of MiSfit it will be even better
http://forum.xda-developers.com/showthread.php?t=1321335
What makes xron better?
Click to expand...
Click to collapse
It's faster+beter games support+some fixes like wi-fi. Check benchmarks of cm a3.5 and latest xronified version
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
the rom developer leo has been so enthusiastic and has been pushing updates one after the other in a regular basis and the rom is fast. you will see it when you try it . moreover few more devs have just joined the development which in my opinion is going to make the rom rock
ok before i got to into cm7, i made the jump to xron. You guys were right, its pretty fantastic.
You can't brick your TouchPad.
It's not possible.
Yeah, I may have panicked a little when all the button combos I knew weren't working. Then I found the correct button combo on the webos forum.
I'm having an issue. I was prompted to update to webOS 3.0.4. Long story short after and hour and a half with the black HP screen coming and going I decided something probably wasn't right. I downloaded webOS doctor and am trying to run it, but for the life of me I can't get my PC to see my TP. My PC keeps making the "USB connecting" sounds. I think the problem is that it's looping between the HP logo and total black screen.
F***ing HP and their ****ty software! Anyone have any ideas on what I can do? I've tried holding menu/power and it just keeps looping
Thanks in advance
edit: got it working, here's what I did thanks to webOS support:
Hold power and press center button 15 times. This turns device into a powered off state.
Hold power and volume up to enter USB mode
Download and run webOS doctor.
After about a total of 3 hours of thinking my TP was dead, I kind of have a new found love for it, lol
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
VGSmatt said:
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
Click to expand...
Click to collapse
Xron comes with Gapps but Leo replaced stock browser with Dolphin (which is better). There is a problem if random FCs but they are so much less then what I had in CM7...as Xron is also based on CM7...you will see few bugs...but overall it made my TP so useful..
i agree, this is so much better then before. i don't see dolphin in my app drawer, no matter, firefox is working fine.
yip, it is better and if you want some eye candy the SPB shell 3D is really cool
Related
First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)
Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.
To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.
I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.
Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state
I can't believe I'm the only one with this problem
lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?
I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.
unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.
Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.
Well, strange that only two or three of us noticed this strange problem.
Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...
I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.
I have CM7 on my TP and today I tried to use it and i couldn't press anything on the screen...The volume buttons changed the volume, the home button went home, the power button turned the screen on and off, and the clock was updating fine, but I couldn't press anything on the screen. From reading other threads, I tried the 20 sec home + power button and that restarted it and it's working now, but does anyone know what might have happened or if it may happen again in the future? It was on all day but it was sitting in the TouchStone...
It happens to most of us. Upgrade to CM9. No point using 7 still.
Sent from my Galaxy Nexus using Tapatalk
I've had this happen several times with CM9 too, especially when taking it off of the Touchstone. I'm not sure why it happens though.
I hadn't upgraded because I thought cm7 was more stable. If that's wrong, then I'll just upgrade to cm9. Also, is it possible to upgrade through Rom Manager?
--
Sent from my SGS2 Skyrocket using Tapatalk
Ferrari353 said:
I hadn't upgraded because I thought cm7 was more stable. If that's wrong, then I'll just upgrade to cm9. Also, is it possible to upgrade through Rom Manager?
--
Sent from my SGS2 Skyrocket using Tapatalk
Click to expand...
Click to collapse
I don't know. Suggest you look on the forum here for instructions or go to lilputing.com. They have a nice guide that explains everything.
Sent from my Galaxy Nexus using Tapatalk
Boy is he going to have a "wtf was I thinking" moment when he "finally" uses ICS on his touchpad for the first time,lol. ICS is so sweeet!
Ferrari353 said:
I have CM7 on my TP and today I tried to use it and i couldn't press anything on the screen...The volume buttons changed the volume, the home button went home, the power button turned the screen on and off, and the clock was updating fine, but I couldn't press anything on the screen. From reading other threads, I tried the 20 sec home + power button and that restarted it and it's working now, but does anyone know what might have happened or if it may happen again in the future? It was on all day but it was sitting in the TouchStone...
Click to expand...
Click to collapse
Definitely update to cm9 alpha 2. You'll notice a big improvement. Also, do a backup in cwm, it will come in handy if things don't go right. I remember reading something about the TouchStone and strange happenings (kind of like yours). I don't have one, so I didn't pay too much attention.
According to the thread, it says to use the AcmeInstaller (the same as the one for CM7) and then place CM9 on the SD card and update from CWM. So do I have to do the first step? Or do I just put the CM9 zip on the TP and install through CWM?
Just flash through CWM. Make sure to factory reset, wipe cache, wipe dalvik, then install. I think that's more wipes that you need, but it won't hurt.
I've been on the ICS ROMs since about 30 minutes after the first beta was posted. I have only had issues with the TouchStone on the ROMs that include bricked kernel. CM9 alpha 2 is by far the best today. I haven't had a single sleep death or freeze as you describe since I came to alpha 2. And none of the ICS ROMs have given me wifi woes like CM7 did.
Ditto the comment above. You will kick yourself for still using CM7 about 4 seconds after the get into ICS. Its freaking amazing, like having a whole new device.
Sent from my Galaxy S II (i777)
OMG OMG OMG!!! I nearly crapped my pants once it booted!! It's so epically awesome, there aren't even words to describe it!! I feel like a teenage girl talking about her iphail haha
It's a whole different Android, I love it!!
I went temporarily blind from the over-exposure to pure awesomeness. I feel your pain. Now the "how do I tri-boot webOS, CM7 and CM9?" question becomes even more trivial. Enjoy it, and prepare for more burns as you fully explore the awesomeness that is ICS on a tablet.
Sent from my Galaxy S II (i777)
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
hm. maybe i should have posted this somewhere else
x000x said:
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
Click to expand...
Click to collapse
Try changing from 'slide' to either 'pin' or 'none'. I think you can do that either in settings or in security. If you want to keep 'slide', I really don't know the answer to your problem.
Good luck.
x000x said:
kind of strange, i just installed cm9 on a new touchpad. everything seems to work like normal, except sometimes it will reboot itself when at the slide to unlock screen. it only seems to reboot then, and only when the backlight shuts off on the lock screen, and never when i am actually using android.
anyone got any ideas?
Click to expand...
Click to collapse
Probably redundant to ask, but which ROM and did you full wipe? It could also possibly be a battery problem; perhaps try another ROM and see if the same issue comes up.
it was just the cm9 nightly. there was nothing else on it but webOs. it was brand new, took it out the box, installed cm9 nightly, gapps. other than than i didnt do anything else to it. when at the slide to unlock, the screen shuts itself off after maybe 15 seconds and i'm assuming goes into a low power state. i'm kind of wondering if that low power 'trigger' is what is causing the reboot. its never happened to my other touchpad.. its really strange
Funny how these problems seem to come and go. Mine used to do the same thing when I first got it, but one day it just stopped having that problem.
Sent from my cm_tenderloin using xda premium
envy
-SGA- said:
Funny how these problems seem to come and go. Mine used to do the same thing when I first got it, but one day it just stopped having that problem.
Click to expand...
Click to collapse
Oh how I envy you. I uninstalled Android, formatted my touchpad, loaded it up in WebOS Doctor and security wiped everything. Then I reinstalled android and immediately cleared the caches and did a backup. From the backup, no matter what ROM I install (all the latest versions), I get random reboots all the F$&#-ing time. There doesn't seem to be anything I can do. Minimum and maximum CPU values don't alleviate the problem. It's frustrating beyond belief.
You should try deleting and remaking the media partition, where android is stored, through novaterm. Then webos doctor it, and reinstall android. No matter what ROM I used to have a scratchy sound from the speakers with the screen off until I did that, and now it has not happened since. It might help your RR problem. I know even acme uninstaller doesn't clean everything!
Sent from my aokp_tenderloin using xda premium
hm. i've never fiddled with novaterm before, is it related to novacom? would just running webos doctor work just as well? i'm thinking i'll just start from a clean slate. even use new cm9 downloads etc.
-SGA- said:
You should try deleting and remaking the media partition, where android is stored, through novaterm. Then webos doctor it, and reinstall android. No matter what ROM I used to have a scratchy sound from the speakers with the screen off until I did that, and now it has not happened since. It might help your RR problem. I know even acme uninstaller doesn't clean everything!
Sent from my aokp_tenderloin using xda premium
Click to expand...
Click to collapse
Try this link : http://forum.xda-developers.com/showthread.php?t=1426244
I hope it helps.
well i did a factory wipe and ran webos doctor. while at the webos screen to create an account it rebooted itself. i'm thinking it might be a hardware issue. this is not looking good.
So recently my touchpad turned off and not turn back on. I thought it was toast the first time this happened. Turns out, I just needed to hold the power button and home button at the same time for like 20 seconds and it came back to life. I'm pretty sure in this instance I had let the battery drain pretty far, yada yada yada.
Anyway, I got it charged back to 100% and everything seemed ok. But it would have random reboots a few times an hour. Also, when I turned the screen off, even at 100% battery, about 10% of the time, the thing would not turn back on unless I held down the power button and home button and rebooted the thing, a la sleep of death.
Per some advice I got from these forums, I redownloaded the ROM, tried different ROMs, Wiped everything multiple times before flashing, removed Android completely with ACME and wiped WebOS completely back to factory and wiped WebOS USB.I reinstalled Android and no matter what ROM I am on, I still get sleep of death just about every time I use it.
I have also tried bumping the minimum CPU speed and even installed a cool app call softlocker that seemed to help a little bit, bit this thing just keeps wigging out.
So, my question is, does anyone know what the hell I am doing wrong? Has anybody come across this before? Every search I do on this is just to get it back to life when you let the battery drain. This is happening to me at 100% battery.
I am about to sell the thing and chalk it up to hardware going bad unless anyone can help. I guess I could probably get some logs with logcat but I have never done it before and don't really know how to read them.
HELP FROM A FELLOW ANDROID TOUCHPADDER>
I have seen /helped with a similar problem, he was in exactly the same situation as you. What fixed for him was to acmeuninstaller android then webos doctor 3.00 followed 3.0.5 and finally reinstalling android.
Sent from my cm_tenderloin using Tapatalk 2
Thank you sir. Is 3.0 and 3.0.5 the webos doctor version or the webos version? I heard if you update webos to the latest ota, you can't install android anymore.... will look into this. thanks.
Flandro said:
Thank you sir. Is 3.0 and 3.0.5 the webos doctor version or the webos version? I heard if you update webos to the latest ota, you can't install android anymore.... will look into this. thanks.
Click to expand...
Click to collapse
It's webos doctor use that to give you 3.0.5 rather than ota it's safer anyway and yes you can put whatever you want on it.
Have fun.
sstar said:
I have seen /helped with a similar problem, he was in exactly the same situation as you. What fixed for him was to acmeuninstaller android then webos doctor 3.00 followed 3.0.5 and finally reinstalling android.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I just did all this and booting back up into android now. Will report back after some use.
Seemed to have done the trick. Thank you so much!
Sent from my cm_tenderloin using XDA Premium HD app
Flandro said:
Seemed to have done the trick. Thank you so much!
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Your are more than welcome I am so glad it has worked for you also. All the best.
Hello. I have a 5th gen kindle fire 7" tablet. I installed CM 12.1 last week. It was working great. Yesterday I decided to try a new theme out. I downloaded the CM12/12.1/13 Dark Side Theme, via the theme modifier. After installation I started having issues with my tablet. Now I can no longer change the theme, launch the Google Play store, go on the internet, or even make changes through the settings. Every time I try, it force closes. When I went to power down, the tablet would only reboot and start up again (yes, i tried rebooting too, hoping there was a command issue or something that had reboot and power off reversed). I tried using flashfire as well and it keeps force closing. It seems any route I take to try and remove the theme, i get booted back to homepage. I've tried factory reset to no avail. I tried using the Super Tool on rootjunky to try to get it back to stock or just do something but all of those options require I go through recovery mode which I can't get to unless I power down, which I can't. Please help.
Did you ever figure this out? This just happened to me.
Shawnshine94 said:
Did you ever figure this out? This just happened to me.
Click to expand...
Click to collapse
Nope. I even emailed the app developer. No response. If I find something out I'll post it on here.
Kenn210 said:
Nope. I even emailed the app developer. No response. If I find something out I'll post it on here.
Click to expand...
Click to collapse
Ok, I finally figured this out. The Day after I went out and bought another one too, go figure. Since I couldn't power down to enter recovery mode, I had to figure out another way to get there. It turns out that if you hold the Power button and the Up button at the same time, It'll power down your phone. From there you can Press the Power button and the Down button to enter into recovery mode. From here there are tutorials on how to go int ADB and sideload the old Kindle Fire firmware. I'm glad I figured this out. I think I'll stay away from those CM 12 themes for a while.