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 ?
Related
I had liquid smooth installed on this phone with cwm before and it crashed and I managed to set my phone back to the newest version but it had no keyboard and it crashed randomly and the bootloader sometimes wouldn't work properly.
Now I finally used kies to recover my phone to stock tmobile rom but the bootloader will sometimes crash during and my phone dies about 15 times a day and sometimes it's when I'm trying to open an application and other times it's simply at lockscreen or in my pocket. What can I do to fix?
Please do a factory reset. After that, observe for few days until you can make sure the issue is not repeating. Do Not Restore any apps or backups.
If it does repeat, Re-Flash Stock firmware using Kies.
Perseus71 said:
Please do a factory reset. After that, observe for few days until you can make sure the issue is not repeating. Do Not Restore any apps or backups.
If it does repeat, Re-Flash Stock firmware using Kies.
Click to expand...
Click to collapse
I tried the factory reset as well as dalvik cache wipe and within a couple hours without installing anything it was still crashing already. After a day I tried reinstalling using kies and it had less frequent crashes but they kept getting more and more frequent so now it is bad once again.
Even the bootloading screen crashes half the time after 6 or so seconds.
At first I thought maybe it's my power button that is a little funky because sometimes I press it and it double presses instead and then lightly tapping it can bring up the option to turn off phone, but I've seen my phone crash just from opening the messaging app and so I'm convinced it's some other issue.
Any other advice? I was thinking of install a custom rom from a 4.2 version of android just because 4.3 seems to be failing with both roms I've tried
Check if your power button is really flasky. Could be hardware issue based on what you have described.
Hi guys,
I'm new to this forum. My HTC Desire 300 is not rooted in anyway. Lately I've been experiencing problems with the System UI. It suddenly stopped working one day, and from then on, the notification bar never worked properly again. It comes back at random times, but even trying to pull it down will make it crash. Swiping a notification away and even just doing nothing to it will cause it to crash. I don't know why this is happening. I've tried factory reset, hard reset, battery pull, booting in safe mode, scanning for viruses, literally everything I can. Nothing works. Booting the phone up will show the error message and sometimes the error message will come up every few seconds then eventually stop and I never see it again until I restart the phone or shut it down and turn back on. Can somebody please help? I'm running 4.1.2 Jelly Bean.
I know that this in not best solution but you could try factory reset. You'll lose all of your data but you mobile should work normally.
Right now I have problem with Bluetooth and planing on doing same thing (or maybe try different ROM ).
ffroms said:
I know that this in not best solution but you could try factory reset. You'll lose all of your data but you mobile should work normally.
Right now I have problem with Bluetooth and planing on doing same thing (or maybe try different ROM ).
Click to expand...
Click to collapse
I wish I could fix it by factory reset, but I've literally done it like 5 times. Nothing works. I still get the same error. I've also tried clearing the cache for system UI app in the "all apps" list, but there is no data on the System UI app, it says 0.00B. I can't clear any cache or data. And I also notice that sometimes System UI app will run in the "running apps" list, but it is "restarting", and it seems like it fails to restart because it is always restarting.
How can I fix my ROM? My phone is not rooted and I have never modded it and installed any ROMs on it. Right now I'm just using 2 notification apps on the Play Store so that I get some sort of notification. But it's just not the same as the notification bar itself. I'm tempted to buy another phone, but when I was looking this problem up on the Internet, it seems like many phones, even the new and good ones get the same problem. So I'm really hesitating.
Did you try to do factory reset from Android or boot loader? Maybe other reset will do the trick.
ffroms said:
Did you try to do factory reset from Android or boot loader? Maybe other reset will do the trick.
Click to expand...
Click to collapse
Uhm what do you mean by bootloader? I think I've attempted to unlock my bootloader but I never actually did it. So I don't think I unlocked my bootloader. But I don't know how to factory reset by bootloader or by other ways that you are talking about. The way I do the factory reset is through my phone's system settings > Backup & reset > Reset phone. I've also tried hard reset.
I mean from default recovery not bootloader. Sorry, my bad.
I've been regularly running cyanogenmod 11 on my Bell S3 without many issues. Last going off, I believe I was running either M11 or M12 of CM11, and all was well. Then, curiosity got the best of me, and I slapped on CyanideL Lollipop beta, and while that ran pretty damn well for me for about a month, I reverted back to CM11 a few days ago due to some minor bugs and annoyances (mostly camera). Anyways, since reverting back to CM11 M12, my phone has been randomly shutting off, not rebooting, just off. It has happened while it's in my pocket not really in use, or it can happen while I'm going to check my text messages.
Thinking this was an issue maybe with M12, I updated to the latest nightly, but nope, its still the same. Some of the times that its happened in my hands, I've seen the Power Button menu pop up, and then disappear. A few seconds later, boom, off she goes. It always powers up again when I power it back on, but I would like to try to get to the bottom of what is causing this, as it is being very annoying for me.
The question is, what can I do to try and nail down this issue? When flashing back to CM11, I did the full wipe, then dalvik/cache after the flash. Is there something that happens when you go from 5.0 back to 4.4 that may cause this?
This is possibly related. I tried out an unofficial cyanogemmod 12 rom on my AT&T S3 for a while, but decided to revert due to camera not working. So I installed S3Rx ROM on the phone and had some issues. The phone would get stuck on the loading screen and never get past that. I did the standard data/factory reset, cache wipe and dalvik wipe before installing S3Rx back, but no luck. The only way I could get it to install correctly was by formatting /system, /cache, /data and /data/media in ClockworkMod recovery. But be aware that you will lose all personal data when you do that so be sure to backup.
Alright, I'll backup what I need to, and do a full wipe as you suggested. I'm pretty sure I did that when I downgraded to begin with, but no hurt in trying it again.
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
audit13 said:
You could flash back to completely stock 4.4.2 using firmware from sammobile.com, depending on the bootloader on your phone.
Click to expand...
Click to collapse
If I do go back to Stock 4.4.2, would I be able to re-root again? Its been a couple of years since I had to mess with stock, so I don't know what has changed.
I've tried a few different things here, completely wiping everything, installing a 4.4.4 kernel, installing CM11 from scratch, restoring from TWRP, etc etc. Still having the issue.
Last thing I'll try before going to stock is to try going back to lollipop.
Update: I'm starting to think that this is just a coincidental hardware issue. It seems to have something to do with my power button, perhaps there's something stuck in it that's cause the button to be pressed. Right before it shuts off, the power menu pops up for a split second once or twice, then the phone becomes unresponsive for a second, then its off. Certainly sounds hardware related. Just attempted lollipop again, and same result.
I think you are correct in your assessment. Open up the phone and see if you can find anything that looks odd.
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.
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!