Related
I have a big problem on my HTC Droid Incredible.
Bypassing the activation screen really irritates me and i can't turn on the USB Debugging which is the key to root and s-off my phone and to bypass the activation screen.
The procedure i did for bypassing the activation screen are: tap 4 corners, safe mode, call *228 and end call after few seconds (did this several times), cdma workshop, ##778 change the nam setting, and non of them works for me.
cmlusco member of xda told me that the best way to bypass it is to change the build.prop in any rom i'm going to flash on my phone. Then he give me this link http://forum.xda-developers.com/showthread.php?t=1306400 and i think this is it, but in the end still failed because i need to turn on my USB Debugging.
Please help me to bypass my Droid Incredible.
I'm here in Philippines and there is no Verizon network provider here.
I already solve this problem and I can use my Droid Incredible. Sweet!!!View the 3rd post how did i do that.
Click to expand...
Click to collapse
are you able to fix this?im having EXACTLY the same problem.
yup I already fix it, just follow this procedure.
1) try to enable usb debugging mode by doing this procedures.
for this,you should need wi-fi.
so,let's start
1)when the phone calls to *228 tap contacts icon,right to the "end call"
2)try to add a new contact and enter facebook or other socialnet dialog.
phone asks you to enable wifi, do this and connect your wifi network
3)next hold the search button and (via voice search) search in google "market"
4)tap to the official market page, phone asks you about opening this page,choose market app.login in the google accounts,if you need.
5)search in market "usb debug" app. install it and tap "open' in the market app
6)enable usb debugging and enjoy)
and for those who don't have a wifi connection in there home, this procedure is for you.
1. call *228 and tap the contact on the right side of end call.
2. add contact and put any information.
3. try to connect it in facebook to prompt the setting window.
4. tap setting.
5. tap search softkey and type application.
6. finally you can enable usb debugging without any problem.
thanks to ramazancik94 for giving this life saver step for enabling usb debugging mode.
2) root and s-off your phone by following this procedure root 2.3.4,downgrade,and s-off
3) if you already have CWM, rooted, and s-off your phone try to install some ROM using CWM in development section. Double check if your phone is s-off via hboot (press and hold power button and volume down), your phone is rooted if you install CWM, and find some ROM that suits your need.
4) Try to use the "end call bypass" if this method doesn't work with you this will be your last resort. Delete the phone.apk before you install the rom, to delete the phone.apk open the "blah blah blah rom.zip" and go to data> system app> find phone.apk and please don't extract the rom and delete the phone.apk or i won't work, just delete it from the zip.
Note: Deleting the phone.apk will result for disable your phone signal. So you're going to use your phone for music, game, watch some movies and wifi internet. You won't be able to use it for call, text and mobile data, and also please read it carefully so you won't **** your phone. You've been warned
For more information visit this thread: help bypass the activation
All big thanks to cmlusco, ramazancik94 and tiny4579 for their help
need help
sir maybe you can help me with this...im new to android phones and i dont think i can make it
can you please send me the step by step procedure of the things i need to do after i put my phone in USB debugging mode?hope you dont mind
my email is [email protected]
my tcp account is kian0926, im here in the Philippines as well and im glad that you were able too fix yours, hoping that i can use mine as well, saving this device from a trash can
many thanx in advance...
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Kian0926 said:
i can't get my ADB working
after i extracted mini-adb under c drive (c:\mini-adb_inc) i extracted adb inside of it
but icant get adb working
when i tried to open adb it just flashes (like blink of an eye) and closes itself immediately
i cant proceed
pls help..............
Click to expand...
Click to collapse
You cant just click on the adb.exe file, it is a cmd line program. Open a cmd prompt on your pc and type " cd C:\mini-adb_inc " then type in your adb command, example " adb devices " this should show the serial number of your phone if connected to the pc and adb and drivers are setup correctly.
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Kian0926 said:
thnx for the reply
but this " cd C:\mini-adb_inc " seems to be invalid when im trying to enter n the command prompt window
i already tried removing those that i downloaded and download them again but still the same thing...
---------- Post added at 02:19 AM ---------- Previous post was at 02:11 AM ----------
also inside of mini-adb extracted on my c drive theres no adb.exe.it just say's adb
under that is AdbWinApi....so cunfused now
Click to expand...
Click to collapse
What makes you think the cd command didnt work, did it give an error? All cd does is change the directory to C:\mini-adb_inc where the adb file is located. It is ok if it says just adb and not adb.exe, your pc is just set to hide extensions. When you first open the cmd prompt to the left of where you type it will say something like C:\users\your_user_name\desktop >, when you type cd C:\mini-adb_inc it should go to the next line, and to the left of where you type now it should say C:\mini-adb_inc >Then type adb devices and see if a serial number comes up.
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Kian0926 said:
"C:\users\your_user_name\desktop" his is what i exactly saw on my laptop and when i tried enterring "c:\mini-adb_inc" a message appears say's like "incorrect path/directory"
im gonna try using another PC and hope this time it works..
Click to expand...
Click to collapse
You have to type " cd C:\mini-adb_inc " or what ever the path is to the adb file. here actually try this. Go to the folder where the adb file you unziped is. Then hold ctrl + shift and right click on an empty space in that folder, and select open cmd prompt here. then type in your adb command, ie adb devices.
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Sorry to say, but if you cant enter hboot, or boot up to the os or recovery, then the phone is more thsn likley bricked. Unless its a battery issue. Does it vibrate at all when trying to start?
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
Does it boot when plugged in? There MAY be some help if it can boot when connected to AC power.
Kian0926 said:
after i successfully activated,rooted to 2.3.7 with cm7 ROM my droid incredible it was working perfectly fine,but after a couple of hours using my droid it unexpectedly shut itself down and left me with just a blinking orange led at the top of it..last application running is viber,im on a call actually..and my phone is on charge...
what might be the cause of it?and can this be fixed?..my phone is completely dead
i even tried resetting the phone(pressing volume down button and power button but still no reponse..
Click to expand...
Click to collapse
I've experience this, just a blinking orange led. What did I do was i charge it and a couple of minute the the blinking orange led stops and it become a steady orange led.
Easier way (offline)
Found what could be an easier way, I'm playing with my sister's incredible and I can get usb debugging enabled by using any of the official verizon update packages (could be a rom, but I downloaded the smallest hboot upgrade from htcdev), it appears to send some commands in usb mode that trigger the activation of usb debugging, what's funny if that if you either disconnect before it's done, or it fails, it leaves usb debugging on.
Non-sense.
EDIT: You just have to open the utility, you don't to flash or disconnect.
Such and old thread but I have a Incredible that a friend gives me and I couldn't access the market app by search function. What I did was search anything with voice commands, then a navigator window opens and change the URL to: market://details?id=usb, it opens the market app and I can install the USB debug app
Simple method, without the use of USB Debudding/rooting flashing:
Go to Emergency dialer,
Enter ##778, and press 'call'
Select 'Edit Mode'.
Password is: 000000
Select 'NAM Settings'
Make the following changes:
MDN = your 10 digit phone# (0000000000)*
MIN1 = your 7 digit phone# (0000000)
MIN2 = the area code of your phone# (000)
Press the 'back' key and go to 'HOME SID/Home NID' settings
Select 'Home SID/NID #1', and change the first value to '189' (Leave the 65535 alone).
Now press your 'menu' key
Press 'commit modifications' "button"
Phone Should reboot now.
Changing MDN using cdmaDevTerm
In some phones MDN cannot be changed, in this case you need to connect the phone to the computer as a "modem" device, and use the opensource cdmaworkshoptool / cdmaDevTerm from here:
http://code.google.com/p/cdmaworkshoptool/
Connect the tool, select manually / automatically the COMPORT for your HTC device, Read from device, Change the MDN to 0000000000 Select write
Disconnect and reboot your device.
It should now by pass the activation.
most of the ref. from
http://androidforums.com/incredible...g-activation-screen-no-service-available.html
k guys, this thread is coming about after respectfully moving the discussion from kalaker's s-off thread.
i've been looking for a while about how to back up my nv keys for data, just in case anything happens to my one v. this is thanks to New Optimus (for steps 8-10) and jmztaylor, who informed me the open sesame door trick works. I AM NOT RESPONSIBLE FOR HOW SOME MAY USE THIS. open sesame door trick has the potential to screw your phone up if you dont do it right, or delete an nv item.
CDMA ONLY (i dont think gsm works the same way anyway)
YOU ARE NOT MODIFYING ANYTHING. All you are doing is backing up your AAA and HA keys. they are used to identify and register your device's data on the VM network. IF YOU MODIFY ANYTHING, ITS YOUR FAULT IF YOU SCREW IT UP.
step 1:
download and install qpst. im not linking to the file, you should be able to find it easily enough by googling it.
step 2:
open up qpst configuration, and let it sit in the background for a minute. install the htc diag drivers for one v from here: http://www.htc.com/www/support/
look for the one v, and download and install the HTC Sync program which will install all the drivers you need.
step 3:
close out of htc sync once its installed, its an annoying program anyway. connect your phone, make sure adb debugging is enabled in developer options in settings. open the dialer, type in ##3424# (##diag#) and a screen will come up that says on and off, with select at the bottom. click on, then select, and it will ask you for your msl code.
note: your msl code can be obtained by a app in market called MSL Reader, you need root for this. follow the prompts in the app, its easy enough to do.
step 4:
after entering your msl code and entering diag mode, go back into qpst configuration. click on "add new port" toward the bottom right, and make sure when the window opens "COMx- USB/QC Diagnostic" is selected and click ok. qpst configuration should now recognize your phone as SURF-MSM7830. if it doesnt, update your version of qpst.
step 5:
in qpst configuration, click on "Start Clients- EFS Explorer". make sure you put your msl in the box that says spc, and click ok. a please wait window will pop up, it will only take a few seconds.
from New Optimus's post: http://forum.xda-developers.com/showpost.php?p=29951978&postcount=796
8. Once the phone reads completely make a new directory named (open sesame door) without the parentheses and all lower case
9. After making the new folder locate abd.exe from the android sdk install folder and press: start, run and type cmd then press enter you will get a command prompt window that opens up navigate to the android sdk directory and type; adb reboot, the phone should then reboot if you’ve done as you were supposed to.
10. After the phone reboots read it again with QPST EFS Explorer which still should be opened, you will notice that the red no access circle has been removed from the nvm directory so expand it and go to the num directory,
Click to expand...
Click to collapse
(note: edited New Optimus's post to remove links to esn/meid changing which is frowned upon in the forums, also i already had the open sesame door folder created upon making the pictures.)
left click and drag 465, 466, 1192 and 1194 to your desktop.
keep 465,466, 1192 and 1194 in a safe spot, they are how you have data on your phone. if something happens to your HOV and those are gone, good luck getting data back.
Quick noob question, do these files get generated by the carrier when you activate the phone?
whoshotjr2006
Do AKEY, SSDA and SSDB files need to be saved? if so, where are the files?
reachforthesky said:
whoshotjr2006
I know the content of file 0 and 1943. Could you briefly describe the contents of these 4 files (465, 466, 1192 and 1194)? Which one is HA, AAA, SSDA and SSDB? Are there any more important NVM files need to be saved?
Click to expand...
Click to collapse
465^"Data Services Mobile IP General User Profile"^"Data*"
466^"Data Services Mobile IP Shared Secret User Profile"^"Data*"
1192 is the AAA secret
1194^"HDR Access Network Stream CHAP Authentication User ID"^"Data*"
The reference is here: http://forum.xda-developers.com/showthread.php?t=1954029
Got sooo excited when I saw this. Used to switch firmware's on my optimus v with the firmware of the optimus s, and use optimus s roms. Had all of my nv data and everything else backed up. Forgot you have to have be on an aosp rom for this to work because you need a port. -_- I don't have a stock backup and right now I'm tethering, so it'd take awhile to download a stock backup. Guess I'll have to wait a week or so.
nvm, I found a backup. I tried it out, and i got to the qpst efs explorer. I did the open sesame door, and it unlocked the nvs, but I only had a couple of the files from the list. I did not have 465 or 466. Also, I had an issue when I tried to recognize the phone. It did recognize the phone in diag mode with the port, but not as surfmsm7830. I have the most updated version of qpst.
I'll have to check what version I'm running of qpst, I know its close to the newest if not the newest. It wouldn't recognize my phone correctly until I had a new enough copy.
Also the first time I tried the open sesame door trick, I too had the limited nv items. I used the ruu to go back to stock, and once I did that the open sesame folder dir survived the ruu and unlocked the rest of the nv items.
Hope that helps.
Sent from my One V using xda app-developers app
What version of QPST are you using for this? I get an error "Online connection failure: Unspecified error" when trying to connect.
I think my phone isn't getting read properly by QPST because under phone it says "(unknown)" even though the other fields fill in correctly.
CDMA Workshop reads my phone no problem, but this thing no luck.
EDIT: Found an updated build and it displays the specified info under phone. Not sure what the lowest working version is, but v2.7 build 323 will not read it, build 366 will though.
So like the Google Play Store, if you install Happy Chick on the stock Ouya Rom it won't show up in the Apps or Software menu. Anyone know a work around, possibly be able to just rename it within the apk to get around it?
The same for me. Any solution?
Hi, don't know if anyone will read this, but here it is:
I suppose installing a custom ROM would also do the trick, but if you want to keep the Ouya ROM (keep in mind that this is not a pretty solution, and that it requires a PC running on the same network as the Ouya):
- Download the ADB tools and install them on your desktop PC
- Activate network ADB on the Ouya (development menu)
- On your PC, go to the ADB folder and type "adb shell am start -n com.xiaoji.emulator/.Entry"
If this does not work, try "adb connect <IP>" with the IP shown on your TV, and then the shell command.
You can create a .BAT file to launch it, which is a cheap hack but works.
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