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
Related
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: *************
imei: **************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Jojo1992 said:
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: SH26RW404047
imei: 359901049107937
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Jojo1992 said:
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Click to expand...
Click to collapse
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
tivofool said:
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
Click to expand...
Click to collapse
i downloaded an RUU:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
then i make this:
fastboot devices
fastboot oem lock
then start RUU, but error no connection to device but in cmd i get a connection
I have a CID 111111 is that the Problem?
Jojo1992 said:
I have a CID 111111 is that the Problem?
Click to expand...
Click to collapse
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
tivofool said:
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
Click to expand...
Click to collapse
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Jojo1992 said:
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Click to expand...
Click to collapse
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
tivofool said:
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Jojo1992 said:
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Click to expand...
Click to collapse
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
tivofool said:
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
Click to expand...
Click to collapse
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Jojo1992 said:
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Click to expand...
Click to collapse
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
tivofool said:
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Jojo1992 said:
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Click to expand...
Click to collapse
There is a stock recovery here
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
The SECOND download is the stock one
Unless you change the name of the recovery the command will probably look more like this:
fastboot flash recovery ville_recovery_signed.img
And yes
fastboot oem lock
after you have flashed the stock recovery of course
tivofool said:
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
[/url]
Click to expand...
Click to collapse
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Jojo1992 said:
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Click to expand...
Click to collapse
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
tivofool said:
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
Click to expand...
Click to collapse
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Jojo1992 said:
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Click to expand...
Click to collapse
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
tivofool said:
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
Click to expand...
Click to collapse
ok thank you very much for the help!
Hi mate good day!
i have htc one s, t-mobile, its unlocked bootloader and s-off using moonshine.
I install the MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0.
after that i only got 2g services.
now im planning to go back to previous rom, anyway, i dont have any back up of my previous rom,
so i decided to download ruu.
I need your help, what are the step to go back to my previous rom.
THIS IS THE INFORMATION OF MY HTC ONE S.
BOOTLOADER.
***TAMPERED***
***LOCKED***
VLE PVT SIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 16 2013,16:59:47:-1
thanks i hope you could me guys,
thanks
bump
rhandeh said:
Hi mate good day!
i have htc one s, t-mobile, its unlocked bootloader and s-off using moonshine.
I install the MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0.
after that i only got 2g services.
now im planning to go back to previous rom, anyway, i dont have any back up of my previous rom,
so i decided to download ruu.
I need your help, what are the step to go back to my previous rom.
THIS IS THE INFORMATION OF MY HTC ONE S.
BOOTLOADER.
***TAMPERED***
***LOCKED***
VLE PVT SIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 16 2013,16:59:47:-1
thanks i hope you could me guys,
thanks
Click to expand...
Click to collapse
Your device is htc one S VILLE C2 (S3 processor) ?
xuanhai266 said:
Your device is htc one S VILLE C2 (S3 processor) ?
Click to expand...
Click to collapse
Nope it's t-mobile, s4 processor
Thanks
rhandeh said:
Hi mate good day!
i have htc one s, t-mobile, its unlocked bootloader and s-off using moonshine.
I install the MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0.
after that i only got 2g services.
now im planning to go back to previous rom, anyway, i dont have any back up of my previous rom,
so i decided to download ruu.
I need your help, what are the step to go back to my previous rom.
THIS IS THE INFORMATION OF MY HTC ONE S.
BOOTLOADER.
***TAMPERED***
***LOCKED***
VLE PVT SIP S-OFF RL
CID-T-MOB010
HBOOT-2.16.0000
RADIO-1.20.50.05.16
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 16 2013,16:59:47:-1
thanks i hope you could me guys,
thanks
Click to expand...
Click to collapse
Go ahead and unlock the bootloader, no reason to have it locked since you are S-off.
Run your RUU.exe
That should put the stock recovery back on. Then go into bootloader and clear storage/factory reset.
Then put back CWM or TWRP recovery and your old ROM
----------------------
If you get an error running the RUU try putting stock recovery on first then running RUU.exe.
tfool said:
Go ahead and unlock the bootloader, no reason to have it locked since you are S-off.
Run your RUU.exe
That should put the stock recovery back on. Then go into bootloader and clear storage/factory reset.
Then put back CWM or TWRP recovery and your old ROM
----------------------
If you get an error running the RUU try putting stock recovery on first then running RUU.exe.
Click to expand...
Click to collapse
Thanks for the help. I will do that. I will update if theres error on it.
Thanks.
tivofool said:
Go ahead and unlock the bootloader, no reason to have it locked since you are S-off.
Run your RUU.exe
That should put the stock recovery back on. Then go into bootloader and clear storage/factory reset.
Then put back CWM or TWRP recovery and your old ROM
----------------------
If you get an error running the RUU try putting stock recovery on first then running RUU.exe.
Click to expand...
Click to collapse
hi mate, i want to ask, when i unlock my bootloader again, do i need to relock it, to run ruu.exe? or its ok, to run ruu.exe since i am s-off now?
thanks
rhandeh said:
hi mate, i want to ask, when i unlock my bootloader again, do i need to relock it, to run ruu.exe? or its ok, to run ruu.exe since i am s-off now?
thanks
Click to expand...
Click to collapse
You are ok to leave it unlocked, I have run a RUU many times with unlocked bootloader. (as long as you are S-Off)
tivofool said:
You are ok to leave it unlocked, I have run a RUU many times with unlocked bootloader. (as long as you are S-Off)
Click to expand...
Click to collapse
You think it will resolved the 4g issue when I go back to stock Rom.
Having hard time when I used data connection. I'm stuck in 2g only.
Well mate thanks for the reply I really appreciated.
tivofool said:
You are ok to leave it unlocked, I have run a RUU many times with unlocked bootloader. (as long as you are S-Off)
Click to expand...
Click to collapse
hi mate.. i have a problem about ruu.exe that i download.
i try 3 ruu.exe for tmobile, but still no luck.
heres the ruu.exe that i download
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed
RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed
and then i got this pop up error.
i attached it.
i hope you could help me,
i unlock my bootloader already.
thanks mate.
rhandeh said:
and then i got this pop up error.
Click to expand...
Click to collapse
Hmmm. Ok lets go through running a RUU and hopefully get it.
Phone needs to be in bootloader (fastboot USB) to run the RUU
Better to be plugged into a USB 2.0
Right click the RUU and run as administrator.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Still error? You could flash stock recovery.
fastboot flash recovery ville_recovery_signed.img
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
Once you have flashed the recovery, do a factory reset in bootloader. Then try the RUU.
I've read somewhere that you need to lock your bootloader in order to run the RUU?
Dont know for sure, but worth a try? :laugh:
tivofool said:
Hmmm. Ok lets go through running a RUU and hopefully get it.
Phone needs to be in bootloader (fastboot USB) to run the RUU
Better to be plugged into a USB 2.0
Right click the RUU and run as administrator.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Still error? You could flash stock recovery.
fastboot flash recovery ville_recovery_signed.img
https://dl.dropboxusercontent.com/u/84212943/ville_recovery_signed.img
Once you have flashed the recovery, do a factory reset in bootloader. Then try the RUU.
Click to expand...
Click to collapse
hi mate, i got back from stock rom. yehey!
i have problem, i got 2 simcard,
one is supported with 4g which i insert, and 4g show up, but few minutes, it become 2g again,
and the other one, who is supported only 3g, i only got 2g still.
but i never factory reset on recovery mode.
wht you think i would do to gain back fully service of 3g or 4g.
thanks
rhandeh said:
hi mate, i got back from stock rom. yehey!
i have problem, i got 2 simcard,
one is supported with 4g which i insert, and 4g show up, but few minutes, it become 2g again,
and the other one, who is supported only 3g, i only got 2g still.
but i never factory reset on recovery mode.
wht you think i would do to gain back fully service of 3g or 4g.
thanks
Click to expand...
Click to collapse
Glad you got back to stock.
Sorry but I don't know about 2g -4g service. I haven't really read any posts that showed how to correct the problem. Sorry.
tivofool said:
Glad you got back to stock.
Sorry but I don't know about 2g -4g service. I haven't really read any posts that showed how to correct the problem. Sorry.
Click to expand...
Click to collapse
i see. its ok mate,thanks for the help again...
rhandeh said:
i see. its ok mate,thanks for the help again...
Click to expand...
Click to collapse
Well here is how someone fixed theirs
http://forum.xda-developers.com/showthread.php?t=2160389&page=19
Seems like you might need to keep reading in that thread, as it definitely doesn't sound easy.
Starts at post #190 where he fixed his.
help needed in downgrade
i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
IIRC the RUU for your device reverts all of that. Not 100% sure about the S-ON though.
I've read somewhere in another guild that it's necessary to first Relock your bootloader (using the oem lock command) and afterwards use the right RUU for your device...
I thought this could be helpful
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader first will cause this to not be the case?
DRUMROT said:
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader it first will cause this to not be the case?
Click to expand...
Click to collapse
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
FantasyGamer said:
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
Click to expand...
Click to collapse
Yeah, I'm assuming I'd have to do some more then just run the RUU.
I'd gladly give it a go but like I posted earlier, I'd like to know if there is a certain order to do this in. If I run the RUU before removing s-off, will that make things easier? Harder? No different?
Anyone?
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
FantasyGamer said:
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
Click to expand...
Click to collapse
Hmmm, all right. I've never used the all-in-one kit but I've noticed it has a "back to s-on" function so I'll give it a try. I'm on Linux so I need to run it in Wine (Windows emulator) so hopefully there's no hiccups.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
1)If you have put on a modified HBoot (such as to remove tampered or red warning) return to stock.
(only added this because if you S-on with modified HBoot it will brick your phone)
2)Run RUU.exe
3)Reset lock status flag
http://forum.xda-developers.com/showthread.php?t=2155955
4)S-ON your phone
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
---------- Post added at 01:15 PM ---------- Previous post was at 01:05 PM ----------
Edited that, If anyone notices a problem please post.
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
FantasyGamer said:
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
Click to expand...
Click to collapse
No, it doesn't need to be locked when S-OFF.
The most important is running the RUU that matches your CID. (since you are s-off it is easy to change the CID to whatever you want, and thus run whatever RUU you want)
i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot
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.