Database Users

[Q] Memory leak or something else?

So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.

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

Phone Semi-BrickeD?

Main:
Ok, so I was waiting until i got a new phone so i can root my g2, well never happened as my g2 decided to randomly freeze up and restart and get stuck in boot loops either on the LG logo, or freeze on the T-mobile splashscreen and restart infinately. So now i got a new phone and i want to root the old one, But first up I need to figure out what is causing the random boot loops, freezing, and shut offs. It's a T-Mobile variant
ALSO: IT WAS NEVER ROOTED, So it's not a root related issue.
NOTES:
plugging it in help increase chances of escaping loop
It doesn't require a plug in to fix but it helps.
Reboot/Glitching occur when phone is in use and out of use.
Phone works normally otherwise but suffers these glitches
Phone has be factory reset twice
Phone has no external damage
Possible Internal:
Broken L. speaker due to rain
Maybe water damage from steam (phone was on counter as i showered a few times)
possible battery issue
Maybe a bit of drop damage as i did drop it a bit, but it was in a tech21 impactology case, and it remains not cracked

I have a similar issue. The phone will loop the LG logo, but only sometimes--at other times it will poop android's boot animation until it decides it wants to boot normally.
It happens in every ROM(ota or cuatom) even after flashing the stock .tot file about 4 times, so it's clearly a hardware defect for me & probably you too. I read the logs & saw rtc blah blah time will be lost on reboot & other errors. During normal use it randomly freezes prior to rebooting itself, though it reboots even while idle for long periods.
Unfortunately I don't have a solution for your problem besides restoring the stock image.
http://forum.xda-developers.com/showthread.php?t=2432476
After that you can trade the phone in, sell it, or send it to LG.
Powered By "Yeeart!"

So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops

pvt900 said:
So If i reflash to STOCK will it work for a short time normally and in x weeks/months resort to it's retardism of loops
Click to expand...
Click to collapse
It fixed my problem temporarily, but not too long afterwards all the issues came crawling back. For this reason I suggested ditching the phone completely unless you really want LG to examine it.
Powered By "Yeeart!"

Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff

pvt900 said:
Since i own 2 G2's is it worth my time re flashing to stock and then rooting the phone, cause i plan to run my sim carded phone as my normaly device and my root would handle experiment tech uses and hacked apps/superuser apps and such stuff
Click to expand...
Click to collapse
I've heard of the random reboot issue. Fixes have been created and detailed. Please give me the following info, and I can help you resolve the problem:
Current Baseband Version
Current Bootstack / Modem
Root status in recovery
Current ROM and Carrier
Current Recovery

I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?

jkeats20 said:
I'm having the exact same issue with my D800. I was rooted and had run a couple of ROMs but returned to stock right after I started experiencing the reboots. Unfortunately, the return to unrooted stock - and upgrade to lollipop - didn't fix the random reboot issue.
I've noticed that when my phone shuts off I typically need to hold down the power button at least a min to get it back up and running. And when I get it back up and running the battery stats show a substantial drop in battery - between 5-10%. I took it to a local shop and they said it was a bad motherboard. I've read some threads about shorting some pins on the MB and then reinstalling pieces of the boot image piece by piece and then use the LG Flash tool to reinstall the OS.
I haven't tried it out yet but is this the fix you have in mind @dmezh?
Click to expand...
Click to collapse
What I had in mind is a multi-step solution that didn't involve opening the device - we can try it, and if it doesn't work then I guess you should try it. I've never actually heard of the pin-shorting, can you post links to the threads?
Anyways, this is roughly what we can try (I can give you all the files you need if you give the info from my first post):
1. Get to fastboot
2. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things
3. Reboot to download mode
4. Reinstall the kitkat TOT
5. Install custom recovery and wipe all partitions
6. Kitkat TOT again
7. Factory reset (yes, even though this is a fresh install)
8. Reflash laf, recovery, boot, modem, sbl1, and a bunch of other things AGAIN
I've tried these steps before on a friend's VS980 and they seemed to fix the problem. I know that this seems overly complex, but it has been documented in other threads. Provide the info, I'll get the files, and let's get started.

I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

jkeats20 said:
I have all of the D800 files I need to restore the KitKat partitions downloaded here:https://www.youtube.com/watch?v=_d5b_osUTug but am not sure how to get the phone into a mode that I can flash the .img files I have into the right locations. I follow what you are proposing I do - just not sure how to get there.
Current Baseband Version: M8974A-AAAANAZN-1.0.19.128
Current Bootstack / Modem - not sure
Root status in recovery: not rooted stock lollipop
Current ROM and Carrier: 5.0.2 AT&T
Current Recovery: Stock Recovery
Here's the link to the hardware shorting pins post: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.

dmezh said:
The pin-shorting manually puts the device into a Qualcomm fallback mode, but this is not necessary if we can just get it to go to fastboot (the images can be flashed from there as well). The only time I've been in fastboot on the G2 was when I flashed a VS980 recovery on an LS980 with AutoRec. Fastboot is triggered if any of a set of five partitions are corrupted.... so we may need to corrupt a partition. I'll try this on one of my devices first before I instruct you to do it.
Click to expand...
Click to collapse
Did you have a chance to try this out? It sounds like a good way to get the phone into fastboot but am reluctant to try without knowing if it's going to work. Thanks for your suggestions so far - and no rush on getting back I have a working backup phone at the moment.

G2 hardware issues, possibly related to flashing?

My G2 has been acting really funky lately, hanging on boot and not being able to "hold" recovery flashes. I'll start from the beginning of my little story.
On Saturday, I wanted to do a nandroid backup from TWRP (not sure which version, an older one but not terribly old). It failed several times. I went back into the OS (CM 12.1) and backed up all apps and app data to an OTG USB via Titanium Backup. This was successful. I tried to go back into TWRP a second time. Nothing. Recovery is not even there, I get a security error from what I believe is fastboot. I went back to CM and tried to re-flash TWRP. Now I get a security error on the LG screen. Nothing would boot, no recovery mode, I did have download mode although I had no PC with me so I didn't know this at the time. I was away last weekend so I had to go without a phone for a day... which was actually... kind of pleasent. Don't ask me why I carried two 32GB USBs and an OTG adapter on my keychain but no laptop, because I have no idea why I would do this, lol.
Came home Sunday afternoon and decided to nuke the whole phone with a TOT flash. Since I always wanted to try CloudyG2 since we all know AOSP-based ROMs don't do the camera justice, I went ahead and TOT flashed, re-rooted, re-AutoRec, etc. Everything worked wonderfully; I did a full wipe in TWRP, flashed in Cloudy, then the KK radio, then Xposed. Played around with things like XCam and a few Xposed modules. Everything was working awesome, so I did my restore in Titanium. Took a few hours, but Titanium says everything went fine (sans for a few CM apps which did not restore by design I guess). I checked out a few apps, all my data is there, wonderful. Titanium told me to restart so after poking around a bit, I went for the restart. Hang on boot. For several hours. Tried to go to recovery, fastboot security error. Seems it can't "hold" recovery or something else that I'm flashing?
Clearly I am doing something incorrect here with flashing and all that, but I can't figure out what. I'm not new to flashing and modding, and I've flashed regular CM updates and other goodies onto this G2 for quite a while with no issues. I'm going through the same steps I would normally with CM, and I've had plenty of success with that. Any ideas what I am doing wrong here?

Had same issue and know I hard bricked it trying to get it fixed ... Off to a different phone I guess .. Not sure why it wouldn't hold a recovery either after a few hours ... I gave up .. Good luck
Sent from my SCH-I535 using XDA Premium 4 mobile app

[Q] sgh 1337 UN stuck on Samsung splash screen (safe strap broken)

So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.

Ghujii said:
So, I have gotten myself in a bit of a pickle I however think I can get out of it by sideloading using EXT. SD, Im not sure what to flash to solve the dillemma however. So this is the situation. I have a (had) a rooted Galaxy s4 (sgh-i337 ucufnc1) with 4.4.2 android. It had safestrap installed and back ups of everything else in sd card and other locations just in case. The phone was acting buggy, so I formatted the phone with safestrap, the problem persisted, ill get into the issue a bit further down. So I booted back into safestrap, and did a complete wipe, however my sd card must've bumped out, because it didnt delete any media files or so it said, and then after the wipe it crashed. and refuses to boot into safestrap or even past the splash logo. I can get into download mode, but usb debugging isnt on anymore since i wiped it, I can get into the other mode as well ( cant for the life of me remember the name of it atm although i use it frequently) with some luck. I also happen to have all .md5 files from a backup i did about 4 months ago in tact, I cannot for the life of me get them to convert properly to apply them to the phone without safestrap however, if anyone has any insight to this please let me know also.
I can/will list any other information I have if anyone needs it, and if anyone can help it would safe a life!
The reason i reformatted it to begin with, was because media would stall, and when i plugged in the audio jack it'd freeze the entire app using it, then the whole phone would freeze. I believe it was due to lucky patcher but im unsure. The issue began when I altered the auto update file, and even after i rectified it, it persisted. At this time i have a phone soft bricked because it didnt delete all the media files and I assume something bugged onto the kernel image but Im not sure. If I can simply try to restore it to stock kernel then im fine with that.
Click to expand...
Click to collapse
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.

Ghujii said:
UPDATE: I resolved the issue, by rooting, safestrapping, ripping the image files, from another galaxy s4 with alike descriptions. then i managed to side load it, then it booted properly, i then reformatted it completely back to 100% factory everything. Now my original problem persists, and i cant help feel that google services is causing it. (examnples of issues" proccess.gapps has stopped. anotrher process error code. phone calls can be made, but not recieved as it seems the server is too busy to n otice it, massive battery drain, audio takes several seconds to play, while video continues to play fine, audiojack is mostly unresponsive, phone calls that are made cannot recieve or send audio during call session, phone may freeze at unlock screen, or any time during operation, may even reboot from process overloading" now keep in mind. i removed every system file and app that the natural reformat will allow. so nothing applied by the user is on the phone, other than natural factory applications. Im digging a bit into the phone as i can but its a slow process whenit starts freezing. if anyone has any idea of what can be causing this, or how to fix this please inform me lol.
Click to expand...
Click to collapse
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.

I will attempt to do this, since nothing since has work. I am about to get a new logic board for the system in the next 2 weeks. Towel root DOES typically work on this system, however the last time I attmpted it it failed to work outright. Im not sure what has changed with the device, but i believe reflashing stock is the best method. The phone now, will boot up, then skip the lock screen and go straight to the home screen, which is black with no pull down bar, or with no signal and there is no way to rectify it. Even if there were, it boots back down and launches back up and becomes locked at the ATT logo.
After a fair bit of messing with it, and recovery mode it will sometimes boot normally where it tells me that processes has failed and askes me to cancel the ''app''. This is the best option to update the phone and attempt root, but getting it here is so difficult because it reboots itself and the mode is rare to acquire. This problem either is due to the kernel, or the rom i believe. I also am to believe the powercell may have some issue, as i replaced the battery a few weeks back and it worked fine for about 1 week.
Booting into safemode doesnt work either as it skips over the lock screen straight to the home screen. Outsidce of replacing the logic board, or attempting another flash im at the end of the short rope i was already on in terms of options.

sway8966 said:
The best solution must be installing the stock firmware via odin. Since you are on NC1 , You can installed the stock NB1.
Here is guide explaining you using odin, installing NB1, root with towel root, updated NC1, install the safestrap. The guide was not specifically written for that but you can find those steps in the guide.
Click to expand...
Click to collapse
UPDATE: I found therein two methods to flashback to stock. I did so, then proceeded to attempt to flash from nb1 to nj4. Progress stopped there when it flung an error 7 at me. So this means either something in my phone is corrupted or the file i downloaded from the above mentioned forum is corrupted. I also attempted flashfire, but seen as it STILL crashes at random due to process errors thats almost impossible to attempt.

[Help!] N910T3 Strange Crashing/Bootloop - Crashes even while in Recovery

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).