Hi
My phone is LG V20 F800K and i wasn't getting oreo update via OTA, so i manually downloaded the files from LG Firmware and installed oreo but then faced horrible battery timing issues so i reverted back to android 7.0 after testing one week on oreo. I did all this using LG UP tool via Uppercut.
Now that i am on stock nougat again, everything else is fine even the battery timing is perfect now as before but now the GPS is not working at all. It displays that it is searching for my location and it never shows it. I tried it in Google find my device app, then Google maps and then thought there might be some else issue, so i tried installing GPS check and fix apps from play store, but all of them just keep searching but nothing happens.
I flashed the stock 7.0 from above mentioned site and even the software version is same which was before i.e. F800K 10E. What is wrong with my phone? Can anyone please help?
Hi
I came back to reply because the problem resolved with a little tweak.
I found this thread on reddit and i tried doing that as a hope of making this happen myself and not spend money for this. I tried cleaning the top points shown in the picture of the reddit link and screwed back in. When i tried it didn't work. Then i just tightened the screws and it worked. So if anyone else is also facing same issues, this might resolve.
https://www.reddit.com/r/lgv20/comments/7fx2gz/becareful_buying_the_top_plastic_bezel_of_the_v20/
Related
Hello,
Yesterday i receive the notification for update for android nougat in my phone. The update ends without any problem but right now with this new firmware I have 3 BIG problems:
Back camera don't work > The camera apps open the front camera and i don't have the button to switch for the other camera.
Flash don't work > Flashlight app only controls the screen but do nothing to the flash.
Laser: The app for measure with the laser don´t open.
I already have done a factory reset without any success.
I already enter in safe mode without success.
I already clear all the cache without success.
Any ideas?
Are someone with the same problem?
Thanks!
Hi I updated my Zenfon 3 to Android 7 two wks ago after receive the msg from Asus. After reading your posting, I try all the problems mentioned in your article but it don't exist (maybe I'm lucky), in fact some of the pre exist (problem come with my purchase) problem such as the ear-phone connection problem has resolved. I have yet to find any major bugs in my Zenfon 3 yet. Overall I'm happy with the update.
Try reinstalling the ota. Flash via bootloader. Get the update file via asus site
I have done that but without success
I haven't experienced any issues. I factory reset right after updating though - you may want to give that a try.
DOall said:
I have done that but without success
Click to expand...
Click to collapse
If that is the case it may already be a phone issue. Flashing a device will do a clean install of the software. So any software issues should be resolved.
I suggest trying downgrading to the very first os in the asus site. Make sure you're using the same version though
Im having a problem with my phone and some apps auto refreshing web pages will auto refresh taking me back to the top, instagram will auto refresh doing the same thing, youtube will reload and restart the video or completely start a different video. I have done a factory restart, started the phone in safe mode and tried using youtube and i still have the problem.
to me this seems to be a software issue but i cant be certin and doing an internet search isn't showing much results.
Does anyone have any ideas?
Android 7.0
Version QH1
I've had this problem since I installed the August android security update, I think it's related to that. Downgrading the software would probably fix it, if it's possible.
Kf_Umbra said:
I've had this problem since I installed the August android security update, I think it's related to that. Downgrading the software would probably fix it, if it's possible.
Click to expand...
Click to collapse
Yesterday (Aug 25, 2017) I did an update to QH1 through the Verizon Upgrade Assistant and it did not correct the problem.
Additionally I'm kind of a bit nervous about downgrading since i have no idea what I'm doing and I'd like to avoid bricking my phone due to my ignorance.
So i guess unless Verizon and/or Samsung decide to do anything about it, I'm in limbo i guess... :crying:
Glad I'm not the only one with this issue, at least it kind of clears up that its not a hardware issue.
I downgraded to the first nougat update (QA4) and everything seems to be working as it should, although I had to wipe my data to make it work :/
can you give me or direct me to instructions for the novice on how to do this?
Is anyone else having this issue? know how to fix it? if you know how to fix the issue can you provide instructions on how you fixed the issue?
From what I have seen and done I'm running u firmware. It seems as if you can downgrade to the oldest nougat firmware only. No Further.
Nexus 6p, unlocked bootloader and running 8.1DP.
Whenever I make a call and put the phone to my ear the screen turns off and never comes back on. I tested the sensor with the device info app and I the sensor stays in the "close" position when engaged untill the app is restarted.
I did some research and I found that some users had this issue with the Nougat update but no relevant solutions were found and the 7.1.1 update fixed the problem.
I would like to avoid factory reset or locking the bootloader if possible.
Can anyone think of a possible solution?
I tried the Proximity sensor reset app from the play store and that does absolutely nothing.
EDIT: Stable 8.1 doesn't fix the issue, even after clean install and manual flash and wipe.
I'm on SuperXe 8.0 Oreo built and it works flawlessly. I remember having that issue on nougat ROMs use to drive me nuts. Every time I needed the keypad I had to fight to get the screen back on. ?
Not a factory reset. Manually wipe the phone and apply the latest 8.0 image.
So after manually flashing the 8.0 image everything worked. I thought id give 8.1 DP2 a shot and I wiped and flashed this manually. It worked during the restore but stopped working after all my apps were back, so I thought it may be an app that's causing the problem. Strated in safe mode, issue is still there. I guess Ill just have to wait for the stable 8.1 release. If anyone else is facing the issue please post here.
so, i will try my luck. first thing is, i have a xt1684 retgb. atm i'm on full stock oreo firmware, a backup that i made where everything should have worked fine. after the issue appeared i restored the backup. but yea, it still persists. what a *****y phone.
now i have the problem, that in any case no voice is recognized neither via the build-in mics nor over a plugged headset.
neither a full stock flash to oreo nor to nougat changed it. everything else seems to be working as it should.
really guys, give me any hint to get rid of this. everything is welcome. :fingers-crossed: i count on you. cheers
okay got a little success in camera. in there i got my voice back after re-enabling mic permission in settings. but it doesn't help on google search e.g. .
i got my mic back working. but i still can't tell what caused it. maybe something equal to the problem that causes no touch issue. don't know. flashed a few stock and rom until it worked again. it was a work or die mission. as mentioned in the stock oreo thread it is really neccessary to let every stock flash finish with the initial setup (even if skip everything) till you are on launcher homescreen.
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others
Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.
This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps