Related
I need to send my phone back for warranty but I'm having trouble returning to stock.
I had a branded T-Mobile UK desire, I rooted it and it was running Redux v 1.1.1, alpharev s-off and amon recovery.
I have not created any goldcard and am unsure if this is necessary as some guides say so and others say just to flash the provider RUU.
I tried to run the tmobile uk ruus from here (both RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4. 05.00.11_release_122755.exe and
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.0 6.00.02_2_release_127570_signed.exe) but I got "Error 140 bootloader version" after it runs - it also asks if I want to update the ROM version from 2.10.405.2 to 1.15.110.11 (I'm not sure if this is a problem and I need to downgrade?)
I then reflashed redux as it wasn't booting, I now notice that bootloader is showing:
Bravo Unknown ship s-on (though I still have alsharev s-off splashscreen)
hboot 0.75
Radio-4.05.00.11
Can someone advise me on how to return to stock from here please?
If you're now on that bootloader you should be able to run the RUU again and it might take. Use the 1.21 one - but bare in mind unless you have an AMOLED screen it will leave you with a black screen as the ROM doesn't support SLCD screens
Thanks,
I'm pretty sure my phone is not AMOLED (Can't see any sign of it on the box), is there a RUU I should run instead or any way of restoring functionality if I try this and the screen does go black?
EDIT: I tried to run the RUU and came up with the same error? Any advice?
I believe you get that error when hboot in ruu is older than the one you currently have. Check if there is a newer ruu.
If you are still s-off hboot couldn't have been reflashed. Weird...
Is it definitely a branded one? Try running them RUU's again.
Thanks, I think it's s-on, but for some reason the splash screen has stayed. I've downloaded the RUUs (for T-Mobile) from here: http://forum.xda-developers.com/showthread.php?t=695667
It's definitely branded (or at least it used to be). I did use this unlocker tool as well, I'm not sure if that will have de-branded it stopping me from using the tmobile uk ruu (in which case do you know is there any way to rebrand before sending back for warranty?)
I think I might try to run a WWE RUU (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed)
You'd need a gold card to use the stock WWE RUU
If you're on HBOOT 0.75 that's the very first HBOOT version, any ROM newer than that will work as the bootloader will be newer. No idea why it's not working but it's the issue with having a phone that doesn't have a modern RUU available for it
I haven't got a clue! I've created a goldcard using goldcard tool 0.0.5 which said I have successfully created one. I have a partition on the card, but as far as I can tell that shouldn't be a problem.
The WWE RUU won't run (error 170 - usb connection error) and when I put the PB99IMG.zip from the Tmobile RUU on the sd root (goldcard) and run bootloader, it doesn't detect it.
If I try to run the TMobile RUU it gets so far and then gives the error 140 bootloader version.
If anyone can suggest anything to try I'd really appreciate it as I'm getting nowhere!
Ok, I managed to get the WWE RUU to work by putting the PB99IMG.zip on the goldcard.
I guess that will have to do when sending back for warranty.
Thanks for the help in any case. If anyone knows why I wasn't able to run the TMobile RUU please let me know.
For a few weeks my Desire has been playing up and unpredictably reboots, seemingly at random. Initially I thought it might be a software issue with the ROM I was using, but the same thing happened with various other ROMs I've tried since. So I'm thinking it's a hardware issue and I'll need to send my Desire in for service.
Normally I'd thoroughly read the forums and work out how to go back to a stock ROM, but I'm running out of time - only a few days left under warranty. Therefore this cry for help...
When I got the device it came with a 2.29.405.2 ROM and a 32.49.00.32U_5.11.05.27 radio ROM. I used unrevoked3 to root the phone and have been using custom ROMs since.
I've downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe, but every time I'm trying to flash it, the process aborts during 'updating signature...' and I end up with:
Code:
ERROR [131]: CUSTOMER ID ERROR.
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Not sure what I'm doing wrong. Maybe I'm using an RUU for the wrong area? I'm pretty sure the original ROM was WWE though (it definitely was 2.29.405.2 / 32.49.00.32U_5.11.05.27). I've read somewhere that you can't just flash an RUU if it has a lower HBOOT version... Do I need a goldcard or what's the best way to go back to the stock ROM?
Any help would be much appreciated...
Just in case, here's what my bootloader info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
You only need a goldcard if you are branded right now..
So is your phone branded with a carrier rom, then you must make a goldcard.
I think customer id error is due to incorrect goldcard.
There is a newer version, 2.29.405.5 I dont know if that's gonna work but worth a try.
You can also try to put the zip on your sd card instead of running an exe on your pc, assuming that you run the exe.
Thanks for the quick response.
My Desire was unbranded, so I guess I won't need a goldcard then.
I've downloaded the newer RUU version you mentioned, but got the same error message...
So far I've only tried the .exe, but I'll see if I have more success with the .zip.
Could the issue be that my current HBOOT version is higher than that of the RUU?
You can try to flash 2.3.3 from htcdev.com it's works for all hboots and without goldcards
boy_in_oz said:
My Desire was unbranded, so I guess I won't need a goldcard then.
Could the issue be that my current HBOOT version is higher than that of the RUU?
Click to expand...
Click to collapse
Since you get a CID error, I would definitely try a goldcard.
You can also try flashing the downgrader from alpharev first.
ETA: I think the latter would help.
from alpharev site: said:
# Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
-Jobo
@MatDrOiD (vv post below) Good point. I failed to notice that.
@touch of jobo:
Flashing downgrader from AlphaRev is not possible, the OP is S-ON.
@OP:
Check bortak's guide to bring your phone back to stock.
Have you tried step 7 in Bortak's guide? (http://forum.xda-developers.com/showthread.php?t=1275632) It was the solution for me! I skipped the downgrading part (had the same hboot as you have, so that shouldn't be a problem) and went on with phase 2.
If your phone was indeed unbranded, the goldcard should not be a problem as I understood..
Thanks guys. I'm at work at the moment but will give Bortak's guide a shot when I get home tonight and report back then.
The definition of unbranded is a bit different. Unbranded does not exactly mean that there isnt a carrier logo. HTC manufactured and sold phones in India as an example is for all intents a branded Device. It's the INFOCID property that defines whether branded or unbranded.
fastboot oem gencheckpt
Click to expand...
Click to collapse
Inside an RUU zip is a small text file. Open it and see if your INFOCID value is included. If not, you cant flash that RUU without a goldcard. See my sig for the unbricking guide, which explains this.
From my Guide:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Wow, I would have never guessed this... With fastboot oem gencheckpt I found that the CID is T-MOB101... i.e. my Desire is actually branded! I bought it from mobicity in Australia as an imported unlocked phone and *assumed* that it was unbranded... So it's not surprising that the RUU gave me a customer ID error. (This also explains why the OTA update failed while I was still using this ROM).
What's really weird though is that the version of the ROM that the phone came with was definitely 2.29.405.2 with baseband ROM 32.49.00.32U_5.11.05.27... I did some googling today, but couldn't actually find a T-Mobile ROM with these version numbers
My guess is that mobicity imported the phone and flashed a stock HTC WWE ROM so they could sell it in Australia...
Any thoughts on this? I'm assuming that means that I do need a goldcard after all to go back to the stock ROM?
Ok, as I couldn't find a T-Mobile ROM with the aforementioned version numbers, I eventually decided to make a goldcard and flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. The whole process worked fine without any error messages and the RUU reported success at the end.
Unfortunately my bootloader still displays the same info as in post 1, i.e. I'm still on HBOOT 0.93.0001. I would have expected this to revert back to 0.93... Did something go wrong with the updating procedure?
The issue is obviously still that the original ROM seemed to be a T-Mobile ROM (in fact I think a German one as fastboot oem gencheckpt reports the carrier as TMD), so I'm not sure if the service point will accept the unbranded WWE ROM I flashed.
The other option might be to flash the official HTC Desire Android 2.3 Upgrade from www.htcdev.com, but I think it's not compatible with T-Mobile Germany Desires... If I could flash this, it would at least be an official release and the service point shouldn't complain. Does anyone know how easy it is to root/S-OFF/install custom recoveries/ROMs afterwards? From what I read, I would need to use revolutionary, right?
Any alternative suggestions would be much appreciate...
Your are totally fine with 2.29 RUU. Hboot would only update if you flash 2.3.3 RUU. Did not read about guys who "bricked" their phone by using 2.3.3 RUU on a desire by T-Mobile.
Sent from ICS with Transparent XDA App
Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
I'm no expert but I did purchase a used M8 last week with similar status, which was able to return to (almost) stock.
First, I think your super cid (11111111) is stopping you from any OTA update. Change that to reflect your carrier.
If you are still not able to check for OTA update after that, you need to unlock the bootloader, install TWRP or CWM boot loader, and flash a backup of stock Rom from your carrier.
billyboy77 said:
Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
Click to expand...
Click to collapse
M8_UL_CA. You are on AT&T, correct?
You can download the latest AT&T RUU here.
Download it onto your PC. Hook up your phone and open command prompt. Direct it to your ADB folder, then enter these commands.
adb reboot bootloader
fastboot reboot-bootloader
fastboot rebootRUU waiting for it to boot after each command.
Then run the RUU download by double clicking on the download, and follow the prompts given.
You will have to run it twice. The first time will not install the whole package, the second time finishes the process. This is normal.
xunholyx said:
M8_UL_CA. You are on AT&T, correct?
Click to expand...
Click to collapse
I'm not with AT&T. I bought the phone carrier unlocked - I use a Three mobile SIM. If the phone has been made S-OFF and carrier unlocked then I'd like to return it to a stock unlocked model if possible...
ikeny said:
I'm no expert but I did purchase a used M8 last week with similar status, which was able to return to (almost) stock.
First, I think your super cid (11111111) is stopping you from any OTA update. Change that to reflect your carrier.
If you are still not able to check for OTA update after that, you need to unlock the bootloader, install TWRP or CWM boot loader, and flash a backup of stock Rom from your carrier.
Click to expand...
Click to collapse
Hi - I don't have a carrier - I bought the phone on its own, supposedly carrier unlocked, using an existing Three mobile SIM that I have.
Does anyone have any suggestions for a suitable SuperCID I could try?
Super cid (11111111) means you can flash any rom manually, but no OTA update.
If you want OTA updates, you either pick a carrier and use its cid, or use the GPE (Google play edition) cid. GPE means no HTC added stuffs, like sense 6.
Either way, Google for the cid numbers.
ikeny said:
Super cid (11111111) means you can flash any rom manually, but no OTA update.
If you want OTA updates, you either pick a carrier and use its cid, or use the GPE (Google play edition) cid. GPE means no HTC added stuffs, like sense 6.
Either way, Google for the cid numbers.
Click to expand...
Click to collapse
My last phone was a stock HTC which I converted to GPE. I got fed up with the phone and tried to revert to stock, but messed up. While HTC fix that one I'm trying to update this replacement... getting a bit fed up with non stock HTC phones now to say the least!
Will changing my CID to something like HTC__001 and rebooting risk bricking the phone?
My HTC M8 also has S-off, and I have no problem changing the cid to whatever I want with the toolkit on xda.
Running OTA updates, on the other hand, is more risky to me since I didn't know the history of my device. I chose to flash a nandroid backup via TWRP. (No RUU published from my carrier). Then I re-rooted the stock rom, retuned back to stock recovery, removed the "modified/tampered" status, and locked the boot loader. I left the S-off status, which is the only non-stock.
billyboy77 said:
My last phone was a stock HTC which I converted to GPE. I got fed up with the phone and tried to revert to stock, but messed up. While HTC fix that one I'm trying to update this replacement... getting a bit fed up with non stock HTC phones now to say the least!
Will changing my CID to something like HTC__001 and rebooting risk bricking the phone?
Click to expand...
Click to collapse
The guy that sold me the phone suggested I flash this RUU to the phone. It appears to be a Brighstar US RUU... which just confuses me even more.
"i have find a way to fix your problem, its very simple, but requires your attention to the following details
follow what this link tells you
http://www.htc.com/us/support/htc-one-m8/news/"
What did you ask from the seller? Was it just something "stock and unlocked"? The US rom quote was definitely stock. (Sim) unlocked or not is independent of the rom. Your phone could be locked/unlocked regardless of the rom you use.
All unmodified version from HTC are stock, including GPE. You need to first decide which carrier you want your phone to be "stock" for.
billyboy77 said:
The guy that sold me the phone suggested I flash this RUU to the phone. It appears to be a Brighstar US RUU... which just confuses me even more.
"i have find a way to fix your problem, its very simple, but requires your attention to the following details
follow what this link tells you
http://www.htc.com/us/support/htc-one-m8/news/"
Click to expand...
Click to collapse
I've just spoken to someone in HTC USA Customer services - the phone is formerly an AT&T contract phone. She told me that I'm better off returning the phone to the seller if I want regular OTA updates.
So either send it back and be without phone for a week or so, or try and return it to factory stock myself. Tricky one.
ikeny said:
What did you ask from the seller? Was it just something "stock and unlocked"? The US rom quote was definitely stock. (Sim) unlocked or not is independent of the rom. Your phone could be locked/unlocked regardless of the rom you use.
All unmodified version from HTC are stock, including GPE. You need to first decide which carrier you want your phone to be "stock" for.
Click to expand...
Click to collapse
OK so in theory, I could change the CID to Three UK, and find a Three UK RUU and convert the phone into a stock unlocked three UK one that works with my sim...?
billyboy77 said:
OK so in theory, I could change the CID to Three UK, and find a Three UK RUU and convert the phone into a stock unlocked three UK one that works with my sim...?
Click to expand...
Click to collapse
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
billyboy77 said:
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I don't think the ROM update exe will run in Mac. You'll need to find a Windows pc for this, or try virtual machine running Windows on your mac.
billyboy77 said:
It looks like my best/safest option is installing the Developer edition RUU - but I am on a mac. Does anyone have the correct Zip file of this?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
all the files you need to convert to DE are here >> https://www.androidfilehost.com/?a=show&w=files&flid=21320
This guide may be easier to convert to the DE as it used RUU. No custom recovery and s-off required.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
billyboy77 said:
Hi
Bricked my old 16gb HTC One M8 - sending to HTC for repair tomorrow.
Ordered a replacement 32gb HTC One M8 from Hong Kong. It was billed as 'new' but on arrival it appears to be S-OFF but locked. Full bootloader details below:
*** LOCKED ***
M8_UL_CA PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMC-boot 2048MB
Mar 22 2014,00:53:32.16037
Whenever I try to update OTA, it tells me my phone is not stock and the update doesn't install. I just want to get the phone back to stock with the latest OTA firmware, nothing more. What would my best course of action be here?
Click to expand...
Click to collapse
If you ordered it from Mainland region then most sellers do S Off there even if the phone is new but if you wanted S On you could have talked to the seller. It's trend over there before getting a new android phone almost 90% sellers sells S OFF and Rooted new devices in almost all major Smartphone brands.
Edit: Yes, M8_UL_CA is definitely (AT&T) What country do you belong to? If you're based in the US then just run official HTC AT&T RUU and you will be able to get OTA updates in the near future.
maheshpatel said:
If you ordered it from Mainland region then most sellers do S Off there even if the phone is new but if you wanted S On you could have talked to the seller. It's trend over there before getting a new android phone almost 90% sellers sells S OFF and Rooted new devices in almost all major Smartphone brands.
Edit: Yes, M8_UL_CA is definitely (AT&T) What country do you belong to? If you're based in the US then just run official HTC AT&T RUU and you will be able to get OTA updates in the near future.
Click to expand...
Click to collapse
Actually, it is AT&T, T-Mob, plus Telus and Rogers (Canada, I'm on Telus).
I see he is unbranded(?) now. The first answer was assuming.
@billyboy77 Your radio version is WWE. Sorry I didn't notice that before.
Download the International WWE RUU here.
You will be able to flash this to get to stock since you are S Off and superCID. It will bring you up to the latest firmware. No need for OTAs. Back up anything that is important to you before running the RUU, because it will wipe your device.
hm... Seems like you guys are really trying your hardest to make this more difficult than it needs to be. Having S-OFF he can practically make his device any device he wants it to be, T-Mobile, AT&T, Unlocked, Developer Edition, surely any GSM based carrier/unlocked version.
What's the problem? Unlock Bootloader, Get a custom recovery, Get Root, Change your MID to the one you want, Change your CID to the one you want, Restore a backup for the one you chose, run OTA's...
"OMG I'm S-OFF and bought unlocked but I can't get OTA's because my phone WAS an AT&T and I'm not on AT&T I'm on Three"
:silly:
BerndM14 said:
hm... Seems like you guys are really trying your hardest to make this more difficult than it needs to be. Having S-OFF he can practically make his device any device he wants it to be, T-Mobile, AT&T, Unlocked, Developer Edition, surely any GSM based carrier/unlocked version.
What's the problem? Unlock Bootloader, Get a custom recovery, Get Root, Change your MID to the one you want, Change your CID to the one you want, Restore a backup for the one you chose, run OTA's...
"OMG I'm S-OFF and bought unlocked but I can't get OTA's because my phone WAS an AT&T and I'm not on AT&T I'm on Three"
:silly:
Click to expand...
Click to collapse
After what happened with my last phone, I'd rather not muck about with unlocking, rooting or any of that balls. Just a stock OS with regular updates will do me just fine (until the new HTC comes out anyway)
Hi, so i just bought an htc m8 from ebay and when it arrived i found out its verizon and its in verizon store demo mode, i already reseted it and the app just keeps coming back, how can i get rid off this?
S-off the device, change cid and flash a wwe ruu like the 4.16.401
Or send it back because you got ripped off !
Is the cid HTC__002 ?
extra help pleasee
Mr Hofs said:
S-off the device, change cid and flash a wwe ruu like the 4.16.401
Or send it back because you got ripped off !
Is the cid HTC__002 ?
Click to expand...
Click to collapse
Hey! i didnt understood any of what you said Could you help me? i can try to learn!
oooof tough one .....
S-OFF = Security off
Means all partitions of the phone that are usually locked down for modding are unlocked now, to change the model id (mid) and region codes (cid). Also for changing the phone from carrier lock to unbranded phone.
S-off is available via www.theroot.ninja
Then you have to change cid to a verizon one (non demo cid) and flash a Verizon RUU.
Comes to think of it that a Verizon might not be able to go WWE, I'm not into Verizon devices.
But that's the story in a nutshell. How to change cids can be found in the general section in several tutorials. Or ask/read in the specific Verizon subforum for the M8. The device has its own section !
Hi all,
My name is Nicola and I'm from Bari, southern Italy.
Well... I'm here because it's a while that I search for a fix for my M9, i can't update it. Everytime it says "variant system version".
I also called HTC custom care that told me that my HTC is american and that is the problem, I should send the phone to HTC USA and that issue is not covered by warranty.
I want to ask if you can help me, please! :crying::crying::crying:
when I go to download mode, it says:
htc download mode
***LOCKED***
htc_himauhl PVT S-OFF
CID- 11111111
LK - 1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.35.401.12
Dec 16 2015, 15:37:25(671758)
please, help me!
good evening
Nicola
Did you buy the phone second hand? Or was it you who set it S-OFF and changed the CID to the SuperCID?
Please use the conversion guide in the ReadMe thread for restoring a CID that is compatible with your current firmware. The matching CIDs are all mentioned near the downloads of the RUU section in said thread. It doesn't matter which of the 10 CIDs you choose. However, the meaning of each CID is explained in the CID list that is linked in the further reading section of the ReadMe thread. The reason for your phone not being able to receive/install OTAs is explained in the OTA section of the mentioned thread.
Hi Flippy,
thanks for reply.
I buy the phone new, from ebay, it was brand new. Honestly, I did nothing to the phone!
I will try changing the CID,
Thanks a lot, Flippy!
Cheers
Nico
croconic said:
I buy the phone new, from ebay, it was brand new.
Click to expand...
Click to collapse
I can tell you for sure that it's not brand new. S-OFF and the SuperCID are both clear indications that someone tinkered with this phone.
In addition, the phone is currently running a European firmware. So, if HTC can prove that it's a US model than it got converted by the previous owner.
So... I got cheated.
Well from now i think i'll buy phones only from trusted sellers, i got a lot of problems with the phone, The battery does not last long, sometimes goes in loop with Google service and I reset the phone for use it again, I had an M7 and that was better for me.