cm10 first boot only - Barnes & Noble Nook Tablet

hello there guys
i have nt 16gb
i installed cwm 6.0.2.5 emmc version
and then i installed cm-10.2.1-acclaim.zip
all went well and the device booted fast
but whenever i restart or turn off the device
it wont boot any more
it pass the cyanboot screen to a black screen and stays there
wiping does solve the issue until next reboot
plz help
do i have to change the cm to an earlier version
does the gapps has anything to do with this , i didn't install it

This "boot into black screen" or "boot crash" is, unfortunately, a known and unresolved problem with 10.1.3, 10.2.x and also some 11 builds -- see http://forum.xda-developers.com/showthread.php?p=48305694#post48305694, http://forum.xda-developers.com/showthread.php?p=49046310#post49046310, http://forum.xda-developers.com/showthread.php?p=48301259#post48301259 and http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94.
You might want to give the CM11 Snapshot M4 build a try (see http://forum.xda-developers.com/showthread.php?t=2670589 for how to upgrade to CM11), as I have not run into the issue with this build.

what about 10.1.2

i tried 10.1.2 and it worked
but it has some issues
there are some apps that doesn't work like candy crush and sumle apps
and nt shuts down when it has 25 percent
it shut down and stuck in a restart loop till i plug the charger
any idead?

Related

Nook tablet restarts again & again

I wanted to try TWRP recovery. I installed rashr app and installed TWRP latest on sd card then rebooted the tablet. It showed me N logo for a few seconds then turned off itself.
Now whenever i turn it on, it shows that N logo for like 5 seconds and turns off. When connected with USB, it keeps restarting. I tried removing the sd card, but no change at all.
Please tell me how to fix this.
Update
i got into clockworkmod 5.0.x recovery (made a bootable sd card) and installed old CM10. But still it keeps flashing only the Nook N logo & restarting forever. I guess my tablet is badly bricked. Is there any other way to fix this?
You need a version of CWM between 6.0.1.x through 6.0.3.x to flash CM10. See http://forum.xda-developers.com/showthread.php?p=51377882#post51377882 for additional info/pointers on how to install CM10.x on emmc.

cynogenmod 10.0 bootloop + error log attached

Hi,
I still have an old v10.0 cyanogenmod on my i9300, a nightly build from August 2012, because there never has been a stable release.
Recently i have found my mobile (having only 2% power less) try to switch off, but it seems that it wasnt impossible for the OS to switch off and so it restarted without having power. Because it was in the night, I just found my mobile in the morning with a bootloop and no power. Even after pluggin the mobile to power and first charging to 100%, I still cannot switch it off. After switching off, it instantly reboots.
The worst problem is, that it is not able to boot. I only see the cyanogenmod boot logo rotating.
With the recovery mode I can access to both sd card and onboard storage. I have downloaded the aroma filemanager and have done an e2fsck with the onboard shell: no problems, everything is fine!
Have cleaned dalvik cache and cache partition: No changes in the behaviour.
Then I have updated the cyanogenmod OS to the latest 10.0 version: cm-10-20121214-NIGHTLY-i9300, but: no changes in the behaviour.
Then I have done an "adb logcat" bootlog, there is a loop caused by a fatal errror in the ActivitiyManager, after each fatal error there is a loop and the mobile tries another time to boot and the log nearly repeats. I have attached the part of that logfile, which repeats every time, means: after the last line of that log you can place the first line of that logfile, endless.
I don't want to upgrade to 10.1, 10.2 or 11, because I still have some important data like wechat and whatsapp msgs, game saves, and so on, which I dont want to lose.
Does someone has an idea, what I can try to do?
Big Thanks!

Black screen after Lg boot logo...

I tried to update to cm13 and flashed the 35B modem and kernel. I then wiped and flashed cm. It didn't boot so i tried Resurrection Remix. I finally got it to boot by selecting safe mode. It didn't boot into to safe mode but booted normally. Now I only get passed the lg boot logo every 5 or 6 times I try to boot. I get a black screen and have to power+volume down and continue boot. Eventually it boots and everything seems to go as normal. I'm only using it as a WiFi device for my daughter to play with but as far as I can tell the radio is working fine and there aren't any other issues. I'm not sure if there was a partition I should have flashed with the other two maybe I missed something during the update... Coming from cm 12.1

Very slow boot up..

My device is a kenzo 3gb 32gb and I face extremely long boot times just because the phone is stuck on mi logo for at least 30secs before starting the os boot animation.. Also after flashing open gapps latest I lost the ability to reboot to recovery and even i cant power off my phone until I go to twrp also third party apps don't reboot the phone to recovery. (Btw i am on omni homemade 8.1 oreo with shadow kernel and reboot to recovery and power off just worked fine without gapps installed)
Can anybody suggest me a fix or workaround for these annoying things I really don't like it.
Thanks in advance.
Those are shadow kernel bugs, change your kernel.

Kernel is not seandroid enforcing and nothing able to do

So, yesterday i wanted to install the lineage 15.0 on my samsung galaxy tab s 10.5 wifi. to my tab: i already hat lineage 14.1 and twrp installed. so i thougth - no big deal, would be a thing of 10 minutes. so i did like the 14.1, flashed the device, installed the 15.0 and the fitting GApps and so on... then i booted (it was already showing the error in the corner), it worked - for a small time. the setup-manager crashed everytime i tried to enter it and so, i shut it down. after that, nothing works anymore. its just showing the error and the grey charging symbol. when i try to enter download mode, the screen turns black for a second and the same as before appears again. my computer isnt recognizing it eather. what can i do? i couldnt find anything about this case
*Update* : i just had to remove the battery and wait a minunte, then it worked again

Categories

Resources