Related
Let's cut the crap. Seems like somebody on a Chinese forum figured out the way to apply the mod to MM2. I just translate it into English.
1. Download the attachment and unzip milestone2_more.ko to the root of sd
2. mount /system/ r/w
3. copy milestone2_more.ko to /system/lib/modules/
4. open terminal emulator
5. input the following command
su
chmod 644 /system/lib/modules/milestone2_more.ko
insmod /system/lib/modules/milestone2_more.ko touch_num=6
(the guy said if you choose a number greater than 6 the system will crash)
now you should get a 6-point-multitouch
original thread: http://bbs.gfan.com/android-1997547-1-1.html
Thank you soooooooo much! )))
Works but MT is still buggy...
oh my god.. thank you, it works.
5 is more than enough
OMG!! You made my day!
Sent from my A953 using XDA Premium App
Is this permanent? Or it'll go away when we reboot?
Sent from my A953 using XDA App
It will go away when you reboot, but its not a big deal to use the command again
Sent from my A953 using XDA Premium App
Just make a init.d script to load it up when the system boots and you won't have to worry about it again..
Just did this, but I think i wrote it wrong. Please correct me
I created a blank file and wrote inside it:
insmod /system/lib/modules/multitouchfix.ko (I replaced the name)
And saved the file as 99multitouchfix inside /system/etc/init.d/
I also fixed permissions for both files
Sent from my A953
Is it working Aragorn?
Thank you. I'll try it when I get home!
inheme said:
Is it working Aragorn?
Click to expand...
Click to collapse
Nope. The module works, but not the init.d script
you can use autostart from Market
AragornPE said:
Nope. The module works, but not the init.d script
Click to expand...
Click to collapse
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
dangpzanco said:
Try this script:
Code:
#!/system/bin/sh
# Load 5 finger multitouch module
insmod /system/lib/modules/defy_more.ko
Also note that the first touch after reboot is delayed.
Click to expand...
Click to collapse
I'll try that as soon as my M2 wakes up, long day for it today =P
Actually,the patch is developed by korean , the XDA thread is http://forum.xda-developers.com/showthread.php?t=1162327
Autoload after reboot: copy install-recovery.sh to /system/etc and set rwxr-xr-x .
If you wanna change the touch point limit , open install-recovery.sh with text editor , change the number that follows "touch_num=". The range is 1~10.
My own test shows more than 6 touch points will NOT lead to system crash , but make it back to 2 points...orz. Since the same patch on D2/D2G/DEFY enable up to 10 points, why
m2 cound not
Ah, forgot to say , the autoload patch is ported from http://bbs.gfan.com/android-1997547-1-1.html
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Install recovery didn't work either
Maybe I'm doing something wrong?
Sent from my A953
AragornPE said:
Neither autostart or init.d script worked. Going to try the install recovery
Sent from my A953
Click to expand...
Click to collapse
Did you set the permission properly，both milestone2_more.ko and install.sh.
All works fine, both the milestone2_more.ko and the install recovery, no problem at all, have 4 MT points now
For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!
I installed adw launcher ex on my s7 tablet and now my touch screen wont work. I've tried to connect it to my PC to root but my PC isn't seeing the device. I don't think its set on debugging mode. Is there anyway to fix this or is it hopeless.
Edit: nevermind I returned it to best buy.
Sent from my Desire HD using xda premium
I've root with gingerbreak and I've root explorer. I'll just edit bluetooth_power.sh with root explorer editing tools and add those code, right?
Sent from my IDEOS S7 Slim using XDA App
shishko said:
For all of you having problem with unresponsive touchscreen after installing alternative launcher on your S7 Slim...
I found out that during boot touchscreen is disabled and official Huawei Launcher enables it, so if you install alternative launcher, touchscreen remains disabled after reboot.
First of all, you have to root you S7 Slim (I've done it using following article http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, just set ro.secure=0 in default.prop and add --base 0x20000000 to mkbootimg command-line). Then, copy file /system/etc/bluetooth_power.sh to your hard disk (adb pull /system/etc/bluetooth_power.sh c:\). Edit that file (c:\bluetooth_power.sh) using Notepad++ and add following lines:
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Then, remount /system partiton read-write (adb remount), and copy that file back (adb push c:\bluetooth_power.sh /system/etc/).
Reboot, and now you can install any launcher you like!
Click to expand...
Click to collapse
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk
Here is the evidence, custom launcher GO Launcher EX works on my HIS7 Slim (CDMA)
#!/system/bin/sh
#
# added by h00131430
#
echo 0 > /sys/class/rfkill/rfkill0/state
echo 1 > /sys/cap_touchscreen/boot_complete
echo 1 > /sys/cap_touchscreen/state
Download file
http://www.multiupload.com/MKBGQUC10X
Worked for me.
glpro said:
Download file
http://www.multiupload.com/MKBGQUC10X
Click to expand...
Click to collapse
Link is dead, could you post another, please?
wheeqo said:
Wow thanks shisko, it works!
My steps a bit different:
1. Root with gingerbreak.
2. Edit bluetooth_power.sh with root explorer.
3. Add those code. Save and exit.
4. Reboot.
5. Add custom launcher.
Sent from my IDEOS S7 Slim using Tapatalk
Click to expand...
Click to collapse
Confirmed, working. I installed Zeam straight to portrait view, and no orientation bug anymore. Cheers!
huawei slim
who can make a better huawei s7 slim rom?
beenhow said:
who can make a better huawei s7 slim rom?
Click to expand...
Click to collapse
1. Tri-zet (Tried and works great) androidtablets.net
2. Zmey Mod (Still running) on ndroidtablets.net
3. Pirate 2.0 by Satec in this forum (Not sure this will run on my s7 105 and too lazy to flash this at the moment cos the ROM i using now is stable enough)
Tri Zet works great!
darkic said:
Tri Zet works great!
Click to expand...
Click to collapse
CM9 , CM10 , paranoid works great , too
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
It's not a matter of being s-on or s-off.. It's a matter of having write protection removed then you can do all of that. S-off just allows you to flash any partition on the device.. (radio, hboot etc..) plus you can flash any ruu you want as long as you change to supercid
There is a kernel module in dev and it's working great on my device.
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
migascalp said:
On M7 it seems to me that the S-OFF also disables write protection system on stock rom
Envoyé de mon HTC Butterfly s en utilisant Tapatalk
Click to expand...
Click to collapse
But you don't need s-off to disable write protection. You just need a kernel with it disabled or the kernel module which flair posted in the development section. I'm using it and am able to write to the system fine and I'm s-on. The title of the thread should be something like "with write protection on" not s-on.
I just wanted to clarify that with S-OFF this module is useless
migascalp said:
I just wanted to clarify that with S-OFF this module is useless
Click to expand...
Click to collapse
You don't need to clarify that to me. I'm very well aware of that. My point was that for this topic you don't need s-off for this to work.. You just need write protection off. Whether that be with with s-off or with a module.. This working is not dependant on s-off.. It's dependant on write protection being off. That is my point.
Sent from my HTC One using Tapatalk
For anyone who wants the stock kernel with write protection off just use this JMZM8 Kernel and then just install busybox like regular and boom Viper4Android, literally made my M8 sound so much better (not that it wasn't already awesome)
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
helloicanseeu said:
worked with htc 816 running indian stock, which still has no s-off at the moment,
had to go to twrp recovery terminal command, to make the symbolic links or move directories....
viper4android made a lot of difference in this particular model.
the next thing would be to make viper4a a system app, since it tended to close and thus lower the volume, usually after some time.
Click to expand...
Click to collapse
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
will try to make it work .... meanwhile from what i gathered in a htc 816 facebook group, most indian pple buying this particular model seems to have no clue about making the most out of its audio properties ... the 816's true selling points were its larger 5.5 " size, great audio output, and relatively low cost compared with other htc flagship models.
One-M8-Master said:
you can try and copy the app or push it in recovery to System/app. if you put it manually in not push via adb be sure to set the right permissions if the recovery doesn't set them automatically ! it should work even without s-off
Click to expand...
Click to collapse
done ... went to twrp recovery,
moved "com.vipercn.viper4android_v2-1.apk" from ""/data/app" to "/system/priv-app"
moved "com.vipercn.viper4anddroid_v2-1/libV4AJniUtils.so" from to "/data/app-lib" to "/system/lib/"
should be working fine, havent extensively tested it out yet though,
reported as a system app, and viper driver is running.
I Can't Get data/soundfx Shortcut to Transfer to /System/lib
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
BaltColts said:
In the opening instructions, #11 says that we have to transfer the data/soundfx shortcut to /system/lib. Everytime I try it with TWRP it just says failed. If I try it with root browser,
it will say successful until the phone is rebooted. Any help would be appreciated. I am a newbie to these things.
Click to expand...
Click to collapse
u need to install twrp recovery for htc 816.
get it from "TeamWin Projects" website.
after successfully installing twrp, boot into recovery mode, use twrp to move data/soundfx shortcut to /system/lib, etc...
hope u get to install viperfx successfully and make full blast of the great audio output of this big value music machine, makes a near perfect combo with my music angel cube speakers(as far as mine human ears tell me), anyone using this combo too?
later htc models based on mediatek chipsets seem to have horrible audio outputs ... maybe even iphone 6 and samsung note4 cant beat htc 816 where mp3 output is concerned
background: htc 816 doesnt has s-off, so its always s-on, which means if u try to write to the "/system" folder, the phone will trigger a reboot immediately, to prevent any modifications to the folder. root browser will not be able to write to /system folder, even if the phone has root access, due to this s-on protection. The only way to edit /system folder is to boot to twrp (in recovery mode).
blewis540 said:
I have successfully created my own bypass to get viper4android to work. Always create a full backup before attempting =)
1. Download viper4android APK
2. Download Root Explorer from the playstore
3. Install Both Apps
4. Launch Root Explorer
5. In root explorer go to /system/lib/soundfx and copy the folder to /data/ (make a soundfx folder)
6. Also copy /system/etc/audio_effects.conf to the /data/soundfx/ folder
7. Using root explorers menu you can create a shortcut (symbolic link) make a shortcut of the /data/soundfx/ folder and a shortcut of the /data/soundfx/audio_effects.conf
8. Boot into TWRP
9.Mount the system partition
10. Rename /system/lib/soundfx to /system/lib/soundfx2
11. Copy soundfx shortcut create earlier to /system/lib/ it will look like a "file" to TWRP
12.Rename the /system/etc/audio_effects.conf to /system/etc/audio_effects.conf1
13. Copy the audio_effects shortcut into /system/etc/ (be sure its name matches the old exactly)
15. Reboot
16. Launch Viper and install driver
I haven't dealt with LPA yet (hasn't had an issue) nor have I done any other modifications at this time which are avail on the viper4android thread.
I was just thinking about symbolic links to get around this S-OFF/ON issue and it appears they work and technically as a workaround we could symbolically link everything in system to another location and access it all. This could easily be put into ROM builds now at least as well!
Build.Prop may be useful to move out via sym link as well
Click to expand...
Click to collapse
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
fade2black101 said:
Will this method work without busybox?
There is a very specific reason why I'd not like to use busybox, so this may end up being a very good solution for me.
Click to expand...
Click to collapse
What's wrong with busybox? its a hidden process only used when an app like V4A calls for it, other then that it has no negative effect. why avoid it?
Besides this thread is disinfo, all this is not required to get V4A working, Go to this thread Here and follow instructions.
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
oulixeus said:
hi,
I have completed those steps, but the viper4android keeps asking me to install the driver.
I have tried also the steps from helloicanseeu. But still, not working.
please help me, because installing viper4android is never been this hard on my previous device. thank you.
Click to expand...
Click to collapse
Which phone u using? What stock rom? I was using stock indian on htc816.
---------- Post added at 09:12 PM ---------- Previous post was at 09:03 PM ----------
XskipperX said:
i got stuck after flashing viper . stuck on htc logo then reboots back to recovery..
Click to expand...
Click to collapse
U followed the steps by blewis?
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
uvt_novice said:
Why it is so complicated..???.if s-on, unlock bootloader and flash a custom kernel (elementalx). In install options just choose to set SElinux permissive. Then, install driver for Viper and reboot. That is it. If s-off, start with kernel installation...
People are talking about that s-off gives full access to system partition - true but not correct. Unlocked bootloader gives write access to system folder, while s-off in addition allows to change partitions, bootloader, etc.
Sent from my HTC One M8 using XDA Free mobile app
Click to expand...
Click to collapse
Welp, it's so complicated because NONE of the instructions seem to work for a huge number of us. I've tried like 5 "failsafe" methods but they just fail and fail.
ONE time I had it working and was all psyched, and then I restarted the phone at some point and that was the end of that. Never worked since.
Hello everyone!
Making another guide, this time on how to fix RIL on CM12 based roms e.g. Vanir and FXP.
The cause of the problem is once again SELinux and the fix is rather simple... let's go!
Before we start there is one crucial requirement! :
Do you have a SIM PIN set? If YES just continue reading. If NO, please set one BEFORE flashing a CM12 ROM.
We need to be able to set SELinux to permissive before the phone attempts to access the SIM card or it will not work! If you have a PIN set, your phone will not "try" to load it till you entered the PIN and that gives SELinux mode changer the time to change the mode! If you have no PIN set the phone will load the SIM card almost immediately and the app is not quick enough to set the mode to permissive before it loads the SIM! Users with no SIM PIN can try "method 2"
Steps:
METHOD1:
1: Install a build of your choice (Vanir/FXP, and no this fix is not for locked bootloader CM12 roms like RR, there is another fix for those roms!).
2: Once your device has booted up, turn off auto brightness to prevent your phone from rebooting while doing these steps. (your phone will soft-reboot once after disabling auto brightness)
3: Download and install SELinux mode changer from here: Google Play (or any other app that is able to set SELinux to permissive on boot.)
4: Open the app grant root access and check the "show notification" Checkbox.
5: Fully reboot your device and WAIT on the lockscreen till the app says that it changed the SELinux mode to permissive!!!
6: Enter your SIM PIN and you should be ready to go!
METHOD2:
1: Create a new script file in /system/su.d.
2: Put this inside of the file:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
3: Set correct permissions.
4: Reboot
(this method was not comfirmed by me! And it might not work, can someone try it?)
Remaining bugs:
1: When you call someone or you get called, the sound will be glitchy!
2: Auto-brightness still does not work!
3: More?
The fix was found by : @AndreAkaNick
Method2 found by @jojos10
Enjoy CM12!,
Noahvt
credits to @AndreAkaNick
Gara91 said:
credits to @AndreAkaNick
Click to expand...
Click to collapse
I almost forgot, thank you
@noahvt
The call gets really bad? You can hear the person on the other side?
lvints said:
@noahvt
The call gets really bad? You can hear the person on the other side?
Click to expand...
Click to collapse
Let me try that for a sec. I'll report when I get back AKA when my phone boots up to FXP 24/02
what if I run su setenforce 0 in terminal and reboot? Do I still need to set SIM PIN then?
vvaklnprm said:
what if I run su setenforce 0 in terminal and reboot? Do I still need to set SIM PIN then?
Click to expand...
Click to collapse
I tried that and it doesn't work...
After reboot selinux returns to enforcing...
How to make permissive selinux with init.d script?
I'm too lazy to download selinux mode changer
Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.
jojos10 said:
Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.
Click to expand...
Click to collapse
could you please make a flashable zip?
also how to get rid of cyanogen recovery? cant install anything
2 not working....but wait...what name this file should have?RIL?RIL fix?
The second fix will not work if Google Now is activated.
I get an error that Google (Now) has a network error while my data and radio works.
dimitrakhs1 said:
2 not working....but wait...what name this file should have?RIL?RIL fix?
Click to expand...
Click to collapse
2 only works if you have flashed chainfire's supersu zip and you can choose any name you like for the .sh file
Sent from my Nexus 7 using XDA Free mobile app
Yeah,but it don't need it in this version,it's pre-rooted already(Resurrection v5.3.6).You suggest flashing this anyway?
dimitrakhs1 said:
Yeah,but it don't need it in this version,it's pre-rooted already(Resurrection v5.3.6).You suggest flashing this anyway?
Click to expand...
Click to collapse
You can flash it if you want. I didn't flash it and now I'm using SELinux Mode Changer.
I have tried the 1st method
It works also on RR 5.3.6 #1 build by Furrydaus
jojos10 said:
Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.
Click to expand...
Click to collapse
I kept trying with FXP CM12 9th Feb , did all the above but RIL still not working.
edit - copied accidentally with a space behind the sh on the first line, hence wasn;t working. Everything works!
does not able to set 3g .. on latest vanir
hey im using latest vanir ... 5.0.2 022715 .. and tried the first method .. set a sim pin .. and it works but when i turn on data ... and set to 3g .. it reboot(screen fade out slowly ) and now when it reboot and again asked for the pin .. and i entered my pin then again it reboots
-EDIT-
it works, accidentally had a space behind the first line of the script hence it didn't work.
Guys my apologies.
Tested again. Turns out the script is not activating no matter what was done - permission set correctly (RWX RX RX chmod755), SuperSU flashed and set on boot, script inside /system/su.d folder. SELinux status keeps being on enforcing.
where can I find the system / su.d
Sent from my Xperia SP using XDA Free mobile app
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!