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 ??
Related
I bought a Droid from ebay with a known problem of a boot loop. I got it fully booting up and somewhat working. It was on android 2.0 so it was easy to root. I then with rom manager installed CWM and installed the latest Cyanogenmod 7. I have formated all partitions before installing C7. My question is i'm still getting multiple reboots before it finally boots. Then random freezing and reboots happen.
Is there a fix for this phone?
Well i think i know what the problem is. The screen needs to be calibrated. I went into dev tools on CM7, pointer location and the with 1 finger placed on the screen it jumps around and is very shaky. On my other droid it is a single pixel. Is there a way to calibrate the screen?
I recently returned to stock 1.2 with the default recovery flashed (CWM SD card), and then I upgraded to 1.3, and then rooted with the ManualNooter 4.5.18 and 4.6.16 (or whatever their numbers are, I followed the instructions to the T).
It worked fine and I installed everything i needed from the market/titanium backup/etc but the second time I reboot the device it is stuck in a boot loop. The splash screen slowly writes out the word "Nook Color" and it will complete this once, but the second time it does this, it reaches the L in Color it stops and starts over. It will do this for hours.
I wiped it and started fresh over, reinstalling 1.2, re-updating to 1.3, re-nootering (sounds dirty...) all over again, re-installing all my apps all over again (took forever) and yet it still does this. As soon as I rebooted it, this began again
I'm a longtime lurker with a rooted and much-abused DInc, I've had PhireMod, CM7 (without the sleep of death) and Honeycomb on my Nook all without issues (that I couldn't fix). But this has me completely flummox'd. What makes this harder to deal with is that my Nook will not recognize my home Wi-Fi so I have to do all my work on it during my lunchbreak (another issue entirely; unrelated, home wifi is a software solution)
Any Ideas? I haven't yet had the chance to flash the better kernel, because when I reboot it's stuck in this loop. I tried re-nootering and that did not help.
Same with me. Happened 3 times to me last night. I'm still figuring out what i can do to make stock 1.3 + OC + rooted to work.
I'm trying to determine what I did in those 3 times in common. Only thing i can think of i did in all those 3 times was OC +format SD card and installed titanium backup from market.
I'm sure its not a new issue because I remember this happening to me a month ago then I gave up and just went back to miui.
I had the same problem. Look for post about adobe flash causing boot loops. I solved the issue by:
1: after installing 4.6.16, I signed into the marked, downloaded titanium backup
2: used TB to delete the copy of abode flash and adobe air.
3: restarted the nook and had no boot looping.
4: I searched and found a copy of the current adobe flash and sideloaded it using CWM.
It's been 3 day and no boot looping.
Regards
I also had the boot loop issue. It was caused because I updated my flash. Check out this thread....it fixed my issue.
http://forum.xda-developers.com/showthread.php?t=1208896&highlight=boot+loop
Thanks, Johnny. You've saved me a lot of trouble.
No problem! Happy to help! Thankfully GMPOWER threw together that zip file for everyone!!
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
joej said:
Be careful when you install any 3rd party keyboards to /system, it also resulted in boot loops for me with a few of them
Click to expand...
Click to collapse
Was thumb kb one of them?
dohturdima said:
Was thumb kb one of them?
Click to expand...
Click to collapse
I have had no issues with Thumb keyboard (either after initial install or updates).
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.
Hello everyone,
first of all thanks for your amazing work and all the stuff you provide. I was a silent reader for a long time, but now my phone is trolling that much, I cannot fix it on my own/with the guides I found here.
I do have an HTC One M7, rooted (superuser) and S-OFF (revone) with Androidd Revolution HD 71.1. I used to update my ROM every month, but I got stuck after the last update. My recovery was TWRP as CWM did not work properly when I rooted my phone.
My issues as a list:
- cannot enter recovery anymore
- cannot connect via USB (tried every port)
- screen turning randomly black on homescreen and sometimes in apps (but they usually work), screen does work, but i cannot see a thing
- since today graphical issues after a reboot (flickering screen, parts of the screen get duplicated)
Since the last update I cannot enter recovery anymore. Getting in bootloader is no problem but i get stuck in the "entering recovery...." screen. It does not move, tested it for some hours. I tried updating the recovery (-), trying to flash stock recovery and reflashing custom (-), trying cwm (-).
After I tried cwm i noticed that it didnt overwrite the recovery but i got both. cwm and twrp, but i cannot delete one of them (didn' work before either). I can start TWRP oder CWM on a booted phone, but updating both bugs and I can't enter recovery with these tools too.
Today I wanted to try again on my own, but my phone won't connect on USB. Tried every port on my computer with and without USB-Debugging. I will try on a other computer, but I could not do this until now. Additionaly I want to wait for some ideas of fixing, as I think "my" trys are not going to work suddenly .
Screen started to turn black a few days ago. Dont know why but I think it could be a software issue. but i cannot update (see above ). When i try to turn my screen on it often just turns instantly black. soft keys are enlightend and it does work (more or less). if i success in sliding down the service bar on the top, i can start my alarm clock app and from there use the soft keys to get in other started apps. From there it works most of the time. Sometimes i need a couple of trys, sometimes it just works as its intended without turning black and sometimes i need several minutes to succeed.
Cannot say more as I did to the graphical issues. Just had them once until I started an app (screen worked). could not reproduce this error.
I would prefer a solution without wiping, but if necessary i will ofc.
Thanks in advance for your help, as I am rather helpless right now.
I attached a photo of the bootloader.
Yours Laexxi
I'm running CM12.1 on an international M7. It's been running fine for two years, but about six months ago it crashed and got stuck in a boot loop. Wiping the cache alone didn't help because it got stuck in an "optimizing app" boot loop, so I wiped data too to make it boot again.
Since then it has been difficult to install new apps from the play store. Sometimes it will reboot after installation of a new app. If that happens then then starting newly installed app will cause an immediate reboot again. After this happens, restarting will also give me a number of "Trebuchet stopped" messages. If I'm unlucky, then it will reboot into a boot loop again after installation and I'm back where I started.
Since the rebooting occurs with different apps and always happens first after the installation, I suspect the data gets corrupted. Which may mean the flash is defective.
Is there a way to properly diagnose this? And if it is a flash storage problem, is that even fixable?
Did a full reformat of everything and reinstalled it with Resurrection Remix. So far I have not had any problems.