Related
Confirmed working on the SPH-D700 Epic 4g, SPH-D710 Epic 4G Touch, SPH-L700/SCH-I515 Galaxy Nexus and SPH-L710 Galaxy S III
I have a DIAG script for the LG Optimus G LS970 here.
No more flashing back to Touchwiz! The following scripts enable USB Modem/Diag mode in AOSP roms(CM9/CM10/AOKP/etc). For those new to this, USB Modem mode is used to interface with Windows CDMA tools such as QPST, QXDM, DFS and CDMA Workshop. Modem mode has always been possible in stock Touchwiz roms using dialer codes. The issue has been AOSP roms not working with the modem mode dialer codes... requiring flashing back to stock TW to use it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
<--------- Doesn't work in AOSP
Few examples of what modem mode could be used for:
[HOW-TO][FIX] Repair your IMEI with QPST - updated w/ info
[How To] Upload a custom PRL to your Epic Touch 4G
[CDMA] 威盛 VIA Repair and Reprogramming
You can use a script manager to run the script. Open script manager, browse to script files on SD card, select script, set to run as SU and hit save. Do this with both scripts. Now you can use the script manager in the Widgets section to create shortcuts on the desktop for easy access. Hopefully these scripts get built into CM10 so this method is no longer needed.
You may or may not have to unplug/plugin the usb cable after new mode is set.
Samsung Epic 4G SPH-D700
Use in terminal emulator/adb or add to script.
**As of Oct 1, 2012... all SPH-D700 CM10 builds have working diag mode via *#*#8778#*#* menu thanks to bbelos. Script is not longer needed on those roms.**
**The SPH-D700 script below is confirmed working on the official TeamEpic CM9 builds**
Modem
Code:
echo MODEM USB > /sys/class/sec/switch/usb_sel
PDA
Code:
echo PDA USB > /sys/class/sec/switch/usb_sel
Samsung Epic 4G Touch SPH-D710
E4GT is working but being picky. If not detected in QPST correctly... connect phone to USB cable. While phone is in normal USB PDA mode open up QPST Service Programming > Server > Stop QPST Server. Now run the CP script(or run the commands in terminal emulator as SU) then pull out the USB cable then put it back in. Wait a second.. you should see a serial port being detected in Windows Device Manager. After port has been added and drivers installed.. go back to QPST Service Programming and enable the QPST Server. Your device should now be detected properly. If you disconnect your phone while QPST Server is running you will have to toggle it off/on again for the phone to show back up.
CP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
CP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo CP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
ALL (AP+CP)
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo ALL > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
AP v2
thx2squash
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo disable_wimax > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo enable_ap > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo disable_cp > /sys/devices/platform/i2c-gpio.17/i2c-17/17-0008/port
echo AP > /sys/class/sec/switch/set_usb_path
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy Nexus (Sprint/Verizon)
Script works great for me on my Sprint Gnex. Varied reports about script working on Verizons. If script fails use terminal emulator instead.
MODEM
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo MODEM > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
PDA
Code:
#/system/bin/sh
echo 0 > /sys/class/android_usb/android0/enable
echo PDA > /sys/devices/tuna_otg/usb_sel
echo 1 > /sys/class/android_usb/android0/enable
Samsung Galaxy S III (Sprint/Verizon/US Cellular/AT&T/T-Mobile)
Use the script!
DIAG+ADB
Code:
#/system/bin/sh
# sets DIAG mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo diag,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
MTP+ADB
Code:
#/system/bin/sh
# sets default USB mode
echo 0 > /sys/class/android_usb/android0/enable
echo 04E8 > /sys/class/android_usb/android0/idVendor
echo 6860 > /sys/class/android_usb/android0/idProduct
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo mtp,acm,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
Samsung Galaxy S IV (Should work on ATT, Tmo, Sprint, Verizon, Cricket etc...)
DIAG+ADB
Code:
#/system/bin/sh
#reboot phone to disable
#enables diag mode
echo "0" /sys/class/android_usb/android0/enable
echo "04E8" /sys/class/android_usb/android0/idVendor
echo "685D" /sys/class/android_usb/android0/idProduct
echo "diag,diag_mdm" /sys/class/android_usb/android0/f_diag/clients
echo "hsic" /sys/class/android_usb/android0/f_acm/acm_transports
echo "diag,acm,adb" /sys/class/android_usb/android0/functions
echo "1" /sys/module/ci13xxx_msm/parameters/streaming
echo "1" /sys/class/android_usb/android0/enable
Original post has been removed since this has been solved. For reference it has been moved to post 5.
Subscribed. Would love to have this feature on CM9 for the epic 4g touch.
Hi, I will try to help you as much as time allows.. But I'm easily confused as I'm trying to understand several different platforms, chipsets, models, AOS versions etc etc. So let's try to be very precise, to make sure that other people (not having an SPH-D710 or NS4G) also can benefit from this discussion. Please consider using:
(a) specific model numbers, in addition to generic names such as "SGS2".
(b) XDA-thread names/titles with posted links so that we don't have to waste time clicking on every link just to find out we have already read it. E.g. like this: "Kernel serial console on I9100".
(c) What exact steps you use to obtain a certain type of output.
Sorry for being anal about this, but it quickly gets really confusing and annoying otherwise, once you start following 30+ threads... Having said all this we can move On-Topic.
--------------------------- updated --------------------------------
[Partial re-post of PM]
Your phone is using the Qualcomm QSC6085 baseband processor, which means that your SPH-D710 is basically completely different from the GT-I9100. Thus it is most likely that the chips used (MUX) to interface with mUSB are also different, and if they are not, they must surely be wired differently to accommodate the modem chipset. The resistor values mentioned is valid for most Samsung phones using the FSA9280A mux, for other devices I have no idea, but given the laziness of Samsung they may still be implemented in various other ways..
Many issues with AOS, is with file-permissions. Another is that you may need to reboot, before certain settings take effect. Third is that there are internal mux's used/controlled by baseband with the +CMUX AT-command (and others). But one thing is for sure, Samsung doesn't want their service people to waste time with all this hacking. So yes, USB service mode (to talk to and tune the modem) via USB cable must be available somehow...
autoprime said:
While in AOSP we have no modem access. via computer or through the phone itself.
Click to expand...
Click to collapse
THAT is exactly what I find strange. You see on both my I9000 and I9100 when you connect your phone without using "modem" (as you put it), it still enables the (virtual-serial-usb) modem interface as an additional device. If I use the PhoneUtil menu to change USB to MODEM, I loose normal connection since windows ask to install proper drivers (referring to 7-CDC.) I don't know what that driver is or where to get it. (In fact it may already be present on my computer as part of the multiple driver CDC that was installed with first time use of Kies.) But perhaps need to be pointed to again, for activation...
For example, on a Vista machine the drivers are located under:
../Program Files/Samsung/USB Drivers/25_escape
There's a bunch of files located there, but the most relevant ones (for me) seem to be:
Code:
ssuddmgr.inf --> Install USB Device Management Serial Port Driver SSUD.DeviceDesc = "SAMSUNG Mobile USB At Command Port "
ssudmdm.inf --> Install CDMA USB Modem device driver SSUD.DeviceDesc = "SAMSUNG Mobile USB Modem"
ssudmdm.cat* -->
Do you also have these or are the ones you use different?
looking at my drivers.. they were indeed pulled from a Kies install and it is using those same drivers. Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem. Viewing Logcat while performing the *#*#8778#*#* PhoneUtil toggle shows no action being performed. And manually setting the mode to Modem via "echo MODEM> /sys/class/sec/switch/usb_sel" only kills the USB detection entirely.
... just the appropriate drivers for Diag mode itself. My computer can see all other phones in diag mode...
Click to expand...
Click to collapse
Which are these?
The very same ones you've mentioned establish a successful "Modem" connection to PC when using Stock Touchwiz on the SPH-D710.
Click to expand...
Click to collapse
Please post the output of:
Code:
# cat /sys/kernel/debug/usb/devices
# ls -l /sys/bus/usb/drivers/cdc_svnet
"No such file or directory" for both. The folder structures seem to be different.
Click to expand...
Click to collapse
Also, it is very important to understand that the ServiceMode application is actually running just as a wrapper for the real code, which is usually running in the baseband. This where all the hardware (MUXes, USB, i2c interfaces etc) are specified, that is used to communicate with modem. However, this may be working differently on your BP, and may be instead done in the RIL libraries, etc.
------------ Final PM Response --------------
Unfortunately it is not the drivers at fault here.. there is no detection taking place at all. The phone is not making the switch from USB PDA ---> Modem.
Click to expand...
Click to collapse
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?
2) In fact, unless you know for sure that your phone contain some (or the same) type of USB/UART switch IC (aka MUX) as in the I9100, there is no reason to expect you to have this "switch" functionality.
3) The USB drivers can do much of this virtual switching magic in software (by themselves). But really I have no clue how those things work in detail! Like I mentioned there are 7 "drivers" doing various ****, that is installed with Kies... How, and under what circumstances these are activated and used, is beyond me. (Or better, you can read how USB ports are activated on Wikipedia and about USB composite devices (CDCs) here.)
4) If you're still convinced that you need to do this switch, there is one more trick. You can try to use this tool (thanks to KickerTom in this post) to list the contents of your /mnt/.lfs/param.blk file, in readable format, or in hex-format with:
Code:
# hexdump -C /mnt/.lfs/param.blk
(You'll need busybox to do this.)
You can use that tool to write and change stuff as well, BUT: Make sure you have a full backup!! The .lfs partion is not writable in the same manner as other types of partitions. It can only "grow", and never get smaller... AFAIK.
KickerTom further states:
From my experiments it looks like the SWITCH_SEL parameter is ignored by the HW, at least I haven't observed any real effect. But you can change the UART switch by modifying a file next to the param.blk, /mnt/.lfs/sw_sel. It contains an ASCII number, by default 1. That is modem uart. Change it to 3 to get PDA uart connected, by e.g. "echo -n 3 > /mnt/.lfs/sw_sel". 5) You may need to reinstall the "Qualcomm USB Host Driver"...
Autoprime, you don't get the mass appreciation, but for those of us who know what you are trying to accomplish, we appreciate it.
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Everything between the lines was originally in the OP as part of the unsolved, [Q] Enabling USB Modem(Diag) Mode on Samsung CDMA Devices w/ AOSP thread.
Currently on the Epic 4G Touch SPH-D710 we are not able to put the phone into USB Modem/Diag mode while using an AOSP rom. This is normally toggled through the PhoneUtil apk with *#*#8778#*#*. To this date, the fix has been to restore back to a stock Touchwiz rom or to boot a Touchwiz rom off the SD card. To my knowledge, outside of the Nexus S 4G(SPH-D720), no CDMA Samsung AOSP roms have USB Modem mode working. This thread is being created to help solve this issue.. for ALL SAMSUNG CDMA DEVICES. Modem/Diag Mode works on HTC, Motorola, LG.. it should work for Samsung devices too
USB Modem/Diag Mode establishes a serial-over-usb connection which allows us to use special Qualcomm tools like QPST and QXDM to talk to our phones. We can access the hidden EFS partition including the non-volatile memory to edit all sorts of values.. we also use this for updating PRL's.. etc etc. It has it's value.. although Samsung and the carriers don't want us in there
I see USB Modem mode in AOSP being possible in two ways.
1. Since the Nexus S 4G(SPH-D720) on Sprint is on AOSP and has working USB Modem/Diag mode.. figure out how the NS4G achieves this mode.
2. Use a hardware jig of some sort to boot into USB Modem/Diag mode.
1. For the software side of things here's some highlights I've come across..
a. Logcat of Nexus S 4G(SPH-D720) while toggling USB Modem/USB modes - http://pastebin.com/TfcSHzYB
b. In terminal emulator/ADB we have "radiooptions" command with some interesting output. QXDM Enable/Disable is what interests me in there. QXDM enable would seem to allow the phone to interface with QXDM.. QXDM requires a USB Modem(Diag) Connection to talk to the phone. Attempting the "radiooptions 3" command does nothing(even on the NS4G). Only command that does seem to work is Radiff which requires a reboot to get working again.
Code:
0 - RADIO_RESET
1 - RADIO_OFF
2 - UNSOL_NETWORK_STATE_CHANGE
[B] 3 - QXDM_ENABLE
4 - QXDM_DISABLE[/B]
5 - RADIO_ON
6 - SETUP_PDP apn
7 - DEACTIVE_PDP
8 - DIAL_CALL number
9 - ANSWER_CALL
10 - END_CALL
c. Use manual commands to enable/disable the USB Modem/Diag mode as TheBeano has shown us here in his Fun with resistors (home/car dock mode + more) thread.
You can see what the current state is with this command:
Code:
cat /sys/class/sec/switch/usb_sel
You can change the state with:
Code:
echo PDA> /sys/class/sec/switch/usb_sel
or
echo MODEM> /sys/class/sec/switch/usb_sel
Currently on the E4GT SPH-D710 enabling MODEM and then connecting the device to Windows results in no connection/USB detection at all. Phone is detected in PDA mode only. In addition, using the PhoneUtil menu(*#*#8778#*#*) and setting the USB mode to "Modem" has no effect at all.
2. As for the hardware side of things, I've been reading through XDA and came across some interesting threads in the SGS2 I9100 forums. A post by E:V:A specifically that mentions putting the phone into different modes by using resistors.. which I suppose would be the same thing as the jig's people have been using to reset their ODIN flash counts.. only using different resistors: Kernel serial console on I9100.
301K looks to be what we use for the standard jigs. that is documented here: [GUIDE] How to Make a USB Jig and Get Rid of Yellow Triangle+ODIN Counter reset. I wonder if there is a mode we can force which establishes USB Modem mode ON and then use serial-over-usb.. like how it works when we set Diag mode in touchwiz roms. AdamOutler has thread dealing with the E4GT pinouts etc.. not sure if this would help at all: Processor datasheets required(E4GT SPH-D710)
Code:
xOM_0=pin E3
xOM_1=pin D2
xOM_2=pin C3
xOM_3=pin E4
xOM_4=pin F2
xOM_5=pin A3
xOM_6=pin F3
I have no idea if anything I've said helps... just putting some ideas out there and hopefully get some people who DO actually know this more advanced stuff to join in I have HTC phones, LG phones, multiple Samsung devices.. Epic(SPH-D700), NS4G(SPH-D720), E4GT(SPH-D710). I can provide any logs needed for those devices.
Random references to Diag mode and AOSP on CDMA devices:
Cannot enter Sprint ## CDMA codes on dialer, need DIAG mode! (HTC AOSP DIAG)
Updating PRL on CM7 (Samsung CDMA AOSP)
Epic Dialer Codes working on CM7
DIAG ##3424# using an AOSP ROM CM7 (Various CDMA HTC methods mentioned)
QPST DIAG Mode CM7 Aka ##3424 (HTC Droid Incredible ADR6300)
Fun with resistors [home/car dock mode + more] (Manually enable/disable UART)
-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
E:V:A said:
Ok, I know I am not coming across very clear, because we apparently have such different devices! Let me try to explain again.
1) I don't know why you insist you need to "make the switch" at all? On the I9100 there is no need to make this "switch" to get modem serial communication port. Why do you think you need it on yours?....
Click to expand...
Click to collapse
It seems the more we compare notes.. the more we see how different the I9100 and SPH-D710 really are. Without getting into technical specifics I can give you a reason why some things are so different... which is how CDMA and GSM differs really. Looking at "security" alone.. GSM uses a SIM card to authenticate on the network.. outside of the IMEI(which seems to be rather accessible on your devices) the SIM card contains most of info the network is looking for. On our devices CDMA devices, ALL of the authentication info is stored on the device itself. Carriers/Manufacturers do NOT want use touching the hidden EFS partition.. where all of our authentication values reside.. ESN/MEID, EVDO username/passwords, PRL.. etc etc. So now, the main key to accessing this hidden partition... USB Modem(Diag) Mode!
I have taken some screenshots of Windows Device Manager. Far left is my Device Manager with no phone plugged in. Middle is phone plugged in but USB Mode is set to "PDA". Right side is phone plugged in and USB Mode set to "MODEM".
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
I hope this sort of explains why our phone may be "locked down" a bit more due to how CDMA works... and also explains how I am sure that we need this USB Modem mode toggled.. and that I am positive Windows is set up properly etc etc. The issue is that we can not force the phone, while using an AOSP rom, into this diagnostic serial mode.
^^ Very good. I understand. Now, can you reproduce the middle picture for your E4GT?
autoprime said:
You can see the difference in the device manager... USB Modem mode giving us a serial diagnostic COM port. This COM port is ONLY available when the phone is set in this specific mode. ONLY when the diagnostic COM port is available can we use Qualcomm software to view the hidden EFS partition of our devices and start to tweak things. For the above image I used a Nexus S 4 G(SPH-D720) which naturally runs on AOSP and has this USB Modem mode working. This mode also work on Touchwiz roms. It does NOT work on AOSP in any other Samsung CDMA phone(the purpose of this thread).
Click to expand...
Click to collapse
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
E:V:A said:
Now, can you reproduce the middle picture for your E4GT?
Click to expand...
Click to collapse
Yes, the exact middle picture is produced on the E4GT. USB Composite and USB Mass Storage Device both show up. When toggling the PhoneUtil from PDA to Modem.. no changes in Device Manager happen. Tried toggling the UART selection in PhoneUtil as well just to see what would happen... no change as well.
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
sfhub said:
Not sure if it helps you figure out how to get it enabled, but the USB port on E4GT is able to support both PDA and MODEM mode simultaneously. They aren't mutually exclusive.
Click to expand...
Click to collapse
That's what I've been trying to tell you guys all along, and I understand my message have not been very clear. This is because I don't quite understand how this works, but that is kind of the whole point with using a USB "Composite Device". The mere fact that you are using adb and can use Kies, is good enough for you to have several virtual (including serial) connections. I already posted a link above, about this. Did you read it?
Also in the middle picture there is an additional icon that is not present in the other two, "Portable Devices". You should run a USB sniffer (eg. USBlyzer ) to find out what happens when you connect, both with the Nexus S and your E4GT.
In addition, what you have marked as "not what we want" in the RHS picture, may in fact be exactly what you want. Because I'm getting more convinced that your Qualcomm tools (from 2006) are seriously outdated. It may just be a matter of updating some drivers, but who knows...
autoprime said:
You're saying the E4GT can be seen on a computer as a mass storage device as well as enabling the diagnostic serial port.. at the same time? could you go into this more? have an example?
Click to expand...
Click to collapse
Yes, on any stock GB ROM, ##8778#, select All to have both modes enabled (AP and CP will result in just one of the modes being enabled). Haven't tested on ICS.
Any progress??
I'm sure getting the touchwiz ics source code once we get an official ota will greatly help this project.
Sent from my SPH-D710 using XDA
E:V:A said:
Any progress??
Click to expand...
Click to collapse
there are /mnt/.lfs files in touchwiz only.. they are missing in AOSP. AOSP file structure seems to be much different. I believe the issue is a lack of "Diag" code in the AOSP code itself. We need to figure out the code in the Creso4G source(Nexus S 4G SPH-D720) which allows diag mode to be enabled and port it to our own device.
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
^^ That is very good news! But I wish you could have been more specific in what drivers you found and/or installed, and what instructions you followed? (Also, what is the model number of that phone?)
gondo77 said:
I was having this same problem on my Epic 4G (non-Touch), running a custom ROM. I wanted to change my PRL manually and the phone COM port would never appear in Device Manager in phone Modem mode - nothing happened.
I was able to fix it, after considerable trial and error, but I'm not sure the fix will translate to the Touch.
It was a driver issue - the computer finally installed the correct driver that allowed the phone modem to communicate with it and appear in Device Manager.
How I found it was a fluke deal - I had pretty much given up and decided to temporarily revert back to stock Gingerbread, figuring that would allow me to change the PRL and then I could re-flash the custom ROM.
I started the stock GB conversion process and ran into a roadblock right away - the COM port wasn't showing up in Odin. The conversion instructions emphasized installing a specific driver (older) for my phone, and I knew I had the latest Windows Update drivers for the Epic 4G installed - these were installed automatically in USB debugging mode. So I went back into debug mode and uninstalled the phone in Device Manager. I then disconnected the phone from the laptop, and installed the driver (64-bit) specified in the instructions. When I plugged the phone back in, I got a successful driver install confirmation.
Then, per the instructions, I unplugged the phone and put it into "download" mode (press 1 on the slideout keyboard along with the power button). Then I launched the required version of Odin and set it up with the stock GB file I had downloaded. The next step was to plug the phone back into the PC, and when I did that, I had Device Manager open and I noticed it installed a modem I had not seen before and COM3 showed up in yellow in Odin, indicating a good connection.
At that point, I shut down Odin, unplugged the phone and restarted both phone and PC. After the restarts, I switched the phone to Modem mode via ##8778# in the PhoneUtil, then connected again via USB and voila, there was the phone modem in Device Manager, using COM5. I went on to manually change the PRL using a procedure for the Epic 4G outlined elsewhere here on XDA.
Don't know if that will shed any light with resolving this issue with the Touch, but doing something similar might be worth a try.
Click to expand...
Click to collapse
was this a touchwiz based rom.. or a aosp based rom?
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
NiteSnow said:
Running the commands below as root will allow you to put your phone into modem mode from *#*#8778#*#*
chown radio /sys/bus/i2c/drivers/fsa9480/7-0025/switch
chmod 660 /sys/bus/i2c/drivers/fsa9480/7-0025/switch
AFAIK this only works for the Crespo4G I haven't been able to test on anything else.
Click to expand...
Click to collapse
Prompts for msl, then gives a modem exception error on CM9 for e4gt.
Sent from my CM9 Epic 4g Touch using Forum Runner
SU PM enable com.samsung
I executed command disable com.samsung ot to get OTA FF18 updates since I am rooted. Then without thinking when to the google store and it told me that the background data was and it gave me an option to ok to turn it on.
Ever since them I can not get to play store it tells me I am not connected but I am . Try to do a able com.samsung command but returns disable.
any suggestions?
thnaks
I am running FF18 rooted stock
COM port not detected
EPIC 4G on stock EC05
All drivers installed
the phone goes into diagnostic mode but does not get detected.
is there any other way to get the phone to connect in CDMA ws ?
Phone was detecting on COM port earlier until i mistakenly uploaded
the Galaxy S3 SPH-L710 NV Item file which i had save from my Galaxy S3.
Instantly i lost my carrier signal and lost connection from CDMA ws.
i rebooted to check. did ##8778# goes to phon utils but even if i select MODEM under USB the modem is not
detected in COM port. just to check if my Drivers were correct or not, i connected my Galaxy S3 in Diagnostic mode..
the phone is detected under COM port but not my EPIC
I Odin back to Stock EC05 and tried without & with root. the phone is not detected on diagnostic/service mode. its detected
on PDA.
Need help to reset the phone so that i can get the phone to work on CDMA ws.
This guide is only for Android smartphones who has problems with IMEI number on MTK chipsets….
“I am not responsible for any damage caused to your phone by using this”
Method 1 – Using Engineer Mode (You must have rooted your device before doing this procedure)
Open the Dialer and type *#*#3646633#*#* you will enter the MTK Engineering Mode or using Mobile Uncle APP Hit the Engineer Mode option and choose the Engineer Mode (MTK).
On EngineerMode Chosee Connectivity and click the CDS information option.
You will see Radio information there and after tapping on it. If you have dual SIM ANDROID then you will see TWO option select any one on which you want to write IMEI with.
Click Phone 1
At “AT+” line add : AT+EGMR = 1,7,”my_first_IMEI_code”
Click on “SEND AT” button below
For second SIM tap Phone 2 and type this command
AT+EGMR=1,10,”my_second_IMEI_code”
Click on “SEND AT COMMAND” button below a second time
Reboot phone
Verify codes with *#06#* if IMEI codes are ok
Method 2 – Using Terminal Emulator (You must have rooted your device before doing this procedure)
change imei with terminal emulator
Install Terminal Emulator
Launch the Terminal Emulator app
Type SU then press ENTER button to get Superuser permission
After that, type this command then press ENTER button
echo ‘AT+EGMR=1,7,”IMEI_NUMBER”‘ >/dev/pttycmd1
If you have dual SIM add this line
echo ‘AT+EGMR=1,10,”IMEI_NUMBER”‘ >/dev/pttycmd1
Last step, reboot your phone/tablet and DONE!
Method 3 – Using MTK Droid Tool
Download MTK droid tools and Extract on your PC/Laptop
Download Universal USB Driver
Enable USB debugging on the phone then connect it to the PC (don’t enable mass storage)
Install Universal USB Driver on the PC with the phone connected; you should get a message saying drivers installed successfully.
Launch MTK droid tools on the PC (still with phone connected to PC)
MTK droid tools should detect and display your phones details
Next you need to click the ROOT button so that it will temporary have Root shell access on your phone in order for it to make the script work on the background.
Click on IMEI/NVRAM
change imei mtkdroid tool
Put your 15 Digits IMEI Number that you can get at the back of your phone inside not the back cover if you have 2 IMEI you need to put that.
Then click Replace IMEI
Restart your phone if it isn’t automatically restarted
Your IMEI issue should have been resolved
I am not responsible for any damage to your phone,do it at your own risk.
Instead we can use mobileuncle tools application from play store for this we need root
Fix Found .
Ghostrider26 said:
This guide is only for Android smartphones who has problems with IMEI number on MTK chipsets….
“I am not responsible for any damage caused to your phone by using this”
Method 1 – Using Engineer Mode (You must have rooted your device before doing this procedure)
Open the Dialer and type *#*#3646633#*#* you will enter the MTK Engineering Mode or using Mobile Uncle APP Hit the Engineer Mode option and choose the Engineer Mode (MTK).
On EngineerMode Chosee Connectivity and click the CDS information option.
You will see Radio information there and after tapping on it. If you have dual SIM ANDROID then you will see TWO option select any one on which you want to write IMEI with.
Click Phone 1
At “AT+” line add : AT+EGMR = 1,7,”my_first_IMEI_code”
Click on “SEND AT” button below
For second SIM tap Phone 2 and type this command
AT+EGMR=1,10,”my_second_IMEI_code”
Click on “SEND AT COMMAND” button below a second time
Reboot phone
Verify codes with *#06#* if IMEI codes are ok
Method 2 – Using Terminal Emulator (You must have rooted your device before doing this procedure)
change imei with terminal emulator
Install Terminal Emulator
Launch the Terminal Emulator app
Type SU then press ENTER button to get Superuser permission
After that, type this command then press ENTER button
echo ‘AT+EGMR=1,7,”IMEI_NUMBER”‘ >/dev/pttycmd1
If you have dual SIM add this line
echo ‘AT+EGMR=1,10,”IMEI_NUMBER”‘ >/dev/pttycmd1
Last step, reboot your phone/tablet and DONE!
Method 3 – Using MTK Droid Tool
Download MTK droid tools and Extract on your PC/Laptop
Download Universal USB Driver
Enable USB debugging on the phone then connect it to the PC (don’t enable mass storage)
Install Universal USB Driver on the PC with the phone connected; you should get a message saying drivers installed successfully.
Launch MTK droid tools on the PC (still with phone connected to PC)
MTK droid tools should detect and display your phones details
Next you need to click the ROOT button so that it will temporary have Root shell access on your phone in order for it to make the script work on the background.
Click on IMEI/NVRAM
change imei mtkdroid tool
Put your 15 Digits IMEI Number that you can get at the back of your phone inside not the back cover if you have 2 IMEI you need to put that.
Then click Replace IMEI
Restart your phone if it isn’t automatically restarted
Your IMEI issue should have been resolved
I am not responsible for any damage to your phone,do it at your own risk.
Click to expand...
Click to collapse
Please thank me if i helped you.
Fix found : -> http://forum.xda-developers.com/canvas-a1/general/fix-imei-perfect-fix-android-imei-t2943567
this will work in old versions, I tried in Engineer Mode v1.8.0, CDS Information is gone, had to flash my device with Android 5.1 and probably an older version of Engineer Mode app
Imei change mtk 6753 homtom ht20 pro android 6.0 sdk 23
NO ROOT
In dialler
*#*#12306#*#*
bring you to secret sub menu in mtk engineering mode
not available in this menu by using this code to *#*#3646633#*#* that option change imei is not available in NORMAL MTK Engineering MODE as CDS information witch one REQUIRED ROOT PERMISSION TO ADD CDS information IN SUB MENU IN NORMAL MTK Engineering MODE
Error shown this command is not allowed in user build. please tell what to do next
Error shown this command is not allowed in user build. please tell what to do next
kbsoni156 said:
Error shown this command is not allowed in user build. please tell what to do next
Click to expand...
Click to collapse
Put a space after AT like "AT +" and not "AT+". Rest should be written as above..
I recently found a problem while doing method 1
"This command is not allowed in user build"
So the solution for that is:-
When we are writing
AT+EGMR = 1,7,”IMEI_code”
we have to give a space b/w AT and +
so final command will be like this
AT +EGMR=1,7,"IMEI_code"
Hit thanks if it worked for u
vinaykharayat said:
I recently found a problem while doing method 1
"This command is not allowed in user build"
So the solution for that is:-
When we are writing
AT+EGMR = 1,7,”IMEI_code”
we have to give a space b/w AT and +
so final command will be like this
AT +EGMR=1,7,"IMEI_code"
Hit thanks if it worked for u
Click to expand...
Click to collapse
FWIW, this doesn't work on a BLU Vivo 5R running Nougat. Gives the same not allowed error with or without the space.
lugnut2099 said:
FWIW, this doesn't work on a BLU Vivo 5R running Nougat. Gives the same not allowed error with or without the space.
Click to expand...
Click to collapse
And just to add on, the terminal commands don't work either. They're accepted without any kind of error, but upon reboot there's still nothing there.
Thanks
It worked perfectly on Lenovo tab 2 a8-50lc, couldn't click thank you button though, its greyed out.
P.s: must have root access. Tried without root gave not allowed in userbuild.
lugnut2099 said:
And just to add on, the terminal commands don't work either. They're accepted without any kind of error, but upon reboot there's still nothing there.
Click to expand...
Click to collapse
No error message either, but not working also.
//Tested on ZTE Blade V10, Android 9, V1.8
EDIT: Already got help from someone here. Thanks! "Case is closed now".
Hello everyone,
unfortunately I bricked my Find 7a while trying to expand the 3GB internal storage with Chinese partition layout. And I don't know where it went wrong. :crying:
I already tried the Unbrick tool (Sahara) and restoring the old partition layout several times. And the partition layout recovery worked, but ColorOS says my NV partition is still invalid. It seems this partition got damaged and now my IMEI is gone and I can't use my mobile network anymore.
And sadly I figured out that the normal TWRP doesn't even show the NV/EFS partition to back (only modified TWRP do), so I don't have an backup of those partitions.
One last change would be to take an backup of another phone, anonymizing it by overwriting the IMEI and kindly sending me the copy.
If someone is willing to do so, I'd be very happy so I can reanimate my Find 7 .
I attached a tutorial:
1. Needed software:
Qualcomm QPST Diag drivers
Qualcomm QPST Tool
IMEI converter
Any hex editor, e.g. HxD Editor
2. Start phone in Diag Mode:
-Enable Developer Settings and then "USB-Debugging" on your device
Install the drivers. They are already signed, so no need to disable Windows signature check.
To enable the Diag Port, either under
a) ColorOS:
-Call *#801# and enable "Engineer Mode Toggle"
b) ADB and root access:
ADB commands:
-adb shell (only when accessing the phone with ADB from pc, not necessary when using TWRP adb terminal)
-su
-setprop sys.usb.config diag,adb
Now in the in the device manager you should see a "Qualcomm/Oppo HS-USB MSM Diagnostics 276C (COM y)" device
3. Backup the IMEI/Baseband infos:
Again, we have 2 alternative ways:
a) QFIL
Open QFIL: C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe.
Did QFIL already automatically recognize the Diag Port in the first row?
From the top menu "Tools" choose the entry "QNC Backup Restore". Backup the QNC
b) QPST
Open QPST Configuration: C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig.exe.
Under the tab "Ports" there should be the COM port from the device manager above.
If not, try "Add New Port" and untick “Show Serial and USB/QC Diagnostic ports only” and choose the right COM port and click OK.
If this doesn't help and no device shows up, add the COM-Port manually by typing the following:
Port: COMy (replace x with the number of what the device manager is showing you for the "Qualcomm/Oppo HS-USB MSM Diagnostics 276C (COM y)"
Label: You are free to name this port what you want
Then in QPST Configuation open the top menu entry "Start Clients" and then "Software Download". Select the port of the device in diagnostic mode and press OK.
Choose the “Backup” option tab, click browse, choose your destination and name of your QCN backup, choose the "QPST NV Memory Files (.qcn)" as “Save as type”, NOT the first option as (.xqcn).
Click “Start” and wait for it to finish. This will back up all your phones NV Items and save them to the QCN Backup File.
5. Anonymizing your IMEI:
Open the .qcn file with HEX editor.
Search for your IMEI in HEX format. To do so, use the IMEI converter, enter your IMEI.
[For your own verifcation: An IMEI in HEX always starts with "08" followed by your first IMEI number and an "A". So if you have IMEI 123456789012345 the HEX format would be 08 1A 32 54 76 98 10 32 54.]
Now search for the converted HEX string (or better search for the first four characters 08xA only). Keep in mind to set the search type to "HEX values" not "Text" or anything else.
Replace all numbers after “08” with dummy numbers, so the result will e.g. be: 08 1A 22 33 44 55 66 77 88. Please copy your chosen dummy HEX IMEI, so I know what I am searching for to insert my IMEI then.
Save the file (as another copy, don't replace your original file in ase you will need it some day)
6. Share the anonymized file with me over PN
I thank all of you for your help! :victory:
Hello, I am new here and I would like to know if it is possible that you could share the file that happened to you since I have the same problem after partitioning my cell phone Beforehand thank you very much Sorry for my bad English
hi. had same problem with imei missing in my phone after hard bricking it and partition all mess up but now I done reparing the partition, some error come up says nv partition error. then I find out the imei is missing. please send me the dummy imei to my email. hope I can have my phone back.
- [email protected]
TL.DR; Trying to root new Verizon Android flip-phone with Marshmallow 6.0.1, ARMv7. Firmware version: VN22010B. Seems to to be locked down.
Click to expand...
Click to collapse
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Why?
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
jfn0802 said:
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
Click to expand...
Click to collapse
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Same problem
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
i get the same error. did you find a solution? i would really appreciate it
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
MendilR said:
i get the same error. did you find a solution? i would really appreciate it
Click to expand...
Click to collapse
re: the certificate error for side loading apps...
Code:
adb shell settings put secure install_non_market_apps 1
turns off the unknown source block, but I'm still getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
Could the apk itself I'm trying to use have a bad certificate? Or is there another solution?
InfectedPackets said:
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Click to expand...
Click to collapse
Just curious - any success or updates. I can't seem to get past " INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
Click to expand...
Click to collapse
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
PAULC91316 said:
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
Click to expand...
Click to collapse
I'm still at the same place I was the other day when I posted this.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from
here.
Click to expand...
Click to collapse
InfectedPackets said:
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Click to expand...
Click to collapse
Can you please share with us the KDZ file?
Thanks!
anyone?
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Thanks for taking your time, to help me.
I will check if I can unlock the bootloader.
Thanks alot
r3w1NNNd said:
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Click to expand...
Click to collapse
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
effulgent.unicorn said:
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
Click to expand...
Click to collapse
my freinds are using it in Canada with videotron and everything works, without unlocking
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Isn't that what turning on the "install from unknown sources" option should do? I still get the Install Parse Failed after switching it on with ADB.
@98jbsz I've tried to uninstall without success. What way did you do it? And does it just leave a blank space in the menu screen?
[Less on topic, sorry again, but has anyone seen the LG Wine LTE? http://www.lg.com/us/cell-phones/lg-UN220-lg-wine
It's strikingly similar to our friend the Exalt LTE here, but it seems less carrier branded/available at US Cellular, so I'm wondering if that would make a difference?
Major differences Wine LTE has more 4G bands (2/4/5/12/25) versus Exalt (4/5/13), which kind of has me kicking myself, because travel and 4G was one of the reasons I bought the Exalt. Both have quadband GSM and WCDMA, but interestingly the Wine also has CDMA.
Beyond that, there are some more smaller differences I scavenged from their LG pages, Exalt has more bluetooth profiles, supports more music formats, has more GPS capabilities, wifi calling, and 1 more ringtone. Wine has more supported video formats, and an FM radio.
I'm curious about what/if the Wine would have for sms messaging (I doubt it'd have Verizon's message+) and instead of my Verizon app...]
98jbsz said:
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
Click to expand...
Click to collapse
Alright, I also managed to uninstall my verizon and verizon's cloud app using
Code:
adb shell and the pm uninstall -k --user 0
But the Verizon apps folder on the menu screen remains, although it's empty. Any ideas on how to remove it?
Then I tried to install an apk using
Code:
pm install
and it came back with [INSTALL_FAILED_INVALID_URI] which...is a different than [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES], but not better.
right, but when you first copy the APK to the phone, and then you install it, you will see the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] error. still not a solution
Hi everyone, I have finally figured out how to get proper diag support on our device. This will allow us to use QPST and such.
It will be a pretty short guide as it's quite simple, but it does enable us to do a whole lot of things we couldn't do before.
Downloads
* QPST
* AsusVoLTE app
Prerequsities
* Both methods require root, at least initially. There are several threads on how to do that, so look those up if you need help.
USB method
Downloads
* Qualcomm USB drivers
Step 1
Install the drivers and QPST from above. If you've already done this from my VoLTE/VoWiFi guide there's no need to reinstall them.
Step 2
When you've done that, install the AsusVoLTE app and connect the phone to the computer and open up it up. Press the Enable DIAG button, and you should hear/see a new device attaching. This should hopefully be enough, but if not, try rebooting the phone. If that still doesn't work try the Remote method below.
Remote method
Prerequsities
* Both your computer and phone have to be connected to the same network. You may also need to allow port 2500 in your firewall.
Step 1
Start by downloading and installing QPST from the link above, no drivers or such required. If you've already done this from following my VoLTE/VoWiFi guide you can safely skip this step.
Step 2
Now run QPSTConfig.exe from the bin folder of the QPST install and wait for it to open up. Head to the IP Server tab and tick the Accept client connections box - we need to do this as we will be connecting to QPST remotely. Take a note of the Server IP Address (this should simply be the ip address of your computer), and potentially the Server Port below if you have changed it from the default value of 2500.
Step 3
Open up the AsusVoLTE app on the phone, and enter the IP address from the Server IP Address in the field, and optionally, change the port number.
After this you can simply press the Start button.
Now that you have done this, you should, momentarily, see a new port appear in QPST Configuration under the Ports tab with a Port number like COM30001 and the Phone column should hopefully say SDM855 (0). If you do see this you are good to go! You can now start exploring EFS and such.
Troubleshooting
Some people have had issues connecting to the diag port, with EfsTools from the VoLTE guide returning BadCmd and QPST not working either. If you have this problem, try restoring modem settings by running this in bootloader (adb reboot bootloader, or press volume up while rebooting):
Warning: This may cause issues with no service for some, do not run this without a full backup of all of the partitions (in particular, modemst1, modemst2, fsg and fsc) on the device!
Code:
REDACTED because people still run these commands without taking a backup
Do note that this will reset any changes you may have done (like enabling VoLTE through PDC).
Thanks to @xbamaris1` for troubleshooting this with me, and for confirming this worked!
Let me know if this has worked for you, and if you have any questions!
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
dennis96411 said:
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
Click to expand...
Click to collapse
I had this problem to until I realized that its network based and your phone should be connected to your WIFI (at least thats what fixed it for me).
However, Despite this, i am still not getting data from it. COM30001 from an IP of 192.168.1.211 (which is my phone) and it is still not able to browse data from QPST
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update 2: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
xbamaris1` said:
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
Click to expand...
Click to collapse
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
dennis96411 said:
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
Click to expand...
Click to collapse
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
xbamaris1` said:
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
Click to expand...
Click to collapse
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
dennis96411 said:
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
Click to expand...
Click to collapse
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
xbamaris1` said:
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
Click to expand...
Click to collapse
Which version of QPST Configuration do you have? This is mine.
dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
It's not necessary, no - if you get it to show up in usb you won't need to do any of this. I could, however, never get the phone to connect in usb mode - it just shows as No phone.
I will try those drivers you posted and update the guide.
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
Oh did those drivers make a difference for you?
HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
How to change imei with EFS
QPST via remote using your guide worked for me. I am able to use EFS Explorer. Thank you @HomerSp!
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
XavierBK said:
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
Click to expand...
Click to collapse
Magisk (the root method) hides itself from bank apps and such, but you can do a SafetyNet check in the magisk manager app, and if that passes so you should be good to go.
Only thing you won't be able to get with the bootloader unlocked is HD video in Netflix and Amazon video.
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
ChronoReverse said:
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
Click to expand...
Click to collapse
Yes indeed, but we have yet to find a way to enable additional bands. We are working on it though, so hopefully we'll have something soon.
Hi, can we use QPST to unlock LTE band on 8G/128G version?