Database Users

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")

[GUIDE] Connecting the LG G3 to Linux/ADB (Aka stop "waiting for device....")
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS ---> Edit: Thanks to Annoyingduck, we have the technique for the Verizon variant in post #5. If you are a VZW user, start with step #8 below and then replace steps 14 and 15 with annoyingducks instructions!
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.

thanks.
this will definitely help those who want to try purpledrake root

I get lost at step 9 lol.

ailima said:
A bunch of people seem to be having trouble using Linux and ADB with their new phones. This is a step-by-step guide. I hope it helps some people.
Disclaimer: I am not responsible for anything you do to your devices. Following these instructions may or may not damage your phone or computer or anything else. You understand that following these instructions is done at your own risk.
THIS GUIDE DOESN'T WORK FOR VERIZON USERS
This has been tested on Ubuntu 14.04. Other variants may require some small changes.
This has been tested on the D851 (TMobile) variant. Sprint and ATT should be the same I think.
--> NOTE: Verizon users need to connect to ADB a little differently. <-- You'll have to find different instructions.
REQUIREMENTS: You must have root access to your linux box.
1. Unplug your phone from the computer
2. Make yourself a "developer" on your phone. Settings > General > About phone > Software information ... then tap "Build number" a bunch of times until it says "You are now a developer" or something like that.
3. Go into the developer settings ... Settings > General > Developer options
4. Check "USB Debugging"
5. Plug the phone in to your computer
6. Drop down the notifications menu and click on the item that has the subtitle "Tap for more USB options". Most likely, the main title will say "Media Device (MTP)". Anyway - click on that.
7. Then choose the option "Send Images (PTP)"
8. Tap your way back Home and then eject and unplug the phone from your computer again.
http://developer.android.com/sdk/installing/index.html?pkg=tools
9. As root, edit or create the file: /etc/udev/rules.d/51-android.rules
10. Add this line (if it isn't already there) Note that the idVendor is 1004 !!! :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
11. Save the file and then run (as root):
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
12. Then as root, run:
Code:
sudo service udev restart
13. Then:
Code:
sudo killall -9 adb
14. Plug your phone in, then try
Code:
adb devices
15. Hopefully, you'll see something like "LGD85149abcd01 device" ... which indicates that it is time to celebrate.
Now go root your phone or start developing uber-apps or something else equally awesome.
If the guide was useful, don't forget to hit Thanks!
Good luck!
Frank.
PS. Special shout out to the guys who developed PurpleDrake. I hope this guide helps some of the questions that are being asked on that thread ... and eases their work load.
Click to expand...
Click to collapse
Great and useful guide Bro !

For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...

Thank you!

If you have ARCH / Manjaro or any ARCH base just type
sudo pacman -S android-udev
Plug in phone and profit

Just as an FYI to Fedora and CentOS 64 bit users: If you get an error about libraries missing you need to add the 64 bit libraries.
Code:
yum clean all
Code:
yum update
Code:
yum install glibc.i686 zlib.i686 libstdc++.i686 ncurses-libs.i686
After that you should be good.

annoyingduck said:
For Verizon, just enable debugging, connect phone, choose internet connection, ethernet (that will enable debugging), then in terminal just run sudo adb devices, the rsa key will pop up on screen, check it to always allow. Adb will show device as offline in the terminal window, now just run adb devices again without sudo and your good to go...
Click to expand...
Click to collapse
This worked for me.

I thank this guide will help too
But, don't use his files to root only the orignal purpledrake files from xda !
http://www.androidrootz.com/2014/07/how-to-root-lg-g3.html

Awesome, thanks. Always try look for those vendor ID's and stopping my phones of trying to install some darn Windows applications.
Android is Linux, why does it need Windows to function?

Thank you!
If i may to add more links for what help others:
ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.3+ (and for win 8+)
http://forum.xda-developers.com/showthread.php?t=2588979
Fastboot problems on Windows 8+ x64 with USB 3.0
http://forum.xda-developers.com/showthread.php?t=2256359
How to install ADB and Fastboot on Windows for use with Android [Guide] 2 methods
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/

Thanks!!! This really helped

Thank you
Very helpful

Thanks for the guide. Would it work on Mac OS X ?

Ths,it wroks pretty good.

Didn't work first time even though I took great care in implementing the command line steps (permissions, file name, file contents, location). Had to go back from the start to notice the PTP step! Howcome it needs to be in Picture Transfer mode? ...Not essential, as I have adb working now, but thought someone might know.
Many, many thanks! Incidentally, i'm only putting it in debugging mode to hunt down what's turning on my G3's Bluetooth by itself. I've never turned BT on nor have I paired it with anything for any reason. I've had the phone two weeks and I've turned bluetooth off a half-dozen times or so. It shows no correlation with Airplane Mode or the WiFi NFC switch or anything else - just happens while the phone is sitting unattended. If anyone has insight on that one, please share it w/me somehow.

Additional steps
If after the steps above device is not detected by sudo ./adb devices, turn off development options: click all apps button->click Settings->click General->Developer options->turn it off, change phone connection to "charging", then change connection to "Send Images (PTP)", and turn back on Developer options, run sudo ./adb devices, and it should detect the phone

Thank you very much. Works for me - LG-F460K 4.4.2

Would this work on LG G4? Currently I have the "waiting for device" problem.

Note 4 Spell Checker not Working

Hi All,
I have Note 4 AT&T vwrsion and i am currently using beta version of MM.
When i jumoed to MM the spell check was working but after a while it just stoped working and i am trying to turn it back on but no luck so far.
I have found this article explaning the steps to turn on the "Auto Spell Check" but unfortunatily this button do not exist in my phone. http://inside-galaxy.blogspot.com/2016/03/samsung-galaxy-s6-edge-how-to-enable_22.html?m=1
Can any one plz help, Thanks in advance.
P.S: i tried at&t thread, no one seams to reply there
Attached is screenshot of my keyboard settings.

Got it fixed via adb command.
- turn on developer options
- turn on usb debugging
- on your PC downlolad and install minimal adb and fastboot ( http://forum.xda-developers.com/show....php?t=2317790 )
- connect your device via usb to your PC, wait 2 minutes until adb drivers have been installed
- run the installed adb link in your start menu, a cmd window opens op
- enter: adb shell
- enter: settings put secure spell_checker_enabled 1
- close cmd, disconnect phone, spell checking is enabled

[GUIDE/TUTORIAL] Asus Transformer Pad TF300T Any version to Android 7.1 Nougat

[GUIDE/TUTORIAL/HOWTO] Asus Transformer Pad TF300T Stock to Android 7.1 Nougat with 2022 Bootloader unlock
This detailed step-by-step guide helps you transform your Asus Transformer Pad TF300T with Android 4.2.1 to a powerful one with Android 7.1 Nougat.
Don't expect Android 8 or newer on this tab, but 7.1 is already perfect ;-)
Netflix and Disney+ work.
This worked for me only with USB 2.
### I'll make a few notes using this style: PLEASE READ THEM.
Make sure you have latest official updates.
Connect tab to Wifi network.
Go to Settings > About > Update.
You may have to restart tab and do this step again to correctly fetch latest official update.
To check your tab is the correct model, go to Settings > About tablet. The details below are listed :
• Android 4.2.1 (Jelly Bean, versions from 4.1 to 4.3.1)
• GPS 7.9.11
• Wi-Fi 7.1.1.50
• BT 10.38
• Camera TF300T-000128
• Kernel 3.1.10*
• Build number
Tap 7 times on this item to unlock the developer options menu.
We need it later
It looks like J0P40D.WW_epad-10.6.1.27.5-20130902
################# TO GO FURTHER, your BOOTLOADER version MUST END IN 27.1 or 27.5 (27.5 in my case).
### If not: reboot tab and check again for system updates
### If it still not 27.1 or 27.5, go straight to the EXTRA part of this tutorial.
CHANGELOG
v14. Unlock bootloader in 2022
v13. Improved readability + Magisk v23
v12. Magisk 22.1 + minor tuto fixes
v11. Magisk 21, TWRP recovery 3.4, 14 wifi channels.
v10. Dropped SuperSU for Magisk, small tutorial improvements, Timduru ROM v39
v9. Timduru v38 and TWRP 3.3.1-0, updated pack
v8. Timduru v35 and better OpenGapps link
v7. Refresh pack v3 with ROM v32 and TWRP recovery 3.2.3-0
v6. Google Play certification + TWRP 3.2.1-0 (in new pack), Katkiss v29
v5. djibe pack v2 for shorter tutorial (now includes both UnLock_Device_App_V8 and V7)
+ STOP FORCING GPU RENDERING (slow down tab so much)
v4. Upgraded to Nougatella build25 and TWRP recovery official 3.1.1-0
v3. Details for manual update of bootloader
v2. Moved to Android 7.1 Nougat, recovery TWRP 3.1.0-0
v1. Initial release
0) BACKUP YOUR DATA
Backup SMS, photos, contacts before going any further (ex: use the backupyourmobile app).
Check that backup is located on microSD card. Then copy the backup on your PC.
1) DOWNLOAD
- djibe Transformer Pad TF300T pack v3: https://www.androidfilehost.com/?fid=17825722713688260169 or https://anonfiles.com/o2ydE3v9zf/djibe_Transformer_Pad_TF300T_pack_v3_zip
(contains Windows MTP drivers + ADB & fastboot drivers + Asus UnLock_Device_App_V7_update.apk + DMclient.apk for TF300T + ESFileExplorer 4.0.4 + KingoRoot 4.4.3.apk + official TWRP recovery 3.4.0-0 + Magisk root).
### Use Incognito web browser mode if needed to download pack.
Unzip pack on Windows desktop.
+ ROM KatKiss Android Nougat 7.1 (v39): https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
Download latest build: https://downloads.timduru.org/android/tf300t/K.A.T/KatKiss/7.x/dev/ or https://www.androidfilehost.com/?fid=17825722713688257428
Thanks to @timduru for his perfect ROMs dedicated to Transformer tabs.
+ OpenGapps ARM 7.1 Pico (Pico Pico Pico only !): https://opengapps.org/?arch=arm&api=7.1&variant=pico
+ Mitmproxy Windows Installer v7.0.0: https://mitmproxy.org/
+ microSD card (FAT32 format), copy the zip files from Katkiss ROM, OpenGapps, Magisk.zip.
### If later on you have errors flashing ROM, GAPPS, MAGISK, try to use another freshly formated microSD (FAT32 partition format).
Then insert it in the tab.
2) INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PAD TF300T
- In Android, go to Settings > About tablet.
Tap 7 times on "Build number", a message says Developer menu is unlocked.
Go to Settings > Developer Menu > check USB debugging ON.
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the Windows Command Prompt, type :
Code:
shutdown -o -r -t 0
it opens Windows Recovery menu:
Go to Troubleshoot > Advanced Options > Startup settings > Restart
At reboot, hit 7 (Disable driver control).
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf > Right click > Install.
Force driver install and wait until a success message prompts (it may never come Nevermind).
Repeat operation with android_winusb.inf .
You can plug tab in USB for driver install completion.
### Not working ? Run the CMD has administrator and write this command :
Code:
RUNDLL32.EXE SETUPAPI.DLL,InstallHinfSection DefaultInstall 132 c:\...\android_winusb.inf
### c:\...\android_winusb.inf being the path to each .inf file. Repeat for each .inf file.
when finished driver installation, reboot PC as usual.
Tab should normaly be seen in Windows explorer as ASUS Transformer Pad TF300.
Make sure MTP file transfer protocol is active on the tablet.
3) ROOT TF300T
Thanks to @d.l.i.w and @GloGlorius, it works in 2022 !
Tablet must be fully charged.
In Android, go to Settings > Security > switch Unknown Sources ON.
Connect tablet to PC.
Copy Kingoroot 4.4.3.apk, ESFileExplorer.apk, DMClient.apk and UnLock_App_V7_update.apk to tablet.
Connect tablet your Wi-Fi network.
Windows connection to Wi-Fi network must be Private (https://support.microsoft.com/en-us...-windows-0460117d-8d3e-a7ac-f003-7a0da607448d),
On the right side of the taskbar, select the Wi-Fi network icon.
Under the name of the Wi-Fi network that you’re connected to, select Properties.
Under Network profile, select Private.
Using File Manager app, install kingo-root-4-4-3.apk and other apps stated above
Launch KingoRoot app.
Tap on One Click Root button.
Wait until ROOT SUCCEEDED is displayed.
Quit app.
### If root fails: wipe data/factory reset and use KingoRoot software for Windows.
4) UNLOCK SYSTEM FILES
Uninstall any installed Unlock App.
Launch ESFileExplorer app.
Tap on top left Hamburger icon to reveal menu > Tools > switch Root Explorer ON.
Kingoroot pops up: Request for root permission, tap on Allow.
Still within ESFileExplorer, go back to Menu > Local > 0.
Long press on DMClient.apk > Copy
Back to Menu > Local > Device > system > app > Paste > Overwrite.
Long press on DMClient.apk > More > Properties > Permissions: Change
Check on as follows:
Owner: Read + Write
Group: Read
Other: Read and confirm with OK
Long press on DMClient.odex > Rename > DMClient.odex.backup
Repeat the same process for UnLock_App_V7_update.apk.
Then restart tablet.
5) SETUP MITMPROXY
Back to computer.
Install Mitmproxy for Windows v5.0 (or 7.0.0) (thx to @Trigve and @Space Gate).
If using PC with Wi-Fi, it must be set as a Private network (see above).
Tablet and computer must be connected to the same router/box.
Find local IP:
- For Wi-Fi connection
Select Start > Settings > Network & internet > Wi-Fi and then select the Wi-Fi network you're connected to.
Under Properties, look for your IP address listed next to IPv4 address.
- For Ethernet connection
Select Start > Settings > Network & internet > Ethernet.
Under Properties, look for your IP address listed next to IPv4 address.
From Windows Start Menu, start mitmweb and grant network access.
Default web browser opens with GUI with url: http://127.0.0.1:8081/#/flows
Go to Options > check Display Event log and click Edit Options.
Scroll down to edit following options:
- block_global: unchecked
- showhost: checked
- ssl_insecure: checked
- tls_version_client_min: UNBOUNDED selected
- tls_version_server_min: UNBOUNDED selected
6) Transformer Pad TF300T BOOTLOADER UNLOCK
Back to tablet.
Go to Settings > Security > Screen lock > PIN.
Set 0000 and retype it on next screen.
Go to Settings > Wi-Fi, long press on local Wi-Fi network > Modify network
Check Show advanced options > Proxy settings > Manual
Proxy hostname: local ip of PC (see Step 5)
Proxy port: 8080
> Save
Disconnect and reconnect to Wi-Fi.
On tablet, launch stock Browser app.
Browse on tablet to mitm.it
Scroll down to download "Android certificate".
Set name: cert > OK, message tells: "cert installed"
Start Unlock Device Tool app.
Scroll down to agree to End User License Agreement.
Check I have read and... and tap on OK.
Check Agree and Press to unlock your device button.
Enter your PIN: 0000 and tap OK
Yipeeeeeeeeeee
After reboot , "The Device is UnLocked" is written on top left screen during boot logo.
Decrypt partitions: go to Settings > Security > Clear Credentials
7) FLASH TWRP 3.4 RECOVERY
Charge tab to 100% before continuing.
Start it in bootloader mode: hold Power + Volume- until you see 3 icons and release buttons.
Connect it to PC.
Open a Windows command prompt on the /djibe pack folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
or while in /djibe folder, type cmd in Windows address bar and confirm with Enter.
### Use fastboot.exe provided in archive. Latest Google binaries won't work.
In Windows Command Prompt (not Windows Powershell !), type:
Code:
fastboot devices
.
If the serial number is written, tab is well connected.
### If not: try this command :
Code:
./fastboot devices
### If still fails: try another USB port
### If still fails: Launch Windows Command prompt in Administrator mode
### If still fails: Check Universal Naked drivers installation
Now type:
Code:
fastboot -i 0x0b05 flash recovery twrp-3.4.0-0-tf300t.img
and wait for the "finished" success message,
### If it fails, try other tricks like above (change USB port, Run Command prompt in Administrator mode, redownload TWRP from official site)
then type:
Code:
fastboot -i 0x0b05 reboot-bootloader
and confirm with Volume+ to load RCK (recovery), it is now TWRP 3.4.
### FROM NOW ON, ONLY USE TWRP RECOVERY TO WIPE DATA OR PARTITIONS, never again bootloader's Wipe data icon !!!
8) SET FILESYSTEM TO F2FS AND NANDROID BACKUP
F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
On TWRP first launch, check Never show this screen during boot again, then Swipe to Allow Modifications.
Go to Backup, make sure System, Data and Boot are checked.
Now tap on Select Storage button > set it on Micro SDCard,
Swipe to Backup.
Tap on the Home button.
Now go Wipe > Advanced Wipe.
Select Dalvik / ART Cache, System, Cache, Data, Internal Storage and Swipe to Wipe (NOT MICROSD).
Tap on Back button (to Advanced Wipe Menu).
Select Cache partition > Repair or Change File System > Change File System > F2FS and Swipe.
Go Back and back to Advanced Wipe Menu.
Select Data partition > Repair or Change File System > Change File System > F2FS and Swipe.
Tap on Home button.
9) FLASH ANDROID + GOOGLE APPS +/- MAGISK
Still on TWRP Home screen, Install > Storage: Internal Storage and change it to microSD card > OK.
### If it fails, use Kang Recovery (without F2FS partitions): https://androidfilehost.com/?fid=24052804347781183
Select KatKiss-7.1_TF300T*.zip, and Add More Zips,
then open_gapps-arm-7.1-pico*.zip and Swipe to Install.
### If it fails, install zips 1 by 1, make sure microSD is valid and that you downloaded OpenGapps ARM 7.1 PICO version.
OPTIONAL --------------
Go to Reboot > Recovery.
Back to TWRP, go to Install > Magisk.zip and Swipe to install.
Be patient.
Android 7.1 is installed.
When done prompts, tap on Wipe Cache/Dalvik and swype to confirm, wait.
Disconnect tab from PC.
Then Reboot System.
Let the tab start (long time).
10) ANDROID 7.1 Nougat
On Android first launch, immediately manually toggle Wifi ON or you'll run into an app crash (Wifi toggle button is on bottom right of screen).
If your Wi-Fi network is not listed, scroll down to Don't use any network for setup (and refer to chapter 12 to access it again)
Configure Android as you like.
Go to Settings > Performance
Check Set clock values on boot
For Maximum frequency, select 1700 MHz.
I/O Scheduler set zen and Set value on boot
In Settings > Mediascanner filters, uncheck Scan.
In Settings > About tablet, tap 7 times on build number, it unlocks the Options for developers in Settings.
Enter this new menu.
In the Hardware acceleration, make sure Force GPU rendering is NOT checked !!!
11) ROOT WITH MAGISK (OPTIONAL)
Magisk root is started with Android, no need for extra manipulation.
You can manage Superuser permissions and Magisk modules from Magisk Manager app.
12) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Kernel Adiutor for advanced overclock
- KAT App to enhance Audio: https://forum.xda-developers.com/transformer-tf300t/development/app-t2824215
- Any Magisk Module or Xposed Module.
- Your tab doesn't see your local Wifi network? You are probably european and your Wifi is set to channel >= 11.
Go to Settings > Wi-Fi > 3 dots icon > Advanced > Change wifi regulatory domain > EMEA and Rest of World.
Reboot tablet, you now see your Wi-Fi listed.
### If not:
Go to Settings > Security > Switch Unknown sources ON
Download from Play Store Smartpack Kernel Manager or with KatBrowser go to m.apkpure.com
Reboot to TWRP recovery (hold power to shutdown > long press on Reboot)
Go to Mount > Check System partition
Go to Install > flash Magisk*.zip
Reboot > System
With Smartpack Kernel Manager, edit build.prop
Look for ro.wifi.channels and set a value of 14 (ro.wifi.channels = 14)
Reboot tab to list all Wifi networks.
- To uninstall Magisk, rename Magisk-v23.0.apk to uninstall.zip and flash it with TWRP recovery
- Edit build.prop
Reboot to recovery > Mount > select System
adb devices
adb root
adb remount
adb pull /system/build.prop
Edit with Notepad++ and save
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
That's it.
Enjoy ;-)
Thanks : Timduru, @d.l.i.w, @GloGlorius, AOSP dev, TWRP team, ChainfireSuperSU, TopJohnWu
---------------------------------------------------------------------------------------------------
EXTRA - UPGRADING BOOTLOADER VERSION OF ASUS TRANSFORMER PAD TF300T
- Either use latest official updates in Settings -> About -> Update (While connected to Internet).
But if you are here, it seems to fail ;-)
- Manually update
In your bootloader version, check for the 2 first letters.
If the letters are corresponding, download the file from the official link.
US : http://dlcdnet.asus.com/pub/ASUS/Ee...7.1996726876.1498828408-1286149849.1498586515
WW : http://dlcdnet.asus.com/pub/ASUS/Ee...7.1996726876.1498828408-1286149849.1498586515
CN : http://dlcdnet.asus.com/pub/ASUS/Ee...4.1996726876.1498828408-1286149849.1498586515
JP : http://dlcdnet.asus.com/pub/ASUS/Ee...4.1996726876.1498828408-1286149849.1498586515
TW : http://dlcdnet.asus.com/pub/ASUS/Ee...7.1996726876.1498828408-1286149849.1498586515
Now, unzip the archive once to obtain it like this : WW_epad-user-10.6.1.27.5.zip (WW or whatever 2 letters you require)
Rename WW_epad-user-10.6.1.27.5.zip to EP201_768_SDUPDATE.zip .
###Beware not to rename it to EP201_768_SDUPDATE.zip.zip !
Copy EP201_768_SDUPDATE.zip to the root of a microSD card formatted in FAT32.
Insert microSD in TF300T shut down.
Start tab in Bootloader Mode (Power + Volume-).
Go to Recovery Mode (RCK)
Flash zip, reboot.
Normally it worked ;-)
Check bootloader version again for xxx.27.5 .
Start this tutorial from start again if bootloader ends in 27.5 .
If not, ask for help in this thread.
-----------------------------------------------------------------------------------------------------------------
KEYBOARD STUCK TO QWERTY
Thanks to @BotAlex
Go to Settings > Apps > AOSP keyboard.
Disable app and delete app data.
Reactivate app.
It should be fixed.
Or install another keyboard like Gboard.

hello,
assume :
Select /cache partition -> Repair or Change File System -> Change File System -> F2FS, Swipe.
Go Back and back to Advanced Wipe Menu.
Select /cache partition -> Repair or Change File System -> Change File System -> F2FS, Swipe.
Tap on Home button.
is :
Select /cache partition -> Repair or Change File System -> Change File System -> F2FS, Swipe.
Go Back and back to Advanced Wipe Menu.
Select /data partition -> Repair or Change File System -> Change File System -> F2FS, Swipe.
Tap on Home button.
Best regards.

I was under the impression that ONLY the data partition benefits from converting to f2fs

bonzoe said:
I was under the impression that ONLY the data partition benefits from converting to f2fs
Click to expand...
Click to collapse
You are right! It is very important to convert /Data only to F2FS, never /Cache, never /System.

Flash twrp3 recovery
Hi
I did like every step..
But at step 4 I get the succes messages and the finished messages But it just normally restarts?
I dont know what I am missing at this point. I did however never got a succes messages after installing the android_winusb.inf
Please shine some light!
Thank you

So, is there an advantage to using TWRP 3.0.2.0 over the KANG TWRP 2.8.7.2 that timduru says to use in his KatKiss 6.0.1 rom?

ImaPoBoy said:
So, is there an advantage to using TWRP 3.0.2.0 over the KANG TWRP 2.8.7.2 that timduru says to use in his KatKiss 6.0.1 rom?
Click to expand...
Click to collapse
Nope! Please stay on Kang TWRP as advised by Timduru in order to avoid any known issues caused by TWRP 3.0! Ever follow his install instruction for KatKiss 6.0.1 carefully.

bonzoe said:
I was under the impression that ONLY the data partition benefits from converting to f2fs
Click to expand...
Click to collapse
I read this and other IRL tests :
https://forum.xda-developers.com/showthread.php?t=2697069
Came to conclusion F2FS is great. I'd appreciate your advice.

ebonit said:
Nope! Please stay on Kang TWRP as advised by Timduru in order to avoid any known issues caused by TWRP 3.0! Ever follow his install instruction for KatKiss 6.0.1 carefully.
Click to expand...
Click to collapse
Never experienced any problems with any Timduru creations.
What are they ? (to improve mu tuts).
Thx for help.

Was trying to reply to this message :
Hi
I did like every step..
But at step 4 I get the succes messages and the finished messages But it just normally restarts?
I dont know what I am missing at this point. I did however never got a succes messages after installing the android_winusb.inf
Please shine some light!
Thank you
Click to expand...
Click to collapse
I'm having the same issue (I think)
On win 10, I never get confirmation message for the winusb driver (I got it for the apxusb), and the SN of my tab shows as ????????? when I try to get fastboot devices in step 4.
I tried on a win7 machine but I cant install the drivers (INF file you selected doesn't support this method of installation)
Any help greatly appreciated ofc

Eypisod said:
Was trying to reply to this message :
I'm having the same issue (I think)
On win 10, I never get confirmation message for the winusb driver (I got it for the apxusb), and the SN of my tab shows as ????????? when I try to get fastboot devices in step 4.
I tried on a win7 machine but I cant install the drivers (INF file you selected doesn't support this method of installation)
Any help greatly appreciated ofc
Click to expand...
Click to collapse
Simply flash Kang TWRP 2.8.7.2 !!! (https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479). This is the right one for TF300T.

ebonit said:
Simply flash Kang TWRP 2.8.7.2 !!! (https://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479). This is the right one for TF300T.
Click to expand...
Click to collapse
Will I be able to do that without the drivers ? I'm under the impression that fastboot doesn't see my tab so I can't install a recovery.

I can't seem to pass the PC to tablet connection step. What could go wrong?
My PC's OS is Windows 10 Pro, 32bit version. I followed the below guide:
2 - INSTALL WINDOWS DRIVERS FOR ASUS TRANSFORMER PAD TF300T
- Windows 8/10 :
On keyboard, type combo : "Windows key + R"
In the command prompt, type : shutdown -o -r -t 0
it opens Windows Recovery menu:
Go to Troubleshoot -> Advanced Options -> Startup settings -> Restart
At reboot, hit 7 (Disable driver control) and follow instructions for Windows Vista/7.
when finished driver installation, reboot PC as usual.
- Windows Vista/Windows 7 :
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
You can plug tab in USB for driver install completion.
Click to expand...
Click to collapse
Both installations responded "sucessful".
I then connect my TF300T to the PC with original charging/data cable, my PC doesn't seem to recognize the tablet. If I go to device manager, I will see an unknown USB with yellow (!).
What did I do wrong?
Thanks,

Eypisod said:
Will I be able to do that without the drivers ? I'm under the impression that fastboot doesn't see my tab so I can't install a recovery.
Click to expand...
Click to collapse
Please download the Asus PC Suite "ASUS PC Sync V1.0.97": https://www.asus.com/de/supportonly/ASUS Transformer Pad TF300T/HelpDesk_Download/
Install the PC Suite on your PC. Connect your Tablet with the PC via USB. Windows will ask for the driver. Point Windows on the folder of the PC Suite. The drivers will be there.

ebonit said:
Please download the Asus PC Suite "ASUS PC Sync V1.0.97":
~~~[link deleted because new members can't post outside link]
Install the PC Suite on your PC. Connect your Tablet with the PC via USB. Windows will ask for the driver. Point Windows on the folder of the PC Suite. The drivers will be there.
Click to expand...
Click to collapse
Still does not work.
*Windows did not ask for the driver.
*When try to update the driver through device manager (pointing to the folder:
ASUS Android USB Drivers
the result shows:
Update Driver Software - Unknown USB Device (Device Descriptor Request Failed)
The best driver software for your device is already installed
Windows has determined the driver software for your device is up to date
Same thing when I tried the "Universal Naked driver".

taz_devil said:
Still does not work.
Click to expand...
Click to collapse
Look at this site: http://gsmusbdriver.com/asus-transformer-pad-tf300t. There you will also find "how to install the USB driver"!
PS: First of all, please check whether on your tablet "USB debugging" is checked on or not. If not check it on!
Then connect your tablet with the PC again. Open the device manager. If there is seen "Android Device" ->ASUS Android Composite ADB Interface or something like that and "Portable Devices"->TF300T, your tablet is known. Then you may check the driver if an update is necessary .

ebonit said:
Look at this site: ~[deleted] There you will also find "how to install the USB driver"!
PS: First of all, please check whether on your tablet "USB debugging" is checked on or not. If not check it on!
Then connect your tablet with the PC again. Open the device manager. If there is seen "Android Device" ->ASUS Android Composite ADB Interface or something like that and "Portable Devices"->TF300T, your tablet is known. Then you may check the driver if an update is necessary .
Click to expand...
Click to collapse
I've done all those things. I am wondering if my data cable is the culprit. Ever since Android 4.x.x whenever I am charging this tablet, and when the battery is 80% or higher, the screen will wake up and the speaker beeps. I have to mute the speaker and over the screen when charging.

djibe89 said:
I read this and other IRL tests :
https://forum.xda-developers.com/showthread.php?t=2697069
Came to conclusion F2FS is great. I'd appreciate your advice.
Click to expand...
Click to collapse
Sorry for late reply, I have been on holiday.
All I know about f2fs is that Timduru recommends using it for data partition on his build. I just follow the experts advice when flashing.

djibe89,
Great job you did here!
Just a few comments. Timduru clearly emphasizes the following points in his installation guide and your guide may cause some confusion under the TF300T owners. I have seen newcomers on the Katkiss threads that had problems with their first install due to not following and using the prescribed versions and steps.
1) Timduru advises only to use twrp_tf300_kang_2.8.7.2.img and not TWRP 3.0.2-0
2) It is also suggested that UnLock_Device_App_V7.apk rather be used as some people had problems with V8.
3) He also suggests using UPDATE-SuperSU-V2.79-20161211114519.zip be used, but does not stipulate not using V2.52 which means this one is optional, your choice.
4) He also advises to ONLY change /data to from ext4fs to f2fs for /data and NOT to do this for /cache.
Just again, excellent job and thanks for sharing.

Hi, thx for posting.
I enhenced the tutorial with your statements.
However, for the TWRP and F2FS notes, it is related.
2.8 TWRP had problems with F2FS, and were buggy until latest 3.02-0. I have this version on all the devices I hack and have complete faith in it.
Enjoy.
See you

Frustated with Google News Application

As the title says, I'm fed up with the Google News Application. But the thing is., It is installed as a system app and I don't want that- Disable is the only option that exists for me. I've been disabling it everyday. Even I've disabled Auto-Update for that but still it ENABLES by itself and even UPDATES BY ITSELF.
I've even seeked the help of customer care but they told me to visit SERVICE CENTRE and I even did the same. When I visited the service centre, they just Hard resetted my device and I told them that I've done it more than 6 times at home. They started arguing with me thereby accusing me with bad words...
My phone is still under warranty and I don't want to lose it by installing TWRP and rooting it...
Any kind SUGGESTIONS are HEARTLY WELCOME.

Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers

SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Okay. Thank you. But it gets only HIDDEN not completely uninstalled. As of I know, I can't uninstall permanently without root access.

SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..

PiXinCreate said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..
Click to expand...
Click to collapse
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.

SnapDrag910 said:
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.
Click to expand...
Click to collapse
Honestly speaking, in New to using ADB... But knew sp flash tool and I had thought that both are similar but not.
Are Nokia drivers are same as Google drivers?
Can you share me the step by step procedure is you enough time now, sir?
I just downloaded latest usb driver from developer.android.com

Hey Guys let me tell you I do get automatic installation (via Google Play) for the Google News app (yes frustrating ) but what I did is uninstalled updates emptied it's data and forced stop / disabled it.
As of this comment I do get automatic installation request via Google Play but Google News doesn't updates. This worked for me.

[Guide] VoLTE/VoWiFi/ViLTE/EVS HD+ codec [no root] latest OOS 11.0.7.7

To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “qud.win.1.1_installer_10061.1.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
You should see some Chinese characters on display
8) Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6"
9) In CMD:
ADB shell
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
10) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator”, select device with filled "EFS" and "Banner" fields and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps in PDC.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
11) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
12) In ADB:
ADB reboot
13) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
14) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
15) Disable USB Debugging if necessary.
16) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
After update to latest version VoLTE was not working again. I think we should repeats this step after every update, until OnePlus (if) fixed this issue.

Hello.
Does the step 9 has to be done , becouse i cant get a connection with efs explorer. Its just blank. I ask becouse i have volte and vowifi activated but my phone wont turn automatic to vowifi when i get a wifi connection. i have to first turn off volte and reboot that the phone connects to vowifi

zorantoma
Hi. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?

vip77 said:
To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “QUD.WIN.1.1+Installer-10037.3+Setup.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
ADB shell
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You should see some Chinese characters on display
8) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator” and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
9) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
10) In ADB:
ADB reboot
11) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
12) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
13) Disable USB Debugging if necessary.
14) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
View attachment 5202729View attachment 5202731View attachment 5202727View attachment 5202725
Click to expand...
Click to collapse
hi i have a problem, i can't connect my op8 to efs file explore, it tells me it is not supported

Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot

vip77 said:
Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot
Click to expand...
Click to collapse
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator

this is what i get when i run efs explorer

patonovich said:
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator
Click to expand...
Click to collapse
zorantoma said:
this is what i get when i run efs explorer
Click to expand...
Click to collapse
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.

vip77 said:
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.
Click to expand...
Click to collapse
WOW thanks

patonovich said:
WOW thanks
Click to expand...
Click to collapse
Please report if everything went well. Good luck.

del

Thank you, it worked.
BR

Working great on OP8T,
Before this guide the Volte profile was change to the default oversea profile.
Thanl you.
UPDATE -
for some reason the OVERSEA profile is active , and volte is lost.
after that i change overideconfig files to Read only after
i copy the file to efsprofiles ,
its work for now for two days in row ,
before that the phone change to ovesea profile in half day.

not working :/
i tried exactly this and not working op8t

Grigiac said:
not working :/
i tried exactly this and not working op8t
Click to expand...
Click to collapse
What exactly "not working" which step?

vip77 said:
What exactly "not working" which step?
Click to expand...
Click to collapse
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.

vip77 said:
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.
Click to expand...
Click to collapse
yes, i did it with pdc on my last device op6 with other guide and work great
but now i have new device and tried with this guide..
and im using slot 1
i have no idea why its not working :/

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
On which country are you?

Dreamelba said:
On which country are you?
Click to expand...
Click to collapse
Israel
tried India & telfonica uk
Nothing work