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!
Related
DISCLAIMER: Please bear in mind that my flashing didn't end up perfect and I'm still learning. That said, we're just gonna be copying some files so I think it's kinda harmles to the phone. It worked for me, but it doesn't mean it will necessarily work for you, I post this because I think it's important that we share our experiences so we can learn from each other. Also I cannot guarantee that it will restore everything. In short what I mean is you do this under your own risk. This procedure was tested only on the following models. If you have success in other models please post back so I can update the list
Tested:
- Galaxy 551 (GT-i5510L)
- Galaxy mini (GT-S5570L)
1. Type *#272* IMEI # on your phone. In the little white box that appears on top there's a 3 letter code, that's your CSC code. Now hit the back button. (DON'T click "Install")
2. Go to /system folder and look for the file "CSCFiles.txt". To make things easier copy it to your sdcard and then download it to a pc so you can watch it during the procedure.
That file lists all the files that the phone uses to install a new CSC when you enter the code *#272* IMEI # so basically what we have to do is go through the system folders looking for those files and back them up in the sdcard or to a pc (your choice). Also back up with Ti Backup (just in case, you should always do a backup)
3. Flash.
4. After flashing go to the /system/csc folder. Inside this folder we have subfolders named with the codes of all the CSC included in the CSC file. What we need to do is create a folder with our CSC name (my case it was CTI) and then put all the files we backed up earlier in it.
5. Take your backed up CSCFiles.txt and back it up again, we're gonna be modifying it (TIP: if you're using Root Explorer for this process it makes a backup for you named CSCFiles.txt.bak).
6. Now we are going to tell android where the files are now so it can install them. Open your CSCFiles.txt for editing (note: I edited with Root Explorer, I just opened the file with windows Notepad to copy some sections for this post and it opened all in one long line, so it's probably not a good idea to edit it on windows) mine looked something like this
Code:
/system/media/bootani.qmg
/system/media/video/shutdown/shutdown.qmg
/system/media/audio/notifications/Claro.mp3
/system/CSCFiles.txt
/system/csc/contents.db
/system/csc/customer.xml
/system/csc/isnew_csc.txt
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/SW_Configuration.xml
/system/wallpaper/drawable/wallpaper_claro.jpg
/system/wallpaper/drawable/wallpaper_claro_small.jpg
/system/wallpaper/default_wallpaper/default_wallpaper.jpg
/system/app/LauncherMyfiles.apk
/system/app/YahooSearch.apk
/system/app/Plugger.apk
/system/app/MBO2_SMS_I5510L_CSBP_AMX_302.apk
/system/app/LauncherMessage.apk
/system/app/LauncherCamera.apk
/system/app/LauncherStk.apk
/system/app/CTI_Link.apk
/system/app/AMXNotification.apk
/system/app/LauncherCalendar.apk
/system/app/ASCR_SMS_i5510L_ML_AMX_301.apk
/system/app/LauncherContact.apk
/system/app/TopappMessage.apk
/system/app/LauncherMusicplayer.apk
/system/app/LauncherSettings.apk
you can tell there are some customized animations (with the operator logo) and sounds, then some bloatware and apps (which I didn't chose to restore) and then there are these files
Code:
/system/CSCFiles.txt
/system/csc/contents.db
/system/csc/customer.xml
/system/csc/isnew_csc.txt
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/SW_Configuration.xml
I only copied these files to the /system/csc/CTI folder we previously created and now comes the "tricky" part. You have to copy the files maintaining the path that the file says. i.e. the CSCFiles.txt goes into /system/csc/CTI/system/CSCFiles.txt then sales_code.dat goes in folder /system/csc/CTI/system/csc/sales_code.dat and so on. Then we have to edit our CSCFiles.txt to reflect these new paths so it will look something like this
Code:
/system/csc/CTI/system/CSCFiles.txt
/system/csc/CTI/system/csc/contents.db
/system/csc/CTI/system/csc/customer.xml
/system/csc/CTI/system/csc/isnew_csc.txt
/system/csc/CTI/system/csc/others.xml
/system/csc/CTI/system/csc/sales_code.dat
/system/csc/CTI/system/csc/feature.xml
/system/csc/CTI/system/SW_Configuration.xml
7. Finally if we've done eveything right when we type *#272* IMEI # our CSC will be listed and we can chose it, select it.
WARNING: THE FOLLOWING STEP WILL ERASE ALL YOUR PHONE DATA AND PERFORM A HARD RESET
8. Click "Install". The phone will shutdown.
9. Turn it on, an image of the little green droid with a box appears for a while and then the phone shuts down again. Just wait a little longer and it will reboot itself and presto!! You have your phone flashed and with your CSC restored!! (and hopefuly everything works out fine). Note that this time the reboot can take longer since it copies all the files before starting the OS.
This is my first Howto so any questions, comments, help will be greately appreciated and encouraged. I will try to answer if I can. Also if you try this on a different phone please tell me so I can start making a list with supported/not supported devices.
Finally!!!
Worked like a charm. I was able to restore the original CSC on my device and proceed with carrier updates. Thanks so much!
jmlowes said:
Worked like a charm. I was able to restore the original CSC on my device and proceed with carrier updates. Thanks so much!
Click to expand...
Click to collapse
I thought this post was dead. But I'm glad to see it helped someone!
Has anyone tested this on an i9100?
this should be sticky since there had been success and the OP did post proper tutorials...
swnt said:
Has anyone tested this on an i9100?
Click to expand...
Click to collapse
So far, I have only tested it with Galaxy GT-I5510L and Galaxy GT-S5570L it "should" work in other models if they maintain the same csc file/folder structure. If anyone tries this and it works for another model please post back results and I'll update first post
Very helpful !! Must be a sticky
Finally!!!
Hey! I tried this method with my Galaxy y 5360L and it works perfectly...
THANKS!!!
Pir8 said:
Hey! I tried this method with my Galaxy y 5360L and it works perfectly...
THANKS!!!
Click to expand...
Click to collapse
Glad it helped!
Veryy usefull, as many dumbs make faults in flashing.
But you could first explain to them what a CSC is
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Veryy usefull, as many dumbs make faults in flashing.
But you could first explain to them what a CSC is
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i think CSC mean country specific code
I have a little warning for this: the "contents.db" is actually an SQLite file, which contains the full path+name and the filesize of the CSC files. I think that this file should be edited when you change the path or the size of your CSCs. Screenshot attached
Thanks man! It really helps alot!
Hi :victory:
After seeing this mod on the news portal I wanted to change the carrier name myself, but unfortunately that was only for Verizon phones. So I looked through /system and found preloaded_config.xml which contained information on all carriers and I managed to change the carrier name (with some help from this app) And here's an easy guide how you can do it yourself!
1. First you want to download preloaded_config.xml and spn-conf.xml.
2. Open the files with a program like Notepad++.
3. Search for your carrier inside preloaded_config.xml. I had to search for "Tele2 NO" (remember capital letters). You will find something like this:
<preloaded-data mnc="07" mcc="240" operator-name="S COMVIQ" service-provider="Tele2 NO" service-provider-id="262">
Click to expand...
Click to collapse
4. The value mnc="07" and mcc="240" makes the number 24007 (put the first value behind the second). These values will differ for every carrier.
5. In spn-conf.xml, replace "XXXXX" with your new number. (For me it's 24007)
6. In spn-conf.xml you must also change what your new carrier name will be. (Replace "skifyr123").
7. Save spn-conf.xml and move it to /system/etc/. Reboot for changes!
And that's it. If it doesn't change be sure you found the correct carrier for your country!
An easier way is to use the app "Carrier Name": http://forum.xda-developers.com/showthread.php?t=901865 But it is reported that it doesn't work on all phones/ROMs. Working on Xperia S.
Nice!
Sent from my LT26i using xda app-developers app
it does not work on me. i did it b4 & now. nothing changed. show my original carrier name only.
im on 2.3.7
Thanks for your work!
Forget it, just saw you recommended it on the end.
Sent from my LT26i with Tapatalk 2
skifyr123 said:
Hi :victory:
After seeing this mod on the news portal I wanted to change the carrier name myself, but unfortunately that was only for Verizon phones. So I looked through /system and found preloaded_config.xml which contained information on all carriers and I managed to change the carrier name (with some help from this app) And here's an easy guide how you can do it yourself!
1. First you want to download preloaded_config.xml and spn-conf.xml.
2. Open the files with a program like Notepad++.
3. Search for your carrier inside preloaded_config.xml. I had to search for "Tele2 NO" (remember capital letters). You will find something like this:
4. The value mnc="07" and mcc="240" makes the number 24007 (put the first value behind the second). These values will differ for every carrier.
5. In spn-conf.xml, replace "XXXXX" with your new number. (For me it's 24007)
6. In spn-conf.xml you must also change what your new carrier name will be. (Replace "skifyr123").
7. Save spn-conf.xml and move it to /system/etc/. Reboot for changes!
And that's it. If it doesn't change be sure you found the correct carrier for your country!
An easier way is to use the app "Carrier Name": http://forum.xda-developers.com/showthread.php?t=901865 But it is reported that it doesn't work on all phones/ROMs. Working on Xperia S.
Click to expand...
Click to collapse
Tried it trough using the app, worked, rebooted, still Vodafone instead of my own name...
Looked trough Root Explorer, found in system/etc file spn-conf.xml, my name was there, and value was 20404 (the right numbers)
Am i missing something? Should i change it in preloaded_config.xml and and save it?
jdpieterman said:
Tried it trough using the app, worked, rebooted, still Vodafone instead of my own name...
Looked trough Root Explorer, found in system/etc file spn-conf.xml, my name was there, and value was 20404 (the right numbers)
Am i missing something? Should i change it in preloaded_config.xml and and save it?
Click to expand...
Click to collapse
Same here, although I noticed my carrier displays as 3uk for a few seconds before changing to 3.
No matter what I try it will not change.
Sent from my XperiaS via transwarp conduit.
works very good for me.. just be sure not to add symbols and caracters in the name such as :"
AND IF U USE ROOT EXPLORER BE SURE TO DELETE THE BACKUP FILE : spn-conf.xml.bak THE APPLICATION AND MOST OF SUCH APPLICATION CREATE BEFORE RESTART..
thanks
Perfectly working with VIVO Xperia S 4.0.4 MooDeD ICS 90.5
Your method and also the recommended apps in my Xperia Mini Pro doesn't work too=(
Does not work on my Razr xt910 226.3 ICS EU.retail
works on SGS2 4.1.2 stock rom
For what it's worth, this method works on my Samsung Galaxy S2, with stock JB.
I've added the following line to change my carrier's name to my custom text:
<spnOverride numeric="12345" spn_display_rule="SPN_RULE_SHOW_SPN" spn="mytext"/>
You'll need to replace the 12345 above with your carrier's MCC+MNC. Use the Network Info II app from the market to get that info.
Make sure to fix permissions and owner on the file after you copy it back to /system/etc.
Not working for Android 9.0 Pie Samsung
Hello everyone, I've an mt6575 based ics device and I'd like to tweak some part of it like the build.prop, and update it via the stock recovery. but my recovery has "everything" except the update option! can I update the said parts if that option was present?
The reason why I want to update the build.prop is because it has some bad lines in it, it says 240 ppi on this 800x480, 7" device! funny! and I also would like to root it if possible...
Any help regarding the said things (recovery, updating build.prop, rooting etc.) is highly appreciated.
Regards.
dakocha said:
Hello everyone, I've an mt6575 based ics device and I'd like to tweak some part of it like the build.prop, and update it via the stock recovery. but my recovery has "everything" except the update option! can I update the said parts if that option was present?
The reason why I want to update the build.prop is because it has some bad lines in it, it says 240 ppi on this 800x480, 7" device! funny! and I also would like to root it if possible...
Any help regarding the said things (recovery, updating build.prop, rooting etc.) is highly appreciated.
Regards.
Click to expand...
Click to collapse
It might come late, but build.prop is not neccessery to be updated, or edited trough recovery, simply, you need to have rrot premission, then use root explorer, or es explorer, navigate to /system and at the end of the scroll line you should be able to see buil.prop file, open it with text editor and change what you need. Another option is to copy it to sdcard and send to PC, where you can use Notepad++ (because regular notepad will stirr things up otherwise) and edit lines. This applies to all devices, but best is to backup your ROM trough recovery prior to doing this. And also you should know what lines you will change and what consequences are going to happen. Good luck
Okay, here's the problem. Actually: two problems.
1. There's an app, which contains some kind of root check to prevent installing the apk on a rooted device. This is the bigger one.
2. The apk can only be installed to specific devices. I believe this can be spoofed by editing build.prop.
But, I can't edit build.prop without root access, so I think the only solution is to find and remove the root check in the apk itself.
Is there anybody who can help with me that?
The apk can be found here: https://telekomse.srs.any.hu/apk/SRS_telekom_mobiltarca.apk
Any tips would be helpful. Thank you!
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.)