Hello everyone!
I installed the snapshot from 6 to 8 and the latest nightly (2/8/14), and C11 small gapps, through TWRP 2.7.0.0 with full wipes (except sdcard).
It's frustrating the many hungs up and random freezes requiring reset. The screen freezes and the apps are useless by themselves activated.
I do not know what else to do.
I beg you to help me.
Sorry for my bad English, and greetings to all.
Related
Hi,
I'm experiencing sudden boot crashes 2 different distribs of Android on my G1.
First with Dwang installed and running fine for several weeks now, the phone simply stopped booting for no reason (Android boot animation freezes then black screen).
Now, after a full (accidental, by the way...) wipe, I'm back with a brand new CM. I reinstall my favorites apps, reboot several times, and suddenly with no apparent reason, I cannot boot again !
It seems that the most recent installed/used app on both cases was Sleep Now! from mobitobi. Without much hope, I tried to remove the app from adb, still not booting.
Here is the catlog : pastebin.com/SepbzzC4
Thanks in advance !
Got it !
Reading the logs, the bug was when scanning for app-private. I'm on App2SD and for some wicked reason, the symlink on data/app-private was broken
Any ideas on how i could happen by accident ??
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.
hi, i have read developers forum and CM11 seems no issues for others except some dock keys and USB3. but for me still freezes:
- at firts time I installed CM11 from official JB, it was some nightly build from march, CM froze within few seconds in setup screen.
- then I cleared again all caches, installed next nightly build, all went ok, CM worked ok for me (FIFA14, music browsing, etc...) but then i installed some Angry birds series for children, and tablet became unstable (maybe more core apps have been updated), froze during games withing 10-20 minutes, I thought it is issue of the game, i uninstalled all Angry birds games, tablet became more unstable, froze within few minutes.
Then i downloaded and installed yesterday nightly build, installation went ok, but again tablet freezes within few minutes...in setup menu, in stand by mode, in game....OS is not working but battery is discharging. then i downloaded and installed today night build, and installed CM completely without keyboard dock, and local language i set to English (original i am using Slovak) to avoid possible issues with dock, keyboard, language set...but it is the same...tablet freezes within few minutes.
then i installed back official JB...all is going ok.
Any idea what is wrong? I have installed CM on Galaxy Tab, on Samsung S4, no problems.
i have working boot loader 10.26 and CWM recovery 6.0.4
-before installation i did factory reset, cleared cache, dalvik cache
-installed CM
-installed signed GAPS
any idea please?
Update your fw/bootloader to 10.26.1.18.
This can be done via microSD update method from ASUS.
Installing an OTA may not install the needed FW/BL in all cases.
The phone just died for the battery ( i have the battery problem of this phone, it dies on 20% battery like you disconnect the same) and I charged a little (20%) and when I boot it up, the phone is soft bricked (just ROM boot screen and vibrates occasionally).
I have last LineageOS Nightly for the phone, root, and busybox.
I had this problem a few times in the past and i successfully solved it by erasing data in TWRP, but its REALLY FRUSTATING format all the apps and start again without previous backup.
I want to find the way to solve it without formating the /data.
Hope help of any of you, thanks<3.
PD: Sorry for my bad English.
Hi friend,
i have the same problem with Ressurection Remix V5.8.2 (Moto X 2014), i found a "fix" without lose any data, simple re-flash with before version of the rom (and clean cache) (in my case Ressurection Remix V5.8.1) and start phone, after boot (ignore some app errors) quick reboot in recover mode and re-flash with the actual version of rom you use (clean again cache) (in my case Ressurection Remix V5.8.2).
Good lock.
Fabiano Souza
Hey bro,
I have the same issue when I have opengapps installed. So it may be fixed with uninstalling opengapps.
It works on ViperOS v2.1 although brings inconvenience
Good luck
Same problem here (for the second time) and occurred on 31st July 2017
zureau said:
Same problem here (for the second time) and occurred on 31st July 2017
Click to expand...
Click to collapse
you try the tips in the post? Same problem after try?
Hello, it's my first post on this forum so sorry If I made this thread in the wrong place.
I have been trying to install PE 12 (plus edition) using official PE site (https://download.pixelexperience.org/lava).
After many attempts to do so, I ended up installing different TWRP recovery images and wiping everything from my phone.
Then I've tried installing official recovery image from site and I've installed ROM by adb sideload and it worked.
First boot wasn't a problem, but from start phone would sometimes crash when attempting to turn it on (or, attempting to unlock lock screen. I can write my PIN, but then rebooting happens). When it wouldn't crash (it's not happening every time) everything would be working as long as I don't turn it off. I don't know what is causing that behaviour.
Would reinstallation help or is it hardware problem (not enough RAM etc.), or lack of swap partition?
PS: Updating every app on phone doesn't help, as well as removing lock screen (no PIN etc.).
Update: I have installed different ROM from sourceforge dedicated to my phone version (galahad). It is android 11. Works 100% fine.