hi, random question,
i went in and changed the build.prop file so that my model number would be t-mobile g2 and not htc vision but for an odd reason, my model number is now t-mobile g2ro.product.brand=tmobile and try as i might, i cant change it back, ive mounted /system, then i adb push a build.prop file (even an unedited one straight from cm7 rc1) unmount /system and then reboot, but alas, no change
could i possibly be missing a step?
kamontryst said:
hi, random question,
i went in and changed the build.prop file so that my model number would be t-mobile g2 and not htc vision but for an odd reason, my model number is now t-mobile g2ro.product.brand=tmobile and try as i might, i cant change it back, ive mounted /system, then i adb push a build.prop file (even an unedited one straight from cm7 rc1) unmount /system and then reboot, but alas, no change
could i possibly be missing a step?
Click to expand...
Click to collapse
Why would you want the model number to say that? It ***IS*** an HTC VISION!!!!
As for the next line getting pulled into the model name line, I bet you edited it with some garbage program, like windoze notebad and broke the file.
dhkr234 said:
Why would you want the model number to say that? It ***IS*** an HTC VISION!!!!
As for the next line getting pulled into the model name line, I bet you edited it with some garbage program, like windoze notebad and broke the file.
Click to expand...
Click to collapse
why? for my own reasons, ok so if notepad is bad then what program do i use?
That sound stupid cuz it is an htc vision and I don't think tmobile made the phone last time I checked ....at the store and rofl he did use nootpud use micrasuft wurdz no? Or wuurdpad XD
Sent from my T-Mobile G2 using XDA App
I would like to be able to do this too...
I for one think this is a legit issue. I would like to change the Model Number from HTC Vision to T-Mobile G2 or Desire Z or Nexus w/keyboard or mYdaMnBusinessWhAtIcallMyRoOtedPHone. Hey kamontryst, let us know if you found a solution.
Related
I'm in the US and just purchased one. Any idea how to identify?
pull the system and check the build.prop thats what i had to do? and ended up with the orange one!
Drizzy Drake Rogers said:
pull the system and check the build.prop thats what i had to do? and ended up with the orange one!
Click to expand...
Click to collapse
Kernel: 2.6.27
Build: 1.76.405.6
Can anyone help me? lol
Where is the build.prop file? Can we access it using a file manager (astro) or does it have to be done through ADB?
If ADB only, could someone please provide directions?
Breakthecycle2 said:
Can anyone help me? lol
Click to expand...
Click to collapse
What exactly are you trying to find out here? If it's an operator branded Hero, it will have... operator branding!
Regards,
Dave
foxmeister said:
What exactly are you trying to find out here? If it's an operator branded Hero, it will have... operator branding!
Regards,
Dave
Click to expand...
Click to collapse
Ahhh...mine isn't branded. Just says HTC
Actually, looking at the Orange website, it appears that Orange haven't applied any physical branding to the phone, whereas my T-Mobile unit has a T-Mobile logo on it.
What colour is your Hero? AFAIK, all Orange UK ones are graphite.
Regards,
Dave
rvashi said:
Where is the build.prop file? Can we access it using a file manager (astro) or does it have to be done through ADB?
If ADB only, could someone please provide directions?
Click to expand...
Click to collapse
ADB way:
> adb shell
# more /system/build.prop
Click to expand...
Click to collapse
cheers
Thanks for the instructions through ADB. Before I try that, I thought I'd give it a shot from Astro File Manager and it worked and I found the build.prop in the System folder.
Confusing though... Mine says its out of 'Rogers' and I know Rogers doesn't have the Hero. I wonder if Paul (Modaco) is using it on Rogers and since I have his ROM on my Hero, that's what it says...true?
rvashi said:
Thanks for the instructions through ADB. Before I try that, I thought I'd give it a shot from Astro File Manager and it worked and I found the build.prop in the System folder.
Confusing though... Mine says its out of 'Rogers' and I know Rogers doesn't have the Hero. I wonder if Paul (Modaco) is using it on Rogers and since I have his ROM on my Hero, that's what it says...true?
Click to expand...
Click to collapse
Yep I'd agree with your synopsis I too have used modaco's update and my build.prop also has rogers in it however it is in a commented out part of the text so will not cause us any problems so don't worry about it.
I am grateful to modaco for producing this rom as it a a hell of a lot better that the rom that the hero came with!!
suppose if you want the original build.prop you could take a nandroid backup, then restore your backup from before installing modaco's rom (that you should have taken) check then restore back to the first nandroid backup.
Then again are we trying to identify the hardware, if so I'm not sure the hero comes in different flavours (yet) apart from the sprint one which seems to quite different but still may have the same hardware.
Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person
can someone help pleaseee
aldog25 said:
Ok, Im trying to flashing my EVo 4G to boost mobile. Im following the guide that eljean posted. I got all the way up to step 5 on the guide and got stuck. Heres how im stuck it says to download autoroot w/2.15.00.11.19 which i did then it say make sure you have a sd card in your evo which I do. then it say to duble click autoroot.bat and i do... it starts and this is where i get stuck it look like it start rooting then it say the ADB shell does not heve root permissioms and then it say FAILED TO GET A ROOT SHELL PLEASE RESTART YOUR PHONE AND TRY AGAIN. can somebody plz help me it making me a very angry person
Click to expand...
Click to collapse
so you're trying to root? go here http://forum.xda-developers.com/showthread.php?t=1218386
..then go back to the original guide to complete
I did that i redownloaded all the auto root files and still when i go to autoroot.bat it still say the same thing does any of this matter? Im running Android ver: 2.3.3
Baseband ver: 2.15.00.05.02
Build number: 4.24.651 L61076 release keys
Software number : 4.4.651.1
PRI ver:1.77_003
On that guide i think it say it only work for Software versions 1.32, 1.36, 3.29, 3.30 & 3.70 and hBoot Version .76, .93, .97, 2.02 & 2.10 and how do i even find out my hoot version?
I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?
aldog25 said:
I just tried the autoroot quick method and it said unknown bootloader version. Bootloader is the wrong version. Is there anyway i can change my bootloader version?
Click to expand...
Click to collapse
Don't use autoroot, click the link i posted...use "revolutionary" Not autoroot
follow the link i posted line by line !!
NO AUTOROOT !
Thanks alot i got pass that step now lol im stuck one more time. Ok I found 9 msid's and zerod them and i found 11 esn's before i got done checking all the esn locations i had about 5 or 6 locations left to check but i didnt becouse it say theres only 9 meids and 11 esns, and now after i zero them all out and reboot my phone and press ##786# the msid and esn is not all zeros like it should say. What do i do now?
Hey louforgiveno do you have a messenger aol msn yahoo or anything if so leave your screen name and log on i be on asap thanks
I just downgraded to 2.05.00.06.10 and used the revskills to try and zero meid/esn i ended up with a log file how do i write this to QXDM now?
i must be missing something cause everywhere i see it no one replies to this question or there is no answer...
after removing 0 and 1943, i can't ever commit the **** to the DIAG TX item... the DIAG RX item takes it just fine. I have been trying and re-trying for hours... thanks
You need the version of qpst listed In the guide....double check your version
I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.
louforgiveno said:
You need the version of qpst listed In the guide....double check your version
Click to expand...
Click to collapse
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Dean_L said:
I used the EFS Explorer to add and extract the files. Edit of course with Winhex. I bet the file is not saved properly if you've done this already.
Click to expand...
Click to collapse
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?
woodz93 said:
I have 2.7 v366, one guide didn't have a number beyond 2.7, another guide lists v355...
Makes sense. when you drag files back do they have the same look as the ones already in there? What i do notice is that all the other files have a consistent modified date, and there is also a batch of files that show mod dates that are more recent and don't have the red line through them (they look like txt file images on a windows pc). are these temp files that are perhaps messing with writing the ****?
Click to expand...
Click to collapse
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.
louforgiveno said:
It's normal that they look different, don't know if you tried it yet, but you need to delete the 0&1943 from the phone before copying them back from pc.
Click to expand...
Click to collapse
i do delete them. but i also see a host of other files that are written on boot(or reboot), those are the ones i'm curious about. i also will downgrade qpst to 2.7.555 to see if that matters.
EDIT: Tried it to no avail. so infuriating... so close but so far...
EDIT: thanks to Klown80 - simple answer is it doesn't matter! there is a guide floating around that says it does, i just happened to end up with it. thinking that it was logical i wasn't going to deviate until i got it right... so unnecessary. so there it is, for those of you who are stumped by this issue...
Anyone know how we can change this text? XML location?
This rom gives you the option to personalize the carrier text AOKP V9
Sent from my Galaxy Nexus using Tapatalk
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Tag, looking through the framework for this and other tweaks are on my lst for this weekend.
nachtschicht said:
Push spn-conf.xml to /system/etc
http://www.multiupload.com/Y2NEG07OI8
Edit it before you do. You need to change number 262 (=Germany) to the number for your country and the following 01 (= T-Mobile) to the number for your network.
At the end of the line you can enter the text you want to appear. Push it and reboot, enjoy
This works with EVERY Rom
Auf meinem Galaxy Nexus geschrieben
Click to expand...
Click to collapse
Anybody know the numbers for USA and Verizon?
BeADroid said:
Anybody know the numbers for USA and Verizon?
Click to expand...
Click to collapse
I'd like to know this too.
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
http://forums.androidcentral.com/ve...d-removed-verizonwireless-lock-drop-down.html
here is a guide
SpinDisc said:
Just went into /system/etc with Root Explorer. Can't find the spn-conf.xml file anywhere (even did the search). Possibly different on the Verizon LTE SGN since the one from Germany is GSM...
Click to expand...
Click to collapse
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
I just realized that you can start Market Enabler and it will tell you the correctly number
nachtschicht said:
That's OK, it won't be there. Just copy it there so it will be recognized
It doesn't have anything to do with GSM or LTE.
Click to expand...
Click to collapse
Thanks for the info! I'm still a newb. My family & friends think I'm a genius (rooted their D.Incredible, D2, Eris, etc). But none of it's possible without the knowledge on XDA. Still learning, and hoping to learn more. Thanks for the info on how to change the banner info, too!
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
mrZoSo said:
I have a VZW GNX.
The first method did not work, tried all the numbers I found for Verizon, unless I did something wrong, heh.
DHO's method, when I look for "64…Verizon Wireless" it's just "64...65..." on the Nexus.
So I'm assuming it's pulling the 'Verizon Wireless' information from something else. It would be nice to find that.
Click to expand...
Click to collapse
I'll update my write up over the weekend as it is for the OG, but look for
HTML:
EriInfo......Verizon Wireless...64...65.
So in the Gnex it is immediately before 64
Can toss a link to market enabler
Sent from my Galaxy Nexus using xda premium
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Nevermind that was a different one I had here, my bad.
I'm going to pull the one off the phone now.
mrZoSo said:
This is what's in the stock one now:
EriInfo...... Google ...64...65...
Click to expand...
Click to collapse
I am still running a stock 4.0.2 based ROM. When I look at some of the ASOP 4.0.3 that I am playing with, one has google, one has verizon. Changing whatever comes before ...64...65 will edit both the lock screen and the tag at the bottom of the notification bar.
CM9 based ROMs seemed to have moved this value to a different file. It would take some digging to determine where they move it to.
DHO said:
If you want to customize/edit the banner I can confirm this method works 100% with the Gnex
http://d-h-o.us/home/?p=282
I have found the best way to flash it is to create an update.zip or to find file in the ROM you are using and flash it with the ROM. By doing this you lose no data, no need to restore any setting.
The method I posted on my site will nuke your account data (aka just sign into google again).
Click to expand...
Click to collapse
Thanks for linking to your great write-up! I followed it (for the most part), and it works...until my screen shuts off (from no activity), and then it goes back to Verizon Wireless. I've tried it two different ways (I'm currently on Deoxed Stock ICL53F with APM & Softkeys):
1. I edited the eri.xml, repackaged it in the APM .zip (since I found that installing other framework-res.apk's broke the APM). Re-flashed the APM .zip, and the new banner "Galaxy Nexus" stuck until the screen shut off. Back on, and it's back to VW
2. I just repackaged the framework-res.apk, and took it out of the APM.zip. Placed it in the "sdcard" section, copied in Root Explorer, and pasted into /system/framework/. After a reboot, same this as #1.
So, how do I get it to stick? Does it have anything to do with the ROM I'm on? Or with APM? I feel like it should work, but something's just not sticking...ugh...
SpinDisc, I'm not sure. I think it may be a function of APM. I have been trying to replicate that bug and I cannot. What launcher are you using?
I cannot replicate it running a ROM compiled from Pete's 4.0.2 AOSP source and NOVA launcher. I will further explore this over the weekend.
This weekend I plan on testing/modding a few different 4.0.3 ROMs, if I find any nuances I will let you know.
If you're rooted, you can use Root Tools.
https://market.android.com/details?...51bGwsMSwxLDEsImNvbS5qcnVtbXkucm9vdHRvb2xzIl0.
Ive been looking around the roms on the sprint section to find another stock rom that is already GSM unlocked so it can be used on t-mobile, like the Cyanogen11 one but cant find a definitive answer while reading through the roms and change logs of the roms. i know this might be a stupid anwsers and sorry if it is, but im not used to dealing with sprint phones and the TC method never worked for me when i have tried to do it and i have done it. any suggestios. thank you in advance.
I think for now it's a test it and keep a list of what works or if you try some post your results here I'm sure we are not the only two wondering this. cm11 works good great data speed for me on att but would also like a stock option.
Sent from my SAMSUNG-SM-N900A using Tapatalk
MrKickstand said:
Ive been looking around the roms on the sprint section to find another stock rom that is already GSM unlocked so it can be used on t-mobile, like the Cyanogen11 one but cant find a definitive answer while reading through the roms and change logs of the roms. i know this might be a stupid anwsers and sorry if it is, but im not used to dealing with sprint phones and the TC method never worked for me when i have tried to do it and i have done it. any suggestios. thank you in advance.
Click to expand...
Click to collapse
The TC method never worked for US carriers. Have you tried the build.prop edit method? Should not be dependent on the rom. For a stock rom I find OpTimuS DE excellent. I used it previously with the build.prop unlock and now with the permanent unlock (but I'm in Canada).
scottdanpor said:
The TC method never worked for US carriers. Have you tried the build.prop edit method? Should not be dependent on the rom. For a stock rom I find OpTimuS DE excellent. I used it previously with the build.prop unlock and now with the permanent unlock (but I'm in Canada).
Click to expand...
Click to collapse
What's the build. Prop method?
MrKickstand said:
What's the build. Prop method?
Click to expand...
Click to collapse
Use rom toolbox (or similar) to edit your build.prop... ***case sensitive!!!!***
ro.build.target_operator = SPR
reboot
ro.build.target_operator = OPEN
reboot, then
ro.build.target_operator = spr
reboot
The last one (spr) is done because you will get system UI crashes if you leave it as OPEN.
scottdanpor said:
Use rom toolbox (or similar) to edit your build.prop... ***case sensitive!!!!***
ro.build.target_operator = SPR
reboot
ro.build.target_operator = OPEN
reboot, then
ro.build.target_operator = spr
reboot
The last one (spr) is done because you will get system UI crashes if you leave it as OPEN.
Click to expand...
Click to collapse
Blah, that didn't work, even with the sprint Sim. When I use the LG tool to go back to stock on picks up some service with the sprint Sim.
MrKickstand said:
Blah, that didn't work, even with the sprint Sim. When I use the LG tool to go back to stock on picks up some service with the sprint Sim.
Click to expand...
Click to collapse
I don't follow. Why would you have a Sprint sim in the phone?? If you do this with a Sprint sim in the phone you will lose data. If you flash a rom or back to stock, you have to edit the build.prop again to activate gsm.
scottdanpor said:
I don't follow. Why would you have a Sprint sim in the phone?? If you do this with a Sprint sim in the phone you will lose data. If you flash a rom or back to stock, you have to edit the build.prop again to activate gsm.
Click to expand...
Click to collapse
Haha sorry I didn't mean to make that confusing. But it didn't work with the T-Mobile Sim either. The only time I have been able to get any type of service bars instead of a red x over it is when I put the sprint Sim in and go back to bare stock
Actually now when I put my T-Mobile Sim back in, it shows all the service bars Grey but can't choose and operator or send a text.
MrKickstand said:
Actually now when I put my T-Mobile Sim back in, it shows all the service bars Grey but can't choose and operator or send a text.
Click to expand...
Click to collapse
You can use the app Tweakker to enter your APN settings.
the phone wants to resort back to cdma for phone service, grab an app called telinfo from the play store and use it to set your phone to GSM (auto PRL), then set your APN to get data working, best of luck!
Few weeks ago i had rooted my htc one m8 and trying to edit the default.xml file but it is not working even i change anything it won't let me do it goes to original state immediately so what might be the cause for this?
Ample12 said:
Few weeks ago i had rooted my htc one m8 and trying to edit the default.xml file but it is not working even i change anything it won't let me do it goes to original state immediately so what might be the cause for this?
Click to expand...
Click to collapse
Do you have read/write access?
/ Sent from my phone /