Develop Bugs

Sending in for warranty

Hi all.
I need to send my HOX in for warranty because of a weird blemish on the top of the screen.
I know I need to flash stock ROM, recovery and lock the bootloader but what else? Should I bother unrooting it?
Also, I don't know which RUU to use for it. I've had a bit of a browse and I can't find anything that details which one should be used or how to find which one to be used. I never noted it down when I first rooted, flashed and all that other jazz.
Thanks guys.

You need to work it out from your CID.
fastboot getvar cid
Maybe, or
fastboot getvar main-ver
Or CIDGetter from the play store.

BenPope said:
You need to work it out from your CID.
fastboot getvar cid
Maybe, or
fastboot getvar main-ver
Or CIDGetter from the play store.
Click to expand...
Click to collapse
Thanks for that. It says I have HTC__Y13
What would that be then?

potplanty said:
Thanks for that. It says I have HTC__Y13
What would that be then?
Click to expand...
Click to collapse
Google.

BenPope said:
Google.
Click to expand...
Click to collapse
All I could find is that it depends on where the phone was from and whether or not it was carrier branded. As for mine, it was from Europe and unbranded and unlocked. Unfortunately for me there are 6 European RUUs and 3 of them are 1.29

potplanty said:
Hi all.
I need to send my HOX in for warranty because of a weird blemish on the top of the screen.
I know I need to flash stock ROM, recovery and lock the bootloader but what else? Should I bother unrooting it?
Also, I don't know which RUU to use for it. I've had a bit of a browse and I can't find anything that details which one should be used or how to find which one to be used. I never noted it down when I first rooted, flashed and all that other jazz.
Thanks guys.
Click to expand...
Click to collapse
First time I sent mine back I never unrooted it and they almost repaired it.

potplanty said:
All I could find is that it depends on where the phone was from and whether or not it was carrier branded. As for mine, it was from Europe and unbranded and unlocked. Unfortunately for me there are 6 European RUUs and 3 of them are 1.29
Click to expand...
Click to collapse
Ok, was a tad harder to find than I thought.
Grab 2.17.401.2, your CID appears to indicate Norway

deakodude said:
First time I sent mine back I never unrooted it and they almost repaired it.
Click to expand...
Click to collapse
Almost?
BenPope said:
Ok, was a tad harder to find than I thought.
Grab 2.17.401.2, your CID appears to indicate Norway
Click to expand...
Click to collapse
Thanks man.

First repair they put new mobo in it,then sent it back to me without the sim tray reading the card so back again for another fix.

[Q] My original Android rom is not stock version?

Hi Guys,
It's the first time I post. Nice to meet you guys.
I bought a HTC oneX in Hong Kong 3 months before with relative cheap price around 435 US dollar. When I got OTA Android 4,1 I cannot install it because it said that my Android is modified. I didn't modify it by myself.
Anyone knows what happens and how to make is possible to upgrade again?
Thank you very much!
Cheers,:laugh:
George

Your rom is indeed modified (at the very least in build.prop, maybe more), so flash a RUU to return to completely stock rom. This will wipe everything, but it allows you to update. There are links to RUUs in the General section.
你的软件的确被改性了。最容易的方法来解决这个问题就是把Android完全擦除，以HTC的RUU方法来恢复到HTC未经修改的Android。这会把你所有的软件、资料等等消除掉，但会让你更新你的Android。你能在General的部分找到下载RUU的论坛主题。
还有：如果你要回复我的答案，请用英语来回复，因为论坛规则说我们必须用用别的语言得有英语的翻译。

That's not an official HK version (which would be '708).
This RUU will wipe your phone but hopefully fix the problem:
http://htcruu.com/securekey.php?fil...Radio_1.1204.105.14_release_261350_signed.exe

Thanks all!
I found that my HTC One X was was already rooted and unlocked when I bought it. It's strange
I got Error 120 at the beginning and I clear the cache in Hboot then it's fixed. Afterwards I got error 155 when running RUU.
Then I try the method in this following link:
http://forum.xda-developers.com/showthread.php?t=1609190
I tried to flash the rom directly but when I execute the code ''fastboot flash system system.img'' it failed.
Do you have any suggestions?
My god, I spent like 5 hours to read but still cannot fix it. Your commands save me lot of time!
Thank you very much!

Run:
fastboot getvar version-main
To check that was the right RUU.
To run the RUU you need to have a locked bootloader:
fastboot oem lock

BenPope said:
Run:
fastboot getvar version-main
To check that was the right RUU.
To run the RUU you need to have a locked bootloader:
fastboot oem lock
Click to expand...
Click to collapse
Hi Ben,
It's written 2.17.707.3. This is the latest version??

You could try this one
http://www.htcruu.com/securekey.php...Radio_5.1204.162.29_release_296434_signed.exe
Brings you straight to JB stock

Hi Mr. Hofs,
Thanks for your advice. I still encountered Error 155. I have relocked my OneX already.
If you saw the capture I posted my software version is modified, may be because of this reason I cannot flash my rom and run RUU.
Do you have other ideas?

Hmmm can you also give the command
Fastboot oem readcid

Mr Hofs said:
Hmmm can you also give the command
Fastboot oem readcid
Click to expand...
Click to collapse
HI Mr Hof,
CID: HTC__044
I don't understand what does it mean?
Thanks!

It means the RUU you tried (3.14.707.) Should work. I wonder if you need to update the firmware before flashing it.

Did you run the RUU with admin priviledges?
Sent from my EndeavorU using xda app-developers app

Hi Mr Hofs
It's working now! The problem is that I didn't run RUU in bootloader. I have to install stock rom 4.0.3 first and upgrade.
Many thanks to your advice! Finally I can fix this problem! Spend me much time
Cheers,
George

Good !
CASE CLOSED !

Cannot write TWRP in S-ON state

Im trying to unbrand my M9. Ive followed the steps, have read the Back up and write only posts on XDA.
Ive only unlocked the bootloader so far through HTCDev, but when I come to flash TWRP, it says
"cannot write revovery in S-ON state", but I thought I had to Flash recvoery first, then S-Off
Im using twrp 2870=hima with SuperSU 2.49BETA.
Like I say, Ive only unlocked bootloader, nothing else.. phone is running fine
Any help please

Flash recovery in download mode rather than bootloader and it should work fine

gffmac said:
Flash recovery in download mode rather than bootloader and it should work fine
Click to expand...
Click to collapse
Thanks friend, all sorted.. the guide said.. it was Bootloader mode,
Im just doing a full system backup before rooting...
wish me luck

NightOrchid said:
Thanks friend, all sorted.. the guide said.. it was Bootloader mode,
Im just doing a full system backup before rooting...
wish me luck
Click to expand...
Click to collapse
maybe you should try a different guide. Sounds like that one was maybe written for the M9?

Ok so now my M9 boots up to desktop then keeps rebooting after i changed the CID to 001.
I can boot into recovery and twrp, but keeps rebooting
SORTED:
If this happens to you, do not panic... its not bricked or broken, My M9 had a CID: ORANG001, but when I changed it to HTC__001, it was bootlooping. According to the folks at sunshine live chat, this can happen when a carrier apps interferes with the particular CID... so just change it back to the original carrier cid.. and it works fine.... then try a different CID, or remove app from system through root.. but be careful of this..
cheers

Set it to supercid 'fastboot oem writecid 11111111' and you will be good to go.

gffmac said:
Set it to supercid 'fastboot oem writecid 11111111' and you will be good to go.
Click to expand...
Click to collapse
I thought supercid stopped it from taking OTAs, besides if its an EE app causing it bootloop from the M9 desktop, will 401.8 not replace the ROM. therefore just set USB debugging, change CID in download mode, then just flash 401 from recovery without bothering with the bootloop.
Thanks

Supercid allows you to use any rom from any network and shouldn't stop otas.
Sent from my HTC One M9 using Tapatalk

gffmac said:
Supercid allows you to use any rom from any network and shouldn't stop otas.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I just used HTC__001 anyway.. didnt bother booting into the OS, just jumped straight to download mode and flashed the WWE 1.32...
Anyway, Im all sorted and all up and running now on wwe 1.40.401.8
Thanks for all the help

HTC one M8 error Cannot mount SD card

Hi there.
Im really new, but I will try to explain.
My brother Htc m8 was updating(usual pop up update from HTC,) last night and after reboot he gets the Cannot mount SD card error, and get stuck into a loop.I can load into recovery, or into bootloader, and thats it, from what ive read past couple of hours I need USB debbuging mode, in order to flash the ROM but as for now I cannot connect my device to the PC to run ADB and Fastboot, and to flash the ROM.Any advice in how to get into USB Debuggin mode ON, or its a lost cause ? Thanks in advance.

You don't need Debugging on, to use fastboot. But you need to be in bootloader-fastboot mode.

redpoint73 said:
You don't need Debugging on, to use fastboot. But you need to be in bootloader-fastboot mode.
Click to expand...
Click to collapse
ok done that by reboot fastboot from bootloader.
still the device isnt detected by ADB...
is there any guide to follow? or the steps that I need to take to make it work ?
Thanks

zizooboy said:
ok done that by reboot fastboot from bootloader.
still the device isnt detected by ADB...
is there any guide to follow? or the steps that I need to take to make it work ?
Click to expand...
Click to collapse
While fastboot does not require debugging on; adb does require it. adb also only works within OS (which you don't have) and recovery.
It sounded like you already had a plan to recover, based on your OP, and just needed fastboot working. Would need more info to help you with further steps.
Is it a stock device, or has it been modded before? Bootloader LOCKED, UNLOCKED or RELOCKED?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
The error is about internal storage no mounting? I assume that is the case, as I don't see how an error with (removable) SD would prevent the phone from booting.

redpoint73 said:
While fastboot does not require debugging on; adb does require it. adb also only works within OS (which you don't have) and recovery.
It sounded like you already had a plan to recover, based on your OP, and just needed fastboot working. Would need more info to help you with further steps.
Is it a stock device, or has it been modded before? Bootloader LOCKED, UNLOCKED or RELOCKED?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
The error is about internal storage no mounting? I assume that is the case, as I don't see how an error with (removable) SD would prevent the phone from booting.
Click to expand...
Click to collapse
I don't have a SD card inside thats why I am surprise never used one and get this error.
device was never moded
results
version :0.5
version bootloader :3.19.0.0000
version baseband 1.29.214.500021.12G
version cpld:None
versionmicrop:none
version main:6.12.401.4
version misc UT SHIP S-OFF
meid: 00000000000000
product :m8_ul_ca
platform: hTCBmsm8974
modelid:0P6B10000
cidnum:11111111
baterry status :Good
baterry voltage 0mV
partition layout :Generic
build mode :SHIP
Boot mode: FASTBOOT
commitno-bootloader :76df2b54
hbootpreupdate:11
gencheckpt:0

zizooboy said:
I don't have a SD card inside thats why I am surprise never used one and get this error.
Click to expand...
Click to collapse
The error is probably referring to the internal storage, which is treated as an SD card by the OS.
zizooboy said:
device was never moded
version main:6.12.401.4
version misc UT SHIP S-OFF
product :m8_ul_ca
modelid:0P6B10000
cidnum:11111111
Click to expand...
Click to collapse
Ohhh yes, its been modded. Just not by you.
It was originally the AT&T US version (m8_ul_ca) that was s-off and had the CID/MID changed to SuperCID (11111111) and Euro MID (0P6B10000) then had Euro firmware (6.12.401.4) installed to remove AT&T software.
It probably also had its back plate changed, to remove the AT&T carrier logo. The model number on the back plate, may even contradict the Euro model number show in your getvar output.
Does it say LOCKED, UNLOCKED or RELOCKED on the bootloader screen (I'm guessing LOCKED)?

redpoint73 said:
The error is probably referring to the internal storage, which is treated as an SD card by the OS.
Ohhh yes, its been modded. Just not by you.
It was originally the AT&T US version (m8_ul_ca) that was s-off and had the CID/MID changed to SuperCID (11111111) and Euro MID (0P6B10000) then had Euro firmware (6.12.401.4) installed to remove AT&T software.
It probably also had its back plate changed, to remove the AT&T carrier logo. The model number on the back plate, may even contradict the Euro model number show in your getvar output.
Does it say LOCKED, UNLOCKED or RELOCKED on the bootloader screen (I'm guessing LOCKED)?
Click to expand...
Click to collapse
Its LOCKED , the phone was buyed from an EBAY shop who at that time said that was a return and was more cheap than usual price.didnt have any problems until now.Any advice from now on ?
Thanks.

Try the RUU here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

redpoint73 said:
Try the RUU here: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Heading to work now. I will download the RUU and follow the steps.Will post the result tommorow.
Thanks in advance.Life saver

zizooboy said:
Life saver
Click to expand...
Click to collapse
Heh, but you don't know that yet. Good luck, and hope it helps.

redpoint73 said:
Heh, but you don't know that yet. Good luck, and hope it helps.
Click to expand...
Click to collapse
It worked.I just followed the instruction and reboot the phone and bam done, phone is alive and Androied 6 on it.Many thanks redpoint73,like I said life saver, and precise advice to a newbie.

redpoint73 said:
Heh, but you don't know that yet. Good luck, and hope it helps.
Click to expand...
Click to collapse
well it helped.
I just followed the instructions ont the site, rebooted the phone and was all good.Many thanks to redpoint73 for helping a newbie with the good advices.
ps: sorry for double posting
Cheers

zizooboy said:
Many thanks redpoint73,like I said life saver, and precise advice to a newbie.
Click to expand...
Click to collapse
You're quite welcome, and happy to help. Glad it worked out.

RUU Suitable for My HTC 10 CID HTC__001

Trying to put my HTC 10 back to stock so looking for any RUU that will work with My CID which is HTC__001 and Mid which is 2PS620000
Not looking for a nougat RUU any will do, i've downloaded about 5 now which i thought would work but keep getting an Error 155
If anyone could point me in the right direction that would be great
I'm S-Off and bootloader is locked...
I'm also in the UK...
Many thanks

I flashed this one from my SD card this morning, everything went smooth and easy. Just like you, S-Off, locked. Don't forget to check the MD5
https://www.androidfilehost.com/?fid=24533100289591083

wakers said:
Trying to put my HTC 10 back to stock so looking for any RUU that will work with My CID which is HTC__001 and Mid which is 2PS620000
Not looking for a nougat RUU any will do, i've downloaded about 5 now which i thought would work but keep getting an Error 155
If anyone could point me in the right direction that would be great
I'm S-Off and bootloader is locked...
I'm also in the UK...
Many thanks
Click to expand...
Click to collapse
You're getting Error 155 because you are S-On. If you were S-Off there wouldn't be a problem, but since you are not you'll need to relock your bootloader to run an RUU.
In fastboot:
fastboot oem lock
then run the RUU again.

Hi thanks for the reply I'm S off and I've relocked the bootloader still get the error...

wakers said:
Hi thanks for the reply I'm S off and I've relocked the bootloader still get the error...
Click to expand...
Click to collapse
Go to the stock guides thread. Download 1.90.401 RUU.zip. rename the zip to 2PS6IMG.zip and put it on external sd card, boot to download mode and press vol up to confirm flash. Remember this will erase your internal storage.

pomponazzo said:
I flashed this one from my SD card this morning, everything went smooth and easy. Just like you, S-Off, locked. Don't forget to check the MD5
https://www.androidfilehost.com/?fid=24533100289591083
Click to expand...
Click to collapse
That will return to stock, but it's ancient
(1.30)
Non nougat are on 1.90 or 1.95 which is available
http://forum.xda-developers.com/showthread.php?p=66830893
Sent from my HTC 10 using XDA-Developers mobile app
See post above mine for good method

Sure. He asked for a reliable download. As I just flashed this one, I'm certain it's OK. I never said it was the only option.

pomponazzo said:
Sure. He asked for a reliable download. As I just flashed this one, I'm certain it's OK. I never said it was the only option.
Click to expand...
Click to collapse
Didn't mean to be over critical.
Your file will certainly work if you are fine with stock HTC 10 software from May 2016
Sent from my HTC 10 using XDA-Developers mobile app

All sorted thanks, I've always flashed RRUs via adb and fastboot just couldn't get it to work so tried the sd card method and voila first time...