Hello,
I'm trying to change the info displayed in my Model Number in "About phone" in Settings.
I have edited build.prop and even used XPosed with Device Faker. It does display the new Model Number in XPosed or any other application but when going to "Settings --> About Phone" , it still displays the original name, which is grayed-out and it's bugging the hell out of me, the fact that I can't change it.
Does anyone have an idea of what I can do, short of flashing a custom ROM?
I'm using stock ROM and rooted.
What are you editing it with, a build.prop app? I normally used root explorer and have never tried any of the apps for that. I'm guessing they do ask for root privileges and you change the system to write to make the changes and back to read only after the changes?
I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings
UzY3L said:
I tried with XPlore, ROM Toolbox and finally with build.prop editor.
The changes are saved and they reflect in any app that reads from the build.prop file.
However, the Model number stays the same in About phone, in Settings
Click to expand...
Click to collapse
Did you search the entire build.prop? It's possible that the name could appear more than once.
Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.
UzY3L said:
Yup, searched and also read it all, lots of times.
It does import some data from oem.prop I think but I checked that and it has nothing related to Model number or device name.
This is very weird and irritating. I tried messing with some more info in build.prop but the phone stopped working so I had to flash the stock firmware again.
Click to expand...
Click to collapse
In my phone settings, in the "software channel" part....mine shows "ATTMX". Is it possible to edit that to show something else??
If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app
rbeavers said:
If your rooted get BuildProp Editor in play store.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did that. Doesn't work. Motorola went to a lot of trouble to stick that model number there for good. I wonder why?
Doesn't matter anymore. I bought an LG G3. Same size, same battery, much better specs, less battery life. An acceptable tradeoff.
Thank you all for your answers!
Related
Been trying to access some info from the "My Account" app and says my phone model is not supported. I think its due to the change in model number in the about phone section. Anyway to change it back to what it was before?
Btw im running CM 5.0.8
Edit: Reason for editing: On the "Model Number" part, its says HTC Dream, I wanted to change the text string back to what it use to be so I fully use the my account app.
old post, but I would like to know where/what I need to do to change the model also. I can't update via my sammy i9000 via Kies, because it's reading as a GT-I9000 after installing a Euro 2.2 ROM, when it's infact a GT-I9000T.. which Kies now has a New Zealand 2.2 update for. The issue is the 3G support of the Euro ROM and the fact it makes my screen on first power up do the rainbow snow deal. I'm hoping the NZ ROM for the actual 9000T will fix this... but I need to change the device model # to test.
The Kies registry patch trick didn't work for me at all. I would run the app, it would appear to change the registry keys, but Kies would either add another set of 3 keys (4, 5, 6) or just change the 1, 2, 3 modified reg keys to what the phone is reporting instead of keeping the modified info.
Any help would be greatly appreciated
/system/build.prop
i am carllindsay, i was surfing to know that, thanks for sharing a nice thread.
dhkr123 said:
/system/build.prop
Click to expand...
Click to collapse
How do you open /system/build.prop? I use ASTRO and can't open it. Is there any editing app that can open any extension?
general-tso said:
How do you open /system/build.prop? I use ASTRO and can't open it. Is there any editing app that can open any extension?
Click to expand...
Click to collapse
You could rename it to .txt, edit, change to .prop.
Or you could adb pull, edit, push ect.
never mind. I have SGS Tools app that lets me edit /system/build.prop without renaming it. SGS Tools is available on the Market for free.
for those who don't know what SGS Tools is, you're missing a lot! Try it.
general-tso said:
for those who don't know what SGS Tools is, you're missing a lot! Try it.
Click to expand...
Click to collapse
For anyone who actually knows how to use a computer.... no, they're not missing ANYTHING. The terminal is FAR more powerful than any nonsense like that.
does anyone know how to get to Qualcomm USB Settings. *#7284# doesn't work.
Thanks
brianrent said:
does anyone know how to get to Qualcomm USB Settings. *#7284# doesn't work.
Thanks
Click to expand...
Click to collapse
Are there no secret codes for this phone?
Nevermind.
For those interested I followed the instructions here
Didn't work the first time with lower case "on" so I used uppercase "ON" and it worked.
brianrent said:
Nevermind.
For those interested I followed the instructions here
Didn't work the first time with lower case "on" so I used uppercase "ON" and it worked.
Click to expand...
Click to collapse
Did you have any issues writing to /efs/carrier from Root Explorer? Every time I try it says the write failed. I even changed the permissions on the folder to 777 and that didn't help. I also tried to push the file from ADBGUI and that didn't work either.
Worked for me just fine. just had to hit read write button at the top before I used notepad or whatever is called to edit it.
Sent from my SM-N900V using xda premium
I don't know if it matters or not but my phone is rooted.
Sent from my SM-N900V using xda premium
Okay, I got the file changed but I cannot get the menu to pop up. I'm just supposed to go to the dialer and type in *#06# and something is supposed to pop up, or am I supposed to hit the dial button?? It just tries to call and I get the default Verizon message that the call can't be completed as dialed. Also, I tried the "intent" shortcut method and when I try to run it, it says "Application not Installed" I've verified that I do have HiddenMenu.apk in my /system/app folder. Not sure why this isn't working for me. My phone is rooted, but I am running the stock Verizon build.
Any help would be greatly appreciated.
ephreet said:
Okay, I got the file changed but I cannot get the menu to pop up. I'm just supposed to go to the dialer and type in *#06# and something is supposed to pop up, or am I supposed to hit the dial button?? It just tries to call and I get the default Verizon message that the call can't be completed as dialed. Also, I tried the "intent" shortcut method and when I try to run it, it says "Application not Installed" I've verified that I do have HiddenMenu.apk in my /system/app folder. Not sure why this isn't working for me. My phone is rooted, but I am running the stock Verizon build.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I did go into /system/app folder and clicked HiddenMenu.apk and installed it but that was before i made the change to capital letters for the "ON" edit. Not sure if that mattered or not. You dont need to hit send, it will work after you hit the last # if it is working.
ephreet said:
Okay, I got the file changed but I cannot get the menu to pop up.
Click to expand...
Click to collapse
I got mine just by editing the text to "ON" with root explorer text editor... never touched hiddenmenu.apk
did you reboot after editing text?
It's just one thing I tried before it finally worked but as I said don't know if it's necessary and probably its already installed if it's in that folder. I'm glad it worked for someone else though.
Sent from my SM-N900V using xda premium
In case anyone was wondering some of the NV Items are WRITE PROTECTED so even though "NV-items_reader_writer.exe" will say "successfully written" some items such as 550 it will not overwrite the info and no change will take place.
Just out of curiosity, what does this hidden menu give access to?
beamed from transporter room 3
It gives you the ability to change USB settings so you can use tools to edit NV item entries. One of which is 550 which is your imei number in case flashing screws up your imei. Also you can backup your entire EFS.
Sent from my SM-N900V using xda premium
Not sure if this is the right thread !
I want to back up my EFS. I screwed up my S4 and want to be careful this time. Is there a tool or tutorial for Verizon Note 3 ?
If *#7284# doesn't work try *#0808#
Hi all,
Some time ago, I was troubleshooting one of the many ossues I have had with my phone. During the troubleshooting, one of the steps was to change the Note 3 model number to that of an S4. That would have effectively resolved the issue.
Now some time has passed, and having the phone identified as an S4 is causing other problems. I cant find the original thread though, and I cant remember which file I changed.
I remember going into Root Browser, and looking up a file. I opened the file in text editor, and changed SM900W8 to SMH I337 or something like that.
Anyone know where that file is? I need to change my model back because of compatibility issues
4DM said:
Hi all,
Some time ago, I was troubleshooting one of the many ossues I have had with my phone. During the troubleshooting, one of the steps was to change the Note 3 model number to that of an S4. That would have effectively resolved the issue.
Now some time has passed, and having the phone identified as an S4 is causing other problems. I cant find the original thread though, and I cant remember which file I changed.
I remember going into Root Browser, and looking up a file. I opened the file in text editor, and changed SM900W8 to SMH I337 or something like that.
Anyone know where that file is? I need to change my model back because of compatibility issues
Click to expand...
Click to collapse
/system/build.prop?
Yep! That's exactly what I was looking for. Thanks!
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
redsmith said:
Today I found something really strange about builds LMY47E and LMY47D. I had been running 47D since last week with a DPI of 520, which was adjusted using Root Explorer in the build.prop. After trying to do the same in 47E, rebooting my device would display the "Android is upgrading... Optimizing app 1 of XXX" screen, and make it bootloop after optimizing the last app, displaying the same screen and optimizing my apps again and again.
After many hours trying to isolate the culprit, I found that to properly change DPI In 47E, one has to edit the build.prop lcd density AND use "adb shell wm density XXX". That's the only way I've made sure my device reboots properly.
I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
antiochasylum said:
I just changed it with root explorer. I didn't have any issues.
Then again I stayed within the default density's from my past devices.
Nexus 6 is 560, I went to 480.
Click to expand...
Click to collapse
That's weird. Mine would survive a couple of reboots but after that, bootloop fest.
I'll keep an eye on this issue anyway.
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
krazekid007 said:
I just went through this on 47E. It was bad but it turns out that you only need to do "adb shell wm density XXX" and not edit the build prop. Editing the build prop sent me through the bootloop
Click to expand...
Click to collapse
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
Still get glitches even after rebooting?
Lol, I'm so glad someone brought this up. Thought I or my phone was going nuts!
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
A2CKilla said:
All I've ever done is change the build.prop, no adb stuff, never had issues...for all builds
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It lasts for a few days sometimes.... Usually after a reboot or 2 its gameover.. It'll usually let me reboot 2x before looping .. If I don't reboot it'll just randomly turn off and then..well.. Loop
Not the only ones with this issue... here's what I have found even with "D" & "E" working with the group trying to port the Blinkfeed Launcher from Sense 7 which requires a DPI change to work correctly on the Nexus 6.
532DPI use to work with 5.0.1 & 5.0.2... No longer the case for any 5.1 build (haven't tried "M" build yet) which is the perfect setting for Blinkfeed Sense 7 Launcher....
I am using 520 right now... other experience issues with the bootloop at 520... I have found a way to test:
1. TWRP backup current good DPI setting... Backup up everything cache, efs, system, data, etc.
2. After TWRP backup, boot up and apply the new settings you wish to test. Apply then completely power off.
3. Power on and boot up. If no optimizing apps issues, you have passed step one.
4. Now TWRP backup your new settings, backup everything, reboot system. If no bootloop, then you should be golden
I think it is something in the code to streamline how it handles graphics... however it seems that what is acceptable varies from phone to phone. Most see good results staying with factors of 40 & 80 while others can do even factors of 20....
Don't think anyone has figured out root cause entirely..... I really like to know why I could 532 before and can't now???
Yea 532 was my buttah
redsmith said:
The thing is, if you only do "adb shell wm..." you will get weird graphical glitches, especially in the keyboard. So far, I've managed to avoid them by editing build.prop too.
Click to expand...
Click to collapse
So were you able to successfully change your DPI by editing the build.prop?
I had to do adb shell trick too, otherwise, bootloops.
Build.prop edit LCD_density
redsmith said:
. . . . . I think this is really weird, since 47D and 47E are supposed to be identical. Does anybody have any clue about this?
Click to expand...
Click to collapse
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
NLBeev said:
Started with rooting 5.0.1. Then edited build.prop with 'build.prop.editor and changed the LCD-density to 493.
Because the native resolution is of the N6 screen is 493.
After upgrading to LMY47D the DPI value was 520 (0r 560?) again. I edited this value 'ro.sf.lcd_density' and set the value to 384.
With that value the N6 is in tablet mode.
After rebooting the value of 'ro.sf.lcd_density was 384, but the display was not different.
In the Build.Prop editor there is a menu item called Build.Prop Tweaks. In the Tweaks-list the entry 'LCD Density' was missing.
I did not have a backup of the build.prop file so a full restore in recovery was needed to correct this.
The Build.Prop editor has an option to create a backup. Use this option first before editing.
Now for about a week with 47D and DPI 384 and font size to huge, the N6 works fine. (Stock, rooted, encrypted).
Remark.
Because the N6 has a amoled display it's a bit strange that the name 'ro.sf.lcd_density' is used.
Click to expand...
Click to collapse
whojabacod said:
Yea 532 was my buttah
Click to expand...
Click to collapse
krazekid007 said:
So were you able to successfully change your DPI by editing the build.prop?
Click to expand...
Click to collapse
redsmith said:
I had to do adb shell trick too, otherwise, bootloops.
Click to expand...
Click to collapse
I don't believe there is any rhyme or reason to it bootlooping... something is definitely different in the programming in 5.1... tried everything last night to get 532DPI to stick.... build.prop.... adb command... tried them all... would reboot 1 time ok, second time "op apps" bootloop. this was not the case with 5.0.1 or 5.0.2... I remember tweaking the dpi by 2 up and down to find a perfect dpi for a Blinkfeed launcher port on 5.0.2 and never had this issue. It is either something Google did on purpose for this build or on accident. Either way, we are kind of screwed until someone smarter than I can put a finger on as to what is causing this... I just think 5.1 was rushed to get VoLTE out there for the Verizon release...
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
NLBeev said:
When your N6 is bootlooping in 5.1. And you can't find the cause and/or a solution then you could decide to go back to the factory settings including unroot. This can be done easily with the toolkit of Wugfresh.
I did that and I am using now 5.1 (47D) and edited buil.prop. DPI set to 384.
Click to expand...
Click to collapse
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
SilkyJohnson said:
Or you can just fastboot flash system.img and save time and your data. It's what I did on a DPI bootloop.
Click to expand...
Click to collapse
Let's hope for him.
NLBeev said:
Let's hope for him.
Click to expand...
Click to collapse
No need to hope - it works. I did it.
Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks
bluenote73 said:
Hi guys
So I recently updated to B25, and suddenly, I'm faced with the camera breaking if I edit my build.prop. All I'm doing is adding ro.config.media_vol_steps=30
I'm using buildprop editor from the playstore.
Even if I go in and remove the entry, or change the entry to =14 (which I believe is stock, but I'm not sure) it doesn't fix my camera. So far, the only way is to reflash B25.
Can anyone tell me why this might be happening and how I can get around it? I am definitely not jazzed about having such coarse media volume steps!
thanks
Click to expand...
Click to collapse
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.
amphi66 said:
Added both media & call volumes steps to my B25 build.prop without issue. I simply made the change using the text editor in Root Explorer, tho, not thru an app.
Click to expand...
Click to collapse
Thanks. That worked for me. I don't know wtf is the problem with that build.prop editor I was using, but it worked flawlessly through the last 2 updates, but suddenly after B25 just seems to cause this problem right away.