Hallo,
my sister has a couple of problems with her cell phone D855(completely stock). She complaint that wifi and bluetooth doesn't work anymore as well random reboots.
At first i did a factory reset, didn't help anything, same goes with lg pc suite and restore upgrade errors. After this i tried flashing the latest stock rom(kdz file) with the lg flash tool and it did not help, instead the mtp/ptp mode was gone, i don't know why. So i changed to kitkat version(kdz file) , mtp worked but the phone was not stable and at some point it stuck in a bootloop, factory reset didn't help. Also tried with the tot method and it stuck was stuck.
Now i've installed V21a-eur version but wifi has no mac address, bluetooth and mtp/ptp doesn't work.
I could use some help :/
update
mtp works now. I was able to root and install a custom recovery.
Concerning wifi, i deleted all files in the data/misc/wifi folder. Wifi module got a mac address and found my access point but then the phone crashed and after the reboot the mac address was lost again.
Related
Hi, still a noob here. I was preparing for the procedure of going back to RUU to allow for the latest OTA update, and something must have gone wrong. I wish I had taken better notes. I was running the x3tremeSense122412 ROM, happy with it.
I did many backups before doing anything else (nandroid - both CWM and TWRP, Titatnium...), then connected the phone to load the older boot.img...For some reason, I first took the SD card out, connected to the computer and overwrote the boot.img file with one from a stock ROM.
Reaizing this was stoopid, I tried to fix it by rewriting the boot.img from the x3treme release. No luck.
So I tried to go back to the various backups, but the phone still does not work.
I also tried to connect it by USB, and am having another problem: adb works (ie adb devices returns the phone ID number), but fastboot does not (gets stuck in 'waiting for the device'). Any hint??
Thanks in advance!! :crying:
R: HELP-phone no longer connects to the network or wifi
fdafan said:
Hi, still a noob here. I was preparing for the procedure of going back to RUU to allow for the latest OTA update, and something must have gone wrong. I wish I had taken better notes. I was running the x3tremeSense122412 ROM, happy with it.
I did many backups before doing anything else (nandroid - both CWM and TWRP, Titatnium...), then connected the phone to load the older boot.img...For some reason, I first took the SD card out, connected to the computer and overwrote the boot.img file with one from a stock ROM.
Reaizing this was stoopid, I tried to fix it by rewriting the boot.img from the x3treme release. No luck.
So I tried to go back to the various backups, but the phone still does not work.
I also tried to connect it by USB, and am having another problem: adb works (ie adb devices returns the phone ID number), but fastboot does not (gets stuck in 'waiting for the device'). Any hint??
Thanks in advance!! :crying:
Click to expand...
Click to collapse
Try to reinstall the phone driver. When you are in fast boot try to locate the htc sync manager driver from the pc
Sent from behind you..
Problem solved
IT"S THE BACK COVER!!
Turns out while I was working on the phone, I kept the back cover off the phone so I could easily access the SD card.
Well....the back cover must contain either an antenna, or be part of the loop for one.
The moment I reconnected the back cover, WiFi came back and the signal on the phone is much stronger.
I now understand why the cover has spring contacts.
I hope this helps someone else - took me two hours of messing around to figure this out!
Now, on to the fastboot problem.
In order to fix my issue connecting to WiFi access points, I decided to delete the files within the /etc/wifi folder (was supposed to delete /data/etc/wifi?)
Since doing so, my phone has been stuck in a boot loop, not allowing me to change much on the phone in that time (maybe 5 secs).
I don't have a recovery installed (just the root with towelroot), so don't have a nandroid backup, and stupidly didn't take a titanium backup.
I do have a backup of the deleted files on my External SD, so could put them back in place, if possible.
Does anyone know of a solution to fix the boot loop, without wiping my data?
Or an option to backup at least my SD Card (ideally data as well) before I factory reset?
Thanks
Idk if it can help, but I did recovery from PC Suite just to get the KDZ of my phone.... It took his time so I went to dinner but when I came back my phone was already flashed. I didn't lose my data or apps it just flashed over it and unrooted (but you can root again).
Here are the answers:
Next time before mase with the root files backup all to SD or PC.
http://forum.xda-developers.com/lg-g3/help/help-lg-g3-d855-boot-loop-t2805286
-
http://forum.xda-developers.com/lg-g3/help/help-stuck-download-mode-t2822338
-
http://forum.xda-developers.com/showthread.php?t=2785089
-
The problem I have is that I cannot get PC Suite to see my phone or connect to it - Probably because I can't get the MTP driver to install.
I've been looking for the KDZ file for the 32GB Eurpean D855, but I have not found it as yet. Also not sure which DLL file I am supposed to be using for Flash Tool!
I did get so close to moving the files back to their correct location, but need like 1 second extra before the reboot!
RudeYute said:
The problem I have is that I cannot get PC Suite to see my phone or connect to it - Probably because I can't get the MTP driver to install.
I've been looking for the KDZ file for the 32GB Eurpean D855, but I have not found it as yet. Also not sure which DLL file I am supposed to be using for Flash Tool!
I did get so close to moving the files back to their correct location, but need like 1 second extra before the reboot!
Click to expand...
Click to collapse
Have you tried to boot in secure mode? Maybe it can give you more seconds.
Just hit power button and when menu comes keep pressing shutdown until appears the message to boot into secure mode.
Also you can try the twrp method and use adb on it to restore files.
Managed to get it recognised on a Windows 8 machine, rather than a Windows 7 machine (yep, strange huh)... managed to restore using PC Suite - no data loss, so i'm very happy!
RudeYute said:
Managed to get it recognised on a Windows 8 machine, rather than a Windows 7 machine (yep, strange huh)... managed to restore using PC Suite - no data loss, so i'm very happy!
Click to expand...
Click to collapse
What did you do to managed to restore using PC Suite - no data loss a little details will halp to others? :silly:
u1988 said:
What did you do to managed to restore using PC Suite - no data loss a little details will halp to others? :silly:
Click to expand...
Click to collapse
I told him on first reply. If you flash to recover through pc suite, it just flash over it without deleting anything.. It just unroot but you can root again.
badtzo said:
I told him on first reply. If you flash to recover through pc suite, it just flash over it without deleting anything.. It just unroot but you can root again.
Click to expand...
Click to collapse
As above. Even if it seems phone is not recognised in Pc Suite (but seems to be in Windows) connect phone and in LG PC Suite select Mobile Device > Restore Upgrade Errors
RudeYute said:
As above. Even if it seems phone is not recognised in Pc Suite (but seems to be in Windows) connect phone and in LG PC Suite select Mobile Device > Restore Upgrade Errors
Click to expand...
Click to collapse
Bootloop began after I though I did a mod and saved the 644 permissions.
PC Suite does not find the phone, even in with above method.
Other ideas?
Hi,
In my school which I don't have access to the router, I can't connect to the wifi with my cellphone, but I can connect with my other devices like my laptop or my other cellphone.
I was using CM12 that suddenly this happened. Then I flashed 3 different roms and reset to factory and even erase everything, but didn't work.
ŮŽPlease help me.
Edit: I can connect to other wifis, but not this one (which is not password protected)
Yesterday I decided to install ClockworkMod. I was running 6.0.0 Marshmallow
I unlocked my bootloader no problem. I decided to root before I flashed the rom. I booted into TWRP using adb, made a nandroid backup, and flashed stock-20a-rooted.zip (I was following this guide). It worked! I used a rootchecker app to ensure I had a good root. Then I went to boot into TWRP to install ClockworkMod. I turned off my phone and did the volume down + power thing, but I got the LG hard factory reset screen. So I decided to use ADB instead and rebooted my phone. However, when I tried to use adb, my device was listed as "unauthorized", and I haven't been able to use adb since! Here's what I tried (but not necessarily in this order):
Using the LG hard factory reset. Nothing changed.
clearing adbkey file on my computer. Nothing changed.
using a different computer with fresh adb and driver install. Nothing changed.
rebooting both PCs. No dice.
tried mtp and ptp on device. Neither worked. Device was not recognized on MTP (used to be recognized by adb when it was on mtp.) device was recognized on ptp, but it was listed as "unauthorized"
tried to revoke usb debugging in settings on device. That option wasn't listed in developer options.
tried to clear adbkey on device and found out that my device still hadn't generated an adbkey file!
throughout this whole time, whenever I plugged in my device, the NSA fingerprint dialog box DID NOT APPEAR.
Questions, thoughts on potential solutions:
can I somehow unroot or go back to stock? I heard we can't do this anymore because it bricks our phones....
I feel like this has something to do with how my device never created an adbkeys file.
SOLUTION
I have been working on this today and I found a solution. I had read that downgrading/unrooting bricks our devices, and so I had ruled it out as an option. After further research I found that we can revert to stock without downgrading and avoid a brick. Since I have an H811 on 20o, I found firmware here and flashed it using LGUP, which you can find here. I suggest using this link to learn how to flash the firmware. After that, ADB worked fine and the NSA fingerprint dialog once again showed up on my device when I ran ADB. Good luck to any of you with the same problem!!! Reply if you need help.
My problem started when I attempted to bypass the FRP by flashing a custom TOT file. I neglected to notice the file was specified for a 32GB version. I flashed it on a 16GB version using LGUpgrade Tool. The phone then froze at the splash page that just says "Google" . I thought I was fortunate enough to be able boot to recovery mode and so I flashed the stock firmware through ADB - the same ROM version that was previously on my phone and from a copy which I had used in the past with no problems. Everything seemed to be working again except my PC doesn't detect the USB connection anymore. I've tried the same procedure but now the command 'adb devices' doesn't list the phone. However, there is a point when I boot to recovery mode the PC makes a sound as if it detects the phone but then moments later it makes the other sound as if it gets disconnected. As I stated earlier, my phone seems to be where I was stuck at FRP with Android version 7.1.2 but my problem now is I can't get the PC to detect the phone when it's plugged into its USB connection. Nothing shows in Windows Explorer as well as Device Manager? I tried re-installing the drivers. Stopping and restarting the ADB server... still no detection. Is there a way to set USB mode to MTC while in FRP mode? Should it matter in Recovery Mode?
I'm going to wait for a response before I attempt to flash again but this time through the SD card because this will be a first time for me using that method and I hope there's a less risky solution.