Related
Long-time Android user here, I have a T-mo MT3G. Rooted long ago and flashed many ROMS.
I also have a Sprint account and am eligible to upgrade so I want to buy an Evo.
The sprint online virtual store seems to be out of stock, but some of the local stores have them.
Can you please give me a strategy for going into the store and walking out with an Evo that is rootable? I read that the latest OTA update has a lock on it that prevents rooting. What should I look for to determine if the Evo they want to sell me is rootable?
Is it even possible? Will they let me boot it to check software version before buying it? Is there any other way to tell?
Also can you fill me in on Hardware versions? I read about light leak and maybe some other problems. What should I look for on the phone to tell which version it is? And what are the differences between hardware versions?
Thank you!
K, there are 3 versions really. 002's I think are all Novatec screens, 003's can either be Epson or Novatec. The Novatec's are prone to the screen separation issue that people have been complaining about and that HTC says is just cosmetic. I replaced my Novatec and happened to get a 003 Epson that did not have the latest OTA update installed.
So, what it comes down to is you ideally want an Epson without the update. There's really no way to tell if it's going to have the update or not without booting it up, and good luck with that in the store because they have to sell it once you open it. If you get one that had the update applied, it's just going to take time before it can be rooted, they're working on it as we speak, you can check out a thread in the developers forums.
The other way to tell if it's an Epson is the back of panel. Check the video to see what I'm talking about. The one on the left is an Epson. Right at 4:07 he starts talking about the "pearlies" on the back. The Epson screen models have a flatter black back, whereas the Nova's have a sort of lighter look to them. I personally like the Epson more, it also feels more "rubbery."
If you buy online, you'll likey get a phone that has the update applied. If you buy from BestBuy you're likely going to get a Nova screen. I think the Sprint stores have the latest inventory, but most of them were shipped on Monday, so today's stock are unlikely to be updated and likely to be Epsons, so that's your best bet.
I exchanged my phone yesterday, got an Epson screen without the update, so I'm happy. Hope this long and exhaustive post helps.
Sirchuk said:
K, there are 3 versions really. 002's I think are all Novatec screens, 003's can either be Epson or Novatec. The Novatec's are prone to the screen separation issue that people have been complaining about and that HTC says is just cosmetic. I replaced my Novatec and happened to get a 003 Epson that did not have the latest OTA update installed.
So, what it comes down to is you ideally want an Epson without the update. There's really no way to tell if it's going to have the update or not without booting it up, and good luck with that in the store because they have to sell it once you open it. If you get one that had the update applied, it's just going to take time before it can be rooted, they're working on it as we speak, you can check out a thread in the developers forums.
The other way to tell if it's an Epson is the back of panel. Check the video to see what I'm talking about. The one on the left is an Epson. Right at 4:07 he starts talking about the "pearlies" on the back. The Epson screen models have a flatter black back, whereas the Nova's have a sort of lighter look to them. I personally like the Epson more, it also feels more "rubbery."
If you buy online, you'll likey get a phone that has the update applied. If you buy from BestBuy you're likely going to get a Nova screen. I think the Sprint stores have the latest inventory, but most of them were shipped on Monday, so today's stock are unlikely to be updated and likely to be Epsons, so that's your best bet.
I exchanged my phone yesterday, got an Epson screen without the update, so I'm happy. Hope this long and exhaustive post helps.
Click to expand...
Click to collapse
Yes thank you for taking the time to answer! Now all the local stores are out of stock too.
I got one.
Very happy in my pants.
Best Buy was out on Saturday, but today they had three new ones, and I got one with software number 1.32.651.6.
I told the girl not even to open the box, she really wanted to.
When I got home and turned it on it wanted to update to the new OTA, so i said 'NO'!
Lol.
Need to root and check HW version.
NAND rooted, brutal
Wow, that was an experience. This is the third android I've rooted.
It was quite the trying experience. But got it done.
Someone needs to streamline the instructions.
Installed Damage control.
Only took about 4 hours.
I have a 002 Evo from launch day. It's started missing calls. Like no missed call notification, nothing in my call log. I'm afraid all I can do is swap it out under TEP. If anyone has any suggestions other than replacing it, let me know! Of course I've rebooted my phone. I know most of you will be jealous...but I have my choice of hardware versions for my replacement phone. (One of the techs in my Sprint store is also my friend.)
Those of you that have 004s, are you happy with your camera, and the ROMs you can run where your camera works? I'm rooted and currently running Fresh 3.5.0.1, but want to play around with Shinzul's 4g CM, Miui, a gb ROM, and maybe an HD or Z ROM. I have run Miui, as well as CM in the past. Should I ask for a 002, or will I be able to use a 004 with the camera working?
Also, suggestions for backing up and restoring to the new hardware phone would be appreciated. I'm thinking of nandroiding and removing the wimax.img before restoring. Will that be ok on new hardware, with new H-boot and all? I have H-boot .76, running the 11.19 radio (have tried going back to the original, no better), the original wimax radio, and PRI 1.34_003. Fresh 3.5.0.1 is based on the latest OTA 3.70.651.1.
Thanks for any advice. I did try to search, but since my questions are pretty hardware specific, it was difficult to get relevant hits.
Happy with 0004... but I'm rooted with stock ROM.
Sent from my PC36100 using XDA App
I know most of you will be jealous...but I have my choice of hardware versions for my replacement phone. (One of the techs in my Sprint store is also my friend.)
Click to expand...
Click to collapse
I'm not so sure about this. To sprint, an Evo is an Evo. I dont think the techs can "choose" what version to order.
And honestly, I've had a version 2, 3, and 4, and all of them have been exactly the same. Even with the camera change with the 04, I cant tell the difference at all.
I'd go with 003, no question. You have more kernels to choose from.
_MetalHead_ said:
I'd go with 003, no question. You have more kernels to choose from.
Click to expand...
Click to collapse
Even with some of the 003s having the newer camera? Thanks for your help.
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
_MetalHead_ said:
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
Click to expand...
Click to collapse
Good point.
smarcin said:
Good point.
Click to expand...
Click to collapse
+1 don't go for a four. Still some problems with custom kernels like others said.
I've got a hardware v3 with the new camera. I've run the newest Fresh rom, myns, caulks, cm 6.1, Cm7, and evervolv. As far as kernels, I've played with most all of them. I haven't experienced any issues, camera or otherwise after HTC released source for 15. I'm pleased with the performance out of it, as far as smoothness and quickness goes.
*edit* I came from a launchday v2, got this one under TEP, new not refurb.
Sent from my PC36100 using XDA App
_MetalHead_ said:
I didn't even think about that. I guess it's a crap shoot. I wouldn't go with 002 for the sole reason that they are older (I'm weird like that) and if you go with 004 you are guaranteed to get a phone that is not compatible with every kernel out there. If you go with 003 at least there is a chance of getting a normal one and not a later one with the new camera.
Click to expand...
Click to collapse
Ive got an 003. What are the benefits to the 004 camera over the 003? Thank you
tailsthecat3 said:
Ive got an 003. What are the benefits to the 004 camera over the 003? Thank you
Click to expand...
Click to collapse
I don't think there are any benefits at all. It's just different, not any better or worse.
Thanks....
Kinda funny no one even mentions which screens anymore. Remember that whole argument? Novatech vs. Epson?
vinscuzzy said:
Kinda funny no one even mentions which screens anymore. Remember that whole argument? Novatech vs. Epson?
Click to expand...
Click to collapse
Yeah, the Epsons suck and I got stuck with one
it's not a matter of what you go with, it's a matter of what they give you. you dont really have a choice unless you buy one used
I have the 0004 HW and I don't know what all the fuss is about. I haven't really had any trouble getting a kernal I want that works with this HW. If it is a Sense rom, run a Netarchy Kernal, they all support 0004 anymore, and if it is an AOSP rom, run Savaged.Zen kernal. They support 0004. I am running CM7+4G with a savaged.zen kernal, (I KNOW I AM SUPPOSED TO RUN THAT KERNAL THEY SAY I HAVE TOO, BUT YA KNOW WHAT? THE SAVAGED.ZEN KERNAL WORKS BETTER, AND 4G WORKS!!!!)
I would have said 2 months ago when I got an evo, that the 0004 HW was crappy as noone supported it, main reason I kept to Fresh. But now, most kernals I like support it, and except when they had CM6.1.2+4G, I haven't had a rom not work with the camera.
I think you just get what you get. I got a replacement last week, its an 003. ##786# tells me it was activated in july and refurbed last month.
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
eraste said:
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Assuming the screen works, yes, you can tell with a magnifying glass or a SMALL drop of water on the screen. An LCD will show colored squares. The AMOLED the dInc uses will show what's called a RBGB pattern (red, blue, green, blue pattern) when viewing a white screen. Also, the backlight will be seen through a black screen on an LCD, which will be very obvious in a dark room. Again, this is assuming the device works correctly.
Easy way to tell: Hardware version 002=AMOLED, 003=SLCD.
Sent from my Droid Incredible running a random CM7 nightly.
Thanks guys so hardware =0002 for me take that to mean I have the older incredible amoled screen which is easier to return to stock right?
Sent from my ADR6300 using XDA App
take out your battery. ADR6300VW = amoled = ADR6300VW2
ADR6300VW3 = SLCD
vassskk said:
take out your battery. ADR6300VW = amoled = ADR6300VW2
ADR6300VW3 = SLCD
Click to expand...
Click to collapse
i didn't know this. thank you.
Just a note on most refurbished phones that information is not there, they placed a refurbished in " " sticker for me it says Philippines and the only information on the sticker is MEID number and couple barcode numbers.
However if you have one that hasn't been refurbished Ie: you never took your old one to verizon for a replacement or through an insurance company claim then you should have factory sticker(info) under battery.
Sent from my ADR6300 using XDA App
eraste said:
Just a note on most refurbished phones that information is not there, they placed a refurbished in " " sticker for me it says Philippines and the only information on the sticker is MEID number and couple barcode numbers.
However if you have one that hasn't been refurbished Ie: you never took your old one to verizon for a replacement or through an insurance company claim then you should have factory sticker(info) under battery.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ i wonder why they do that...
NP wolf!
No clue, I knew that trick by the time I got the phone in the mail that was the first thing I looked for lol. When I saw that refurbished sticker I was like da**! Lol
Sent from my ADR6300 using XDA App
SteveG12543 said:
Easy way to tell: Hardware version 002=AMOLED, 003=SLCD.
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
This doesn't seem to be true anymore if you flash the new 2.3.4 leak... I've had my inc since the day it came out and it always used to say 002 for the hardware version, but since I've flashed the new 2.3.4 leak, it now says hardware version 003... can anyone else confirm this?? FYI I flashed the one JoelZ posted
I would imagine that's because the GB leak has a sprint build.prop. Unless you changed it yourself or whoever put the rom out changed it, it will show some incorrect information.
taihard said:
This doesn't seem to be true anymore if you flash the new 2.3.4 leak... I've had my inc since the day it came out and it always used to say 002 for the hardware version, but since I've flashed the new 2.3.4 leak, it now says hardware version 003... can anyone else confirm this?? FYI I flashed the one JoelZ posted
Click to expand...
Click to collapse
Huh... That's shady lol. Weird.
Sent from my Droid Incredible running a random CM7 nightly.
msg deleted
I know I have an AMOLED screen.
But I've been seeing hardware = 0003 under MIUI ROMs and Nils' Gingerbread too, so I doubt it has anything to do with Sprint-related origins.
Hardware version 2 is Amoled and version 3 is SLCD
eraste said:
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
jpradley said:
I know I have an AMOLED screen.
But I've been seeing hardware = 0003 under MIUI ROMs and Nils' Gingerbread too, so I doubt it has anything to do with Sprint-related origins.
Click to expand...
Click to collapse
On MIUI, the settings menu doesn't even show hardware version. Only place I've seen it is in one of setCPU's "about" menus, and it was reported 002 which is correct. As for nil's rom, I thought it was based off a sprint rom but that could be incorrect.
You have to look at your stats when your phone is bone stock....
0002 is AMOLED and 0003 is SLCD. However when you flash a new rom, etc whatever that rom was built on is what will show up under hardware version. So if you looked and wrote down your stats when your phone was stock and it is hardware version 0002 its AMOLED and 0003 is SLCD.
I am using Nils gingersense 3.0 ver 1.6 and under the hardware version it says 0003 but I know mine is the older AMOLED 0002, And when I flash my " stock with root" backup my hardware version shows me 0002 like when I first powered it on from verizon.
Screen size is another thing I noticed will be wrong when flashing custom roms etc. Flashed one that had my screen size at 4.3" lol I got an incredible so I know thats false... My advice to anyone would be to record all your information on a lil notepad before changing anything incase you forget.
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.
rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.
JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
They all say 'Android is updating' everytime you power the phone on ;-)
oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.
drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.
I heard that they are updating the baseband, not the software version...
I'm a XDAer in Asia and I happen to live in Taiwan at this moment
from what I've seen from Taiwanese blog posts Taiwan is now under the crisis of the most outrageous $ 800+ phone deaths
As you can see from the video I post below:
currently unable to post any links.........sorry
Note 7 will constantly freeze then reboot, some have issues happening several times a day
there is currently a thread in a Taiwanese reddit regarding this issue, some people are already frustrated by this issue but is unable to exchange for a new device due to the shortage of supplies.
Does anyone know whether this is a hardware fault or a software fault, because a friend of mine had the same issue and he has already updated to the latest firmware. I would like to grab one too if this issue got solved, which IMHO might thake several months.
I know a lot of other regions are not effected by this issue, please help.
Singapore is affected by this issue too
Is this the F/FD version having this issue?
Yeah it's seems to be happening to a lot of people in Australia too. Mine has been fine but few others are affected
Could it be related to device/battery overheat due to the ambient temperature?
Sent from my SM-N930W8 using Tapatalk