Develop Bugs

Restoring IMEI Number for mtk device

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

How to disable carrier-check for native WiFi Tether (no root)

*EDIT* This appears to only be working for people with NON-unlimited data plans. I apologize for the inconvenience...
Saw this over in the AT&T subforum, originally posted by @ExTREmE99 , just reposting here.
This will disable the carrier check on your Verizon G4 and allow you to use the native WiFi tether - no root needed!
1. Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2. Enable USB debugging under Settings -> Developer options
3. Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4. Start an adb shell: adb shell
5. In the adb shell, run these commands one by one:
settings put global tether_dun_required 0
settings put system tether_entitlement_check_state 0
reboot
When your phone comes back up you will have a fully functional native WiFi tether

i must be doing something wrong because i still get the "you need a subscription" popup

Worked for me, thanks! Needed this a few days ago and couldn't use it n was like "F***, wish I had root" hahaha. Oh and also shouldn't this be posted in General?

jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot

Congobongo said:
Same here, did I do this right?
Code:
$ adb shell
[email protected]:/ $ settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
[email protected]:/ $ reboot
Click to expand...
Click to collapse
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed

Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
I see it after i reboot and try using the hotspot app

jrc27 said:
I see it after i reboot and try using the hotspot app
Click to expand...
Click to collapse
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.

Tomyk89 said:
don't use the hotspot app - in fact, disable that one.
You want to use the built in functionality to tether (not technically an app)
Go to settings, More (under wireless networks), then "Mobile Hotspot". You can setup your SSID and password in there. Also, you can create a shortcut in your notification bar by scrolling over to the right side, clicking edit, then checking the box next to "Mobile Hotspot"
Hope that helps.
Click to expand...
Click to collapse
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...

jrc27 said:
I can't even find the damn app to disable it.
I tried as you suggested, going in through the settings and i still get the verizon C*ckblock...
Click to expand...
Click to collapse
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!

Tomyk89 said:
Could you try disabling the verizon hotspot app? Mine was disabled way before I discovered this so I may need to add this step to the instructions. you may want to go through the steps one more time after that to ensure everything is set correctly. Don't forget to restart either. It works great on mine so it should for yours as well - unless you took the update a week ago?
Let me know - Thanks!
Click to expand...
Click to collapse
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox

jrc27 said:
I've been very careful not to take the update. Is the hot spot app have a weird name or something? I can't seem to find it in the app manager or using rom toolbox
Click to expand...
Click to collapse
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?

jrc27 said:
i must be doing something wrong because i still get the "you need a subscription" popup
Click to expand...
Click to collapse
Should it be? I assumed stuff like this went under the Help section since it was helping people. Maybe I'm wrong. If a MOD would like to correct me and maybe move the thread, feel free.

Tomyk89 said:
hmmm i think I'm confused. My Hotspot app is apparently still in my app drawer. When i click on it it just takes me to the native hotspot functionality.
Honestly I'd attempt to run those commands again. It would help if you took a screen shot of the command prompt window after running all of the commands. After each command it should pause for a second or two then jump to the next line with no errors or responses.
Is your USB debugging on? Also, are you in MTP or PTP USB mode when plugged into your PC?
Click to expand...
Click to collapse
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!

jrc27 said:
Heading to bed...I'll give it another go in the morning
Thanks again for the help, i appreciate it!
Click to expand...
Click to collapse
no problem dude. try some of my suggestions tomorrow and get back to me. feel free to PM and we can post the final solution up here as to not fill the the thread up with troubleshooting.

No Go...
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.

joebrady119 said:
Tried multiple times and could not get it to work. adb looked successful but after reboot I still get a subscription check.
Click to expand...
Click to collapse
have you taken the latest OTA update?

Tomyk89 said:
have you taken the latest OTA update?
Click to expand...
Click to collapse
Have not taken any OTA.

This unfortunately doesn't seem to work for me either
I had to put my device in PTP mode in order for ADB to show the device, after the device was confirmed with adb devices, I issued the commands this is the output
Code:
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb devices
List of devices attached
VS986931(changed the last four for security) device
C:\Users\NOTIMPORTANT\AppData\Local\Android\sdk>adb shell
[email protected]:/ $ settings put global tether_dun_required 0
settings put global tether_dun_required 0
[email protected]:/ $ settings put system tether_entitlement_check_state 0
settings put system tether_entitlement_check_state 0
[email protected]:/ $
When I attempt to enable hotspot I am greeted with the "Use of this service requires a subscription..."
FoxFi seems to work, I just HATE having to change my lock screen in order to use the damn thing!
I'm willing to run further tests and commands if you would like, please just let me know.
I have NOT taken any over the air update. I used the Debloater tool and blocked/hid the app.

Tomyk89 said:
when do you see the subscription message?
try typing:
adb devices
you should see a string of characters listing your device. if it shows no device, then you need to double check that you have your device drivers installed
Click to expand...
Click to collapse
Here's a screenshot of my terminal window:
I'm using the native tethering just like everybody else (Settings, More, flick the tethering switch to On and receive the service check). Haven't taken the OTA and have the service disabled via debloater tool. I appreciate the help!

At this point I'm not sure why some are reporting that this works while others aren't. I added a message on the original post warning that this isn't a for sure thing. I'll be sure to update if/when I find a fix or what is going wrong, but for now I think I have enough info to look into this. thanks for your help everyone and I hope that I can find a fix for this. Worst case - we have to wait until we have root to enable this.
-tom

Rooting the LG Exalt LTE from Verizon (LG VN220) - Request for Advice

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

[MOD]No notch ? Welcome to the immersive mode ! Remove the notification bar

Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
EDIT: I have tested "Immersive Manager Application" from Google Play Store and it's perfect. Very simple and it works even when you reboot your phone.
No more need to type adb commands below except at least few adb commands to grant the Secure Settings permission to the app. This is well explained by the application when you launch it the first time.
I let the adb commands below for information in case we had some "purists" who prefer adb than an immersive app.
1/ Enable the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Enable USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:

Pls the screen..
Redmi K20 cihazımdan Tapatalk kullanılarak gönderildi

pidobeuliou said:
Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
1/ Activate the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Activate USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:
Click to expand...
Click to collapse
Thanks for the instructions bro... I like the immersive mode on all the apps but i do not in instagram app, What is the command to get the immersive mode on all the apps but not in some specifics one?

The setting is reset on reboots. How can it be persisted?

salzzz said:
The setting is reset on reboots. How can it be persisted?
Click to expand...
Click to collapse
Do you have root permissions? If the asnwer is "yes" you can do this:
Install terminal emulator from google play store. Open it and writte "su"
now writte this:
settings put global policy_control immersive.status=*
Tachan! you have immensive mode active. Only save the command in a note app. Always you reboot your phone the only thing you have to do is open terminal, su and paste your command.
A lot more easy and fast than do it with adb. the only "problem" is you need root.
If someone knows how to add an exception, please say so.

How do you show it on lock screen? Any ideas?

"Permission denial: writing to settings requires:android.permission.write_security_settings"

ramsyst said:
"Permission denial: writing to settings requires:android.permission.write_security_settings"
Click to expand...
Click to collapse
Did you manage to overcome this getting same error here
NVM, fixed it

ralphoberholzer said:
Did you manage to overcome this getting same error here
NVM, fixed it
Click to expand...
Click to collapse
Still getting the same error, how did u get around it ?

ramsyst said:
Still getting the same error, how did u get around it ?
Click to expand...
Click to collapse
Enable USB debugging (security settings) under developer options.
I used SystemUI Tuner as it allows for blacklisting apps (sucha as whatsapp) that don´t manage full screen well.

ralphoberholzer said:
Enable USB debugging (security settings) under developer options
Click to expand...
Click to collapse
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
Worked great, Thanks

pidobeuliou said:
Hi,
Our Xiaomi MI 9T is splendid with its great AMOLED full screen without any notch or hole.
However, the web browsers like Chrome (and others apps) doesn't propose the possibility in the settings to remove the notification bar and to get a true immersive full screen mode.
No problem, adb is there!
No need to root the smartphone.
1/ Activate the Developper mode
Go to Parameters/ About the phone
Click many times (at least 10) on the MIUI Version to activate the Developper mode
2/ Activate USB Debugging
Go to Parameters/... Others parameters/Developper options
Click on USB debugging
Click on Install via USB => You will have to connect to your MI account
Click on USB debugging (security parameters)
3/ Launch adb on your PC
Get adb.exe on the net (very easy)
Put it in a folder of your PC (for instance C:/adb)
Connect your smartphone to the PC
Launch a DOS command window
Go to the adb folder => cd /adb
To check if your smartphone is ready, type:
Code:
adb devices
If it's the first time, there will be a popup on your smartphone to authorize the adb commands
Then, normally your device will appear after typing "adb devices"
4/ Get the list of applications installed on your smartphone
Code:
adb shell pm list packages
Retrieve the name of the application(s) you want to remove the notification bar.
5a/ For instance, hide the notification bar only for Chrome and Google Photos
Code:
adb shell settings put global policy_control immersive.status=com.android.chrome,com.google.android.apps.photos
Note: Each time you enter this command, you cancel the previous one. You need to type only one command with all the apps you want to remove the notification bar (names of app are separated by a comma ,).
5b/ For instance, if you want to hide the notification bar for all the applications
Code:
adb shell settings put global policy_control immersive.status=*
6/ If you want to cancel this setting and put back the notification bar
Code:
adb shell settings put global policy_control null*
Enjoy your brillant full screen mainly when you are in dark mode.
:good:
Click to expand...
Click to collapse
I am sorry friend, bootloader unlocked ?

wilmerwils said:
I am sorry friend, bootloader unlocked ?
Click to expand...
Click to collapse
No, it's not necessary to unlock the bootloader.
You have just to activate the developper mode as I indicate it.

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
Yes, it's true. Each time you reboot the phone, you should loose the setting.
And good point, thank you Ramsyst, I didn't check on Google Play Store the myriad of immersive mode applications!!
I have tested "Immersive Manager Application" and it's perfect. Very simple and it works even when you reboot your phone. :good::good:
I had previously created a task with Tasker and AutoTools (paid version) to change the immersive mode with the "Custom Setting" feature. But knowing that there are many apps (free and paid version) doing that better than AutoTools, it's not usefull to describe how I did it.

pidobeuliou said:
Yes, it's true. Each time you reboot the phone, you should loose the setting.
And good point, thank you Ramsyst, I didn't check on Google Play Store the myriad of immersive mode applications!!
I have tested "Immersive Manager Application" and it's perfect. Very simple and it works even when you reboot your phone. :good::good:
I had previously created a task with Tasker and AutoTools (paid version) to change the immersive mode with the "Custom Setting" feature. But knowing that there are many apps (free and paid version) doing that better than AutoTools, it's not usefull to describe how I did it.
Click to expand...
Click to collapse
Thank you too! I didn't know this immersive mode was possible until i stumbled on your thread. Now, we can all enjoy that beautiful screen 100%!

No devices / emulator found ... Please help. I instal drivers do all on this topic

ramsyst said:
Thank you! It worked, but as stated above, it reset after phone restart.
Maybe running a tasker command at boot might fix it ?
Edit: Use the Immersive Manager app (thank me later!)
Click to expand...
Click to collapse
With Tasker you already have an option to make all apps you want to go immersive! There is no need to use any other command or app.
I believe everybody in the world should buy tasker
Is the best Android app. It may looks hard in the begining, but your imagination is the limit to do whatever you want.

Hi how can i used this on split screen but in full screen mode with status bar and navigation?

MrYuu said:
Hi how can i used this on split screen but in full screen mode with status bar and navigation?
Click to expand...
Click to collapse
You're right. I had never tested the split screen function. The notification bar is not hidden on split screen mode even when immersive mode is activated. The result is a bit weird as there is a mix of notification bar and app on the top of the screen.
"Google search" indicates that you are not the first one to face this issue... but apparently no solution has been found so far.
If somebody can help.

Question How to access fastboot ?

Hi,
I recently try to root my OPPO RENO 6 5G (PEQM00).
I bought an unlocktool license and I managed to unlock my bootloader however I had to flash the wrong rom (A11 and not A16) due to the wifi and bluetooth not working anymore ...
Here are some pictures: my oem unlock is ok, magisk is well installed.
I managed to patch the correct version of the boot.img with magisk but I cannot access fastboot to flash the correct version ...
When I try I have the message:
serial_do_not_match
fastboot verify fail
If you have a solution ... I also can't get the scatter file ... I have an error
Thanks, R3MY

I want to clarify that the problem probably comes from the boot.img because in recovery mode when I try to update online I manage to connect to wifi.

Hello may I ask if you have had any success in rooting the OPPO RENO 6 5G? If so, can you share the steps on how to access fastboot mode? Thank you in advance...
If I am not mistaken, Oppo company has strict policy against rooting, so they disable fastboot mode to make it difficult to root.

dima114 said:
Hello may I ask if you have had any success in rooting the OPPO RENO 6 5G? If so, can you share the steps on how to access fastboot mode? Thank you in advance...
If I am not mistaken, Oppo company has strict policy against rooting, so they disable fastboot mode to make it difficult to root.
Click to expand...
Click to collapse
Hi dima114,
I use Unlocktool to bypass authentification on OPPO Reno 6 5G. (it's a paid software).
U can add me on discord it's more simple to exchange. R3MY#4706
Regards, R3MY

remy411 said:
Hi,
I managed to patch the correct version of the boot.img with magisk but I cannot access fastboot to flash the correct version ...
Click to expand...
Click to collapse
Try ""adb reboot fastboot"" maybe ?

rootinhoppo said:
Try ""adb reboot fastboot"" maybe ?
Click to expand...
Click to collapse
I have already try i have this error : unlock_verify_fail so the phone reboot in normal mode.

Ok.
You can try to temporarily disable all kind of locking (pin code, gesture...)
I see you have an option "do not user lockscreen ("ne pas utiliser le chiffrement d'application") in developer mode. Although I don't believe it'll change anything, you can try with this option on. And, at the very bottom of the developper mode, you may have an option called "disable permission monitoring" ("desactiver la surveillance des applications"). You may toggle this one too.
Then test again and see if it changes something. Either way, don't forget to put the options back to normal when you're done.
ps: btw, when you type "adb devices", your device id appears, right?

rootinhoppo said:
Ok.
You can try to temporarily disable all kind of locking (pin code, gesture...)
I see you have an option "do not user lockscreen ("ne pas utiliser le chiffrement d'application") in developer mode. Although I don't believe it'll change anything, you can try with this option on. And, at the very bottom of the developper mode, you may have an option called "disable permission monitoring" ("desactiver la surveillance des applications"). You may toggle this one too.
Then test again and see if it changes something. Either way, don't forget to put the options back to normal when you're done.
ps: btw, when you type "adb devices", your device id appears, right?
Click to expand...
Click to collapse
when i type adb devices, device id appear, yes.
But that's about it... i cannot enter fastboot mode no matter what i try... by pressing power+volume down, power+volume up, or pressing all 3 buttons together. I also tried to enter fastboot mode using adb command adb reboot-bootloader, to no avail.
I've also tried your suggestions, unfortunately, it doesnt work.

dima114 said:
when i type adb devices, device id appear, yes.
But that's about it... i cannot enter fastboot mode no matter what i try... by pressing power+volume down, power+volume up, or pressing all 3 buttons together. I also tried to enter fastboot mode using adb command adb reboot-bootloader, to no avail.
I've also tried your suggestions, unfortunately, it doesnt work.
Click to expand...
Click to collapse
Yeah it's normal OPPO don't like root and the bootloader is locked
You need to unlock your bootloader with a software like UnlockTool. (19$ for 3 Months)

remy411 said:
Hi dima114,
I use Unlocktool to bypass authentification on OPPO Reno 6 5G. (it's a paid software).
U can add me on discord it's more simple to exchange. R3MY#4706
Regards, R3MY
Click to expand...
Click to collapse
i add u discord, please accept. dedefathah