Hello there all, I've been having issues with the lag on my SM-G935A.
Essentially, the first part of this story can be found here and it contains the ROM I currently have flashed on my phone. After the attempted root to begin with, my phone has become extremely laggy and I have tried nearly every method under the sun in which to fix it including a factory reset.
If anyone could give me any methods to attempt to fix this issue or stock ROMs to flash to fix it.
Thanks in advance!
Related
I tried to flash a rom and it didn't go so well due to the fact it was for Verizon S4 only and I missed that,
anyway I decided to go back to my recovered stock TW rooted Rom and everything was fine until... my WiFi stopped working, just wouldnt turn on then was asking me to reboot my device?
after a bit of searching I found out to just revert back to official stock firmware.. BUT
for some strange reason and for the first time ever, when I reflash the official stock firmware it stays as custom and is all buggy and crashes a lot. could this be because I am flashing an official stock that is less updated than my rooted TW?
someone help me cause it's really starting to aggravate me!
thanks!
When you flash the stock, do a factory reset. Any if it does not work, repeat the procedure (reset/flash/reset). But make sure you have the right stock (I suggest to take it from sammobile). I heard of up to 7 tries before success...
good luck
@JacksonPa93:
Can you check if you actually have this problem (WLAN/Bluetooth doesn't work and random crashes with reboots):
http://forum.xda-developers.com/showpost.php?p=44996177&postcount=16
fixed!
I think I've solved it by what was mentioned about factory reset>flash stock
Took me 5 times to eventually get it working..
thanks guys
Hi,
I have a big problem with LG G2 from At&t. I've bought on swappa.com for using in Trinidad. When I bought it, It was running a 4.22 stock and rooted and unlocked. Everything worked well except quick remote.
After some time new (last week) the phone started to freeze and reboot about 5 times a day. Sometimes when it was rebooting it would cycle on/off a few times before it would boot successfully.
I thought it was just a software error so I had done a factory reset and install the stock rooted 4.4.2 rom but still had the same problem. I even tried cloudystock 2.2 and had the same problem all with no additional apps installed.
Is there any way to troubleshoot the error? Is this a software or hardware problem?
It there anyway from this mess?
Thanks for every suggestion.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks
For me it was a bad motherboard. I ended up buying a tmobile board and replaced it. Everything worked fine after. Try a battery change first though. That might solve it as my battery was bad and maybe that made the motherboard go bad as well. I bought a motherboard off ebay so that's where I sourced it if you want to go down that route.
Thank you very much for your reply. I was actually wondering if it might be the battery. I will try that first. Again thank you for the reply.
So, just to preface, I am a rooting beginner. I'm not sure if the damage that has obviously been done is a result of some sort of incompatibility or a failure on my part.
In short, I'm using an N910F (Vodafone, UK), and I attempted to root my device after becoming somewhat impatient waiting for Vodafone / Samsung to pull thumbs out of relative asses and release Marshmallow.
I rooted using CF Root, version LMY47X.N910FXXS1COK2 - going onto a device running 5.1.1. After this, I installed Resurrection Remix, which ran for a small period of time.
After this, I started experiencing black screens, and failures to boot, as well as boot loops.
So, after this, I flashed stock 5.0.1 back to the phone, which wasn't 100% stable in the beginning. So, I factory reset, and flashed again, and here I am.
I am currently suffering from major hanging issues, as well as random shutdowns, which can only be solved by removing the battery, it might seem.
Model Number - N910F
Android Version - 5.1.1
Build Number - LMY47X.N910FXXS1CPC6
Knox 2.4.1
All Rom's were flashed with Odin on a Windows PC.
Thanks in advance, all.
Bread:silly:
Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?
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).