I just updated my g4, the firmware is ZVF didn't notice any real changes.
MY G4 is stuck on boot looping after this and I am not finding a way out.
tried factory reset and even flashing stock firmware is not working
anishkhadgi4xda said:
tried factory reset and even flashing stock firmware is not working
Click to expand...
Click to collapse
Same thing happened to mine a few months ago, it overheated so I sent it in for repair. Took two weeks to get it back
so how was the problem solved?
what solved the problem? Which Android Version are you in now? Did they fix software or hardware?
LG fixed it, at the time I was on zve. They replaced the motherboard with a new one
Related
I got mine from uk handtec and been use four days without any problem
but today it reboot two times alreday without any touch.
did anyone have that kind of iusse any suggestion?
I haven't root my phone and I updated to 534 firmware
paullu said:
I got mine from uk handtec and been use four days without any problem
but today it reboot two times alreday without any touch.
did anyone have that kind of iusse any suggestion?
I haven't root my phone and I updated to 534 firmware
Click to expand...
Click to collapse
you might need to do a factory reset then update the firmware again, I think the update to 534 didn't go too well... also happened to my samsung phones preiously after updating to latest firmware...
Morlock O said:
you might need to do a factory reset then update the firmware again, I think the update to 534 didn't go too well... also happened to my samsung phones preiously after updating to latest firmware...
Click to expand...
Click to collapse
I was just about to post about the same issue. Twice now when driving I have noticed that the phone suddenly reboots. It's sitting in a passive car holder (no power, NFC, bluetooth etc). But it's just in my line of sight so I quickly notice when it suddenly boots.
I have no idea if it does this the rest of the day or not as well. But this is not a good sign.
if resetting to factory setting then re-updating the firmware does not work, try to re-flash the stock firmware using FTF files...
http://forum.xda-developers.com/showthread.php?t=2459365
http://forum.xda-developers.com/showthread.php?t=2464389
this usually happens when there is some conflict with the firmware.. very common issue with all android phones...
I'd flash it with flashtool.
I did a "reflash" of the latest firmware using the PC companion software that came with the phone. Will report back in it helped or not.
I did a factory reset.hope will solve it
Guys, I'm facing a serious problem with my moto g2 phone. It's gonna about 10th month I'm using it.
Presently the device's screen is not responding maximum times.
I already tried almost everything from my side to solve it. I did factory reset, Downgrade to KITKAT & finally locked bootloader, installed Official Stock ROM.
But the same problem is still remain.
Please suggest guys....
Hey all. I have an unrooted, stock N4 that appears to be "overloaded" and randomly lags and reboots. It's been happening for a week
I have tried the following solutions
- Factory reset
- PopRocks ROM
- 5.1.1 Stock ROM
- SD Card reformatting
- SD Card removal
- Clearing cache
I am at a loss of what it could possibly be. I am running the latest firmware for the phone now. It seems to just reboot doing the simplest things. Even scrolling through XDA on chrome was laggy as hell. I've tried searching the internet for another solution but to no avail. The only thing I haven't tried is KitKat but it doesn't make sense since I was running Lollipop with no problems until a week ago.
I have the exact same issues on my phone, completely stock out of the box. T-Mobile is sending a warranty replacement next week. Hopefully it won't happen with the new device
kitchencop said:
I have the exact same issues on my phone, completely stock out of the box. T-Mobile is sending a warranty replacement next week. Hopefully it won't happen with the new device
Click to expand...
Click to collapse
I've had this phone for about 7 months now and I got it on Ebay so I don't think there's any chance of me getting a new one from tmobile. Seems like hardware failure to me.
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:
Hi, I have a droid turbo that is driving me crazy, when the phone took the update to marshamallow, after a couple of weeks the wifi and signal had lost, sometimes when I restarted it or doing factory reset the networks worked, but always going to the same situation. I reflashed the stock 6.0.1 with rsd lite, it worked, but for a couple of days so I thought it was the motherboard, then I bought another one ($40 dollars) from a cracked screen turbo. That motherboard had 5.1.1 so it worked fine for a couple of days until the OTA came again and installed, it worked fine but a few days later the phone showed the same problems. I dont know what to do, I cant downgrade because the locked bootloader ( and sunshine is to expensive for me $25 dollars is to much in Mexico) and is the second motherboard !!! what is happening??? Please help me
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Einheit-101 said:
U should have sunshined your device and installed a custom Rom/ modified stock with new kernel, because now being unrooted with a half-bricked device means there is pretty much nothing that can be done to fix that software issue
Click to expand...
Click to collapse
but why this error is just happening to me? I dont find another users with 6.0.1 having the same issue, I repeat, I have 2 motherboards with the same problems that's to weird :/
I dont know man. Idk what you did or did not.