[Q] CM10 suddenly unstable after reboot. - T-Mobile Samsung Galaxy S II SGH-T989

recently flashed cyanogenmod 10 (stable) to my sgs2. It worked wonderfully until my first reboot, then any app, including settings would freeze and need to be killed. I tried fixing permissions, but would get stuck at the boot animation. tried wiping cache, again stuck at boot animation. restoring from a backup made before the first reboot works fine, but sure enough the same stability issues come back if I reboot the phone.
Anyone have any idea whats going on or how i can fix this? I searched for a while for similar threads but couldn't find anything.

so ronrey.

Related

Software causing phone to freeze on boot

Hey guys,
I went to reboot my phone this morning, and for some reason, it caused my phone to get stuck at the white HTC screen.
I did a full wipe, reflashed my ROM (ARHD 3.2) and installed all my programs. Again, on reboot it crashes.
Now, I have flashed the ROM again. After install I did a reboot, and it worked perfectly. What do you think could be causing this? Some software interfering with the boot cycle?
madindehead said:
Hey guys,
I went to reboot my phone this morning, and for some reason, it caused my phone to get stuck at the white HTC screen.
I did a full wipe, reflashed my ROM (ARHD 3.2) and installed all my programs. Again, on reboot it crashes.
Now, I have flashed the ROM again. After install I did a reboot, and it worked perfectly. What do you think could be causing this? Some software interfering with the boot cycle?
Click to expand...
Click to collapse
Did you restore your backups? Did you use fullwipe to wipe or did you do it manually?
I remember last time i got bootloop/stuck at HTC screen was when i restored my apps from mybackup pro...sometimes these apps do not work as they are supposed to
All I did was reboot my phone. Then it crashed.
After I flashed the ROM again, and reinstalled some apps, it crashed again. I hadn't restored any data at all.
I'm assuming then that it was an app that caused my phone to crash.
Could this be a hardware issue?
I reflashed a new ROM, installed some programs, went to reboot, and it has crashed. Again.
REALLY starting to annoy me. Anyone have any ideas what could crash a boot crash like this?
Ok. I think I have found the culprit!
Seems it's Busybox v1.8.1.4!
I installed it, rebooted and it crashed. Did it again on a fresh flash with no user data returned. Same effect.
Just out of interest, has anyone else had problems with Busybox 1.8.1.4 causing their phone to crash?

[Q] Random reboots and bootloop even after fullwipe

Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!

[Q] CM 10.2 bootloop, after successful boot

Hey all,
I've been running CyanogenMod 10.1.3 (Stable) since it came out, and used the Nightlies for many months prior to this.
I recently decided to try the CM 10.2 nightlies, and successfully booted into CM 10.2-20131107. I let Google play restore my apps, and then decided to run "Fix Permissions" and reboot for good measure, however my device was stuck in a boot loop (Google screen with lock) for approximately 10 minutes, before I decided it definitely wasn't going to boot.
This is the second time this hapoened, the first time being with an earlier 10.2 nightly. I assumed it was an issue with that build, but ive found no other reports of my particular issue (I apologise if I am wrong about that, its hard to know exactly what to search for!)
Prior to install, I wiped everything (System, Dalvik Cache, Cache, Data and data/media) for good measure.
I use TWRP.
Does anyone have any idea what the problem might be? I've wiped everything, and gone back to 10.1.3 now with no issues, so at least I have a functioning device.
All I wanted was natively supported TRIM..

Getting bootloops after rebooting for being laggy

Hi all, I would like to have some feedback if some of you is experiencing the same issue as I am. My N5X is running Stock Marshmallow (latest release) and it's rooted (SuperSU v2.71) with Xposed (latest version for arm64).
Every now and then (usually with an uptime more than 80 hours) the device becomes very laggy and my usual solution for eliminating the lag is rebooting. It would be the ideal solution if only the device wasn't remaining stuck in bootloop after rebooting.
For now the only "solution" I have found is doing a factory reset from TWRP, after performing a backup of /data. Uninstalling from recovery Xposed or simply wiping cache/dalvik or even flashing separately the stock images (boot, cache, system, vendor) did nothing without a factory reset.
The first times I got bootloops on the device I knew why it was happening (one time I modified build.prop forgetting to change the permissions, another time a similar thing but with the transfer of an app in /system), but these kinds of bootloop remain a mistery for me.
It also occurred without Xposed installed and with both stock and ElementalX kernel.
A peculiar thing I noticed while in TWRP is that the Cache was displayed occupying 0 MB. Might it be related to this issue?
Now, I know now that I should probably reboot more often, but I still would like to know why this happens because it's being very annoying doing the restore procedure every damn week.
And so, while doing my research, I wanted to have some feedback from those of you who had similar issues with a similar setup.
Thanks and cheers!
A new kind of problem occurred. This time Telegram wasn't connecting to the net and so I rebooted. And BOOM, stuck at the boot animation (the four colored points) for no apparent reason.
If I only wiped Dalvik and Cache in recovery, the phone would go past the boot animation, but after the Android logo, it would display only a black screen.
This time, before doing a factory reset, I flashed via fastboot boot, cache, system and vendor, hoping that could solve something for the future.
I have no idea why this is happening. After the new reset, I will try to limit the modifications to /system by not installing Stericson's Busybox and GSam Root Companion app, but I'm still wandering in the dark. It looks like my 5X is possessed.
Please, if you have any sort of feedback or insight, I will gladly listen.
Update: today I had no issues but I rebooted anyway. Result: stuck at bootanimation.
As you English speakers say:"F*ck this sh*t, I'm out".
Yeah, I decided that I'm done with the stock ROM and decided to flash PureNexus ROM in the hope that the **** up I was doing with the stock ROM will never happen again.
Maybe now the mods can close this thread.

Galaxy Note 10.1 SM-P600 Reboot Loop

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!

Categories

Resources