[Q] Trying to get back to stock

[LanceM]

Some info
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot getvar version-main
version-main: 2.20.502.7
finished. total time: 0.026s
And I have HBOOT-1.14.0002
I show
TAMPERED
RELOCKED

I can not seem to flash back to stock using htc_one_x_RUU_2.20.502.7_att_us_08022012.exe, it fails.

So then I get the rom.zip file from htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and run...
C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.983s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.433s

Im guessing this is because I followed the instructions (to relock the bootloader) before I ran htc_one_x_RUU_2.20.502.7_att_us_08022012.exe

What would you recommend as my next step?

Im following this guide http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone

 

[LanceM]

I was able to unlock the bootloader... Now Im stuck here...

C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.981s]
writing 'boot'...
OKAY [ 1.548s]
finished. total time: 2.531s

C:\Users\e073175\Downloads\HTC_ONE_X\rom>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.016s

 

[MRaaJR]

"Please note that this method isn't 100% reliable and should be considered a last resort; there have been various reports of this not working due to system.img file being to large."

The error that you are getting seems to be indicative of a known issue. I am sure someone who knows whats up will be along shortly. At least you can take comfort in knowing you are not the only person with this issue. That is when things get scary lol.

 

[Heisenberg]

Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.

Sent from my Evita

 

[LanceM]

Are you s-on or s-off? Do you have SuperCID? I would not use the methods you have chosen to return to stock.

Sent from my Evita

I am S-ON and I do not have SuperCID.

 

[LanceM]

I am S-ON and I do not have SuperCID.

fastboot oem readcid
...
(bootloader) cid: HTC__621
OKAY [ 0.010s]
finished. total time: 0.010s

fastboot getvar cid
cid: HTC__621
finished. total time: 0.003s

 

[LanceM]

When I try and flash

1.85 or 1.83

I get this error

<T111504><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>

 

[Heisenberg]

You can't RUU backwards unless you're s-off.

Sent from my Evita

 

[LanceM]

You can't RUU backwards unless you're s-off.

Sent from my Evita

Ok Tim... So what do I do to get 2.20 on the phone, stock...

 

[Heisenberg]

If you're wanting to run the at&t RUU you'll also need the at&t CID. Otherwise you need to run the RUU that corresponds with the HTC__621 CID. Why is it the 2.20 in particular that you want?

Sent from my Evita

 

[LanceM]

Im not stuck on 2.20. I just want the phone back to stock.

 

[Heisenberg]

Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.

Sent from my Evita

 

[LanceM]

Ok, so then you need to run an RUU that's compatible with the CID you have, and it can't be a backyard update.

Sent from my Evita

Well, that is my question... What RUU is compatible with my CID? And can I change the CID to work for an AT&T RUU, because it seems like 621 is a tawian RUU. If I can, what do I need to change the CID too?

 

[Heisenberg]

Did you change the CID to HTC__621? It doesn't look like an Evita CID.

Sent from my Evita

 

[LanceM]

Did you change the CID to HTC__621? It doesn't look like an Evita CID.

Sent from my Evita

No, when I got the phone a while ago, I rooted and superCID'ed it. It was changed to 1111111, but now for some reason it has changed to 621, which I dont quite understand and has caused quite an issue for me trying to go back to stock.

 

[Heisenberg]

The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?

Sent from my Evita

 

[LanceM]

The CID can't just change by itself, that doesn't make any sense. Are you certain that you were successful in getting SuperCID when you rooted the phone?

Sent from my Evita

I bought the phone in San Antonio at an AT&T store.... Way back when the phone just came out...

At that point, after XDA had root and SuperCID, I did those... And put CM10 on it... Through many upgrades and tinkering, somehow the phone got the CID 621. An Asian CID, I did NOT do this.

Regardless, it is fixed now. I followed the instructions in this thread to change the CID back to 1111111. It worked, then what I did was push the recovery and boot from 2.20 to the phone, then re-locked it.

At this point, I ran the 2.20 RUU and it took... Then I ran the 3.18 phone and now... QHSUSB_DLOAD

Off to http://forum.xda-developers.com/showthread.php?t=1966850

Now downloading linux...

I will fix this damn thing lol!

 

[954wrecker]

You pulled a classic megadoug. S on super Cid ruu strikes again. JTAG is the only way to fix it now

Sent from my HTC One XL

 

[Heisenberg]

Yep. S-on + SuperCID + jb RUU = brick. So you'll need a jtag repair. It's worth tying the unbrick method but nine times out of ten it doesn't work.

Sent from my Evita