Related
Description:
Android KitKat Blocks Some Access to Micro SD Cards
Important note:
Root is mandatory and this guide works for all 4.4+ android devices.
In other words, if you have problems with this guide, then do a check, and check again.
Or you doing something wrong, or yours device stil dont have real root status.
Once again, root status is ability to EDIT and SAVE changes to system files.
If you cant do BOTH things, then you doing SOMETHING WRONG or you dont have real ROOT status, or both of them.
Backup your stock platform.xml before modifications, just in case.
Two solutions, manual solution and one click/app solution, both solution doing same thing.
1.
1. Launch your favorite file manager with enabled root access rights.
You can use any app you prefer which can run elevated on your device.
For example, the 'Root Explorer' app or 'Total Commander' or 'File Manager' from CyanogenMod will do.
2. Navigate to the following file:
/system/etc/permissions/platform.xml
3. Find android.permission.WRITE_EXTERNAL_STORAGE and android.permission.WRITE_MEDIA_STORAGE lines. These are XML sections. You need to make them look exactly like the strings below:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Save the platform.xml file. It’s necessary to set the file permissions to 644 (rw-/r–/r–) before mobile restarting. Now reboot your Android device.
Click to expand...
Click to collapse
2.
App written by @tliebeck
[APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD
I take it there is no way to do that without root?!
I did that without root.
I used root explorer and text editor
@puck1e
could you tell me exactly how you did that? I am so desperate that I am thinking about switching to another phone
No, he didn't do that.
That is impossible.
Without root you cant remount system as r/w and edit system files.
Read this thread, maybe there is a way.
http://forum.xda-developers.com/showthread.php?t=1725222
you're right. it didn't save the file. sorry.
poolmaker said:
No, he didn't do that.
That is impossible.
Without root you cant remount system as r/w and edit system files.
Read this thread, maybe there is a way.
http://forum.xda-developers.com/showthread.php?t=1725222
Click to expand...
Click to collapse
oh man, too good to be true
I tried it as well but it does not save any changes to the file
so I guess there is no other possibility than to unlock the bootloader and then root the device - and lose the warranty
slead1 said:
oh man, too good to be true
I tried it as well but it does not save any changes to the file
so I guess there is no other possibility than to unlock the bootloader and then root the device - and lose the warranty
Click to expand...
Click to collapse
What if I told you there is a way to root your device without unlocking the bootloader?
You can find all the details in this thread:
http://forum.xda-developers.com/showthread.php?t=2634196
Yes, but we are talking about 4.4.2 firmware.
like poolmaker already said, its 4.4.2
so it would appear that we all have to wait and see if someone comes up with an idea or the app developers adjust their apps
still, thanks for the link, I will have a look at it. for all I know it might just work with 4.4.2 also
slead1 said:
like poolmaker already said, its 4.4.2
so it would appear that we all have to wait and see if someone comes up with an idea or the app developers adjust their apps
still, thanks for the link, I will have a look at it. for all I know it might just work with 4.4.2 also
Click to expand...
Click to collapse
Ok, I have forgotten that there is no method for kit kat yet:silly:. You can always root on 4.3, backup your TA and only then unlock bootloader ( It is how I have done it). If something goes wrong I hope I will be able to restore my TA partition and lock bootloader again. Or you can wait a bit. I am sure soon someone will figure out how to root it.
I swear I read somewhere on xda that someone rooted 4.4 with 'doomlord'-method, but I can't find it anymore.. Darn!
Sent from my D5503 using xda app-developers app
Mono_pol said:
I am sure soon someone will figure out how to root it.
Click to expand...
Click to collapse
If your bootloader is unlocked it's simple, hotboot a kernel with CWM, flash the root.zip, done.
Sure, but that is (seems to me) last option to him.
If i understand situation well, @Mono_pol want to wait working exploit in 4.4.2 firmware (root without unlocking bootloader).
I have already unlocked my bootloader. Long time ago to be honest. Now I am running rooted KitKat without any issues so far. My comments were directed at @slead1 just to give him some idea if he does not want to wait for a working exploit on android 4.4.
4.4.2 looks so different form the other 4.x.
sander151187 said:
I swear I read somewhere on xda that someone rooted 4.4 with 'doomlord'-method, but I can't find it anymore.. Darn!
Sent from my D5503 using xda app-developers app
Click to expand...
Click to collapse
if u have unlocked bootloader you can flash this kernel with fasat boot comand.This one is with recovery
Z1c_DooMLoRD_AdvStkKernel_FW-681_v03
link
https://mega.co.nz/#!ZIMCXT7J!ES_Ldwh9oBjamrr191ZZ-iMXGZMIMHaG1iXV3kp6ER4
Hi,
Does this app posted a few days ago also do the job behind the scenes ?
[APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD
TwoPointZero said:
Hi,
Does this app posted a few days ago also do the job behind the scenes ?
[APP][4.4][ROOT] SDFix: Modify device permissions to allow apps to write to MicroSD
Click to expand...
Click to collapse
My Z1 Compact is "unlocked" with method explained in this thread.
App does same job/modifications, personally didnt tried app.
Manualy or with app, choice is yours.
I will wait for an exploit,...dont want to unlock the bootloader and lose the warrenty
Hello everyone,
My sensor went bad after screen replacement. It always detects as near. Until now I was using xposed to disable it. But now after upgrading to Android N, I don't have xposed and I don't know how to fix it.
The screen is turned off when I make/attend a call, making it difficult to end.
Is there any config file or something in source where I can disable it??
Thank you.
You can use settings>accessibility>Use power button to end call...
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
swapnil0545 said:
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
Click to expand...
Click to collapse
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
The solution for that it change the black thing make the bigger hole on sensor of light and the small one with other
Default for that is small one with sensor light and bigger one for something else
So sorry for bad language see that steps here
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
ze7zez said:
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
Click to expand...
Click to collapse
I am going to try this. I hope I don't soft brick it.
swapnil0545 said:
I am going to try this. I hope I don't soft brick it.
Click to expand...
Click to collapse
Hey did you get it to work?
I've tried - no, did not work on 7.1.
Have you any other solution? I've the same issue on nexus 6p After display replacement. And now on nougat i can't fix it. Simeone Can help me?
My other solution was to recompile Dialer.apk with proximity disabled.
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Where is the apk located? I'm running 7.0 and cannot find it in the system/apps folder.
On CM14 it is in /system/priv-app/Dialer/
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
You are a life saver
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7 ?
sweetmyke said:
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7
Click to expand...
Click to collapse
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
driftking132 said:
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Click to expand...
Click to collapse
You should run these commands on a PC, to which phone is connected by USB cable.
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
I've attached my version of the fix that I've been running since CM13, now recompiled for CM14.1. There's effectively only one line of code changed. Source is up-to-date to Feb 6, 2017.
As far as I can tell, digital0's version works just as well, so there's no reason to try mine if you're not having issues with his.
Same way to install the apk. Attached diff for the curious.
Shimakaze said:
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
Click to expand...
Click to collapse
The CM build I used at the time of compiling gave the error. It is most probably not needed now.
driftking132 said:
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
Click to expand...
Click to collapse
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
sweetmyke said:
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
Click to expand...
Click to collapse
its worked but in call screen there is no answer/ reject buttons please fix this
Anyone know how to remove Cricket Wireless mobile hotspot restrictions? I'm on an unlimited plan, and would like to use the phone's built-in hotspot.
Cybertron713 said:
Anyone know how to remove Cricket Wireless mobile hotspot restrictions? I'm on an unlimited plan, and would like to use the phone's built-in hotspot.
Click to expand...
Click to collapse
Are you unlocked and rooted? Have you tried adding "net.tethering.noprovisioning=true" to the build.prop file then reboot? That works for most people...
acejavelin said:
Are you unlocked and rooted? Have you tried adding "net.tethering.noprovisioning=true" to the build.prop file then reboot? That works for most people...
Click to expand...
Click to collapse
Unlocked (bootloader and, naturally, carrier) and rooted (via magisk).
I have not. Don't actually know how to edit build.prop on-device.
Cybertron713 said:
Unlocked (bootloader and, naturally, carrier) and rooted (via magisk).
I have not. Don't actually know how to edit build.prop on-device.
Click to expand...
Click to collapse
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a root text editor (Jota, Turbo, QuickEdit, etc)
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
acejavelin said:
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a root text editor (Jota, Turbo, QuickEdit, etc)
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
Click to expand...
Click to collapse
Ayyy, that worked! Thanks, my man!
Cybertron713 said:
Ayyy, that worked! Thanks, my man!
Click to expand...
Click to collapse
Glad it worked... Don't forget to click "Thanks" at the bottom of my posts, best way to show your appreciation.
acejavelin said:
Glad it worked... Don't forget to click "Thanks" at the bottom of my posts, best way to show your appreciation.
Click to expand...
Click to collapse
Of course! Been off XDA for too long, forgot the thanks system.
***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!*** ***PIXEL 2XL ONLY!!!***
Confirmed this works with Android O and P!
UPDATE 3/17/2020: Now confirmed this works with Android Q, but with slight modification!
It took me many hours to piece together the various forums and articles, but these instructions will have you up and running in 30 mins max!
*Below instructions assume brand new phone out of the box, everything stock.
1. Download adb and fastboot on your computer. You don't need the whole SDK and don't need to install anything; Google now provides them in a simple zip file. Get it here for Windows, Linux, Mac. If you're using a Mac, all you have to do is open Terminal, cd into the directory where you unzipped the files, and type ./adb [command] from there. EX: If you downloaded the zip file into your Downloads folder, and extracted the zip also in your Downloads, you'd type the following on a Mac:
Code:
cd ~/downloads/extractedfoldername
Code:
./adb version
with your phone plugged in via USB to the computer to test adb works. Make sure to enable developer mode on your phone, and also enable USB Debugging. NOTE: For all below references to adb and fastboot, make sure to include the "./" before the command from the extracted directory. EX: "./adb" and "./fastboot"
2. Unlock bootloader. Follow the directions provided here in the "Unlock the bootloader of the Pixel 2 / Pixel 2 XL" section. (Don't waste your time reading the rest of those instructions, since that will confuse you and they don't work anyways.) I did unlock_critical at first, but the bootloader still said it was locked. Then I did "flashing unlock" and that unlocked the bootloader. Make sure device status in fastboot on the phone says "unlocked." Reboot the phone.
3. Download the latest Magisk Manager from here to your computer. I used 5.6.4.
4. Type
Code:
./adb push <path_to_file> /sdcard/Download
5. On the phone, go to your Downloads app and install the Magisk Manager apk.
6. Open the manager. Click the Install button. It will ask if you want to "install Magisk-vXX.zip now". Click Install and then select Download Zip Only at the next prompt.
7. Download the TWRP image here to your computer. NOTE: You only need to download the IMG file! Don't need the zip file.
7.5 From your computer, run:
Code:
./adb reboot bootloader
8. From your computer, run:
Code:
./fastboot boot path/to/twrp.img
9. Once phone boots into TWRP, go to Install. Then go to the MagiskManager directory. In there, you should see the "Magisk-vXX.zip" file you downloaded in Step 6.
10. Now reboot your phone and open up the Magisk app. You should now see it says "Latest Version: vXX.X" and "Installed Version: vXX.x" with green check marks next to the items. Open the Magisk settings (3 bars on the top left) and you should see a bunch of options, one of them says #SuperUser. This means you now have root!!
11. To enable the tethering:
For Android 8 and 9:
Code:
./adb shell
Code:
su
**(grant permission if phone asks)**
Code:
mount -o rw,remount /system
Code:
echo "net.tethering.noprovisioning=true" >> /system/build.prop
Very important step! You must reboot for the changes to take effect.
Code:
reboot
For Android 10
It seems like you can no longer mount /system as rw. So it's a little more complicated. If you fully installed Magisk (not the way I did it above), then from Magisk Manager, go to Modules and download MagiskHide Props Config and busybox-ndk. Follow the instructions here to run the Props Config.
If you followed my rooting instructions above, running the Props Config won't work, but there is a workaround.
You could still use the module, but instead of using the props command and the terminal UI, you just use the configuration file to set everything up. Download the settings file, extract it from the module zip (in the /common folder) or copy it from the module directory under /data/adb (in the /common folder), add
Code:
net.tethering.noprovisioning=true
to the CONFPROPS variable, place it in the root of your internal storage (/sdcard) in /data or in /cache (or /data/cache if you're using an A/B device) and reboot.
Another option is to just use a simple boot script. Put the following in a file (doesn't matter what you name it) in /data/adb/service.d:
Code:
#!/system/bin/sh
resetprop net.tethering.noprovisioning true
Give it execution permission (chmod 755 is usually the goto) and then that prop will be set at each boot. If it doesn't seem to work, put the script in /data/adb/post-fs-data.d instead.
Very important step! You must reboot for the changes to take effect.
Code:
reboot
[email protected]##
Giant shoutout and thank you to @Didgeridoohan for helping me debug and figuring this out! You're a life saver.
References:
MagiskHide Props Config Documentation thread
MagiskHide Props Config README
Thread where Didgeridoohan explains the process and help me debug
Codes
Hi im having trouble with getting the commands right, I seem to be getting the message stating the command push requires argument but im not sure why, can you provide the actual command in full how it should be input.
Thanks
I didn't even bother using the commands. All I did was root as given in the guides for this device. I then used a file manager with root capability to access build.prop and edit the file directly to add the line. Afterward I rebooted and was all set.
Of course, with my service provider I may not have needed to do this as their provisioning doesn't seem to touch tethering, even though they don't allow it. I'll find out next month when the security update comes through.
Excellent guide, except for one crucial missing step:
7.5 Reboot back into the bootloader:
Code:
adb reboot bootloader
I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?
Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?
ashayden said:
I'm on a grandfathered att unlimited plan, which does not allow tethering. I have edited the build prop to enable it, but does anyone know if they can detect that I am tethering?
Click to expand...
Click to collapse
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
This is a true statement.
frankygoes said:
Need help.
i accidentally used this for a pixel 2 and now cannot get past the white startup screen with the google logo. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue. I previously used the build.prop updated a number of times, but after doing it with the July factory images, I get stuck on boot. Anyone figure out a way around this?
I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro
soccercake7 said:
I did this method and have root but I have no recovery.
According to this: https://twrp.me/google/googlepixel2xl.html I needed to install twrp zip after fastboot boot twrp.img and I can't do it now because I'm rooted and need to reflash boot image. dang!
/necro
Click to expand...
Click to collapse
You don't need reflash your boot image. Just put your phone into recovery, then go back to temporary twrp by fastboot boot twrp.img. Then flash twrp.zip
Strephon Alkhalikoi said:
There are multiple ways they can detect whether you are tethering or not. And there's no way to hide the activity either.
Click to expand...
Click to collapse
Not entirely true if your device is fresh out the box. On my previous phone when we were all trying to unlock the bootloader on the Verizon variant, I did it accidentally. I failed to unlock the bootloader lol, but if you never put a Sim in the device and delete the radio file to temporarily "un-grey" the OEM unlock ticker, and then install a vpn (I used the cracked adguard plus from revdl) and turn on basically everything, then factory reset to get the radio back, then reinstall the vpn and enable all the ad masking options and THEN put your sim in for the first time...
I don't know how or why it works but I went almost three months tethering my heart out on Verizon for like 400-700 gigs/month without being throttled one bit or subjected to their bull**** priority system. An added peculiarity was I also had glasswire data moniter installed before ever inserting the sim and both it and the Verizon built in data meter both just stayed at zero. Unfortunately, I was sending a file to a friend with sendanywhere and we were having trouble getting it to accept the access code so I turned off the adguard protections just for like two minutes and both data monitors started spitting out numbers and I got throttled into Oblivion the following bill cycle.
Again, I don't know how many of those steps are needed or what exactly to turn on in adguard, but I do know that it somehow let's you in the data door and keeps the traffic source anonymous until you give the device a window to phone home with your account. Wish I could be more specific with directions but it absolutely worked, somehow. I haven't used sendanywhere since that day and never will again because it ruined something so beautiful for me.
I tried for probably two dozen hours to reset and recreate the circumstances and get those sweet, sweet zeroes back, but to no avail, so I would assume that it can't ever work on the device once it's had a Sim installed even for a moment, and once working you must keep the vpn running from startup forever...probably can't ever factory reset or you will lose it. I really don't know. I'm sure one of the techier peeps here could figure out how and why it works or already knows, but doesn't want to post it because then it will get fixed and ruin his or her own beautiful thing.
8wrlobo said:
Not entirely true if your device is fresh out the box.
Click to expand...
Click to collapse
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.
Strephon Alkhalikoi said:
https://android.stackexchange.com/q...-companies-detect-tethering-incl-wifi-hotspot
You got lucky.
Click to expand...
Click to collapse
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.
n2music said:
I use NordVPN and VPN Tether on rooted (Magisk) stock Google Pixel 2 XL . Carrier doesn't see my tethering.
Click to expand...
Click to collapse
A VPN if I recall doesn't prevent the carrier from using the number of hops (i.e. the TTL number) to detect tethering. It does prevent them from seeing what data you are pushing across the network however.
My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.
n2music said:
My total data use increases, but tether usage does not. I rarely use more than 30gigs altogether each month anyway, not an abuser.
Click to expand...
Click to collapse
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.
Strephon Alkhalikoi said:
Not an abuser, but in the eyes of the carriers that don't want you tethering without paying you are a thief. It's silly because in the end it's still data, and just a way for the carriers to gouge you.
Click to expand...
Click to collapse
I actually do pay for it. I am on beyond unlimited. But I agree with you.
n2music said:
I actually do pay for it. I am on beyond unlimited. But I agree with you.
Click to expand...
Click to collapse
Sorry for assuming you didn't pay for the privilege. Since the discussion started by others centered on ways to prevent carriers from detecting tethering, I ran on that assumption.
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