This does nothing more than re-brand the build.prop to T-Mobile G2 if you are using one. In other words it might not actually get around certain apps such as say Hulu in identifying your device with a non-Stock rom.
I wrote up this flashable zip because I was tired of editing the build.prop after a rom update. All this zip does is search for existing property lines and replaces them as per Gino A Melone's patchprops.sh script.
The following properties are replaced in the /system/build.prop , all others are left alone.
Code:
ro.product.model=T-Mobile G2
ro.product.brand=tmobile
ro.product.name=htc_vision
ro.aa.maincid=T-MOB010
ro.aa.cidlist=T-MOB010
ro.aa.modelid=PC1010000
ro.aa.skulist=531
ro.aa.mainsku=531
ro.ril.oem.ecclist=911
ro.product.model.internal=A8181
Modifying
You can also unpack the zip and modify the build.prop.patch file in notepad++/textmate and then re-zip accordingly to have your own set of props to be replaced upon flashing.
In OSX you'll want to zip it via command line (making sure to remove the .DS_Store files first) with something like:
Code:
zip -r9 vision_tmobile_branding.zip ./*
I imagine it's pretty much the same on linux. I only mention it because archiving tools may not correctly pack the zip, or may include the parent folder instead.
kbeezie said:
ro.product.model.internal=A8181
Click to expand...
Click to collapse
It should be A7272, isn't it?
Because A8181 is for original Desire.
NeverGone\RU said:
It should be A7272, isn't it?
Because A8181 is for original Desire.
Click to expand...
Click to collapse
No 7272 is desireZ, 8181 is G2, I've verified it.
(though oddly the tmobile UK desire shares the same internal ID as the tmobile USA g2, as does a tmobile G7 windows phone)
Sent from my T-Mobile G2
This is the best. Thumbs up and thanks mate!
Sent from my HTC Vision using xda premium
I'm not on tmo, but thanks for contributing this!
Sent from my HTC Vision using xda app-developers app
=JKT= said:
I'm not on tmo, but thanks for contributing this!
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
No Prob. It's mainly an issue with Tmobile users, since most roms are done by international developers, as such it's defaulted to the Desire-Z prop info. I mainly consider the patch to be cosmetic.
Related
Found great INFO on how to use smali,backsmali
from SINO8R and HOW-TO remove the 7 trottling files "sins" THX Sino8r for this great info...
you can find his thread way bigger ....my file ONLY works on mentioned software
I recompiled services.jar .
removed the 7 files .. "throttling" with smali,backsmali
somehow it shoud fc on entering apn ..but dos NOT.. heh
SERVICES.JAR.zip for SOFTWARE:
1.34.405.5
Radio 12.28b.60.140eU 26.03.02.26 M
FILE BELOW
RENAME IT SERVICES.JAR AND ENABLE DATA ROAMING BEFORE YOU REPLACE ..
i used ROOTEXPLORER from market to replace /system/framework/services.jar and set permissions rw r r like the other files
THX Marsdroid
Follow me on Twitter
Has anyone tried this yet? Is it for download speeds? I'm not quite sure I understand..
Could we have a bit more explanation please
steviewevie said:
Could we have a bit more explanation please
Click to expand...
Click to collapse
This is the method taken from the G2 forums, but not so much info there either.
Sent from my HTC Vision using XDA App
On the G2 side this seems to have been specifically designed to defeat something that T-Mobile have implemented for data throttling, i.e. where you go over a certain data usage limit they slow your download speeds.
I'm not clear on who can benefit from this on a DZ, e.g. what other carriers ? Do they use the same methods that this workaround will help with ?
3.dk is trottling ..not sure if they use the same mode.. anyways no one wil be able to trottle me this way again...
Sent from my HTC Vision using XDA App
Could this disable data throttling by O2 (Germany), too?
I am on an unlimited data plan with Bell, and bought a Desire Z to replace my HTC Hero. Because of the massive amount of tethering I used to do, they throttled my speeds to about 1MB's... my upload was untouched at about 2-3MB's. After following the guide on the thread in the G2 section, my download speed is up to around 4MB's. Worked for me, just thought I would chime in.
Great..sadly dosent work with 3 from dk
Sent from my HTC Vision using XDA App
There's an unlimited data plan for Bell? Was it some sort of deal?
Sent from my HTC Vision using XDA App
tried this in terminal emulator.. i mounted the system rw then mv services.jar to /system/framework/... when i restart it hangs after htc logo (where the cyanogenmod animation should be) had to use advanced clockwork recovery restore to fix system.. what am i doing wrong? why is it doing that..
Maybe your not using stock... .. try replacing it with root explorer and set the permissions ... i did that
Sent from my HTC Vision using XDA App
brokenworm said:
Your not using stock..and cyanogenmod dont include trottling in the first place . Heh or try replacing it with root explorer and set the permissions ... i did that
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
*Clip* cm DOES include throttle services in services.jar! Oh and the thank you was a mistake, i meant to hit reply. *Clip*
kthx... my thread has been alterted ... and updated i had to reupload the file.
thx
Kindly please write instructions on what to do with the file
ok so i extracted a rom from a ruu, but now where do i start?
what do i need to extract from the rom.zip? i know i need system.img but what else?
Which RUU did you extract the ROM package from? Is it from the Evo 4G RUU, or are you porting from a different device's RUU?
Might I suggest downloading a stock updated ROM and look how /system is set up? The most basic folders of a ROM would be /system and /METAINF (this contains the scripts for the ROM to be flashed and .apk to be installed).
Are you planning to theme? Do you have ADB set up (Java installed beforehand)? I would suggest looking for PapaSmurf's Everything Android thread and downloading the tools there.
Sent from my SPH-M900 using xda premium
i extracted the rom from the htc primo(One V) leaked ruu.
bennyboy78 said:
i extracted the rom from the htc primo(One V) leaked ruu.
Click to expand...
Click to collapse
Ah, ICS Sense. We currently don't have a kernel that will even let the phone boot. We are missing valuable libs and drivers, and the fact that the Evo is EOL'ed doesn't help, so we won't be getting updated packages. It would be nice if HTC dropped kernel source for ICS, but alas, they have not.
Sent from my SPH-M900 using xda premium
tropicalbrit said:
Which RUU did you extract the ROM package from? Is it from the Evo 4G RUU, or are you porting from a different device's RUU?
Might I suggest downloading a stock updated ROM and look how /system is set up? The most basic folders of a ROM would be /system and /METAINF (this contains the scripts for the ROM to be flashed and .apk to be installed).
Are you planning to theme? Do you have ADB set up (Java installed beforehand)? I would suggest looking for PapaSmurf's Everything Android thread and downloading the tools there.
Sent from my SPH-M900 using xda premium
Click to expand...
Click to collapse
i am not planning to theme. currently, the important things are still .img file types. what do i do with these? i cant open them since theyre .img's
i see... hmmm...
well i guess i will just hold off till HTC releases some source code for ics... hopefully
bennyboy78 said:
i see... hmmm...
well i guess i will just hold off till HTC releases some source code for ics... hopefully
Click to expand...
Click to collapse
If you would like to continue, I can look for some links to decompile the images.
While it is not impossible to port, it would be very difficult. Some drivers might have to be written, considering Sense 4.0 uses ImageSense or some nonsense like that. An ICS kernel source drop would definitely help, especially for the lowest-end One-series phone.
Sent from my SPH-M900 using xda premium
if you could find some links that be great. thanks
tropicalbrit said:
If you would like to continue, I can look for some links to decompile the images.
While it is not impossible to port, it would be very difficult. Some drivers might have to be written, considering Sense 4.0 uses ImageSense or some nonsense like that. An ICS kernel source drop would definitely help, especially for the lowest-end One-series phone.
Sent from my SPH-M900 using xda premium
Click to expand...
Click to collapse
The Primo doesn't have Sense 4.0; it has 3.6. It's got a single-core, 1GHz CPU with WVGA resolution, and the ROM size is only around 300MB. I think this IS the lowest end ICS One series phone, but it'll definitely be a while before the source drops.
i had long ago rooted my device , i lost my nandroid back up on the second day when i had flashed a custom rom..
and now i use a so callled stock rom that i downloaded from somewhere idk
i dont get ny updates.. y is this so? ??
Why stock rom??? Get back on CM7 !
Or install a custom stock rom - get .sense - it's got sense v3.5.
*se-nsei. said:
Why stock rom??? Get back on CM7 !
Or install a custom stock rom - get .sense - it's got sense v3.5.
Click to expand...
Click to collapse
yeah bro i know that .. comon i am a tester of that rom i m in your team of wfsdev and you dont realize wierd.. nywys.. but i do think that my touch isnt that much responsive as it was and i think my radio should be updated
Forget about official updates if you have rooted device.
Wow, neither of you helped this guy, or even tried.
The only thing I would know to do is to find the original ruu for your carrier, flash that, and see where you stand. I'm pretty sure the updater only checks for firmware versions. NOT su installation. Could be wrong though...
mhrsolanki2020 said:
i had long ago rooted my device , i lost my nandroid back up on the second day when i had flashed a custom rom..
and now i use a so callled stock rom that i downloaded from somewhere idk
i dont get ny updates.. y is this so? ??
Click to expand...
Click to collapse
I think I can help you but I have a question
What does boot.img and system.yaffs2.img contain?
Edit: no need to feel sad, the update won't release in India for some time.
Sent from my HTC A510e using XDA
BigChillin said:
Wow, neither of you helped this guy, or even tried.
The only thing I would know to do is to find the original ruu for your carrier, flash that, and see where you stand. I'm pretty sure the updater only checks for firmware versions. NOT su installation. Could be wrong though...
Click to expand...
Click to collapse
We've been searching for a long time . It isn't there!
Sent from my HTC A510e using XDA
vbhtt said:
I think I can help you but I have a question
What does boot.img and system.yaffs2.img contain?
Edit: no need to feel sad, the update won't release in India for some time.
Sent from my HTC A510e using XDA
Click to expand...
Click to collapse
The boot.img contains all the data that is required for booting like boot animation your kernal and all .. the.system.yaffs2.img contains all the system apps (HTC likes , sense. , rosie n all ) .. its like a structure .. will explain you in detail when I sit on my lappy I can't wrote that Much with my cell
Sent from my HTC Wildfire S A510e using xda premium
BigChillin said:
Wow, neither of you helped this guy, or even tried.
The only thing I would know to do is to find the original ruu for your carrier, flash that, and see where you stand. I'm pretty sure the updater only checks for firmware versions. NOT su installation. Could be wrong though...
Click to expand...
Click to collapse
i actually tried to download the ruu of aisa but then when i extract the rom.zip from %temp% ie c:temp/rom.zip and try to extract it the error comes that it is not proper file like it is damaged (dont remember the exact error) then i have to break the operation .. so i posted ..
ny one from india can make a backup and just mail me the boot.img and system.yaffs2.img from the clockworkmod folder in the sd card???
vbhtt said:
I think I can help you but I have a question
What does boot.img and system.yaffs2.img contain?
Edit: no need to feel sad, the update won't release in India for some time.
Sent from my HTC A510e using XDA
Click to expand...
Click to collapse
see bro i explained you about the boot.img its only that much now in detail fr system.yaffs2.img (can be told as system.img too)
system.img is the system folder in your rom. when it is extracted it becomes the system folder..
if you go into system folder yyou will see these folders..
Code:
app
bin
customize
etc
fonts
framework
lip
lost+found
media
usr
xbin
and a file named build.prop
app:
Code:
it is a folder where all system apps are there..
you can paste a apk there to make it the system app
(the system apps dont get updates from market mostly
bin:
Code:
it hellps the icons to animate..
like if the animation has 9 images then to move those nine images
(that is to animate those nine images to become one animation)
the commands are given here in bin
(as far as i know i may be wrong about this)
customize:
Code:
all the customisations are here like your boot animation
(the default one not the customized one)
your default wall paper.. etc
etc:
Code:
all the permisions and etc are here
like the permisions of su , the bluetooth paired devices
your wifi passwords and all
fonts :
Code:
no explaination needed
framework:
Code:
it is a folder where all the jar files are located..
the jar files are used for all the work you do ..
like if you assign the MENU key with a Launcher then
tht assigning is saved into a jar
(this is never used with launchers its just an example)
if you wanna change the theme then you can edit
the framework-res.apk in it :D
lib:
Code:
all the lib like sound plugins this plugin that plugin
lost+found:
Code:
i dont know , its allways empty for me :(
donnt know what it is
media:
Code:
here you can paste the bootanimation.zip
of your own choice to have a
customized bootanimation.zip .
usr:
Code:
here all the icons are located ..
the icon of wifi bluetooth keyboard and all
xbin:
Code:
it is just a bin mostly used as a temp folder :D
the build.prop
Code:
its a file that is as like the updater script
but doesnt update nything but shows the information in the rom,
like what is the build of the rom
what version of the sense
what resolution you want
(the default is 120 but it is changable :D)
got things clear?
I got an idea. Go to HTC service centre and shed 500 re, rest they will do
Sent from my HTC Wildfire S A510e using XDA
peace.nitish said:
I got an idea. Go to HTC service centre and shed 500 re, rest they will do
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
bro if i go there with this version then i am pretty sure that i am gonna loose my warranty ..
Not a problem for me coz I am a cellphone retailer. Hehe
Sent from my HTC Wildfire S A510e using XDA
peace.nitish said:
Not a problem for me coz I am a cellphone retailer. Hehe
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
oh then the warranty wont be affecting you
Hi All,
I'm starting this thread so that we can compile in one location the methods we attempted to create a zip for the recent Jellybean update, and hopefully advance the creation of this rom. This should be mentioned before starting.
ONLY POST IF YOU HAVE RELEVENT INFORMATION REGARDING THIS JELLYBEAN ROM.
This Includes:
Procedures
Logcats
Test Builds
Helpful Suggestions (Be Specific)
To start, I've attempted the following alterations on the zip level:
Straight System dump with updated updater-script
System dump with default updater script
Modified updater script removing patch elements
Utilizing the Canadian Rom, which flashed and appplying new system.
Swapping out radio flashing and boot.img with shellnutt's boot.img
I also have the following plans:
System Dump on Canadian Rom, and default boot.img
Recursive Deleting of patched files
Example
Code:
assert(apply_patch_check("/system/3rd_party/videowiz/lib/libMvMMAS.so", "65cfe8efc36cf58669e5fb9f30274bc49c3f9703", "e1a051bb2562af8d9b106ef4b875f85a6109ee9e"));
set_progress(0.003080);
delete("/system/3rd_party/videowiz/lib/libMvMMAS.so");
Than initiate the normal package_extract_dir("system", "/system");
Any other information would be great. Some developers have gotten it to flash but not boot.
Also, here's a link to the test builds I released.
http://goo.im/devs/AdriVelazquez/Roms/Nightlies/TestSprint
Thanks to all the developers that have been working on it.
This is what I've tried:
Used the boot.img & system.img. from dump to compile a rom in dxsdia's kitchen. I was able to apply root to the boot.img and compiled a zip but it wont flash. I then added the updater script from the dump but it still wouldn' t flash. Ithink my problem is in the updater script. I didn't take thetime to configure the kitchen properly for the optimus G but will do so tonight. I have the 2 test zips at home and I'll post them tonight if anyone wants to take a look.
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
johnq54 said:
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
Click to expand...
Click to collapse
I already tried that. That was the test zip I did last night.
Sent from my LG-LS970 using xda premium
I also tried both mentioned here, none worked for me as well. I contacted couple of friends to help us out, Scott (Scrossler cleanrom series) already answer me back, he's looking into it, I will let u guys know if they get something working.
Edit: houston answer as well, he is gonna work on it as well.
LROD'S OPTIMUS G
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
grktaurus83 said:
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
Click to expand...
Click to collapse
This is what I was looking for. Thanks!
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Shelnutt2 said:
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Click to expand...
Click to collapse
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Thanks dastin for answering and thanks guys for getting what he needs to help us.
LROD'S OPTIMUS G
do we have any logcats?
dastin1015 said:
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Click to expand...
Click to collapse
A bit late but might still be helpful to others. Here is a pastie of the by-name goodness as clear as a bell. This is the Sprint varaint
http://pastebin.com/teQmXDX9
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
_Epic said:
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
Click to expand...
Click to collapse
Same here
Sent from my LG-LS970 using xda premium
Veritass said:
Same here
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
can either of you post the build.prop? I won't be updating.
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
How's this?
http://pastebin.com/yjNnR2sh
Sent from my LG-LS970 using xda premium
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
Here's the build.prop
http://pastebin.com/UXSBvNMj
Provided by epic since I haven't done the update also.
Sent from my LG-LS970 using xda premium
I sent Adriel build.prop file but forgot I could copy text and post to pastebin. That's why we both posted. Lol.
Sent from my LG-LS970 using xda premium
Good morning to all, We have another dev, his name is negamann303 from the evo 3d forum, he's working hard on our project, already send me stuff to test, we will not post anything because these zips are highly flammable and all the testing is done in a spare phone I have, I will keep u guys updated.
LROD'S OPTIMUS G
I have an i747m galaxy s3 which is unlocked, i downloaded the Wicked rom which has the multi carrier feature, i accidentally clicked on T-mobile device in Aroma and continued with the setup. What surprised me was that it worked perfectly ( I prevoiusly flashed an t999 international rom and bricked my phone) but i was just wondering if that is an exception with the Wicked Rom or do t-mobile roms work on the at&t gs3? while were at it do sprint roms also work on at&t? I'm new to flashing, any help is appreciated
Yes you can flash a t999 rom to your i747, I have flashed many of your i747 roms to my t999... There is no such thing as a t999 International version, though. International S III has a different ChipSet so they brick our US S III's. Read some more and be careful what you click or you'll be sitting on 500$ paper weight bud.
Yes you can. You may have to do some build.prop edits to change from d2tmo to d2att to get everything working right
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad you like the wicked rom on Att...look out because Evil1Art say wicked 10 should be out in couple of days.
TeknoGodz said:
Yes you can. You may have to do some build.prop edits to change from d2tmo to d2att to get everything working right
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How do i go from d2att to d2tmo? can you send me a link on build prop editing?
1981resse said:
glad you like the wicked rom on Att...look out because Evil1Art say wicked 10 should be out in couple of days.
Click to expand...
Click to collapse
Yea man im waiting for that but mean while i'm on aokp
OmarEz007 said:
How do i go from d2att to d2tmo? can you send me a link on build prop editing?
Click to expand...
Click to collapse
You can use RootExplorer or Solid Explorer to edit your build.prop file located under your system root in the folder "system" (/system/build.prop)
Your build.prop is basically a configuration file that stores information about your phone.
The lines that you would need to edit are "ro.product.name" and "ro.product.device"
Once you flash the tmo ROM you would edit the above lines accordingly. Then, reboot the device for the changes to take affect.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
You can use RootExplorer or Solid Explorer to edit your build.prop file located under your system root in the folder "system" (/system/build.prop)
Your build.prop is basically a configuration file that stores information about your phone.
The lines that you would need to edit are "ro.product.name" and "ro.product.device"
Once you flash the tmo ROM you would edit the above lines accordingly. Then, reboot the device for the changes to take affect.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot for your help. Also one last thing is it only tmobile roms that work on att phones or should sprint and t999 work if i also change the build prop? either way you've been really helpful
OmarEz007 said:
Thanks a lot for your help. Also one last thing is it only tmobile roms that work on att phones or should sprint and t999 work if i also change the build prop? either way you've been really helpful
Click to expand...
Click to collapse
T999 is the TMobile version. The other ROMs (Verizon and Sprint) CAN work, but you cannot just flash them like the t999 ROMs. You have to make some edits to port the ROM over before you can flash, otherwise you may harm tour device. I'd recommend searching XDA on "ROM porting for the S3."
Also, just so you know, for the build.prop, the code names for each device is:
"d2att" is AT&T
"d2tmo" is T-Mobile
"d2spr" is Sprint
"d2vzw" is Verizon
There are some great tutorials out there, its a little more in depth than what I can go into here.
Sent from my SGH-I747 using xda app-developers app