I've just received a new T-Mobile G1 and I am pretty desperate to update to a cupcake build. There's loads of guide here that will walk me through it no problem, but there are some things they don't explain fully (or at least, I can't find them).
Will I lose all my contacts and messages when I update? Will I lose all my T-Mobile data (like message settings, 3G settings etc.?). Will Market and everything else still work? What will stop functioning correctly when I do upgrade, specifically for T-Mobile in the UK?
Thanks a lot!
Tony
Funkstar De Luxe said:
I've just received a new T-Mobile G1 and I am pretty desperate to update to a cupcake build. There's loads of guide here that will walk me through it no problem, but there are some things they don't explain fully (or at least, I can't find them).
Will I lose all my contacts and messages when I update? Will I lose all my T-Mobile data (like message settings, 3G settings etc.?). Will Market and everything else still work? What will stop functioning correctly when I do upgrade, specifically for T-Mobile in the UK?
Thanks a lot!
Tony
Click to expand...
Click to collapse
You will lose messages, you will not lose any T-Mobile data, you will not lose any contacts. I suggest you check out Haykuro's thread: http://forum.xda-developers.com/showthread.php?t=498026
You will need root. And I suggest you go with haykuro's 4.5 build. I won't go in to any more detail, just do some research in haykuro's thread and others on how to get root, etc. Good luck.
Wel.. Where can i start? The cupcake your possibly reading about isnt fully working on G1 Yet..
I recomend you try one of the magic roms ported to G1, Preferbly 5.0H
Root is easy to achieve, Just read around.. Plenty ahve asked how to do this before, so please dont make new threads, Just read please
If you are referring to the ''Cupcake'' that T-Mobile is releasing this Easter then all these guys are wrong. If you do update to HTC Sapphire it will void your warranty and there's a small(Or large if you don't follow directions) that you could brick your brand new G1. The ''Cupcake'' that T-Mobile will release or at least hoping it will, will be coming in the next days. This update is 100% safe and will not do anything harmful to your g1. It wont even delete anything.
Mast3rmatt said:
If you are referring to the ''Cupcake'' that T-Mobile is releasing this Easter then all these guys are wrong. If you do update to HTC Sapphire it will void your warranty and there's a small(Or large if you don't follow directions) that you could brick your brand new G1. The ''Cupcake'' that T-Mobile will release or at least hoping it will, will be coming in the next days. This update is 100% safe and will not do anything harmful to your g1. It wont even delete anything.
Click to expand...
Click to collapse
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
blackknightavalon said:
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
Click to expand...
Click to collapse
That's exactly what I'm planning to do. I was hard set against root when I first got my g1, but I have seen the light and enjoyed my rooted g1. Thank goodness for the jfupdater app
blackknightavalon said:
And as I've said in other threads re: Cupcake, I say we wait for JF to do his thing with it.
Click to expand...
Click to collapse
Huh? That has nothing to do with my post other. My post was answering his question about ''CupCake'' from T-Mobile and not some other Rooted Cupcake. I understand that there are other cupcakes but the best will be T-Mobile for the time being.
I think I said CupCake enough times
Mast3rmatt said:
Huh? That has nothing to do with my post other. My post was answering his question about ''CupCake'' from T-Mobile and not some other Rooted Cupcake.
Click to expand...
Click to collapse
Actually, he asked about *a* Cupcake build - he made no mention of an official build, therefore it is reasonable to presume that he is referring to *one that is available* and not *one that isn't*.
I understand that there are other cupcakes but the best will be T-Mobile for the time being.
Click to expand...
Click to collapse
Really? For the time being, there is no T-Mobile Cupcake build so how it can it be best? Granted, if and when it comes out, it may well be superior, but that is by no means certain since Haykuros builds are getting better all the time.
If the OP is waiting on an official T-Mobile Cupcake update, I suggest there is no point asking around here since if he leaves his phone with a vanilla build, he'll get the update soon enough, if and when it is released.
Regards,
Dave
Thanks guys. I'm not waiting on the t-mobile build as I have little faith in them releasing it any time soon. I'll ask my question in a different way; what's the best build to put on my UK t-mobile G1? With regards to battery life and features? Thanks
I suggest you read the threads about rooting your G1. The first thing you have to do is downgrade to RC7, and get root. Then, don't accept any OTA (from T-Mobile) upgrades if you should get a notice.
After downgrading and getting root, read up on some of the different builds. You can go to JF's RC9, which is a modded version of the official UK one with root. I would really advise you to do this first, so you will know how to flash your roms, and how to flash the radio.
It will give you a stable version which won't accept OTA updates so you don't have to worry about losing root. (Plug your phone into a power source, or at the very least, be sure your battery has a full charge while flashing, and don't ever turn your phone off while it is flashing.)
After that, read threads like the one comparing the two Magic versions. 5.xG is the google version, and 5.xH is the HTC version.
Once you have gotten root and gone to RC9, you will be able to do something called a Nandroid backup of your phone. You will then be able to try both versions of magic, and also to restore your phone to RC9 if they don't work out for you without losing anything. (Another reason to try a more official mod before trying the Magic ones).
edit: I just found this on the Magic wiki page. It looks helpful: http://code.google.com/p/sapphire-port-dream/wiki/PageName
Have fun with it!
Related
I am new to the Dream, I just got mine on Friday. I have now got root access. I want to know when the RC31 comes out, if I update via t-mobile will it kill root access, or will I need to hold off until a modded FW comes from JesusFreke.
Thanks
Tim
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Thats what I figured. thanks for the info.
otto888 said:
Yes,if you update via t-mobile,it will remove root. Its best if you wait for a modded FW if you want root.
Click to expand...
Click to collapse
While I agree that it would probably be best to not upgrade right away, we don't know anything about RC31 yet. The only thing I think that has been officially announce is that it would contain elements of cupcake. I'm not even sure how official that was either. Let's try not to speculate.
Echoing what's been said above, being that we know NOTHING about the next OTA update, it will likely (at the very least) remove root access from a JF RC30 device. It might even prevent you from backflashing to RC29 to get back to the modified JF RC30. So whatever you do, DON'T let your phone update until the new version is examined and tested by others, or you might find yourself with a permanently locked down G1.
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
Correct, or the update will fail, can't remember which one.
So I guess it would be safe to say....
STAY TUNED!!! Same XDA time, Same XDA channel
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I love when modders do that, keeps me from doing something stupid
Iceucold said:
If you're running any JF version of the firmware, you will not receive OTA updates. So, you have nothing to worry about unless you actually flash back to RC29 manually.
Click to expand...
Click to collapse
I am not entirely convinced of this.
I had a chat with a co-worker about this and he said "well no, between the engineering bootloader and the test keys, there is no way the modded rc30 can be OTA'd".
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
I imagine that anyone with ADP1 or ADP1.1 will be left alone as it would be a bad move to screw with your developer audience; but I could be wrong. They could go after anyone who doesn't have an official ADP image (non JF kernel)...
I have no idea what they are really planning but it does seem that this could be a "check mate" pivotal move if they wanted to play that card this early in the game.
Of course, it could be as simple as "let's leave everyone where they are and only focus on security moving forward" which is most likely going to be the case....
deprecate said:
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
The running theory is that T-Mo will not do this because all devices with the standard ota-keys installed will also get the "targeted" test-key rc31, reboot, and then freak out because the update is signed with a mismatched key.
The way the update service works is the device periodically sends its Android build fingerprint to Google servers. If the fingerprint is of a supported device (in this case Dream) and the build number is lower than the most recent, then the server may push an update back to the device. Since JF modified builds report an official fingerprint, there is no way for the server to distinguish between a modified and unmodified RC30.
However, i've seen enough in information technology to know that very little is truly "impossible". Based on what is currently known though, it is highly unlikely that Google/T-Mo/HTC could forcibly reroot a modified RC30 G1 at this time.
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
speoples20 said:
I really don't see T-mobile doing this. Why would they? At this point people with root don't have any real advantage over normal phones other than techie stuff. We are not pirating software or getting free minutes. Unless it becomes an issue I think T-mobile will leave us alone.
Click to expand...
Click to collapse
There is no piracy because apps are free. Once support for paid apps arrives, piracy will start. (Someone in this forum started a thread wondering how to do that). It happens in all software platforms, and it's going to happen with Android also. Note that I don't endorse piracy (for some weird reason people think that developers are the only guys who should work for free), less in these environments where there are lots of applications than are made by individuals, not big companies, but this won't prevent piracy to come to Android.
Anyway, if I were TMob I would try to remove root from as many devices as I can (which obviusly does NOT include ADP1, as it has nothing to do with TMob),
not just for the piracy, but to keep users from breaking their devices due to doing stupid thing with a rooted phone.
T-Mobile motivation to wipe devices using test keys
T-Mobile could have a motivation to wipe devices by providing an update using test keys. Tethering is against the terms of service and can only be done if you have root. They could take the *IAA approach and say that any one who has root wants to be able to tether and break their TOS (since tethering is the biggest advantage to root right now). If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered. BTW, for all who tether use this addon for firefox and change your user string to match the android's browser (https://addons.mozilla.org/en-US/firefox/addon/59) so they can not tell.
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Doing an update using test-keys sounds a bit desperate to me.
Moreover, as jashsu said, it seems that there is no way that currently TMob could know if you were using a G1 with an stock R30 or JF's one, so if they offered the update with testing keys, stock R30 phones would reject it.
They could try some tricks as offering the update with test keys for a while, then switch to another with official keys, then came back to test keys, etc...
But as I said, this sounds desperate and sloppy.
Mi bet is that they would try to fix the downgrade issue, and will use the official keys, so anyone with JF will be safe.
Anyway (I have an ADP1, so I've not receive any update from now), I though that, when an update was available, the user was asked whether to update or not.
clarke.hackworth said:
If enough people tethered it could cause a problem as they may not have the bandwidth to accommodate what people want to do when tethered.
Click to expand...
Click to collapse
This is not a problem. They will simply throttle you down to EDGE if they consider you are using up too much bandwidth (tethering or otherwise).
Is there a way to make new keys that are different from the dev keys, or is google the only ones who can do that?
Click to expand...
Click to collapse
Anyone can create signing keys. Not sure what you're getting at though.
clarke.hackworth said:
Tethering is against the terms of service and can only be done if you have root.
Click to expand...
Click to collapse
It is? Where? Last I remember I saw the CEO say it wasn't and it is allowed. And that they wouldn't stop it or prevent it in anyway.
deprecate said:
I tossed this at him.
What if tmo decided to setup something like this...
check what you are running.
check what keys you are running.
send an update that does something along the lines of...
if your image is equal to or less than rc30 and your keys are either ota or test then update.
There is nothing that keeps them from pushing a testkey signed rc31 and replacing everything on your phone; including the testkeys back to ota keys.
Click to expand...
Click to collapse
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
JesusFreke said:
It still wouldn't apply the update, even if they sent out an OTA signed with test keys. The OTAs are verified against the certificate present in /system/etc/security/otacerts.zip.
Since that file has been deleted, it wouldn't be able to verify the OTA, no matter how it was signed.
Click to expand...
Click to collapse
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
deprecate said:
Good point. That completely escaped me. But wouldn't it be entertaining to see an official rc31 sent out with your certs as the target
Click to expand...
Click to collapse
Very entertaining
I have been wavering back and forth on deciding to root or not. I am leaning toward doing it but I am so freakin busy with school and work that I was going to wait a few weeks until I had a chunk of time to read up and really understand what I am about to do.
My decision seems to have been forcibly accelerated today when the t-mobile update screen popped up. I have pressed update later a few times so far but wanted to ask a quick question before I decide which way to go with this. I want the new features in RC33 (and maybe better battery too?!?), but the additional features with the JF rooted versions seem way better.
Can anybody verify yet if I go ahead with the official RC33 update will I still be able to get root using the current methods? If not, any ideas if this is going to be possible? I know that is speculation but since its been out for a bit now I figured somebody would have some insight on this.
Thanks for any input you all can offer. All you guys around this site were great when I was messin around with my Shadow/Juno before I got the G1.
Thanks again!
Nick
Go ahead and go to the official RC33 update, it will still work. JesusFreke himself said that the update doesn't touch the bootloader, so the downgrader still works on this version.
It worked for me from RC33 official, it'll work for you too.
I understand your feeling about rooting. I also have limited free time between school, work, gf, and families. I say just do the rooting. It only took me couple hours on the weekend to get it done. To be honest, I found the tutorial on this site is a little too complicated and can be intimidating for those that not comfortable with linux command line.
just follow the rooting method on this thread below:
http://androidcommunity.com/forums/f28/rooting-your-g1-made-easy-11825/
I did it and never look back. I haven't heard that RC33 does any significant change on battery life, so I don't think it's worth the upgrade. I say go with Developer firmware (ADP1.x). ability to dump cache on sdcard + 3G wifi tethering + no google initial login = WIN with root
Yeh if you don't have time go for it. Like the previous posters have mentioned is does not make any irreversible changes that you would not be able to root the phone later when you have time. I would rather suggest following the tutorial on this page:
http://forum.xda-developers.com/showthread.php?t=442480
because it has all the links needed embeded right into the tutorial and is very straight forward about what and how to do to get a modified root rc33 on your phone and start living Android like it was intended lol.
Thanks...
Thanks for the info in all of your responses. I went ahead and updated to RC33 with the official update this morning. I think that it seems to be running better. After the update my avaliable storage space went from like 6 to 23 mb which I thought was odd. I think that I will end up rooting my G1 before cupcake, or the next update that comes our way. I am just going to wait until I have time to mess around with it some more. It does seem like an easy process but it is not without chance for issues as I have read from other posts.
Thanks again for the responses and advice.
Nick
http://www.youtube.com/watch?v=9W7Kfucgeck
I've hard reset it like advised and haven't installed any 3rd party apps.
After I wait a few hours, the phone will start to respond, but will be significantly sluggish.
I believe I should have posted this in the general section (Not sure, I'm fairly new to these forums)
AB_ said:
http://www.youtube.com/watch?v=9W7Kfucgeck
I've hard reset it like advised and haven't installed any 3rd party apps.
After I wait a few hours, the phone will start to respond, but will be significantly sluggish.
Click to expand...
Click to collapse
I think it's time you bring it to your local Verizon store and show them. Tell them "Look, I turn on the phone, and I can't use it!" I'm guessing they're smart enough to realize you need a replacement because that's not normal. I'm sure they'll give you another replacement.
If they don't, flash a ROM and see if it works. If everything works with the custom ROM, then it was obviously a Verizon stock ROM flaw (which I doubt since this doesn't seem common).
Yea, I had to pay for my first replacement ($50)
I hear the official 6.5 is out, where can I find that?
Also, I don't know the first thing about flashing phones with custom ROMs
AB_ said:
Yea, I had to pay for my first replacement ($50)
I hear the official 6.5 is out, where can I find that?
Also, I don't know the first thing about flashing phones with custom ROMs
Click to expand...
Click to collapse
Pshh.. they gave you a faulty one now, so you shouldn't have to pay for the next replacement!
Officially, WM6.5 for the TP2 is for the Unlocked GSM European TP2. It's only for GSM networks, though (you have CDMA, so you can't flash that!).
Custom ROM flashing: I learned from a pictorial. Just follow everything! Always flash a CDMA Rhodium/TP2 ROM (you can find those at PPCGeeks) to your Verizon/Sprint/Telus TP2.
Most ROMs are not going to be suited for your phone (keyboard), so some fixes are found here.
Some of the famous CDMA ROMs are MightROMs and EnergyROMs. Find one that suits you!
*CDMA = Sprint/Verizon/Telus
GSM = Unlocked/Tilt2/T-Mobile* ROMs are made specifically for one network, and a particular device. So, never flash a GSM ROM onto a CDMA phone, and never flash a TP1 ROM to a TP2.
Good luck!
sumflipnol said:
Officially, WM6.5 for the TP2 is for the Unlocked GSM European TP2. It's only for GSM networks, though (you have CDMA, so you can't flash that!).
Click to expand...
Click to collapse
Actually, the US Cellular TP2 also comes with 6.5. If you don't have a US Cellular phone though, you still can't flash it and will need a custom rom.
Wow, you guys are extremely helpful over here.
So I should flash it, or ask for a new one?
Acorns said:
Actually, the US Cellular TP2 also comes with 6.5. If you don't have a US Cellular phone though, you still can't flash it and will need a custom rom.
Click to expand...
Click to collapse
I heard about that. However, like you said, it wouldn't be great with a Verizon phone since I doubt there's an official ROM floating around (there would be a ROM dump on PPCGeeks) but why would anyone want a stock ROM to replace a stock ROM?!
AB_ said:
Wow, you guys are extremely helpful over here.
So I should flash it, or ask for a new one?
Click to expand...
Click to collapse
Ask for a new one first because we don't know if the issue you have is due to faulty hardware or software. If it's hardware, a new ROM can't do anything. If it was software or firmware(ROM), then a new ROM should be able to fix it.
If you ever need to return the phone and it has a custom ROM, you will have to re-flash the stock ROM found at thewingster. You will then have to follow the steps to return stockSPL (very bottom of the post). If you don't do these return-to-stock steps, Verizon wouldn't accept it!
Got my new one in the maill today, for free.
Thanks guys.
now.. should I flash? I want 6.5 badddd
AB_ said:
Got my new one in the maill today, for free.
Thanks guys.
now.. should I flash? I want 6.5 badddd
Click to expand...
Click to collapse
I'm guessing wait 'til the weekend arrives. Use the phone hardcore! If anything goes wrong with it for the next few days, at least you can return it again.
If you're truly desperate, I guess you could flash!
lol there's hardcore ways to use our phone? I thought it was bad-ass all around.
Is there an ETA of when Verizon's TP2 6.5 is suppose to arrive? I thought it was December/January :\
It's out... check out the thread over at PPC Geeks.
Got it. Thanks
I posted something on this in general but it doesn't get as much traffic, and I'd imagine the rom would be somewhere in here, but I can't find it. Anyway....
I used to use a mytouch 3G, but have sold it an am unrooting it before I ship. I flashed the original SAPPIMG.nbh, and now it's showing android version 1.5, and says that the system is currently up to date. Is there an easy way to manually update it to 1.6 so this guy gets the most recent version?
I'd imagine if I can find the original Tmo 1.6 I could update it, but I've spent an hour searching and haven't found it. Any advice? I'd like to ship this thing out today, if I can.
factory reset????
I did, and that brings me to 1.5, however it says the phone is up to date.
y r u selling?
Bought a Nexus one.
mikeybags said:
Bought a Nexus one.
Click to expand...
Click to collapse
Boo
Nexus two in a few months, just you wait. You'll be like "NOOO!!!!"
This really seems like one of those scenarios where the company will just keep pooping out new phones rather than upgrading the one that exists.
I'm in the same boat. Want to get my mt3g 100% stock and current. Gave it to the wife and do not want to be on the hook for tech support; so back to stock it goes of I can find the right way to do it.
http://developer.htc.com/google-io-device.html
does that help?
Here you can find the official Google rom for 32B: http://developer.htc.com/google-io-device.html
This is not your operator ROM but at least it's a stock rom without root. Hoping this helps
Peace.
psycotic11 said:
http://developer.htc.com/google-io-device.html
does that help?
Click to expand...
Click to collapse
You posted while i was reading... Doh!
http://www.androidpolice.com/2011/0...pdate-to-allow-sideloading-on-select-devices/
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
cappysw10 said:
Here come the bricks. Will you go back to stock just for a sideloading ota update when you can do this on any custom rom?
Caution swyping! Read at your own risk.
Click to expand...
Click to collapse
KonaZXIII said:
According to 99% of the threads here on XDA, if you even look at your Cappy the wrong way you run the risk of bricking it. lol
Click to expand...
Click to collapse
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Will this be rolling out to Eclair users or just Froyo? And if you're on Eclair will this OTA include the Froyo upgrade? Anyone gotten this OTA yet?
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
I was (mostly) being facetious there. I've been flashing and modding my phone for a while now and it has been next to impossible to hard brick.
well dont say stuff that can confuse the noobs please.
Anyone actually receive the update yet? Anyone who did, straight stock, rooted, any other notable differences?
Can we be connected via Wifi? Need to be on data network?
I just tried to see if it was available to me... nothing at 1pm in Atlanta
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
AT&T could f#@% up a wet dream. This could also be a plot to void your warranty. "You loaded an unauthorized app which caused your trouble, not our problem. Oh, btw, we'll sell you an Infuse cheap."
Caution swyping! Read at your own risk.
Can at least one post in any forum I've looked at site a source or show something more believable then one crappy blurry pic of a random computer screen. Heck why is it not even the whole screen? What is that a pic of, other then something somebody made up who was not even good enough to use photoshop?
TRusselo said:
umm...? if you receive OTA updates, you will already be OTA updatED to froyo. no?
so if you are still on eclair... umm.. wait!.. why would anyone still be on eclair?
oh... im scared of flash video and voice search... lol
Click to expand...
Click to collapse
Froyo was never rolled out OTA was it? Thought it was a Kies update.
I'm helping my extremely tech-illiterate friend with her Captivate and I want to figure out exactly what the details are of the various updates so that I don't scare her with anything
I'm from I9000-land and I flash every couple of days But I'm a bit unfamiliar with the Captivate scene.
No they tried an OTA but it ended up bricking alot of devices due to no 3 button support. To be honest if it is not a kies update I would never touch it. To many things to go wrong with OTA. But we will see. It will most likely be 2.2 update
my question is would it cause any issues on a rooted stock froyo ?
I was just on-line with the Technical Support chat via the AT&T site and I asked the rep if she could confirm that this OTA update was even available. And she replied that she doesn't even see this update for the Captivate on her system. Not sure what's true or not...
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
ScottyNuttz said:
I hope it's here in time for free plants vs. zombies, May 31st! I don't want my wife to have to pay. (I already have the Amazon Appstore on mine, of course).
Click to expand...
Click to collapse
Just grab it from the Amazon website and then once AT&T allows sideloading you can install the appstore and then install the game on your phone.
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
dmnall said:
At least ATT is going in the right direction, however, they need to update all their android phones to have hsupa also then having a stock phone is not so bad but I have been able to sideload with out using a computer since getting the phone enabling non market apps since the first day on my captivate *Launch date*. I have been using HSUPA ever since I started using Custom roms after the first froyo leak was released by DG.. So nothing to really effect me at all with this news, but it is good that any future phones released will have at least this enabled..
Cheers,
Charlie
Click to expand...
Click to collapse
+1
they may be late to the party but at least they deserve a lil love for moving in the right direction and at least in one regard listening to their customers. Now if they would just be smart enough to realize/admit charging for tethering is a scam and recognize the marketing bonanza "Free to Tether" would be.
TRusselo said:
FALSE!
the ONLY WAY to brick your device perminantly is to have a bad bootloader flash.
OTA will not mess with custom roms.
OTA for this update will not touch bootloaders.
i dont even have this problem or ATT but even I say thank you for not being dicks anymore ATT!!
Click to expand...
Click to collapse
Don't tell that to other members of the Galaxy S family. OTA updates have occasionally done worse.