[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
For the sake of visibility, I figured I would go ahead and post this here for everybody. Wildchld did post in The Archangels "Don't Want a Brick..." sticky, but as it seems that many people don't read or keep up with the sticky threads, I thought it would be more noticeable here.

Also it appears that a lot of people may be using the Google Wallet workarounds, and potentially may be using Mobile Odin as well. This seemed important enough to post here to warn those using both of the potential to brick their device.

If you have modified your build.prop to trick Google Wallet into thinking it is on a different device...

DO NOT FLASH ANYTHING WITH MOBILE ODIN!!!

YOU WILL BRICK YOUR PHONE!​

So basically here's the deal...modifying these lines in the build.prop essentially fools an app such as Google Wallet into thinking it is on a different, supported device.

ro.product.device=d2tmo

ro.product.name=d2tmo

ro.product.model=SGH-T999

The values shown above are the CORRECT ones for our device. If you change them, Google Wallet is not the only app that will think it is on a different phone! This probably would not be a major concern for most apps. However, by tricking Mobile Odin into believing it is on a Nexus or something else will cause it to load the incorrect partition mapping (and maybe the wrong flash kernel). Then when you try to flash something under this setup it will flash the wrong partitions with the wrong images, resulting in a brand new brick!

Thanks to Wildchld for finding this! You can find his post about it here.

From his post, a quote from Chainfire

: "Quite likely, you will brick your device so hard only a JTAG unit will be able to revive it. A service center will replace the mainboard (about half the price of a new device) to fix such a brick. I would strongly advise against making a program that writes raw partitions believe it's on a different phone than it really is."

I do not think this will be a problem for the regular PC Odin, but have not confirmed this yet.

If you want to flash with Mobile Odin, please restore your backed up copy of the build.prop before flashing! Probably would be a good idea to go into app manager and clear cache and data for Mobile Odin as well.

I believe there is a Wallet workaround that uses a hacked apk and does not require the build.prop edits to remain. You can change them back to original values after initial setup.

I do not use Wallet, so I am not sure which method is which right now.

I hope this information proves useful for some of you! Dont forget to hit the Thanks button when you check out Wildchlds post or XquiziT rom threads! I would not have known about this if not for him!

Note: This also applies to any mod that edits the build.prop in this way. Such as editing it so you can download/buy unsupported apps from the Play Store, among others.

There is nothing wrong with Mobile Odin!

It is a powerful tool and functions just as it is supposed to. It is up to the user to use it in a safe way for their own purposes, and to know what they are doing with it!

Also, this is not meant to be an attack on those who have released these mods, my only intent is to caution folks so they may avoid serious and sometimes expensive problems!