Database Info

[Q] One X (evita) not booting CM10/10.1

I have an HTC One X sitting here that I bought from somebody. It came rooted with an unlocked bootloader running CleanRom. I downloaded CM, wiped like usual and flashed the rom. I can't get it to boot now, it endlessly shows the CM boot logo (but doesn't appear to be restarting) and I was wondering if there was anything special I had to do to get CM working.

Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2

rpomponio said:
Fastboot flash boot boot.img......
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I take the boot.img from the zip and flash that in fastboot?

driftkidd2323 said:
I take the boot.img from the zip and flash that in fastboot?
Click to expand...
Click to collapse
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2

rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
cm10 booted right up, thanks!

driftkidd2323 said:
cm10 booted right up, thanks!
Click to expand...
Click to collapse
Your welcome, please hit the thanks button.
Sent from my HTC One XL using Tapatalk 2

Help
rpomponio said:
Yes sir. Depending on what version your hboot is, that might be your problem..
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.

cassidyc123 said:
Hello, I as well have a HTC one X Evita the HBoot curently is 1.14.0002 Do you belive that is the problem with mine as well? If so I do know how to use Fastboot and all but do i need to Install the ROM first then Flash the boot.img over or does it mater what order.
Click to expand...
Click to collapse
If you are on hboot 1.14, and have flashed CM10, and not the boot.img, than yes, this almost certainly your problem.
It doesn't matter whether you flash boot.img over fastboot before or after the ROM.

Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D

danishdaycare said:
Whats the diffence between the boot.img found in the 10.1 zipfile for htc one x and the one linked in download :
Boot.img (secure=0): http://d-h.st/vzF
Which one should I chose?
/ D
Click to expand...
Click to collapse
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.

DvineLord said:
um http://d-h.st/vzF is for the endeavoru so NO one here would EVER flash it. do you have an evita or an endeavoru? this forum is for the evita.
Click to expand...
Click to collapse
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.

flint24 said:
I accidentally flashed my evita with an endeavoru boot.img and now it's stuck in a splash screen boot loop. Is there any way to fix this? Thanks guys.
Click to expand...
Click to collapse
Flash the evita boot.img?

exad said:
Flash the evita boot.img?
Click to expand...
Click to collapse
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610

flint24 said:
Sure but which one? Any one? I found this link by Googling but I hope I'm putting the right boot on my phone. I got my One XL from Germany around November 2012.
http://forum.xda-developers.com/showthread.php?t=2119610
Click to expand...
Click to collapse
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.

Myrder said:
If you bootloader says Evita, stay here. If not, run away... far, far away and never come back.
If it is evita go to a cm10/10.1 thread, grab the correct version and pull the boot.img from it. NEVER google for anything, now that you have found this forum. That's one of the quickest ways to break your phone.
Click to expand...
Click to collapse
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?

flint24 said:
Thanks. I'm downloading it now from a reeeeaaaally slow connection so it'll take time to see if this works.
Also I've unlocked my bootloader but it also says "TAMPERED." Should I be worried about that?
Click to expand...
Click to collapse
Tampered is an indication that you unlocked the phone. You can remove it by RUUing after S-OFF if it bothers you.

I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now

flint24 said:
I followed Myrder's advice and loaded CM 10 for evita and it got me back into my phone but the touchscreen isn't working now
Click to expand...
Click to collapse
If you have hboot 2.14 you need to downgrade your touchscreen firmware to get touchscreen working in AOSP ROMS

Sounds to me like you really need to do some reading. And really, reading should be done before attempting any of the things you're doing to your phone. You're lucky you haven't bricked it.
Sent from my Evita using XDA Premium

I'm kind of in a chicken before the egg situation. I found the files and commands needed to downgrade my touchscreen, however I think this requires the phone to have usb debugging on, which I can't select because the touchscreen doesn't work.
If that's not necessary because it's all in fastboot anyway, then I have to figure out why I'm getting a "remote 99 unknown fail" and a "status read fail too many links" error message when I try to run the commands for S-OFF and touchscreen downgrade in bootloader.

[Q] unable to revert to stock

So I tried to install a custom rom on my phone, yet I was stupid and did not back it up. The phone is stuck in a boot loop. I tried using the 1.85 RUU, but kept getting error 155 (i tried everything). please excuse my noobness, I have absolutely no idea what I am doing.

Where did you get to? What hboot are you on? Did you flash recovery? Can you get to recovery?
If you don't know what the hell you're doing why the hell would you root your phone? If you wanted to juggle fire would you just start or look into the risks and safest ways to do it first?
Sent from my One X using xda app-developers app

exad said:
Where did you get to? What hboot are you on? Did you flash recovery? Can you get to recovery?
If you don't know what the hell you're doing why the hell would you root your phone? If you wanted to juggle fire would you just start or look into the risks and safest ways to do it first?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
i've gotten into recovery and my hboot is 1.14.0002

When you flash a rom, because you're on hboot 1.14 you need to fastboot flash boot boot.IMG
The boot.IMG would be extracted from the rom you're flashing.
Sent from my One X using xda app-developers app

exad said:
When you flash a rom, because you're on hboot 1.14 you need to fastboot flash boot boot.IMG
The boot.IMG would be extracted from the rom you're flashing.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I tried going from stock ics to ice cold. I flashed the boot.img, and then in cwm it gave me an error and could not flash the rom

alexeloplaw said:
I tried going from stock ics to ice cold. I flashed the boot.img, and then in cwm it gave me an error and could not flash the rom
Click to expand...
Click to collapse
What kind of error did it give you?

alexeloplaw said:
I tried going from stock ics to ice cold.
Click to expand...
Click to collapse
Be sure you're using the right version of IC. There is only one version, a jelly bean port, that works on this phone. Everything else will hard brick you. There is no evita version of IceColdSandwich.
You can't use the 1.85 RUU with 1.14 hboot unless you're s-off. You're probably on 2.20.

alexeloplaw said:
I tried going from stock ics to ice cold. I flashed the boot.img, and then in cwm it gave me an error and could not flash the rom
Click to expand...
Click to collapse
im not sure. it said installation failed haha

iElvis said:
Be sure you're using the right version of IC. There is only one version, a jelly bean port, that works on this phone. Everything else will hard brick you. There is no evita version of IceColdSandwich.
You can't use the 1.85 RUU with 1.14 hboot unless you're s-off. You're probably on 2.20.
Click to expand...
Click to collapse
well how should i go about fixing this? im sorry, i'm so clueless.

alexeloplaw said:
well how should i go about fixing this? im sorry, i'm so clueless.
Click to expand...
Click to collapse
Download the 2.20 ruu
Reboot to bootloader
Fastboot oem lock
Run the ruu
Don't reroot until you know what you're doing.
Sent from my Nexus 7 using Tapatalk HD

iElvis said:
Download the 2.20 ruu
Reboot to bootloader
Fastboot oem lock
Run the ruu
Don't reroot until you know what you're doing.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thank you so much! i tried rooting again and flashed cm10 haha. I just didn't know how to revert to stock

Problem when installing Cm 10.1 based roms

I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.

avlbj6 said:
I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.
Click to expand...
Click to collapse
If you can get into bootloader try flashing the boot.img via fastboot

ronnie498 said:
If you can get into bootloader try flashing the boot.img via fastboot
Click to expand...
Click to collapse
I can't get into bootloader

If you have adb access, what happens when you do:
Code:
adb reboot bootloader

hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
He won't have adb access because that requires the phone to be booted into the OS.
Sent from my Evita

then connect to pc,that way my phone was somehow reconized and i was able to adb
Click to expand...
Click to collapse
:fingers-crossed:

hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.

avlbj6 said:
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.
Click to expand...
Click to collapse
Did you run the 3.18 RUU?

What hboot and firmware version are you on?
Sent from my Evita

Hboot 1.09
Sent from my HTC One XL using Tapatalk 2

hi_cannon said:
Did you run the 3.18 RUU?
Click to expand...
Click to collapse
No I didn't.is that so?
Sent from my HTC One XL using Tapatalk 2

timmaaa said:
What hboot and firmware version are you on?
Sent from my Evita
Click to expand...
Click to collapse
Hboot 1.09
Sent from my HTC One XL using Tapatalk 2

odd problem until now since newest aosp need 3.18 base or 2.14 hboot.

I keep confusing quote with reply smh lol

DvineLord said:
odd problem until now since newest aosp need 3.18 base or 2.14 hboot.
Click to expand...
Click to collapse
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2

avlbj6 said:
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita

timmaaa said:
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks man.And I'm already s-off and I been running magiorom since he released it.But ima do the ruu part now
Sent from my HTC One XL using Tapatalk 2

[Q] Post root unable to access phone through ADB

AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.

alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!

Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app

Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.

You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app

exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.

Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app

Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium

exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***

Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app

exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium

Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app

Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium

31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium

31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18

If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?

Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.

So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?

Return to stock

Guys
I have to return to stock so that i can my phone back to HTC for factory work. It is not going back to TMOB.
With all that i have done i want to make sure i follow the steps and do everything.
I currently have upgraded to the latest firmware 3.14 and have HBOOT 2.15.0000. I'm S-OFF with Super CID.
what do i need to un-do in order to return to stock?
Can i simply flash a stock RUU and relock or do i need to put TMOB CID back on, go to S-ON, etc?
all help is appreciated.
Rugged

Rugged96 said:
Guys
I have to return to stock so that i can my phone back to HTC for factory work. It is not going back to TMOB.
With all that i have done i want to make sure i follow the steps and do everything.
I currently have upgraded to the latest firmware 3.14 and have HBOOT 2.15.0000. I'm S-OFF with Super CID.
what do i need to un-do in order to return to stock?
Can i simply flash a stock RUU and relock or do i need to put TMOB CID back on, go to S-ON, etc?
all help is appreciated.
Rugged
Click to expand...
Click to collapse
Run this command
fastboot oem writecid T-MOB010
Go Here
For unlocked to locked
Download RUU
Run ruu
And plz for the love of god make sure your on stock hboot (meaning all ready ran a ruu ) when you give this command or you will brick
fastboot oem writesecureflag 3
You should now be bone stock
Sent from my One S using Tapatalk 2

Flashalot said:
Run this command
fastboot oem writecid T-MOB010
Go Here
For unlocked to locked
Download RUU
Run ruu
And plz for the love of god make sure your on stock hboot (meaning all ready ran a ruu ) when you give this command or you will brick
fastboot oem writesecureflag 3
You should now be bone stock
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
that's exactly what i ended up doing. i had to run around 3 different threads to find the steps but i got it to work. thanks for putting it together in one place!

Rugged96 said:
that's exactly what i ended up doing. i had to run around 3 different threads to find the steps but i got it to work. thanks for putting it together in one place!
Click to expand...
Click to collapse
No problem glad to help
Sent from my One S using Tapatalk 2

HTC is shipping me back my phone but i'm curious.
what are the odds that they repaired my version vs just sending me a refurb device?

Flashalot said:
Run this command
fastboot oem writecid T-MOB010
Go Here
For unlocked to locked
Download RUU
Run ruu
And plz for the love of god make sure your on stock hboot (meaning all ready ran a ruu ) when you give this command or you will brick
fastboot oem writesecureflag 3
You should now be bone stock
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
okay...it looks like i got my exact same phone back...how do i 'undo' these steps? i assume it's easier than starting from scratch.

Rugged96 said:
okay...it looks like i got my exact same phone back...how do i 'undo' these steps? i assume it's easier than starting from scratch.
Click to expand...
Click to collapse
To being rooted or stock
Sent from my One S using Tapatalk 2

Flashalot said:
To being rooted or stock
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
I want to go back to unlocked, Super CID, S-Off and Root. since i was previously all those things do i start completely over?

Rugged96 said:
I want to go back to unlocked, Super CID, S-Off and Root. since i was previously all those things do i start completely over?
Click to expand...
Click to collapse
Unlock/Root using Hasoon's AIO tool
if you don't mind answering, why exactly do you want to SuperCID/S-OFF?

I want to install the latest kernel and run cm10.1
Sent using Tapatalk 2

Rugged96 said:
I want to install the latest kernel and run cm10.1
Sent using Tapatalk 2
Click to expand...
Click to collapse
For that you need unlocked bootloader, custom recovery and root. No S-OFF/SuperCID needed.
In fact, largely, some folks have reported bricks running CM10.2 (4.3) with S-OFF.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
For that you need unlocked bootloader, custom recovery and root. No S-OFF/SuperCID needed.
In fact, largely, some folks have reported bricks running CM10.2 (4.3) with S-OFF.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I prefer to have S-OFF for the ease of flashing and I was planning CM10.1 not 10.2...i'm not ready for that fun yet

Rugged96 said:
I prefer to have S-OFF for the ease of flashing and I was planning CM10.1 not 10.2...i'm not ready for that fun yet
Click to expand...
Click to collapse
Mooneshie then fastboot oem writecid 11111111
Sent from my HTC VLE_U using Tapatalk 2