Database Users

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device

FULL Disk ENCRYPTION + ROOT Easy steps >>> HOW TO root & encrypt entire device
How to encrypt your rooted device. I wrote these instructions based on my Note 4 (T-Mobile branded N910T3 ) BUT they will work for ANY device!
THE SHORT OF IT:
YOU SIMPLY NEED TO ECRYPT YOUR DEVICE FIRST PRIOR TO ROOTING. YOU CAN ROOT IT AFTER IT IS ENCRYPTED, NOT BEFORE.
tested on Android 4, 5, & 6.
Once you root or install various roms you lose the ability to encrypt your device. This issue manifests itself in the form of either hanging, rebooting, or the animation just sitting there but not actually doing anything when you try to use the full disk encryption feature built into all modern versions of android. Below are the steps on how to get this native encryption feature working while still maintaining your root & favorite rom.
Credit goes to chatty kathy, i mean bruzzy who graciously and verbosely provided instructions on how to encrypt my rooted 12.2" Samsung Galaxy Note Pro (AT&T branded SM-P907A) here: http://forum.xda-developers.com/showthread.php?t=2791587
McFood on androidforums.com also reiterated much of the same here: http://androidforums.com/threads/how-to-encrypt-a-rooted-device.866968/
As usual: Use this guide at your own risk!
Quick Overview:
Unroot if rooted. Encrypt. Reroot. The only thing special is that you have to manually kick start SuperSU when rooting after the encryption is in affect. See steps 12 & 13.
INSTRUCTIONS:
-------------------
0. Make a backup to your external SD card of your entire system FIRST such as a nandroid backup via a custom recovery (Philz Touch, TWRP, etc). I even do modem, etc. just in case you ever need.
1. Ensure your device is not rooted and also not encrypted (if already rooted, skip to step 3; if already encrypted, decrypt or do a factory-reset - don't try CF-Auto-Root on an encrypted device, it'll soft-brick)
2. Root the device (I used this sticky: http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 )
3. Temporarily un-root the device (when using SuperSU: go to Settings and remove the tick at the option "Activate Superuser")
4. Reboot
5. Activate the device encryption (the battery must be at least at 80% and the device must be plugged in the wall charger)
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
7. After the encryption is finished the device will reboot and ask for the password, just log in
8. If not yet done, flash a custom recovery where you have console access or can use ADB as root (I used TWRP)
9. Boot into recovery. (POWER + VOLUME UP + HOME button together at the same time)
10. Mount /system (it's not mounted automatically, at least not in the version I used - TWRP 2.7.1.0).
11. Open a console or ADB shell to run the basic linux commands in red in the next two steps on the phone ((In TWRP it is under Advanced & then Terminal Command and start the console in any directory, it doesn't matter, i would choose the root directory / ))
11-continued: Laymans terms: go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in the commands in red in steps 12 & 13.
12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )
14. Reboot
15. Send the NSA a message and tell them to lick your balls. Oh wait nevermind they have a backdoor in AES... FTP = Fukt The Police :cyclops:

OP space
The real trick here is disabling (step 3) and then manually re-enabling (steps 12 and 13) root which you manually re-enable after the encryption is complete. The order is key. You cannot encrypt the device while rooted.
go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.

? on steps 12 + 13
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?

?
Bueller?

V3racious said:
6. The device will restart after a short period of time and start the encryption (this will take some time, but you should see a progress bar indicating how far it is)
Click to expand...
Click to collapse
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Exactly. I tried this before and got the same results.

jrkart99 said:
Exactly. I tried this before and got the same results.
Click to expand...
Click to collapse
I just gave up on root for now.

Breakdown of steps 12 & 13
jrkart99 said:
"12. Copy the su binary (if you use SuperSU you run this command: cp /system/xbin/daemonsu /system/xbin/su )
13. Execute the installation (if you use SuperSU run this command: /system/xbin/su --install )"
Where in TWRP do I do this?
Also, do I need to be in the rom I am choosing as my daily driver when i start this process? What do i do if I change roms?
Click to expand...
Click to collapse
For steps 12 and 13 you go to Advanced in TWRP and then Terminal Command. Just press select to start shell in the root directory "/ ".
once you are at the prompt you simply type in those commands:
cp /system/xbin/daemonsu /system/xbin/su
::THEN PRESS ENTER TO EXECUTE THE COPY COMMAND::
Then type:
/system/xbin/su --install
:RESS ENTER TO EXECUTE THE su COMMAND running the installation.::
Now reboot and you are done!
If you don't have TWRP installed there are other options to be able to run the command. Most custom recoveries either allow you to bring up a console window like that or they allow you to run commands on your device through your PC using ADB, either way it will work, you are just copying files with the first command and executing one of them to install on the second.
To answer your other question: YES you need to choose your ROM first, otherwise you have to do this all over again. Install your ROM first, root it next if your rom doesn't come pre-rooted, manually disable root, and lastly encrypt the device.

livejamie said:
This part never happens for me, it just gets stuck on the boot animation. I've disabled superuser. What else can I do? This is really frustrating.
Click to expand...
Click to collapse
Can you verify that you have in fact disabled root first? You cannot encrypt a rooted device. Also what is the model number of your device? What version of Android are you using?

Try this method after SuperSU is installed.
http://forum.xda-developers.com/showthread.php?p=56037508
Good luck
Sent from my Nexus 7 using Tapatalk

Hello,
I have sprint note 4.. I have installed HybridX Android 5.1.1 on it.. which have root and everything ready.
I go to system apps, from there disable SuperSu and then reboot in safe mode and start encryption.. These are the steps I read on another page..
However, my phone gets stuck on the sprint spark yellow screen as soon as I say ok to encrypt.. it will restart and gets stuck on there.
I have tried without restarting in safe mode.. but the same result.
What can I do to encrypt my Sprint Note 4.
Thanks

Hello,
I am on Galaxy Note 3 with N7 Darklord ROM and both methods don't work.
Root is disabled, but when I run encryption, the phone restarts in 2-3 minutes
and nothing is encrypted
Please advise how to encrypt the device! Thanks!

5.0.1 Should be fine to root + encrypt
Hi all,
Just to confirm that the only version I managed to root and encrypt is 5.0.1.
I have a Note 4 910F and this worked;
- Flash stock via odin
- Root (chainfire via odin)
- Install Busybox
- Install Terminal Emulator, then run su -> pkill -KILL daemonsu (same as other instructions on this forum)
- Encrypt the phone
Again, this only worked on 5.0.1 (N910FXXU1BOC5_N910FBTU1BOB2_N910FXXU1BOC4_HOME.tar)
All other versions got stuck on encryption screen.

In short, all you have to do is ENCRYPT the device FIRST then ROOT it AFTERWARDS. It will not work once the device is rooted. I have not had a chance to try unrooting through SuperSU or disabling the daemonsu through a terminal emulator as mentioned so I am not sure if this works but it definitely works if you encrypt PRIOR to rooting. I can confirm it works on Marshmallow as I just did so on a Note 4.

Now has anyone had any luck making backup images of their encrypted devices? If so what custom recovery software and version are you running on your device?

Editting Build.prop

I'm trying to add net.tethering.noprovisioning=true to my build.prop but can't do it. I am rooted and have an unlocked bootloader. Rootexplorer and ES File Explorer can't do it. So I copied the build.prop, made my change, went to Twrp, mounted system, pasted my build.prop and rebooted and the original build.prop was back.
I guess I need to have a script run after boot to mount system and echo >> the statement into the buildprop. Any suggestions how to run the script or get my build.prop to stick.

Try disabling system write protection.
http://forum.xda-developers.com/axo...to-persist-t3440276/post68206618#post68206618

xtermmin said:
Try disabling system write protection.
http://forum.xda-developers.com/axo...to-persist-t3440276/post68206618#post68206618
Click to expand...
Click to collapse
I did get it to stick finally but I did not accomplish what I wanted. I was looking to hide tethering from the carrier. It worked on Nexus6P. I can't get my ATT unlimited ipad sim to work my Axon7 but it works fine every other device I own except Windows Phone. Guess my Moto E will continue to be my hotspot.

Try using terminal emulator and type these two commands
Su
Settings put global tether_dun_required 0
Worked no problems for me on my axon (also made the build.prop edit of course)

[Sprint/others?] Hotspot now functions correctly with root

Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.

I used that code for my Nexus 5 on T-mobile without rooting. My Pixel is on back order and not able to test it on T-mobile. Is it necessary to root for only the phones on Sprint? Anyone test it on T-mobile (for native hotspot)?

Sorry, yes, I copied my post from a comment I made in another hotspot thread where the code was brought up and I tested it, but it didn't work for me without root. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access. Once you get your phone I would check out that workaround comment, and if you have problems try the root command.

Sprint Tether working now for me on adroid 7.1
I tried many things including the above..but none worked. I was able to root the system and what worked for me.
I followed these directions
Go here http://www.theandroidsoul.com/enabl...ing-pixel-and-pixel-xl-verizon-sprint-others/
Setup ADB and Fastboot on your PC (link).
Download the CarrierEntitlement.apk file and save it to a separate folder on your PC.
Connect your Pixel phone to the PC.
Open a command window inside the folder where you saved CarrierEntitlement.apk file in Step 2 above. To do that, “Shift + Right click” on any empty white space inside the folder and then select Open command window here from the context menu.
Once the command window is open, issue the following commands one-by-one disable provishning checks on your Pixel phone:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
└ You may get a prompt on your phone to grant root access, accept it.
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
Your phone will now reboot. Once that is done, go to Settings » More » Tethering & portable hotspot » and enable Portable WiFi hotspot. It should work.
I found this did work to enable the wifi hotspot app but this didnt let the computer connected browse the internet.
I then found this and now im able to browse on a computer connected to my hotspot
http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
I only used this part
Download/install a Terminal emulator app from Play Store (link →).
Make sure the terminal asked for rights when typing su because you have to grant it before it works correctly
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
Now my computer connected to the hotspot worked perfect and im very happy.
but i think if you follow this you can get it working right away without my above stuff.
Root your Android device running on Android 7.1 Nougat.
Edit build.prop file: Add the net.tethering.noprovisioning=true line to the bottom of build.prop file on your Android device. Use the link below for help with editing build.prop file.
How to edit build.prop on a rooted Android device
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (link →).
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device.
That’s it. You should have Tethering enabled on your Android 7.1 Nougat running device now.
I hope this helps as I haven't found this info in one area on here and sorry if it is but I didnt find it.

Is there a way to stop H91810p schedule update?

As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?

TempezT said:
As title says... Just found out about H91810p will make the phone unrootable which is something im planning later on. Sadly the update is scheduled for next restart.
Anything i can do to prevent that?
Click to expand...
Click to collapse
if you're rooted, go to /cache and rename update.zip to something else. then create a zero length file using the name update.zip. lastly set the permissions on that file to read only

Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (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.
*Install LG drivers
WIN:
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
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!

Damn I dont have a computer in hand. Guess i have to wait until im back home in October. Cross fingers this thing don't restart cause that freaking patch is already scheduled.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on:
Also if you are already flashed and rooted, jump to step #8 for the info regarding OTAs...
====================================================
Specifically for T-Mobile LG V20 H918
Firmware(s) 10I & 10J
====================================================
BOOTLOADER
SOURCES:
*** https://forum.xda-developers.com/v20/how-to/guide-unlock-bootloader-t3488878
*** https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594/page2
*** https://forum.xda-developers.com/showpost.php?p=69897433&postcount=1060
*** https://forum.xda-developers.com/pi...e-pixel-xl-t3466185/post69239012#post69239012
====================================================
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
*Turn on developer mode:
Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
*Turn on OEM unlock and USB debugging:
Settings -> Developer options -> OEM unlock & USB Debugging. (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.
*Install LG drivers
WIN:
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
You may need to get an additional .dll for adb to work, if so you can pull it from the pixel add compilation here:
https://xenserver.underpants-gnomes.biz/~romracer/fastboot_adb_pixel.zip
*In Terminal navigate to ADB root:
Type
Code:
adb devices
and authorize your computer on the phone
Type
Code:
adb reboot bootloader
Type
Code:
fastboot devices
and make sure your phone shows up
Type
Code:
fastboot oem unlock
Type
Code:
fastboot getvar all
Should say (bootloader) unlocked:yes
Type
Code:
fastboot reboot
====================================================
TWRP & ROOT:
SOURCES:
http://www.droidviews.com/install-twrp-root-t-mobile-lg-v20/
https://forum.xda-developers.com/v20/how-to/instruction-to-root-h918-10i-t3536472
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
https://build.nethunter.com/android-tools/dirtycow/arm64/
https://github.com/jcadduono/android_external_dirtycow#running
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
https://download.chainfire.eu/supersu
====================================================
*Prerequisites:
Your LG driver must be up to date. You can have problems with USB 3.1 if so grab latest drivers.
ADB installed, put all 4 recowvery files into the folder:
https://build.nethunter.com/android-tools/dirtycow/arm64/
Download the TWRP “twrp-3.0.2-1-h918” image:
https://build.nethunter.com/test-builds/twrp/lge/twrp-3.0.2-1-h918.img
Rename TWRP file to twrp.img and put it into internal storage (sdcard)
Download SuperSU:
https://download.chainfire.eu/supersu
Copy SuperSU onto external memory card (or keep in root of adb, and you could push it back, after formating).
You must be on a 100% stock ROM. Rooted or not.
USB Debugging & OEM unlock allowed in Developer Settings
Bootloader unlocked
Make sure all security/locks are off. No pins, fingerprint, etc…
Steps:
1. Plug your phone to your host computer. Make sure it's in MTP mode.
2. Open your command prompt:
Code:
cd\
cd (right click your mouse and paste the ADB platform-tools address, if using portable pack, where you put the adb folder)
Code:
adb devices
This will show your connected phone
3. Enter the following prompt: (you can simply highlight, copy, right click on command prompt and choose paste):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
cd /data/local/tmp
chmod 0777 *
./dirtycow /system/bin/applypatch recowvery-applypatch
* On ADB shell mode, you should see $ on the front. Wait for few…
Code:
./dirtycow /system/bin/app_process64 recowvery-app_process64
* Your phone screen may look weird. Wait for another few minutes. Once finished exit.
Code:
exit
4. Type:
Code:
adb logcat -s recowvery
You should see a lot of lines comes across your screen.
Once you see the ASCII box with the message about giving jcadduomo a hug you can press CTRL+C to exit logcat.
Reboot to the stock recovery:
Code:
adb shell reboot recovery
Restart a session:
Code:
adb shell
You will see a $ sign. Now to check…
Code:
getenforce
It should show Permissive. Thanks Dirty COW!!!
5. Temp Root. Lets patch the boot image:
Code:
cd /data/local/tmp
./dirtycow /system/bin/run-as recowvery-run-as
run-as exec ./recowvery-applypatch boot
Lets run as root
Code:
run-as su
You should have a #, indicating you have root. Ahh my little nix…
6. Flash TWRP
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
exit
reboot recovery
The phone should have flashed TWRP and rebooted into recovery.
7. TWRP:
In TWRP swipe to allow modifications. Or TWRP will be replaced next boot!
To disable any encryption perform the factory reset, and the Format Data options.
Install SuperSU from the external SD location.
If you didn’t do a full wipe and reset, you probably want to wipe cache and dalvik.
Reboot to system.
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Also in titanium backup (buy it already if you haven’t lol), freeze:
FOTA Update 7.0
Update Center 5.30.12
(I also disabled the com.lge.updatecenter.xxx overlay and themes, cuz whatever... lol)
Reboot and swipe away the notification if its still there. Should have stopped by this point.
======================
There ya go, good luck!
Click to expand...
Click to collapse
Okay someone in my base lend his laptop but its low end(sony viao core2 duo) dunno how well this work for flashing purposes, also I wanted to point before doing the process that my phone was unlocked permanently by tmobile unlock app and wanted to know if this can affect the unlocking or any other function of my v20.

Following those instructions to root will not gid rid of your carrier unlock.

You might be able to go to Settings>>Storage and delete Cached data.

Zacharee1 said:
You might be able to go to Settings>>Storage and delete Cached data.
Click to expand...
Click to collapse
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.

TempezT said:
Thank you! Now my other concern is that Im paying Jump! and root would void the warranty so I dont know if I should go ahead and do it regardless cause that silly update is already scheduled.
Click to expand...
Click to collapse
You can always restore to stock with the H918. Backup and root.

Zacharee1 said:
You can always restore to stock with the H918. Backup and root.
Click to expand...
Click to collapse
Thanks!
The issue Im having now is that I cant find how to root H91810k which is the current version my phone has besides the schedule update. Any info on that?

You have to find the KDZ for 10d and flash it with LGUP. Then you can use EasyRecowvery to root.
Flashing KDZs will wipe your data, so use LG Bridge to make a backup.

MDMAchine said:
Here since your on TMO, I compiled this for a buddy of mine through various sources (links provided) on the whole procedure start to finish. Might as well paste it for ya. Props to all original authors, etc...
I just did this on mine, same model, on firmware 10j. If your not on that or i step one will be to flash to the appropriate version. I didnt include that in my notes as myself and my buddy were both on 10j. But theres plenty of threads for that. if your on that, continue on.......
Click to expand...
Click to collapse
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!

wewantutopia said:
This is awesome! Thank you!!! You may want to make this its own post it's so helpful. Thanks again!!!!!!!!!
Click to expand...
Click to collapse
No problem! Glad it helped, I will probably update the post a bit, and then I'll re-post it to its own thread in a few days. As I noticed this section is a bit disorganized...

MDMAchine said:
8. Stop them OTA updates!!!
====================================================
https://forum.xda-developers.com/showpost.php?p=72463487&postcount=4237
https://forum.xda-developers.com/showpost.php?p=70795926&postcount=5
====================================================
Open up your dialer interface and type in 277634#*#
This will bring up a hidden menu and then select Wi-Fi test and then select OTA then select disable.
After that you will have to kill the hidden menu and you shouldn't be seeing the annoying OTA icon in your status bar anymore.
In file manager (root browser):
Rename otacerts.zip in /system/etc/security to otacerts.bak.
The full update is found in the cache partition called update.zip.
Move (or delete) the update.zip file from /cache directory (I put it on the sd card).
** dimm0k's method there seems to achieve a similar result, cant hurt to add the step of creating a zero length file after deleting/moving update.zip. I hadnt seen it, thus never did that but I havent had any OTA activity in a few days on mine.
Click to expand...
Click to collapse
just wanted to add that SOMETIMES the update.zip is not in /cache. had this happen to me when I had the LGV10 and it just happened to me now. I had recently wiped my device to start from scratch and after initially setting up my device I got the update icon and indeed /cache/update.zip existed. a few reboots later for various reasons the update icon/notification disappeared, as did /cache/update.zip. I thought I was in the clear until last night when I got the update icon/notification again, but this time it was not in /cache. it somehow changed to /data/data/com.google.android.gms/app_download. so if you can't find it in /cache, look there!

Sprint, Tmobile, Verizon (unlocked phone) Wi-Fi hotspot working method. Latest Pie

UPDATE: November 26.
It also works with Tmobile and Verizon (unlocked phone)
Running on latest Pie 9.0 and November update, and magisk beta 17. 3
Original.
you need to root the phone. Or else it does not work.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
@filthysanches did a detailed step by step for newbies down below.
Thanks.
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse

I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!

beezar said:
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
Click to expand...
Click to collapse
Do you have a tutorial link for this, I've followed at least 3 of them I've found online and I can't get Magisk modules to install. Says that /system can't be mounted.

eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
does this work the same way using android sdk?
Step 1: open command window
Step 2: type "cd (folder location of the platform-tools sdk)"
step 3: type "settings put global tether_dun_required 0"
step 4 :type "reboot"
I'm going to try this when I get home, just wanted to confirm if this method makes sense.

Step 2.5 type adb devices. If you see your device then step 2.6. type adb shell

Boom! Works now. Thanks ya'll.

I did everything with adb... I think modules with magisk are tricky sometimes

Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)

uofirob said:
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
Click to expand...
Click to collapse
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!

cedargreen said:
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
Click to expand...
Click to collapse
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?

uofirob said:
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
Click to expand...
Click to collapse
Had that too on wife's phone that was rma'd due to constant boot loops. Only thing I have done differently is to delete the net.tethering.noprovisioning=true as well as going into magisk and uninstalling back to normal boot img, prior to taking the Nov OTA. Once that was done I went into twrp and reflashed the magisk zip then redid the build.prop.
My noob understanding of that popup is that something in system has been modified (build.prop?) Causing the notification.
I rma'd before I was able to read about it so couldn't test to see if I could complete uninstall then back to factory then update everything and finally magisk, edit build.prop.

eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction

I know this is mentioned for Sprint but on stock 025, Nov sec, rooted with Magisk, the above did not work on MetroPCS

access unravel
As a side note, installing a root access "app hider" will reverse the second part of this process breaking connectivity. Not a huge deal but worth noting, as I'm not sure what root access apps will also reverse this.

Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?

filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
Worked perfect. Thank you.

I am looking for non root solution but so far I can't find it
Got it work
https://forum.xda-developers.com/pixel-2-xl/how-to/root-sprint-hotspot-t3738118

Thank you for breaking this down and explaining it. I performed the first part with the buildprop editor using ES File Explorer with root permissions. It still didn't work so I had to wait till I was done with work to perform the second process with ADB and all is working now so happy. I just got my pixel 2XL and wasn't sure if this would work or not.
Thank you so much too whoever solved this.

rockingondrums said:
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
Click to expand...
Click to collapse
did anyone ever confirm this?

Can anyone confirm if this works on pie? Carrier has my tethering disabled.