I'm trying to stop the tethering check by editing the build.prop.
Everytime i edit (using numerous editors on my mac, including the terminal via vi) my device hangs on the google logo.
Stock Rom, rooted.
Any thoughts on why this would be?
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
Tried this too an nothing!
I can't figure this out for the life of me.
You need to copy the build.prop out to your SD card, edit with a proper editor, copy it back into place replacing the current file, and then change permissions to 755 I believe. I suggest keeping an unmodified version of the build prop on your SD card also
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
This thread should help a bit. I know its for the g3 but same premise. the permissions appear to be 644 not 755.
http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693
mhennigan1377 said:
Tried this too an nothing!
I can't figure this out for the life of me.
Click to expand...
Click to collapse
You set the partition to R/W using the little button at the top before making the edits?
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
Evo_Shift said:
You set the partition to R/W using the little button at the top before making the edits?
Click to expand...
Click to collapse
The whole partition or just the file? I was setting the file. Should this be R/W for Group and Other ?
mhennigan1377 said:
The whole partition or just the file? I was setting the file. Should this be R/W for Group and Other ?
Click to expand...
Click to collapse
In root explorer, explore to /system. Make the /system r/w (it'll have a r/o next to it so press the "Mount R/W"). Long press the build.prop file and select Open in Text Editor, make your changes and save & exit. Press "Mount R/O" at the top to change the /system back to read only. Reboot.
simms22 said:
i use root explorer(root file explorer app), has worked perfectly with it for 6 years now
Click to expand...
Click to collapse
yup. just used this app this morning to edit the build.prop. no issues here
Got it that time, must have been not the system partition changes.
Thanks!!!
Related
First of all, make a backup!! I am not responsible for the terrible things that can happen to an android device when things go awry lol....
Secondly, I have only tried this using Vegan rom (beta 4, and beta 5.1)... I am assuming it will work with any alternate rom but NO PROMISES!!
TO OBTAIN THE NEEDED FILES:
1) Do a google search for "swype on gtablet (kinda)"
2) Somewhere the search results (it was the very first one when I did the search), you should see a post on the tegratab.com forum entitled "swype on gtablet (kinda)" (posted by rothnic)
3) Download the package on that forum, and extract it. There should be three files located in this package: swype.apk, libswypecore.so, and build.prop.
**Keep the page open as we are also going to use the top of the build.prop file that rothnic posted there!! THANK YOU ROTHNIC!!!!!
INSTALL METHOD USING ROOT EXPLORER
I would complete these steps entirely from your gtab, as it does away with the need to transfer files from a pc, etc!
1) Using root explorer, copy first the swype.apk file, and paste it to \\system\app. Once it is copied, long press on it and click "permissions". The permissions should be set as follows:
Read: Check all three boxes down (for user, group, and others).
Write: Check the first box (for user)
Execute: Check the first box (for user)
2) Now again using root explorer, copy the libSwypeCore.so file, and paste it to \\system\lib. Make sure you mount the \\system\lib folder as "read/write" before copying. Once it is copied, set the permissions exactly as you did for the swype.apk file. Make sure you mount the \\system\lib folder as "read only" again before you exit.
3) Now its time to edit the build.prop file, only we are going to make it easy. Instead of going through and editing it, copy the top of the file that rothnic posted on the tegratab site, and replace the top of your build.prop file with what he has there. Don't edit it or anything, just copy it word for word. I did this in root explorer by doing the following:
Using Root Explorer, browse to \\system. Once in this folder, mark it as "read/write".
Locate the build.prop file, and long press on it.
Select "open in text editor".
Copy the text that rothnic had in the post on tegratab, and use it to replace the text that already exists there at the top of the file. It will fit exactly as the original one that you are replacing did. DO NOT CHANGE THE BOTTOM OF THE FILE AT ALL!!!
When you have copied the text, press the "settings" button, and press "save and exit".
(FYI, I am using Vegantab beta 5.1, and replacing the top of the build.prop file did not do any damage to the tablet at all)
Now restart the tablet.
When the tablet restarts, long press on any text entry field and press "input method".
Swype should be an option. Select it, and start swyping!!
If swype isn't listed, click settings, language and keyboard. Check the box next to swype.
(this will also be a good time to click on swype settings and DISABLE audio feedback, as it will drive you and everyone around you NUTS!!)
Now follow the steps above to set swype as your input method and enjoy!!
INSTALL METHOD USING TERMINAL (Courtesy of Terrypchan)
This can be done without root explorer, BUT you have to be willing to type commands in a terminal emulator. I did it without root explorer by using the terminal emulator app with the VEGAn b5 rom (which is already rooted). The only tricky command you need to do is:
1. su
2. cd /
3. mount -w -o remount /dev/block/mtdblock3 /system
Step 3 is how you mount /system as read-write. That allows you to copy the apk to /system/app and to copy the lib to /system/lib. You can also copy build.prop to /system here. I also did the chmod commands here as well, i.e.
chmod 644 /system/lib/libSwypeCore.so
chmod 644 /system/app/Swype.apk
I had already edited the build.prop on another machine where I could use a real text editor.
This is the command to remount /system as read-only:
mount -r -o remount /dev/block/blockmtd3 /system
reboot and I'm Swype-ing away.
any chance you could paste the build prop edit in here? For some reason my browser is cutting off part of it.
Thanx,
I bet the mod deletes this within the hour!
Hmm, wonder how long this post will last
Agreed... I respect the effort tho and his directions are perfect!
Thanks brotha...
Sent from my SGH-T959
Instructions worked perfectly for me with the small substitution of adb push/pull to edit the build.prop (root explorer force closed after I had edited the file and before saving so I said screw it ). Thanks!
Combine this with the rainex fix for screen smoothness and it makes for a pretty good time lol
Sent from my Droid using XDA App
You don't have to adb it, that's why he recommended root explorer. If you edit it there it automatically makes a backup for you. I've done this with three ROMs, vegan4, zpad3, and vegan5... Never had to use adb
Sent from my Zpad flavored Gtab...
Need help with editing build.prop....swype rar had build.prop in it. Do I copy that same file in full and paste it at the top of build.prop in /system/build.prop...I am confused as to hoe many lines of build.prop I need to edit or change?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
worked for me just fine.
Followed instructions, and used a little common sence along the way. Now it's all up and running.
Thanks a lot for the write up..
Using swpe to type this...
Thanks so much man!
New2Android said:
Need help with editing build.prop....swype rar had build.prop in it. Do I copy that same file in full and paste it at the top of build.prop in /system/build.prop...I am confused as to hoe many lines of build.prop I need to edit or change?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
No ignore the build file in the rar file....
You need to follow the directions exactly and copy the text from the forum post. Remember only the top portion
Swype Keyboard
Confirmed Working on the G tab following above steps. Stock TnT Firmware 3389. Working flawless. Sound and swype.
I am able to get the swype keyboard to come up and type on it but am not able to swype. Dont know what i am doing wrong.
Edited build.prop as shown in the forum still cant swype but just use swype keyboard as a regular keyboard.
Any help will be appreciated
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Any downside to editing the build file in this manner?
Can you change it back after it is installed?
Do you have to redo this every time you go to update your rom?
TaterTot24 said:
Any downside to editing the build file in this manner?
Can you change it back after it is installed?
Do you have to redo this every time you go to update your rom?
Click to expand...
Click to collapse
Thats the nice thing about root explorer, it automatically makes a backup when you have modified it
Yes this would need to be redone for each rom.
Sent from my VegaN 'flavored' GTab...
New2Android said:
I am able to get the swype keyboard to come up and type on it but am not able to swype. Dont know what i am doing wrong.
Edited build.prop as shown in the forum still cant swype but just use swype keyboard as a regular keyboard.
Any help will be appreciated
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
I initially had the same issue, there's something incorrect in the build.prop. PM me and I'll get a copy of mine to you as i'm using VegaN5 as well.
Sent from my VegaN 'flavored' GTab...
Wow. I can't believe this is still here! Anyway, on to my question...
Is it possible/advised to edit the build.prop on a PC using a standard text editor like notepad? I ask because the browsers on my GTab don't show the whole of the text we're supposed to copy from tegratab.
Thanks in advance.
Editing on a pc is probably fine, however you have to make sure the formatting stays correct, otherwise it all goes south lol.
I printed out a copy of the top of the build.prop that rothnic posted on the tegratab site and used that for reference when editing on my tab....made it easier to see where I was in the text editor
Sent from my Droid using XDA App
TaterTot24 said:
Any downside to editing the build file in this manner?
Not that I have seen so far, and I've used this through two roms now
Can you change it back after it is installed?
as i2steve said, root explorer is awesome and makes a copy of the original file for you
Do you have to redo this every time you go to update your rom?
Click to expand...
Click to collapse
Unfortunatley, yes, so I would keep the files saved somewhere on your tab lol
Sent from my Droid using XDA App
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.
dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.
mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.
You might try fixing permissions under recovery.
have you tried the app: nook netflix fixer?
I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?
Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.
I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App
foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"
backup and restore fresh start....?
I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App
foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best
All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App
bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?
I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.
NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>
mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney
How to change the system file's attribution?
Such as from Read only to Normal so that we can replace them..
I have Root Exlporer but it does not do it.. Any other Tool ?
sas_sas said:
How to change the system file's attribution?
Such as from Read only to Normal so that we can replace them..
I have Root Exlporer but it does not do it.. Any other Tool ?
Click to expand...
Click to collapse
Are you rooted?!
Sent from my GT-I9000 using XDA Premium App
Root Explorer should work.
You need to be rooted and have the system mounted as R/W
have the same problem. Phone is rooted, rootexplore asked for super ursser permission, is set to R/W and still i can't change gps.conf in etc folder! i mean i'm copy/paste the change one but it remains the same! WTF?
Have you tried setting the permissions? Long press and hit permissions. Select the ones you want and try again.
Check if the SU permission is correctly attributed to root explorer, or give it again
sas_sas said:
How to change the system file's attribution?
Such as from Read only to Normal so that we can replace them..
I have Root Exlporer but it does not do it.. Any other Tool ?
Click to expand...
Click to collapse
Follow the steps
http://www.hdtechvideo.com/?p=59
creative0100 said:
Have you tried setting the permissions? Long press and hit permissions. Select the ones you want and try again.
Click to expand...
Click to collapse
been there, tried that, after changing permissions they magically turn back and stay same as before:/
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
the first method worked great for me
thanks
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
I tried both without success.. What explorer are you using? I tried with ES and got an error "the operation failed".. and I couldnt change permissions neither
thanks for any help
Are you rooted?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
blazeplacid said:
Are you rooted?
Click to expand...
Click to collapse
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
karacc said:
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
Click to expand...
Click to collapse
You go to the setting of ES,then at the bottom of setting menu, it has Root setting. Go there and checked all check boxes. If you can, that's mean your KF is rooted.
Sent from my KFTT using xda app-developers app
tried method 1 and it worked right away :good:
Worked
Method 1 worked for me.
Thanks.
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Worked for me, too. Was surprised about the beautiful wallpapers to see now everytime i turn the thingy on
Adding a Boot Animation
Thanks for this info. I used the 2nd method and it worked immediately. Are there Boot Animations for the KFHD? Or can Boot Animations from, say my LG ICS Spectrum work?
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Awesome, confirmed working on kindle fire 2 running 10.2.1
frieked said:
Awesome, confirmed working on kindle fire 2 running 10.2.1
Click to expand...
Click to collapse
Thanks a lot for this :highfive:
Confirmed works on KF 8.9, thanks OP! I renamed to dtcp_apk.ads
finally, those horrific ad screens are gone! thank you sir!
if you have adb available, you should be able to do this without a root explorer.
use one of the following codes:
adb shell
su
mount -o remount,rw /system
mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.apk.bak
exit
exit
adb shell
su
mount -o remount,rw /system
chmod 000 /system/app/dtcp_apk.apk
exit
exit
adb shell
su
mount -o remount,rw /system
rm /system/app/dtcp_apk.apk
exit
exit
The first one will rename it. The second one will clear its permissions. The third one will remove it completely.
It should go without saying, but its not my fault if you screw something up, or if it is necessary to have this apk in your system, and you use the third method. I haven't tried it, but it should work. I do know what the commands do.
Didn't also work for me with es file explorer the first time i've tried it, although i've enabled all root options.
Rebooting the device helped me, but it's also important to make sure that you give the explorer the permission to change system data
Sent from my KFTT using XDA Premium HD app
Method 1 working
I tried it just out of curiosity and it worked right away. Using ES explorer, BTW.
Thanks!
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Thank you so much!!! Method 1 worked great. Also renamed the odex file to .odex.bat through root explorer. Note, in root explorer you will probably have to push the little 'Mount R/W" button once you get into system/app
Sweet. $15 saved.
Thanks for the quick 'how to'.
I'm rooted with tmobile unlocked usa phone, I was trying to edit things in build prop with root explorer and it doesn't let me do any thing, I even tried to use SQLite editor and it returns with database is currently used
- Open Root Explorer
- Root/system/build.prop
- Press 'Mount r/w' on top
- r/w should now be displayed on left, where r/o was previously displayed.
- Long press build.prop
- Press 'Open in Text Editor'
- Press the text line you want to change*
* Proceed with caution
- Take a look here in post #1 under 'Root Explorer Method' for more info.
(Step #4 will not apply regarding your inquiry.)
http://forum.xda-developers.com/showthread.php?t=1193245
Update/Edit:
See posts below.
I've included a screenshot.
The problem is Root Explorer does not allow you to edit text file more than 10kB.
If you have this problem, use ES File Explorer.
lrmdaddy said:
I'm rooted with tmobile unlocked usa phone, I was trying to edit things in build prop with root explorer and it doesn't let me do any thing, I even tried to use SQLite editor and it returns with database is currently used
Click to expand...
Click to collapse
mingkee said:
The problem is Root Explorer does not allow you to edit text file more than 10kB.
If you have this problem, use ES File Explorer.
Click to expand...
Click to collapse
Yes definitely use ES file Explorer for any build prop edits. Root explorer will not save any changes
Sent from my Nexus 5
ShapesBlue said:
Yes definitely use ES file Explorer for any build prop edits. Root explorer will not save any changes
Sent from my Nexus 5
Click to expand...
Click to collapse
Moved my post.
---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------
mingkee said:
The problem is Root Explorer does not allow you to edit text file more than 10kB.
If you have this problem, use ES File Explorer.
Click to expand...
Click to collapse
This is true
I edited my post.
ShapesBlue said:
Yes definitely use ES file Explorer for any build prop edits. Root explorer will not save any changes
Sent from my Nexus 5
Click to expand...
Click to collapse
thanks, sad for me to have to give up root explorer been loyal to it for at least 8 yrs.......but to my surprise es file explorer is easy to use and seems to work better....thanks for directing me to it.....
lrmdaddy said:
thanks, sad for me to have to give up root explorer been loyal to it for at least 8 yrs.......but to my surprise es file explorer is easy to use and seems to work better....thanks for directing me to it.....
Click to expand...
Click to collapse
I just use both. I use root explorer for nearly everything except build.prop edits
Sent from my Nexus 5