yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] AeroPeg:
Fastboot getvar all

Here's what I got when I typed fastboot getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.24.21331147A1.09G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.16.1540.8

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: BS_US001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 3aa067db

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.035s

Update: just googled 0P6B12000 is Dev edition, my bad. Going to try easy method of installing the 4.16.1540.8 RUU. Thanks ckpv5. Will post with results.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Then it is confirmed that you have a Dev Ed device.

Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.

Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
[One (M8) Q&A, Help & Troubleshooting] AeroPeg:
4.16.1540.8 RUU stuck

4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now. Phone is showing just the silver htc logo, no progress bar or anything else.

Should I try flashing the 6.12.1540.4 firmware now? Thanks for the help so far ckpv5 :)

Also, is the phone charging while connected to the computer & updating? Just asking since I can't see the battery percent (no OS) and don't want the phone to die while flashing.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.

See the How-To linked above for the HTC Sync Manager download page, install it as it will install the USB Driver, then uninstall the Sync Manager but leave the driver

While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
[One (M8) Q&A, Help & Troubleshooting] AeroPeg:
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?

Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
You must use USB2.0

When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.

If you don't have a USB2.0 - other options :

Option 1:

Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.

Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.

Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.

boot to bootloader then select hboot or boot to hboot - it's your choice

hboot will scan the file and ask to volume up to update

volume up

finish, press power to reboot and do all the setup stuff

remove 0P6BIMG.zip from your microSD

now you have ROM installed then can proceed with OTA and the rest.

Option 2:

Re unlock your bootloader again with your unlock_code.bin that you got from HTC.

Install TWRP 2.8.7.0

Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery

Reboot.. setup.. OTA..OTA.. done.

You can get all the needed files in the link shown in my signature

So now .. you have 3 options to choose.

1. RUU method

2. 0P6BIMG.zip method

3. Nandroid method

I got to go now ... good luck
[One (M8) Q&A, Help & Troubleshooting] AeroPeg:
SOLUTION - see ckpv5's 3 solutions

Thanks a TON ckpv5. I followed your instructions & reinstalled HTC Sync Manager, then connected the cable to a USB 2.0 port instead of 3.0. The RUU method you originally suggested worked like a charm. I now have stock HTC software, stock recovery just like I wanted. I then did an OTA to the latest software. When I sell my device in a few days, I'll be sure to follow your tip and run the latest 6.12.1540.4 RUU to clear off all the old OTA files.

Many thanks again for your help - hopefully others will see the 3 solutions you posted.
[One (M8) Q&A, Help & Troubleshooting] ceylin45:
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated

Thanks..

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.25.214500021.06G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.16.401.10

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: HT44LWM05174

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 3aa067db

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.078s
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Yes ... just follow what is written on top post above.
[Galaxy S6 Q&A, Help & Troubleshooting] bigaloz:
Hi. Just opened my Christmas present - new S6. However, when i turned it on the phone boots to the opening screen where you select the country but the touch screen doesn't work. The back button, recent app button and home button all work.

I've tried rebooting but same problem.

I've searched the net for a solution but nothing. Anyone have a suggestion or do i have to take the phone to Samsung.?

Thanks

Alan
[Galaxy S6 Q&A, Help & Troubleshooting] SaffatBokul:
Yeah I think you got a defective device. Send it back to samsung. Bad luck
[Galaxy S6 Q&A, Help & Troubleshooting] bigaloz:
Cheers. What a pain in the arse...
[Android Q&A, Help & Troubleshooting] Lgspirit:
Hi everybody. For the last 3 days ive been trying to find a way to get this phone to work with my midi keyboard.

I got this phone quite recently and thought that most smartphones nowadays would come with the normal functions as any pc does.

Ive rooted it with kingroot tried several usb tools but no success. I registered here to ask anybody if theres a way to enable or force it to usb otg.

I got 2 cables none worked.
[XDA Assist] R212Warden:
Hi, i got my hands on Kurio xtreme tablet and after rooting i have decided to check its bootloader(for unlocking).

Unfortunately extracted boot.img reveals nothing intresting, and im too much of a n00b to do any more :) . Only interesting things that grep found were "PMDB" and "FSTK".

This thing has Intel Atom z2520 chipset and post.bin has Intel signature. It runs Android 4.4.2 with stock recovery, which is accessible through droidboot.

I belive there is something else hidden in the bootloader partition. Extraction gives 3 files, two .bin files and a key.

Can i get any assistance on this please?

Bootloader: https://drive.google.com/open?id=0B8e7D92j5MIPeGZEMFlRZnZSeTg
[XDA Assist] Saber:
Hi,

Thanks for using XDA assist.

I couldn't find a specific thread that could help you out. Instead, I would suggest posting in the Android Q&A, Help & Troubleshooting forum as there is no dedicated forum for your device.

Good Luck! - gsstudios
[XDA Assist] R212Warden:
Thanks, will check/post there :)
[Mi 3 Q&A, Help & Troubleshooting] wky750:
All the CM13's ROM have the same problem: the phone number of came in is "unkown"!

Did anyone meet same ploblem as me?

Describe:

1. when calling in, is whould show the phome number right! same as contacts name.

2. If the call not be answered, the number ( or contact name) can be show right in RECENTS list.

3. The all number of answered call are showed "unknown" in RECENTS list.

Why? soo strange. Where to setting to correct this wrong? Who can help me?

My phone is xiaomi 3C.

Thanks!
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
Are you cdma user? Ivan's mm has fixed that, but the other roms still have this bug.

update: didn't see you are using mi3c. yes, Ivan already fixed that in his 5.12.1 build. if it really annoys you, try ivan's latest version 5.12.18.
[Mi 3 Q&A, Help & Troubleshooting] wky750:
Thanks for reply.

I have tried Ivan's rom. It hasnt this problem. I have thought only I have this ploblem. Thank for you message that I was wrong.

yes, I am CDMA user.
[Mi 3 Q&A, Help & Troubleshooting] nokiaer:
me too! cm13 is no signal even flash the CDMA zip
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
two temporary solutions for no cdma signal:

1. dirty flash from cm 12.1

2. or add these lines to /system/build.prop of cm13.zip and then clean flash

# Telephony property for fixing cdma

ril.subscription.types=NV,RUIM

ro.telephony.default_network=22

Tested on my MI4LTE-CT, should also work on mi3c or mi4c. it causes mobile network FC, but nothing bad else.
[Mi 3 Q&A, Help & Troubleshooting] wky750:
Mokee change log: Ivan - Fix unknow number in call log when cdma is a MT call.

Thanks to Ivan!!
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
It still doesn't work on mokee 1231 nightly, but I guess it will be finally fixed soon.
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
Thanks Ivan. It's already fixed on mokee 0101 nightly.
[Mi 3 Q&A, Help & Troubleshooting] wky750:
CM13 still not work on 0102!

Mokee had fixed, I flashed too. But why does CM13 still not work on 0102? Didn't mokee post the change to CM?
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
Ivan pushed his fix to mokee's source only, so cm didn't get the bug fixed. Since almost all cancro devs are using mi3/4w, I guess they won't fix it too soon because they even don't know this bug exists.

Edit: I‘m happy to say I was wrong, fix showed up in cm13 0103 changelog.
[Mi 3 Q&A, Help & Troubleshooting] wky750:
really? that's great!

btw, where to see the changelog? I always get "err02: Change data unavailable. " from http://www.cmxlog.com/13/cancro/, only

occasionally can get the right result.
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
I don't know. I saw it here: https://github.com/CyanogenMod/android_packages_services_Telephony/commits/cm-13.0

I guess very few people use CDMA except for China? Here is about 200 million...
[Mi 3 Q&A, Help & Troubleshooting] wky750:
谢谢！那个链接我这儿可用。既然只有中国人用，你也是中国人了？用中文还是方便些。
[Mi 3 Q&A, Help & Troubleshooting] aslike2:
?*??+??*??ID...I should have noticed that...
[MDA II, XDA II, 2060 General] nebondkiev:
I got problem with my device.

Every time I insert a sim card it show Unknown SIM status.

I already try several unlocking tools but still the same.

Any body have an idea?

Thanks...
[MDA II, XDA II, 2060 General] Rudegar:
i would try another simcard as some are just incompatible
[MDA II, XDA II, 2060 General] nebondkiev:
I did bro... but still the same
[MDA II, XDA II, 2060 General] utak3r:
uch... :eek:

I don't think it's locking situation... IMHO it's something with your hardware smart-chip reader... :(

Did you flash it recently?
[MDA II, XDA II, 2060 General] nebondkiev:
Maybe... So is there any hope for my problem??
[MDA II, XDA II, 2060 General] Rudegar:
guess you could try upgrading it to a diff rom

and or radiostack
[MDA II, XDA II, 2060 General] nebondkiev:
How can I upgrade the radio stack?

Can u tell me?
[MDA II, XDA II, 2060 General] Rudegar:
like you upgrade the normal rom but having the

"Radio_.nbf" of your choice in the dir with the flash tool

rather then the "nk.nbf"
[MDA II, XDA II, 2060 General] nebondkiev:
I already upgrade it to version 1.19...

but nothing change. Any other way??
[MDA II, XDA II, 2060 General] flyboyovyick:
i had the same problem with my htc vox.

wouldn't recognize any sim card i put in. i swapped parts and everything, and it still would work, so i just give it to my uncle.
[MDA II, XDA II, 2060 General] SiL3nTKiLL:
try changing the rom? different sim card? different radio?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] Ankitdahal:
I need Pit File please If you do have note 10.1 save your pit file and share :( :(

My problem : http://xdaforums.com/galaxy-note-10-1/help/stock-rom-didnt-installed-bootloop-self-t3277850

Merry Christmas Guys !!
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mke1973:
Try the PIT file in this thread. http://xdaforums.com/showthread.php?t=2363703
[General Questions and Answers] Herchizante:
I go to:

https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail

and I set:

Product ID: 10125092

IMEI: 353059020693015

s/n: C2Z7NB9421413504

but I get:

Please input the correct Product ID. :eek:

I'm sure about numbers... I could upload the pics....
[General Questions and Answers] Becky pac:
please send me the product ID or

Bootloader code

details;

Model: Huawei Ascend G630-U10

IMEI1: 867256029325206

IMEI2: 867256029360211

Serial NO: H3L7S15925003594

Please tell me the product ID
[XDA Assist] cruelle:
Alright Guys,

This is my first post in here so try to gentle on me. ;)

So i had my Acer Liquid (T03) Z 630 for quite a while now so today i decided to flash a custom recovery i've done this before several times so nothing unusual unlocking bootloader etc.

Now comes the tricky part in a way.

I flashed TWRP as usual phone rebooted as USUAL and now i am kind of stuck in an Infinite boot loop of death and i cant even enter bootloader.

The only thing it does is "showing" the Manufacturers Logo for like 1 to 3 seconds sometimes longer sometimes shorter but in the end always reboots tried to enter recovery etc etc and read for hours now.

Funny thing is while it is "showing" the Manufacturers logo it still gets recognized by my Linux pc so my hopes are kind of up that there'll be a solution different then dumping that pretty phone ;)

Thanks in Advance for any help that might be offered :)
[XDA Assist] Vatsal:
Hello,

I couldn't find much related to your question/device

You may try asking it here Android Q&A or Ask any Q noobfriendly, the experts there maybe able to assist you.

Good luck!

-Vatsal
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
p8 lite keep blinking on huawei logo

i try to reprogram via sd card but it not going to updating mode and keep blinking on huawei logo

is there any possible way to solve this problem

is there any other way to flash like adb ?

if yes then share the procedure and the files
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
kindly share ur expertise
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
where are the experts ?
[P8lite Q&A, Help & Troubleshooting] sokkoban:
What you have written does not provide information about the problem that you have.

Describe in detail what you tried to do. If you tried to install a new firmware write full model that you have and software
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
wat type of information u want ?

simple is that huawei p8 lite ale-l21 just reboot on huawei logo

and when i try to reprogram via sd card (dload) and press volume + - but set not going to update mode
[P8lite Q&A, Help & Troubleshooting] sokkoban:
OK

1. Which version of firmware running now on device

2. Which version of firmware you want to install

3. What were your actions before you get to the problem

I can not guess what you have done to get this problem
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
i recieve this phone in the same condition from customer

so i dont know the version ?
[P8lite Q&A, Help & Troubleshooting] sokkoban:
Try this

Bootloader must be unlocked!!!

1. Connect device with PC

2. With two buttons enter into bootloader (Volume down+Power button+MicroUSB)

3. Download this rom(B052) and execute FLASH-ALL.bat file https://drive.google.com/file/d/0B1rEfLdrJbhKX0plUjFVb3ZVSjQ/view?usp=sharing

Wait to flash rom

If everything is ok you get mobile with original firmware now you can flash via OTA last update for your device
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
thnx for the useful reply but the problem is : for unlocking bootloader imei and product serial number and product id is needed

imei i get from box

but how to get product serial number

and for product id need to dial this *#*#1357946#*#* but set is rebooting on logo

any other way to unlock bootloader

hope get authentic and useful reply for u
[P8lite Q&A, Help & Troubleshooting] sokkoban:
First try factory reset again with two buttons( Volume up+Power button)

If the problem still continue download and use this for view info about the device! https://drive.google.com/file/d/0B1rEfLdrJbhKTTZ0ZlpYd3R2VWs/view?usp=sharing

Connect phone with PC and run bat file and executable if you lucky may be get info about unlock bootloader
[P8lite Q&A, Help & Troubleshooting] GSM-HUM:
there are 8 items

adb.exe

adbwinapi.dll

fastboot.exe

oneclick-root-for-plite.bat

recoveryp8lite.img

stockrecovery.img

update-supersu-v2.46.zip

so i only download .bat or something else ?

appreciate ur assitance
[P8lite Q&A, Help & Troubleshooting] sokkoban:
Opss

Sorry but I wrong the link. This is correct link https://drive.google.com/file/d/0B1rEfLdrJbhKWjFrVUxJdGNsTXM/view?usp=sharing

First try factory reset again with two buttons( Volume up+Power button)
[Galaxy S 4 General] lordodin912:
Made this thread to show support and wish happy holidays and new year to some of our favorite people here on XDA (no particular order) and show how much we appreciate their hard work. First, thanks to XDA, and everyone who works on it!

Special thanks go out to all these people, without whom we wouldn't enjoy our device(s) the way we do today:

[MENTION=631273]Chainfire[/MENTION] [MENTION=5403589]Albe95[/MENTION] [MENTION=4272718]hawkerpaul[/MENTION] [MENTION=4619873]gharrington[/MENTION] [MENTION=3322708]albinoman887[/MENTION] [MENTION=4200595]josegalre[/MENTION] [MENTION=4648515]AL_IRAQI[/MENTION] [MENTION=2430512]raffaele88[/MENTION] [MENTION=5650065]peppe130[/MENTION] [MENTION=5010221]sombree[/MENTION] [MENTION=6798823]TechVeerA[/MENTION] [MENTION=3562083]wanam[/MENTION] [MENTION=3068641]jamal2367[/MENTION] [MENTION=4401403]friedrich420[/MENTION] [MENTION=4543502]slim80[/MENTION] [MENTION=6314676]Tamri[/MENTION]da [/MENTION] [MENTION=6046038]Ross Korolov[/MENTION] [MENTION=3332811]faux123[/MENTION] [MENTION=4751298]Carotix[/MENTION] [MENTION=1670609]shoman94[/MENTION] [MENTION=4593553]Mahdi786[/MENTION] [MENTION=5244417]alemtro95[/MENTION] [MENTION=3860593]semdoc[/MENTION] [MENTION=1627369]adizzle[/MENTION] [MENTION=1835300]Ghost4[/MENTION]4 [MENTION=981123]dontpannic[/MENTION] [MENTION=4376579]BoBCatRoM[/MENTION] @-JKay- [MENTION=5899304]Tkkg1994[/MENTION] [MENTION=5903578]rullert[/MENTION] [MENTION=3666499]vladnosferatu[/MENTION] [MENTION=630648]blk[/MENTION]-jack [MENTION=4291281]F4bioo[/MENTION]

...continue next post...
[Galaxy S 4 General] lordodin912:
... [MENTION=4419114]rovo89[/MENTION] @alucard_24 @edzamber @asgard [MENTION=1488698]rayman95[/MENTION] [MENTION=6046196]TQue[/MENTION]tski [MENTION=329570]malybru[/MENTION] @Grommish [MENTION=6032143]Seik19[/MENTION] @Hawke84 [MENTION=4829924]Synergy510[/MENTION] [MENTION=6304619]MZO[/MENTION] [MENTION=3099681]XeoNoX[/MENTION] [MENTION=6253646]luistro[/MENTION] [MENTION=4581600]ISF[/MENTION] [MENTION=5266778]JASONRR[/MENTION] @FabioSan @dandroid13 [MENTION=4323143]Skipjacks[/MENTION] @Exel [MENTION=5137082]TJSteveMX[/MENTION] [MENTION=3101740]Towle[/MENTION]. [MENTION=5580710]ShinySide[/MENTION] @hanspampel [MENTION=3125148]KennyG123[/MENTION] @AhmadRkein [MENTION=4342818]pvsgh[/MENTION] [MENTION=6576153]jimbomodder[/MENTION] @Dees_Troy [MENTION=6396069]Nana Ayeh[/MENTION] [MENTION=4666971]Phil3759[/MENTION] @chenxiaolong @Danvdh @angelcalibur

@-+BB+- [MENTION=824976]k0nane[/MENTION] [MENTION=5804776]Kushan02[/MENTION] [MENTION=4325945]ktoonsez[/MENTION] [MENTION=4454815]jovy23[/MENTION] @iB4STiD [MENTION=5047159]Tylog[/MENTION]

@evil1art @AntaresOne [MENTION=2385005]invisiblek[/MENTION] [MENTION=4881555]jbats[/MENTION] [MENTION=5684962]Yousvel[/MENTION] [MENTION=6903129]ManuProN5[/MENTION] @broodplank1337 [MENTION=4921688]The Sickness[/MENTION] @googy_anas @Fenny.....and everyone else involved with the s4 forums!! Truly amazing work from all of you here on xda, hope everybody has a relaxing Holiday and great New Year, Thanks again!!?
[Galaxy S 4 General] Nana Ayeh:
+1
[Galaxy S 4 General] peppe130:
Thank you very much dear! I wish you happy Christmas and happy new year! :)
[Galaxy S 4 General] Whiskey103:
iFeel offended for not being mentioned.

Thread closed.

HO HO HO :D
[XDA Assist] dordian K:
Today I fired up the unlocked Samsung Galaxy S3 SGH-i747 that I just bought from BestBuy.com. Instead of the Android 4.0 it was advertised to be shipped with, it's carrying SE for Android 4.4.2, in 'Enforcing' mode (with a kernel from 05-19-2014).

The app folder doesn't show Knox, and in Settings / Security / Device administrators there's no sign of Knox. Is it possible that I'm Knox-free? :) ...or is it just hiding somewhere? :mad:
[XDA Assist] Saber:
Hi,

Thanks for using XDA assist.

According to the XDA thread below:

|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |

Looking at how the OP details the steps to root, it is clear that Knox is present in the firmware you are on.

Android versions 4.3 and 4.4 both contain Knox security built-in with the official OTA update. If you root your device, it will trip the knox counter and will void your warrenty.

I hope this addresses your questions :) - gsstudios
[Verizon LG G4] fates13:
Credit goes to [MENTION=4222336]DerekZ10[/MENTION] and [MENTION=986309]cym1124[/MENTION]

So I can't be the only one who's had proximity sensor issues after putting on a glass screen protector. The phone screen would remain black during calls and the only way to get it back up was if the other person hung up the call. Turns out you can fix the issue by recalibrating the sensor in the hidden menu.

Steps:

1. Type ##228378 in the dialer and press call. It should bring up the hidden menu

2. Select "Device Test"->"MT", it will show "system will be restarted", then choose OK.

3. After reboot, GENESIS MiniOS 3.1 screen will show up, press "individual item+power" while power button is pressed.

4. Find "sensor test", enter it(do not block the proximity sensor), the proximity sensor will be automatically calibrated. Then block proximity sensor two times to exit.

5. Find "Back to the MainList" and click it

6. Press "Normal boot+power" while power butten is pressed to reboot system

7. Make a call and test the sensor to see if the screen turns off when next to your ear and back on when pulled away from your ear.
[Verizon LG G4] CyberManiaK:
On my G4 this code doesn't work. It just try to place the Call. Is there another code I should try?

Enviado desde mi VS986 mediante Tapatalk
[Verizon LG G4] fates13:
It only works for Verizon G4's. If you have a non-Verizon G4 then you need to find the right code in the general G4 forums.
[Verizon LG G4] CyberManiaK:
Mine is verizon on 13b rooted and it doesn't work, at least with my tempered glass protector is not as bad.
[Verizon LG G4] Naemion:
works with my Verizon g4
[Verizon LG G4] motorhead_biker:
It worked thanks!
[Verizon LG G4] Neighbor395:
Thanks, worked for me on 13b.