knock on will not work to wake phone... - LG G Flex

So I was rooted AT&T and on 4.2.2 I could simply double tap the screen to wake up my phone. then I wanted to look at the new 4.4.2 so I used the LG Flash tool and flashed my phone back to stock with "LGD950AT-01-V10l-310-410-JAN-25-2014+0.tot" from the back to stock thread. took the KK update and played with it a couple days but missed certain things I needed Root for so I flashed back to stock 4.2.2 again with the same file listed above.
Everything is working except the knock-on. I tried doing a factory reset, (power off, hold vol- and power until LG logo shows, release for a second and rehold buttons until prompted for factory reset) but that didn't fix it. I tried re-flashing the thing with the same tot file, but that didn't fix it either...
I have tried going through settings/general/gestures and it is selected. I can double tap to turn my screen OFF, but once the screen is off I cannot simply knock knock to turn the screen back on.
any ideas?

Keep the root, don't mess up with superSu, keep it and upgrade to kitkat from menu, and you will get kitkat and your phone will stay rooted, I just did this and had same problem, Please let us know if you were successful doing all this, I have done this yesterday and I am rooted and have kitkat on att Lg Flex..good luck
schollianmj said:
So I was rooted AT&T and on 4.2.2 I could simply double tap the screen to wake up my phone. then I wanted to look at the new 4.4.2 so I used the LG Flash tool and flashed my phone back to stock with "LGD950AT-01-V10l-310-410-JAN-25-2014+0.tot" from the back to stock thread. took the KK update and played with it a couple days but missed certain things I needed Root for so I flashed back to stock 4.2.2 again with the same file listed above.
Everything is working except the knock-on. I tried doing a factory reset, (power off, hold vol- and power until LG logo shows, release for a second and rehold buttons until prompted for factory reset) but that didn't fix it. I tried re-flashing the thing with the same tot file, but that didn't fix it either...
I have tried going through settings/general/gestures and it is selected. I can double tap to turn my screen OFF, but once the screen is off I cannot simply knock knock to turn the screen back on.
any ideas?
Click to expand...
Click to collapse

schollianmj said:
So I was rooted AT&T and on 4.2.2 I could simply double tap the screen to wake up my phone. then I wanted to look at the new 4.4.2 so I used the LG Flash tool and flashed my phone back to stock with "LGD950AT-01-V10l-310-410-JAN-25-2014+0.tot" from the back to stock thread. took the KK update and played with it a couple days but missed certain things I needed Root for so I flashed back to stock 4.2.2 again with the same file listed above.
Everything is working except the knock-on. I tried doing a factory reset, (power off, hold vol- and power until LG logo shows, release for a second and rehold buttons until prompted for factory reset) but that didn't fix it. I tried re-flashing the thing with the same tot file, but that didn't fix it either...
I have tried going through settings/general/gestures and it is selected. I can double tap to turn my screen OFF, but once the screen is off I cannot simply knock knock to turn the screen back on.
any ideas?
Click to expand...
Click to collapse
I am having the same problem , did you ever get this figured out?

Had the exact same problem. I then did as Oscar786 suggested and Knock On works again, while maintaining root. So I am now on 4.4.2 with root and working Knock On.

RBDH said:
Had the exact same problem. I then did as Oscar786 suggested and Knock On works again, while maintaining root. So I am now on 4.4.2 with root and working Knock On.
Click to expand...
Click to collapse
yup. for some reason the tot file willnot support knock on.... but I am now rooted 4.4.2.

schollianmj said:
yup. for some reason the tot file willnot support knock on.... but I am now rooted 4.4.2.
Click to expand...
Click to collapse
Thanks, i did root and took the ota again and now knock on works again. I think when we revert back to stock some 4.4 files get left behind and things go funky. I also had no data when i went back to stock from 4.4
Sent from my LG-D950 using XDA Premium 4 mobile app

My data was working fine. but at least we got it sorted out!

Bumping this up from the dead because I have the same issue on a completely stock sprint phone. I have tried everything, even the secret menu tricks from the old G2 thread... any thoughts or suggestions for me? It knocks off easily, but will never knock on.

Guys you have to dial 3845#*yourphonemodel#
Ex. 3845#*955#

Claudio67 said:
Guys you have to dial 3845#*yourphonemodel#
Ex. 3845#*955#
Click to expand...
Click to collapse
And then go to "settings -> update touch firmware".

nvm
Just started working again.
I can find the ghost in the machine more than most.
All good now.

dannejanne said:
And then go to "settings -> update touch firmware".
Click to expand...
Click to collapse
Thanks buddy, just gor fixed
---------- Post added at 11:29 AM ---------- Previous post was at 11:17 AM ----------
kamarsyed said:
Thanks buddy, just gor fixed
Click to expand...
Click to collapse
You are the champ

Related

[Q] Why does my rom install in seconds and boot to black screen?

I have a note 3 that I'm trying to get Cyanogenmod 11 on to. I should note that I got this working with my Droid Razr earlier today using the exact same process. I get to the point where I flash the rom and it only takes like 5 seconds then says "successful". When I boot the rom I just get a black screen that I have to hold the power button down to get out of. My note 3 is running 4.4.2 I have root and busybox is installed. I've tried safestrap 3.72 and 3.75. I've even tried the stock slot (and then reverted back when it didn't work). I'm out of things to try and I can't find anyone else who has had a similar issue. Anyone got any ideas?
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
andygev35 said:
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
Click to expand...
Click to collapse
How are people getting cyanogenmod 11 on their att note 3s if not through safestrap?
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an N900T, or an N9005 Note 3 on at&t.
andygev35 said:
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an international note 3 on at&t.
Click to expand...
Click to collapse
Well that's sad. I'm assuming any of these will work in the meantime? http://forum.xda-developers.com/note-3-att/#romList
They should, just make sure if you're on KK to choose a KK rom.
noob over here needing help
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
sethers said:
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
Click to expand...
Click to collapse
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Sethers, please do not hijack and do not double post your questions in multiple threads.
graydiggy said:
Sethers, please do not hijack and do not double post your questions in multiple threads.
Click to expand...
Click to collapse
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08 said:
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Click to expand...
Click to collapse
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
sethers said:
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
Click to expand...
Click to collapse
If you're on the A3 bootloader then reflashing NC2 with odin will clear this up, (double-check in download mode) then follow the instructions in this thread. If you're on A2 you can still do this but it will overwrite your bootloader and lock you into NC2 so if that's the case you might want to read through that thread to make sure you're ok with that!

Touch Screen issues after root

So I was going through the process of rooting my phone, and after I rooted my phone with CF auto root my touch screen calibration is all off for my touch screen with the diparity getting greater the further to the right and the further down you go on the screen, but my s-pen works at is should. Is this a known issue, or is there a way to fix this?
I have tried flashing different roms, and un rooting as well as a different recovery, but even in the recoveries the screen is not calibrated properly.
Did I just suffer bad luck and lose my touch digitizer at the same time?
I really haven't heard of anything like this. Don't wait to long to return if you still can
BAD ASS NOTE 4
Recalibrate
Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
How do you go about doing that? I don't have the problem, only with a certain rim. Wanted to see if that worked
Sent from my SM-N910T using XDA Free mobile app
Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
Do you know of an app to do it or the code.
BAD ASS NOTE 4
Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
I tried the *#0*#, but I cant even get that to work since its so inaccurate,
Looking into it:
http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/
Looks like they are making it harder.
We are flashing so hard we didn't notice.
Honestly flash firekat and use it as a base.
But, we'll have a better answer soon.
I'm having the same exact problem here.
I have illustrated the problem in the attached photo, just to make it clear.
My phone is Note 4 Sprint
I have flashed custom and stock firmware but ends up with no luck
Hope to find the solution here :good:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Exact same issue here as well. After rooting my phone and installing CM 12 on it all of a sudden my touchscreen calibration is waaaay off. Its more pronounced the further down the screen you go (ie I click in the 2/3 section top to bottom to click on the actual bottom) but with the s-pen everything is fine. I tried the code dial *#2663# but then I receive the prompt "connection problem or invalid mmi code". I am connected to the mobile network (Rogers in Canada) and mobile data is working without issue. I've tried completely wiping the phone again, all partitions and reformatting system, reflashing CM12 + gapps and still the issue persists. Google-fu isn't turning up with much either, please help!
Did you do it with Odin.
Yes I rooted it with Odin using CF-Root as with all my past Samsung devices (specifically this link: download.chainfire.eu/563/CF-Root/CF-Auto-Root/CF-Auto-Root-trltecan-trltecan-smn910w8.zip). TWRP recovery was flashed with version 2.8.1.0 (don't have the original link at hand but filename is: openrecovery-twrp-2.8.1.0-trltecan.img), following with CM 12. I've tried reflashing the root as well and it did not help. Screen calibration is off even in TWRP but as mentioned before s-pen works fine.
Update on this, I flashed back to a stock (but flashable) ROM. Ran the *#2663# screen firmware fix, which resolved the inconsistency. Booted back into recovery, re-flashed the AOSP ROM (Beanstalk in my case, I was trying it as I thought CM was my issue initially (which I know was wrong)) and everything is good.
Very frustrating but at least now it works. Replying to SMS messages with the s-pen made me feel like my father typing....
Well you can root only in android 2.2 or below because if you root in a lastest version on android it would not work it will crash your phone it will delete system files which you cannot restore, it critical job to do and very dangerous, I notice that some ones phone got rooted and does not work by someone rooting it to cyangemod,which delete the whole system files, well if you rooted your phone there will be lots of problem that you may not like, the rooting can do anything in your phone.
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Thanks for finding this thought i had a busted note
you saved my note 4!
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
thank you for this info!! you saved my note 4 . i was having some touch screen issues!
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Oh, Thank You! This restored my Note 4 after I had accidentally flashed the wrong recovery image (which screwed up my touch screen calibration, but luckily nothing else). Kudos!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:35 AM ----------
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Oh, Thank You! This restored my Note 4 after I had accidentally flashed the wrong recovery image (which screwed up my touch screen calibration, but luckily nothing else). Kudos!!!
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Thank you so much this was the exact fix my phone needed. I've spent so much time with @Flashvetrin trying to figure it out
Thank you thank you Thank you
re: screen calibration issue
Dockadocka said:
So I was going through the process of rooting my phone, and after I rooted my phone with CF auto root my touch screen calibration is all off for my touch screen with the diparity getting greater the further to the right and the further down you go on the screen, but my s-pen works at is should. Is this a known issue, or is there a way to fix this?
I have tried flashing different roms, and un rooting as well as a different recovery, but even in the recoveries the screen is not calibrated properly.
Did I just suffer bad luck and lose my touch digitizer at the same time?
Click to expand...
Click to collapse
Don't worry, here is the fix for it.
I had the exact same problem a few weeks ago.
Go to the dialer screen and click in:
*#2663# screen fix works perfect, it will display a menu, select re-calibrate
or update or something to that effect, ( I forgot the exact wording)
But when you see that menu screen you will know which one to click.
You might have odin flashed the wrong twrp for the phone, but either
way this will fix it.
I would suggest that before you do this, odin flash the n910t
stock samsung firmware, that way twrp will get over-written.
Good luck,
Have a great day!

Knock On

I have been doing some searching and seen that several people have had trouble with knock on. I ran into the same problem but have yet to fix it. Got me wondering what causes the problem in the first place. Any thoughts? Additional pointers to fixing it would also be appreciated.
Sent from my VS980 4G using XDA Free mobile app
NOTE: Just noticed that when I dialed *611 to get Verizon, com.lge.doubletap fc'd.
More info is needed like what rom or kernel your on to know or have an idea why it's not working for you. Then you might get some answers that help you out
It's not all that critical to me just more of a brain exercise to me trying to figure it out. Interestingly, I found that immediately after I went back stock, rerooted, etc and turned on the option to use the power key to lock knock on quit working and wouldn't come back on.
I have stock ROM and rooted but after I installed twrp recovery the knock on stopped working. Now when I double tap the phone restarts. I liked using that feature.
Found a solution that worked for me, sensor calibration in settings , gestures.
Unfortunately it worked for a little while, now its not working. Seems like the phone goes into deep sleep and when I double knock the phone restarts.
This morning I did factory reset, its still rooted but I will try it without a custom recovery. Knock on is working for now. I thought factory
reset would get rid of TWRP, its still there and so is the knock problem.
Knock on help
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)
dakattak said:
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)
Click to expand...
Click to collapse
I don't know about fixing the dead spot/black band on your screen (you probably need a new screen now), but I suggest you .kdz your way back to stock 27A, use stump root again, but, this time, do not use AutoRec. Using AutoRec on 27A causes all kinds of issues.
You have to flash a bumped recovery using adb commands...I think I read somewhere that there is a tool, or something that automates the adb commands for you, and flashes a bumped recovery for you, but I can't remember where I read it...use blastagator's bumped recovery to flash to your phone; just take out the recovery image from his zip, and flash it using adb commands.
Blastagator recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Thanks for your response. I guess using auto rec on 27a was the culprit like you say. I seem to remember it happening shortly after the update.
As for the dead spot. It doesn't affect my screen other than not responding to touch in the affected region. The entire screen display works visually.
I'll give this a shot tonight and see how it goes.
Again, thank you for your response!
Cheers
Sent from my VS980 4G using XDA Free mobile app
I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.
ATgiant said:
I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.
Click to expand...
Click to collapse
After a lengthy power outage in my building, I was finally give blastagator's bumped recovery a try. I flashed back to stock 27A and rooted with stump like you suggested. Couldn't get it to flash manually with adb or terminal. I ended up using flashify to flash blastagator's bumped recovery image. It installed fine and I was able to boot into the custom recovery, unfortunately the dead spot is still there.
So annoying. It looks like I'll be contacting Verizon about a replacement.
Thanks again for your help

[Q] Getting Started with the LG G2 (Verizon)

My fellow Android users & developers,
I've been out of the game for a while now (since the HTC incredible). I recently purchased an LG G2 when my upgrade came up. I'm moving back from an iPhone. The one thing that I am trying to do with this phone is some how set up tethering. Previously with my incredible I had to root the phone and then install a ROM. I have been searching around google and the site and all I am finding are horror stories of people bricking their phones. There are a million threads here. Can someone point me in the direction of what I need to enable tethering or how to properly root my device so I can install ROMs from the site? Any tips or links would be greatly appreciated!
My Device:
LG G2 VS98039A (Verizon)
Build: LRX22G
Kernel: 3.4.0-perf-ga038154
Thanks,
Scyth3
Just picked up a used G2 that should be arriving tomorrow so doing some homework today on this device. This is what I am planning to do when mine arrives, best of luck to you
root = http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
hotspot (see post 339) = http://forum.xda-developers.com/showthread.php?t=2456338&page=34
First of all, do you have warranty?
If you do, check if your GPS is working, only GPS sensors. There are a lot of reports with LG G2 gps broken, not working, etc.
If its broken, go and replace it. If its works and you are stock 39A, root your phone with root method that @someguyatx recommended and then, install recovery with this link:
http://forum.xda-developers.com/verizon-g2/development/tool-freedom-tool-vs980-39a-twrp-t3053134
When done, do a full nandroid backup prior doing anything. After that, I can recommend xddadeb version of Lollipop, its great and removes a lot of bloatware.
Anything, just ask
Thank you both for the replies. My warrenty should be gone at this point. I have had the phone for more than a little while I should have mentioned. How would I go about checking the GPS to ensure it is functioning? I have never had any trouble with using google maps or anything of that nature. Also on the link to the rooting page I noticed below the first post is a "one-click root". Should I manually do the instructions at the top or just use the one-click root?
Thanks again!
I am planning to follow the one click procedure link tomorrow to root as soon as I verify my phone works. Check out the video in the one click link from qbking77, his stuff is always good.
If your maps have been working properly then your GPS should be good to go.
I didn't even scroll down far enough to see the video originally haha. Thank you so much for your help. I'm in the process of rooting it now! I'll update the post once I am finished! :good:
Hope it went well, my phone just came in today so I will be rooting it tonight. Looks like I need to update first since its still on android 4.4.2
Sent from my XT1080 using Tapatalk
Just an advice: lollipop uses more battery so its not mandatory to update to that versio, its your choice.
Enviado desde mi VS980 4G mediante Tapatalk
I'm updated to lollipop, GPS is working great and I rooted after a few tries with the one click and a driver reinstall. Its refreshing to still have devices that root this easy. IJust need to add recovery and flash the hotspot zip. Thanks Deathsync3 for starting the thread and neondunker. Loving the G2 so far, much snappier than the Droid Maxx
Sent from my VS980 4G using Tapatalk
Remember to do a full nandroid backup of your stock rom, including EFS and those stuff.
Everything went smoothly. I did have some initial trouble though. To anyone using this method it does work BUT, when you get to the point after you have installed the drivers for the device and unzipped the .exe. Plug your phone in and click start root. when you get the prompts on the phone DO NOT check the box that says, "always allow". I REPEAT DO NOT CHECK the box. Simple click "ok" on the prompts and the root will complete sucessfully. I am now onto installing backup , a ROM, and hotspot. @neondunker can you link me to the ROM that you were talking about in the post? Also can you explain a little more in depth or provide a link in regards to what needs to be backed up? Is it still like the HTC Incredible where I had to go in and clear the cache, delvik cache, etc? Thanks again everyone!
Well the idea is to perform a full nandroid backup before leaving stock just in case. Then you can leave that backup on a pendrive or computer.
About the rom, is the xdadeb one in android devolpment. You wont miss it since itsa always in the first page. Just follow the instructions, dumb proof hehehehe.
Enviado desde mi VS980 4G mediante Tapatalk
@neondunker One last thing. How do I enter back into recovery mode now that TWIN is installed? Thanks for all of your other help man!
Two ways
One through adb and the other is to power off the cellphone. Then power up while pressing power + down volume. As soon as the lg logo appears release the buttons and hold again volume down.
Enviado desde mi VS980 4G mediante Tapatalk
neondunker said:
Two ways
One through adb and the other is to power off the cellphone. Then power up while pressing power + down volume. As soon as the lg logo appears release the buttons and hold again volume down.
Enviado desde mi VS980 4G mediante Tapatalk
Click to expand...
Click to collapse
What is ADB? annd when I power off then power and hold down the power and volume button it puts the phone into safe mode....I just did some searching outside the fourm. It seems this is the way to get into TWRP.
Try holding volume down + power
Immediately when LG appears let go of both and ONLY hold onto power, should boot into option to factory reset
Hit power button 3 times to continue, then it will load twrp
Even though it highlights factory reset it will NOT erase your data and should open up to TWRP.
Quote:
Thank you illyfilly and bodom_hc. Bodom_hc's method worked. I know others must be having this same issue/maybe someone should post it up somewhere. I really apprecaite the time you both took out to reply to me. Now I can flash rom's like I have for every other device. Much appreciated, thank you!
Quote:
Thank you for this! I was having the same problem. I have to admit, I panicked a little when it said it was proceeding with the factory hard reset, but then the recovery screen came up. Phew!
Thanks again.
Can anyone quadruple confirm that doing this does NOT erase all user data/settings and factory reset the G2? I'm honestly too scared to do this as I can't do a nandroid backup without TWRP... Thank so much!
Click to expand...
Click to collapse
This all being said, can you confirm this is the way that you go about entering TWRP?
Deathscyth3 said:
What is ADB? annd when I power off then power and hold down the power and volume button it puts the phone into safe mode....I just did some searching outside the fourm. It seems this is the way to get into TWRP.
This all being said, can you confirm this is the way that you go about entering TWRP?
Click to expand...
Click to collapse
Took a Leap of faith. I can confirm this is the method of how to access TWRP on the Verizon LG G2 once rooted and installed. Now onto the ROM and hotspot!:good:
Deathscyth3 said:
Took a Leap of faith. I can confirm this is the method of how to access TWRP on the Verizon LG G2 once rooted and installed. Now onto the ROM and hotspot!:good:
Click to expand...
Click to collapse
So what do you have to do exactly? I have been using the quick boot app for years to go into recovery but its helpful to know the hardware key combo.
someguyatx said:
So what do you have to do exactly? I have been using the quick boot app for years to go into recovery but its helpful to know the hardware key combo.
Click to expand...
Click to collapse
@someguyatx In order to access TWRP using the phones buttons:
****PLEASE NOTE this is for the VERIZON LG G2****
1. Power down your phone
2.HOLD the following buttons: POWER button and the DOWN volume button
3. Once the LG logo pops up let go of the buttons
4. Once the LG logo disappears hold both the POWER and DOWN volume button again
5. This will take you to the factory data reset screen
6.You will see some text that says, "Erase all user & restore default settings --> your selections will be yes or no. Select YES ( just trust me)
7. It will prompt you again ---> select YES, but this time press the power button 3 times ( so YES, YES, YES.)
8. The phone will go back to the LG screen and then the TEAMWIN logo will pop up and take you into recovery.
@someguyatx and @neondunker and @amcleod1995 have a question for both of you though.....This version of TWRP seems to be behind in regards to some of the ROMs I've looked at our is 5.x.x.x they use 6.x.x.x. I saw that some of the boot stacks include the "updated version" but how do you flash a boot stack? My brother started another thread asking the question as we have both reasearched quite a bit to avoid bricking out LGs.
Brother's thread ----> http://forum.xda-developers.com/lg-g2/help/how-to-flash-bootstack-t3139847
I flashed xdabbeb 3.1.2 Rom this morning and just followed the directions, first I flashed the 39a bootstack then rebooted to recovery wiped the stuff it said and flashed the Rom. So far it's running great.
Yes, its a great rom and the multitasking apps have improved over the 4.4 version. The only drawback is the battery life.

H811 completely dead

Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.

Categories

Resources