Database Info

[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

[Q] Trying to flash AOKP MR-1

I'm on PA 2.54, which I flashed a few months ago, but I want to flash AOKP MR-1 (or any nightly newer than that), however, when I flash it, it shows the AOKP text art in the install zip from SD card, then it goes down to something along the lines of "HTC One X // evita", then the progress bar goes to like 70%, and it freezes there. After a couple of minutes, the progress bar ends, but it never went any further than the model name, and when I try to boot, it just stays on the HTC screen.
This happens with every build of AOKP.
This is the AT&T HTC One X.

Ratzu said:
I'm on PA 2.54, which I flashed a few months ago, but I want to flash AOKP MR-1 (or any nightly newer than that), however, when I flash it, it shows the AOKP text art in the install zip from SD card, then it goes down to something along the lines of "HTC One X // evita", then the progress bar goes to like 70%, and it freezes there. After a couple of minutes, the progress bar ends, but it never whent any further than the model name, and when I try to boot, it just stays on the HTC screen.
This happens with every build of AOKP.
This is the AT&T HTC One.
Click to expand...
Click to collapse
Wrong phone? this is the One XL Forums.

exad said:
Wrong phone? this is the One XL Forums.
Click to expand...
Click to collapse
Whoops, meant One X.

Ratzu said:
Whoops, meant One X.
Click to expand...
Click to collapse
What hboot? what recovery/version? S-ON or S-OFF?

exad said:
What hboot? what recovery/version? S-ON or S-OFF?
Click to expand...
Click to collapse
I have ClockworkMod Recovery v6.0.3.1.
How do I check my hboot?
I'm pretty sure it's S-ON, because I don't remember turning it off, but how can I check to be sure?

Ratzu said:
I have ClockworkMod Recovery v6.0.3.1.
How do I check my hboot?
I'm pretty sure it's S-ON, because I don't remember turning it off, but how can I check to be sure?
Click to expand...
Click to collapse
I'm surprised you managed to root without even knowing what your hboot is or what S-ON/S-OFF is -_-
You're in a dangerous situation my friend. You know just enough to royally screw yourself but not enough to know that you might.
Hboot version and Secrity lock status are both in the bootloader.

exad;41197Do177 said:
I'm surprised you managed to root without even knowing what your hboot is or what S-ON/S-OFF is -_-
You're in a dangerous situation my friend. You know just enough to royally screw yourself but not enough to know that you might.
Hboot version and Secrity lock status are both in the bootloader.
Click to expand...
Click to collapse
I know what boot and s-off/s-on are, it's just that I went through this process almost six months ago, so I don't exactly remember what I did and didn't do.
S-ON
HBoot 1.14.0002
Do I need S-OFF?

No you just need to fastboot boot boot.img
You can extract boot.img from the rom zip.
S-off would eliminate the need for that step.
Sent from my One X using xda app-developers app

That didn't work.
EDIT: Never mind, I typed in fastboot boot boot.img instead of fastboot flash boot boot.img
Thanks

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] RUU question

i just want to know how you use a ruu? i want to upgrade to 3.18 just dont know how to use the ruu

Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita

RollTribe said:
Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita
Click to expand...
Click to collapse
i am s-off will i have to re root my phone after i use the ruu?

The RUU will return your phone to completely stock, so of course you will not have root anymore. But, your unlocked bootloader and s-off status will survive the process so all you need to do is flash TWRP again and then you can flash a rooted ROM.
Sent from my Evita

timmaaa said:
The RUU will return your phone to completely stock, so of course you will not have root anymore. But, your unlocked bootloader and s-off status will survive the process so all you need to do is flash TWRP again and then you can flash a rooted ROM.
Sent from my Evita
Click to expand...
Click to collapse
awsome so do i just fastboot flash a recovery?

Yep. I recommend TWRP 2.6
Sent from my Evita

timmaaa said:
Yep. I recommend TWRP 2.6
Sent from my Evita
Click to expand...
Click to collapse
ok oh and timmaaa you the man iv asked questions here before and you always come thru with a good answer

No worries mate. I only ask that you share your knowledge and help others where you can
Sent from my Evita

timmaaa said:
Yep. I recommend TWRP 2.6
Sent from my Evita
Click to expand...
Click to collapse
yo time im having troubles getting twrp 2.6 flashed. when i fastboot flash recovery openrecovery-twrp-2.6.0.0-evita it does nothing?

696kris969 said:
yo time im having troubles getting twrp 2.6 flashed. when i fastboot flash recovery openrecovery-twrp-2.6.0.0-evita it does nothing?
Click to expand...
Click to collapse
You are putting the ".img" on the end of the command right?
Sent from my Evita

I S-OFF'd and ran the 3.18 RUU in order to run CM 10.1 nightlies. I'm thinking about selling this phone, so would I just run the same RUU again in order to return to stock AT&T status?
Sent from my One X using Tapatalk 4

jkel777 said:
I S-OFF'd and ran the 3.18 RUU in order to run CM 10.1 nightlies. I'm thinking about selling this phone, so would I just run the same RUU again in order to return to stock AT&T status?
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
You could relock if you want to, but it doesn't really matter.
Sent from my evita

RollTribe said:
Just plug in your phone and run it. It's an exe file.
Be sure you're s-off, though, unless you're stock.
Sent from my evita
Click to expand...
Click to collapse
Maybe a stupid question but does the phone have to be in fastboot mode to run the ruu?
Sent from my HTC One XL using xda premium

MrMiami81 said:
Maybe a stupid question but does the phone have to be in fastboot mode to run the ruu?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yes, I believe it does have to be in fastboot.
Sent from my HTC One X using Tapatalk 4

jkel777 said:
Yes, I believe it does have to be in fastboot.
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
Yes. Fastboot to run the ruu exe.
Fastboot -----> fastboot oem rebootRUU to use the ruu zip
Fastboot flash zip rom.zip
Sent from my HTC One using Tapatalk 2

Can't S-Off for the life of me

Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.

I got s-off with viper
Sent from my VENOMized HoxL

area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?

Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita

timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)

Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita

timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.

The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita

timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2

Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.

Did you flash the boot.img via fastboot?
Sent from my Evita

timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.

It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita

timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.

It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita

timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0

Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita

timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP