Related
Hi guys,
Longtime iPhone user here, looking to defect. After being inspired by a poster over at The Verge, I embarked on a 30 day trial of a One X yesterday. I've been wanting a nice big screen for a while, and the One X is just all kinds of hot.
Anyhow, I'm still on the fence with a straight up stock device. I suspect I might change my tune with a custom ROM, but I'm now under the impression that a custom ROM is not possible without first unlocking the bootloader. Is this a correct statement? Things have been changing so much over the last week or two with the One X, I'm having a hard time deciphering a clear answer to this.
I'm comfortable with rooting (did this last night) and perfectly comfortable with the process of unlocking the bootloader. But the unlocking scares me a bit, as it doesn't appear to be completely reversible. This doesn't jive to well with my "30 day trial" plans if I decide to return the phone. Seems best I can do is get it back to a "Re-locked" status, which I'm thinking might not be ideal if I decide to return the phone. Who knows, AT&T may not care (or even check), but I wouldn't be surprised if they did.
Bottom line, I want to dip my toe into the custom ROM pool, but without having to commit to an unlocked bootloader. Possible?
Pretty sure it's not possible, but im not 100%. You need a custom recovery (CWM or TWRP) to flash roms and in order to replace the stock recovery I'm pretty sure you need to be bootloader unlocked.
Stiggosaurus said:
Hi guys,
Longtime iPhone user here, looking to defect. After being inspired by a poster over at The Verge, I embarked on a 30 day trial of a One X yesterday. I've been wanting a nice big screen for a while, and the One X is just all kinds of hot.
Anyhow, I'm still on the fence with a straight up stock device. I suspect I might change my tune with a custom ROM, but I'm now under the impression that a custom ROM is not possible without first unlocking the bootloader. Is this a correct statement? Things have been changing so much over the last week or two with the One X, I'm having a hard time deciphering a clear answer to this.
I'm comfortable with rooting (did this last night) and perfectly comfortable with the process of unlocking the bootloader. But the unlocking scares me a bit, as it doesn't appear to be completely reversible. This doesn't jive to well with my "30 day trial" plans if I decide to return the phone. Seems best I can do is get it back to a "Re-locked" status, which I'm thinking might not be ideal if I decide to return the phone. Who knows, AT&T may not care (or even check), but I wouldn't be surprised if they did.
Bottom line, I want to dip my toe into the custom ROM pool, but without having to commit to an unlocked bootloader. Possible?
Click to expand...
Click to collapse
Correct you will need to unlock the downloader. But if you check your bootloader right now, it already says tampered due to rooting. In my experience at&t wont check the status, but more to the point you can unlock the bootloader being it already shows the tampered flag.
Sent from my HTC One XL using Tapatalk 2
kleeman7 said:
Correct you will need to unlock the downloader. But if you check your bootloader right now, it already says tampered due to rooting. In my experience at&t wont check the status, but more to the point you can unlock the bootloader being it already shows the tampered flag.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It does show tampered but when run an RUU that goes away.
@OP- Odds are the rep at the AT&T store isn't going to know to check the bootloader to see if it's been unlocked. I'm fairly confident that once you unlock and try out some custom ROMs (CleanROM SE is my recommendation), you won't be going back to iOS any time soon.
Sent from my HTC One X using xda premium
Plus, with fastboot on, it's "harder" to get to bootloader.
Sent from my HTC One XL using Tapatalk 2
kleeman7 said:
Correct you will need to unlock the downloader. But if you check your bootloader right now, it already says tampered due to rooting. In my experience at&t wont check the status, but more to the point you can unlock the bootloader being it already shows the tampered flag.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
True, but I got the tampered flag to clear last night by flashing the stock RUU back. That did freak me out last night when I noticed it though, and it's the only reason I went back to complete stock last night just to make sure I wasn't already screwed.
_MetalHead_ said:
It does show tampered but when run an RUU that goes away.
@OP- Odds are the rep at the AT&T store isn't going to know to check the bootloader to see if it's been unlocked. I'm fairly confident that once you unlock and try out some custom ROMs (CleanROM SE is my recommendation), you won't be going back to iOS any time soon.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
kleeman7 said:
Plus, with fastboot on, it's "harder" to get to bootloader.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Interesting! This probably explains why I haven't been able to get into the bootloader for the last 10 minutes! That did the trick though, so thanks for that.
But seriously, I sure wasn't able to get into the bootloader with fastboot enabled. Knowing that, I feel a little more comfortable just going ahead and unlocking now.
I returned a ROM'd up HOX to at&t and they didn't even turn on the screen. You'll be good, they don't ask questions if you're in your 30 days.
Sent from my HTC One X using xda premium
I'm now rooted, bootloader unlocked, and running CleanROM SE 3.0. Thanks for the info everyone, really appreciate it! Now we'll see how the next 30 days goes...
Any other tips/suggestions/ideas for things I should do for an iOS switcher?
Awesome! You're going to love that ROM. Aside from downloading Titanium Backup to keep all your crap backed up should you decide to switch ROMs, I'd say just play around with what you've got for now. I spent 4 months on an iPhone 4S and loved it, but as soon as I got back to Android with my HOX, I haven't missed a minute of my iOS experience. If you get frustrated with anything, just chock it up to learning a new OS and don't be discouraged. I think by the end of your 30 days you will find that Android is actually MORE intuitive and user friendly than iOS, and you won't have to jump through so many hoops to accomplish simple tasks. You are going to love it. Welcome to the wonderful world of Android
_MetalHead_ said:
It does show tampered but when run an RUU that goes away.
@OP- Odds are the rep at the AT&T store isn't going to know to check the bootloader to see if it's been unlocked. I'm fairly confident that once you unlock and try out some custom ROMs (CleanROM SE is my recommendation), you won't be going back to iOS any time soon.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
They've never checked any phone I've returned that was bootloader unlocked or rooted. I do try to go back to as close to stock as possible tho.
Sent from my HTC One XL using XDA
SkizzMcNizz said:
They've never checked any phone I've returned that was bootloader unlocked or rooted. I do try to go back to as close to stock as possible tho.
Sent from my HTC One XL using XDA
Click to expand...
Click to collapse
Yep, I've returned 2 with relocked bootloaders and they didn't check either phone.
I was on an iphone for 2 1/2 years before taking the plunge into android with the HOX...to be honest I don't miss iOS one bit. I've found that everything I can do with android and this phone stock, I needed a jailbroken iphone to accomplish...
Only reason I rooted and unlocked my HOX was because I'm a "tinkerer" and love customization and the ability to do whatever I want to my device. I haven't flashed any ROM's yet, mainly because I'm still learning this stuff but I'm sure it won't be long..
Ok so heres the short of it. I was attempting to root my phone with the Hasoon V1.1 Tool kit and needless to say, everything went wrong. Here's what happened. I did everything to unlock the bootloader. Got my token ID and all that stuff. Next, I loaded the twrp recovery. Cleared everything out of the phone, and went to load a rom. It kept telling me "Failed" when I tried applying the rom. It ended up getting into a boot loop and wouldn't do much. I got it to go back to the recovery when this started and still it wouldn't load any of the ATT Htc One x Roms. I made sure those were the ones I had. Now, at random throughout the process at some point last night, it wouldn't do anything. It has a blank screen. When I plug it in, the status light shows nothing. It was on the charger last night all night, and has not changed. No status light, no screen, nothing! I know you guys are going to ask for more information, but low and behold, like most people you smart guys deal with, I'm a noob. I rooted my google G1, and my HTC inspire without too much trouble, but this is just completely beyond me. As I was doing research I read about problems people were having with the blank screen of death. I'm just worried because I don't have insurance and I'm pretty much screwed without a phone. Does anyone have any input as to what I can do? I'm just beyond aggrivated not having a phone, and I don't have much money to be getting a new one. PLEASE HELP ME
-Mike
Which Rom exactly were you trying to install?
Sent from my HTC One X using xda app-developers app
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
InflatedTitan said:
Which ROM you flashed? Did you successfully root? Can you hold power + volume down to access twrp? Did you try to charge it? What does it do when plugged to computer?
Sent from my One X using xda premium
Click to expand...
Click to collapse
This, as well as... Which phone do you have, the X or XL. The XL is specific in which rooting method you can use.
Sent from my HTC One XL using xda app-developers app
-Power and volume down do absolutely nothing
-Rom was Endeavoru Cyanogen Mod
-Kernel was Franco Kernel r21
-Plugged into computer, does nothing. No status light, nothing.
I am thinking it wasn't the software that did it. It was plugged into the usb port of my laptop the whole time, but may have died. I read online somewhere if you completely discharge the phone, you need a special charger to charge it. If I loaded the wrong kernel it could have gotten below it's "dead" percentage. Correct me if I'm wrong, but with Lithium Ion batteries, completely discharging them is not good for the battery. If it had nothing to tell it to stop, and the usb port on my laptop didn't keep up with the amount I was messing with it, it could just be completely dead. I don't know. I'm an idiot and I apologize about all the gapps I'm giving you guys with information. I'm doing the best I can, but bottom line is after it didn't work at first, I tried a few different recoveries with Hasoons tool kit, and a couple different roms but the roms never loaded. Always failed.
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
With your battery being so low and possibly even dead when you tried to do anything with it, could have a problem. The other problem, if my memory is correct in what I was reading the Endeavoru cyanogen ROM is for the X only, international version. If yours is AT&T like you say, if the flash was performed correctly.... I hate to say this but you might have a nice $500 paperweight, for now. I would PM Abdolutelygrim and see what he thinks, unless he isn't already here.. his current project is unbricking Evita.
Sent from my HTC One XL using xda app-developers app
minimac21234 said:
The phone I have I believe to be the One X, but I don't know the difference. When I booted my phone, it did the HTC Quietly Brilliant screen, then the ATT Rethink possible screen. What is the difference between the one X and one XL? I thought the XL was a larger version of the phone unfortunately, and now I'm seeing differently. It's the ATT phone, 16 gb internal storage, mini sim on the top, Dual Core processor not quad core.
Click to expand...
Click to collapse
You have what we call an HTC one xl or AT&T one x. The phones look almost exactly the same but the internal components are completely different. (youre in the right forum)
Sent from my HTC One XL
I went through almost the same thing last night, with the exception of my battery dying. In the event that you are able to get the phone to charge, this guide helped me get my phone working again.
Good luck!
The phone was fully charged when I began, and I periodically connected and disconnected it when I was having my initial problems. I deleted my cache dalvic cache, etc everything after I saved all my important pictures and videos and files etc. so I just deleted everything to start over fresh. I don't know what the hell I did. I just figured this wouldnt be too hard since I did it with 2 of my own phones in the past, and a few friends phones also. I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
minimac21234 said:
I think my problem may have been with being ignorant and not knowing there were multiple versions of this phone that all look identical but aren't. Ohhhhhhhh boy. This is bad lol.
Click to expand...
Click to collapse
That is indeed your problem. The One X and One XL use a different partition layout, and international roms will attempt to overwrite the One XL boot partition. Hboot is wp in 2.20 but not in earlier versions. Even so, you can end up with corrupted firmware even if hboot is untouched. Numerous people have done it. Some devs are working on a way to fix this. Here's the thread, you'll need to get yourself in the queue or just see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=1966850
Replacement isn't an option. I didn't get a chance to get insurance on it because I cracked the digitizer within the first 2 weeks of having the phone, and I opened it last night to see if something from when I cracked the digitizer came loose causing the phone to not boot. Thanks for the feedback so far guys. I'm not expecting miracles. I put myself into this mess, I'm just really hoping someone may be able to fix it soon. Not having a phone is really going to put a damper on my side work. Can't get phone calls from people on craigslist if I don't have a phone SH!T
Do you know what firmware your phone was on before you did this........it will be the determining factor if it's fixable atm
Sent from my HTC One XL using Tapatalk 2
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL. I feel like the biggest jackass. I'm the computer/cell phone/electronics guy in my area, and now I feel as if I should go into early retirement. I will stay open minded and hopeful that absolutelygrim and others come up with a solution, but bottom line, for all you guys that have made this process damn near idiot proof for people like me, I want to say thanks, and also apologize for all of us noobs that make something as simple as knowing what you are doing before you do it and following directions harder for the developers. It's awesome you guys do what you do in your spare time, only for people like myself to make it more of a hastle. Once again, thanks for trying to fix this guys. My bad.
18th... I was on 2.20. I read that there is a work around for 1.80(I think that's the firmware), but either way, yes I was on 2.20. I have been looking once a week for a new exploit to be able to root the one x, since there wasnt any options until about a week ago if you had 2.20. I bet that's why there are so many people screwing this up. They, like myself, are probably so eager to root it they don't take their time. I remember the first time I rooted my HTC inspire I took about 3-4 hours because I quadrouple checked what I was doing. And damn it am I kicking myself in the ass that I didn't do that this time around.
The problem was the endeavor Rom....but depending on what firmware you were on, 1.85 or 2.20 it can be fixed. If you were on 1.85 or below, it's fixable right now. If 2.20 then not atm.
Sent from my HTC One XL using Tapatalk 2
minimac21234 said:
I'm wondering if when I was trying to use CWM it screwed me up too. I read in a few peoples signatures that CWM also isn't compatable with the One XL.
Click to expand...
Click to collapse
The problem with CWM is that the version for the One XL is an unsupported port. So it's buggy, but the worst I've heard of it doing is corrupting people's sd card or occasionally borking installs, both of which are easily fixable.
The only time I've heard of CWM bricking One XL phones is when people use ROM Manager (which isn't supported for this phone, though GP will let you install it anyway) to install the endeavour version, which causes the same problem as flashing an endeavour rom.
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
InflatedTitan said:
Dang.. I thought it was just icecoldjelly that been banging up peoples OneX. I guess the new hboots aren't as noob-proof as we thought
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
Click to expand...
Click to collapse
It very well could be just Ice Cold Jelly. There is no guarantee something else I did last night bricked my phone. I know I attempted ICJ, and a few other stupid and ignorant attempts. But, I would guess it was from that.
minimac21234 said:
I know I attempted ICJ
Click to expand...
Click to collapse
There you are. That is surely the culprit.
iElvis said:
There you are. That is surely the culprit.
Click to expand...
Click to collapse
Lol... I knew I could get it out of him
Just jokin, hope everything works out OP... just keep following absolutelygrimm's unbricking thread and hope for a breakthrough
Sent from my Liquidy Smooth, blazingly fast as f#@k OneXL using xda premium app.
Okay, before I get started, I am no noob when it comes to adb, linux, qpst, and htc phones. That being said, I was recently making and flashing several splash screens for my AT&T one x. unfortunately, I made a typo whle "dd" pushing the last one to my phone. In the typo I sent the splash screen to blk0p4 instead of 0p14, so when I typed in "adb reboot" my phone shut down, and never came back up. It now shows as QHSUSB_DLOAD in windows. I've spent countless hours searching xda, android central, and various other sites for a possible fix. I've tried the unbricking project, Jet method, and everything else I can find. The device shows up in linux, but my partitions do not show. So basically what I'm looking for is anyone with any fresh ideas on how to get it back to life. My warranty is void, as my phone is disassembled right now, so the battery didn't die while stuck in this mode. I'm really hoping I can escape this without sending my phone into jtag service. Anyone with any ideas to help? If I'm not around on XDA, you can usually always get me on gtalk @ [email protected]. Hopefully someone with more knowledge than I, can help me get my phone back in working order.
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
iElvis said:
It sounds like you're on hboot 1.14? p4 is the extended partition table, but I assume you know that. You're in the same boat as people who flashed Tegra 3 roms.
AFAIK, there is no fix for that sort of brick short of jtag. A lot of smart people have been working on it without success.
Click to expand...
Click to collapse
yes, the phone came to me with hboot 1.14. And the only thing I knew about 0p4, was that I had to hex edit it to htcdev unlock, before s-off. Everything keeps pointing to jtag being the only option to fix my phone.
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Myrder said:
Correct. Jtag is the only way you would be able to revive your device.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
kind of figured that. I've searched everywhere trying to find another fix. Looks like I'll be paying $65 to send my phone in for jtag...
Mods can delete this thread if you wish.
So, here's my situation:
I have a HTC One X that is currently on Straight Talk.
Since Straight Talk doesn't push updates through the BYOP program, I called ATT and asked them what I can do to get the JB 4.1 update.
They told me to get it off the HTC website and do it myself and stuff like that.
So, downloaded HTC Sync Manager, ROM, everything.
Ran the ROM, it installed, everything was lookin' sexy.
Well, everything was working very sexy as well until my phone randomly reboot.
I was like dafuq, thought it must have been a tiny glitch, so didn't pay that much attention to it, until it reboot randomly again 10 minutes later.
This time, however, it didn't get past the ATT logo, and it reboot again. I tried getting it into bootloader, did that, and wiped the phone through bootloader.
Everythin' going dandy, then another random Reboot.
HOWEVER, this time it was just stuck at the HTC logo, and then turned off. Unresponsive. Zero. Nada.
Soooooo. now I have a HTC One X, that's unresponsive, as if the battery is completely dead.
THING IS THOUGH: When I plug it into my computer, it does the ba-dum sound, followed by a da-da-da right after.
Checked DM, apparently it's QHSUSB_LOAD now with an Error 28.
I read on other forums that apparently you have to have S-off to do even a normal update?
How come HTC didn't have it on their website?
It didn't say sh*t on installation windows either about having s-off.
Kinda like someone giving you cake and saying "Oh yeah lol, I **** in there"
Phone is bricked, no doubt, looking for a JTag around my town and Craigslist atm as well, but just wondering, is there anything else that it could be?
I'm 19 and I'm desperate to have my NoLifePartner One X back.
kthxgaiz<3
If you had never rooted the phone or unlocked the bootloader you can install an official update no problems.
The whole "must be s-off" thing is for people who have rooted, and therefore have SuperCID. If you have SuperCID and run an official update while s-on, it will brick.
So if you had never altered your device, you should have been ok. In saying that, these official updates have been known to brick stock phones from time to time.
So, if you had a stock phone and ran the correct update and it bricked your device, that should be covered by warranty I believe.
Sent from my Evita
QHSUSB_LOAD after running the 3.18 RUU means you are bricked.
As mentioned in the previous reply, S-off is not "supposed" to be a requirement for running the RUU. For some reason not completely understood, the 3.18 RUU (and folks also report for 3.17 RUU on some other carriers) and OTA will brick the phone if it is SuperCID and S-on. So S-off (or alternately changing back to the AT&T CID) is the workaround. This was not the case with previous RUUs (SuperCID and S-on was fine). In any case, if the phone was SuperCID, it was a user modification, and HTC is under no obligation to inform you that it can brick the phone.
If you didn't have SuperCID, than its possible the RUU just bricked the phone randomly. Its happened to a small minority of people. Anytime bootloader or radio is modified/updated, and things do go quite right, you stand a small chance of bricking the device. In this case, you should be covered under warranty if the phone is less than a year old.
What if I bought the phone used from a store in my city, and the 'void' stickers have already been altered..?
UserNamesTooMainstream said:
What if I bought the phone used from a store in my city, and the 'void' stickers have already been altered..?
Click to expand...
Click to collapse
Your screwed
P_Dub_S said:
Youre screwed
Click to expand...
Click to collapse
And not by a 5 ft 7 120 smoking sexy dirty blonde lookin for a rebound...
:thumbdown::beer::beer:
Sent from my HTC One XL using xda premium
Does the T-Mobile HTC One S always come S-Off or was I lucky on my trade today? I traded my mint Sony Xperia Play (AT&T) this morning for a HTC One S, also mint. I've traded, bought and sold to the guy before and I know he gets his devices new by special means and knows nothing about rooting, bootloaders or S-Off.
Anyways I got curious in snooping around the bootloader menu and to my surprise found it to be S-Off...
Was this luck or do all/most/many come this way?
...nobody knows??? Just curious...
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
Oh okay. I was surprised to find it S-Off when I got this thing. I couldn't believe my eyes. That will save me a load full of work, especially the part were some of the tools require a Linux OS instead of Windows. Now ofcourse Linux is a download and installation away, but my "temporary" (now permanent) laptop is so old it only packs 128mb of ram (max can ONLY reach 512mb) and any type of Linux installation just hangs and never installs no matter how many hours you leave it running.
Not to mention some of these devices require the "hotwire" trick, and every time i need something (such as a paper clip) it is nowhere to be found.
Crossvxm said:
...nobody knows??? Just curious...
Click to expand...
Click to collapse
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
tivofool said:
Most come with S-ON, although some are sold S-off and Supercid (International use, I'm pretty sure)
Click to expand...
Click to collapse
all the devices come with s-on.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
Nah trust me his knowledge on rooting and so on is VERY LOW. It once took me nearly an hour to show him how to flash a rom on a device I sold him and in a day or two he already messed things up since the rom would wipe many key apps when given an old fashion factory reset. ANOTHER good hour wasted explaining to him the process over phone. If he were to buy these devices used already then sell them to me I would believe that perhaps that person did it instead of him. He gets them brand new in a store he works in, instead of commissions/bonuses for his many sales his boss lets him pick a free phone of his choice as long as its not 100% modern (e.g. a Nexus 5. wish I had that type of boss) in which he gets the opportunity to make more money off of that but remember, his boss doesn't have to pay cash, and he's basically stuck with selling it himself.
If he cant flash a simple rom, or even use a simple app to root a device, I doubt he will ever be able to S-Off an HTC. Also if he were younger (lol) I'd consider the possibility. I honestly believe that this thing may have mistakingly been left S-Off or something by the factory. Or maybe it served a purpose back at HTC.
Whatever the case, it was a big surprise to me.
real187 said:
htc wil never ever give you a s-off device for free.
you have several situations. here are a few.
1: the previous owner of the device,
A was so kind to leave the device s-off, sold it
B he wasnt able/willing to get the s-on back properly, sold it.
C he ****ed up the device, was able to get it running again, left it as is, sold it.
D...
when i sell my devices i always ask you gonna customize it, if yes i leave it s-off. if not full stock
all the devices come with s-on.
Click to expand...
Click to collapse
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
tivofool said:
I would have to dig through old posts to find it, but I was talking to one guy who had just bought one from a store and they were S-off supercid. He said there were about 3-4 more there. Now this guy was from the middle east, I cannot remember which country he said.
I just assumed they had to sell them to that area that way so they could be used with their particular carrier.
I'll search and post it if I can find it.
Edit: found it, he was from Pakistan
http://forum.xda-developers.com/showthread.php?t=2483636
Click to expand...
Click to collapse
Hey now that you mention it I think thats the race his bosses are. But whats a supercid? Never heard of that before?
Nah definitely not as lucky to have a supercid. I assume CID = Carrier Identification seeing mine is T-Mobile related.
Sent from my LG-LS970 using xda app-developers app