Related
Decided this should have a thread of its own instead of hiding in another thread.
I originally stumbled onto this thanks to cyryl's post where I found that disabling 3G helped prevent a lot of the Sleep of Deaths (SoDs) I was seeing. (Phone was sleeping with solid green LED, then suddenly switches to orange LED and is totally hung.) That led to the discovery that the Vogue sources (which XDAndroid is derived from) had a bunch of newer fixes to their RIL library that were never pulled into XDAndroid.
I set up a clone of the XDAndroid and Vogue repos and merged them all in here:
http://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/androidhtc1
I also fixed several bugs that weren't fixed in either of the previous source trees as well (mostly memory leaks). The result was working well on my phone, but since then I've gone on to fix additional bugs, making this RIL behave almost identically to the native HTC RIL running on my G1 phone.
I used to get SoDs within about 10 minutes of booting up if I had 3G enabled. Now my phone has lasted 24 hours at a stretch without any crashes. The binary is attached here if anyone else wants to try it out. Instructions courtesy of Entropy512.
Entropy512 said:
To test this fix (should work with any Froyo 2.2.2 based builds):
Unzip the attached zip file
Place libhtcgeneric-ril.so somewhere on your SD card. For organization, I use bindfiles/lib/libhtcgeneric-ril.so
Open conf/froyo.user.conf in your favorite text editor
Within the custom_shells{} section of froyo.user.conf, add:
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /lib/froyo/libhtcgeneric-ril.so
On Gingerbread it would be
mount --bind /sdcard/bindfiles/lib/libhtcgeneric-ril.so /system/lib/libhtcgeneric-ril.so
Click to expand...
Click to collapse
If you run into problems, get a log taken when the problem occurred and attach it with your post describing the problem!
Problem reports without accompanying logs are useless and a waste of time.
You will always need the output from "logcat -v time -b radio". Sometimes you will also need the output from "logcat -v time" (simultaneous with the first). If you don't know how to obtain these, then please STOP NOW and don't proceed any further with this.
There is an alternate set of files in post #6 for use with a patched rootfs. See that post for the details.
The ril in this post is no longer being updated. Use the alternate ril in post #6 to get the latest bug fixes.
Using CDMA Mode
Documenting this here for my future reference, don't do this unless you're actively involved in helping me debug:
To switch into CDMA mode with your current install
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
update secure set value='4' where name='preferred_network_mode';
.quit
Reboot for it to take effect.
Alternatively you can blow away your data.img and edit /system/build.prop and set ro.telephony.default_network = 4 before booting. (Earlier versions of this post said to use 6 for the mode. That was a mistake, 4 is the correct value.)
The original value was 0, so you can switch back to that if you need to.
You will also need to edit a property file to add your network info anyway. You must add e.g.
Code:
ro.cdma.home.operator.alpha = Sprint
ro.cdma.home.operator.numeric = 310120
Replace "Sprint" and "310120" with the correct name and ID number (MCC/MNC) for your mobile network. If you don't get the operator ID right some features will not work properly (roaming display, international dialing...). The easiest way to do this is just to create a file /data/local.prop and put these settings there. I believe the operator ID for Verizon is 310012 but haven't verified this. A complete list of operator IDs can be found on Wikipedia.
If you run into problems we need "logcat -v time -b radio" starting from as soon as possible in the boot to catch all the gory details. Also a regular "logcat -v time" running at the same time.
In fake GSM mode the phone always used a hardcoded operator ID of 310995, and the APN for that ID was used for mobile data settings. In CDMA mode the phone sees the actual operator ID, so you'll need to add an appropriate APN to match that ID. See http://cleanimport.xda/index.php?threads/1023116/.
Thanks for creating a separate testing thread for this - it needed it, and I was going to suggest it if you hadn't already made this thread .
I have tested this on my CDMA RHOD400.
Seems to work well - unfortunately I'm not a good test case, as I very rarely, if ever, get SoD's.
I do know that 30s sleep issue seems resolved - I made several calls, ran it overnight, and it still sleeps quickly with WisTilt2's test kernel. Now we need him to commit his code, get your code tested a little more and commit yours... Holy cow batman, our port is lookin great!
I use Complete GingerBread Bundle!!** GBX0A - Alpha! Camera!
Here is my log http://forum.xda-developers.com/showpost.php?p=12403347&postcount=22
Borrow to use once:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
New init version
This is an alternate version of the ril which uses /system/bin/pppd instead of /bin/pppd. In order for it to work, you also must change some files in the rootfs. The new files are attached here in rootnew.zip. Here are the instructions for installing from a root command shell, assuming the zip file is in /sdcard/rootnew.zip:
Code:
# cd /
# mount -o remount,rw /
# rm -rf .git
# mv init.android init.android.BAK
# unzip /sdcard/rootnew.zip
# chmod 755 init.android init.etc/ppp/ip-*-*
# mount -o remount,ro /
Reboot after installing. You only need to do this once on a given rootfs. If you switch to a different rootfs you will need to do it again.
The advantage of using this approach is that the /system/bin/pppd doesn't ever try to write to /etc/ppp (so there is less opportunity for filesystem corruption when things go wrong) and the ril will not interfere with Android VPN use. Also this approach is required for NAND installs. I expect that this approach will be the default in the next FRX/GBX releases, but so far the changes haven't been merged yet.
This ril is no longer functionally the same as the ril in the first post. The code is in the initpppd branch of my git repo.
https://gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril/commits/initpppd
Update: Everything in my initpppd branch has been merged into the main xdandroid repo. All of my fixes will be in the next official xdandroid builds, there's no longer any need to use my personal repo.
You can safely install the rootnew files regardless of which ril you use. But the ril in this post requires these files; it will not work without them.
Note: the init script in this rootnew archive is a patched version based on the xdandroid git repo. If you're running on F22's rootfs, you don't need this archive. Instead, you can grab F22's rootfs image with my patches already applied.
Also note: the ril attached here is no longer equivalent in functionality to the one in the original post. This ril no longer has fake GSM support; if you're using a CDMA phone see below. This ril also no longer uses any options in the startup.txt file. If you had force_cdma or north_am_dialing in your startup.txt file they are now ignored. If you set your operator name and ID correctly in build.prop then the dialing is automatically handled by Android.
Also this ril supports dynamic mode switching for world phones. If you have a rhod400/rhod500 and use both GSM and CDMA you can switch back and forth on demand. Currently the menu for this is buried inside the *#*#INFO#*#* menu.
[size="+2"]New CDMA support[/size]
This version now switches into CDMA mode automatically; you no longer need to set the default_network property or muck with sqlite3. If you have a rhod400/rhod500 and no SIM card installed, your phone will use CDMA by default. If you have a SIM card installed, it will default to GSM and you'll have to switch to CDMA yourself. If you're using my updated Phone.apk (a new version of that as well, not yet uploaded) then the World Phone menu will be enabled automatically and you can use that to select the mode. Otherwise just use the *#*#INFO#*#* phone menu.
You will still need to set your APN for MMS to work, and you'll probably still need to install an eri.xml file. And you still need to set your operator ID properties.
Note: if you try to switch modes on the current GBX image, the Phone app will crash. It's a bug in Google's code, not the RIL. I've written a fix for this and the fix is in the XDAndroid repos, so it will work fine in the next GBX release. Froyo is fine either way.
muziling said:
After set preferred_network_mode to 6, com.android.phone process keep FC
logcat -b radio & logcat logs below
Click to expand...
Click to collapse
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
highlandsun said:
Thanks, this is helpful, it shows that we're missing two critical commands for CDMA support in the RIL, CDMA_SET_SUBSCRIPTION and DEVICE_IDENTITY. You should switch back to GSM mode (mode 0) until this is implemented.
Click to expand...
Click to collapse
Okay, so just to clarify, this shouldn't work for CDMA at this point? Arrrghhh is on CDMA, it seemed to work for him?
highlandsun said:
OK. Definitely it will fail with Gingerbread. I'm only testing with Froyo so far.
Click to expand...
Click to collapse
Also, just to clarify, this shouldn't work on Gingerbread at all at this point (and not just setting the network to 6 will fail)? I have it mounted in Gingerbread under the lib/froyo directory, since there is no /lib/gingerbread directory, and everything seems to be normal so far but I'm not sure how to tell if it's actually being used and I haven't called the network 6 command yet.
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6 4).
OK, here's the current status before I leave for the weekend:
Currently the ril code sets a radio status of "SIM not ready" when the radio power is first turned on. The CDMA phone sees this and says "wtf, it's trying to use a GSM SIM card" so it kills itself to start the GSM phone code again.
So we need to be able to obtain the current operating mode in the ril so we can see, if we're trying to startup with network mode 6, it should use some other radio status code instead of the SIM-related codes.
Anyone who wants to dig into it and think about how to do that, please do...
highlandsun said:
I've uploaded a new one (and changed the version string to 1.6.1) which has these two missing commands implemented. So if you want to test CDMA and get another log, please do.
manekineko: the old RIL says version 0.8. Mine says "Version 1.6.x [xda]".
This will work fine on gingerbread for GSM. If you have mobile data turned off, it probably works with CDMA phones too, in fake-GSM mode. I have no idea what it will do when you flip the switch to real CDMA mode (mode 6).
Click to expand...
Click to collapse
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
pdawg17 said:
So is this not expected to work correctly for CDMA? I get a lot of SoD due to poor reception so I'd love to use this but I will be out for the day so should I wait to use it when I can post logs?
Click to expand...
Click to collapse
It's only working well for GSM. Sounds like you should pass it by for now.
Request - for those of us following your source tree, when you upload a binary can you post which git revision that binary was built from?
Thanks
Started running this last night when you posted it in the other thread. I'm GSM only (Rhod210) so I can't help with CDMA, but I've been the victim of what are probably RIL related bugs. In areas with bad signal and when switching between EDGE/GPRS/UMTS networks I've experienced a bug where the "phone" part of the phone starts going haywire. The first symptom is that the phone no longer responds to incoming calls. From that point on, I can receive one text message after which point I can no longer send or receive text messages nor can I make or receive calls. Switchiung to airplane mode doesn't fix the issue and a reboot is required.
I'm hoping you've accidentally fixed this bug too.
highlandsun said:
It's only working well for GSM. Sounds like you should pass it by for now.
Click to expand...
Click to collapse
Confirmed. Works well on my Tilt2. It seems that data speeds are better as well. Can't say for sure but will keep testing. Great work!!
For the less educated amongst everyone, what chance is there of making a quick kernel zImage for us to try out?
I can't use anything after Feb 28th or I get a home screen lock.
The RIL is not a kernel module (.ko), but a loadable library (.so). This is why you need to use the mount command in froyo.conf.
-- Starfox
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Okay, found the conf file. Making the changes now! Must've been a late night. lol
problem still, logs below
6d5b27e_6.zip is network mode 6 's log, com.android.phone keep FC.
6d5b27e_0.zip is network mode 0 's log, when 3G enable, phone in, who call me will listen hang up audio ,and I can not accept and reject this call in my phone.
Raa_1 said:
Ahhh okay, gotcha.
I might muddle around with it and see if I can get it to go. Any pointers for a new user to get this to happen?
The FAQ's don't seem to cover loading new modules! lol
Well had a look using droidexplorer and no conf folder at all. Can't seem to find the froyo config file to edit.
If I was to put it on the sdcard in andboot/conf, would that be okay? And where does this froyo config file come from for me to put it there? :/
Click to expand...
Click to collapse
That's odd - what build are you running, and how was it installed?
I know the conf file was included with the FRX05 full ZIP bundle (or was it the FRX04 bundle?)
Hi guys, i'm from the Nexus S area, I have a question about the EVO. Someone I know has an EVO and his contract is up now, and mentioned flashing to another carrier. Does anyone know if he can get his phone flashed to the other carrier(Revol) with the custom rom already on it?
It will have to be a stock sense 1.0 rom or Espt codes wont work to activate the phone.
Sent From My EViLizED-iCS-EVo4G
It's possible, but he would have to hunt for some cdma pst tools for his PC which shouldn't be hard (e.g. QPST 2.7 355 ) so that you can connect to your phone via USB Cable. Now of coarse as mentioned above you will need HTC Sense to be able to dial keypad commands to get your phone into DIAG Mode "##3424#", but don't frown yet because if you have AndroidSDK or HTC Sync even so that you can use adb commands you should be able to put the phone into DIAG mode this way. I am assuming the phone is rooted since he has a custom rom. below are the adb commands to use to put the phone into DIAG Mode then you shouldn't have a problem looking for a guide using those cdma PST tools to program his phone to revol.
ADB Commands:
First be sure to cd into your directory where adb.exe is located.
adb devices <<< this command is just to be sure your phone is found
adb shell
$ su
# echo 1 > /sys/devices/virtual/usb-composit/diag/enable
That should enable DIAG for you. To disable DIAG once your done simply change the "1" from the last line to a "0" and it will be disabled.
Hope this helps one way or another.. good luck bud.
I have some one that has an Evo and wants it flashed to boost mobile. Question how do I go about that and can it still be rooted and have a custom rom after flashing it??
I have an EVO. Its on Boost. You can find the guide on how to do it around the net and on the forum. You can also buy the same guide on ebay... not sure why people bother.
You can root the phone or port it to Boost while it is not rooted. Doesn't matter. Once ported you can put on any rom that you feel like... again root or no doesn't matter. I have a non Sense rom. EPST codes sometimes give me trouble but for the most part I dont need it. I use Miui. You can use any rom you want but Sense rom will not give you voicemail notifications while any AOSP rom will. Thus my choice of Miui.
Without epst access on a sense rom you'll have trouble with MMS (picture messaging). What you have to do is change the APN settings... on a AOSP rom that's complicated. The easiest solution that I found is to not use the bundled messaging app and get GO SMS Pro from the Market (free). Once installed go into Settings> Adwanced> MMS Settings and Fill APN Configuration Manually
MMSC: http://mm.myboostmobile.com
MMS Proxy: Leave this one alone/unchanged
MMS Port: 80
Good luck.
PS: Please do not start a thread about this as the thread will quickly become a legal vs. illegal thread.
There is a special secret dial code for invoking an extended Engineering Mode on the Oneplus 3:
*#36446337#
This opens up the menue of this extended EM.
It worked. But I screwed it up, so I cannot invoke it any more
I know, shame on me and all that stuff, this was totally my fault, as I played around with the apk, copied (not moved) it to the Download folder and tried to install it like a normal app.
Did not work.
But now also invoking the original extended EM no longer works ([email protected]).
I'd like to kindly ask the real experts among you:
1. What is it I screwed up with my stupid attempts to install this apk?
2. Is there any way to restore the information the dialer needs for parsing this secret code - other than performing a factory reset?
Or which is the information that got lost or overwritten?
3. All files in
/system/app/EngineeringMode
/system/app/EngSpecialTest
appear to have been unaffected.
(But could anyone please share the proper contents of these two folders, in case the extended EM works properly for him?)
4. Is there any way of invoking the extended EM directly working around doing it with the secret dialer code given above? e.g. by modifying the apk - admittedly in a more sophisticated way I attempted ?
I hope my question comes in the proper forum, don't want to cross-post it.
Thanks in advance!
Please Post Files as attachment or Link...
Would you be kind enough to post these files or a link to them? Unsure, but suspect a permissions issue or incorrect location of said files. I think you can connect to computer (with debugging enabled, & allowing access & allowing the rsa prompt also). You will need a command line/terminal depending on your desktop /laptop os. . I would say that you can use adb devices, then adb shell and finally am then the package name. Not sure how to format the activity manager command. Mayb am start - n xxx or am start xxx. Perhaps forum or Google can help. I kno that typing just am from the adb shell will list all possible options.
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
Hey!
I have LG L62VL phone, need to connect it to DFS for programming NAM...
I have root (I found ROOT method which one is working, but it works only until reboot). Tried Shortcut Master Lite apk, couldn`t find anything for activation diag or hiddenmenu. Hidden Menu is working by *#546368#*62#, but there is only:
Device Test
ELT Test
Factory Reset
Log Service
HW Version
CMAS_RMT
QFUSE_CAL
If connect usb in MTP mode, it`s showing COM Port but not working with DFS (red words...)
Is there way to connect this phone to DFS?
Since you have root, maybe doing this in a terminal might work?
Code:
su
setprop sys.usb.diag_enable 1
setprop sys.usb.config qmicm,adb
setprop sys.usb.state qmicm,adb
I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters.
Don't really know for sure if that would work. You could also write to the sysfs parameters as root located in /sys/class/android_usb/android0/. I've been able to get the Qualcomm HS 9008 mode enabled on other qualcomm devices that have been locked down using that method.
Out of curiosity, may I ask how you were able to obtain root on this phone?
zdwilson said:
Since you have root, maybe doing this in a terminal might work?
Code:
su
setprop sys.usb.diag_enable 1
setprop sys.usb.config qmicm,adb
setprop sys.usb.state qmicm,adb
I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters.
Don't really know for sure if that would work. You could also write to the sysfs parameters as root located in /sys/class/android_usb/android0/. I've been able to get the Qualcomm HS 9008 mode enabled on other qualcomm devices that have been locked down using that method.
Out of curiosity, may I ask how you were able to obtain root on this phone?
Click to expand...
Click to collapse
Hi i have a LG G7 and as u say "I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters." i cant enable the diag serial mode. Do you have any clue by looking at my init.lge.usb.*.rc on how can enable it?
I have root, but those 3 lines above does nothing.
prokiller1199 said:
Hi i have a LG G7 and as u say "I've noticed in most current LG phones, in the init.*.usb.*.rc files in the root filesystem (or even the recovery and laf ramdisks), there are no *.prop lines that use "diag" as a usb config, but qmicm enables the diag function in the android_usb sysfs parameters." i cant enable the diag serial mode. Do you have any clue by looking at my init.lge.usb.*.rc on how can enable it?
I have root, but those 3 lines above does nothing.
Click to expand...
Click to collapse
Yeah, I wasn't certain that would work, figured it'd be worth a shot. I don't have a G7 or the capacity to download the kdz and extract those files right now, I figure the contents of those files may differ slightly from the ones on the K20 I have.
If you could post the contents of your init.lge.usb.*.rc file(s) in a [ code ] tag or pastebin or something, I can take a look and see if I can gleam anything from that for you.
zdwilson said:
Yeah, I wasn't certain that would work, figured it'd be worth a shot. I don't have a G7 or the capacity to download the kdz and extract those files right now, I figure the contents of those files may differ slightly from the ones on the K20 I have.
If you could post the contents of your init.lge.usb.*.rc file(s) in a [ code ] tag or pastebin or something, I can take a look and see if I can gleam anything from that for you.
Click to expand...
Click to collapse
kindly check pm