Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
fishstick2k8 said:
Hello,
I've seen many threads implying that editing your build.prop file is simple, yet many other threads exclaiming that people have bricked their devices.
Has anyone successfully edited their SGH-T989/D phones to emulate the SGH-1337M? I have an odd reason, but I don't want to screw up.
Here is a link to the Galaxy S4 (I9500) build prop:
http://www.androidpolice.com/2013/0...gb-system-dump-leaked-and-ready-for-download/
Here is a link to the SIIx build.prop:
http://forum.xda-developers.com/showthread.php?t=1697142
How simple is this process? Which lines should I edit? What is your recommended editor app?
Thanks, I'd rather ask now than beg for solutions later.:fingers-crossed:
Click to expand...
Click to collapse
What exactly are you trying to do in the build prop to emulate the S4?
smokinjoe2122 said:
What exactly are you trying to do in the build prop to emulate the S4?
Click to expand...
Click to collapse
Maybe 'emulate' is the wrong word, but I am under the impression that I can swap the model number by changing the ro.product.model in the build.prop file. I want Google to think my SIIx is an S4 so I can access advanced apps that aren't optimized for my SIIx.
Here is a guide I found for simpletons like myself, but I just want to see if anyone else has done so successfully.
http://forum.xda-developers.com/showthread.php?t=1948558
I got impatient and changed the model number in the Build.prop and the phone did not brick. The System Settings on the phone does in fact confirm the updated model number as being SGH-1337M but the Play store hasn't updated the device yet so I can't confirm if my 'illusion' has completely worked.:laugh:
Get play store set correctly
http://www.howtogeek.com/116456/how-to-install-incompatible-android-apps-from-google-play/
looks like you done it all right except for the final step.
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Change permissions to rw
Sent from my MB855 using XDA Free mobile app
zzEvilGeniuszz said:
I changed my build.prop to make my LG L70 work with my Gear 2 watch. The watch got boring so I sold it, now I am looking to switch it back. I copied the original and tried to delete the modded one and it did not allow me. I tried to manually edit build.prop and it wouldnt save.
Any of you know how to revert?
Click to expand...
Click to collapse
yess...
if you have rooted your phone and then edited your build.prop with a change in android version....
then you have to root it again, and then go through the same process....
Related
I modified my build.prop to try and get Netflix to work, which failed. (Sadface.) Today I noticed that Swype has stopped working, searching on the error message it looks like yeah, it also checks ro.product.model or ro.product.manufacturer to make sure you've got the right phone for the version.
Anyways, like an idiot I accidentally deleted my backup build.prop. Turns out even a factory reset doesn't replace that file. So! I was hoping someone had a backed up unmodified build.prop and could quickly tell me what those two lines (ro.product.model and ro.product.manufacturer) read.
Thanks!
cspariah said:
I modified my build.prop to try and get Netflix to work, which failed. (Sadface.) Today I noticed that Swype has stopped working, searching on the error message it looks like yeah, it also checks ro.product.model or ro.product.manufacturer to make sure you've got the right phone for the version.
Anyways, like an idiot I accidentally deleted my backup build.prop. Turns out even a factory reset doesn't replace that file. So! I was hoping someone had a backed up unmodified build.prop and could quickly tell me what those two lines (ro.product.model and ro.product.manufacturer) read.
Thanks!
Click to expand...
Click to collapse
ro.product.model=SPH-D700
ro.product.brand=sprint
ro.product.name=SPH-D700
ro.product.device=SPH-D700
ro.product.board=SPH-D700
Awesome, thanks so much! Fixing the model line and rebooting resolved the Swype issue.
cspariah said:
Awesome, thanks so much! Fixing the model line and rebooting resolved the Swype issue.
Click to expand...
Click to collapse
Glad to help.
Similar Issue
KennyG123 said:
Glad to help.
Click to expand...
Click to collapse
I Need help with a very similar Issue; allow me to explain:
I rooted my Xperia E (C1504) using a C1505 Unbranded Kernel, during the process my build.prop was changed so that the device that shows in settings\about phobne is now C1505, i received an update from sony through update center and i can't install it, i'm guessing because of this issue, i was wandering if you could help me by providing this info so i can edit my build.prop and fix it.
Best Regards
Dr.Metalhead said:
I Need help with a very similar Issue; allow me to explain:
I rooted my Xperia E (C1504) using a C1505 Unbranded Kernel, during the process my build.prop was changed so that the device that shows in settings\about phobne is now C1505, i received an update from sony through update center and i can't install it, i'm guessing because of this issue, i was wandering if you could help me by providing this info so i can edit my build.prop and fix it.
Best Regards
Click to expand...
Click to collapse
You should ask for a copy of someone's build.prop by posting a question thread in this section http://forum.xda-developers.com/xperia-j-e/help
Thanks
KennyG123 said:
You should ask for a copy of someone's build.prop by posting a question thread in this section http://forum.xda-developers.com/xperia-j-e/help
Click to expand...
Click to collapse
Thanks, & sorry for being such a N00b =)
Dr.Metalhead said:
Thanks, & sorry for being such a N00b =)
Click to expand...
Click to collapse
Hopefully you will find more people willing to help...that is what we all should be here for.
So There are 2 JB TW roms posted on here that i see.. and after it becomes officially available, more roms will start to come out.. The old wallet fix for ICS WILL NOT work for Jellybean.. NFC will break and your phone will vibrate like crazy...
I dug through sprints latest leak and compiled a flashable zip file to make Google Wallet work... Tested on my end and it works!
The steps still apply from ICS versions
... open your buildprop in text editor and edit these fields..
ro product model ..... to -- Galaxy Nexus
ro product name...........to-- yakju
ro product device .......to -- maguro
save it...
Reboot into recovery... Flash the JMJellyBeanWalletFix.zip
reboot...
go to the playstore and download wallet....... You should be good to go..
Ignore the "unsupported device" message on the top... its saying this because the phone is rooted... everything works!
Nice job bro! :good:
Sent from my SGH-T999 with frosty jellybeans.
thank you... this was the only thing keeping me with aosp roms.. I use google wallet everywhereeee,.... well thats not the case nomore... im back on your rom!
joemagistro said:
So There are 2 JB TW roms posted on here that i see.. and after it becomes officially available, more roms will start to come out.. The old wallet fix for ICS WILL NOT work for Jellybean.. NFC will break and your phone will vibrate like crazy...
I dug through sprints latest leak and compiled a flashable zip file to make Google Wallet work... Tested on my end and it works!
The steps still apply from ICS versions
... open your buildprop in text editor and edit these fields..
ro product model ..... to -- Galaxy Nexus
ro product name...........to-- yakju
ro product device .......to -- maguro
save it...
Reboot into recovery... Flash the JMJellyBeanWalletFix.zip
reboot...
go to the playstore and download wallet....... You should be good to go..
Ignore the "unsupported device" message on the top... its saying this because the phone is rooted... everything works!
Click to expand...
Click to collapse
Been looking for this for a while
Thank You
thanx op and i can confirm it works on djintrigue808 latest build and wildchilds latest build.
Thanks for your work.
joemagistro said:
So There are 2 JB TW roms posted on here that i see.. and after it becomes officially available, more roms will start to come out.. The old wallet fix for ICS WILL NOT work for Jellybean.. NFC will break and your phone will vibrate like crazy...
I dug through sprints latest leak and compiled a flashable zip file to make Google Wallet work... Tested on my end and it works!
The steps still apply from ICS versions
... open your buildprop in text editor and edit these fields..
ro product model ..... to -- Galaxy Nexus
ro product name...........to-- yakju
ro product device .......to -- maguro
save it...
Reboot into recovery... Flash the JMJellyBeanWalletFix.zip
reboot...
go to the playstore and download wallet....... You should be good to go..
Ignore the "unsupported device" message on the top... its saying this because the phone is rooted... everything works!
Click to expand...
Click to collapse
Fan-freakin-tantistic! Do we change the build.prop file back after getting Wallet up and running? If so, can you please post the steps, etc? Really appreciate your work!!
For those who wanted AOSP MMS apk working with Jellywiz: http://forum.xda-developers.com/showthread.php?t=1921429
Thanks a ton for this! I went ahead and wrote a quick article on OMG!Droid to spread the news.
http://omgdroid.com/how-to-install-...ile-galaxy-s-iii-running-touchwiz-jelly-bean/
ShermCraig said:
Fan-freakin-tantistic! Do we change the build.prop file back after getting Wallet up and running? If so, can you please post the steps, etc? Really appreciate your work!!
Click to expand...
Click to collapse
It wouldn't hurt to try, but I think if you change the build back to stock, wallet will relock and FC saying that your device isn't supported
Sent from my galaxy nexus using Xparent Purple Tapatalk 2
Wow... posted in wrong forum. Its too early. Sorry guys.
thank you soooo freaking much!! I've been wanting to try out the NFC payment thing since i got my GS3. Now, i can officially look cool infront of the cashiers, and show off to my sad friends who have an iphone
Great job.
if you want to go back to the original buildprop use the modaco fixed google wallet from the att forum.
and turn of automatic update for the google wallet in the playstore.
In that way you can go back to the original build prop when everything is installed.
Works perfect for me.
Thank you again
Downloaded patch, set to Galaxy Nexus. Installed Wallet from play store and it installed but says that "Google wallet is not yet available for your device or mobile network." Wonder if new version (Oct 3rd) looks to see what network you are on.
chewwy420 said:
Downloaded patch, set to Galaxy Nexus. Installed Wallet from play store and it installed but says that "Google wallet is not yet available for your device or mobile network." Wonder if new version (Oct 3rd) looks to see what network you are on.
Click to expand...
Click to collapse
Did you change your build.prop? The 3 different lines I mean and then rebooted?
if not you have to do that otherwise it won't work.
where can i find my buildprop file?
Looking with my root explorer but cant find anything called buildprop. I'm on liquidsmooth. Just looking for a little guidance. Thanks!
saytj1 said:
Been looking for this for a while
Thank You
Click to expand...
Click to collapse
joemagistro said:
So There are 2 JB TW roms posted on here that i see.. and after it becomes officially available, more roms will start to come out.. The old wallet fix for ICS WILL NOT work for Jellybean.. NFC will break and your phone will vibrate like crazy...
I dug through sprints latest leak and compiled a flashable zip file to make Google Wallet work... Tested on my end and it works!
The steps still apply from ICS versions
... open your buildprop in text editor and edit these fields..
ro product model ..... to -- Galaxy Nexus
ro product name...........to-- yakju
ro product device .......to -- maguro
save it...
Reboot into recovery... Flash the JMJellyBeanWalletFix.zip
reboot...
go to the playstore and download wallet....... You should be good to go..
Ignore the "unsupported device" message on the top... its saying this because the phone is rooted... everything works!
Click to expand...
Click to collapse
Tight job homie! Needed this to flaunt in my friends' faces....they have iPhones lol.
scottslc said:
Looking with my root explorer but cant find anything called buildprop. I'm on liquidsmooth. Just looking for a little guidance. Thanks!
Click to expand...
Click to collapse
Under /system folder.
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
peterkef said:
Did you change your build.prop? The 3 different lines I mean and then rebooted?
if not you have to do that otherwise it won't work.
Click to expand...
Click to collapse
Ya, I was being stupid! missed a line.
thanks.
ok, i feel like a newbe goof but...
I found the build.prop file. I can open it but can't edit it. When I try my phone says it's a file system read only file. More guidance please...
scottslc said:
I found the build.prop file. I can open it but can't edit it. When I try my phone says it's a file system read only file. More guidance please...
Click to expand...
Click to collapse
You need to mount it as R/W.
In root explorer there should be a button at the top that says mount r/w.
Well I got the lollipop at&t 4g lte icon product name from TEKHD and it works good and i noticed it also takes off the sfinder and quick connect.
If you guys wanna try it out you need build.prop and edit this two lines and reboot.
ro.product.name=trlteuc
ro.product.device=trlteatt
All I had to change was product.name=to trlteatt nothing else unless your on Canadian firmware
This has actually been posted and discussed before in several forums. You can also try
trltevzw - verizon
Trltespr - sprint
Trltexx - international
And a few more that I can't think of right now.
do I need to be rooted to do this? i tryed but it is read only.
Build.prop editor works best with root.
Is there a wat I can get the LTE icons and kill "ATT" like in Gravity Box. I'm on TEK rom and love it, but the carrier text tweak is not killing the "ATT"
One thing that tripped me up was the persistent gap in the layout. In a Doh moment I figured out it was the spot for the download booster ucin, typically shut off.
Working, thanks a lot. All i changed was product name too
Has anyone figured out how to get this to work on 5.1.1 roms?
blane3298 said:
Has anyone figured out how to get this to work on 5.1.1 roms?
Click to expand...
Click to collapse
x2 on it.....it seem that with 5.1.1 update it is not anymore possible to make these change.....
zxaz said:
x2 on it.....it seem that with 5.1.1 update it is not anymore possible to make these change.....
Click to expand...
Click to collapse
Along with the build prop edits you must also change the sale_code.dat file in the csc folder from tmo to att. Works on the latest Tek rom. I'm using one from a stock Att Rom, but editing the file with file explorer, etc..may work as well.
I'd like to see screen captures of the different logos....they may all suck? LOL
bigron77 said:
Along with the build prop edits you must also change the sale_code.dat file in the csc folder from tmo to att. Works on the latest Tek rom. I'm using one from a stock Att Rom, but editing the file with file explorer, etc..may work as well.
Click to expand...
Click to collapse
i can confirm that"s it work perfectly on 5.1.1 stock rom.......bigron77 your the man!! after 6 month you finally solve the mystery...lolll
zxaz said:
i can confirm that"s it work perfectly on 5.1.1 stock rom.......bigron77 your the man!! after 6 month you finally solve the mystery...lolll
Click to expand...
Click to collapse
Does changing these files have any effect on anything other than just icons? Would changing tmo to vzw affect any other things because of gsm/cdma differences?
on my side, i have a sm-n910w8 wich is a canadians version....it worked perfectly!! i alway liked to have the carrier id on the status bar (i"m a rare one i guess loll) it didn"t change anything about the gsm/cdma thing...
well....have installed marshmallow on my note 4......have tested to see if we still able to change the data icon...and onm my side on stock rom android 6 i"m not able anymore to change anything....i change the ro.product.name and the sale_code.dat and it change nothing???? somebody have tested it to see???
thanks.......
Is this possible with MM 6.0.1 n910t?
Sent from my SM-N920G using XDA-Developers mobile app
should have made an update since my last thread......i"ve marshmallow on my note 4...you can"t change the build.pro to have for example the at&t data icon since marshmallow is still not available for the note 4....this is why the build.pro change mod doesn"t work......
Well.....saw that att upgraded finally the note 4 to marshmallow....have made a trie to have the att data icon by the build.prop.....it didn't worked.....maybe i made something wrong?? Someone had succes to make the change?
Thanks in advance.........
mr pnut said:
Well I got the lollipop at&t 4g lte icon product name from TEKHD and it works good and i noticed it also takes off the sfinder and quick connect.
If you guys wanna try it out you need build.prop and edit this two lines and reboot.
ro.product.name=trlteuc
ro.product.device=trlteatt
Does this work for the new bootloader mm?
Click to expand...
Click to collapse
mbr007 said:
mr pnut said:
Well I got the lollipop at&t 4g lte icon product name from TEKHD and it works good and i noticed it also takes off the sfinder and quick connect.
If you guys wanna try it out you need build.prop and edit this two lines and reboot.
ro.product.name=trlteuc
ro.product.device=trlteatt
Does this work for the new bootloader mm?
Click to expand...
Click to collapse
it didn"t work on mine....stock marshmallow rom
Click to expand...
Click to collapse
hey guys,
this might be a more broader android question, but either way: is there a way to change the hardware device name of a device?
i.e. my issue is the following - i use the "good for work" application for my work emails. My company basically has every manufacturer added to their approved list (HTC, Samsung, even Nexus devices work no problem). Now that I have my sweet OP3, I get the below error message (pic attached)
"the device hardware version is 'oneplus a3000 android 6.0.1' and is not permitted. Install the application on a permitted device."
now - before you tell me to go to my network admins and have the device added - I can't do that for reasons I won't go into here. Basically i want to understand if there's a way to change certain files on the phone that will make this application think it's a nexus device and clear it.
I tried editing the build.prop file (using twrp and adb - since I don't have root) to remove all mention of oneplus, etc. and replacing with "nexus" or something else (used the build.prop file from my 5x for reference). But the app still does not work and the OP3 still shows the model as One Plus 3 in the "about phone" section. This is really fascinating to me. What is driving this device's identity?
Appreciate any thoughts/suggestions you might have.
Try xposed mods... I think it is possible
Wrong forum.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
wrong section.
post this in Q&A
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Go to your Bluetooth settings, select the menu, and Rename this device.
JumboMan said:
@piotrus22, If you correctly modified your build prop then it's almost impossible to come as Oneplus name in about section of setting.
as far as I know the name in about section is read from build prop.
can you provide link to your modified build.prop file so i can see what's a problem.
Have you applied correct permissions (rw-r--r-- or 0644) to build prop after side loading
Click to expand...
Click to collapse
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
piotrus22 said:
thanks @JumboMan. attached are both build.props (edited and non-edited). I ran the command "adb shell chmod 644 /system/build.prop" after I pushed the file onto the phone. I believe it worked because I added the line about LCD density (ro.sf.lcd_density=420) and the density did indeed change. Also - I am able to view the updated build.prop in a file browser when I open the phone with the changes I've made.
...still confused...
Click to expand...
Click to collapse
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
JumboMan said:
I have carefully inspected build.prop file and i found that build.prop doesn't have "ro.product.model" line . That's why you are not able to change device name.
So if you have to change device name you have to manually add above line with whatever device name you want and push file to phone and apply proper permissions
e.g ro.product.model=device name you want
In your case above line will look like ro.product.model=Nexus 5x
Though not required,change lines containing OnePlus to your custom device name
Click to expand...
Click to collapse
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
piotrus22 said:
ok - making progress here. the model name now shows up as Nexus 5x, but when the computer recognizes the phone it still shows up as ONEPLUS A3000... and what about the build? I've tweaked everything I can think of but still can't change the build number from "ONEPLUS A3000_16_0705"
any ideas?
Click to expand...
Click to collapse
now I think I'm going out of ideas.
I think you have to ask some experienced dev
JumboMan said:
now I think I'm going out of ideas.
I think you have to ask some experienced dev
Click to expand...
Click to collapse
how do I do that? just hope one of them sees this post? LOL
piotrus22 said:
how do I do that? just hope one of them sees this post? LOL
Click to expand...
Click to collapse
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
JumboMan said:
Yesterday I researched a lot about your question but I only found half answer.
Now Today I'm back with more build prop lines that will 100% solve your question.
This time I tested myself first before posting to confirm the changes
So here is a Trick
=====
1.To change Model Number
ro.product.model=Nexus 5x
2.To Change Build Number
ro.build.display.id=Nexus 5x
ro.build.display.full_id=Nexus 5x
ro.build.id.hardware=Nexus 5x
=====
Note - value "Nexus 5x" is used just as an example.
You change this value to anything you want.
Click to expand...
Click to collapse
you sir are amazing. just tried it and it worked. will test it out to see if it causes other issues. may I buy you a beer?
piotrus22 said:
may I buy you a beer?
Click to expand...
Click to collapse
For me Thanks=Beer, so thanks are sufficient
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
piotrus22 said:
Ok @JumboMan, so now my phone won't save video. Basically when I try to take a video with the camera app, it hangs up on the "saving" section. Then the only way to get the camera running again is to reboot. I can't believe this is related to what I did in the build.prop files right?
Click to expand...
Click to collapse
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
JumboMan said:
It may be due to build prop changes but I'm not sure. can you use 3rd party camera app check for your problem. or it only occurs with stock camera.
Click to expand...
Click to collapse
Third party camera app has the same problem. Will revert to original build prop and see if that fixes the issue. Will report back.
JumboMan said:
For me Thanks=Beer, so thanks are sufficient
Click to expand...
Click to collapse
Dethfull said:
The driver names will ever be the real device name. So...
:thumbup:
Sent from my XT320 using xda premium
Click to expand...
Click to collapse
@Dethfull do you know which items in the build prop coordinate to the drivers for the camera?
ok so I think I fixed it. I played around with the build.prop file and it appears changing the ro.product.manufacturer =OnePlus back from Nexus5 did the trick. Camera seems to be much faster than before and videos can save now, and the Good app still works.
Will update if things change but hopefully not!
I was trying to edit the build.prop of my galaxy s5 to fake the device info, but the ploblem is that under ro.product.model stands for default =klte and if I change it there is no effect in the settings even after trying the method with the console. And no I'm not to stupid to edit the file cause everything else works fine (I tried the android version fake). So is there any help? My idea is that it has something to do with lineageos cause on other tutorials there stands always the model number for example SM-G960F and not like in my file klte.
Aladie said:
I was trying to edit the build.prop of my galaxy s5 to fake the device info,..........
Click to expand...
Click to collapse
I don't have this variant but, your best bet is to post this question within one of the following threads that's specific to your device and Firmware.
https://forum.xda-developers.com/showthread.php?t=3476433
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
Sent from my SM-G900V using The ClaRetoX Forum App.
Nougat is inherently difficult to edit system files in order to keep you safer from being hacked.. your best bet is to either make a flashable for use in recovery or use terminal in twrp itself to edit the file before reboot
Sent from my Moto E (4) Plus using Tapatalk