Hello.
Does anyone know how to change the product model number of A101?
I tried Captivate SGS Tools to modify "ro.product.model=" in "build.prop".
However, it doesn't work.
("ro.product.model=" doesn't exist in build.prop, don't know why.
I added by myself but every time I rebooted A101, it returned to the original status)
The reason I want to modify the model number is, some specific software restrict the usage only with specific phone models.
Thanks in advance!
what root method do you use?
what you want to do will only work with my root kernel/initramfs (+rw) or urukdroid
I used your method to root my A101
(Really thanks!)
However, I root without +RW.
If this can be done, I don't mind root using +RW again. Can you please tell me how to change model name?
Thank you.
you have to use +rw to make changes on build.prop file persistent. after you installed +rw you can edit the file again and reboot.
I edited the build.prop to get more apps on market (here)
Thanks!!!
I tried and it works! I can now edit build.prop!
Thanks!
I asked this in the general Q&A thread because I feel it is an android issue, not a Note issue...but alas no one even replied, trying it out here. Please help!
RockZors said:
Hello all,
I have a Samsung Galaxy Note i717. I have installed a few ROM's, but recently I installed CM9 unofficial build. After it was installed, I noticed that my default.prop is only like 4 lines long. So I try and add stuff to it (I am rooted, and used RW mode in Root Explorer). I can close the file and save changes successfully, but when I reboot it is back to the way it was with the 4 lines. It is not only that though, any files i add to the "/" get deleted upon reboot.
Things I have tried:
ODIN to stock rom, still did not have a full default.prop
Tried many different ways to change file system (different programs)
Ran fix permissions in CWM and busybox installer script
All with no success. Is there anything else I can try to fix this and be able to edit my "/" and have changes take affect. Or has anyone had this issue before?
Thanks
Click to expand...
Click to collapse
I was wondering if anyone with an i717 could go into cwm, run a backup, and upload that somewhere so I can restore it. Keep in mind your personal data gets backed up also, so preferably someone with a fresh working install. I don't care what rom it is either.
Thanks for reading.
The default.prop should only be 4 lines..
Are you confusing it with the build.prop?
Wow well don't I feel stupid. That's exactly what it was. Thanks for helping me see the way!
Hi guys, before I start I'll say that I have searched all over the internet and here on the forums and I couldn't find my particular issue. Well the thing is that I edited the line in my build.prop "ro.build.version.codename=REL" to "ro.build.version.codename=L" so I could get the material design on the Google Now Launcher pulled from a Android L build here's the thread I got that app: http://forum.xda-developers.com/android/apps-games/app-android-lollipop-apps-launcher-apps-t2912905
I did that and now my device will boot up normally then I will reboot by itself then show the boot animation then repeat the same process again and again until I force the phone to recovery or fastboot.
By the way my device is the LG Optimus G (E970) running GEE 3 ROM 1.2 and TRWP 2.6.3.0 and I have a backup of the original build.prop on my PC. I don't want to lose my data and apps since I forgot to make a backup (silly me).
I would like to know if there is a way to push the build.prop file on my PC to my phone so I could just replace it, or create a flashable zip.
Please help me, and thanks in advance.
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
question
AntonyOrtega said:
Nevermind. I managed to push the original build.prop file to /system set the correct permissions and now my phone is working again.
Admin feel free to delete or close this thread.
Click to expand...
Click to collapse
how were you able to do it when you couldnt get past booting.
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)
Hi There
I have been a long time Hacker of largely MTK devices. So I wanted to ask a question and see if there's anything I am missing here:
I have an Android 8.1 device, I have rooted it using Magisk no problem and I have successfully changed the bootanimation.zip and also the audio files. I have been able to release the rooted OS, get the OS back to a released state with the changes as I have simply kept the removed dm-verity flags that Magisk uses on the OS.
However, I am unable to change the build.prop at all.
If I copy the build.prop file from the device, edit it on the PC, and save it back it bootloops. If I edit it, roll back all the changes and re-copy it back to the device it is fine.
I noticed the original build.prop permissions are RW (Chmod 600). I tested the above chmodding to 600 and 644 and it makes no difference. If it has changes in it, it fails, if not it works!
So something somewhere is maybe checking the build.prop against an original and not liking it.
Is there anyone on here that could help shed some light on this at all?
Bump...Anyone?
So an update to this is that I have now successfully removed DM-Verity from this device. I have also managed this on many other devices. I prove this by installing all kinds of changes on the device.
So I can pretty much do anything with this device, almost like pre-Android 5.1, however whenever I edit the build.prop at all it bootloops.
What I have tried so far:
I have tried all kinds of permissions on the file
I have duplicated the /vendor/build.prop in an attempt to get round possible build.prop variety issue.
I have removed the /vendor/build.prop
I have replaced system/prop with original build.prop but still edited (and changed back) from my PC and the device boots OK.
So it looks like somethiung is looking up the build.prop file and checking something. Almost like a DM-verity for the build.prop.
Really out of ideas now. i can literally unlock/change anything MTK now except for this issue.
Any help is much appreciated.
Oh i forgot to mention, this is a systemless and not TREBLE OS.
I usually change /system/build.prop and have never had an issue up through Android 10. I know this is elementary and no intention to offend anyone - but are you sure the file is being saved with unix-style line endings.
File-permission must be set to 644.