Database Info

[Q] Return to Stock without device history - AT&T, Rogers HTC One X, Telstra One XL

So I am a little (a lot) scared to touch my new phone.
I recently acquired an AT&T One X, and it is currently rooted, and running CleanROM 6.5.0. I don't have the history of the device, so I am not sure how its previous owner got it to here, and what the safest steps would be to get it back to pure stock.
I am not worried about resetting the tamper indication or warranty issues. I just would like to get back to the stock AT&T software, and then I can go from there getting it where I want it.
The phone has TWRP Recovery, but had no recovery images. I have made a recovery for where it is at currently.
Bootloader currently shows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
CID- 11111111
HBOOT-2.15.0000
RADIO -0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Aug 14 2013, 16:02:22 -1
I would say my skill level with phones is "moderate". I at least know enough to not mess with something if I am not 100% sure.
So, from what I am seeing, the phone is S-on, and bootloader is locked, and I have superCID, so I should be able to just flash the proper RUU?
Or, is there anything else I need to do first?

Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.

timmaaa said:
Absolutely do not run an RUU while s-on, SuperCID + s-on + RUU = bricked phone. Where did you read that you can run an RUU with that combination? It's completely untrue. You can't run any RUU anyway, there are no RUUs after your current firmware version and you can't RUU backwards while s-on.
May I ask why you want to return it to a stock at&t ROM though? There is really no benefit of doing so, it's seriously a step backwards because at&t intentionally break some features and leave others out on their ROMs. What is your end goal for this device? I'll help you get there in the most efficient and safe way.
PS. Questions go in the q&a section, please make sure you post in the right section in future.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.

Your thread is now in the Q&A section:good:

floodx4 said:
Thanks for the heads up! I have been through so many posts in the last couple hours, I probably got confused about where I needed to be to safely RUU.
I don't necessarily want to be on a stock ROM, as much as I just want to return the phone to stock, and start over myself. I don't like the idea of having a customized device, and not knowing how it got there.
BUT, where I would to end up, is with CleanROM 7.0, or something similar. I am just looking for a stock(ish), rooted JB ROM, with sense 5.0.
I don't trust my skills enough to like messing with kernels and such, so I am just looking for a good JB ROM to run.
Thanks for the help! And sorry for the wrong forum.
Click to expand...
Click to collapse
I admire the fact that you want to get it there yourself, the learning aspect of unlocking a device is very important in my eyes. The first thing you need to do is get s-off so you can safely run an RUU without bricking your device. I'll give you a quick run down of the entire process first though.
1. Get s-off.
2. Run the 3.18 RUU.
3. Change CID from SuperCID to original CID.
4. Use the 3.18 root method to gain SuperCID again.
5. Unlock your bootloader at htcdev.
6. Install TWRP recovery.
7. Upgrade to the 2.15 firmware package.
8. Flash Cleanrom 7.x.
So, first you'll need s-off. The easiest way is probably to use the Rumrunner method, you'll find it here:
Http://Rumrunner.us
Even before doing that though you'll need to setup an adb/fastboot environment on your PC. Adb.exe and fastboot.exe are programs you install on Windows in order to communicate with your phone via the usb cable and command prompt. In order for these to work you'll also need HTC drivers installed.
This thread is the easiest way to install adb/fastboot:
http://forum.xda-developers.com/showthread.php?p=42407269
This is where you can find the latest HTC drivers:
http://forum.xda-developers.com/showthread.php?t=2535581
Once you have those both installed you should test out the communication. Connect your phone in fastboot mode (boot into bootloader and connect device, it'll say fastboot usb on the phone), open a command prompt from within your fastboot folder (navigate to where fastboot is located on your PC, shift + right click anywhere in that folder, select open command prompt here), and issue this command:
Code:
fastboot devices
It should now return your device serial number, if it does you can go ahead and attempt Rumrunner s-off. If it doesn't return the serial you have a problem with communication.
Sent from my Evita.

How do I know what the original CID should be?

The above post by me lists how to go about the entire process, which isn't completely necessary but I've outlined it because you said you want to start from the beginning. There is a shorter way to do this, if you'd like to go for that just let me know and I'll outline though too. Your steps there look ok but I'd make a slight change.
Sent from my Evita.

floodx4 please be sure to click timmaaa thanks button.
That's how we show appreciation on XDA

Dang.......
Went through the Rumrunner process, everything seemed to go as it should, but I am still S-on.
Also, tried to unlock through HTC DEV, and I get nothing after flash the unlock token. (phone never gives me the "accept" screen.
Communication is good through fastboot, but something doesn't seem right.
Any ideas, or should I just leave well enough alone and live with 4.1?

Oh, that's my fault, I forgot you need an unlocked bootloader for Rumrunner to work. Sometimes it can take several attempts at flashing the unlock token for it to work, so keep trying that.
Sent from my Evita.

Man.....not sure what the previous owner did here, but....
I tried flashing the unlock token several times....all seemed to go through, but no "accept" screen on the phone.
Finally, I sent the fastboot oem lock command, and it "somewhat" acted like it relocked it. (I did get a FAILED message in there somewhere).
Resent the flash token command, and viola! I got the "accept" screen. Accepted the warning....and.....still locked
Went through Rumrunner again, just to see, and same result. I get the success message, but still have a locked bootloader, and still have s-on.
Back to the drawing board.......
EDIT: Went back through the process again, and noticed that when I send the fastboot oem lock command, the status changes to ***RELOCKED***, and after I flash the token, and accept the warning, the phone resets back to factory.....but bootloader still shows locked.
2nd EDIT: I think I may be on to something here!
Could the phone have one of the tools installed that "spoof" the hboot screen?
Here is what I get from a getvar all:
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.20.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT255W302399
(bootloader) imei: 3xxxx6
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4052mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.083s
Could I be s-off and unlocked, and just not seeing it?

Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now disconnect your phone and select recovery from the bootloader screen on your phone. Hopefully it boots into TWRP recovery, this proves that your bootloader is in fact unlocked.
Sent from my Evita.

timmaaa said:
Yeah, the previous owner has spoofed the hboot, so even though the phone shows locked after you flash the token I believe it's unlocked. Test the theory by trying to install a custom recovery.
<snip>
Click to expand...
Click to collapse
OK, we are getting somewhere!
I have the TWRP recovery. (I believe I already may have had this same recovery, but It did flash successfully via the commands, so I think I'm good)
So....now what? Can I "un-spoof" the hboot to be sure? Or just be satisfied with the above experiment? And if so, does this put me at Step #2 "Flash the 3.18 RUU"?

Yeah I believe you're good to go, I'd like to be doubly sure first though. You can change your CID as many times as you like if you have s-off, but with s-on you can't do that. So I'd suggest trying to change it and this will confirm your security status. The command is:
Code:
fastboot oem writecid 22222222
Hopefully that'll work, confirm by giving this command:
Code:
fastboot oem readcid
Hopefully you'll see eight two's. Once you've confirmed that works you can change it back, and you'll be good to go with the 3.18 RUU. The RUU will install the official 2.14 hboot so the locked/unlocked/relocked flags at the top of your bootloader screen will be normal again.
PS. You might want to edit the IMEI out of your post above, you should never post that publicly.
Sent from my Evita.

Cool, writecid worked.
And speaking of that, Step 3, Change CID to original......what would the original CID be?

I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.

timmaaa said:
I wouldn't worry about that step, the point of that was to use the 3.18 root method.as a learning tool, it's completely unnecessary for you, but to be honest it's more trouble than it's worth. Right now I think you're learning quite a lot so you can run the 3.18 RUU, skip step 3 and 4, you've already unlocked your bootloader so skip step 5, you'll need to install TWRP recovery again after the RUU so do step 6, then you can continue on with steps 7 and 8.
Sent from my Evita.
Click to expand...
Click to collapse
Awesome.
Just to be sure here....do I want my bootloader locked or unlocked when I flash the RUU?

You're s-off so you can leave the bootloader unlocked. Here's a link for the RUU.
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
Sent from my Evita.

I cant hit the thanks button enough!
CleanRom 7 installed and working great, and best of all, I know where it came from.
Now its time to take this thing for a test drive.......

Oohhhh yeah! That's what I'm talkin bout!
Great news, and once again I admire you for actually wanting to put in the effort and do some learning along the way. Most people want to take the shortest road possible, and they're inevitably the ones who have no idea what to do when something goes wrong.
If you do ever need help in the future just let me know.
Sent from my Evita.

Related

Hi, I received a replacement from AT&T for a phone that had a damaged sim connection, so I am sending back the old one.
My question is how can I revert the phone I am sending back completely to stock?
Currently my bootloader screen shows:
*** LOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26 2012,12:37:14:-1
Also, if anyone has sent back a non-stock phone, did everything go alright?
----EDIT Sept 08 2013----
In case anyone would like to do something similar, here are the steps I took.
1) Copy off all my data
2) Run the 2.20 RUU
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3

antichamp said:
Hi, I received a replacement from AT&T for a phone that had a damaged sim connection, so I am sending back the old one.
My question is how can I revert the phone I am sending back completely to stock?
Currently my bootloader screen shows:
*** LOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26 2012,12:37:14:-1
Also, if anyone has sent back a non-stock phone, did everything go alright?
Click to expand...
Click to collapse
I would have changed the cid back to stock personally:
fastboot oem writecid CWS__001
I don't think you can with a locked bootloader. But if that Locked is just spoofed, it should be doable.
You could also S-ON:
fastboot oem writesecureflag 3

No, the lock isn't spoofed, but I still have the unlock token.
I probably should have mentioned I still have a custom rom; what order should I reset everything?
Unlock > RUU > UnSuperCID > Relock > S-ON > Done?

You may need to s-on before relock. Other than that. Looks like the right order.
But typically it will say relocked instead of locked unless spoofed.
Sent from my HTC One XL using xda app-developers app

In all honesty being a hardware fault, they likely won't check into it that thoroughly, however I suppose better safe than sorry.

The steps should be
Unlock > RUU > UnSuperCID > S-ON > Relock > Done?
Where is the "Relock" step in your description ?
1) Copy off all my data
2) Run the 2.20 RUU
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
I am asking because I am Unlock and I want to know how to Relock.(back to stock for warranty)
Thanks for your help

1. Backup data.
2. Run 3.18 RUU (must have s-off first).
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Don't worry about making the phone s-on again as they don't worry about this for warranty purposes. It's far more important to change the relocked flag in the bootloader to locked. I've seen one case where having the altered bootloader flags and going back to s-on has bricked the device, so leave it s-off.
Sent from my Evita

timmaaa said:
1. Backup data.
2. Run 3.18 RUU (must have s-off first).
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Don't worry about making the phone s-on again as they don't worry about this for warranty purposes. It's far more important to change the relocked flag in the bootloader to locked. I've seen one case where having the altered bootloader flags and going back to s-on has bricked the device, so leave it s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your answer,
One more question, if I don't have the last RUU ( I am on Telus) but I have my original Nandroid backup with TWRP (before root and unlock) can I use it to go back to stock ?
Or should I use an old RUU and upgrade to last update OTA after ?
What is the best option
Thanks
Info:
bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.661.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4119mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Using a backup only restores the ROM partition to stock, you'll need to use an older RUU and upgrade via OTA. So run the RUU, then return your CID to the Telus CID and take the OTA updates.
Sent from my Evita

Hello everybody,
I'm tired of these custom ROMs. There is always something not working or the phone just doesn't perform as good. Now I just want to return my phone back to stock. I read the thread, as well as some other threads but I'm not sure what the correct steps are. That is why I want to ask again just in case. Here's my phone info AT&T HTC ONE X:
***UNLOCKED***
EVITA PVT S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
emmc-boot
Nov 26,2012
Rooted
SuperCID-11111111
TWRP Recovery 2.3.6
ViperXL 3.8.0
I have used the [TOOL] OneClick SuperCID for Unlocking Bootloader tool from the forum and unlocked my bootloader through HTC developer webpage. I was unable to S-OFF my device I don't know why.
Is it necessary to S-OFF the device to return it back to stock?
Which RUU should I flash the 2.20 or the 3.18?
And then should I do this:
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
Or this:
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Thank you guys

My suggestion would be to get s-off and then run the 3.18 RUU. You don't really need to worry about locking the bootloader that way, just in case you decide you want the ability to go custom again in the future.
Sent from my Evita

timmaaa said:
My suggestion would be to get s-off and then run the 3.18 RUU. You don't really need to worry about locking the bootloader that way, just in case you decide you want the ability to go custom again in the future.
Sent from my Evita
Click to expand...
Click to collapse
The thing is that I can't get it to s-off. I've everything I found in the forum and I can't turn it off. What if I don't s-off it can I still run the RUU? Or I'll brick my phone?

I have to disagree there, you most likely can get s-off, but haven't found why it isn't working yet. If you run the RUU while s-on it'll brick. That's if the RUU even works, while s-on you can't RUU backwards which I'm assuming also means you can't RUU to the same version you're already on. What ROM have you attempted getting s-off on?
Sent from my Evita

superlamer said:
What if I don't s-off it can I still run the RUU? Or I'll brick my phone?
Click to expand...
Click to collapse
3.18 with S-on and SuperCID is a sure brick. DO NOT ATTEMPT.
---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------
timmaaa said:
while s-on you can't RUU backwards which I'm assuming also means you can't RUU to the same version you're already on.
Click to expand...
Click to collapse
Same version is normally ok, you just can't go backwards with s-on. Of course I say "normally" since as mentioned with SuperCID and S-on, running 3.18 will brick the device.
timmaaa said:
What ROM have you attempted getting s-off on?
Click to expand...
Click to collapse
Seems like he is trying to S-off on ViperXL 3.8.0. Its a good question, as it seems that some folks have had trouble getting s-off on certain ROMs.
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
superlamer said:
Hello everybody,
I'm tired of these custom ROMs. There is always something not working or the phone just doesn't perform as good. Now I just want to return my phone back to stock.
Click to expand...
Click to collapse
I think you are insane. Stock AT&T ROM is full of bloat and gimped of basic features. There are quite a few stock-based ROMs that are superior to stock AT&T, or even stock rooted ROMs for almost any other carrier but AT&T.
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
superlamer said:
Is it necessary to S-OFF the device to return it back to stock?
Which RUU should I flash the 2.20 or the 3.18?
And then should I do this:
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
Or this:
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Click to expand...
Click to collapse
You don't need s-off to change from SuperCID to CWS__001 using the fastboot command. In theory, you should be able to do this, relock the bootloader, and run the 3.18 RUU.
But again, its not my personal recommendation.

Ok If I am on HBOOT-2.14.0000 and want to S-OFF should I upgrade my firmware to 2.20 using this thread?
http://forum.xda-developers.com/showthread.php?t=1952038
Or I should use the method form this?
http://forum.xda-developers.com/showthread.php?t=2155071
I have tried this method and it didn't work for me, may be I am doing something wrong. Do you know any other ways I can try?
Thanks for the help

superlamer said:
Ok If I am on HBOOT-2.14.0000 and want to S-OFF should I upgrade my firmware to 2.20 using this thread?
http://forum.xda-developers.com/showthread.php?t=1952038
Click to expand...
Click to collapse
That is not a method to upgrade firmware, its a method to root. You are already rooted.
superlamer said:
http://forum.xda-developers.com/showthread.php?t=2423735
I have tried this method and it didn't work for me, may be I am doing something wrong. Do you know any other ways I can try?
Click to expand...
Click to collapse
That is the only method for s-off. So yes that is what you should be using for s-off.
Some folks have had trouble getting S-off on some ROMs. You might try to flash an older ROM (even ICS) and try the Facepalm method again.

Ok, just to make sure I don't screw up my phone before I do this. Sorry for asking things that have already been asked.
I'm on ViperXL 3.2.8 (not 3.8.0 as I said in one of my previous posts). The Android version is 4.1.1
Is there a chance to brick the phone doing this?
These are the steps I should follow correct?
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip> this zipt file 2.15.0000_5.08.111.2-1.31a.32.45.16_2_10.141.32.34a.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN if it fails keeep on trying until it succeeds
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
If this doesn't work can I flash an ICS rom? The HBOOT version shouldn't matter right?
I also found this thread:
http://forum.xda-developers.com/showthread.php?t=2494998&page=3
Looks like this guy has exactly the same issue as I do. I admin I did not looked at the error it was giving me, I was looking for "INFO..... OK". I will try again and and try to capture the error this time
If everything is successfull I guess I should be able to even upgrade to Android 4.2.2 and not have the random reboots and the signal drops (this is the reason I went back to ViperXL 3.28 and Android 4.1.1).

Hang on. You need s-off to flash that 2.15 firmware package. You're a bit all over the place, what is your end objective?
Sent from my Evita

timmaaa said:
Hang on. You need s-off to flash that 2.15 firmware package. You're a bit all over the place, what is your end objective?
Sent from my Evita
Click to expand...
Click to collapse
Haha sorry about that I used to have Samsung Galaxy S and it was so easy to flash that thing, now with the One X there are so many things I don't know where to start. I guess I want to S-OFF it first. Then I would like to return it to the stock Android like when I bought the phone.

Flash an Android 4.0 or 4.1 Sense ROM and try the Facepalm s-off process, if it doesn't work copy the text from the command prompt and paste it here so we can try to diagnose what's wrong.
Sent from my Evita

Hello, after looking into my problem all night (it is 4 a.m. now) I still cannot get my One X out of its issue.
Background to this story:
Bought this phone from a friend who had TWRP2 as the recovery, unlocked, s-on, supercid. I wanted to upgrade to a newer ROM, specifically Carbon on Jellybean 4.2.2, and I needed to update hboot to accept the newer ROM. Follow the procedures of multiple threads and they all lead me down the same path of re-locking your bootloader and let the install do the rest. However, the installer has failed multiple times (error codes 140 and 158) and I am now stuck and have no idea where to go next.
The current status of the One X is not to great. It now has a relocked bootloader, HBOOT version of 2.14.0000, A broken recovery, what seems to be a mismatched baseband, Stuck at FASTBOOT USB, no ADB, will not boot into a ROM, RUU will not complete its job (fails at sending ROM), and I am all out energy and grammar.
*Trying to re-unlock the bootloader via HTCdev will NOT unlock it.
I am stuck, (yea I am a noob). If you need anymore info, just ask.

I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.

Flashing the stock recovery only really applies when you're trying to take an OTA, it isn't required for an RUU.
Sent from my Evita

whoooops just kidding then. might worth a shot to give it a try though? I was just tossing out ideas.

brotherross said:
I'm not entirely sure, but I think you should try and flash the stock recovery and then RUU. I couldn't find the stock recovery in RedPoint's compilation roll-up thread, but I found it on a youtube video when I searched "att one x stock recovery". After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
I am not exactly sure how to do that.

I honestly don't think that's going to help you anyway.
Sent from my Evita

timmaaa said:
I honestly don't think that's going to help you anyway.
Sent from my Evita
Click to expand...
Click to collapse
Alright, gonna need to fix it later. (Recovery still broken, I assume because of the failed RUU)

Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
brotherross said:
After you get the stock recovery installed I believe you should be able to then RUU.
Click to expand...
Click to collapse
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).

redpoint73 said:
Which RUU are you trying to run?
Is this the AT&T version of the One X?
Be aware that running any Jellybean RUU (3.18, 3.17) with S-on and SuperCID will brick the phone. So if you were trying to run a JB RUU, it might actually be a good thing it didn't install.
If you were trying to run an older RUU (2.20, etc.) then it will fail since the hboot version is older (hboot 2.14 goes with 3.1x).
Do you still have a TWRP nandroid available (if not, whey the heck not?!?!). Have you tried to flash TWRP again using fastboot? If that works you can try to get your nandroid restored. With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot.
---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------
As already pointed out by timmaaa, this is incorrect. RUU installs stock recovery on its own, and stock recovery is therefore not needed for an RUU (only an OTA).
Click to expand...
Click to collapse
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Anytype of backup was made on the phone with TWRP, if TWRP still exists on the phone, it should be there.
I have not tried flashing TWRP back. I can try that next, can you point me in the right direction? Which version of TWRP do you recommend? (I am a noob)
"With S-on, be aware that you will need to flash the boot.img for that ROM separately using fastboot." I am not aware of this, (again, noob) do I just extract the boot.img from the zip and use 'fastboot flash boot boot.img' ?

It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita

timmaaa said:
It looks like the problem is that you're trying to run an RUU that is older than your current firmware version. So, you would need to use a later RUU. But, like Redpoint said, if you are s-on and SuperCID this will brick your device. Maybe what you should try first is flashing TWRP recovery again and seeing if you can restore a backup or even just flash another ROM.
Download TWRP 2.6 from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and see if you can restore a backup. You are s-on so you will need to flash the boot.img from the ROM that's backed up after restoring it. If you didn't backup the boot partition you might be out of luck.
If this is the case, download a ROM (and gapps if it's an aosp ROM), extract the boot.img from the ROM zip and place it in your fastboot folder on your PC, copy the ROM zip (and gapps if applicable) to your phone, flash ROM zip (and gapps if applicable) in TWRP, reboot to bootloader, connect to pc, give this command:
Code:
fastboot flash boot boot.img
Reboot your phone and hopefully it will boot.
Sent from my Evita
Click to expand...
Click to collapse
I may need to reiterate, that my bootloader is still locked.

MDAWG25 said:
Yes, this is the AT&T version.
I was trying to do an RUU with RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25.
Click to expand...
Click to collapse
This is why you are getting errors 140 and 158. As timmaaa mentioned, you can't run an older RUU than the hboot that is already on your phone. The RUU you stated is very old, the 1.73 firmware with 1.09 hboot that came out at the phone's release. You are on hboot 2.14, so once the RUU sees that your hboot version is greater than that of the RUU (1.09), it fails.
Thye 3.18 RUU (which comes with hboot 2.14) would be what you want. BUT as already mentioned, you should not run this with S-on and SuperCID, as there is a bug with the Jellybean RUUs where this combo will brick the phone (not fixable without JTAG or new motherboard).
Follow timmaaa's steps in the previous post.
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
You might be in a catch-22 here then. As you know, you can't install custom recovery with a relocked bootloader (and S-on). You can keep trying to unlock it, but I'm not sure if that can be done if the phone can't boot.

MDAWG25 said:
I may need to reiterate, that my bootloader is still locked.
Click to expand...
Click to collapse
Sorry, I missed that. As Redpoint said above, you might be in a catch 22 situation here unfortunately.
Sent from my Evita

Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.

redpoint73 said:
Yeah, normally RUU would be the answer. But the RUU bricking bug mentioned is stopping you from going that route.
Keep trying to unlock the bootloader. If you were able to relock in the current condition, maybe you can unlock. Unlocking is quirky and will fail, then will succeed after multiple attempts. So just the fact it hasn't worked yet, doesn't necessarily mean it won't.
Click to expand...
Click to collapse
I am currently not home to interface with the device physically (RDP). I should be returning around 4PM EST.
The superCID was written by the previous owner. Writing a generic CID (like HTC_001) is not an option with s-on, is it?
*Are there any RUUs that won't brick when flashing?

<Sorry for the double post but this post is different then my last>
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.

You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
MDAWG25 said:
Interesting thing, I can still write the recovery image even though fastboot claims it is 'relocked'. Here is the command line output.
sending 'recovery' (8028 KB)...
OKAY [ 0.993s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
The signature checking failed, but it still accepted the image. Not sure if this means anything.
Click to expand...
Click to collapse
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita

timmaaa said:
You could try hex editing your CID back to its original CID, but it must be the original CID to match the CID that the RUU is looking for, not just any CID. In order for this to work your would need to have adb fully working though. Please note the method I linked to above is to gain SuperCID, but the principle is the same, you just want to change 11111111 back to CWS__001 for an at&t phone.
The only RUUs that won't brick are the lower ones, which you can't run because you're s-on.
Sent from my Evita
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Can you actually enter recovery? The failed message tells me that it hasn't worked.
Sent from my Evita
Click to expand...
Click to collapse
Fastboot claims it wrote the recovery image, it just failed the signature check, unless it reverted, should it still be there?
I am not home to try it. I am RDPing to my computer at home, which the phone is connected to. I should be home at 4PM EST (4 hours from now).
Here is a 'getvar all'
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT246*********** (omitted for privacy)
(bootloader) imei: 359****************** (omitted for privacy)
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
See anything out of the usual?
Being able to unlock the bootloader will solve all my issues, I should be able to try again when I get home.

It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita

timmaaa said:
It looks to me like it failed while writing, but I may be wrong. The info you just posted looks to be ok. I'd continue to try unlocking the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
I won't post again until 4pm est, as I do not have full access to the device.
Thank you for your help, I really do appreciate it.

Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/

Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app

rolo143 said:
Is there anyone who can help me S-off my HTC device?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Im in the same boat, Ive found my partition is write protected and cant find any other method to do it, I have tried both moonshine (my device isnt supported) and facepalm (protected partition) methods. Ive given up and stuck with MagioRom, which is like MaximusRom, but not so stable currently, but saying that the last RC5 of Magio is stable for me so far.

rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
Hi,
can you provide a log (or screenshots) of all the commands you enter and the files you push / pull?
Have you tried Moonshine S-OFF?

I can't. I didn't take screenshots, but believe me, I follow exactly the steps in the above mentioned thread to get supercid. But it just didn't stick. I keep getting T-MOB010 cid.
I think there's nothing I can do because my phone isn't supported by moonshine (I think) and my hboot is 2.15
Anyway I want to try MagioROM. Is it stable now or will it give me constant reboots?
Sent from my One S using xda app-developers app

Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Sent from my HTC One S using XDA Premium 4 mobile app

Malexion said:
Try to install official RUU to your phone. Before that you need reblocked your bootloader. After installation unlocked bootloader again and try get S-OFF.
Click to expand...
Click to collapse
+1 on Malexion's suggestion.
Being on HBOOT 2.15 is not enough. For Moonshine to work, you need to be on one of the supported firmwares listed at the top of the Moonshine OP:
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
Click to expand...
Click to collapse
If you have an RUU available for your carrier that's on one of those, it can be done..
I'm on T-Mobile US, and had accepted the OTA JB update to 3.14.531.17 before deciding to go for S-OFF. That little OTA update from .11 to .17 apparently includes some cute write protection that doesn't allow for SuperCID (among other things). As with you then, Facepalm was out of the question for me.
So I turned to Moonshine, which worked after jumping through the right hoops:
Downloaded supported RUU
Verified that RUU matched my carrier, HBOOT and baseband
Locked bootloader
Flashed RUU (in my case, I was going back to 3.14.531.11 (T-MOB))
Unlocked bootloader (you'll need to get a new unlock key from htcdev)
Ran Moonshine
Moonshine worked on the first try for me, but from reading the posts, it's clearly not as easy for everyone (especially on Windows for whatever reason).
Hopefully that helps, but happy to provide more info if you have questions.
Good luck!
---------- Post added at 10:23 PM ---------- Previous post was at 10:17 PM ----------
rolo143 said:
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Click to expand...
Click to collapse
Also, forgot to mention that Moonshine does not require SuperCID. I never had it and still don't. (If Moonshine S-OFF works for you, it's easy to get SuperCID if you really need it -- which I don't, so I haven't bothered yet).

T-Mobile
I'm also on T-Mobile and I wish I saw your post before I "upgraded" from .11 to .17. Quick question for you, because I just got this phone and don't know a whole lot about it. I've heard that HTC and/or Google released a jelly bean update that was horrible on the battery, and had to follow up with an update.
Is the .11 update the battery draining bad update? Is the battery drain problem something that can be fixed via a rom, rather than the update?
I guess that was more than one question, but any answers would be much appreciated. Also, if you could comment on your battery life since moving down to .11....

Yes, the .11 OTA was the first JB rollout for this phone, and the .17 OTA was released soon after to correct the battery drain issue.
I was only on the older .11 firmware for a few days before I flashed a new ROM, but it seemed pretty brutal. I'm still new to flashing ROMs, though, and I've read that it can take a new ROM a little time to optimize battery life... Not sure if that also applies to RUUs.
But it was bad enough that I would recommend only flashing the .11 firmware if you intend to switch to another ROM.
Anyhow, I flashed AOSPA 3+ a few days later and love it. A stable port, fast and fun to play with the hybrid engine. Battery life on PA has been good so far, seems on par or better than the .17 firmware in my case.
Hope that helps!
---------- Post added at 02:08 AM ---------- Previous post was at 01:50 AM ----------
Clarification: I would only bother with the older firmware as an interim step to (a) getting Moonshine S-OFF before flashing a new ROM, or (b) going back to stock and eventually the later .17 version via OTA.
(If you ever go back to stock, be *very* careful to read up on proper procedure before ever allowing a carrier OTA once you've played around with your phone... There are one or two cases where a carrier OTA is an instant brick scenario if you don't take the proper precautions).

When I type on cmd command:
"fastboot getvar all"
this is what appears:
Code:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT242W420470
imei: 359902047827302
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: T-MOB010
battery-status: good
battery-voltage: 3964mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Now, from here... Can someone please tell me how to find my corresponding RUU file? How can I install it? Do I need S-OFF for that? Please help... I don't really understand how can I achieve S-OFF in my HTC One S and I read a LOT of guides already.... Just don't know what can I do so I can install MaximusHD Rom and stick with it.

@rolo143: I'll pull together my exact steps for you when I'm in front of my computer again... In the meantime, to stay safe I would remove your serial number and imei from your last post.

Flashing the RUU so you can run Moonshine S-OFF
1: VERIFY ADB/FASTBOOT ENVIRONMENT & HTC DRIVERS ARE WORKING
Boot phone into fastboot mode (boot into bootloader, select "fastboot" from hboot menu).
Connect to PC (phone will now show "fastboot USB" highlighted), open command prompt and enter:
fastboot devices
It should return "[serial number] fastboot" if it's working properly.
You've already entered fastboot getvar all to get the info you need to get the correct RUU.
Click to expand...
Click to collapse
2: MAKE A NANDROID BACKUP
Use your custom recovery (TWRP or ClockworkMod) to make a backup of your device.
Put a copy of your nandroid onto your PC for safe keeping.
Click to expand...
Click to collapse
3: DOWNLOAD THE APPROPRIATE RUU
I got my RUU from this xda thread:
Since you're not S-OFF and SuperCID, you have to use an RUU that matches your carrier, hboot and baseband (radio).
Based upon your fastboot getvar all results...
Your carrier: T-MOB010 (cid) = TMUS (T-Mobile US carrier) ... I used this cid list to double-check this.
Your current hboot: 2.15, which will work with the JB 3.14.531.11 RUU you're going to flash, so you're good there.
Your current radio: 1.13.50.05.31.
I downloaded the matching RUU (you'll be using the same that I did):
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release... (truncated rest of filename).
Happily, this RUU is one of the four firmware versions supported by Moonshine S-OFF.
Click to expand...
Click to collapse
4. LOCK BOOTLOADER
Put phone into bootloader mode, connect to PC, open command prompt and enter:
fastboot devices
If it shows your serial number again, then enter:
fastboot oem lock
Your bootloader will now be locked and the phone may reboot back into bootloader. Leave the phone connected to the PC.
Click to expand...
Click to collapse
5. RUN THE RUU
Leave phone in fastboot mode (if it rebooted to bootloader you may need to select "fastboot" again). You should see "Fastboot USB" highlighted on the phone.
On your PC, run the RUU (.exe) that you downloaded. Give it a few minutes after you run it, as it took mine a while to actually look like it was doing anything.
Once it finally loads, you'll get a window that gives you a series of instructions. Follow them and then let it do it's thing.
Do NOT unplug your phone from the PC (I wouldn't touch the thing, frankly) until it reboots the phone automatically.
Once your phone reboots to system, it'll be running 3.14.531.11 Jellybean!
Click to expand...
Click to collapse
5. MOONSHINE S-OFF
Revisit the Moonshine S-OFF thread and follow the instructions very deliberately. Now that you're on a supported firmware, it should work.
---- EDIT ---- After you successfully run the RUU, you'll need to unlock your bootloader again before running Moonshine. You won't be able to use your old unlock .bin file, so you'll need to request a new one via htcdev. If you want to brush up on that, follow the unlock instructions on this xda tutorial thread.
Good luck!
Click to expand...
Click to collapse

Good post
When I did moonshine, I eventually put mint linux on a laptop just to get it to work. Where there is a will there is a way.

Thanks... I've learned a ton over the last few months from everyone being so supportive here. Want to give back a little where I can.
I tried and tried to set up Ubuntu Linux, but I simply could not get it to play nicely with my MacBook Pro. For my new Android obsession, I'm running Windows through Parallels, and I didn't want to use that for Moonshine since they don't officially support VMs. But the Ubuntu install on my particular hardware just kept throwing up too many roadblocks. Thankfully, I was able to pretty carefully manage my HTC driver setup on the Mac and in the VM, and once I figured out the right combo, my adb/fastboot connections have been rock solid. So I took a deep breath and gave Moonshine a go through Parallels, and it took on the first try. Go figure, after all of my toying around with Linux.

super cid
hi
my one s ville is for TIM Italya operator
when i want to perform super cid ,my cid is TIM--401
I change it to 11111111 but it doesnt work and my cid again is TIM--401
WHAT should i do for super cid my phone????

2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Great post and thank you for the effort to write the detailed instructions. I was able to successfully do the moonshine s-off

rolo143 said:
Please help me, I'm desperate.
- I want to install MaximusHD ROM.
- I have HBOOT 2.15.
- I unlocked bootloader via HTCDev.
- I have CM10.1 running on my phone.
I tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
This: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
I haven't even tried using the facepalm method because I can't get supercid.
After I followed all the steps correctly, I run command "fastboot oem readcid" and still get the T-MOB010 CID.
I repeated the whole process 3 times, making perfectly sure I didn't make any mistake and still, can't get supercid 11111111.
I tried using moonshine method too, but when I run distiller.exe at the end it says read and try again or something. So I just cant get S-OFF or supercid.
Please tell me how can I get MaximusHD Rom working on my phone! Please! :/
Click to expand...
Click to collapse
If it works in windows moonshine I did this tutorial but in spanish to help all who have problems to make the soff
http://www.taringa.net/posts/celulares/17401702/Como-hacer-soff-en-HTC-one-s-3-14-531-17RD.html

2k10GT said:
Flashing the RUU so you can run Moonshine S-OFF
Click to expand...
Click to collapse
Thanks for that concise summary. It helped me when I finally decided to get around to get S-OFF on my phone (flashing boot.img with every ROM switch/update/downgrade/etc. got tiresome).

Hello everybody!
I am can't get SuperCID in my HTC One S. In this time i have in phone root, unlock from htcdev and it's all. Trying with adb command receive T-MOB010 Cid, Moonshine after 3'd reboot stopping in '.........' in Fastboot. This '.......' points I am wait for 30 min and after disconnecting phone it still writing in comp screen. RUU from TMOB supported by Moonshine is installed to phone. What I wrong doing. *wall*. Help me, please!

> tried this method to get Supercid, because, as far as I know, you need to have Supercid before getting S-OFF. (Please correct me if I'm wrong)
Wait. You do not have to have SuperCID to get S-OFF.
Try moonshine. Some of us couldn't get S-OFF any other way. Also, I had to use an Ubuntu Live CD - Windows didn't work for me no matter what I tried. It kept getting stuck at "..........."
When I used the Ubuntu live CD it went right through.

ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0

lordofegypt said:
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT2CNW302531
imei: 354370050060697
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita

timmaaa said:
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
Click to expand...
Click to collapse
and concerning that backup you're talking about,,does it have to be matching my CID or any of my details ? or just any backup is fine ?

The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita

timmaaa said:
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
Click to expand...
Click to collapse
thx for the help,,ok so currently i found the needed NANDROID,,made the restore and am back to stock android 4.1.1 with relocked bootloader and stock recovery flashed,,i tried searching for software updates and it says no updates found when my neighbor got the same device and he recieved an update for 4.2.2 ??
however am not quite sure if the stock recovery flashed successfully or not ,,in the fastboot it said that the flashing was successful but when i tried to access the recovery from the boot it just went blank screen ,,is that ok and am not supposed to enter the stock recovery but then why it doesnt make the update ? or there's something wrong with the recovery i got ?

You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita

ngiyal 457
timmaaa said:
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
Click to expand...
Click to collapse
ok i found the recovery ,flashed it and able to access the recovery nw,,but in order to do so i had to unlock the bootloader again other wise it will just keep on booting into the bootmode which is kinda wierd...
anyway you got any ideas why am unable to receive the OTA ?

I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita

timmaaa said:
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
Click to expand...
Click to collapse
surprisingly i just got an update for the "people" app through searching for software updates (not through playstore)...does that mean that my OTA is working fine and its just a delay or something like that for the full software,,or this app update has nothing to do with the OTA's ?

The people app itself is separate from the OTA.
Sent from my Evita

j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me

madoooz said:
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
Click to expand...
Click to collapse
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You

jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
Click to expand...
Click to collapse
Just have a look in our Android Development section, you'll find it in there, along with some great custom ROMs you might want to try.
Sent from my Evita

jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well.
Click to expand...
Click to collapse
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
jnthnbgg said:
With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement.
Click to expand...
Click to collapse
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).

redpoint73 said:
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
Click to expand...
Click to collapse
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)

jnthnbgg said:
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
Click to expand...
Click to collapse
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita

timmaaa said:
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
Click to expand...
Click to collapse
Well I know it is the S-On as I saw even though I was doing all according to the instructions I could find. I had Unlock, SU CID, just could not get that S-OFF. I tried it manually, via the toolkits people have out there, using a 2.0 USB cable. But without the S-OFF I did not get the firmware installed so that was my source of headache with that I just had a bit of lag in the bootloader screen and i click one to many times past recovery and viola up the crick without a canoe lol

Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita

timmaaa said:
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
Click to expand...
Click to collapse
So going the route of Palm as I can not get adb to connect but I can fastboot USB, The first attempt ends with FAILED remote:92 supercid! please flush image again immediately. The second attempt ends in FAILED remote:99 unknow fail

You're gonna need to get adb working, both methods require it. I'm in a good mood so I'm gonna give you the solution to the error 99 problem, but please in future search properly before posting, the solution to that problem has been posted dozens of times in the Facepalm thread.
When you get error 99 after flashing the zip, you need to force a reboot to the bootloader and start the process again and you should get error 92 again.
Why isn't adb working? What ROM are you on? Have you updated your drivers? Do you have usb debugging turned on in Developer Options?
Sent from my Evita

Hi,
I got a Roger's HOX. I got the bootloader unlocked (from HTCDev site).
Now here is what I want to know:
- What's the difference between the unlocked and locked bootloader?
- Is it the same as S-OFF?
- If not, is there a "safe" method for S-OFF now?
- What does changing the CID do? does it make my Rogers HOX become a phone from another region or not from Rogers?
- If it does, will I get the update (system update mode) that is for non-Rogers HOX users?

johnrich23 said:
Hi,
I got a Roger's HOX. I got the bootloader unlocked (from HTCDev site).
Now here is what I want to know:
- What's the difference between the unlocked and locked bootloader?
- Is it the same as S-OFF?
- If not, is there a "safe" method for S-OFF now?
- What does changing the CID do? does it make my Rogers HOX become a phone from another region or not from Rogers?
- If it does, will I get the update (system update mode) that is for non-Rogers HOX users?
Click to expand...
Click to collapse
- An unlocked bootloader allows you to install a custom recovery, and in turn install root and custom ROMs, kernels etc. A locked bootloader obviously does not allow any of that.
- No it isn't the same as s-off. S-off means that all security checks have been disabled. One example of a benefit of this is that kernels and radios can be flashed in recovery.
- What do you mean by safe? There has never been a method that isn't safe. There are two known methods for s-off on our device, Facepalm S-off, and Rumrunner S-off.
- Changing the CID basically removes the hard-coded carrier designation on the device. Changing it does not really change the phone in any way, it just removes the carrier identity.
- You should still be able to check for updates, but you should never apply an official update on a modified device.
Sent from my Evita

timmaaa said:
- An unlocked bootloader allows you to install a custom recovery, and in turn install root and custom ROMs, kernels etc. A locked bootloader obviously does not allow any of that.
- No it isn't the same as s-off. S-off means that all security checks have been disabled. One example of a benefit of this is that kernels and radios can be flashed in recovery.
- What do you mean by safe? There has never been a method that isn't safe. There are two known methods for s-off on our device, Facepalm S-off, and Rumrunner S-off.
- Changing the CID basically removes the hard-coded carrier designation on the device. Changing it does not really change the phone in any way, it just removes the carrier identity.
- You should still be able to check for updates, but you should never apply an official update on a modified device.
Sent from my Evita
Click to expand...
Click to collapse
as for the Rumrunner, I've read the instructions carefully, especially this line on the instructions
Your device must be HTCDEV unlocked or rooted unless using rumrunner with a device blocked by htcdev (e.g. m7wlv)
the OR clause makes me think that having a rooted phone is optional. but when I tried it. it notified me that the phone is not rooted. do you have links for rooting it, I'm having problems looking it up on the forums

You just need to install Superuser or SuperSU through a custom recovery to get root. Do you have a custom recovery installed yet?
And what is your end goal? Do you want to retain your stock ROM? Do you want to install a custom Sense ROM? Do you want to install a custom aosp ROM? If it's aosp you're after, do you want KitKat or older Android versions. It's important for me to know so I can advise you properly.
Sent from my Evita

timmaaa said:
- An unlocked bootloader allows you to install a custom recovery, and in turn install root and custom ROMs, kernels etc. A locked bootloader obviously does not allow any of that.
- No it isn't the same as s-off. S-off means that all security checks have been disabled. One example of a benefit of this is that kernels and radios can be flashed in recovery.
- What do you mean by safe? There has never been a method that isn't safe. There are two known methods for s-off on our device, Facepalm S-off, and Rumrunner S-off.
- Changing the CID basically removes the hard-coded carrier designation on the device. Changing it does not really change the phone in any way, it just removes the carrier identity.
- You should still be able to check for updates, but you should never apply an official update on a modified device.
Sent from my Evita
Click to expand...
Click to collapse
I just want to have my Rogers HOX updated to 4.2.2 which is officially impossible. So I am looking for options to get my phone change region (just get out of rogers) and try to do Official Update from other region (pref Asia). I once did this to my Vodafone HTC Desire Z and got it to WWE. but I can't search the said post so I can compare

johnrich23 said:
I just want to have my Rogers HOX updated to 4.2.2 which is officially impossible. So I am looking for options to get my phone change region (just get out of rogers) and try to do Official Update from other region (pref Asia). I once did this to my Vodafone HTC Desire Z and got it to WWE. but I can't search the said post so I can compare
Click to expand...
Click to collapse
Ok. That's possible but it's going to be a bit of a pain the butt. Have you considered installing a custom ROM? There are many added benefits and it's a hell of a lot easier. What are your bootloader details? I only need the first five lines.

which are the one's I need to get?
these are the one's I got from doing getvar all on fastboot
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.631.2
version-misc: PVT SHIP S-ON
serialno: HT24RW300168
imei: XXXXXXXXXXXXXXX
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: ROGER001
battery-status: good
battery-voltage: 4127mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11 gencheckpt: 0
maybe this helps, I am really a bit scared on flashing, as I have hard bricked one(QHUSB_DLOAD something like that) and threw away my 4month old HTC Desire Z before for flashing

johnrich23 said:
which are the one's I need to get?
these are the one's I got from doing getvar all on fastboot
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.23a.32.09.29
version-cpld: None
version-microp: None
version-main: 3.17.631.2
version-misc: PVT SHIP S-ON
serialno: HT24RW300168
imei: XXXXXXXXXXXXXXX
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: ROGER001
battery-status: good
battery-voltage: 4127mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11 gencheckpt: 0
maybe this helps, I am really a bit scared on flashing, as I have hard bricked one(QHUSB_DLOAD something like that) and threw away my 4month old HTC Desire Z before for flashing
Click to expand...
Click to collapse
I did mean the information displayed on your phone screen while booted into the bootloader, but that's fine
You have a far greater chance of bricking your device by trying to update using semi official methods than you would by just flashing a ROM. As long as you only download ROMs from our specific device forum you'll be totally fine. Bricking really only occurs due to carelessness or ignorance.
With your phone the way it is currently all you need to do is this:
Install TWRP recovery from here.
Install a Sense 5 Android 4.2.2 ROM (something like Kickdroid might be suitable) from here.
Get s-off using the Rumrunner method here.
Install the 2.15 firmware from the beginning of this thread.
Then you'll be enjoying what seems like a brand new phone. I'd suggest you read my Evita FAQ and How-To Guide For Beginners threads in my signature, they contain some ultra valuable information and directions you'll need.

Questions:
- By doing these steps, may HOX is rooted and flashed right?
- I wont be seeing that annoying Rogers on startup?
- There is a way to revert all of these?
I just recently had my phone hung on bootloader when I tried "writecid" command with this setting on my phone and really feared that I had done paperweight 2.0 (1.0 being HTC Desire Z)

johnrich23 said:
Questions:
- By doing these steps, may HOX is rooted and flashed right?
- I wont be seeing that annoying Rogers on startup?
- There is a way to revert all of these?
I just recently had my phone hung on bootloader when I tried "writecid" command with this setting on my phone and really feared that I had done paperweight 2.0 (1.0 being HTC Desire Z)
Click to expand...
Click to collapse
-Flashed is a fairly ambiguous term but I guess you could say that, yes. You will be rooted as the custom ROMs are generally pre-rooted.
-You won't see Rogers anymore, you'll have a completely new boot animation. Each ROM usually has a unique boot animation.
-You can revert to your stock ROM as long as you make a backup in TWRP before installing a new ROM (inductions in my How-To thread). If you want to revert to a completely stock setup you can run a Rogers RUU, change your CID back, relock your bootloader, return to s-on.
The writecid command will only work once you have s-off. That reminds me, once you have s-off you'll need to change your CID to SuperCID in order to flash the 2.15 firmware I mentioned. I'm assuming you already know it but here's the command:
Code:
fastboot oem writecid 11111111
Sent from my Evita

timmaaa said:
You have a far greater chance of bricking your device by trying to update using semi official methods than you would by just flashing a ROM.
Click to expand...
Click to collapse
Agree. To change CID, you need the bootloader unlocked and root, anyway. So you might as well just install custom recovery, s-off and enable yourself to flash any variety of custom ROMs or stock rooted ROMs. Modifying the CID in order to install an update by "semi official" means (as timmaaa puts it) is risky, and we've seen at least a few folks brick their phones here doing similar things.
---------- Post added at 09:09 AM ---------- Previous post was at 08:59 AM ----------
johnrich23 said:
Questions:
- By doing these steps, may HOX is rooted and flashed right?
Click to expand...
Click to collapse
As timmaaa mentioned, the word "flashed" is fairly vague and doesn't really mean much of anything. The term "flash" basically refers to any type of firmware installation to a non-volatile form of memory. You can "flash" new BIOS to your computer's motherboard, or updated firmware to your router for example. Even the original factory installed OS, bootloader, radio, etc. can be considered a "flash".
If you mean flashing a custom ROM, then yes following timmaaa's steps you will have that.
Honestly, if you have been flashing custom ROMs on your old Desire Z (great phone for its time, BTW, I had one too!) you should already know the answers to many of the questions you are asking. My impression is that you may be going about things a bit haphazardly and without the proper knowledge (quite probably why you bricked your DZ). I would suggest slowing down, and doing a lot more reading and research using timmaaa's FAQ and Beginner guide, before proceeding with any mods to the phone. Get a good understanding of the concepts and processes first, otherwise you will brick another phone.
My Index thread also has a ton of info: http://forum.xda-developers.com/showthread.php?t=1671237

I was reading your guide for beginner's. and I'm a bit stuck on the part of Making a Nandroid Backup with TWRP Recovery.
The instructions were a bit vague for me.
how do you do this?
"All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes."
- where is the TWRP home screen?
on my HBOOT, here are the screens I see
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- before seeing that *** TAMPERED *** part on top of unlocked. I just went to recovery

johnrich23 said:
I was reading your guide for beginner's. and I'm a bit stuck on the part of Making a Nandroid Backup with TWRP Recovery.
The instructions were a bit vague for me.
how do you do this?
"All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes."
- where is the TWRP home screen?
on my HBOOT, here are the screens I see
View attachment 2592304 View attachment 2592305
- before seeing that *** TAMPERED *** part on top of unlocked. I just went to recovery
Click to expand...
Click to collapse
The TWRP home screen is the first screen you see when you enter recovery. You can enter recovery by selecting it from the bootloader screen (volume keys scroll, power key selects). Of course you must have TWRP recovery installed to use the backup feature, have you installed it yet?
Sent from my Evita

yes, I followed the steps by putting the following commands
fastboot flash recovery "filename.img"
fastboot erase cache
fastboot reboot-bootloader
How do I know if its already installed?

Have you tried to enter TWRP?
Sent from my Evita
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
Also, the "filename.img" part of my tutorial command is just an example. You did enter the exact filename in your command didn't you?
Sent from my Evita
---------- Post added at 01:41 AM ---------- Previous post was at 01:39 AM ----------
So the command should look exactly like this:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita

johnrich23 said:
- where is the TWRP home screen?
on my HBOOT, here are the screens I see
View attachment 2592304 View attachment 2592305
Click to expand...
Click to collapse
Again, this is something (booting to recovery from bootloader) you should already know if you have flashed custom ROMs on another device before.

I think, I did it now. will update you on the process, if Im stuck with something. (i really have to practice reading the instructions from now on, don't want to lose another phone)

timmaaa said:
- Changing the CID basically removes the hard-coded carrier designation on the device. Changing it does not really change the phone in any way, it just removes the carrier identity.
Click to expand...
Click to collapse
Does this mean that a carrier (sim) unlock would fail?
I am trying to get this done from Rogers the code they provide does not work.
Thanks
----
Rooted
Unlocked
S/OFF
Super CID

CottenCandy said:
Does this mean that a carrier (sim) unlock would fail?
I am trying to get this done from Rogers the code they provide does not work.
Thanks
----
Rooted
Unlocked
S/OFF
Super CID
Click to expand...
Click to collapse
No I don't think so. You do need to be on a Sense ROM for an unlock code to work though.
Sent from my Evita

timmaaa said:
No I don't think so. You do need to be on a Sense ROM for an unlock code to work though.
Sent from my Evita
Click to expand...
Click to collapse
Ah, I see!
Can it be any sense ROM or does it have to be an actual HTC ROM?
Is it easy to return the phone back to normal (RUU) after all I've done to it?
Thanks!