CM9 keeps rebooting on NT 16GB - Barnes & Noble Nook Tablet

Having enjoyed CM7, I decided to try out CM9 with the latest version Alpha 0.04 on my NT 16GB. Install went smoothly and was able to boot into CM9 but as soon as I try to change the wallpaper it rebooted. Then I tried to install an app from the Play store and it rebooted again. It rebooted every time I did either of these things.
I tried the newboot.zip fix from succulent and the instructions mentioned here http://forum.xda-developers.com/showpost.php?p=26694005&postcount=609 but it didn't fix the problem.
Then I tried installing CM9 from rooted stock 1.4.2 and I'm encountering the same problems. I've also noticed that it seems to reboot approx. 10-15mins after boot no matter what i'm doing.
Any help with this problem would be appreciated.

I have a 16GB and I have not experienced this issue upon initial installation of .04 or after flashing the fix.
Have you been wiping data/cache prior to installing?

Yes, I have been wiping data/cache prior to installing.
This was my first attempt at CM9 and I didn't have this problem with rooted stock or CM7.

Fresh downloads of all the zips on another computer seems to have helped. Going on 3hrs without reboot.

Related

[Q] G Harmony-Problem Installing G-apps

I am trying to install the G Harmony ROM with BL 1.2[http://forum.xda-developers.com/showthread.php?t=1007455]. The install of the ROM itself is very smooth. After flashing the ROM, I tried to flash the G-apps using the file provided in the OP. The install went on smoothly. On reboot, however, I don't see any Google apps in the system anywhere. Indeed, even Titanium Backup, which was working well before I flashed the G apps, tells me I am not rooted. I tried wiping data,cache,dalvik and fixing permissions, but same result every time. I even tried flashing the CM7 G-apps, but same results. Any ideas, anyone ?
I am in the identical situation with BL1.1 or 1.2. about to try Cyanogen just to see if it's my tablet or not.
Just tried the latest cyanogen mod 7.0.3 and latest gapps. No Gapps or market from that ROM either. Dunno what we are doing wrong. Do we have to wipe our Internal SD's? I used gapps-gb-20110613-signed from cyanogen...and still no apps/market.
I also just tried wiping my SD card (internal), and formatting system. Had to nvflash back to stock. Atttempted G-harmony again. Same results. No apps will install from GoogleApps-GRJ22. It's really strange, the install appears to go fine from clockwork, then there is just nothing there.
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
hungrymr2 said:
Here is what I did to get gapps.
install rom, run it once.
innstall gapps, run it, and the screen will ask for gmail account and password
after failing to connect, its going to ask if you wanna connect by wfi..
done deal.
Click to expand...
Click to collapse
@hungrymr2 - that is what is not happening. After flashing the ROM, I am flashing the G-apps. I would normally expect to see the google set up screen on reboot, but there is nothing - no set up screen, no G-apps.
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
hungrymr2 said:
Interesting, i think it happened to me before. I had to reinstall the rom or a different one.
Click to expand...
Click to collapse
Went back to CM7 for now.
Looks like the matter has come to the attention of the dev. Hopefully there will be a resolution soon.
Make sure you clear dalvik code and cache. Might be a good idea to format the internal sd as well. Just good practice to clear everything each time you install a new rom.

Problem with new GingerStreak 2.4.4

i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
Honestly honestly what I suggest is you back up to a more stable build. GB2..4.4 is a beta just like all the Gingerbread builds and upcoming ICS builds will be betas because there are no official releases,
If something like a boot loop hangs you up, you definitely shouldn't be running Gingerbread or anything beyond Froyo as those problems will always exist with these builds....
But to answer your question, you need to boot into recover, clear your cache, your dalvik cache, flash the ROM again and then do a factory reset
raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
cdzo72 said:
Honestly honestly what I suggest is you back up to a more stable build. GB2..4.4 is a beta just like all the Gingerbread builds and upcoming ICS builds will be betas because there are no official releases,
If something like a boot loop hangs you up, you definitely shouldn't be running Gingerbread or anything beyond Froyo as those problems will always exist with these builds....
But to answer your question, you need to boot into recover, clear your cache, your dalvik cache, flash the ROM again and then do a factory reset
Click to expand...
Click to collapse
The latest GingerStreak build is stable for most people using it, but it is not a final release yet
The boot loop problems are most likely related to not doing a factory reset of the phone or not following the install instructions to the letter. Another possibility is over clocking the CPU too high, some Streaks can not be over clocked.
If you can get into recovery do a reset from the first screen.
ADW
Just to add......I had the same problem after flashing 2.3.3. In fact, mine went Bricked and couldn't even get back to stock with streakflash. Luckily, I've had BB's Geek warranty, so I got a replacement.
Couldn't stand stock ROM, so tried SD 2.4.4. All went well until I started updating restored apps from the market, then phone would go into reboot loops, requiring a factory reset each time.
Then I tried without overclocking, still crashed into the reboot loops.
Finally, went to a different launcher (Go, rather than ADW) and so far it's stayed stable. No FCs, nothing. I'm thinking ADW didn't like something.
raptoid said:
i installed GS 2.4.4 and intalled same programs after reboot the streak and have a problem loop booting what can i do ?
Click to expand...
Click to collapse
I think is md5 checksum problem, try to verify it before flash, and flash rom only if you're sure of that
Just try dsc rom. I got no random reboot, no sod or any major bug.
power_rom is rapid, stable and smooth.

multiple problems with gtabcomb 3.3 - help?

ive been getting tons of force closes, wifi "error" in settings, apps freezing and locking up, market and google apps not recognizing my accounts. tried factory reset, wipe, davlik, repartition, and reflashing gtabcomb 3. no change.
is it time to nvflash to stock and start over? anyone else have issues like this?
I too have run into the same issues you are reporting when I was running gtabcomb and flashback 10. I am not going to say that this will fix your issues, but I can verify what happened for me. The other day I unluckily (or luckily I guess) got stuck in a CWM boot loop. To resolve the issue I NVFLASHed back to stock, wiped data and reflashed flashback 10. Since then the performance of my tab has improved tenfold (at least). I have had one instance of the wifi error, but have had far fewer FCs. It actually made the tab much more usable. If you haven't already, I would suggest an NVFLASH to start with a clean slate.
RonPorreca said:
I too have run into the same issues you are reporting when I was running gtabcomb and flashback 10. I am not going to say that this will fix your issues, but I can verify what happened for me. The other day I unluckily (or luckily I guess) got stuck in a CWM boot loop. To resolve the issue I NVFLASHed back to stock, wiped data and reflashed flashback 10. Since then the performance of my tab has improved tenfold (at least). I have had one instance of the wifi error, but have had far fewer FCs. It actually made the tab much more usable. If you haven't already, I would suggest an NVFLASH to start with a clean slate.
Click to expand...
Click to collapse
interesting. i completely wiped tablet, repartitioned, wiped caches, dalvik, reflashed and so far, so good. if this fails, ill nvflash to stock. thanks!

[Q] CherryKang Issues

Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.

[Q] PA ROM weird issue!

After flashing the latest version( pa_i9300-5.1-20150528.zip) in recovery, 'Reboot System' reboots to recovery itself. Weird! So I flashed the earlier version(pa_i9300-5.1-20150520.zip) and it rebooted to system and it works. Now I get the OTA update in 'Paranoid OTA' app for the latest version that gave me problems. If I install,
1. Will there be any issues with reboot or any other related issues?
2. Should I reinstall installed apps after update?
Thanks 
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Organizer21 said:
Not sure if related but I installed pa_i9300-5.1-20150520.zip some time ago on my i9300, everything has been working nicely. Then came the 28th update and another one earlier this month... but installing those updates just resulted in a crash after installing (as in the boot screen looping). Now my system just popped up with an 20150619 update so I thought to try again, but again it download and installs just to loop the boot screen. This time thought I afterwards decided to re-install superSU and my boeffla kernel, that seemingly did something as the phone booted and update. Now maybe this is something one have to do for each update for it to work? I'd love to know for the future as I'm no expert on this, though if you have something similar maybe that's what is required.
Click to expand...
Click to collapse
I think flashing the Kernel as you did after the dirty flash will help. But the there is no stable Kernel available for CM12.1, even the Boeffla you are using is in the alpha stage, no support yet! So how is the battery life and stability with Boeffla Kernel?

Categories

Resources