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!
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.
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....
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
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
Code:
ro.lge.proximity.delay = 150
mot.proximity.delay = 150
5) Save the file
6) Reboot
is this a permanent fix or what?
and how did u figure it out?
thx by the way
It should be permanent. Waiting to see will it stay fixed after rom update tho.
I did a lot of research, tried some apps but it did not work, and finally found this fix on some chinese forum.
mr_techno said:
1) Install File Explorer Root Browser
2) Go to System folder
3) Scroll all the way down and opet build.prop file
4) Add these 2 lines at the end of the file:
5) Save the file
6) Reboot
Click to expand...
Click to collapse
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
mr_techno said:
Well I did not have delay in my build.prop (using pixel experience plus rom) and so far, no more issues with the sensor. Maybe try and change it to 150? What rom are you using?
Click to expand...
Click to collapse
PE 10.
AFAIK the instable proximity sensor issue is due to a poor driver released in a Xiaomi firmware, nothing so easy to solve.
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Sentox6 said:
Just registered to say my formerly non-operational proximity sensor now works perfectly (Pixel Experience)! Thanks very much.
Click to expand...
Click to collapse
Mine too following the OP instructions ?
fox_xda2 said:
Delay is already set at 200 in build.prop. I doubt just changing the delay fixes much.
Keep us posted on the fix…ya never know
Click to expand...
Click to collapse
Worked with OP instructions.
Sent from my Redmi Note 7 using XDA Labs
Thanks, it worked perectly on PE 9!
Thanks a lot! Worked wonderfully on PE 9!
if this fix doesnt work and youve tried all kinds of "fixes" you may want to check out this if you have previously changed the screen or frame or had any hardware repair done to your xiaomi redmi note 7, there may be small peices you forgot to install. https://forum.xda-developers.com/redmi-note-7/how-to/fix-xiaomi-redmi-note-7-proximity-t4008965
Did it, seems that solved my problem to hear whatsapp audios outside in the sun. Ty
For now works like a charm in MIUI 11.0.3.0 Global, thanks.
:good:
Just want to say thanks for this fix. Works with PE10 with latest Delta update. For those who don't want root can uninstall magisk after editing build prop no problem at all
CR Droid 6.2 12JAN release. Nothing has changed unfortunately with this trick :crying:
Thanks. I am on Havoc 3.1 and the it fixed it.
Well, this can be included for sure, if y'all can let me know this actually works, I'd add the prop to the device tree. Thanks!
Hi, I want to disable the High volume warning, I already have a solution, right now I use terminal shortcut pro and have created a shortcut to run the command
Code:
settings put global audio_safe_volume_state 0
it work great but doesn't survive a reboot so I have to run the shortcut after every reboot. I found an old thread on reddit that say adding the line
Code:
audio.safemedia.bypass=true
to build.prop can also disable the high volume warning, but the thread was so old, they were talking android 6.0
I plan to try to add this prop on boot using the magisk module MagiskHide Props Config, I know it work great because I already added a prop to reduce the media volume steps to 15 instead of 30, but i dont know if the prop
Code:
audio.safemedia.bypass=true
is still working on android 10
Another solution would be to have an app that run the terminal command
Code:
settings put global audio_safe_volume_state 0
automatically after boot, but I would prefer to add the prop line if anyone can confirm it still work on android 10
Thank you all !
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
xe0r said:
Nice to know.... what's also wondering from time to time how to overcome the warning. let me know if you get it to a working solution.
Just for the last part: tasker would be the way to go.
Gesendet von meinem HD1903 mit Tapatalk
Click to expand...
Click to collapse
After 24 hours testing the audio.safemedia.bypass=true with MagiskHide Props Config, I have not seen the warning yet, but I need to test it longer to be sure it work
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved !
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
memocatcher said:
Hey one question, how were you able to edit the build.prop file? Whenever I try to do so with Root Explorer, it doesn't save my changes. OnePlus 8 Pro Android 10
Click to expand...
Click to collapse
Only with Magisk module MagiskHide Props Config
jacobyo7 said:
Just a quick update for future search, the prop
Code:
audio.safemedia.bypass=true
seem to work, I have not seen the high volume warning for the whole week, so problem solved!
Click to expand...
Click to collapse
Hello and thank you for finding a workaround for this stupid issue! Do you know if this is still working on android 11? After installing the module, how can I correctly set it? Thank you so much for your help
I tried setting it with termux but it's not working
addsfsds said:
I tried setting it with termux but it's not working
Click to expand...
Click to collapse
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
jacobyo7 said:
I still use it with 11 on my OP7T but I am unsure if this prop remove the audio warning or if there is no warning at all on my device. Never tried 11 wihtout the prop so IDK.
Another way you can try is the system UI tuner app on the play store, there is a setting to disable the warning under the audio & sound category. Good luck !
Click to expand...
Click to collapse
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
addsfsds said:
Thank you for your reply! I kept trying to no avail. Can't make it work unfortunately. When you upgraded to android 11, did you make the procedure again from scratch? Can you please explain what you did on termux?
Is the system ui app an app that it's aways on background?
Thank you so much!
Click to expand...
Click to collapse
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
jacobyo7 said:
No the system UI tuner app just change some hidden android settings, it do not run in the background. The description of the app even state you can delete the app once you changed the desired setting. Read the whole description to understand how it work. Try it, I think this might be the best solution.
SystemUI Tuner - Apps on Google Play
PLEASE READ ENTIRE DESCRIPTION BEFORE INSTALLING
play.google.com
Click to expand...
Click to collapse
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
addsfsds said:
Code:
settings put global audio_safe_volume_state 0
Thank you for your kind suggestion. I tried and again it didn't work, really don't know why.
Click to expand...
Click to collapse
i can confirm that no app does change the setting of safe volume limit.
All tests on rooted device from LOS14-LOS19. Tried different apps like systemuituner, safevolumelimitdisabler, volumesteps+, jamesdsp etc.
Tried to patch the global variable "safe_media_volume" like described here on a rooted device but no luck.
Just ran
[adb shell] settings put global audio_safe_volume_state 0
via adb, when the message popped up, afterits i had to confirm the nag-screen, to raise the volume. it's so weird..