I'm running stock rom with xposed and frankenclark.
The last 3 Fridays (yes its true!) the phone has locked up. I reboot and the boots up without signal. There is no signal indicator. It is like the radio has been turned off. The only way I have to resolve this is to restore a back in recovery.
I really have no clue what is the cause?
Any ideas?
No one? It has just done it again!
Backed up all apps with TI booted to recovery, full back up. rebooted and not signal WTF is wrong with this phone?
Is there a secret option somewhere to toggle the phones radio?
EDIT - Could it be a FAULTY SIM?
EDIT 2 - restored a NANDROID from last week = signal again....
What modules are you running
lafester said:
What modules are you running
Click to expand...
Click to collapse
Amplify, Gravitybox and Greenify.
The very first time it done it, I installed iFont and changed the system font. I immediately thought it was xposed but it works flawlessly "most" of the time!
This is still a massive issue for me.
it has done it two time now in the last 3 days. I'm wondering if it is something to do with Gravitybox and or xposed as each time it has happened I have lost my reboot menu. I power off, power on, phone boots but with no signal indicator at all and "emergency calls only."
I rebooted to recovery restored a nandroid excluding data - this didn't work. Rebooted to recovery, restored only the nandroid data and now my phone is working.
I didn't have any of these issue prior to rooting and installing xposed.
Any one have ANY ideas at all what is causing this infuriating issue?
Try reflashing the modems
Related
Last night the nexus is charging for the whole night as usual.
But this morning the power button gets something wrong. There is no response after i press the button.
And about half an hour passed, the screen would be on and off incessantly with the power off menu.
So i have no ideas about this, did anyone meet this problem before. Help!
Thanks.
We need more information! Rooted? Custom ROM? Have you added an app recently before experiencing this problem? Have you tried to reboot the phone?
We need more information! Rooted? Custom ROM? Have you added an app recently before experiencing this problem? Have you tried to reboot the phone?
Rooted? Yes
Custom ROM? No, using the official rom.
Have you added an app recently before experiencing this problem?
Seems no, but the only one unusual is i used the headset to listen internet radio.
Have you tried to reboot the phone?
Yes, after i choose power off from the popup menu, it will reboot automatically.
and i have tried to remove my battery then put it in again, the phone still boot automatically.
And now I have already reset my phone to factory setting. The problem is still there.
I am totally lost!
I am having this same issue, it started when I flashed the Desire Rom but has since continued back to cyanogen's when I flashed back to that.
It only seems to happen when I run apps that are not google apps, that interact with the microSD card, such as twidroid or titanium backup.
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 is rooted. Twrp recovery.
I have flashed Franco, stock, matr1x. Kernels and no luck.
The phone was always disconnecting from WiFi after 4.4.3 update. But one day it stopped and I usually restart to fix and nothing. From there, I started to try different Kernels. Nothing has worked.
I resorted to factory restore. And I did it twice. Nothing.
Weird thing is when I factory restored, my pictures were still there. Yes, I'm 100% I did a factory restore.
All my apps were deleted but just my photos were there. Is this some sort of twrp safety feature or something? I'm on stock rom.
It will scan WiFi but will not connect. Some WiFi isn't even shown. My works WiFi is not even listed yet, my house is.
I'm out of my high speed data and I'm now suffering 2g speeds and nightmare battery life from the data. Can someone help me?
On 4.4.4 stock rom rooted with twrp recovery.
Have you try the WIFI Fix?
I have. But I'll try again. So far I'm now 99% sure my WiFi is defective from a hardware point. . Completely flashed fresh stock 4.4.4 and 4.3. And reflashed 4.4.4 and nothing.
Rooted Vz S5 and about a week ago, updated Kernel via Odin (OTA updates were frozen). Worked fine, seemed to have no issues. Last night, however, any connection to Wi-Fi network forces a soft reboot. Leaving Wi-Fi on but unconnected does not cause the problem, but anytime it connects to router, every 30 seconds or so, it rolls into a soft reboot. So, for now, stuck sucking data. Any ideas on what may be the problem? I noticed also some odd looking artifacts on screen when the phone goes past the splash screen to lock screen. Bit of an android noob, so any help would be greatly appreciated. Not sure if this was just a coincidence, but I had also received a notice from Google "advising" me to uninstall towel root.
Cheers
JammerJoe said:
, updated Kernel via Odin
Click to expand...
Click to collapse
Did you update the rest of the system, or just the kernel? System version must match kernel version.
Thanks for the reply. I update the system as well. However, I did not do a complete wipe at the time. So, I went back, wiped, and flashed over again to the updated system and kernel, re-installed towelroot, flashed the old kernel, and then back to updated kernel again. Pain in the rear, (as all the apps and data had to be restored), but it looks like everything is working as it should now. Kind of an odd bug as nothing else appeared to be causing problems other than connecting to Wi-Fi.
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!