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?
Related
Can anyone give me a hand with this?
I was running CM7 n40 with ALSA and dalingrin's 0413a kernel. Watching videos in vevo when the nook froze and reset itself and got stuck looping at the CM7 animation.
I've rebooted into CWR, tried first wiping Dalvik cache, it didn't seem to make a difference. I then tried formatting /cache and reinstalling n40 and dalingrin's 0404 kernel. No joy either.
Short of reinstalling everything, is there anything else I can try?
If you are running from an SD card then your problem is likely the card. If you aren't running from an SD card then... Maybe someone else can help you.
Forgot to add, running from eMMC.
I had the same thing, only with CM stable...ended up having to rebuild my / boot with the file here.... http://forum.xda-developers.com/showthread.php?t=914690.
Very last file in first post. Had to flash it then start all over....
Sent from my NookColor using XDA Premium App
You are not alone, mine just did this after updating to the latest nightly and restoring with Titanium Backup. I did not flash a kernel, just the nightly using Rom Manager.
My symptoms were that it seemed to run OK, then I opened the gallery to set a different wallpaper and got constant FCs, so then I restarted. Now I'm watching the circle go round and round.
OK, back to previous, just restored the nandroid backup Rom Manager made prior to the update. Seems to be working fine.
I flashed n40 and dalingrin's oc kernel 0404. Stable and happy as can be.
I'm thinking the issue was with ALSA and experimental kernel 0413a, which has been reported to crash video playback in some cases. Don't know how or why it would corrupt my install though.
Let me just mention a lot of people are claiming false boot loops lately. Sometimes it just takes a long time to reboot, especially after it froze. I've had it take up to 20mins before with the little skateboard android.
So next time unless it's giving you "Touch The Future" and then the CWM treatment, give it a bit to load and see if it does after 10 mins or so. (Usually just after the screen dims, my nook loads up just fine)
No that's unacceptable. Considering the amount of data it should be loading, something is very wrong with your nook if it takes more than 5 minutes to boot.
And yes it was boot looping, the animation restarted itself repeatedly (wasn't just the arrow spinning).
Can't help at all but to offer another data point: I was on nightly 39, ALSA update, and kernel 0413a. Was flicking between homescreens when it locked up, forcing a hard shutdown. When I booted back up, it was stuck in a bootloop. Tried all the usual paths to recovery, but had to resort to a backup.
Moved on to n41 (ALSA included) and kernel 0418c. Stable in every case so far.
I'm having same issue and mine is still not working no matter what I did.
I even tried to restore it back to stock - Format/ Fdisk / DD / etc... tried everything I could find. I even had my back up but couldn't restore. I think I created more problem while I was trying to fix it.
Now I can only boot from SD. So I was not the only one.
Eww, I would never touch any sort of partition change with eMMC installs. Usually I just go back to stock or latest backup. Found out there may be an issue with backups created from CWR flashed to eMMC (MD5 check failure). SO anyone who's made a backp from that, do yourself a favor and boot off a CWR SD and do a backup onto that just to be safe.
Sorry about your troubles, hope you get it sorted. Guess I got away easy with just format and nightly re-flash.
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
I meant ACMEInstaller2 where I wrote Novacom2 ....
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....
quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now
I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.
I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?
I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?
I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.
Hi guys,
I just got two HD+ 32GB and installed cm-10.1-20130527-UNOFFICIAL-ovation-emmc following evergreen and leapinlar's instructions. The installation went well, and I can boot the tablets into twrp recovery. But I cannot boot one tablet into Android. It always hangs on CyanogenMod log (the rotating circle/wheel with CyanogenMod text at the center) when trying to boot into Android. I reboot the tablet several times now and still have the same issue.
I repeated the same procedure on another Nook HD+ 32GB and I can boot the second tablet into Android after several reboots. But I still have no luck with the first tablet.
Any suggestion?
Thanks a lot for the help!
Sean
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Ravynmagi said:
I installed CM10.1 eMMC on my HD+ for the first time last night and the same thing happened to me. So I went back into recovery and installed the CM10.1 again and then it booted up normally afterwards. So in my case at least it seems like it didn't install right on the first try.
Click to expand...
Click to collapse
Thanks a lot for the suggestion. I finally got It to work by booting into TWRP to wipe system, data, and caches, then re-installing from zips.
Sean
Same issue, apparently (hopefully...) resolved
LIke many other posters here and elsewhere, I installed CM 10.1 on my brand new Nook HD+ 32gb, got it to boot into CWM after many trials and tribulations (I had to reboot about 30 times to get the device to boot into recovery from SD; it crashed halfway through backup in spectacularly frustrating fashion, and it took me about 30 more hard resets to get it to boot into CWM again. I used a brand new Amazon Basics 32gb class 10 card). I did a little victory dance, loaded up some apps (probably too aggressively: 50 or 60 of them), rebooted, and.... you know what happened then, or you wouldn't be reading this (probably whilst sweating and/or crying).
After uninstalling some resource-intensive apps, then booting into recovery and wiping both caches, I was able to reboot normally (aside from waiting a couple of minutes for apps to be "updated" or "optimized" or whatever), but the next and all subsequent reboots failed unless I first booted into recovery and wiped the caches.
Finally, after reading a number of posters with the same problem (including @Ravynmagi and @sean_nj here--thanks, guys), I took a deep breath, did a full Titanium backup, booted into CWM, did a factory data reset, and reinstalled the three zips from the bootable SD. CM booted quickly and normally. I rebooted a couple of times with no problems. I installed a few apps, rebooted normally. I installed a few more apps (including a couple which I sideloaded), again rebooted normally. In the last 18 hours, I've installed a few more apps, played some resource-intensive games, tested Netflix and a sideloaded video, etc.
As of now, the device works like a charm and boots quickly and without drama. If anything changes (and I'm still able to communicate like a civilized human being), I'll make sure to update here.
unable to reboot get spinning logo
I recently updated Nook HD+ to 10.1 w/o problems.Each time I have rebooted it take 2 -3 tries before it finally boots ups. Those other times if boots to the spinning Cyanogen logo. Is there something I can do to check with the system booted up correctly to figure out the problem. If not, what steps should I take now and how do you do a complete backup of all the newly added material since the initial update. Thanks again,
Al
I'm facing the same problems but with a different setup: latest CM 10.2 Carbon ROM release (both versions with and without multiwindow). I have random bootloops and I'm unable to track down the problem.
Are we the only users with those bootloops?
Was searching for this. I am not having a problem booting per se, but all of a sudden I am getting a weird booting thing. Where the logo comes up and spins but its distorted, then it becomes normal looking, then my Nook will kind of reboot. Not a complete reboot just the screen goes black for a millisecond and then the logo starts over again where its all distorted, then it goes normal and then it boots.
I guess you can call it a logo boot loop. The thing is, it doesn't happen all he time, just most of the time now. When it happens, my SD card is incorrectly mounted and I have to umount it and take it out physically and re-insert it.
Nook HD+ 32gb, CM 10.1.3 stable and mbg4ga emmc. Not sure if this is the same as you guys but it sounds related. I've re-flashed several times. I think if you guys can find a cure, then it would probably work for me as well. Quick question, any of you guys using auto-patcher to patch Pdroid? How about Xposed?
For getting caught in the boot loop try:
Settings>Launcher>uncheck wallpaper quick render.
This is for stock Trebuchet 1.0 Launcher. I hope the developers are aware of this.
Probably coincidental but, the glitch caused by the magnetic closure on my case much better.(when you try to unlock and it blinks and goes back to lock).
Good luck.
I installed the latest CM 10.2 (cm-10.2-20130827-NIGHTLY-ovation.zip) as well as the newest GApps. Everything seems to work fine until I install a few apps. Unfortunately I can't say if any of the apps could be causing the behavior which is as follows:
I've had this issue a couple of times already and, after becoming frustrated mostly due to the Nook only deciding to boot from the SD every once in about 30 retries, usually resulting in a revert to stock by default, I gave up and reverted to stock. Of course the taste of CM that I got was too sweet to give up completely. So, today I tried again and had the same problem. Seemingly it will work fine until you reboot after installing quite a few apps. I made sure to restart the tablet several times after installing it and everything went as planned. Whenever the play store had finished installing my swathe of apps, I decided to restart and this is when I was met, yet again, with the rotating CM boot animation.
It's quite annoying really, considering how fast it seems when I'm using it. I haven't got CM installed on the tablet's own recovery partition (if it has one -- I've not read up on these things) but have been running it from the SD. I don't know if that makes a difference. I've formatted all the pertinent partitions before starting the ROM for the first time. I delete the data/cache twice all-in-all, once before and once after. Dalvik too.
Basically I'm flummoxed.
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
realeze said:
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
Click to expand...
Click to collapse
I can't clear cache because I keep the recovery on the SD and it decides it doesn't want to boot from it nine times out of ten, even after following the newer instructions for formatting the SD. After a few failed reboots it just reverts to stock. If I flash CMW recovery to the Nook's recovery partition, will I still be able to revert to stock that way? As annoying as it is, it's nice to have that ability.
I'll try a new install today and avoid checking the wallpaper hack because that appears to cause a problem. I had flashed it yesterday and used it for quite a while, installed all my apps and restarted it many times without issue. After checking that I think I restarted and met the endless logo. Will report back later today.
I can confirm that when I leave the quick wallpaper render option unchecked, it does not lead to a catastrophic failure. Strange that I need to reformat the SD each time or it doesn't reliably boot from it. Either way, I've been using this install for a few days now without any unexpected issues.
Thanks for the advice.
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.