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.
Related
Team Vanir Jellybean v2-7, Galaxy Nexus Verizon
Last week i was having issues with the phone not booting, or just locking up not responding etc. A wipe seemed to help, and wit work for a while. I'd get my phone setup to where I wanted it again, and then the issues would come back.
I found a post that said it was possible EXT4 formatting issues because of a bad poweroff. So I downloaded all the stock 4.04 images, fastboot erased system boot recovery. Flashed the latest radios, stock system boot userdata and clockwork recovery 5.5.0.4. Booted seemed to be fine.
Rebooted into Clockwork and installed Vanir v7, ran fine for a few days. I thought the issue was gone. Until this morning when I got a text message and went to unlock the phone and it was locked up. I pulled the battery and that is when everything got extremely bad
Would not boot past the boot animation. I tried the following
I reinstalled the ROM,
i treid to wipe data,
wiped data and reinstalled the ROM.
although I was able to make a nandroid backup before I tried all of this
Then as a last resort I went into the mounts and storage and FORMATTED /system /data and /cache in CWM. Reinstalled the ROM and it actually booted.
What greeted me there is the last thing I'd EVER expect to see. I don't know how, what or why but all my data was there... every app text missed call... all of it.. even tho I had wiped AND formatted several times and did NOT restore my backup. EDIT: Even more oddness... My user apps didn't get wiped, they are all still there, but they are all acting like I had cleared their data through the applications menu....
I still don't know if this is because of a NAND issue that formatting fixed both times (flashing stock and using format in CWM) or if it will ever come back. Has any1 else had any issues of this sort? I really don't think this is a ROM issue.
you're probably causing more damage by flashing this, wiping this and that. best option is to leave it stock for now by flashing the factory image again. if it is a NAND issue then it would have stopped booting when the issue occured. but if it is still causing problems then send it back for a replacement.
First, for shortening and simplicity let's use cm versions only last numbers (cm-12.1-20151230-NIGHTLY-nicki will be 30 etc.).
I will arrange my short story in points for better understanding, let's begin here:
- I installed CM 23 (it's 12.1 but the number is for nightly like shown higher) and updated to 26, everything was fine
- quick install of Open Gapps, my apps and doing settings stuff, everything fine
- wild update to 30 appeared, i updated it and it was not very effective
- device rebooted, flashed update automatically, optimized apps aaaaand it got stuck on finishing boot. it was fully ok and responding cause a sound played when i plugged it to charging, it was showing touches ( i set it to show em before update), but it was stuck. So i took battery out and it started to boot, after couple of seconds screen brightness turned down as in every normal booting, boot animation slowed and lagged a few times but then continued to bootloop. Here is a list of things i tried:
- rebooting of course
- clearing cache and dalvik in twrp, then it just optimized apps again and got stuck on starting apps
- wiping data, still bootloop
- wiping everything and installing fresh CM 30
Only the last worked but i lost everything i installed etc. I made a backup of data partition but it restored only some apps ( not even gapps) and settings for some reason.
so after installing everything again i lived it for a while, but because it is a nightly a new update was posted! CM 104
- i downloaded it in cm updater as every other update (btw flashing cm 26 and then 30 from .zip gave the same result), installed it, and it worked soo...
- two days later another update appeared(cm 106), i check every update changelog and this one was big.
- happy of last successful update i just updated it but this time it didn't worked so well
everything is the same as updating 26 to 30, and here we are it got stuck on finishing boot, i took battery out, bootloop, clearing cache and dalvik, optimizing apps, got stuck on starting apps, system fully responding to the same things. i turned the phone down and started this thread.
I have a full backup of everything on another sd with cm 30 and installed apps, but because system is responding i think you guys can help me. i don't want to do a clean install every time a not working update appears. I could stay on last working version, but i'm a type of a person who wants everything updated even if won't give me anything new so staying on last working version from backup is only accepted if you guys won't have any solution or at least idea.
Big thanks for everyone that will bring anything here and probably save some time another happy cm user
EDIT: also, i can restore that backup i have and install version 104, and then figure out how to install it properly
my own idea
so, now i have restored my backup and when i have some free time i'll try to install fresh cm without gapps and update it a few versions, if it'll work problem solved. i will have to just clear cache and dalvik after every update and flash gapps. I only want to ask, if it will work, will flashing gapps with the old ones installed make any issues?
Try to re install rom after full wipe
rohitnegi44 said:
Try to re install rom after full wipe
Click to expand...
Click to collapse
i specially wrote this thread with extra simplicity, but you didn't read that it's working after full wipe, i'm trying to install update AND save my data. read before you post and try to get some easy thank points or whatever this forum has somewhere else.
FIXED IT!!
So for everyone who's looking for answer to this problem here's the fix: after cm flashes and turns off, hold VOL+ button to go to recovery instantly then wipe cache and dalvik, flash gapps, again wipe cache and dalvik reboot. For me it worked.
Hello,
It seems that my G925T has some problems with soft reboots. I don't know exactly what the problem might be, maybe you can help me troubleshot.
So I have followed up all the things a normal user might do like:
soft reset, hard reset, odin stock rom flashing, smart switch disaster recovery, disabling certain apps, going to safe mode, cleaning cache, resetting cache and dalvik, but nothing. Flashing a different custom rom, custom kernel but still problem remains.
Even after following up with all these steps, my phone still reboots unexpectedly while I use it and even i don't use it. An average is that my phone gets these unexpected reboots like everyday. Maybe 3 time a day, or maybe next day. It seems like soft reboot.
For an some addition information my phone is IMEI repair, but everything is fine, i can get updates as i am currently on the official stock ROM.
Currently I am on latest update DOJC.
What do you think it might be the problem ?
Has soft reboots to do with IMEI repair ?
Is there anyway i can troubleshot this ?
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!
Yesterday I did a dirty flash of Oxygen OS 9.0.10 on my OnePlus 5T which was initially running Oxygen OS 5.1.7 with Oreo 8.1.0. After that I flashed latest Magisk zip. After booting into system, then after the final setup of the update, I flashed franco kernel from TWRP.
Everything went smooth. All apps were functioning fine. Today in the evening, while watching YouTube, the touch stopped responding. I restarted my phone, cleared cache, dalvic, still the touch wasn't responding.
I booted in TWRP, the touchscreen wasn't responsive, therefore I used my mouse to decrypt then copied full zip of OOS 9.1.0 zip via adb from my laptop. After clearing cache, dalvic, I flashed the zip file.
After booting into system, my phone is showing the message, "phone is starting" with animated strip below it. This has been since past 45-50 minutes.
The touch is not functioning even now.
What should I do to resolve this trouble?
Has you debloat something from /system/app or priv-app? On my tablet it prevents to boot completely and stucks in this Android update loop.
Also not everytime a good idea to dirty flash to another Android major version (Oreo > Pie)!
Try a fresh install.
OxygenOS 9.0.10
No-Verity v4 (if a decrypted phone)
Boot.
Then back to TWRP
Magisk & Custom Kernel
Boot.
Restore maybe from Titanium user apps only (except Whatsapp/Threema/Telegram.. GCM/FCM notifications problems).
Flash Magisk modules.
Sent with much love and Android.
I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there).
I have found that when the touch screen stops responding, the ONLY thing that will get it working again is flashing back to stock firmware - I have been using 9.0.9 (didn't even realise .10 was out). Sometimes it doesn't work the first go, and I have to reflash again over the top (maybe even a couple of times) but I've never failed to get it working after a few goes.
Problem (on my phone at least) is that phone then hangs on the "just a sec" screen at first boot, but once the screen works again I do a clean flash of LineageOS so the setupwizard hanging is not a problem for me per se, except that the touch screen inevitably flakes out again - sometimes it takes a few days, sometimes it happens within minutes, but nothing I have tried has made it go away completely. I'd say it was a hardware problem except that reflashing the stock OOS ROM can bring it back to life... maybe it's some weird hard+firmware combination that is triggering it.
Anyway, reflash stock a few more times and see if that helps.