Related
Anyone can confirm this?
This guide will help you to connect your G1 to laptop's Ad-hoc wireless network.
Requirements:
1. Rooted G1 phone.
2. Terminal emulator. (You can download it here or from Android market)
3. Busybox for android. (download)
Steps:
1. Install Terminal emulator
I assume that most of you guys already have this since it is essential for root access.
For those who don't have this installed you will have to make sure that you have root access first.
The easyest way to install this application is to download it from Android market, but if you don't have access to internet from your phone, you could install it over ADB or some other way.
2. Install busybox for android
Open Terminal emulator and type following commands:
Become super user:
Code:
Code:
su
Make new directory for busybox and navigate to it:
Code:
Code:
mkdir /data/busybox
cd /data/busybox
Now you should copy your downloaded busybox file to this new directory. You could do this simply by connecting your phone to the computer over usb cable and copy file to the sdcard or you could push it using ADB service directly to our directory. If you wish to do this over ADB you should do the following.
a) ADB is part of Android SDK and you can freely download it for Windows, Linux or even Mac, just google it. Your downloaded busybox file must be in the same folder with adb or you can specify the different path in adb command if you have it somewhere else. To push the file to the phone using ADB you could type the following command on your computer (offcourse you must first navigate to the folder in which is your Android SDK and then to the subfolder tools):
Code:
Code:
adb push busybox /data/busybox/busybox
b) The other way is to copy the file to your sdcard and then move it to our folder with cat command, since we don't have cp command to copy the file. To do this you must type the following commands on your phone assuming we didn't leave Terminal emulator and we are still in /data/busybox/ directory.
Code:
Code:
cat /sdcard/busybox > ./busybox
Now that you have it in your folder you should do the following:
Make busybox binary executable
Code:
Code:
chmod 755 ./busybox
Execute following command to install busybox:
Code:
Code:
./busybox --install
Make all the installed tools in folder executable like you did with the first one:
Code:
Code:
chmod 755 *
Last step is to export it to PATH to make it usable at all time.
Code:
Code:
export PATH=/data/busybox:$PATH
3. Now you can modify two important files to make your phone able to connect to Ad-hoc
First gain root access with su command like before:
Code:
Code:
su
Remount /system partition as read-write with the following command:
Code:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Navigate to /system/etc/wifi/
Code:
Code:
cd /system/etc/wifi
Now you must edit tiwlan.ini file in current directory. I did this with VI editor which is part of busybox. You must know some basic things about VI editor befor you do this. VI operates in two modes. When you open editor you are in command mode and you can't edit your file yet.
To edit file type:
Code:
Code:
vi tiwlan.ini
First you must navigate trough file with your trackball. Find the following line:
Code:
Code:
WiFiAdhoc = 0
This is the line we need to edit. To enter edit mode press A on your phone's keyboard. Now move the cursor with trackball to the end off this line. Replace 0 with 1. You must add two more lines in order this to work. To add new line press enter key and then type:
Code:
Code:
dot11DesiredSSID = HTCG1
dot11DesiredBSSType = 0
Replace HTCG1 with whatever you like. This is SSID of your wireless Ad-hoc network.
Now you must exit back again to command mode. This is done with escape key, and since our keyboard doesn't have escape key we must click down trackball and simultaniously press 1. This is the same as you pressed escape on regular computer keyboard. In command mode again we can't edit the file but we can type commands. Command for saving file is 'w' and for exiting editor is 'q'. Every command is typed after ':' so our command to save file and exit editor will be:
Code:
Code:
:wq
The next file we need to edit is /data/misc/wifi/wpa_supplicant.conf
Edit it the same way as previous file and add these lines:
Code:
Code:
network={
ssid="HTCG1"
key_mgmt=NONE
mode=1
}
Save and exit
'mode = 1' indicate that this is Ad-hoc network
4. Make Ad-hoc network on your laptop or computer.
I assume you know how to do that and I won't explain it because you can google it. Only thing to know when you do this is that you have to set SSID for the network same as the SSID in two files you edited and that you must make open network without wep or other security. Yet if you decide to have protected network you must also edit wpa_supplicant.conf file and modify it. Again google it if you want to know more.
5. Finally connect
If you configured correctly your computer wireless network and selected it to connect, you should then disable and enable wireless in your mobile phone settings. If SSID is broadcasted you should see your network and signal strenght in network list. Connect.
that may work. theres an app for that though (not trying to sound iphonish )
aNetShare. easy to use.
aNetSHARE mega upload link
I think aNetShare is for sharing your G1s data network to your computer. This guide is for doing the opposite. Basically useful if you have a wired only internet connection but want to use your laptops wireless card to share the wired connection with the G1. That being said, I tried to do this and my G1 is unable to connect to the ad hoc network.
Holy crap iv been waiting for this for a long time.
Hopefully some guys are able to put a gui around this to make it user friendly
Hey, can anyone tell me how should I change the last file, like this (how to make those spaces?):
network={
ssid="HTCG1"
key_mgmt=NONE
mode=1
}
like this:
network={
ssid="HTCG1"
key_mgmt=NONE
mode=1
}
like this:
network={
ssid="HTCG1"
key_mgmt=NONE
mode=1
}
or maybe like this:
network={ssid="HTCG1"
key_mgmt=NONE
mode=1}
Any ideas? I tried different combinations, nothing happens. Maybe I am setting ad-hoc wrong in the computer. Can anyone give me a simple solution? I'm without net in G1 for a couple of days, so I need to share my laptop net connetcion with G1.
No matter what your changes, all of they are right. If you are on right way, you can see there is a network named "HTCG1" in available wireless networks, in Wireless Settings. I was successful with this tutorial. Let's make the changes, step-by-step.
(additional CHOWN notes added below. If you are getting "chown: unknown user/group system:system" read them!
Ok, we do have a WHOLE other thread that was made a sticky already, but you need to read the WHOLE thing to get all the properly interesting parts. I'll make sure I keep this OP up to date.
The following methods enable side loading and installing of apps onto the captivate, without the need of a program on a computer attached via the SDK. There are multiple methods, and for the most part, these methods that have worked flawlessly for many users here on this forum. We're just collecting them all in one post for speed and clarity.
Methods that assist in loading applications, without modification to the settings (a.k.a still need a computer attached) can be found at the collective wiki, http://samsungcaptivate.wikia.com/wiki/How_to_Sideload
ALL METHODS REQUIRE ROOT & BUSYBOX:
Root your phone, see http://forum.xda-developers.com/showthread.php?t=725555
Busybox : http://www.appbrain.com/app/stericson.busybox
Please, save a clean, un-altered backup copy of this file. To be safe. Rarely does corruption occur, but if it does, it won't be good.
Method 1: From Win7x64, Samsung Drivers, Android SDK installed.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the command prompt. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppBrain etc and run it. It will download and install the latest version for you.
From my Win7x64, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to PC, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open command prompt, follow along:
Code:
> c:
> cd \android\tools
> adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the pc,
"USB Connected select to... ", Mount
mine mounted as H:
Code:
> copy H:\settings.db settings.db
> sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> copy settings.db H:\settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Bam. Done.
Method 2: with Root Explorer
(courtesy of kirbo20)
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
(added by gotfolk)
again using FF plug in..
Click Secure on the left pane
click on install_non_market_apps
click edit
number 3 states value click there and type in 1. hit ok
(/gotfolk)
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
( This is a sqlite3 database file, you can find many GUI editors that will be able to handle the editing, including a FF plugin. Search "SQLite" )
Method 3: with Root Explorer & Sqlite Editor & Terminal Emulator
(courtesy of ice3186)
- Open Root Explorer
- Browse to /dbdata/databases/com.android.providers.settings/
- copy settings.db to the root of your sd card ( /sdcard/ )
- Click on the newly copied settings.db in /sdcard/, with SQLite Editor installed, you can open and edit it here.
- Select the "secure" table, and update the value of 'install_nonmarket_apps' from 0 to 1, and save.
- close out of SQLite editor
- copy the modified file ( /sdcard/settings.db ), and browse back to /dbdata/databases/com.android.providers.settings/ and paste
- confirm the overwrite if asked and then open again to confirm it's been changed.
- open Terminal Emulator
Code:
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# reboot
- reboot phone.
No PC, no Mac, no drivers, no SDK. Viola.
Method 4: Mac & Android SDK
You will see "[sdcard]" through this method...I don't own a Mac so I'm guessing a bit.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the Terminal. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppDroid etc and run it. It will download and install the latest version for you.
From a Max OS X, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to Mac, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open Terminal, follow along:
Code:
> cd /android/tools
> ./adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the Mac,
"USB Connected select to... ", Mount
mine mounted as [sdcard]
Code:
> cp [sdcard]/settings.db settings.db
> ./sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> cp settings.db [sdcard]/settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> ./adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> ./adb reboot
Method 5: Android SDK only
Of course, this also requires root and BusyBox.
From the android sdk tools folder in a command prompt:
note: all linux/mac should use './adb' in place of just 'adb', and place quotes on the echo statement between echo and |
Code:
adb shell
su
chmod 666 /dbdata/databases/com.android.providers.settings/settings.db
exit
exit
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /dbdata/databases/com.android.providers.settings/settings.db
adb shell
su
chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
chown system.system /dbdata/databases/com.android.providers.settings/settings.db
reboot
NOTICE
You must chown the settings.db file and reboot once it is back in its original location. If you do not, you will not be able to alter settings such as WiFi,GPS, default Ringtones, etc. It's also highly likely that you may wish to chmod to 660 (-rw-rw---), so I've tacked that in here and above.
Code:
> adb shell
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Chown Note
In the event that you are getting "chown: unknown user/group system:system" please try 1000.1000 as this has been reported to work on several of the samfirmware-released roms that fail with this message.
Absolutely do not use someone else's settings.db unless you specifially make it a point replace android_id with your android_id!
Special Note
Any of these adb comments can be run from Terminal Emulator (Android Terminal Emulator, free) from the su command. I use the ADB here as it is a lot easier to type into. Terminal Emulator will provide you with a shell that is an exact match of the 'adb shell' command, as they both simply provide the shell to you.
Result:
After completing this process you will be able to load non-market apps directly from the APK files, SDK tools, tools such as DroidExplorer and apps such as APKtor.
You will be able to download the APKs directly, and then install from your favorite file browser (e.g. MyFiles(s), Astro(f), RootExplorer($)...)
Tools
SQLite Administrator (Win, GUI, no FF required) http://sqliteadmin.orbmu2k.de/
SQLite Manager (FF addon, search for it)
Application links
Root Explorer http://www.appbrain.com/app/com.speedsoftware.rootexplorer
SQLite Editor http://www.appbrain.com/app/com.speedsoftware.sqleditor
Terminal Emulator http://www.appbrain.com/app/jackpal.androidterm
BusyBox http://www.appbrain.com/app/stericson.busybox
bump.. settings.db people.. please read the threads!!
good stuff!!!
Ok. I can find settings.db with root explorer. i can copy it and i put it in my sdcard folder but nothing is there when i try to find it on my computer. Im trying to use SQlite editor on firefox. Im also on a powermac g4 if that makes a difference. I did download sqlite editor on my phone and I can find where to change the values for installing non market apps but when I change from a zero to a one it denies me. Please help
Ok, so let me make sure I have your process:
- Rooted
- Installed busybox ?
- Installed Root Explorer
- copied settings.db to /sdcard
-- cant see the file when mounted to Mac, thus can't edit with FF plugin
-- SQLite editor for android wont allow access..
(is this the SQLite Editor you used? http://www.appbrain.com/app/com.speedsoftware.sqleditor)
Try installing "Android Terminal Emulator" from the market (http://www.appbrain.com/app/jackpal.androidterm)
- open Terminal Emulator
$ su
# cd /sdcard
# chmod 777 settings.db
# exit
- Open the sqlite editor, and make the change
- back to Terminal Emulator
$ su
# chmod 660 settings.db
- proceed with rest of instructions.
how many more threads do we need on the same thing? We already have ALL of this info posted, several times.
designgears said:
how many more threads do we need on the same thing? We already have ALL of this info posted, several times.
Click to expand...
Click to collapse
Please read my initial post, first few lines. I explained why, specifically: Consolidation.
Thanks I will give it a try later today.
Sent from my SAMSUNG-SGH-I897 using XDA App
- OP updated to reflect stock ownership settings for 'chown'
Also, which sqlite app are you using? I'll put that up as method 3 if it works out nicely for you.
fixed a typo in the chown command.. bad copy paste.. bad.. doh.
added method 3 courtest of ice3186
added links to Root Explorer ($), SQLite Editor ($) and Android Terminal Emulator (free) and added the chmod/chown commands to method 3, as they were skipped by accident.
bump** for newcomers, sry.
thanks max for adding the third method. this was by far much easier than the first two methods. I have a hard time getting my mac to talk to my phone sometimes and it was good to not have to plug the lil guy in at all. Worked like a charm
myself and ice3186 are glad we could be of help
If I had accidentally deleted the settings.db how should I go about recovering my phone? Now I have the issue that my phone won't boot past the boot animation and I'm notbsure what to do
mkslt4 said:
If I had accidentally deleted the settings.db how should I go about recovering my phone? Now I have the issue that my phone won't boot past the boot animation and I'm notbsure what to do
Click to expand...
Click to collapse
Did you make any kind of backup before hand?
You may have to use someone else's settings.db and then do a factory reset.
Depending on how much you've done with the phone I'd suggest deciding on doing a the reboot process for rooting, but choosing to clear data. This may rebuild it, I am not sure.
my dbdata directory is empty.. My phone is less then 2 hours old and i have some market apps installed..
xetrev said:
my dbdata directory is empty.. My phone is less then 2 hours old and i have some market apps installed..
Click to expand...
Click to collapse
Oh, if it's running, then this folder isn't actually empty.
What are you using to browse this folder?
i followed this guide to a T yesterday when i did this. I used option 1, ADB commands on terminal since i'm a mac and it was super easy, did it in about 5 minutes.
this is just my opinion but i think everyone should try playing with the ADB commands, they're actually really useful and educational to know. and if you should brick your phone, just use clockwork recovery to restore it.
that being said, maybe you should add a disclaimer that when done on a mac, the adb commands require a "./" in front (so adb reboot becomes ./adb reboot). cp, chown, and chmod commands don't need it though (or at least i didn't).
I had a hell of a time finding this while digging through the forums. I thought I would wrap it up in one nice neat easily readable thing....
In order to get Netflix working on the 3.0 kernal you need to do 1 of 2 things.
Option 1
You can edit build.prop by using Root Explorer and going to /system/build.prop and selecting "Open in Text Editor" Via long-press. Than edit build.prop on the line ro.product.model and change it to Amazon Kindle Fire
Option 2
You can use ADB to do it as well by doing this
From the command line:
I) Remount /system in read/write mode using:
Code:
adb remount
II) Next, Copy build.prop to your PC, it will show up in the same directory as adb.exe
Code:
adb pull /system/build.prop
III) Next Edit build.prop using notepad or your preferred text editor on the line (notepad++ is mine) ro.product.model and change it to Amazon Kindle Fire
IV) And Push build.prop back to the device
Code:
adb push build.prop /system/build.prop
Finally, After Either Option Restart the Device and you should be watching Netflix bau55 style.
THANKS TO nathris AND twa_priv for providing the fix
s0m3f00l
I think his latest updated ROM fixes the issue with build.prop. There's nothing new but the did fix the name.
ya I flashed his 4/22 rom and Netflix works fine.
Sent from my Amazon Kindle Fire using xda premium
Hashcode updated hist 04-22 build with the fixed build.prop. The build can be found here: http://rombot.droidhive.com/ROMs/otter/cm9/
I installed from CM9 reloaded and I had to go through the fix.
s0m3f00l said:
I installed from CM9 reloaded and I had to go through the fix.
Click to expand...
Click to collapse
Yeah, all roms build before yesterday probably have this issue.
the Other modules for updating the platform.xml file is bit complex and risky....
below are the steps which is easy and safe
advantages ::
1) you can save the Kernel, from any modifications..
2) you still can keep the system protection ON and dont have to break it
Friends...
here is the workaround i Did and succeeded.....
note : 1 ) rooted mobile 2) should have installed twrp recovery in the mobile... 3) terminal emulator for android installed
1) I made a copy of platform.xml in my sd card and copied to PC
2) edited the platform.xml using note++ in my pc like below...
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORA GE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
<group gid="media_rw" />
</permission>
3) copied the modifed file again to sd card of the phone
4) modify the ownership and permission of platform.xml for mobile requirement ::
i) use the terminal emulator for android
ii) open the term
( i) type the following a) su b) cd /ext_sdcard/path/ c) ls -l |grep -i plat
d) chown root:root platform.xml e) chmod 644 platform.xml f) ls -l |grep -i plat --> verify if the permission is ( rw-r-r root root )
4) rebooted the mobile to twrp recovery
5) using mount option mount system & sd card
6) using advanced option, go to filemanager and /system/etc/permissions/ select the file ( platform.xml)
i) it will show special menu rename the original platform.xml to platform.xml.org
7) go back to filemanager, /ext_sdcard/path..../ copy the platform.xml from sdcard to /system/etc/permissions/ ( system location )
8) using chmod change the permission to 0644 ( check the owner information too, skip if the 4 step is completed )
9) reboot the mobile...
10) you can see any applications requiring sd card access will be happy & not annoying about the write permission on the sd card...
11) you can verify if the file has been modified or not by using the terminal emulator
i) use the terminal emulator for android
ii) open the term
i) type the following a) su b) cd /system/etc/permissions/ c) ls -l |grep -i plat d) cat platform.xml ( you can see the new entries in them )
12) if this fails, go back to twrp recovery and
remove or delete the newly added platform.xml and rename the original file to its former state....
Let me know if you succeed in this or need any help ....
:good::good::good::good::good::good::good::good::highfive::highfive::highfive::highfive::highfive::good::good::good::good::good:
hi SivasankarC,
give me your modify-platform-xml-file plesssss.....
kishorparmar said:
hi SivasankarC,
give me your modify-platform-xml-file plesssss.....
Click to expand...
Click to collapse
ok done ............
https://drive.google.com/file/d/0B-0MK7r6HDbzWmtTN2FYNTc3UEk/edit?usp=sharing
goodluck....
SivasankarC said:
ok done ............
https://drive.google.com/file/d/0B-0MK7r6HDbzWmtTN2FYNTc3UEk/edit?usp=sharing
goodluck....
Click to expand...
Click to collapse
---------------------
Thanks bro.......:good::good::good:
---------- Post added at 02:57 PM ---------- Previous post was at 02:20 PM ----------
hi SivasankarC,
terminal emulator staps is necessary ?
if I do this staps copy past your modify-platform-xml-file from twrp recovery
1- copy your modify-platform-xml-file to sd card
2- rebooted to twrp recovery
3-using mount option mounted system & sd card
4-using advanced option, renamed the original platform.xml to platform.xml.backup
5-copied the platform.xml from sdcard to system location
6- using chmod i changed the permission to 644
7-reboot the mobile
its working ?
thanks.
kishorparmar said:
---------------------
Thanks bro.......:good::good::good:
---------- Post added at 02:57 PM ---------- Previous post was at 02:20 PM ----------
hi SivasankarC,
terminal emulator staps is necessary ?
if I do this staps copy past your modify-platform-xml-file from twrp recovery
1- copy your modify-platform-xml-file to sd card
2- rebooted to twrp recovery
3-using mount option mounted system & sd card
4-using advanced option, renamed the original platform.xml to platform.xml.backup
5-copied the platform.xml from sdcard to system location
6- using chmod i changed the permission to 644
7-reboot the mobile
its working ?
thanks.
Click to expand...
Click to collapse
Yes that should do the magic......
after reboot...........
just check this
i) type the following a) su b) cd /system/etc/permissions/ c) ls -l |grep -i plat
both the platform files should be having same permissions.... rw-r-r and root:root
check if application has the access to ext sd card.....
SivasankarC said:
Yes that should do the magic......
after reboot...........
just check this
i) type the following a) su b) cd /system/etc/permissions/ c) ls -l |grep -i plat
both the platform files should be having same permissions.... rw-r-r and root:root
check if application has the access to ext sd card.....
Click to expand...
Click to collapse
----------------------
thanks.
hi SivasankarC
Its Possible we Swap Internal and External Memory on rooted htc 816 ?
kishorparmar said:
hi SivasankarC
Its Possible we Swap Internal and External Memory on rooted htc 816 ?
Click to expand...
Click to collapse
I am pretty much sure, that can be done........... filesystem entries has to be modified... and might be many other short cuts has to be re-linked.....
but i have not done that............ it might ruin the speed and possibly corrupt....
use a good sd card ( i use samsung pro card ) and use folder mount application buy pro....
phone should be rooted,,,,
after any application is installed in the device....
1) manually stop the application from apps->services....
2) use root explorer to move the entire content of the apps to sd card....
3) use folder mount app to create a link to directory....
4) start the apps....
( i used in NFS MW moved the 2 gb data to sdcard and base app in internal mem game is working good no issues )
by doing this, you can have the apps in sd card, with the internal memory free....
some basic apps like players.... etc if installed in internal memory will have good response time....
but having entire apps in sd card... hmmm i dont recommend....
hi SivasankarC,
thanks for reply....:laugh:
SivasankarC said:
the Other modules for updating the platform.xml file is bit complex and risky....
below are the steps which is easy and safe
advantages ::
1) you can save the Kernel, from any modifications..
2) you still can keep the system protection ON and dont have to break it
Friends...
here is the workaround i Did and succeeded.....
note : 1 ) rooted mobile 2) should have installed twrp recovery in the mobile... 3) terminal emulator for android installed
1) I made a copy of platform.xml in my sd card and copied to PC
2) edited the platform.xml using note++ in my pc like below...
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORA GE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
<group gid="media_rw" />
</permission>
3) copied the modifed file again to sd card of the phone
4) modify the ownership and permission of platform.xml for mobile requirement ::
i) use the terminal emulator for android
ii) open the term
( i) type the following a) su b) cd /ext_sdcard/path/ c) ls -l |grep -i plat
d) chown root:root platform.xml e) chmod 644 platform.xml f) ls -l |grep -i plat --> verify if the permission is ( rw-r-r root root )
4) rebooted the mobile to twrp recovery
5) using mount option mount system & sd card
6) using advanced option, go to filemanager and /system/etc/permissions/ select the file ( platform.xml)
i) it will show special menu rename the original platform.xml to platform.xml.org
7) go back to filemanager, /ext_sdcard/path..../ copy the platform.xml from sdcard to /system/etc/permissions/ ( system location )
8) using chmod change the permission to 0644 ( check the owner information too, skip if the 4 step is completed )
9) reboot the mobile...
10) you can see any applications requiring sd card access will be happy & not annoying about the write permission on the sd card...
11) you can verify if the file has been modified or not by using the terminal emulator
i) use the terminal emulator for android
ii) open the term
i) type the following a) su b) cd /system/etc/permissions/ c) ls -l |grep -i plat d) cat platform.xml ( you can see the new entries in them )
12) if this fails, go back to twrp recovery and
remove or delete the newly added platform.xml and rename the original file to its former state....
Let me know if you succeed in this or need any help ....
:good::good::good::good::good::good::good::good::highfive::highfive::highfive::highfive::highfive::good::good::good::good::good:
Click to expand...
Click to collapse
Thank you so much for this mate. Helped a lot and saved me a lot of trouble
Plz Help
Im a noob and im not getting how to go through this step can sum1 guide me in detail. my 816 is rooted
---------- Post added 27th July 2014 at 12:04 AM ---------- Previous post was 26th July 2014 at 11:49 PM ----------
i used xposed and downloaded sd fix module from it and now i can del and copy files from sd card but in tube mate im not able to download videos directly to sd card. will replacing platform.xml wrk for me?
Just copy the file and everything will work.It work on my phone l edit file myself...
Sent from LG 4X HD using Tapatalk 2
kishorparmar said:
---------------------
Thanks bro.......:good::good::good:
---------- Post added at 02:57 PM ---------- Previous post was at 02:20 PM ----------
hi SivasankarC,
terminal emulator staps is necessary ?
if I do this staps copy past your modify-platform-xml-file from twrp recovery
1- copy your modify-platform-xml-file to sd card
2- rebooted to twrp recovery
3-using mount option mounted system & sd card
4-using advanced option, renamed the original platform.xml to platform.xml.backup
5-copied the platform.xml from sdcard to system location
6- using chmod i changed the permission to 644
7-reboot the mobile
its working ?
thanks.
Click to expand...
Click to collapse
Thanks!
Yes it's working at HTC Desire 601 zara ul 4.4.2 rooted s-on
Thx bro
Sent from my D816w using XDA Free mobile app
Thank you kindly my good man.
I used this trick to edit the default.xml file
Changed the rule from 2 to 0
Confirm free WIFI Tethering now working. Very handy trick when you do not have S-off. :good:
Edit: WIFI Hotspot appeared to be working but there is actually no internet connection. Not sure if that's a tethering guard apk issue?
I make easy way to do it
You can flash this zip on your recovery
My recovery is CWM
So it pass I test yet but I want you to test it too
:fingers-crossed::fingers-crossed:
biwajung said:
i make easy way to do it
you can flash this zip on your recovery
my recovery is cwm
so it pass i test yet but i want you to test it too
:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
it did not work
biwajung said:
I make easy way to do it
You can flash this zip on your recovery
My recovery is CWM
So it pass I test yet but I want you to test it too
:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hi biwajung,
I used your flashable .zip (I'm on CWM as well)
It flashed successfully but I'm not sure if it work.
I punched the below into terminal emulator and saw this (screenshot attached)? Does that mean it worked or no? Sorry for the dumb question?
View attachment 2959901
Sivasankar
I currently have 5.36gb of "other" on the internal storage. We're you able to move 2gb of that to your SD card or did you move the "apps" ? I have about 1gb of apps on the internal storage. I was just wondering which 2gb you were able to move to the SD card? It would be awesome if you could provide a step by step how you moved the 2gb to the SD card......thanks.
Sent from my 710C using XDA Free mobile app
i've do it already verygood
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it has been reported that certain build.prop tweaks can cease to function, after removing root.
My use case and reason for posting, is to try and be close to stock as possible and use the most minimal changes. This assists in streamlining my added tweaks after I apply OTA's and updates. As of now, the following tweaks are working with the 8.1.0 and 9.0 (Nov Patch)
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell on your PC. Ensure USB Debugging is enabled on your phone, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below. Ensure you have the latest ADB drivers for your PC and navigate to the "CMD" shell.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
b00ster23 said:
I've seen a few Build.Prop tweaks floating around, but thought it would be a good idea to start a repository for quick reference. Can add tweaks as they become known and verified to work. To edit the build.prop you will need ROOT access. Also, it's been reported that certain build.prop tweaks cease to function after removing root.
Unlock/Flash/Root Guide provided by @nathanchance
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
WiFi Tether
net.tethering.noprovisioning=true
Disable USB Debugging Notification
persist.adb.notify=0
Disable Sending Usage Data
ro.config.nocheckin=1
There are too many build.prop editors out there to list, so I'm going to bypass recommendations. However, the following is a way to edit the build prop from the ADB Shell. Ensure USB Debugging is enabled, if it isn't already done, and run the following commands. Just replace the command between the "quotation marks" below.
adb shell
su
**(grant permission if phone asks)**
mount -o rw,remount /system
echo "persist.adb.notify=0" >> /system/build.prop
reboot
EDIT#2 Disable Sending Usage Data
Click to expand...
Click to collapse
Is those build.prop tweaks (except from disabling USB notification) even working?
xFirefly93 said:
Is those build.prop tweaks (except from disabling USB notification) even working?
Click to expand...
Click to collapse
Why yes they are. The purpose that I use them for is to stay at stock with the least invasive changes. Makes it easier to update OTA's and reapply my 'tweaks'