Hello guys,
Still unsolved
Suspects: uwlopservice (in logcat log), dalvik-vm, link2sd
I have a bootloop problem after installing numerous apps and then using link2sd to move them to sd-ext. I've noticed that whenever I use link2sd it sometimes reboots the system whilst processing numerous apps to link, I'm not sure if this is related to the bootloop problem.
Anyway, this was the last thing I was doing before the device entered a bootloop. The bootloop reboots after the main screen is shown (however there is never enough time to enter the apps menu before it reboots), the reboot sometimes happens immediately after the main screen is loaded or up to about 30 secs after.
I initially thought this was due to the lack of space on /data but i moved the dalvik-cache to sd-ext, but the device still continued to bootloop. The other thing is that I have installed 256 apps (a nice power of 2), perhaps the x8 is limited.
I've attached the logcat log (as bootlop) and the /data/anr/traces.txt (as traces-bootlop).
I hope someone can help.
Cheers
j.
Still unsolved (see next post)
OK. The problem no longer manifests itself on my device. I am unsure of the cause and what I may have done to correct it. However, the main changes I made are as follows:
* Restored original non-bootlooping ROM backup (CM mod backup and restore feature)
* Restored bootlooping ROM backup.
* Moved the dalvik-cache from /data (which was 99.9% full to sd-ext). I tried booting after this, but the OS still bootlooped.
* Created a backup of this ROM.
* Restored the previous step's ROM after restoring any other ROM.
* Calibrated the battery using BatteryCalibrate(tor) on the market.
I do not know whether these steps actually solved the issue, but the problem no longer manifests itself. Perhaps this will be useful to someone else.
Contrary to the previous post, my x8 is still experiencing a bootloop. However, I have discovered that the loop occurs only whilst having the USB/charger cable plugged in through the entire boot process. If the cable is plugged in after boot, the device does not crash (i.e. reboot entering a bootloop). I wonder whether any other users have experience this.
(edit) now this problem seems completely intermittent. sometimes it boots successfully sometimes not, i'm guessing that there is a rogue app somewhere causing this. Just a suspicion so far.
*bump******
decrease789 said:
Contrary to the previous post, my x8 is still experiencing a bootloop. However, I have discovered that the loop occurs only whilst having the USB/charger cable plugged in through the entire boot process. If the cable is plugged in after boot, the device does not crash (i.e. reboot entering a bootloop). I wonder whether any other users have experience this.
(edit) now this problem seems completely intermittent. sometimes it boots successfully sometimes not, i'm guessing that there is a rogue app somewhere causing this. Just a suspicion so far.
Click to expand...
Click to collapse
yes in 2.1 stock to solve this i replaced stock with a custom rom where i could use app2sd ie: 2.2 or 2.3
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've left my phone with 60% charge yesterday night.When I woke up the battery was at 0%.I charged it to 100%, rebooted and the phone was stuck at LG loading screen.I got CM11 nightly 26.
Then I restored 2 diff nandroid backups after a full wipe.It did not work and I finally decided to use lg mobile support tool.It successfully downloads, installs the firmware but somehow the phone is stuck at bootanimation.
I've tried to reinstall USB drivers; flashed the KDZ about 5 times now and I really am hopeless.
I haven't dropped my phone; haven't done any physical damage to it and as far as I know if it was just corrupt internal storage I could get over the problem by wiping the partitions.What could be causing this problem?
Weird part is; when this happened I wouldn't even get to see CM boot animation but after attempting to unbrick the phone with mobile support tool, I got to see the bootanimation but it didn't boot (waited approx 30 mins)
Has anyone faced such annoying brick before? What could be causing it? Any solutions/recommendations?
EDIT : According to logs the s/w upgrade completes successfully.No errors nothing, but the phone won't go thru the boot animation.
Mobile support tool .KDZ flashing logs
EDIT2[SOLVED] : Seems like I've found the issue and solved it.The O/S crashed somehow during the night; damaging the TWRP date file(s).As specified in this post (under warning title) it led to a softbrick which can only be recovered after flashing a firmware and wiping data/cache partitions afterwards.I actually had TWRP 6.3.0 and was made by a different user but issue seems to persist.Guess I'll stick with CWM.
I hope this helps someone if they face the same issue later on.
Hi, this is my first post. I have tried to search and look through the question threads, but nothing seems to be close to the problem I have here, hoping someone can help me.
I have this Xperia TX, recently given by my friend, it can boot up ->sony->ribbon-> entering system->shutting down, it's not like a sudden blackout but more like a command sent telling the phone to shut down, it has the window saying shutting down and vibration at the end, but the shutting down is instant, can't operate yet. I made several approaches trying to fix it, these are what I have been done with it.
-Flashing different stock ROMs using flashtool, the flashing went perfectly without errors, and phone will boot and install new system until the setup wizard (languages, time etc) comes out on screen, and it shuts down right away.
-I used flashtool to unlock BL, succeeded.
-I flashed TWRP, it can boot into TWRP without any problems and working fine.
-I formatted the phone partitions using TWRP, working fine.
-I flashed cm-12.1-20151010, and same thing happened as soon as the system launcher comes out.
-And I flashed stock ROM again, the problem remains.
The phone won't charge the battery, so I tried using a separate charger avoiding 0 battery situation (I do see the battery icon showing 50%+ when it shutting down), and I also tried another lt18i battery (don't want to buy a new one yet in case the phone is dying), and there is no different.
I don't understand the problem, all the operations work fine but can't boot in system, doesn't seem like a hardware thing but what else can it be? I am not hoping to fix it any more at this point, but can anyone tell me what could possibly cause this? Can I read a boot up log somewhere so that I know what happens during booting?
I hope I didn't break any routine or do anything wrong here, if I did, apologies in advance, thank you.
hello there,
i recently installed cyanogen mod 11 (4.4 kitkat) on my phone via CWM. i used following guide to restore my data:
http://androidforums.com/threads/guide-to-retaining-data-after-flashing-a-new-rom.682090/ (basically just restoring my data through a cwm option).
however, the system keeps optimizing 78 apps on every boot. on the first boot it were around 170 apps. i tried some of the solutions on the internet, e.g wiping my dalvik cache (which leads to oprimizing the 170 apps again) or not charging while booting, needless to say none of them worked.
one solution i havent tried yet is to reinstall the apps. i would like to know if you have suggestions which may work. also please tell me if i you need any further information.
Doflaminhgo said:
hello there,
i recently installed cyanogen mod 11 (4.4 kitkat) on my phone via CWM. i used following guide to restore my data:
http://androidforums.com/threads/guide-to-retaining-data-after-flashing-a-new-rom.682090/ (basically just restoring my data through a cwm option).
however, the system keeps optimizing 78 apps on every boot. on the first boot it were around 170 apps. i tried some of the solutions on the internet, e.g wiping my dalvik cache (which leads to oprimizing the 170 apps again) or not charging while booting, needless to say none of them worked.
one solution i havent tried yet is to reinstall the apps. i would like to know if you have suggestions which may work. also please tell me if i you need any further information.
Click to expand...
Click to collapse
Have you tried:
Boot (and update), software shutdown, reboot? (i.e. select Power Off on the screen)
Boot (and update), hardware shutdown, reboot? (i.e. hold down the power button until it dies)
Boot (and update), remove and replace battery, reboot? (i.e. don't let the operating system shutdown properly at all)
Taking a backup after it's updated, then restoring from that backup?
Wiping regular cache as well as dalvik?
That's just "this might work" things I might try.
As for actually diagnosing the issue and prescribing a targeted response - that's beyond my expertise.
assuming with "update" you mean the optimization process: yeah, tried most of them except your fourth suggestion. going to try that one soon. even if it should not work, your answer is appreciated
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.