Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
smarikoe said:
Hi guys,
My f400l has been experiencing issues for a while now. One morning, I woke up to find an unresponsive device. Took out battery and turned it on again to find that the device had partially reset itself (ie. going back to stock launcher and layout, missing apps). Device was still rooted so I tried to restore apps and settings via titanium backup. However, phone kept freezing throughout restore process.
Next, I decided to flash back to stock. This is when i noticed that wifi would remain at 'wifi turning on' but never actually turn on. Additionally, bluetooth could not be turned on. I then upgraded to lollipop via normal firmware update from lg software on my pc. Phone then would freeze after every 2 mins.
After trialing many rooms, I am now on cloudyg3 2.1 but wifi/bluetooth are still not working and phone still freezes occasionally (usually at the beginning of the day).
Really at a loss here, can anyone suggest what seems to be happening and what I can do about it?
Thanks everyone!
Click to expand...
Click to collapse
reflash the modem and kernel and you should be set
suljo94 said:
reflash the modem and kernel and you should be set
Click to expand...
Click to collapse
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
smarikoe said:
sounds simple enough.
Would these be the right links?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-rin-kernel-1-0-t2847581
http://forum.xda-developers.com/showthread.php?t=2784501
If flashing the modem, wouldn't I need to first revert back to stock kitkat?
Click to expand...
Click to collapse
flash the correct one
https://www.androidfilehost.com/?w=files&flid=22640
suljo94 said:
flash the correct one
Click to expand...
Click to collapse
Argh! So i tried flashing and upon reboot, phone came up with a security error. Currently reverting back to stock via download mode. I couldn't get back into recovery. Did I do something wrong? Thanks for the help so far tho!
EDIT: ahhh just realized i flashed a kitkat kernel, woops! Will see how things pan out for now
So i went back to stock and flashed a kernel but that didn't seem to help. Can't seem to find a zip file for kitkat baseband so I'm a bit lost as to how to flash a modem.
One thing I also noticed is that fact that i cannot access recovery via hardware buttons? I use power and volume down but the combo doesn't work. It just boots normally?
Hey guys. After rooting it, I messed up with xposed and my phone started rebooting. It was usable, but whenever I would open any audio file, it would reboot. So I tried wiping my data in recovery and now I can't leave the starting setup! It always reboots when I'm digiting my wifi password. Does anyone know how to fix this? Got my phone yesterday.
Update: Got it past the starting setup, and can use it. but it's still rebooting all the time.
Figured the problem was with the asus keyboard. Backed up my swiftkey and it works just fine. but still can't hear any music and who knows what else
Ksagrande said:
Hey guys. After rooting it, I messed up with xposed and my phone started rebooting. It was usable, but whenever I would open any audio file, it would reboot. So I tried wiping my data in recovery and now I can't leave the starting setup! It always reboots when I'm digiting my wifi password. Does anyone know how to fix this? Got my phone yesterday.
Update: Got it past the starting setup, and can use it. but it's still rebooting all the time.
Figured the problem was with the asus keyboard. Backed up my swiftkey and it works just fine. but still can't hear any music and who knows what else
Click to expand...
Click to collapse
Be aware that there are xposed modules that either don't work or could cause issues. If I was you I'd stop all the modules, see if it has the problem on reboot and if it doesn't, try them one at a time.
If that doesn't work you might need to do a factory reset to undo the bad thing you did...
ultramag69 said:
Be aware that there are xposed modules that either don't work or could cause issues. If I was you I'd stop all the modules, see if it has the problem on reboot and if it doesn't, try them one at a time.
If that doesn't work you might need to do a factory reset to undo the bad thing you did...
Click to expand...
Click to collapse
Yep. I knew about the modules. I was just dumb lol. All modules are off. Also already did a factory reset but it didn't work. It's not rebooting anymore, since um using SwiftKey, but I just don't have any sound. And it's like the sound can't be processed. When opening a song on poweramp it keeps going to other tracks until I close it, and the other players just get stuck. All the system sounds are also not working.
Just found out the calls work. Only in the loudspeaker though. Funny
flash stock ROM over and I don't see how that could not solve all your problems.
Fed4Lyfe said:
flash stock ROM over and I don't see how that could not solve all your problems.
Click to expand...
Click to collapse
Just did it and it solved everything. Thank you!
Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]
frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.
So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.
No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.
So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
time_lord2004 said:
I did an online chat with HTC and they led me thru the process of going into the Testing screen (via *#*#46...) and I tried the 'turn on radio' button. No luck. They suggested I return the phone for repair, but as it's 1.5 years old, out of warranty, it probably isn't worth it
I had one last idea. Although I've tried factory resets a couple of times, I have not tried uploading a different ROM. If I do put a different ROM on the phone, does the bootloader reset any of the hardware (i.e cellular radio)?
Click to expand...
Click to collapse
Simply installing a custom ROM will not affect the radio partition.
Why not try a RUU to return to full stock. Find one for your phone and run that. If it still doesn't work then it's a hardware problem.
Ok, so I replaced the current 2.41.401.41 (August) ROM with the earlier 2.41.401.4 (January) in the hope that a ROM change might reset the cellular radio. It didn't. 'Turn on radio' still does not respond either.
I did this with the bootloader onlocked, but S-ON. I think my very last attempt to fix this could be to set S-OFF, in the hope that some tool might be able to access the radio partition and re-write it or reset it or something. (This is still in the slim chance that this fault really is in software and not hardware!)
Are there any xda tools that write to or reset the radio partition (when S-OFF is set)?
What the...?!!?? So I thought as one last go at this (unless someone had comments re the S-OFF/radio partition idea), I'd let the phone get the OTA update back to the latest OS. So first I executed 'fastboot oem lock'. That of course erased device and reset it again. Radio still not working, no surprise.
After that, restarted in bootloader mode to confirm it says 'relocked', then rebooted normally... and I've started receiving missed txts! WTF.
So with enough restarts/resets, it's fixed itself? Faulty hardware, yeah right. Unless it is on the turn and happens again. [Edit: Yes it has, damn.]
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
I got this disease a week ago, tried to restart, didn't help. Been tapping airplane mode like million times, nothing. Found this thread, followed your instructions guys.
time_lord2004 said:
Ok, so it looks like it's possibly a software problem (but maybe at a low-level, related to the radio partition maybe?).
So got the phone onto the latest OTA software, but it broke again after a reboot (as above). I decided to repeat some steps (without needing the OTA update this time - just with the latest official ROM).
- Unlocked bootloader, restarted; does a factory reset; radio broken still.
- Relocked bootloader, restarted; does a factory reset; radio broken still.
- Shutdown, go to bootloader, check status to see that it's 'relocked' (it is), restarted, radio now works.
I'm too nervous to experiment further, but it seems this process is repeatable. I don't know if the radio coming to life, each time after this sequence of events, is a coincidence or not, but if it isn't, it would suggest to me that locking the bootloader then checking the status fixes things. Maybe this sequence toggles something dodgy in the radio partition.
Click to expand...
Click to collapse
Didn't work for me :/ moved on to zachariah's solution...
zachariah109 said:
amazing this is happening so close to Christmas on the older phones (mine has just done this aswell)
I'm going to dig into the phone and see what i can find leaving the phone off for 5 min and restarting has re enabled the radio for me 3 times, going to lock/unlock bootloader to see if this is repeatable fix.. jesus htc its like you've programmed the radio to spazz out. (this phones been used in 4 countries on 4 different sims, australia > japan > Malaysia >back to australia) so shes been well used.
Click to expand...
Click to collapse
Yes, IT WORKED.
Don't get me wrong, this is not the end.
Today. Radio doesn't work again. 5min off doesn't help anymore, unlocking-relocking bootloader ain't do **** too.
If you find any other action sequence which "fixes" radio, please share.
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
lightweaponx said:
So did any one of you actually try running a RUU like Tarima said? That should reflash the radio partition and fix any potential software issues.
Click to expand...
Click to collapse
Today I ran RUU. It didn't fix radio. Problem must be somewhere out of radio/system partitions range.
Well, I thought I'd do one final(?) post regarding this issue. I'm starting to concede that I might have a hardware fault, but it's taken a while to accept this.
About 2 weeks ago I started having problems with the 'swipe-down' at the top of the screen to look at notifications and settings (and it started responding badly in the camera app). Then it stopped responding completely... work-around was to use an 'open notifications' app.
However, I tried out 'Apex Launcher' as an alternative to the Sense interface, and swipe-down worked perfectly ok, so isn't the hardware ok? Isn't it a software issue? However, swipe-down had completely stopped working in the camera app by then (using a different camera app is acceptable work-around).
Roll forward to a couple of nights ago, I got notification and updated to android 8/Oreo, what have I got to lose! After the update completed, I can now swipe-down ok again on the home screen! But still not in the default camera app! So have I got a hardware problem or not...
But the big thing, and the biggest headache... once again after the big update (to Oreo) and reboot - once again the cellular radio was not working. I tried all my tricks of the past, nothing would make it go. A factory reset (to Oreo, not an old RUU), unlock and relock (which does a factory reset), nothing worked. Brought up phone info via *#*#4636#*#* and this seems to have had a make-over. There is now a button for 'mobile radio power' (must be a replacement for the 'turn on radio' option) which was showing as off. Turning it on seemed to do nothing (leaving it for a while and then waiting for screen refresh, this button would display as off again).
I'd probably rebooted, shutdown/gone into bootloader at least 2 dozen times, tried all combinations of everything I could think of and could not get it to wake up. At lunchtime today I was leaving the office, booting up my phone one last time and said to a workmate 'going to a shop to look at new phones'. 30 seconds later I look down at my screen... what the *(&$%*&!! I have a signal! Missed txts are coming in!
I know that now that the cellular radio is on, it'll keep running. It always has through this whole ordeal. It's just a matter of getting it to turn on in the first place, or starting after a reboot.
The fact that after installing Oreo the swipe-down works nicely (except for the default camera), and the cellular stuff works fine, once it is on, it really is difficult to conclude whether these are all software or hardware issues. But the reluctance of the system to turn on the cellular radio might be the biggest damning factor to point to it being dodgy hardware.
So the key is not to have to reboot ever again, or at least until the next flagship is out! I still have faith in the HTC stuff, but this has been frustrating...
Hope this helps someone out there!
So i've opened mine up - was due for a screen replacement anyway - tada bad contacts to the radio module (dry solder joint) physically pressed the radio module and it turned straight on. *i've added some paper layers underneath to keep *merckanikal* pressure on it (easier fix than reflowing) and now i know where it chip is i can press on the screen to add a little more if it doesn't work
It really ****ed me today however(seemed to cause phone to bsod, then reboot without radio) and the reason i've spent the last 3 hours replacing the screen and ****ing with the radio.
(whole day of work lost thanks to it. won't see that time back)
In other news i went and tested the note 8's spen - and i think i'm retiring the 10 this week. althought i've just fixed it shes' let me down for the last time.
The only negative i've gotten from the mechanical pressure is the lcd is showing a slight tinge of red now that the glue has hardened. and theirs pressure on the back of the screen. i used 4 layers of 80gsm paper (folded) to pack it out. i'm hoping as the phone heats and moves the paper will compact slightly more and the red blub on the screen will dissipate entirely -
- restarted over a dozen times to confirm the fix is atleast working for me. bootloader'd recoveried etc.. hasn't disabled the radio since..
Hope this helps for any of you still hanging onto the htc10.. (the pixel2's daddy, seriously just feels like the exact same phone*thats what she said?*)
time_lord2004 said:
Hi, I rebooted by HTC 10 a day ago (after 3 months uptime; previously restarted ok after 4.5 months) and now it no longer gets a cell signal (no service). Phone was working ok before the restart.
Wifi works ok, bluetooth ok, USB ok. I've been into settings, Backup & Reset, and tried a Network settings reset. Didn't fix it, so I tried a Factory data reset; still not working.
Under settings, Airplane mode says "Turning off..." as if it can't complete the operation. Under About->Network, Service state reports 'Radio Off'.
Under Mobile data->Network operators, selecting 'Search for networks' reports "Something went wrong while searching for networks."
I can't imaging it is a hardware error because it was working until the reboot yesterday.
Are there any tools I can use to diagnose the radio?
Click to expand...
Click to collapse
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Dissmeister said:
Not sure if this will help you or if you even have the issue now but its worth the try if you do. I upgraded firmware and lost radio too and couldnt get it back in any other way until I tried this. Worked perfectly
https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
See if it works. I cant say for your device but its worth the try
Click to expand...
Click to collapse
Did It Really Works
Adeel Ali said:
Did Anyone Has Tried The Method On S-Off by Fastboot erase persist plz tell me if it works i also have same issue
---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------
Did It Really Works
Click to expand...
Click to collapse
Yes it works.
yldlj said:
Yes it works.
Click to expand...
Click to collapse
Brother Did U Tried It U Also Have HTC 10
Adeel Ali said:
Brother Did U Tried It U Also Have HTC 10
Click to expand...
Click to collapse
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
yldlj said:
That thread is full of people who it worked for. It didn't work there wouldn't even be a thread telling people what to do. If the issue your having is because you went from Oreo to Nougat then yes it definitely works. Did you try it?
Click to expand...
Click to collapse
Yes I Went From Oreo To Nougat Once
Adeel Ali said:
Yes I Went From Oreo To Nougat Once
Click to expand...
Click to collapse
Then erase persist. Or get back on oreo
RUU worked for me
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.