Dear all,
Since we still can not be able to flash EU or global firmware without erasing chip method (which has risks to lose EFS) I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB.
Please bear in mind to open debugging and for sure connect to PC.
adb shell pm uninstall –k —-user 0 com.elevenst
adb shell pm uninstall –k —-user 0 com.skt.massivear
adb shell pm uninstall –k —-user 0 com.skt.hps20client
adb shell pm uninstall –k —-user 0 com.kt.ollehusimmanager
adb shell pm uninstall –k —-user 0 com.skt.skaf.l001mtm091
adb shell pm uninstall –k —-user 0 com.skt.prod.dialer
adb shell pm uninstall –k —-user 0 com.sktelecom.minit
adb shell pm uninstall –k —-user 0 com.sktelecom.tauth
adb shell pm uninstall –k —-user 0 com.skt.t_smart_charge
adb shell pm uninstall –k —-user 0 com.sktelecom.vcoloring
adb shell pm uninstall –k —-user 0 com.skt.skaf.OA00018282
adb shell pm uninstall –k —-user 0 com.skt.skaf.OA00199800
adb shell pm uninstall –k —-user 0 com.skt.hpsagree
adb shell pm uninstall –k —-user 0 com.skt.skaf.OA00412131
adb shell pm uninstall –k —-user 0 com.lge.sktgnsstest
adb shell pm uninstall –k —-user 0 com.skt.skaf.A000Z00040
adb shell pm uninstall –k —-user 0 com.sktelecom.smartcard.SmartcardService
adb shell pm uninstall –k —-user 0 com.kt.serviceagent
adb shell pm uninstall –k —-user 0 com.lge.lgemembership
adb shell pm uninstall –k —-user 0 com.lge.findlostphone
Click to expand...
Click to collapse
benzersizadam said:
Dear all,
Since we still can not be able to flash EU or global firmware I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB.
Please bear in mind to open debugging and for sure connect to PC.
Click to expand...
Click to collapse
I've had firmware from every model on my demo device. you have to use ChipErase in LGUP 1.16 to flash other firmware.
So far only firmware that gave issue was south african. You run through setup, and can use the device, but if you power it off and back on, you have to go through setup again
although now that i have lgup drivers instlled, adb doesn't see my device anymore
KaptinBoxxi said:
I've had firmware from every model on my demo device. you have to use ChipErase in LGUP 1.16 to flash other firmware.
So far only firmware that gave issue was south african. You run through setup, and can use the device, but if you power it off and back on, you have to go through setup again
although now that i have lgup drivers instlled, adb doesn't see my device anymore
Click to expand...
Click to collapse
I dont think that I will risk to brick my device just for flashing another fw
benzersizadam said:
I dont think that I will risk to brick my device just for flashing another fw
Click to expand...
Click to collapse
I've done every single firmware variant, only issue was what I said on the south african firmware. I mean if you actually daily the device (I don't), I get it, its a hassle.
I'm just pointing out that your statement of "Since we still can not be able to flash EU or global firmware I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB."
is false information and that we can flash any firmware from anywhere in the world. Verizon Firmware actually has an OTA update already that successfully flashes as well.
KaptinBoxxi said:
I've done every single firmware variant, only issue was what I said on the south african firmware. I mean if you actually daily the device (I don't), I get it, its a hassle.
I'm just pointing out that your statement of "Since we still can not be able to flash EU or global firmware I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB."
is false information and that we can flash any firmware from anywhere in the world. Verizon Firmware actually has an OTA update already that successfully flashes as well.
Click to expand...
Click to collapse
I see but there is also another risks of losing NV file so imei and efs. It is irreversible and super dangerous.
So i will rephrase my text with your suggestion.
KaptinBoxxi said:
I've done every single firmware variant, only issue was what I said on the south african firmware. I mean if you actually daily the device (I don't), I get it, its a hassle.
I'm just pointing out that your statement of "Since we still can not be able to flash EU or global firmware I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB."
is false information and that we can flash any firmware from anywhere in the world. Verizon Firmware actually has an OTA update already that successfully flashes as well.
Click to expand...
Click to collapse
Is Is possible you share us the firmware and guide here to change it from south Korean firmware
waseem.gani said:
Is Is possible you share us the firmware and guide here to change it from south Korean firmware
Click to expand...
Click to collapse
There is a guide, look at the LGUP 1.16 post I have. You would use ChipErase to flash another region's firmware. ALTHOUGH, it seems that non-demo devices can't do it. Some regions have issues as well. Best luck I've had is verizon firmware, but that's because its a verizon demo device. Make the firmware match your exact device model number
benzersizadam: do you still facing this problem??
Error:0x5319, Not allow to change the device (COM_KR->COM1_EU)
i am getting this error and cant flash even with chip erase...
nijat1122 said:
benzersizadam: do you still facing this problem??
Click to expand...
Click to collapse
yes i still can not change the region due to imei problem
benzersizadam said:
Dear all,
Since we still can not be able to flash EU or global firmware without erasing chip method (which has risks to lose EFS) I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB.
Please bear in mind to open debugging and for sure connect to PC.
Click to expand...
Click to collapse
Sweet, good tip! I will do this once I get my device. Question tho, what's up with the region and imei problem? Why would you want to set it to another (your current) region, what's the benefit?
Ok...someone help me here... I have a lg Velvet korean model 900N. I have hybrid sim slot but no option to use two sim at a time in the phone settings. I know, korean model doesn support dual sim.but as i have two sim slot.is it possible to enable dual sim if I switch firmware. Can anybody confirm? if possible, a detailed guide would be highly appreciated. Sorry for posting it here, Velvet forum doesn't have much activity regarding this issue. Thanks guys.
benzersizadam said:
Dear all,
Since we still can not be able to flash EU or global firmware without erasing chip method (which has risks to lose EFS) I found all Korean (SK Telecom) and related apps and removed it. Just wrote following commands one by one via ADB.
Please bear in mind to open debugging and for sure connect to PC.
Click to expand...
Click to collapse
You can try by flashing European firmware LM-G900EM in your LM-G900N by using following method provided in the link.I am not responsible if any damage occurs. Post in thread 'Firmware Switch' https://forum.xda-developers.com/t/firmware-switch.4307817/post-87450935
stefanw1337 said:
Sweet, good tip! I will do this once I get my device. Question tho, what's up with the region and imei problem? Why would you want to set it to another (your current) region, what's the benefit?
Click to expand...
Click to collapse
well lots of reasons behind. but main problem is bloatware and language.
Related
I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
aequitas3 said:
I know that this issue has yet to be resolved, but I noticed that it is popping up for some of us P769BK users who decided to be 'guinea pigs' by testing the waters of flashing kdz files from various L9 devices, so I figured it would be best to start an actual thread instead of asking in threads not relevant to the question at hand.
I saw a post by Lelus asking an individual if they could give the touch firmware version, which gave me the idea that this is potentially reversible with some time and patience (mainly for my sake since I have one L9 just to mess around with ). The touch firmware version on my daily P769BK is 6, whereas the firmware version on my "play-around" P769BK is firmware 12 after flashing the India kdz file onto it and flashing it back to stock V10G kdz. Any suggestions on where the touch firmware could be located to be pulled from a working L9 and be pushed onto the other via adb after applying the new rooting method?
Just an info note: both of my P769BK are on V10G, one rooted and OTA updated with Voodoo root keeper, the other one stock V10G with mirrored touch issue.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yes I have tried flashing the Canadian V11A kdz and no luck with that one either. The touch screen is still mirrored, but not entirely sure what the firmware version is, if it stays 12 or changes.
Sent from my LG-P769 using xda app-developers app
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
No LG logo is normal and not inversely colored. Although I didn't think to wiping system with fastboot and then flashing the kdz, I'll give that a try in a little.
Sent from my LG-P769 using xda app-developers app
Lelus said:
Either v10g kdz doesn't have touch screen firmware update ,or flasher checks version before update and doesn't downgrade I don't think it can be pulled from working phone.
Have you tried flashing your phone with wind 10a http://csmgdl.lgmobile.com/swdata/WDLSW/LGP769/AAWCBK/V11a_00/V11A_00.kdz ?
Click to expand...
Click to collapse
Yeah i think u r right about the updater not updating the touch screen firmware...because i get to see several parameters errors reoccurring while flashing any kdz....and if there was any way to reflash the touchscreen firmware then maybe the problem would resolve....i think the TS firmware in the v10E is different (if any user could confirm) then is it possible to downgrade to that firmware...as it seems that flashing the Indian kdz has downgraded the TS firmware....sorry had to get my doubts cleared in front of the experts
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Tablechair said:
When you guys boot is the LG logo mirrored and reverse colored?
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
Maybe if you wipe system with fastboot and then flash kdz?
Click to expand...
Click to collapse
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
Lelus said:
I'm pretty sure now that controller module has built-in firmware and it's compiled into kernel. From what I can tell, flashing takes place if the ver present in the EEPROM is at a lower revision than the one embedded into the module.
Click to expand...
Click to collapse
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
PROgenitor said:
The LG logo is mirrored and inverse coloured when flashing from Indian kdz to T-mobile v10G....but after flashing the canadian v11A the mirrored effect of the screen goes away...but the touch mess-up issue remains.
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
So does that mean flashing a new kernel(namely v10E) or reflashing the same kernel could install the TS drivers afresh?
Click to expand...
Click to collapse
Unfortunately not... a kernel would have to have touch screen firmware v13 or higher and p769v10g is 6 which is probably latest.
http://forum.xda-developers.com/showpost.php?p=39268215&postcount=24
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
I'll give it a try after testing the wiping of /system via flashboot doesn't do any good lol
Sent from my LG-P769 using xda app-developers app
Anyone give a try? I would but im kinda poor and this is my only phone.
Lelus said:
I'm pretty sure this won't work and can be damaging , but if someone is willing to give it a try:
Unzip 19.bin (which is just 10k of 00's) to sdcard
On a rooted phone with proper stock rom
$ adb shell
$ su
$ echo 1 /sdcard/external_sd/19.bin > /sys/devices/virtual/input/lge_touch/firmware
Reboot phone
Again , there is possibility of damaging your device.
Click to expand...
Click to collapse
I just saw the 19.bin file and as told by you, its 10kilobytes of just Null characters (Hex Code 00).
Are you replacing file with name "firmware" and size only 89bytes with a file of 10000bytes? The file "firmware" actually is a text file which holds only firmware version number. Will this work? Anyone tried?
Doesnt KDZ flashing replaces this file too?
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
Here is my output.
Code:
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 77 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ #
[email protected]:/ # uname -a
uname -a
Linux localhost 3.0.21 #1 SMP PREEMPT Wed Jan 9 16:40:29 KST 2013 armv7l GNU/Lin
ux
[email protected]:/ #
ls -la /sys/devices/omapdss/display0/driver
[email protected]:/sys/devices/omapdss/display0 # ls -la /sys/devices/omapdss/display
0/driver
es/omapdss/display0/driver <
lrwxrwxrwx root root 2013-03-11 00:47 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/sys/devices/omapdss/display0 #
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
there isn't module for the touch screen, it's statically compiled into kernel
Lelus said:
there isn't module for the touch screen, it's statically compiled into kernel
Click to expand...
Click to collapse
I see.
kevev said:
PROgenitor: Have you tried flashing the T-Mobile P769 10G KDZ? If you have not, try this first. Use the instructions posted by cmahendra for gaining root via KDZ flash.
But before doing this, may we have the output from these commands first?
adb shell
su -
lsmod
uname -a
ls -la /sys/devices/omapdss/display0/driver
I am wondering if you have a different kernel, or just a different module. It could still be an init script issue.Would you also be able to share a CWM backup before flashing the KDZ so that I can compare?
Click to expand...
Click to collapse
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
C:\Root\stuff>adb shell
[email protected]:/ $ su -
su -
[email protected]:/ # lsmod
lsmod
bcmdhd 410031 0 - Live 0xbf053000
omaplfb_sgx540_120 19252 0 - Live 0xbf04a000
pvrsrvkm_sgx540_120 259245 67 omaplfb_sgx540_120, Live 0xbf000000
[email protected]:/ # uname -a
uname -a
sh: uname: not found
127|[email protected]:/ # ls -la /sys/devices/omapdss/display0/driver
ls -la /sys/devices/omapdss/display0/driver
lrwxrwxrwx root root 2013-03-12 13:22 driver -> ../../../bus/om
apdss/drivers/tx11d108vm_panel
[email protected]:/ #
Click to expand...
Click to collapse
PROgenitor said:
I have tried flashing P769 V10G(T-mobile) and V11A Canada(Wind) several times after the issue....but no success...so i flashed the P765 V10C(India) and gained root and installed CWM recovery.....Then via recovery i restored a CWM backup of a rooted P769 V10G(from cmahendra's post)....I am currently on that....i will just try and give you the output.
My Output:
Click to expand...
Click to collapse
Does this mean, you have not yet tried LELUS method alongwith direct flashing of P769V10G or P769V11A?
If not yet done, try that with HARDRESET to phone before and after the flashing with Lelus root. :good: Good luck.
Could someone with a phone other then p769 check their touchscreen firmware version.
Lelus said:
Could someone with a phone other then p769 check their touchscreen firmware version.
Click to expand...
Click to collapse
P765 V10G India , Touch Firmware Version: 12.
EDIT:
3845#*765# ---> H/W Device Test --->Touch Test --->Touch Firmware Version : 12
P765: IPS Display
P769: Corning Gorilla Glass
I've successfully rooted my device via Kingroot (Super stoked!). However, I'm not as savvy as others and need to wait for further development and user friendly installs.
Is there any method to prevent OTA updates from downloading/installing automatically?
from adb:
confirm PC can see the fire:
adb devices
get to adb shell
adb shell
Then run:
pm block com.amazon.otaverifier
pm block com.amazon.dcp
positivehxcgo said:
I've successfully rooted my device via Kingroot (Super stoked!). However, I'm not as savvy as others and need to wait for further development and user friendly installs.
Is there any method to prevent OTA updates from downloading/installing automatically?
Click to expand...
Click to collapse
I have the following 2 packages blocked via ADB (This will stop OTA)
com.amazon.otaverifier
com.amazon.dcp
this is posted in @andersonsalas rooting guide
I have been researching the ADB thing all day - and I STILL don't seem to grasp it.
positivehxcgo said:
I have been researching the ADB thing all day - and I STILL don't seem to grasp it.
Click to expand...
Click to collapse
I'm pretty sure there is a good tutorial on XDA somewhere to get you setup and running. It's actually quite simple don't dig in too deep to start, I'll post a link to it if I can find it, I'm bored at work anyway
If you are not an H918, H830, or US996 (Unlocked, NOT US Cellular) user, kindly leave this thread, this will not do anything for your device, exchange it if you're so desperate. Thank you.
Note for US996: It's probably easier for you guys just to flash TWRP the normal way and pull your battery then do the factory reset dance to get in!
Team Win Recovery Project 3.0.2-1
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
This will allow you to install TWRP and flash SuperSU!
Step 1: Unlocking your bootloader
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
H918/H830 users only:
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You will probably need to complete the Android setup wizard at this point to get access to ADB again.
US996 users only:
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
Once you're finished with unlocking your bootloader, continue on to step 2.
Step 2: Running recowvery
You can find the recowvery binaries (you need to download all of these) at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow#running (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3: Flashing TWRP & Rooting
Notice: There is currently no decryption support, just the same as the LG G5, I'm running into the exact same scenario (unable to start rpmb device).
Due to this, I have disabled hardware decryption in this build to keep it stable. If you wish to have your data work in TWRP, you will need to disable decryption.
If you're coming from the Note 7 or S7, this will be a familiar scenario for you.
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, you can also just use adb push. (mentioned here)
Download TWRP: (official builds, V20 is waiting for TWRP 3.1.0 for twrp.me download)
H918: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
US996: https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-us996.img
H830: https://twrp.me/devices/lgg5h830.html
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU: https://download.chainfire.eu/supersu
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4: Have fun!
I know a few people have mentioned donating, there is a button right on this post under my username.
Sorry, I don't keep a list as I prefer to keep people's information confidential, but if you do send any money my way, you can request that I mention you at the bottom of this post with any details.
I ask that people please not attach files in this thread, everything required is mentioned in this post, and should be stable in its present state. Thank you.
Thanks for testing on my phone! =]
Does This wipe data on the phone?
justthefacts said:
Does This wipe data on the phone?
Click to expand...
Click to collapse
Unlocking the bootloader does.
jcadduono said:
Alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over TeamViewer thanks to @slayerh4x and @Darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that I'm still working on getting TWRP to boot, there seems to be something about the stock kernel sources that doesn't want TWRP to be a part of it.
This will not get you SuperSU or app root access, this is only a root shell allowing you to flash TWRP when it's ready and do other things.
This does however open up some methods of installing SuperSU without TWRP. @Chainfire might have some ideas if he wishes to show up here and stir up some noise.
We do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for TWRP.
For the instructions on using recowvery, you should read the README.md on the GitHub page:
https://github.com/jcadduono/android_external_dirtycow
You can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
You will need to unlock your bootloader first. For this you'll probably need LG's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
You will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in PTP mode (for transferring images). I don't know why this is, a misconfiguration in LG's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
Warning: This step will wipe all your data and factory reset your phone!
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
You should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, I'm really tired.
Click to expand...
Click to collapse
Thank you for taking the time to begin with the first step to develop on this device! (although i will have to do a replacement tomorrow for 2 defects that emerged on my phone) I always had in mind that this device had only a 50% of chances to get rooted, and that it might actually never get rooted . But now chances have increased even more thanks to your hard work. and also thanks to the others you previously mentioned. Let us see if Chainfire takes an interest on adding the final details :good:
I've got ADB working fine, but get nothing with fastboot. Just a blank line when I type 'fastboot devices'. Tried 3 different USB ports also. Windows 10 x64.
I did grab the ADB/fastboot files linked in the first post, but the older files I had don't work either, and they have no issues with my Nexus 7 2013 and HTC 10.
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
So Idk what to do or how to get the file to flash it.. Any help?
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
My advice? Never, ever take an update until the developers say that they are sure they can exploit it. From what I can see, this process uses the "dirty cow" exploit which will assuredly be fixed on the next security update.
---------- Post added at 05:11 PM ---------- Previous post was at 05:10 PM ----------
bambam126 said:
So Idk what to do or how to get the file to flash it.. Any help?
Click to expand...
Click to collapse
Why not wait until they can get full root and TWRP? As I see it, this process is to help other developers and people that know what they're doing refine and advance the move to full root. I don't think it's quite ready for prime time yet. It does nothing but get the foot in the door for rooting.
---------- Post added at 05:17 PM ---------- Previous post was at 05:11 PM ----------
And, we're off to the races. Let the "I bricked my phone" threads begin!
douger1957 said:
[/COLOR]And, we're off to the races. Let the "I bricked my phone" threads begin!
Click to expand...
Click to collapse
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
mrtruckincowboy said:
Promising stuff ,I just upgraded to this phone yesterday ,and was hoping to eventually get custom roms on it
Sent from my VS995 using Tapatalk
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Quick question should I wait or take the ota updates?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
mrtruckincowboy said:
They discuss unlocking in the first post so I'm optimistic. Even if not there has been custom stuff done around locked bootloader.I came from s4 and that was possible with the loki method so im optimistic
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
Oh. Great to know. I hope they manage to do something with the verizon variants, in fact, with all the variants . Maybe after that they will have more interest on the device
jcadduono said:
alright, so you guys have probably heard about me working on this project for a week now. Sorry it's been taking so long, there's been so many variables and hurdles to go through!
I don't own the device myself, so it was all done over teamviewer thanks to @slayerh4x and @darriousx who stayed around in the #twrp channel on freenode to assist with their devices.
Understand that i'm still working on getting twrp to boot, there seems to be something about the stock kernel sources that doesn't want twrp to be a part of it.
this will not get you supersu or app root access, this is only a root shell allowing you to flash twrp when it's ready and do other things.
this does however open up some methods of installing supersu without twrp. @chainfire might have some ideas if he wishes to show up here and stir up some noise.
we do have the ability to do a full ramdisk unpack, edit, repack, and flash within the confines of /data/local while booted into the permissive system using recowvery-applypatch.
This should bring some opportunities, but it's still more sane to just wait for twrp.
For the instructions on using recowvery, you should read the readme.md on the github page:
https://github.com/jcadduono/android_external_dirtycow
you can find the recowvery binaries prebuilt at:
https://build.nethunter.com/android-tools/dirtycow/arm64/
you will need to unlock your bootloader first. For this you'll probably need lg's drivers.
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00120120425
mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?filekey=uw00320110909
you will also need adb and fastboot. You can download them in a portable small form factor here:
http://forum.xda-developers.com/android/software/host-tools-t3402497
start by turning on developer options in settings -> about device -> software info -> build number. (tap 7 times until it's enabled)
now navigate to settings -> developer options -> oem unlock. (turn it on)
don't ever turn oem unlock or developer options off when using a custom rom or recovery. This could lose to loss of all your data.
For your computer to see adb, you will need to put the phone in ptp mode (for transferring images). I don't know why this is, a misconfiguration in lg's kernel gadget drivers maybe?
Extract adb and fastboot to a folder on your pc.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other usb ports.
To unlock your bootloader, use fastboot oem unlock once the phone boots into fastboot mode.
warning: This step will wipe all your data and factory reset your phone!
you can check the status of your bootloader lock with the fastboot getvar all command.
Ex. (bootloader) unlocked:yes
you should now boot back into your phone (fastboot reboot).
You're now ready to follow the recowvery installation instructions.
See here: https://github.com/jcadduono/android_external_dirtycow
there's also a full write up on that page on how recowvery works if you're into that kind of stuff.
I probably need to proof read it though, i'm really tired.
Click to expand...
Click to collapse
you are the man !!!!!!!!!!!!!!!!!!!!!!!
joseguillen1994 said:
LOL! YASSSSSS i can imagine that already. There will be some who will get it hard bricked .
---------- Post added at 05:39 PM ---------- Previous post was at 05:34 PM ----------
Isn't your model the verizon model? If it is... I havent heard any Verizon user to have unlocked the bootloader for their LG V20's. Not to be a downer, but the methods on this thread are only possible for the H918 (Tmobile variant). unless someone found a way to unlock Verizon's bootloader.
Click to expand...
Click to collapse
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
douger1957 said:
For me, there's a certain amount of education that needs to be tackled before you start messing with a phone. I have never had a LG smartphone before, but rather quickly discovered that LGUP is not ODIN, and that yes, you can hard brick a LG doing stuff that a Samsung will shrug off.
Too many people are impatient and won't let the developers come out with a product that is relatively easy to use. Too many people won't take the time to learn what they're doing and how to fix their mistakes. Too many people won't bother to read and follow simple instructions, and too many people think their experience on other phones will play out here. The only thing this phone has in common with others is the basic Android. It's what LG has put on top that has given the developers a hard time. That, and Nougat seems to be a new beast to be slain.
Click to expand...
Click to collapse
yup! i couldn't have written it better hahaha. But it is bound to happen for some people that will not pay careful attention. I mena, im not an expert, im maybe a little more than a noob now since i have been dealing with this for quite some time, and that is why i just started my C++ class in order to reach at least a good-to-go level of understanding.
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a H918 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Locked or unlock
jcadduono said:
As this method does not ever mount your system r/w, it won't brick your system. Since it also can't provide you with real root access until you reboot recovery into a permissive system, you risk no chances of bricking your device if this is not for it, because if your device is locked, the recovery will refuse to boot and be replaced with stock again 2 seconds later.
Unfortunately I have not yet disabled verity in the fstab, so if a V20 user uses their new root shell to remount system as r/w then they will be bricked. I'll see if I can find a decent way to do this...probably with sed.
But yeah. You're safe if your bootloader is locked.
Click to expand...
Click to collapse
Oh, ye of little faith. Where there's a will, there's a way.
Chainfire just tweeted:
Just installed SuperSU on a V20, based on @jcadduono 's initial work. Good times.
Can this method be used on other devices?
Sent from my R1HD(ZenUI) via Tapatalk
I have a Nova 3e (ANE-AL00), i been rebrand to ANE-L21C432 EU version, everything work but auto-rotate ,i check the detail on huawei cn/eu website ,.cn version didn't have Gyroscope sensor ,eu version come with Gyroscope , highly recommend don't rebrand your AL00 -L21C432!
how did you rebranded ? using twrp ?
I just flashed system.img in ANE-AL00 from ANE-L21 and now all google stuff works with no chinese bloatware.
anuj0sharma said:
how did you rebranded ? using twrp ?
I just flashed system.img in ANE-AL00 from ANE-L21 and now all google stuff works with no chinese bloatware.
Click to expand...
Click to collapse
Hi, could you briefly outline how you rebranded your device?
I assume you unlocked the boot loader via the Huawei form page, installed TWRP, and simply flashed system.img from ANE-L21? Any other steps? Thanks!
sweetjuice said:
I have a Nova 3e (ANE-AL00), i been rebrand to ANE-L21C432 EU version, everything work but auto-rotate ,i check the detail on huawei cn/eu website ,.cn version didn't have Gyroscope sensor ,eu version come with Gyroscope , highly recommend don't rebrand your AL00 -L21C432!
Click to expand...
Click to collapse
Then how does the screen rotate normally?
Letzen said:
Then how does the screen rotate normally?
Click to expand...
Click to collapse
screen rotate not work !
sweetjuice said:
screen rotate not work !
Click to expand...
Click to collapse
So, to clarify:
1. Auto-rotate doesn't work in China Version.
2. Auto-rotate works in European Version.
Right?
Jello_Conspiracy said:
Hi, could you briefly outline how you rebranded your device?
I assume you unlocked the boot loader via the Huawei form page, installed TWRP, and simply flashed system.img from ANE-L21? Any other steps? Thanks!
Click to expand...
Click to collapse
exactly!
Options 1:
unlocked bootloader.... (there was no possibility to do it with Huawei webpage anymore so.. i have to pay to DC-unlock ) but it worked !!
installed TWRP and flashed system.img on system image partion.. (not system...it was system image). After reboot it was showing my model as ANE-AL00 only but, there was nothing Chinese. The firmware was complete of international unlocked version.
Option 2:
There is one more way now.. using TWRP only you can use this tool .. https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the step on the page and you will have the ANE_AL00 working as ANE-LX1 (remember your phone will still show you ANE-AL00 because we are not rebranding it.. just flashing another firmware which is more user friendly with all google stuff out of the box)
Option 3:
Another way is to search a patch for google framework for chinese phones .. you may have to download .apk on phone or on pc and after flashing that you will have google paystore on your device and you can install all google stuff post that.. (it seems the most safest way so far as you dont have to root, unlock bootloader or temper your device anyway and install all google apps.. )
To get rid of Chinese apps or bloatwares you can use adb ..
steps:
1. connect device, make sure ADB is working (check with CMD "adb devices")
2. go to shell, using CMD "adb shell"
3. get list of install packages using CMD "pm list packages" (use google to find out what does each package name means).
4. remove package using CMD "pm uninstall -k --user 0 $packagname" (e.g. pm uninstall -k --user 0 com.android.inputdevices)
5. if correctly typed, you receive message "SUCCESS"
if step 3 is not user friendly for you. ... head on to paystore and install an app named "app inspector".
go to apps tab in the app and you will see all the istalled apps on your device. click the app you want to remove and see the name of the app on the top..
the name will start with "com.xxxxxxxxxxx". it will remove the app permanently.
I hope the tips will be helpful for all those bought the Chinese version like me and were wondering seeing the Chinese stuff all around the phone.
Please do not forget to hit thanks if it helps you anyway..
anuj0sharma said:
exactly!
Options 1:
unlocked bootloader.... (there was no possibility to do it with Huawei webpage anymore so.. i have to pay to DC-unlock ) but it worked !!
installed TWRP and flashed system.img on system image partion.. (not system...it was system image). After reboot it was showing my model as ANE-AL00 only but, there was nothing Chinese. The firmware was complete of international unlocked version.
Option 2:
There is one more way now.. using TWRP only you can use this tool .. https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Follow the step on the page and you will have the ANE_AL00 working as ANE-LX1 (remember your phone will still show you ANE-AL00 because we are not rebranding it.. just flashing another firmware which is more user friendly with all google stuff out of the box)
Option 3:
Another way is to search a patch for google framework for chinese phones .. you may have to download .apk on phone or on pc and after flashing that you will have google paystore on your device and you can install all google stuff post that.. (it seems the most safest way so far as you dont have to root, unlock bootloader or temper your device anyway and install all google apps.. )
To get rid of Chinese apps or bloatwares you can use adb ..
steps:
1. connect device, make sure ADB is working (check with CMD "adb devices")
2. go to shell, using CMD "adb shell"
3. get list of install packages using CMD "pm list packages" (use google to find out what does each package name means).
4. remove package using CMD "pm uninstall -k --user 0 $packagname" (e.g. pm uninstall -k --user 0 com.android.inputdevices)
5. if correctly typed, you receive message "SUCCESS"
if step 3 is not user friendly for you. ... head on to paystore and install an app named "app inspector".
go to apps tab in the app and you will see all the istalled apps on your device. click the app you want to remove and see the name of the app on the top..
the name will start with "com.xxxxxxxxxxx". it will remove the app permanently.
I hope the tips will be helpful for all those bought the Chinese version like me and were wondering seeing the Chinese stuff all around the phone.
Please do not forget to hit thanks if it helps you anyway..
Click to expand...
Click to collapse
Thanks so much! Appreciate the detailed reply!
sweetjuice said:
I have a Nova 3e (ANE-AL00), i been rebrand to ANE-L21C432 EU version, everything work but auto-rotate ,i check the detail on huawei cn/eu website ,.cn version didn't have Gyroscope sensor ,eu version come with Gyroscope , highly recommend don't rebrand your AL00 -L21C432!
Click to expand...
Click to collapse
Hi, did you find anyway to make the screen autorotate..
before flashing the ANE-L21 rom my auto rotate used to work in my ANE-AL00.
The mistake I did was, along with the update.zip i also flashed xxx_hw.zip file in twrp.
First time with only system.img, everything was working well without any issue. Now also the phone works well but, without screen auto rotate.
Can someone link or upload the xxx_hw.zip file for ANE-AL00 ? I am sure that shall solve the problem.
Thanks.
anuj0sharma said:
Hi, did you find anyway to make the screen autorotate..
before flashing the ANE-L21 rom my auto rotate used to work in my ANE-AL00.
The mistake I did was, along with the update.zip i also flashed xxx_hw.zip file in twrp.
First time with only system.img, everything was working well without any issue. Now also the phone works well but, without screen auto rotate.
Can someone link or upload the xxx_hw.zip file for ANE-AL00 ? I am sure that shall solve the problem.
Thanks.
Click to expand...
Click to collapse
seems ANE-L22C636 HK ROM work perfectly on ANE-AL00!but i can;t find the ROM!
ANE-AL00 is an Indian model which does not have Gyroscope, having build #ANE-AL00 8.0.0.131 (C675)
Hi
Is p20 lite ANE-AL100 does't have gyro or is there any trick to enable it
indigo110 said:
ANE-AL00 is an Indian model which does not have Gyroscope, having build #ANE-AL00 8.0.0.131 (C675)
Click to expand...
Click to collapse
I have the Indian version ANE-AL00, it has Gyroscope and auto rotate.
kumarsid7 said:
I have the Indian version ANE-AL00, it has Gyroscope and auto rotate.
Click to expand...
Click to collapse
Are you sure about Gyroscope, youtube 360 video works on your phone?
I just checked and it is not working on my phone, currently, i am on ANE-AL00 8.0.0.154(C675) build
indigo110 said:
Are you sure about Gyroscope, youtube 360 video works on your phone?
I just checked and it is not working on my phone, currently, i am on ANE-AL00 8.0.0.154(C675) build
Click to expand...
Click to collapse
My bad! I was talking only about auto rotate of screen.
YouTube 360 and VR apps are not working.
Auto rotate must be working with acceleration.
How does 360 degree videos working on fb alone in ANE-AL00 8.0.0.154
hi
what is the easy way to rebrand
i have nove 3e from china
ane-al00
sensors
Any news about saving the sensors while rebranding? Thanks!
Hey all,
Not sure if this was the correct forum but seemed like a good starting place. Have 3 Verizon G6s and recently upgraded one to PIE and it SUCKS. Very slow. Some apps are not working. I want to go back to Oreo and never move to Pie until these phone die.
Previously I owned 5 different Samsung phones and rooted them all (some with stock ROMs, others with custom ones) so I have no qualms about tinkering but on this phone I use Google Pay so I need to find a way to revert back to a stock Oreo ROM, prevent it from future upgrades and keep Google Pay happy with what I did.
Anyone have a suggestion as to how to proceed or another forum to ask in?
Also, my other 2 phones keep nagging me to update and I would like to kill that request for good. Looking for help there too.
Thanks
Frank in Michigan
How to disable system updates without Root
Give credits to these posts and their respective owners:
https://android.stackexchange.com/q/56620
The one listed below I highly recommend. It is what made this possible for me.
Check it out for more about getting set up with ADB.
https://www.xda-developers.com/disable-system-app-bloatware-android/
For other carriers besides Verizon, use apps such as App Inspector (I used ES File Explorer) and find the offending apps' package name(s).
You can also use Developer Assistant if the app you want to disable comes up in your face while using your device.
This app shows what the package name is of the app running in the foreground.
The same set of commands worked well for me, disabling the updates on (Verizon branded) LG V20, G6 and V30 all running Oreo.
The updates app or update notifications have not bugged once since I used the treatment (below).
If I open Settings and touch "System Updates" it gives no response.
Assuming you already have ADB set up and USB Debugging enabled and authorized between phone and PC, connect your device to PC.
The command line below works for any pre-G7 LG phones that are VZW branded.
I have copied cmd.exe into my folder where ADB.exe is located, that's the CMD you should open in the next step...or use your preferred method of running ADB.
Run these 4 commands in CMD:
Code:
adb -d shell pm clear com.lge.lgdmwebviewer4vzw
adb -d shell pm clear com.lge.lgdmsclient
adb -d shell pm disable-user --user 0 com.lge.lgdmsclient
adb -d shell pm disable-user --user 0 com.lge.lgdmwebviewer4vzw
**THAT'S ALL IT TAKES***
If you saw "Success" after each of the above commands, you just won the lottery!
Disconnect your phone and enjoy no more pesky "update available" popups!
I haven't tried this yet, but if you want to downgrade, check this thread from the G7 forums: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
It obviously works on G7 so maybe it will on G6.
Please post results if any one reading this has done it.
The latest VS988 Oreo firmware can be located here.
https://lg-firmwares.com/downloads-file/20111/VS98820j_00_0620_ARB00
Hope this helps!
bakStāger said:
Give credits to these posts and their respective owners:
https://android.stackexchange.com/q/56620
The one listed below I highly recommend. It is what made this possible for me.
Check it out for more about getting set up with ADB.
https://www.xda-developers.com/disable-system-app-bloatware-android/
For other carriers besides Verizon, use apps such as App Inspector (I used ES File Explorer) and find the offending apps' package name(s).
You can also use Developer Assistant if the app you want to disable comes up in your face while using your device.
This app shows what the package name is of the app running in the foreground.
The same set of commands worked well for me, disabling the updates on (Verizon branded) LG V20, G6 and V30 all running Oreo.
The updates app or update notifications have not bugged once since I used the treatment (below).
If I open Settings and touch "System Updates" it gives no response.
Assuming you already have ADB set up and USB Debugging enabled and authorized between phone and PC, connect your device to PC.
The command line below works for any pre-G7 LG phones that are VZW branded.
I have copied cmd.exe into my folder where ADB.exe is located, that's the CMD you should open in the next step...or use your preferred method of running ADB.
Run these 4 commands in CMD:
Code:
adb -d shell pm clear com.lge.lgdmwebviewer4vzw
adb -d shell pm clear com.lge.lgdmsclient
adb -d shell pm disable-user --user 0 com.lge.lgdmsclient
adb -d shell pm disable-user --user 0 com.lge.lgdmwebviewer4vzw
**THAT'S ALL IT TAKES***
If you saw "Success" after each of the above commands, you just won the lottery!
Disconnect your phone and enjoy no more pesky "update available" popups!
I haven't tried this yet, but if you want to downgrade, check this thread from the G7 forums: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
It obviously works on G7 so maybe it will on G6.
Please post results if any one reading this has done it.
The latest VS988 Oreo firmware can be located here.
https://lg-firmwares.com/downloads-file/20111/VS98820j_00_0620_ARB00
Hope this helps!
Click to expand...
Click to collapse
i've wanted to downgrade Pie to Oreo, i used LG UP which was i guess 1.14 version, but it refused to downgrade giving an error, should i try it with this method?
has anyone downgraded their verizon G6 to oreo?
jafferkhan said:
i've wanted to downgrade Pie to Oreo, i used LG UP which was i guess 1.14 version, but it refused to downgrade giving an error, should i try it with this method?
has anyone downgraded their verizon G6 to oreo?
Click to expand...
Click to collapse
I would recommend using this LGUP 1.14 patched, kudos to mylgphones.com for posting them.
Direct download link is https:// drive.google.com/open?id=1SOhoR2hn9PKiIvUUeiDVeX-8PfuMx1qq
Remove space in the link, XDA doesn't let me insert links
After you run the MSI install file, copy the files from the patch folder and replace the originals in "C:\Program Files (x86)\LG Electronics\LGUP" or wherever you installed LGUP; make sure you replace the DLL file with the patched one as well.
I killed my updates when I was still at version VS98820e so I don't have any experience with downgrading from Pie myself.
I would suggest to make sure you have the LG mobile drivers installed first; and when you go to flash the KDZ, make sure you backup all your userdata first.
Then shut off your phone, hold VOLUME_UP key and connect to PC. You should see download mode appear within 5 seconds.
Now, on your PC, open LGUP and it should open to the connected device selection menu. Choose your phone and press OK. The next window should be the main LGUP window. I haven't tried it but I would suggest to use the "Update" option then load your kdz file in the "bin file" area and flash. If it doesn't flash successfully, use the "Refurbish" option instead.
Hopefully this helps someone to recover from the Pie dilemma! :laugh:
jafferkhan said:
i've wanted to downgrade Pie to Oreo, i used LG UP which was i guess 1.14 version, but it refused to downgrade giving an error, should i try it with this method?
has anyone downgraded their verizon G6 to oreo?
Click to expand...
Click to collapse
Did you success in downgrading pie to oreo?
I have the same concern if I can downgrade my G6 Verizon.
uphantom89 said:
Did you success in downgrading pie to oreo?
I have the same concern if I can downgrade my G6 Verizon.
Click to expand...
Click to collapse
Yes. Successfully downgraded.
Used a couple of files from the g7 forum for LGup and a dll file, it's very easy.
Now happily running Oreo on my Verizon G6
jafferkhan said:
Yes. Successfully downgraded.
Used a couple of files from the g7 forum for LGup and a dll file, it's very easy.
Now happily running Oreo on my Verizon G6
Click to expand...
Click to collapse
Wow, you lighten my hope . Let me try to downgrade. LG G6 Pie is slow.
BTW, may I know the instruction that you followed to downgrade?
uphantom89 said:
Wow, you lighten my hope . Let me try to downgrade. LG G6 Pie is slow.
BTW, may I know the instruction that you followed to downgrade?
Click to expand...
Click to collapse
OK here goes
1. Download the latest Oreo from lg-firmware...
2. Download LGup version 1.14 along with a .dll file from the g7 forum. You'll need to put that. Dll file inside a folder when you install LGup for it to prevent any errors and allow downgrade
3. Install all drivers properly
4. Put the phone in download mode
5. Select the kdz you downloaded from the firmware site
6. Hit start...
Wait for it to end and say 'successful.
7. After you set up the phone, factory reset it once then set it up to prevent battery drains and smoother performance.
jafferkhan said:
OK here goes
1. Download the latest Oreo from lg-firmware...
2. Download LGup version 1.14 along with a .dll file from the g7 forum. You'll need to put that. Dll file inside a folder when you install LGup for it to prevent any errors and allow downgrade
3. Install all drivers properly
4. Put the phone in download mode
5. Select the kdz you downloaded from the firmware site
6. Hit start...
Wait for it to end and say 'successful.
7. After you set up the phone, factory reset it once then set it up to prevent battery drains and smoother performance.
Click to expand...
Click to collapse
Thank you so much, let me try
jafferkhan said:
OK here goes
1. Download the latest Oreo from lg-firmware...
2. Download LGup version 1.14 along with a .dll file from the g7 forum. You'll need to put that. Dll file inside a folder when you install LGup for it to prevent any errors and allow downgrade
3. Install all drivers properly
4. Put the phone in download mode
5. Select the kdz you downloaded from the firmware site
6. Hit start...
Wait for it to end and say 'successful.
7. After you set up the phone, factory reset it once then set it up to prevent battery drains and smoother performance.
Click to expand...
Click to collapse
I did as your instruction, however, at step 6. , it ran 4% and then stop, an error board appeared with ".dll" error (I don't remember exactly the statement, but in short It requested me to use appropriate dll file). I did try several dll file but couldn't find the one that allow me to pass 4% installation loading
uphantom89 said:
I did as your instruction, however, at step 6. , it ran 4% and then stop, an error board appeared with ".dll" error (I don't remember exactly the statement, but in short It requested me to use appropriate dll file). I did try several dll file but couldn't find the one that allow me to pass 4% installation loading
Click to expand...
Click to collapse
sorry for the late reply, but as i mentioned, you will get the right .dll file for lgup 1.14 from the g7 forum linked in the earlier posts. replace it with the one you think isn't working. i faced the same issue and solved it