Hey guys,
i have been using Ivan Mehler's cm 5.1 rom and since early this year i am on his 6.0 rom and everything was fine until mid june. Since than i have the 'sleep of death' syndrom (phone won't wake up from deep sleep until hard reset). I can keep it from freezing when i stop it from going into deep sleep via apps like 'Safecharge' or having muted music playing in the background. It could be a hardware issue. I have dropped it twice pretty hard, once in 2014 and a second time 2 weeks before the sods started. Else it runs without issues. I reverted to a backup, installed another cm 6.0 rom and reverted back to stock, to no avail.
First, how do i best diagnose whats causing this?
And secondly, are there any leftovers from older roms that could interfere when i install a new rom via twrp and doing a complete wipe including reformatting the file system etc? What i like to know is whether when installing the latest stock rom via odin, does that mean that every bit on every storage/memory of the phone is being completely wiped and newly written, or are there some basic parts of android/linux that would not be touched?
Related
Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.
Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
Hi all!
First of all thanks for your work..it's awesome!!thanks to you i enjoyed my s plus until some days ago it has broken..very sad day
However i decided to move on with a more modern cel, so i decided for a s4 mini.
But since the beginning i've had lot of problems..
My phone after an original update from samsung started to freeze and reboot..more and more often..i read it could be an issue with original update so i decided to mod my phone since i've had great improvements with my old s plus..
first i installed cm11 but the phone keep rebooting and rebooting ..so i installed cm12 with android l..but the problem is still here!!
the more my phone became hot the more it reboot..it's unusable and i don't know what to do..i'm also begin to doubt it's a hw problem
my warranty is gone with all this mods..so what to do? any others has this kind of problem?
thanks if yo want to answer
People encountering this should perform a factory reset and wipe everything from the phone.
Then, perform a clean install of whichever rom you wish to use, without any additional apps.
I recently encountered an issue with Apex Launcher and a recent update. Android keep crashing and soft rebooting often.. only after a few days did I realise the launcher was the issue. Since I uninstalled the app the phone hasnt restarted once!
Mine restarts after i turn on Mobile Data + GPS for navigation..
It works for a minute and restarts.
I don't know where the problem is either. I tried to flash cm10, 11.. stock 4.2 / 4.4 and nothing seems to get me rid of the problem
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
I'm absolutely losing my mind please help
A little story time, skip to the end for my question;
So, how to start - One day I unlocked my bootloader, went for some android 11 rom and all was fine. Then android 12 was released and I downloaded the crdroid 12 rom, where I was experiencing some battery drain issues. So I downloaded pixel experience rom. The Bluetooth died because of this rom's cursed source code. I flashed the latest miui fastboot rom and the Bluetooth issue still persisted (remember this for later - not all the drivers flash with the Rom). I fixed the Bluetooth issue by switching several miui roms, also made a guide if you're interested. That fixed the Bluetooth issue and I went for pixel plus ui rom. It was a bit laggy, so I switched to the shiny new Evolution X rom. It was amazing, so much stuff co customize, etc. Well, i experienced another battery drain issues, so I just went for the stock miui with magisk pixelify module. Im pretty fine with this rom, and I thought the problems are gone, because it stock and everything should be fine. Well no. The battery drain issue persists. I was wondering what even is happening, so I opened battery settings. That said that the top apps wasting my battery is screen, Google services and android system. I downloaded a CPU usage stats app, which showed me that the cpu usage is at 99% (I think it's correct as the phone is overheating). The app with most cpu usage was using only 1%. I don't know if this is a firmware bug or whatever, but I think some rom broke it and the latest stock miui didn't overwrite that driver, as written above with the Bluetooth issue.
So, how can I make my phone be as it was released from xiaomi with all the drivers to actually use the hardware correctly?
Thanks in advance for any replies, I'm seriously going to throw my phone out of the window
Also the way how I install the stock Rom is by downloading the latest fastboot rom, extracting it and executing ./flash_all.sh file.
SOLVED! My problem was because of my credit card. I have my cc in the phone case. The cpu was going insane because it was constantly detecting the card and loading info from it. Literally turning off NFC fixed this whole issue. Bruh.