Database Users

HTC support response to installing 3.26.651.3!!

From HTC support-
On Friday, Engadget posted an article telling users how to download and install an unofficial version of software that was found on one of our R&D servers. We pulled server offline within an hour or so of finding out about the issue, with the wrong software (anything other than 1.47.x.x) FOTA updates won’t work for you. Most likely you are on version 3.26.651.3, which is the version that got leaked. If you do have this software , Sprint has requested that we send you to a Sprint service center. There they will be rolled back to software 1.47.x.x. and FOTA will work from there. With the software versions other than 1.47.x.x to go to a Sprint Service Center. The Service Center has special tools that will allow them to help you.
Tools?!?
I have been to 2 Sprint service centers; 1 didn't know what I was talking about and the other attempted to rollback but it failed...as expected right??
I have contacted HTC about this and have yet to hear anything back...
Has anyone heard something similar?

Edit: misread...sorry

Somebody needs to leak this "tool#
Sent from my PC36100 using XDA App

SharkUW said:
Somebody needs to leak this "tool#
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ditto
10char

Actually this is great that they broke ota so least u will not unroot by mistake
Sent from my EVO using XDA App

I wonder what there response will be.

So they can role it back but we can't. has to be a way. even if we did a full install of 1.47. I am sure someone around here can find a way to help us. I hate dealing with my sprint store.

Just took mine in. Guy said he received an email from HTC the other day and it would take about an hour to roll it back. Ill ask him what he used when i pick it up. That is if it worked!

I am going to head to a sprint store later today to do this, and find out if root will work afterwards.
Also can we get a link to this post?

I bet a lot of people here would be interested in the method they are using to "roll back".

blkout01 said:
I bet a lot of people here would be interested in the method they are using to "roll back".
Click to expand...
Click to collapse
I also bet there is a Sprint Store employee on XDA that could shed some light on this.

I was at a sprint service center yesterday and they just ordered me a new evo which will be in in a few days. Never mentioned they could roll back the software. In fact he didn't even say anything to me about having superuser on my phone. With me being an android newbie I didn't know ihad to remove it before applying the ota update so now its stuck on it since I can't root now.
Sent from my EVO

Does anyone have a link to where this was stated by sprint?

zackhow said:
Does anyone have a link to where this was stated by sprint?
Click to expand...
Click to collapse
I have not seen anything publicly that states this, however, I am only relaying what was sent to me from HTC support.
I hope they are right since I have no issues with my phone and would hate to replace it over something "simple"...
GTK

Called Sprint who referred me to a service center who had no idea what I'm talking about. Maybe the only way out of this is to root and load a froyo ROM?

I don't get it - what did the leaked update break that can't be fixed by updating to the root-safe OTA release?

I agree, I'd wait for an XDA developer Sprint won't know nothing.

sjwaste said:
I don't get it - what did the leaked update break that can't be fixed by updating to the root-safe OTA release?
Click to expand...
Click to collapse
People that were not rooted and updated to the leaked ota can't update to the final build because the ota expects to patch up a 1.47 rom on the phone. Obviously it can't do that if the rom on the phone is not 1.47

Last Updated: Aug 04, 2010
Just like your computer, your phone's software needs to be updated periodically to make sure you have all the latest fixes and enhancements to keep it running at optimal performance. Follow the steps below to check your current version and perform any needed updates.
Version History
Current Version: 3.26.651.3
from the sprint website so i doubt they can update to.6

I am sure HTC will post something on their twitter account. They have already stated they are working on a fix. I think the OP was told to take it to a repair center because they may still be working on a software fix or OTA fix for this.

[Q] 2.21 upgrade via OTA for DK28 crowd?

Does anyone know if the Sprint froyo upgrade via OTA will hit folks who upgraded in December to DK28?
If not, what should one do to get the OTA update? Or will there be a update.zip with a similar upgrade process used to get to DK28?
Thanks in advance.

Search around in the future, but the chances are slim. Just hold out until a rooted flashable update.zip is released on here (XDA). It will be a matter of a day or two, or maybe only hours considering how quickly it was up for DK28.

No, you will have to be on a 2.1 ROM (preferably DI18) to get the OTA

Sprints official policy is if you take a phone in with DK28 they will revert it to DI18..but you can do that yourself via Odin..

gTen said:
Sprints official policy is if you take a phone in with DK28 they will revert it to DI18..but you can do that yourself via Odin..
Click to expand...
Click to collapse
Do they void your warranty, or give you a ghetto pass on that one...?

"Sprints official policy is if you take a phone in with DK28 they will revert it to DI18..but you can do that yourself via Odin.."
is this at any sprint store? or what's the story on this?

ungovernable1977 said:
Do they void your warranty, or give you a ghetto pass on that one...?
Click to expand...
Click to collapse
I remember reading a thread on SDX a few months ago posted by a member who worked for Sprint. Basically it stated that Sprint had no written policy about rooting or custom ROMs. I will search for it and post a link when I find it.

I dont think they would do a downgrade service, I think the policy is if for any reason, like something not working, they first Odin to DI18, then fix? But they supposedly voided warranties for that... i think theres a gray area... but dont just take it there to be reverted... Odin is easier than rooting.... just read.

nikcybag said:
"Sprints official policy is if you take a phone in with DK28 they will revert it to DI18..but you can do that yourself via Odin.."
is this at any sprint store? or what's the story on this?
Click to expand...
Click to collapse
Many Sprint stores don't have the capability to revert your phone. It probably has to be a repair store.

gTen said:
Sprints official policy is if you take a phone in with DK28 they will revert it to DI18..but you can do that yourself via Odin..
Click to expand...
Click to collapse
Can you verify this claim? I don't know Sprint's official policy on bringing a leaked os to them. Logic would suggest that your warranty is immediately void if you present them with a phone that is clearly rooted and flashed with a leaked os, asking them to hook you up with the official os. Personally, I wouldn't think for one second about bringing my phone to a Sprint store without flashing a stock os beforehand.

mattallica76 said:
I remember reading a thread on SDX a few months ago posted by a member who worked for Sprint. Basically it stated that Sprint had no written policy about rooting or custom ROMs. I will search for it and post a link when I find it.
Click to expand...
Click to collapse
Basically what it said was if anyone brings their phone in for a repair and it is running dk28 was to repair it like normal but flash it to di18 before giving it back to the customer, and no it wouldn't affect warranty. But that was just pertaining to stock dk28, now if you are running a custom rom based off of dk 28 or di18 for that matter then I'm pretty sure it voids your warranty
Sent from my SPH-D700 using XDA App

Sh0wNuF said:
Basically what it said was if anyone brings their phone in for a repair and it is running dk28 was to repair it like normal but flash it to di18 before giving it back to the customer, and no it wouldn't affect warranty. But that was just pertaining to stock dk28, now if you are running a custom rom based off of dk 28 or di18 for that matter then I'm pretty sure it voids your warranty
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No, that's not what I'm talking about. I'm saying that at the time of the post I read on SDX, Sprint had NO official policy on rooting and custom ROMs(according to the company memo in the post). So they can't flag your account or void your warranty.

cops arent supposed to pinprick your ID to signify a 'troublemaker', but they did for years. Just use Odin... read, read, read... and none of this will be relevant.

I have TEP, and on my first epic, it developed a line of pixels across the bottom side (in landscape) of magenta pixels... bright as hell. A tech told me it was cosmetic, and would cost 35 bux... nowhere in the policy does it say anything about ANY cost with TEP other than the insurance deductable, I said WTF, went to another store, they ordered me a replacement right away... Just because theres no clear policy, does not mean they cant be a **** and tell you to walk... so I wouldn't chance it. Plus, if a bunch of people with DK28 phones came in they would get sick of it real fast. It does make sense though if you did that update.zip, the original, that they kind of should give you a pass, as nothing is hacked, and it came from google, you could just say you read an article with a link to download it. XDA what? SDX who??? Still... just use Odin. If Sprint is being soft on policy about DK28, save it for those who have no other recourse... dont ruin it...
Besides, OTHER than the AMAZING sprint techs on here, a lot of those people are clowns, I would trust Odin over them any day. Especially as Epic for example, their jobs are becoming easier and easier... less real repair, more modular replacement... lowering the bar for the gig... Maybe if they told me their XDA screen name, I would trust em...

ungovernable1977 said:
I have TEP, and on my first epic, it developed a line of pixels across the bottom side (in landscape) of magenta pixels... bright as hell. A tech told me it was cosmetic, and would cost 35 bux... nowhere in the policy does it say anything about ANY cost with TEP other than the insurance deductable, I said WTF, went to another store, they ordered me a replacement right away... Just because theres no clear policy, does not mean they cant be a **** and tell you to walk... so I wouldn't chance it. Plus, if a bunch of people with DK28 phones came in they would get sick of it real fast. It does make sense though if you did that update.zip, the original, that they kind of should give you a pass, as nothing is hacked, and it came from google, you could just say you read an article with a link to download it. XDA what? SDX who??? Still... just use Odin. If Sprint is being soft on policy about DK28, save it for those who have no other recourse... dont ruin it...
Besides, OTHER than the AMAZING sprint techs on here, a lot of those people are clowns, I would trust Odin over them any day. Especially as Epic for example, their jobs are becoming easier and easier... less real repair, more modular replacement... lowering the bar for the gig... Maybe if they told me their XDA screen name, I would trust em...
Click to expand...
Click to collapse
Only one problem with using Odin to revert to 2.1: every time I do it, the accelerometer gets thrown out of whack and does not auto-rotate. This is an easy fix, although only if you are rooted. So you would have to Odin to stock, root, fix the screen rotation problem, and then un-root to receive the OTA update? Probably easier to just wait for the zip.
Or maybe the DI18 .tar I am using is messed up??

OK, if you can deal w/o the autorotate for a little bit, do it then update, as the update will wipe any settings you will make anyways. Sounds a lot like you should just wait for the special update.zip on XDA, then go from there.... would be a lot easier if you have to have a functional autorotate between Sun 11:59 PM and Noon the next day... because id bet by then, you will either have the download and be on Froyo, or it will be up here... do whatever is easiest for you. Im only going to DI18 if as soon as it gets on here, it gets rooted, EXT4'd, etc... too much... as long as theres a stock, with root only, version, I would like to try it... Im not sure I need deodexing, is that just for the themes that go over roms, or if its baked in than can it be odexed??? Just seen conflicting opinions on what to do. I really love the R&D done on here, and my phone has EXT4, but I would like to TRY the OG before it gets modified... just to see how stable it really is.... will effect how I feel about the delay a lot I think... If they put out a near 100% solid ROM (GPS fixed as stated, accelerometers, BT, any other actual function...). Still want a free USB>HDMI cable... John??? Ill blame sprint for everything....?

ungovernable1977 said:
OK, if you can deal w/o the autorotate for a little bit, do it then update, as the update will wipe any settings you will make anyways. Sounds a lot like you should just wait for the special update.zip on XDA, then go from there.... would be a lot easier if you have to have a functional autorotate between Sun 11:59 PM and Noon the next day... because id bet by then, you will either have the download and be on Froyo, or it will be up here... do whatever is easiest for you.
Click to expand...
Click to collapse
Good point. I have already reverted back to DI18 (as of last night) and rooted and fixed the rotate problem. I gotta say, dk28 was cool, but eclair absolutely flies on the epic...I forgot how fast it was (hoping and assuming the same will be true for eb13). I did this because I read somewhere that stock, rooted epics would be eligible for the OTA update, but now I'm not so sure. As you said, there is so much conflicting information out there!
But when all is said and done, I will probably just Odin again on Sunday night and wait and see what happens, both here and OTA. Waiting for devs to do their thing is probably the easiest, most pain free way of doing this.

yeah, as long as theres an untouched, well maybe just rooted version... as stated in another thread, may be a good idea to see what stock really looks like before the Devs break out the scalpels.

djbacon06 said:
Good point. I have already reverted back to DI18 (as of last night) and rooted and fixed the rotate problem. I gotta say, dk28 was cool, but eclair absolutely flies on the epic...I forgot how fast it was (hoping and assuming the same will be true for eb13). I did this because I read somewhere that stock, rooted epics would be eligible for the OTA update, but now I'm not so sure. As you said, there is so much conflicting information out there!
But when all is said and done, I will probably just Odin again on Sunday night and wait and see what happens, both here and OTA. Waiting for devs to do their thing is probably the easiest, most pain free way of doing this.
Click to expand...
Click to collapse
Stock rooted dg27 epics received the di07 and di18 ota without a problem, but they lost root after the fact. Not really an issue though.
Sent from an Epic I haven't bricked yet.

mattallica76 said:
No, that's not what I'm talking about. I'm saying that at the time of the post I read on SDX, Sprint had NO official policy on rooting and custom ROMs(according to the company memo in the post). So they can't flag your account or void your warranty.
Click to expand...
Click to collapse
I can corroborate this.
I've taken my epic (running Bonsai) in to the Sprint repair store because the touch screen stopped responding accurately, they replaced the screen and gave me the phone back with all my data and ROM intact. Never even mentioned it...

Worst AT&T Tech chat ever, but revealed some strange things going on with 1.83

EDIT 2: It appears to be up OTA so connect to wifi and check for an update!
Edit for those who just came here to figure out what was going on with 1.83:
It would appear that some sort of error occurred in which the beta of 1.83 was released OTA to a few people and to even more through the computer connect update software. This is why people were reporting that they had had success downloading the new update. However it was not available for everyone and appears to have been pulled completely. Things were made more confusing because AT&T and Motorola both appeared to make some false claims that the new update was beginning its release on April 29th. However this was a mistake and they later retracted their claims either by deleting the comment altogether or saying that they meant that the beta would be released to limited amounts of people at that time. This appears to be the cause of all of the confusion, but the bottom line is that the official update is NOT out yet, and if you want the 1.83 beta that others have gotten, check around, it isn't too hard to find!
Original post:
So I came across an AT&T answers page actually listing 4.1.83 on the site which said it was available and all I had to do was connect to wifi and check for updates to get it.
So I think "SWEET!" and try it, but still no luck
By this time I figure alright if AT&T is listing this but it's not up may as well go ahead and bother their tech support for a while and see if I get any answers
They take a LONG time to answer my question and eventually tell me that there is no 1.83 update. To which I reply "Excuse me, BS, here is exactly what YOUR site says" -copy, paste, and post link to it-
They take a long time, then completely ignore it and tell me to access my phones settings and tell them what software version I am running.
Meanwhile I get a little suspicious about whats going on and open a new window and follow the link I sent them.
It had been edited WHILE I was talking to them! The 1.83 part had been completely taken out. All that was left was the 1.57 update. The tech support person continued to play dumb and tell me there was only a 1.57 update and that I could contact motorola if I had any more issues.
I'll post a screenshot of what the site said when I accessed it this morning. I don't know if the info on that page is old news to these forums or when it even went up, but At&T certainly has their heads up their asses.

Oops, forgot about that mention. Pay no attention to the man behind the curtain.

Did you tell them there are even websites with benchmarks out there like
Anandtech?
http://www.anandtech.com/show/4304/att-update-enables-hsupa-on-motorola-atrix-htc-inspire

wah
----------------------------------------

Very weird....its because they are getting ready for gingerbread. Oh wait, nevermind, just wishful thinking.
Sent from my MB860 using Tapatalk

I talked with them a bit more after posting.
I told them that this was not a Motorola issue, and that I now wanted to know what had happened with the AT&T site and that I saw that it had been edited. They continued to post more Motorola contact info and asked if they could help me in any other way.
I told them that they could start by actually reading what I was typing to them, and repeated that the page had been edited. I am subjected to more waiting until finally the associate tells me they "didn't see" the second update before, but now they know what I am talking about. The page is still edited so I have no idea how they saw it right then... but yeah.
They then ask me to connect to wifi and try to perform the update. Told them I already did. They then say, that maybe AT&T recalled the update and tell me to wait. I wait. Then they come back asking if I have contacted motorola, I tell them no. They then link me to a post in motorolas forums and tell me to check there.
The thread I am linked to is merely people complaining about the same page on AT&T that I was referring to in the first place... with no answer on it as to what was going on, when I point this out the associate remains silent. I continue to do other things on my computer checking back every few minutes. After 10 minutes of silence I go ahead and tell them that I could see that they were not even going to try to help me and closed out the conversation.
Disappointing, though I am now reasonably certain that I am the reason the page got edited haha

OTA
So do we know if anybody has gotten the update OTA or has it all been "self-help" installation. AT&T changing their website makes it appear delays to OTA update. Question remains, is it becuase of AT&T or Motorola?

That's classic, I wonder what they would say if I walked into a store and asked about the 1.83 update, especially since I have it on my phone already so I can prove it exists.
Sent from my MB860 using XDA App

soxfan37 said:
So do we know if anybody has gotten the update OTA or has it all been "self-help" installation. AT&T changing their website makes it appear delays to OTA update. Question remains, is it becuase of AT&T or Motorola?
Click to expand...
Click to collapse
My guess would be att, since Motorola had it officially on one of their websites for a USB link update
Sent from my MB860 using XDA App

If you check the motorola owners forums, they say the update hasnt officially been publicly released although, many ppl besides beta testers were able to snag the update before it seemed to have been pulled. You can always download the 1.83 SBF thats floating around and flash to it.

Nothing new here. AT&T sticking thier heads and the sand and ignoring the customer. Can not/will not even respond to direct legitimate questions. Maybe it is time to try to get their attention another way. here is the link where you can post comments to the FCC concerning their attempt to monopolize. http://fjallfoss.fcc.gov/ecfs/
I think everybody that has an issue with at&t's customer support, rate plans, crippling devices, false advertising, etc., that have tried to get answers or support with no satisfaction should make these issues known. If the congressional reps on the committees start asking the same questions we have, then maybe, just maybe, att will understand we are customers, and not just a source of income. Maybe I should start a thread just for this so we get as many people as possible to send their thoughts along.

I've been running 1.83 since the 29th and I'm not a beta tester. I actually got it by downloading the Motorola software Updater from here http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX(TM)%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download/SoftwareUpdateforATTATRIX4Gversion.4.1.57.pdf.
All I did was plug my phone in and it looked for an update for like 5 minutes then said there was one available and asked if I wanted to install it (Of course yes) 15 min later it was done. I actually flashed back to 1.26 3 times and updated to 1.83 like this because I messed up root (Come to find I just needed gingerbreak). Some people can't get it so I'm not sure if they took it down from moto or what the deal was. Everything on the page says 1.57 but it still let me update to 1.83 multiple times so I donno.

Clienterror said:
I've been running 1.83 since the 29th and I'm not a beta tester. I actually got it by downloading the Motorola software Updater from here http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX(TM)%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download/SoftwareUpdateforATTATRIX4Gversion.4.1.57.pdf.
All I did was plug my phone in and it looked for an update for like 5 minutes then said there was one available and asked if I wanted to install it (Of course yes) 15 min later it was done. I actually flashed back to 1.26 3 times and updated to 1.83 like this because I messed up root (Come to find I just needed gingerbreak). Some people can't get it so I'm not sure if they took it down from moto or what the deal was. Everything on the page says 1.57 but it still let me update to 1.83 multiple times so I donno.
Click to expand...
Click to collapse
when did you do this?

gammite said:
when did you do this?
Click to expand...
Click to collapse
I'm pretty sure it was the morning of the 29th.

It was working, but has since been pulled. I saw both the AT&T page as well as the Moto update. Neither are working now.

Ima stop by the store and inquire about it there, see how interesting that conversation is as soon as I'm done at the gym since there's an official att store right next door, talk about convenient.
Sent from my MB860 using XDA App

Same here...I got the update from the moto site on the morning of the 29th.

Well, that turned out to be as pointless as I expected it to be, no one had any clue what I was talking about or why the update would be there one minute then all traces be gone the next. Their only suggestion was maybe there was a bug in it.
Sent from my MB860 using XDA App

Maybe there going to update to unlock unknown apps so u can install Amazon app n other programs.
Sent from my MB860 using XDA App

From what i've read, i'm guessing the 1.83 update is still in beta testing, but for some reason someone in ATT's dev team messed up and relayed it as "release" to another ATT team and motorola, who put it up on their websites as available for download without further questioning. If anyone got it through OTA, they might have been part of the first wave before someone in ATT realized the mistake and pulled the update out.
Then ATT decided to go for a "what update?" policy instead of "whoops."

I found a TMO store with the Gingerbread SDCARDS but>>

I found a store in my town that had the SD Card gingerbread update so I went there today. While I was waiting to be seen, I saw a My Touch 4g get updated using the SD Card by a customer service person. It took about 10 minutes. I was encouraged to see how quick it took. Now it was my turn. The customer service (C/S) who assisted me was a former tech support person for Tmoble who was now working in a store. She was very knowledgeable and very nice. She took my sdcard out and put in the gingerbread sdcard. The update started. There was about 10 steps that the update had to go through. The first step was 'bootloader'. The C/S said that this was the first G2 that she has done. She said she had done her My Touch 4g Slide and the update went smooth so again I was encouraged. I was happy to not have to wait for the OTA.
Well the update started on the first step and 45 minutes later, it was still on the first step. So she stopped the update to allow me to do a factory reset of my phone and I did so. The store had two gingerbread sdcards so she tried the second one on my phone. I went to starbucks for coffee and 20 minutes later, the update was still stuck on the first step. So, she told me that there was something wrong. She asked me if I had done anything to the phone? I said no. I told her that this G2 was a replacement phone that I had just recieved about a month ago because my first G2 stop charging. Well she gave up and so did I.
I called TMO C/S and they said that they had no record of the G2's having problems with the store gingerbread sdcards. He first asked me if I had any third party apps on my phone, I said no. They told me that the cards did not come from them but they came from HTC. So, I called HTC. The guy there commenced to reading the press release that we all have read a thousands times about being able to go to the store and get gingerbread after August 6. He also told me that he had no record of G2's having problems getting the update at the stores. I asked him if the same SD Card was to be used on the My Touch and on the G2? He said that he did not know and yes he was tech support . He advised me to call HTC headquarters at a different number and ask them that but they were closed.
I know some of you are gonna tell me to do the update myself with the links that are eveywhere on the web. Well, I'm not gonna do that. Tmo and HTC gotta get it together. They are running a business and they MUST do what they say they gonna do. I know that TMO don't have to provide any updates, I know this but they are offiering the updates and they tell us to wait for the OTA or go to a store after the Aug 6. Well I did that, I got nothing. By the way, there are three TMO stores in my town and only one had the SDCARDS. Peace

Well they DON'T know what they are doing otherwise the custom rom community wouldn't be as big as it is if they were able to get anything right themselves. So your **** out of luck. Let us know when you want a good working phone.
Sent from my HTC Vision using XDA Premium App

xsteven77x said:
Well they DON'T know what they are doing otherwise the custom rom community wouldn't be as big as it is if they were able to get anything right themselves. So your **** out of luck. Let us know when you want a good working phone.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
That's being kinda rude. If he doesn't want to root or apply manually he doesn't have to. He's just telling us what happened. No need to be rude.
OP, if the SDcard update didn't work, you should wait and see if you can get the OTA. If the OTA isn't working for your device either, you should contact T-mobile and express that you'd like a phone with 2.3 or will properly update to 2.3, assuming that you don't want to root or manually apply the update yourself.

That's ridiculous....minus the rude part, it is true tmobile and htc would much rather see you buy one of their newer phones and renew your contact than get a good working update. Try custom roms if you can...the vision is one of the easiest to root and stable when rooted and there are hundreds of roms around, I'm sure theres some rom gingerbread flavored you'll like.
Sent from my HTC Vision using XDA App

Whether you choose to root or not, it's your device and you can do what you want with it. If you want the stock T-mo experience, then they should give you what they promised you. Good luck!

While I disagree with you rooting (many of the problems here are people who shouldn't even need to root in the first place, it's not for everybody), I don't understand why you wouldn't manually update. Download the file, name it update.zip, put on your sd card root, press a few buttons, done!
Sent from my T-mobile G2 using Tapatalk

Nospin said:
While I disagree with you rooting (many of the problems here are people who shouldn't even need to root in the first place, it's not for everybody), I don't understand why you wouldn't manually update. Download the file, name it update.zip, put on your sd card root, press a few buttons, done!
Sent from my T-mobile G2 using Tapatalk
Click to expand...
Click to collapse
Exactly, easiest thing to do
Sent from my T-Mobile G2

I may have the answer. You said that you had received the phone as a replacement. Did it already have gingerbread on it? Remember that some of the phones people were getting as replacements had gingerbread 2.3.3 on them and if your phone was one of those you can't update from 2.3.3 to the final release which is 2.3.4. Just a thought.

rkwhyte2 said:
I may have the answer. You said that you had received the phone as a replacement. Did it already have gingerbread on it? Remember that some of the phones people were getting as replacements had gingerbread 2.3.3 on them and if your phone was one of those you can't update from 2.3.3 to the final release which is 2.3.4. Just a thought.
Click to expand...
Click to collapse
The replacement phone I received was 2.2.

xsteven77x said:
Well they DON'T know what they are doing otherwise the custom rom community wouldn't be as big as it is if they were able to get anything right themselves. So your **** out of luck. Let us know when you want a good working phone.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I am very familar with rooting. I rooted my G1 within 5 months of having it and it stayed rooted for a year and half more until I retired it and got the G2. The reason I chose not to root my G2 was because I did not want to be contastantly flashing and removing roms and fixing issues. I got tired of baby sitting my G1. I have other things to do.

brownbomba said:
I am very familar with rooting. I rooted my G1 within 5 months of having it and it stayed rooted for a year and half more until I retired it and got the G2. The reason I chose not to root my G2 was because I did not want to be contastantly flashing and removing roms and fixing issues. I got tired of baby sitting my G1. I have other things to do.
Click to expand...
Click to collapse
So... you tried a bunch of half-baked "roms" made by a bunch of kiddies who don't know what they're doing and found it a royal PITA. Ever heard of a "superstock" system image? Its basically the factory image with a few goodies added in, specifically ROOT. It doesn't require any "babysitting", but opens the door for some amount of enhancement, like the ability to change your hosts file (usually used to block spam), or the ability to delete useless cruft from the system image (i.e., you don't like the gmail application? Delete it.). You don't have to go with a full out special brownies system, but it is nice to at least gain control of what you own.

The store I work at finally got the SD cards to update, but the G2 update will not install.
The update works fine on the mytouch 4g, so the card is goood.

Well that sucks. Hope you get the issue resolved soon.

Looks like I figured it out. The G2 would only update if the battery was %100 charged.
Any less and it would freeze during the update.
Now that I know the update works I'll try and post the files when I get home.

Thanks atlp99!
I'd really like to get my hands on that file. I assume it is a pc10img.zip ? Seems like this is the best solution for those of us running the 2.3.3 leak...

G2 2.3.4 update pc10img
Here is the G2 update off of the micro sd cards the stores are receiving.
https://rapidshare.com/files/3796067356/PC10IMG.zip

Works for 2.3.3 leak!
Just used this file to update my G2 running the 2.3.3 "leaked" gingerbread rom. No problems. Just slip the file into your root directory, and hold the volume down while turning the phone on. Piece of cake. You will lose your application data, of course, but you'll be updated...

atlp99 said:
Here is the G2 update off of the micro sd cards the stores are receiving.
https://rapidshare.com/files/3796067356/PC10IMG.zip
Click to expand...
Click to collapse
No less than a day after I suck it up and downgrade my G2 to 2.2 so I can update (using update.zip) to 2.3.4 does the PC10IMG.zip get posted. My lack of patience kicked in. Nevertheless, thank you for posting this!

Blink37x said:
No less than a day after I suck it up and downgrade my G2 to 2.2 so I can update (using update.zip) to 2.3.4 does the PC10IMG.zip get posted. My lack of patience kicked in. Nevertheless, thank you for posting this!
Click to expand...
Click to collapse
Hopefully a dev can finally make a debloated with goodies added rom! Please god!
Sent from my HTC Vision using XDA Premium App

atlp99 said:
Looks like I figured it out. The G2 would only update if the battery was %100 charged.
Any less and it would freeze during the update.
Now that I know the update works I'll try and post the files when I get home.
Click to expand...
Click to collapse
Having my battery at 100 percent did not work for me. The update still just sat there looking at me. This is crazy buy while I was trying to figure out what the problem was. I decided to do checkin and about 5 minutes later, I got the updae OTA

So why us Sprint detecting I'm in mikfroyo 4.62

Anyone know why when I tried to open a network support ticket they are detecting I'm on a mikfroyo rom. I changed Roms so many times the past 6months.. so what the hell is up with that:
They even said you have to be on a official Rom.. man how they detect this info is pretty funny. And how wrong it is.
But any way to fix that issue
Sent from my PC36100 using XDA App

Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...

I don't need support. I do wish to inform them of their network problem here... If so I have 8 other people with Sprint who are official.. who can report the network problem aswell ... Why would I need support if my phone is perfectly fine. And besides the fact I'm not running the Rom they are indicating I am...
Sent from my PC36100 using XDA App

Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.

nemoid said:
Why do you think they would give you support when you voided your warranty by rooting and installing another ROM?
I mean seriously...
Click to expand...
Click to collapse
You only voided your warranty with HTC, not sprint. I've taken my rooted/S-OFF device many times and have talked to the store reps and they have no policy against rooted devices. There is stores that will give you a hassle just to be lazy, meanwhile other stores will ask you to simply flash back to stock to help narrow down issues caused by software or hardware.

Oh so a version from stock that just has apps removed that ate considered bloated. So that can be a phone error. Dude I've flashed many roms kernels and radios and its the network. I'm not after phone support. I don't need a warranty on my Damn phone but I pay them for service via their towers if they have issues with it then they should fix their network problems. I will pay insurion if I have phone issues its why I have them.
Sent from my PC36100 using XDA App

The guy just said to install a stock Rom and give him info. The guy was like okay 3rd party. You need to install stock . But he did agree there is probably a problem in the area.
Sent from my PC36100 using XDA App

ANyways the guy said I should keep stock until testing is done well. Im on a modified stock rom etc (testing this rom out). Anyways is there a way to show them my software/build number as stock or whatever to fool them when i re provision it to update their system?

nemoid said:
Again... think about it for a little bit. They don't know if you have 8 other people who are experiencing they same problem you are.
They're not going to waste their time with a problem that could be the result of a modded phone.
Click to expand...
Click to collapse
no they are not wasting their time providing CUSTOMER support to a paying CUSTOMER

How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App

culua said:
How can Sprint finds out if your rooted with a custom Rom? Even they never saw the phone?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I used to Run Mikfroyo but the thing is I don't know how they know I was on a custom rom. Maybe when provision your phone it sends that data. Now I'm On a different rom but i was unaware how he knew. The guy *PinkElmo* basically just said to go back to stock ROM for the duration of the testing (sounds like he not only not has a problem with it but sounds like he uses custom as wellXD).
I'm still puzzled as to how they found out...

I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App

culua said:
I also currently using mikfroyo 4.61. But I didn't start rooting after a month signing up.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had to provision a few months back though... But It Got me wondering. I have been downloading a stock rom at 199mb it should take roughly 2-8 hours on the Sprints NOW DialUp Network

Sprint has a program called OMA-DM. This program has all the information from the status section of your device. When I worked for sprint we would have customers update their data profile, this would send the information to the tool. The rep can then see what rom you are on. However this did not work on AOSP roms since they do not update the profile.
If you want to fool sprint update your profile under a stock unmodified rom, then flash to AOSP, the info for the sense rom would be still in the system.
Furthermore they can see if you have updated the profile, so if you tell them that you did they will be able to see if you actually did or not.. They are also able to view all the transactions with dates and times between your phone and the tool.
My advise to you is to suck it up and run the official rom until the testing is over, usually about a week.
Also sprint has no control over a custom rom, so they automatically have you update profile and firmware to the current version to ensure that the phone is working to their standards and things that they have control over.
TL;DR - Quit complaining and use a stock rom so sprint can do their testing.

The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...

Pao23 said:
The complaining in this thread has me puzzled. Run a stock Tom for them to test, reinstall favorite Tom when done...
Click to expand...
Click to collapse
is your favorite "Tom" a "Tom Collins"? hahaha, sorry. i had to.

Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App

I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics

cmsjr123 said:
Thanks and for data profile. Just the one under updates? If so it would have shown mikg if clean rom I got a download of stock and was going to flash it when i can before Tuesday since Monday is a holiday...
Thanks for informing me how they detect what Rom your on.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the one under the updates.
scottspa74 said:
I imagine sprint can know quite a bit about your phone. When I had my diamond, (or maybe it was my Evo, I forget) something wasn't working right. I got on the phone with a tech, and he proceeded to to operate my phone while I was holding my phone. I could see the screen clicks, and him going from one menu to another, operating my phone remotely. Blew me away.
As for the monitoring SW mentioned earlier in this thread, does it read build prop values? Cuz I'm guessing that's how they get your device info.
Lastly, post 2 and 3 about not expecting sprint to work on/assess your rooted phone. BS. Sprint has given mixed signals about this. I know there have been internal memos released stating they now will honor rooted phones. I think lazyness is the culprit when a comes to CSRs or techs rejecting for root. I've always taken in my rooted phone and put a stockish rom on it first, when I have a hardware problem (blown speaker, broken screen, etc.)
sent from xda app on drews ics
Click to expand...
Click to collapse
They used an application call LogMeIn Rescue. It gives them the ability to remotely view/control a pc, windows or blackberry phone. Its actually a lot easier to do it for a customer more often then trying to walk them through it.
Yes the information displayed in the about phone section is stored in the build.prop.
As for the software; software plays a factor in how the device operates and communicates with the network. Sprint has designed the stock software on their devices to their standards. They know their software and how it works. Now take a custom rom, one that has be frankenstined together. How do you expect a company to properly troubleshoot and diagnose a problem that could very well be related to the customer software?
I totally agree with the laziness part on the Tech Reps, after working with the company for several years, Id have to say most of the reps were less educated or technically minded about the device that they were working with. I could not tell you how many times I would hear customers complain about the Tech Reps.
Going to a hardware issue, Custom software would not break the screen, blow a speaker, or otherwise cause physical damage to the device (with the exception of a battery). So these should have no effect on hardware warranty's or exchanges.