Develop Bugs

[Q] MTP USB Device?

I thought I was doing great after uninstalling bloatware. However, when I tried to connect my Note 2 to my PC via USB I received the error that MTP USB Device driver could not be loaded. Apparently I must have uninstalled something on my Note 2 that is not allowing me to connect to the PC via USB. I have been searching for days, read many postings with the same problem, downloading various Driver apps to no avail. I even downloaded and installed Samsung Drivers which also did not work. I still can use my USB plug from NOTE 2 to my Flash Drive to get stuff transfered to/from Note2/PC.
It never ends. Fix one thing and then another pops up. LOL
What else can I say except - H-E-L-P.

What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Click to expand...
Click to collapse
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.

asctony said:
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.
Click to expand...
Click to collapse
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?

AE74 said:
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?
Click to expand...
Click to collapse
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.

asctony said:
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.
Click to expand...
Click to collapse
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/

AE74 said:
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/
Click to expand...
Click to collapse
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.

asctony said:
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.
Click to expand...
Click to collapse
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.

AE74 said:
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.
Click to expand...
Click to collapse
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.

asctony said:
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.
Click to expand...
Click to collapse
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?

SUCCESS-Thanks to Y-O-U!!!!
AE74 said:
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?
Click to expand...
Click to collapse
Yes, I uninstalled both of those. Re-installed both Service Mode and MTP Application, powered off both PC and Note 2. Rebooted, USBd Note 2 to PC and SUCCESS!!!!!!!!!
Thank you very much for your help!!!!! You are no longer a Jr. U R A SR!!!

[Q] Really nervous about accidentally bricking, so just some cautionary questions...

So I have an Optimus G LS970, added a couple apps, but other than that it's pretty basic. I'm wanting to root this device and eventually add a custom rom on it perhaps, but I've very new to this and don't want to accidentally brick my device.
1) I've been looking for stable linux rooting methods, the only one I've found that looks promising is here, but it's 2 years old. Does anyone know anything about it's stability for android 4.1.2, kernel 3.4.0?
2) In order to transfer files (music, pictures, pdfs/ebooks) to/from my device it needs to be mounted, but I haven't been able to mount it for this (or any other) purpose at all. It shows up as connected (command "lsusb" shows "Bus 002 Device 028: ID 1004:631d LG Electronics, Inc.") but it won't mount. Will this be possible once rooted, or is there some other cause to this?
3) Once rooted, I want to get rid of some of the Preinstalled apps but I'm not sure which will lead to instability and which would be fine to remove, does anyone know where I can check this, or would I just need to list all the apps I don't want on my phone and have you all tell me on an app-by-app basis which is safe to remove?
4) Lastly, when it comes to using alternative app markets, I haven't had much luck. I was trying to test using alt stores with f-droid and nothing showed in the lists, so I don't know if that's a thing with f-droid or my device. Is there anything you need to do to use alt app stores aside from enabling it in the system settings, and installing the app store's .. app?
Thanks in advance!

JustAk said:
So I have an Optimus G LS970, added a couple apps, but other than that it's pretty basic. I'm wanting to root this device and eventually add a custom rom on it perhaps, but I've very new to this and don't want to accidentally brick my device.
1) I've been looking for stable linux rooting methods, the only one I've found that looks promising is here, but it's 2 years old. Does anyone know anything about it's stability for android 4.1.2, kernel 3.4.0?
2) In order to transfer files (music, pictures, pdfs/ebooks) to/from my device it needs to be mounted, but I haven't been able to mount it for this (or any other) purpose at all. It shows up as connected (command "lsusb" shows "Bus 002 Device 028: ID 1004:631d LG Electronics, Inc.") but it won't mount. Will this be possible once rooted, or is there some other cause to this?
3) Once rooted, I want to get rid of some of the Preinstalled apps but I'm not sure which will lead to instability and which would be fine to remove, does anyone know where I can check this, or would I just need to list all the apps I don't want on my phone and have you all tell me on an app-by-app basis which is safe to remove?
4) Lastly, when it comes to using alternative app markets, I haven't had much luck. I was trying to test using alt stores with f-droid and nothing showed in the lists, so I don't know if that's a thing with f-droid or my device. Is there anything you need to do to use alt app stores aside from enabling it in the system settings, and installing the app store's .. app?
Thanks in advance!
Click to expand...
Click to collapse
All of your questions are answered here. http://forum.xda-developers.com/showthread.php?t=2050582
And the FAQ.
1. See above
2. Install the LG drivers, link is in that OP, then tick MPT. That should transfer your files. If not, you may need to uninstall, then reinstall them.
3. DO NOT remove any apps unless you unlock! Info is in that link also.
4. I have no idea on that one.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
All of your questions are answered here. http://forum.xda-developers.com/showthread.php?t=2050582
And the FAQ.
1. See above
2. Install the LG drivers, link is in that OP, then tick MPT. That should transfer your files. If not, you may need to uninstall, then reinstall them.
3. DO NOT remove any apps unless you unlock! Info is in that link also.
4. I have no idea on that one.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
1) *EDIT* [Doesn't say anything about linux rooting, how am I supposed to install a windows drive on a linux system?] I overlooked the linux mention. Thanks! Can't find something. How/where do I find adb?
2) Ignore, see 1) [Again, how am I supposed to install the Windows driver in linux?]
3) Thanks for that. I didn't know the importance of unlocking the bootloader.

JustAk said:
1) *EDIT* [Doesn't say anything about linux rooting, how am I supposed to install a windows drive on a linux system?] I overlooked the linux mention. Thanks! Can't find something. How/where do I find adb?
2) Ignore, see 1) [Again, how am I supposed to install the Windows driver in linux?]
3) Thanks for that. I didn't know the importance of unlocking the bootloader.
Click to expand...
Click to collapse
Sorry bout that. Linux drivers are native, so they're anyway installed.
You use either fiddy629 root for Linux, or Framaroot.
Sent from my LG-LS970 using XDA Premium 4 mobile app
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
Edit. You don't have to have ADB, but there's alot of info if you google it.
Sent from my LG-LS970 using XDA Premium 4 mobile app

engine95 said:
Sorry bout that. Linux drivers are native, so they're anyway installed.
You use either fiddy629 root for Linux, or Framaroot.
Sent from my LG-LS970 using XDA Premium 4 mobile app
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
Edit. You don't have to have ADB, but there's alot of info if you google it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried fiddy619's thing here using the universal linux one. It asked me for ADB. Found that debian has "android-tools-adb" so I installed that, now there's this:
Code:
Using: /usr/bin/adb
Waiting for device... Connect your LGOG via USB in Charge Only Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Device found
Beginning Root Process
Disconnect your phone from USB
Disable USB Debugging
Enable USB Debugging
Press enter to Continue
I can't tell if this is telling me to do these things, or if it's saying it already did them. Any idea?

JustAk said:
I tried fiddy619's thing here using the universal linux one. It asked me for ADB. Found that debian has "android-tools-adb" so I installed that, now there's this:
Code:
Using: /usr/bin/adb
Waiting for device... Connect your LGOG via USB in Charge Only Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Device found
Beginning Root Process
Disconnect your phone from USB
Disable USB Debugging
Enable USB Debugging
Press enter to Continue
I can't tell if this is telling me to do these things, or if it's saying it already did them. Any idea?
Click to expand...
Click to collapse
Nevermind that, I got it working just fine. took o nly a couple seconds and it was done. Now I have "SuperSU" in my apps menu, so I'm guessing it worked.

JustAk said:
Nevermind that, I got it working just fine. took o nly a couple seconds and it was done. Now I have "SuperSU" in my apps menu, so I'm guessing it worked.
Click to expand...
Click to collapse
Awesome, glad to hear it worked! Which if you have SuperSU it should have. I too only use linux(Linux Mint specifically) and while most guides are made for Windows, things are usually easier from the linux terminal because we don't need to download drivers, android uses a modified linux kernel, etc. Welcome to the forums, glad to have you here! All the info you need is here and plenty of people will be glad to help(as engine has already demonstrated). As for the alternative app markets, Ive read plenty and tested a few but really, nothing comes close to the play store. On our phone Banks Gapps is the standard google apps package to install if you are flashing a custom rom. Just make sure you get the correct version of gapps for the version of android your rom is based on.

HPTesla said:
Awesome, glad to hear it worked! Which if you have SuperSU it should have. I too only use linux(Linux Mint specifically) and while most guides are made for Windows, things are usually easier from the linux terminal because we don't need to download drivers, android uses a modified linux kernel, etc. Welcome to the forums, glad to have you here! All the info you need is here and plenty of people will be glad to help(as engine has already demonstrated). As for the alternative app markets, Ive read plenty and tested a few but really, nothing comes close to the play store. On our phone Banks Gapps is the standard google apps package to install if you are flashing a custom rom. Just make sure you get the correct version of gapps for the version of android your rom is based on.
Click to expand...
Click to collapse
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.

JustAk said:
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.
Click to expand...
Click to collapse
This may or may not help, but when I've had issues with Linux hooking up I've had to format my SD. Something gets stuck in there that Linux just didn't like.
Sent from my LG-LS970 using XDA Premium 4 mobile app

JustAk said:
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.
Click to expand...
Click to collapse
Are you doing this with the phone turned on and booted into the os? It gives you a PTP error first, make sure the phone is in MTP. At the bottom you also have a LIBMTP error tho. I don't have much experience with debian but from what I understand it is extremely stable but the downside is that it can be a bit out of date at times. Ubuntu and all ubuntu derivatives had a major mtp flaw awhile back but it has since been fixed. Im not sure if it has been fixed in debian. Yes ubuntu is based off of debian, but just like linux mint will add things to the ubuntu base, ubuntu will do the same to the debian base. So LIBMTP MAY be out of date, Im not sure. I know that I have no problem seeing my phone from either the terminal or file browser. Check this out and see if it helps any.
If not you may have to follow engine's advice and format the sd.
EDIT: Also this might work, it is for linux mint but adding the repository and installing it should work on debian(I think) since they all use .deb files. Before ubuntu officially supported mtp by default this was the most popular work around.

HPTesla said:
Are you doing this with the phone turned on and booted into the os? It gives you a PTP error first, make sure the phone is in MTP. At the bottom you also have a LIBMTP error tho. I don't have much experience with debian but from what I understand it is extremely stable but the downside is that it can be a bit out of date at times. Ubuntu and all ubuntu derivatives had a major mtp flaw awhile back but it has since been fixed. Im not sure if it has been fixed in debian. Yes ubuntu is based off of debian, but just like linux mint will add things to the ubuntu base, ubuntu will do the same to the debian base. So LIBMTP MAY be out of date, Im not sure. I know that I have no problem seeing my phone from either the terminal or file browser. Check this out and see if it helps any.
If not you may have to follow engine's advice and format the sd.
EDIT: Also this might work, it is for linux mint but adding the repository and installing it should work on debian(I think) since they all use .deb files. Before ubuntu officially supported mtp by default this was the most popular work around.
Click to expand...
Click to collapse
The first thing you linked to (steneteg.org or somesuch) was another avenue I went down trying to solve this, but alas it resulted with much the same problems. The second link to the linuxmint forums looked very promising, the only problem with it is the ppa has been dropped by webupd8 so it no longer is available (404s).
I have just discovered earlier today that adb push/pull works for getting things onto/off of my device, but I can't use adb to mount the device to allow it to be seen with a filemanager (thunar in this case). So, that's progress I think.
EDIT : I just saw mention somewhere of androidair, have yyou any experience with this app's reliability/security?

JustAk said:
The first thing you linked to (steneteg.org or somesuch) was another avenue I went down trying to solve this, but alas it resulted with much the same problems. The second link to the linuxmint forums looked very promising, the only problem with it is the ppa has been dropped by webupd8 so it no longer is available (404s).
I have just discovered earlier today that adb push/pull works for getting things onto/off of my device, but I can't use adb to mount the device to allow it to be seen with a filemanager (thunar in this case). So, that's progress I think.
EDIT : I just saw mention somewhere of androidair, have yyou any experience with this app's reliability/security?
Click to expand...
Click to collapse
You can try searching for other places where go-mptfs is located, other ppas where it still might be. The ubuntu forums also has this as a possible solution. I haven't used androidair but I have moved files over wifi using the sshdroid app and an ssh server on my pc with great success. If you have any experience with ssh that could be a possible solution although it is obviously slower than usb. But ssh in general is a simple and great tool, also pretty secure since you are simply connected to your home wifi - as long as your wifi is secure you should be fine.
On my pc I believe its openssh that I use - plenty of tutorials out there for that - and here is the link to sshdroid in the play store. Hope this helps!
EDIT: I will also be at work until 2p.m. EST so may not be able to reply back until then - don't worry, I will as soon as I get home if you have any other issues.

How to get into Qualcomm diagnostic mode?

Hello there.
I have been having the 'stupidly set baseband to USA and unable to change back' issue with my Nexus 5x, using a European version. I live in Croatia, so as you would imagine this has meant a complete loss of signal/mobile operator/3g etc.
As per my other thread in Nexus 5x help and troubleshooting,
http://forum.xda-developers.com/nexus-5x/help/usa-baseband-set-european-model-t3252879
I have exhausted other options and have come to the realisation that as per other users issues with other phones that the use of QPST tools and using a clean QCN file to inject into my phone is the only course of action left. However, I have no knowledge of such things (not to say that I am unable to inform myself).
I emailed a developer with regards to users issues with Nexus 5 phones (not 5x), and he said that I need to enter this mode on my phone.
Could anyone help me out with this, and in general with this issue? As some have tried to help but unfortunately my thread has more of my own replies than other users. (In elaborating on steps taken to resolve my misery).
I am not looking for a 'one button fix', I have educated myself far and beyond with regards to this issue, I just need some more expert help so that I can sort this out myself.
Please, anyone?
Marko

Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko

was.once.dead said:
Thank God.
I can actually get a new phone. Help not needed in the end.
Thanks anyway.
Marko
Click to expand...
Click to collapse
glad you got your probelm fixed dont know if this will help you or others but if you press *#*#4636#*#* your phone will enter a radio diagnostics tool where you can set your preferred network type and also select your radio baseband by using the 3 dots at the top. For my 5X i can select USA BAnd or Band mode 6, Band mode 7.
sorry if this is OT and not related to your issue.

Thank you for your input. However my phone does not have those options. Only USA band, which led to this week long stress for me. Im going to be able to get a replacement device in the end, so im happy about that, but this issue is unfortunately somewhat of a one way street wherin the usual simple solutions or even more complex adb, fastboot, etc etc things do not bring about any resolutions.
Again, thanks for trying to help but its a phone to phone kind of thing.
Marko

Best advice I can give. Don't mess with the basebands

zelendel said:
Best advice I can give. Don't mess with the basebands
Click to expand...
Click to collapse
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.

clivemckracken said:
Best advice ever...
But.... If you are really hot on getting the 5x into diagnostic mode to run QPST, QXDM, etc., do this. (I did this on my 5x to obtain the QCN file to check out the NV and EFS items, grab QXDM logs, etc.)
1. Use Heisenberg's most excellent step-by-step tutorial on unlocking the boot loader, rooting the phone, and installing super user apk.
2. Once rooted, connect the phone to a PC and open up adb, then issue the adb shell command.
3. Once in adb shell, type: su -c 'setprop sys.usb.config diag,adb'
4. At this point, you should see a pop up on the phone to authorize super user access. Click to allow access.
5. Now you will probably have to load a driver on the computer for diag access. I got lucky (since I have a mess of drivers on my computer) and the driver loaded automatically. As I recall, my computer selected qcusbser.sys. Seems to be a pretty generic QCOM driver vs. an LG specific driver.
6. You now have diag access. You will have to run steps 2 - 3 after each phone reboot. In other words, these steps aren't "sticky" between reboots.
7. ????
8. Profit
I did this and it worked for me.
Click to expand...
Click to collapse
Please give me the global version of rfnv files:good:

Please give me the global version of rfnv files
Sorry, bro. I only have the values from my US version.

[Tool][Mac] Google Installer and Amazon Killer

About:
Scripts and packages to install Google services, aid in KingRoot, and disable Amazon services written for Apple OS X.
Requirements:
OS X, device wifi connected, debugging enabled, host RSA key accepted.
Notice:
This project is sleeping. Feel free to modify and redistribute. However, be warned that tampering with the scripts may cause unintended damage to your device.
Link:
Download v0.33
Usage:
Download and extract .zip file.
Run Terminal, cd into extracted GIaAK folder, then "sh install.sh".
Contributors:
kanderson88 - inspiration, collaboration
sd_shadow - insights
KingRoot - root

I am glad there are some happy Mac users here, I have made a bunch of neat scripts but never uploaded them. Good work.

Gonna give it a go, wish me luck! lol

#to re-enable Amazon Web view. Google web view doesn't currently step in and take over, probably needs permission to.
./adb shell
su
pm enable com.amazon.webview
pm uninstall com.Google.Android.webview
#affects things like Spotify Facebook login function, etc.

Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"

TripFlex said:
Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"
Click to expand...
Click to collapse
I had no issues downloading today. Using it soon.

Does this exist for windows? How about a similar tool?

can any one post command for manual install in windows ?

-waiting for device-
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.

watson007 said:
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.
Click to expand...
Click to collapse
On tablet Go into settings > device options > developer options > enable ADB.
If you don't see developer options then settings > device options > tap on build number 7 times > then tap developer options > enable ADB. You will get a pop up on your tablet asking for permission. check the box and say yes.

For Windows
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.

leejuspsa said:
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.
Click to expand...
Click to collapse
What version of FireOS are you on?

DragonFire1024 said:
What version of FireOS are you on?
Click to expand...
Click to collapse
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.

leejuspsa said:
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.
Click to expand...
Click to collapse
Did you do this before or after 5.4.0.1? We are trying to determine if uninstalling/disabling the apps is still possible on 5.4.0.1.
EDIT: Just noticed you said earlier version.

Does anyone know if this will work with the new 2017 edition?

pastorbennett said:
Does anyone know if this will work with the new 2017 edition?
Click to expand...
Click to collapse
did you end up trying it?

Can anyone modify it for linux or windows? As not everyone has a mac.

dadoc04 said:
did you end up trying it?
Click to expand...
Click to collapse
Sort of. It won't work, because Kingroot isn't yet compatible with the 2017 Fire HDs.

[Guide] Enabling VoLTE/VoWiFi v2

Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.2
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
If you prefer to not use the app, simply run this in an adb shell:
Code:
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
If you are unable to set those properties for whatever reason, like if you have returned to stock after flashing the mbn and no longer have root, there is another possibility to force VoLTE/VoWiFi; There's a secret code you can use to force-enable it, but unfortunately it does not survive a reboot (not sure why ASUS didn't make it persistent).
Enter this in the dialler:
Code:
*#*#3642623344#*#*
The number will clear itself, and you shouldn't see any output if it succeeded.
When you have done this, go to (System) Settings -> Mobile network and toggle Mobile data off then on again. You should hopefully see the VoWiFi or VoLTE icon in the status bar now, but like I said above you will have to redo this if you reboot the phone - so if you can, please use the properties method instead.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
Code:
<efstool port="2500" remote="true" baudrate="38400" password="FFFFFFFFFFFFFFFF" spc="000000"/>
You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
To get it working on the second SIM slot you will also have to run this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards

I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?

xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.

HomerSp said:
Is COM1 the only port available? What does it identify itself as in Device Manager? It should be a Qualcomm ... 902d device.
I'm on the tencent version, yeah, so it should be working for you as well.
Click to expand...
Click to collapse
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?

Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.

Cammarratta said:
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
Use serial port 'COM13'
Critical error. The requested resource is in use.
I keep getting the following error and I'm not sure what the cause may be. Is it possible that a video tutorial could be made to help out in beginning as I'm not sure what I'm doing wrong on my end.
Thank you so much for your work on this though! It is nothing short of amazing.
Does it matter which USB port we use on the device? I've tested both the bottom and the side and neither are working.
Click to expand...
Click to collapse
Make sure you dont have QPST server running. Its not required if using the tools. I ran into this issue and realized thats what it was that was using it.

How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!

Cammarratta said:
How do I make sure the server is not running? I've rebooted and checked but I'm not seeing anything/indication of it doing so. Thank you in advance!
Click to expand...
Click to collapse
Open up QPST Configuration > at the top click Server > then Stop QPST Server. After that, see if efsTools give you anything. (efsTools efsInfo)

Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though

Cammarratta said:
Hrmmm still not working on my end. Not sure what I'm doing wrong but I'll give it a rest for the time being.
My qserver keeps saying that it cannot find my USB or phone either. So I might be missing something. I'll Uninstall and try again though
Click to expand...
Click to collapse
What does it say for you? It won't find it if you turn it off. What is the COM port / driver that shows up in Device Manager

xbamaris1` said:
I changed it to that, I'm even trying this on a completely different computer to see. Now its on COM3 on the different system with that driver. I even recently did a full WW firmware flash and factory reset as well. So its pretty much completely stock other than Root and the Apps you made / modified.
Still, Critical error. Bad Command when running efsTools efsInfo
What version of the driver does it say for you?
Edit: When you're able to access efs, What does your sys.usb.state say? I have rndis,adb shown but sys.usb.config is set for rndis,diag,adb. Does your sys.usb.state have diag included?
Click to expand...
Click to collapse
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.

HomerSp said:
Preface
With this guide I can officially deprecate the other guide I wrote, as we will no longer have to hack together a solution by loading profiles for other carriers. Meaning, that this should just work provided an mbn exists for your carrier - doesn't matter from which device. This has been reported to work on TMO in the US, which did not work with my other method.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Downloads
* AsusVoLTE v1.0.1
* EfsTools 0.10 modded 1.1
* EFS items
* Xiaomi Mi 9T MBNs (optional)
Step 1 - setting props
Install the AsusVoLTE app from above, make sure to upgrade if you already have it installed. Run the app and press the Enable VoLTE button; this should set some properties on the device to force-enable VoLTE after we have also done the other steps below. If you already enable VoLTE using my old method you can safely skip this step.
Step 2 - making sure it works
Before we begin, make sure you close down QPST, otherwise EfsTools will error out because there can not be two clients connected at once.
Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
If you are connected via wifi you will need to change port to 2500 (or whatever port you used in the AsusVoLTE app) and remote to true. So the efstool line should look something like this:
You can test the connection by running this in the cmd window:
This should report back some info if everything is working. If not, try rebooting the device and redo the bits from the DIAG guide.
Step 3 - disabling mcfg
Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
If everything worked you should see no error messages.
Step 4 - writing mbn
If you are using the Xiaomi Mi 9T mbns zip from above, move it to the EfsTools directory and extract it. Now we simply need to find the mbn for your carrier.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Source code:
AsusVoLTE - Github
EfsTools - Github
Let me know if this works for you, or if you have any questions.
Regards
Click to expand...
Click to collapse
Absolutely genius, your work here is greatly appreciated everything is working perfectly VoLTE and VoWiFi with caller display
I used the EE mbn included in the Xiaomi Mi 9T MBNs provided , So for anyone on EE i can say it works without a problem.
Thank you :good:HomerSp

in device manager it shows up as
Qualcomm HS-USB Android DIAG 902D (COM13)
EDIT: It started working oddly enough. Which mi9 file would I flash for tmobile USA to test?
Thank you in advance for this!
Edit 2: got it working! Had to Uninstall, reinstall qpst, open up app and click enable DIAG, then stop the server in qstp and input the commands and it worked!

HomerSp said:
Could you try this updated EfsTools: https://github.com/HomerSp/EfsTools...modded-1.1/EfsTools-0.10-modded-1.1-win32.zip Hopefully it should work for you.
sys.usb.state is supposed to say just rndis,adb - diag will only be listed in sys.usb.config.
Click to expand...
Click to collapse
Thought so, just wanted to make sure.
https://imgur.com/a/WZvKteM is what I get. Is it possible to go back to an earlier RAW rom? I want to see if theres something in earlier ROMS that will make it work. I'm just at a loss. I'm not sure what I'm missing for this to work.

@HomerSp, thanks so much for all your efforts and skills - works a charm on ee UK using Mi9T MBN's

xbamaris1` said:
I cannot for the life of me get either method to work. Connected via USB. DIAG mode driver is loaded on COM1, even changed Baud rate on the COM port in device manager to 38400. USB method gives me "Critical Error: Bad Command" Remote method does not send any information but indefinitely runs. I'm really not sure what else to try. Im on the latest WW Firmware with Magisk root. Is there anything else I can check? Are you on the 8 GB Tencent version?
Click to expand...
Click to collapse
Same issue as you, i had it working at the start then it just stopped altogether. Hoping a next asus update could reset whatever i did to it and retry it again

Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?

killerdvd said:
Mine is getting stuck on "Use serial port 'COM5'" and nothing happens after that. Any recommendations how to make it work?
Click to expand...
Click to collapse
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.

Cammarratta said:
I had to Uninstall qpst entirely, reinstall it. Then plug my phone in, open up the Asus volteapp and hit enable DIAG, my device then showed up in device manager, then I stopped the qpst server and it worked for me just fine. Using windows 10 with latest update.
Click to expand...
Click to collapse
Thanks for the quick response. My device is already showing in device manager with COM 6. I never installed QPST since is not needed for USB connection. QPST is not even mention on OP.

I want to say the first part says that you need to have DIAG enabled.
Prerequsities
* You must have working DIAG mode. See my other thread for more information on how to set that up.
Click to expand...
Click to collapse
Which I think needed QPST installed. Unless I'm sadly mistaken, then please disregard!