Related
Hey Guys, I have been beating my head against a brick wall trying to fix my phone.
Yesterday I was on a call with someone and suddenly I lost service (not uncommon for where I was since I have weak service there), but this time the phone was frozen. The dialer screen was on but was frozen. My phone would not react to anything. So naturally I pulled the battery and rebooted the phone. The phone started up as normally it would but then after 5 minutes of the phone running it froze again. During those five minutes I never received any cell signal.
The most recent "work" I had done on my phone was change the kernel to the AK Kernel on the guide here. This was done 3 days before anything started happening. I tried a new kernel because ever since upgrading to Paranoid 3.0 my phone was acting slow and occasionally I would get a screen of death typically about once a day. The 3 days that I had the new kernel, everything was working great (phone was faster, responsive and no SOD).
I tried restoring a nandroid before upgrading the kernel and it made no difference. Ever since the first time my phone down freezes after 3-5 mins after booting up. Nothing that I have tried has fixed the issue.
I have done a clean install, tried locking and re-rooting, tried a different kernel. All to no avail. Please help I am thinking there is something seriously wrong and may need to take it back to verizon. I am trying to restore my device to stock but am unable to do so. I have been using this guide: Restore to Stock. Any suggestions to make it "clean" enough to get verizon to replace it?
I'm going through withdrawals, please help!
Could not fix it, so I contacted tech support and explained everything that I did to try to fix and they just sent me a warranty replacement. I hope that it was a device error and not something that was caused by other ROMs or Kernels.
I just had a weird problem start the other day. I was at work and my phone constantly rebooted throughout the night. When I left for the weekend it didn't do it at all again until I was driving past where I work. And now at work again it is rebooting over and over. My phone is rooted and I am using miui rom.
jah8551 said:
I just had a weird problem start the other day. I was at work and my phone constantly rebooted throughout the night. When I left for the weekend it didn't do it at all again until I was driving past where I work. And now at work again it is rebooting over and over. My phone is rooted and I am using miui rom.
Click to expand...
Click to collapse
This has been happening to me since switching to CM11. Every day on my commute to and from work the phone reboots when I drive through a particular area. I spent two hours in that area yesterday and my phone boot looped the entire time.
I am having the exact same problem. I thought I was going crazy, but I can literally repeat the reboots by walking to certain areas in my apartment building and on my commute to work, however not a single reboot the whole day at the office. SO STRANGE!
I'm glad I'm not the only one, I don't even know where to start, I haven't changed or downloaded anything on my phone in months.
Sent from my SPH-L710 using Tapatalk 4
I have done multiple roms, changed network variables and even odin'd back to stock...still happening.
I temporarily loaded stock and updated PRL and profile, yet the problem is still occurring. Logcat is useless because it rotates at startup, unless someone is aware of another way to see old logs?
I posted this on the CM thread, but figured it might help here as well. I connected my laptop on the drive home and captured logcat right up until the phone started rebooting. Maybe someone can make sense of this. Thanks in advance.
Wow, I thought I was going crazy! Same thing is happening to me as well.
Any updates? I'm still having this
Sent from my SPH-L710 using xda app-developers app
This is familiar to the problem I've been having on my phone running MOAR. The battery died while I was at my house and ever since I get constant reboots if I run DKP kernel, I flash the stock kernel bundled in the MOAR ROM and the reboots stop but I get not signal within a half mile or so radius of my house. I flashed back the stock ROM and modems and radios of all versions but nothing helps. I got the MSL code and did a reset via the ##786# menu but that didn't help. Sprint said it's probably a tower upgrade that's going on but other Sprint phones get signal/reception without any problem and they won't replace the phone because of a small crack on the screen.
maxpower12 said:
This is familiar to the problem I've been having on my phone running MOAR. The battery died while I was at my house and ever since I get constant reboots if I run DKP kernel, I flash the stock kernel bundled in the MOAR ROM and the reboots stop but I get not signal within a half mile or so radius of my house. I flashed back the stock ROM and modems and radios of all versions but nothing helps. I got the MSL code and did a reset via the ##786# menu but that didn't help. Sprint said it's probably a tower upgrade that's going on but other Sprint phones get signal/reception without any problem and they won't replace the phone because of a small crack on the screen.
Click to expand...
Click to collapse
Do you mean ##72786# ? Did you try updating your Modem to MK3 ? You can find it HERE.
prboy1969 said:
Do you mean ##72786# ? Did you try updating your Modem to MK3 ? You can find it HERE.
Click to expand...
Click to collapse
I've done both resets. There's another option in ##786# that wipes everything and reinstalls the ROM and reactivates the phone. I've tried the MK3 modem with no luck. Last night I was able to get the phone into LTE only mode in the ##3282# menu after several tries and the connection was stable, in CDMA only mode it disconnects constantly and reboots occasionally, same with CDMA/LTE mode. The problem with LTE only mode is that LTE is not available everywhere yet.
jah8551 said:
I just had a weird problem start the other day. I was at work and my phone constantly rebooted throughout the night. When I left for the weekend it didn't do it at all again until I was driving past where I work. And now at work again it is rebooting over and over. My phone is rooted and I am using miui rom.
Click to expand...
Click to collapse
Having the same issue since last week. I installed CM 10.2 and accidentally triggered the knox warranty, so can't even take it back to Sprint now. Afraid to go back to stock, as I've read that I may brick my phone. Stuck with constant reboot loop at home (unless I turn airplane mode). Has anyone found a fix? Please help... about to go to t-mobile and switch providers!
PS: Does anyone know how I can apply the ##72786# in CM 10.2? Is it possible?
yodaddyleo said:
Having the same issue since last week. I installed CM 10.2 and accidentally triggered the knox warranty, so can't even take it back to Sprint now. Afraid to go back to stock, as I've read that I may brick my phone. Stuck with constant reboot loop at home (unless I turn airplane mode). Has anyone found a fix? Please help... about to go to t-mobile and switch providers!
PS: Does anyone know how I can apply the ##72786# in CM 10.2? Is it possible?
Click to expand...
Click to collapse
I don't think dialer codes work on CM. I got the reboot loops to stop by flashing a different kernel but by doing this the phone has a very hard time keeping a connection to the tower. I noticed last night that the phone seems to have a problem connecting to LTE or eHRPD even if it's in CDMA only mode but seems fine if I go into ##DATA# and using my MSL code I change the network to EVDO only mode.
I'm also experiencing similar characteristics of an on going reboot. My phone has been doing this for the past two days, I've reverted to the stock ROM, updated my PRL and yet I'm in a constant reboot. I went to Sprint and they offered to re-install the stock ROM for a fee ($75), I laughed while the friendly consultant called me an idiot for rooting my device. Anyhow, I'm all ears for a solution and in hope to get this phone working again. Last resort, I may just bite the bullet and buy an S4...
Cheers!
EDIT: I was last using the Slim Bean 4.2 build
Interesting thing, my sister and brother each have an S3 with Sprint. They came to visit last night and my sister's phone goes into a reboot loop but my brother's phone is fine. They're both running stock 4.3 and unrooted. The problem seems to be with certain S3s not liking certain towers.
I'm having a very similar problem. I have a i9305 which keeps restarting on it's own. Seems completely random, today it has done it twice, yesterday it did it about 5 times. Sometimes I'm using it when it happens and sometimes it's just sitting on my desk. Also if the battery is below about 40% it will often go in to a boot loop when it restarts. It was doing it when stock, rooted it and flashed a couple different roms, still did it, back to stock now and it's continuing to restart randomly.
There's a lot of people having this issue if you do a google search. THere does seem to be a power button issue with a lot of S3's but mine doesn't have any of the other power button symptoms (such as turning on as soon as you insert the battery).
I'm reluctant to return the phone as I can't be arsed dealing with the warranty process and I rooted it
Similar problem on stock rooted 4.3 row with kt kernel. reboots seem to happen at my house and only in lte/cdma mode. At the same time I notice constant reception issues. In cdmal no problems at all.
Nice, I just set mine to CDMA instead of lte/cdma and no more problems, no more 4g but I don't care as long as my phone works
Sent from my SPH-L710 using Tapatalk 4
jah8551 said:
Nice, I just set mine to CDMA instead of lte/cdma and no more problems, no more 4g but I don't care as long as my phone works
Sent from my SPH-L710 using Tapatalk 4
Click to expand...
Click to collapse
If you get your MSL code you can go into ##DATA# and edit the "HDR/1X Selection" under "Others" and force the phone to be LTE only. It might take a several tries before the selection actually sticks and signal sometimes goes away for me momentarily. There's also the problem that LTE isn't available everywhere yet so when I leave my house I select LTE/CDMA in the regular networks connections menu and let the phone reboot.
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart
So yesterday I rooted my Sprint Note 4 and everything went well. I then went and got TWRP as well and when done, I got CM12.2 with the appropriate G Apps and flashed both correctly as well. When CM12.2 booted up, it was a little glitchy at first but then it smoothed out and was an amazing experience until this morning. I loved this, but I didnt know it would do this too me. So I woke up this morning and the service wasnt working. It said sprint, but nothing was happening, couldnt recieve texts or anything. Then it just showed an X next to my bars with zero bars lit up, of course. I had zero service. So I then went into twrp, factory wiped and restored a backup I had done before I flashed all this. STILL, on boot up and setup, a big red x next to my zero service bars! Can someone please help me asap? Would removing the root and completely factory reseting the phone from a computer remove it? (Going to do it anyway). HELP?
As the title says I am currently only getting LTE signal on initial boot and it shows its registered to tmobile on the top left but after about a minute I get no signal at all just an X on where the signal bar would be. I checked the signal on boot and it is -119dm 21asu then drops to -113dm and 0asu.
Let me start with all I did since last night. I have been planing on upgrading from kitkat to lolipop and finally started taking steps to do that last night. I first used Kies 3 to backup my data then decided maybe its best to do a full nandroid as well. I installed TWRP and did a full backup, played with my phone a bit then wound up falling asleep without finishing. This morning I knocked the phone off my dresser with the charger still attached and nothing appeared wrong with it. It wasn't until I was driving to work trying to load up spotify that I noticed I was getting no signal. I rebooted when I got to work but did not watch the whole boot up process and only saw that I was still getting no signal. On my lunch break I decided that maybe I screwed something up when I flashed TWRP with odin 3.10 and followed this guide to get started with the upgrade (http://forum.xda-developers.com/not...icial-lollipop-n900tuvufob5-t-mobile-t3046295). Note that I already had mobile odin installed on my phone. When I finished up and everything looks good but I still dont have signal. I noticed that the baseband was still showing up as the kitkat baseband so I flashed the lolipop modem with odin and after boot saw that it did indeed upgrade the baseband but still no signal.
I should also mention a week ago I replaced the usb3.0 port on my phone because the old one was a bit loose when plugged in. I had not had any issues with it until I noticed no signal this morning and am at a loss as to what my problem could be. I did remove the back and check the antenna connections once I got home but it does not fix the issue. Wifi still works and wifi calling appears to work as well. Issue seems to be with just the cellular part. Hoping some one here can pick up on what I possibly messed up.
Was a software issue
I got it working. Looks like there was a software conflict with an app or apps possibly because I did a factory reset and re flashed in Odin using this guide (http://forum.xda-developers.com/showthread.php?t=2672393) and my cellular signal is back to normal. I had to start fresh but at least I have a usable phone now. Hope this helps anyone in a similar situation.