Related
Google made a change from Android 4.1.2 which allows operators to know when users are using tethering and conveniently block tethered devices from accessing internet.
This can be fixed permanently using the following procedure and no root required on all rom types (stock, mod):
1) Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
2) Enable USB debugging under Settings -> Developer options
3) Connect the device with a USB cable to a computer with the Android SDK platform tools installed
4) Start an adb shell: adb shell
5) In the adb shell, run this command:
Code:
settings put global tether_dun_required 0
Tested on Nexus 5 & 6 with Marshmallow STOCK ROM
Just tried this on a freshly imaged Verizon Nexus 6 with Marshmallow, and I'm still getting the prompt for subscribing to tethering.
Can you do this with sqlite editor? If so, how?
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk
trent999 said:
Can this be tried even if the Nexus6 boot loader is locked, without unlocking it ?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
I'm on Verizon and that's what I did also.
Sent from my Nexus 6 using Tapatalk
nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You don't need root to do it, you can make the change via recovery and adb shell commands.
wishkah said:
Can you do this with sqlite editor? If so, how?
Click to expand...
Click to collapse
I'm not sure this can be done with sqlite editor anymore because when I go to the file path data>data>com.android.providers.settings>databases there is no longer a settings.db in that location to edit.
Maybe I'm missing something.... IDK???
didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
Click to expand...
Click to collapse
editing the build.prop worked for me! thanks guys/gals
nexus6r3plicant01 said:
You need root to edit the build prop like this but you can also edit the build prop thru adb commands
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is Rooot needed to do this through adb?
That is my question, too.
For right now, I want to wait to unlock and root. I have reasons...
Can I edit and replace build.prop somehow under those conditions ?
I have ADB and fastboot both working and have pulled a copy of the stock Lollipop build.prop onto my laptop. I can edit it, but can I push the revised copy back with the boot loader still locked and no root ?
I read somewhere about achieving temporary root via fastboot booting twrp, instead of flashing, but that fails for me and I cannot find the referencing thread.
Sent from my VS985 4G using Tapatalk
Same boat here. I'd love to enable this, but don't want to do too much as I'm switching to a 6P in two weeks.
Do you need root to mod this? i'm not able to R/W system without it I assume?
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Yes, the above is what I have been looking at, but it is important to realize it requires an unlocked bootloader, which requires a total phone wipe.
Plus I am concerned that this will prevent any future OTA, like to Marshmallow for mine, and also make it impossible to use Android Pay on that device, if those issues matter to you.
Yes, I know it is self-limiting to have a stock, locked N6.
Sent from my Nexus 6 using Tapatalk
pmhesse said:
Note that this does make the scary This device is corrupt... message appear at bootup.
Click to expand...
Click to collapse
Also note that this will also make you unable to apply any future OTAs (neither pushed to you by Google, nor sideloaded via ADB).
18 months ago, before /system validation became a thing, I would have recommended this method to a lot of "casual" modders - booting to TWRP to fix a couple things, and then going on their merry way with an unrooted "stock" (or close enough to it as to not matter) device.
Now that /system validation is a thing (breaks OTA applicability, dm-verity), I wonder if it's actually more advisable that people keep TWRP installed, and take the time to fully educate themselves about what they're doing, so that in the future they can fix things themselves more easily (and manually apply the monthly security patches, etc.).
I'm honestly not sure about the right answer - what do folks think?
pmhesse said:
So, this link provides information on how to make the modifications to the build.prop without root which is what I needed to make things happen on Verizon. Note that this does make the scary This device is corrupt... message appear at bootup. Specific steps I followed (assuming you've got adb working and USB debugging enabled):
- Download TWRP 2.8.7.1 from here
- adb reboot bootloader
- fastboot boot twrp-2.8.7.1-shamu.img
- When TWRP finishes booting, click Mount and check the box for /system
- adb pull /system/build.prop
- Use your favorite text editor to add the line net.tethering.noprovisioning=true to the build.prop file you just downloaded off the phone. Save the file.
- adb push build.prop /system/
- adb shell chmod 644 /system/build.prop
- adb shell settings put global tether_dun_required 0
- adb reboot
And voila. When you reboot you'll be able to tether. At least I was.
Click to expand...
Click to collapse
Ah. I don't have TWRP installed. Thats what I was missing. I went full stock besides my unlocked bootloader with Marshmallow. Not being able to Android Pay also sucks as I do use that. Wonder if I set it up first, then do this if it will let me still use the cards I load.
Durthquake said:
didn't work on my stock Nexus 6 - still says to contact ATT.
---------- Post added at 10:41 AM ---------- Previous post was at 10:32 AM ----------
editing the build.prop worked for me! thanks guys/gals
Click to expand...
Click to collapse
So the command did not work but adding the net..etc to build prop worked anyone in T-Mobile done this yet? Thanks
Correct, the command didn't work, but the line at end of build.prop did. Should work for any carrier.
Ocelot13 said:
net.tethering.noprovisioning=true
Pasted at end of build prop. Save. Reboot. Done.
Click to expand...
Click to collapse
Thank you!
After updating my HTC desire 820 dual sim to marshmallow . I found out that marshamallw has a hidden feature of multiwindow that can be accesses by changing a line in build.prop but everytime I edit the build prop and reboot my phone the values in build prop again switches to default values.. here is what i did-
1. Install root browser and mount system with read and write permissions.
2. Open /system/build.prop and search for ro.build.type
3. Change the value from user to userdebug.
4. Reboot the system
!!!! After reboot the value again switches to user
I have tried all methods .. by adb by build prop editor apk... But no successs .. i cant see multiwindow option in developer option ...
PLEASE LOOK FOR SOLUTION ASAP...
You must have root,and s-off, I have do and have this feature now after reboot.
Sent from my HTC_D820u using Tapatalk
misisipiman said:
You must have root,and s-off, I have do and have this feature now after reboot.
Sent from my HTC_D820u using Tapatalk
Click to expand...
Click to collapse
i have already rooted the phone but how can i obtain s-off?
Nipun Gupta said:
i have already rooted the phone but how can i obtain s-off?
Click to expand...
Click to collapse
With xtc2clip or s-shine
Hmm... I think that if I edit build.prop, change ro.build.type and restart only Android framework it could be work.
---------EDIT:
^^ this wouldn't work. Only solution that I see is, reboot to TWRP, mount system partition, connect to pc, adb shell and modify /system/build.prop.
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Nikish21 said:
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Best of luck. :good:
Would it work with los stock kernel?
impulsar said:
Would it work with los stock kernel?
Click to expand...
Click to collapse
No idea. I am using vegito kernel v7
riazul.islam20 said:
No idea. I am using vegito kernel v7
Click to expand...
Click to collapse
Vegito kernel by default supports dt2w right?
impulsar said:
Vegito kernel by default supports dt2w right?
Click to expand...
Click to collapse
Might be. But by default it was inactivated.
Is it possible to add screen of gestures in lenovo vibe k5
Is it possible to lock device by double taping...Just like dt2wake??
jometzz said:
Is it possible to lock device by double taping...Just like dt2wake??
Click to expand...
Click to collapse
Why not?
Just double tap on statue bar
riazul.islam20 said:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Click to expand...
Click to collapse
It gets reset to 0 on reboot. Why?
afzalsayed96 said:
It gets reset to 0 on reboot. Why?
Click to expand...
Click to collapse
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
#!/system/bin/sh
echo 2 > /sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
Android_touch
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Goutham47 said:
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Click to expand...
Click to collapse
the same here, please help
Please someone who says the correct way to do the procedure in Rom AOSP or LineageOS in 7.1.2
Someone using dt2w on oreo? Please share info if there's a way to activate it under oreo
nonline said:
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
Click to expand...
Click to collapse
bro...i m getting endless boot animation...what to do...??? plzz help
Hello !
October update is available.
Lets talk about it?
Confirmed, October patch rolling! Downloading!
prannoytambe said:
Confirmed, October patch rolling! Downloading!
Click to expand...
Click to collapse
That was news yesterday?
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
jcunltd said:
Someone could corroborate this news .. according to the aptx function has been included "Streaming: Qualcomm aptX audio"
Souce: http://en.miui.com/thread-4235944-1-1.html
Click to expand...
Click to collapse
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Letitflow said:
I can confirm this:
aptx and aptX HD are now working with my MI A2 and Sony WH-1000XM2
Click to expand...
Click to collapse
anyone knows why the update size is so much smaller than the beta testers got? thanks
installations fails on my phone.
Voniaak said:
Hello !
October update is available.
Lets talk about it?
Click to expand...
Click to collapse
I noticed, when scrolling, I rarely get accidental taps. I used to get them a lot with September update.
bavmouse said:
installations fails on my phone.
Click to expand...
Click to collapse
Did you restore stock boot image and not modify the system partition?
Benjamin_L said:
Did you restore stock boot image and not modify the system partition?
Click to expand...
Click to collapse
that's possible. how can i modify ? thanks.
bavmouse said:
that's possible. how can i modify ? thanks.
Click to expand...
Click to collapse
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
i bricked my device and restored it with fastboot flash.
CPU frequency stuck at 100% bug still exist. Work fine for 10 mins after reboot, after that stuck at 100% again.
yes. I can confirm, that after using FP sensor, CPU stuck at 100% load. :/
Why do we need to repeat this in this thread. Everything has already been mentioned before in other threads.. Doesn't help when someone is looking for information
Benjamin_L said:
First I need to know what you did? did you flash the patched boot image? Other apps that modify system like adblock? Did you modify build.prop?
Click to expand...
Click to collapse
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Before trying this, I suggest you to backup your files.
Verify the system version in Settings > System > About the device > Version number and download the same version installed in your device:
V9.6.10.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.13.0.ODIMIFE
V9.6.14.0.ODIMIFE
V9.6.15.0.ODIMIFE
Unzip the package (7zip works perfectly to this job) and copy the files boot.img and system.img
1) Copy system.img and boot.img into adb folder
2) go to "settings > system > developer ... > USB deployment and enable it
3) plug you device on your computer, turn it off and turn it on again while holding power + volume down until your screen shows the Xiaomi bunny and "Fastboot".
4) in Fastboot, type "fastboot devices" and make sure your device is listed.
5) in Fastboot, type "fastboot flash system system.img" (without quotes) and wait it finishes.
6) in Fastboot, type "fastboot flash boot_b boot.img" (without quotes) and wait it finishes.
7) in Fastboot, type "fastboot flash boot_a boot.img" (without quotes) and wait it finishes.
8) in Fastboot, type "fastboot reboot" and unplug your device.
This works for me, maybe works for you.
ccbz said:
Installation also fails in my phone
The things I reverted are:
Changes made by adblock
Magisk mods: emojiOne and Mi A2 Camera app (I thought it was an enhanced version)
I flashed the original boot.img
But after these steps the installation doesn't work.
Other root apps I use:
Greenify, but not for system apps
Uptodown, but it has root privileges denied always
SD Maid. I think I didn't delete anything but maybe I compacted some databases
Any ideas? Is there any way to get more detailed info about the installation error?
Thanks!
Click to expand...
Click to collapse
Mounting system makes otas impossible already so follow the instructions before my post
New update today...
After yesterday an update was delivered, I am now offered a new update. The installation is now running. I noticed after yesterday's update that there were significant "memory / processing delays", which had previously not occurred on my device. The update is 203 mb, yesterday only 103.5mb were delivered.
OP status for the first time
I just found out you can snooze it just before typing this sentence lol. But is there a way to disable the notification permanently without root?
I don't expect it to survive a reboot but if there is a way I would imagine it being achieved via ADB?
Not a big deal anymore since I just found out you can snooze it for 2 hours but hey might as well finish what I started. If you were wondering my concern is burn in but I think the icons on the status bar move? I would rest better knowing it's not there anyway.
Thanks, I appreciate it.
EDIT: Nevermind I think I did it.
System/System app settings
Then disable "Show update notifications"
EDIT 2: It did not work:laugh:
- With root I used this solution:
Edit the file: system/build.prop
copy / paste the line that contains the version number.
Example: ro.build.version.incremental=V14.3.11.0.PFJMIXM
I have put a "#" for memo and changed v10 to v14 :
Code:
# ro.build.version.incremental=V10.3.11.0.PFJMIXM
ro.build.version.incremental=V14.3.11.0.PFJMIXM
- Without root It may also be possible (to check) to modify this file with XiaomiADBFastbootTools (with the small embedded file manager).
Do I need an unlocked bootloader or root access to use XiaomiADBFastbootTools?
The Flasher, Wiper and Camera2 modules require an unlocked bootloader but everything else works without rooting or unlocking.
Click to expand...
Click to collapse