I dabbled in a few custom roms when I first bought my note mainly note 7 ports. After they started having problems with each battery dying at 50%,random reboots etc.. I tried to go back to stock but when I tried to odin to QC1 it kept failing and failing so I odined to the newest update QC2 and it finally passed.I did like three factory resets and I was back on stock and happy until i started having random issues. Every time I'm in a phone call after like a few minutes go by the phone would randomly reboot itself then I would have problems where on facebook or snapchat it would freeze up and I would have to pull the battery.Then I would have issues with the phone battery not getting down to 0% and dying but dying at 50 or 25%.Also, I keep having to do the freezer trick to get my phone turned back on again. Ive tried every kernel to fix these issues QC1,QC2.PE3.PJ2,BEASTMODE ETC.. and nothing works,also im stock rooted qc2 if that helps running pj2 kernel if that helps..
Related
Hi all. Have a weird problem with my G1 that my girlfriend is using at the moment. It is rooted and I have tried various ROMs to see if I can fix the problem.
The problem I am having is that once the phone gets plugged into charge, it turns itself off and it seems to loose the ROM that has been flashed so then I have to reboot into recovery and re-flash it. It does this every time I try a different ROM so can't be related to one particular ROM.
Does anyone have any ideas why it would do this?
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
So I finally did the upgrade to 5.1.1 on my note 4 a month ago. After a day of it running fine, started to have random crashes, lagging screens, black screens, boot loop, boot into download mode, boot into software crash screens, and so on. I then installed a custom fw, which has lessened the problems, but I still crash 2-3 times a day. As well as laggy screens or boot issues. I'm wondering if it might be the cfw and the fw I got, fw was official from tmobile, customer was one from this site. Or is it a common issues and I should downgrade? I've re installed official 3 times, full wipes each time, and I've done the cfw 3-4 times as well full wipes as well Still same issue. Any help would be great.
Hello all. I am from the UK and recently purchased a sprint model phone. I wanted to remove handsfree activation. In order to do that i need a root. I rooted 5.1.1 with kernel SpaceX-Kernel-v0.1_N920P(official).tar and all seemed ok. Then i noticed that you could root marshmallow. I followed a tutorial on youtube and flashed two files through twrp no-verify-opt-encrypt.zip and SuperSU zip. I rebooted the phone and now i have a persistent problem. After around 15-30 seconds my phone shuts off and reboots itself. I have tried reflashing stock roms and the problem still persists. I have no idea if i have broken the phone as its usable until it shuts off . I went into the about phone section and it tells me the baseband and software versions are unknown aswell. Is there anyway to recover this?
Let the battery die completely and then it will work fine again afterwards
954wrecker said:
Let the battery die completely and then it will work fine again afterwards
Click to expand...
Click to collapse
This has solved the issue. Many thanks ! :laugh:
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.