Database Info

Can't flash anything, RUU isn't working.

So, I used to be an Android expert and knew what was wrong just by the symptoms of the problem, having had an iPhone for about 4 months has changed all that. I'm still familiar with some of the stuff, fast boot, installing a recovery, mostly basic things, so I come here to the community I uses to help in.
Here's my issue: Viper ROM was installed, and I wanted to try out Rebel ROM. Downloaded it, but wouldn't connect to my computer through the ROM, so I booted to recovery to mount the internal storage.
It wouldn't flash, stating an error, tried CleanROM, same error. Now there's no OS on the phone, so I decided to RUU so I'd have something too work with.
Its on 2.20 so I downloaded that one, and program ran fine till it told me there was an error and so I can't even have a stock ROM.
TL;DR It can boot to recovery, fast boot, but can't flash a ROM or RUU. Any ideas? Thanks guys for your replies.
Sent from my Nexus 7 using Tapatalk 2

Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off

The error is because you didn't lock your bootloader before running the ruu fastboot oem lock

subarudroid said:
Did you try extracting the boot.IMG from the ROM, fastboot flash boot.img. if your on 1.14 Hboot you'll need to do this.
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.

a box of kittens said:
The error is because you didn't lock your bootloader before running the ruu fastboot oem lock
Click to expand...
Click to collapse
Oh, thank you sir! I'll look up how to do that.
There's no way to downgrade the hboot, is there?

Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not

a box of kittens said:
Flashing boot imgs can only be done through fastboot without s off(which I highly recommend you do) but tutorial on fastboot coming up!
Click to expand...
Click to collapse
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.

http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533 here is the download link
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
theking_13 said:
My device is S-ON, so I should S-OFF it?
And no way to downgrade the hboot? I know you can't RUU down to an earlier version because of this.
Click to expand...
Click to collapse
Yes s off makes things 100 x easier and without s off you can't downgrade hboot through ruu

Thank you sir! With S-OFF, I can RUU back to an earlier version? I tried searching through the dev section, I mostly found ROMs, and a couple mods.

http://forum.xda-developers.com/showthread.php?t=2155071 here is our s off thread very easy after that you can flash the ruu and it will downgrade your hboot... I recokmend you flash to viper than you do s off..but I'll link you to the ruu thread in a sec
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
http://www.androidfiles.org/ruu/?dir=Evita all the ruus... Get the att 1.85 ruu

theking_13 said:
I am on hboot 1.14, can I use XsMagicals program? I'd rather use the ADB commands but I've forgotten them.
Click to expand...
Click to collapse
Yes you can. But I'd go with what kitten says. S-off = happiness with flashing ROMs to your hearts content.
Sent from my HOX w/CM10.1 4.2.2 s-off

I keep sending the boot.img to the HOX via ADB, but when I try to install it in TWRP, I still get that same error. What am I missing here guys?

Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off

subarudroid said:
Turn off the md5 check before u flash the ROM zip
Sent from my HOX w/CM10.1 4.2.2 s-off
Click to expand...
Click to collapse
In the settings? Nothing is checked, and when I flash the ROM, the option that says "Zip file signature verification" is also unchecked.

Here's the error I get.
Code:
E: error in sdcard/CleanROM JL Beta 1.zip
(Status 1)
Error flashing zip 'sdcard/CleanROM JL Beta 1.zip'
Updating partition details...
[COLOR="Red"]Failed[/COLOR]

Nvm, fixed it! Thanks to both of you, couldn't have done it without your input.

[Q] at&t HOX how to flash 4.2.2, Recovery & CID problem

Hello guys
I've just received att HOX from ebay, and when i enter in bootloader, it's kinda strange,
because it says "EVITA" in bootloader menu.
Bootloader is unlocked, S-OFF, CID-1111111
HBOOT 1.09.0000
I want to flash Android Revolution HD 31.0 JB rom, but it needs Custom recovery, which i can't flash.
Tried several times, but when i want to enter Recovery, says "This build is for development purposes only Do not distribute outside oh HTC ... bla bla" with red text and stucks there.
Also, it needs Firmware.zip, which defends on CID, but i don't know original CID of my phone.
Can i use whatever firmware.zip I want?
Please tell me which firmware should i choose, which recovery should i flash,
and why it says "Evita"? It's not One XL and it's not on Tegra 3 chipset..
Any help would be greatly appreciated ))

It says Evita because it's a One XL, not a One X. Android Revolution is not meant for this phone, so don't try to flash that. Only get ROMs from this forum, the development threads are here and here.
The reason your recovery won't load is probably because you're flashing the wrong one. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone. Just make sure you only get ROMs from the two links I provided before.
Sent from my Evita
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Also, don't mess around with the CID or any firmware zips, it's not necessary.
Sent from my Evita
---------- Post added at 03:24 AM ---------- Previous post was at 03:10 AM ----------
Oh and another thing, if you want to flash any of the latest aosp ROMs you'll need to RUU up to the latest. You can find the 3.18 RUU here. Because you have s-off it doesn't matter that you have SuperCID (11111111).
Sent from my Evita

timmaaa said:
It says Evita because it's a One XL, not a One X. Android Revolution is not meant for this phone, so don't try to flash that. Only get ROMs from this forum, the development threads are here and here.
The reason your recovery won't load is probably because you're flashing the wrong one. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone. Just make sure you only get ROMs from the two links I provided before.
Sent from my Evita
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
Also, don't mess around with the CID or any firmware zips, it's not necessary.
Sent from my Evita
---------- Post added at 03:24 AM ---------- Previous post was at 03:10 AM ----------
Oh and another thing, if you want to flash any of the latest aosp ROMs you'll need to RUU up to the latest. You can find the 3.18 RUU here. Because you have s-off it doesn't matter that you have SuperCID (11111111).
Sent from my Evita
Click to expand...
Click to collapse
First of all, thank you for your reply))
But i think it's not XL, i had doubt about it, but phone storage is 16GB, not 32
I've tried and flashed TWRP 2.6 recovery and boot.img of Android Revolution HD 31,
now it says same first, when i try to enter recovery, then loads TWRP. but as i think it cant read internal memory, i tried to WIPE data, but it says no storage/ sd-ext ... are mounted and finishes with error.
Also, phone doesn't power up now. When i power up normally, it shows "This build is for development purposes only Do not distribute outside oh HTC ..." again and stucks there.
Don't know what to do, as i know difference between One X and One XL is internal storage (XL 32 GB)
but definitely it has 16 only..

uNdea said:
First of all, thank you for your reply))
But i think it's not XL, i had doubt about it, but phone storage is 16GB, not 32
I've tried and flashed TWRP 2.6 recovery and boot.img of Android Revolution HD 31,
now it says same first, when i try to enter recovery, then loads TWRP. but as i think it cant read internal memory, i tried to WIPE data, but it says no storage/ sd-ext ... are mounted and finishes with error.
Also, phone doesn't power up now. When i power up normally, it shows "This build is for development purposes only Do not distribute outside oh HTC ..." again and stucks there.
Don't know what to do, as i know difference between One X and One XL is internal storage (XL 32 GB)
but definitely it has 16 only..
Click to expand...
Click to collapse
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita

timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
Tim is 100% Correct.
Evita = One XL
Endeavor = One X

timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
I'm sorry for that, I'm don't want to brick my phone.
I don't have more knowledge about it than you, so take my apologies
I had flashed that before I read your post).
I'll try your method and post about result.
Thanks again and sorry for my English.

Your English is fine, don't worry about that. Just make sure you only download ROMs from the two development sections I linked to before.
Sent from my Evita

timmaaa said:
You clearly don't know the difference between the two models at all. It has nothing to do with the internal storage. I actually know what I'm talking about and I'm trying to stop you from bricking your phone.
Evita is the codename for the One XL. This is the phone you have.
Endeavor is the codename for the One X. You do not have this phone.
Also, the One XL comes in 16gb and 32gb models.
Hopefully that's clear enough for your to understand and you'll stop trying to brick your phone now?
Or you can continue to ignore the educated advice I'm giving you and continue flashing things that aren't meant for your phone and destroy it. It's your choice though.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa said:
Your English is fine, don't worry about that. Just make sure you only download ROMs from the two development sections I linked to before.
Sent from my Evita
Click to expand...
Click to collapse
Flashed TWRP and it enters normally, but still when i try Wipe/factory reset, gives error and says that "unable to mount storage, sdcard and etc"
Is it normal?
I'll try to flash 3.18 RUU now, because phone doesn't boot up and I cant place custom ROM on internal storage.
Am i doing it right?

uNdea said:
Flashed TWRP and it enters normally, but still when i try Wipe/factory reset, gives error and says that "unable to mount storage, sdcard and etc"
Is it normal?
I'll try to flash 3.18 RUU now, because phone doesn't boot up and I cant place custom ROM on internal storage.
Am i doing it right?
Click to expand...
Click to collapse
if you are using twrp 2.6 you can just format the SD card in twrp, it should work fine after.

exad said:
if you are using twrp 2.6 you can just format the SD card in twrp, it should work fine after.
Click to expand...
Click to collapse
Thank you, I've formatted SD card and WIPE option has worked!
But i have no idea why i get that message when i try to power on phone normally..
"This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action."
Can i fix it without RUU?

uNdea said:
Thank you, I've formatted SD card and WIPE option has worked!
But i have no idea why i get that message when i try to power on phone normally..
"This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action."
Can i fix it without RUU?
Click to expand...
Click to collapse
That's normal. if it bothers you that much, you can flash a modified hboot. There's a link in the mods section of the resource compilation thread. There's a link in my signature.

exad said:
That's normal. if it bothers you that much, you can flash a modified hboot. There's a link in the mods section of the resource compilation thread. There's a link in my signature.
Click to expand...
Click to collapse
It's nothing if phone will boot up, but it restarts and restarts. Seems bootloop

uNdea said:
It's nothing if phone will boot up, but it restarts and restarts. Seems bootloop
Click to expand...
Click to collapse
What rom did you flash?

exad said:
What rom did you flash?
Click to expand...
Click to collapse
Just flashed Boot.img from Android revolution HD.zip file, nothing more.
Im trying to flash boot.img of stock ICS, maybe it will fix that..

Please link me to the rom you flashed.
Sent from my One X using xda app-developers app

exad said:
Please link me to the rom you flashed.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Flashed Boot.img from this == > > http://forum.xda-developers.com/showthread.php?t=1562603
************
I've flashed RUU 3.18 for evita and that problem is fixed, phone works normally with hboot 2.14.
Will try to flash recovery and some Sense 5 custom rom now. Thanks for help))

uNdea said:
Just flashed Boot.img from Android revolution HD.zip file, nothing more.
Im trying to flash boot.img of stock ICS, maybe it will fix that..
Click to expand...
Click to collapse
Like timmaaa, told you your phone is a evita, so the boot.img you installed from Android revolution HD.zip is not good, My evita is the first evita att issued and it is only 16 GB (referbished for $10.00, got what I payed for )
Hboot 1.09 and boot.img, radio.img, etc..
1.85.502.3_UrDroid_TWRP_Firmware_Aroma_Installer.zip
EDIT: late .. Glad you figured things out

uNdea said:
Flashed Boot.img from this == > > http://forum.xda-developers.com/showthread.php?t=1562603
************
I've flashed RUU 3.18 for evita and that problem is fixed, phone works normally with hboot 2.14.
Will try to flash recovery and some Sense 5 custom rom now. Thanks for help))
Click to expand...
Click to collapse
Mate, I told you in the beginning that Android Revolution is not for your phone. So like Carl said, that boot.img is not for your phone. ONLY EVER GET ROMS FROM THE TWO LINKS I PROVIDED IN MY FIRST REPLY. Also, you don't need to flash the boot.img, you are s-off so it doesn't matter.
Sent from my Evita

[Q] HTC ONE XL size Issue

Hello there guys,
Been trying to root my XL from Telstra (AUS) but some weird things are going on.
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
http://forum.xda-developers.com/showthread.php?t=1952038
Also, tried to root my phone using this thread below:
http://forum.xda-developers.com/showthread.php?t=1859478
So far, I have achieved to Installed S-OFF and CWM.
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Im uploading some of the current photos taken so you guys can have more information on S-OFF and CWM.
Thanks in advance.
Ps: One of the pictures was a Failed OTA from Telstra, is there a way to go back to and be able to install the OTA from Telstra instead of any custom ROM (In case we cant find what is causing the phone to block the supercid and the super SU)

Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app

31ken31 said:
Ota won't work with a custom recovery.
I am running MagioR4 sense 5 4.2.2 you can install that now without doing anything else to your phone. There are a few others as well, but this is only one I've been running so I can't say much about others, but assume they will work out just as well.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?

Desertum said:
Can't figure out why i'm unable to to SuperCid my phone, my current Supercid is TELST001
Click to expand...
Click to collapse
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Desertum said:
Hi there mate,
Tried to run Super Su and shows as the phone been not rooted, i'm a bit confused atm.
Is there a need to Super Cid and if i were to use the OTA, can i remove the custom recovery?
Click to expand...
Click to collapse
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Desertum said:
What i'm trying to do here is to use any 4.22 Android Rom with sense 5, like CleanROM or CyanogenMod 10
Click to expand...
Click to collapse
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.

redpoint73 said:
That's the carrier ID (CID) not SuperCID. SuperCID is 11111111 or 22222222. I think you know that, but let's get the terms right to avoid confusion.
You don't have S-off. It says right in your screenshot that the phone is still s-on.
But you it says UNLOCKED, so your bootloader is unlocked. All S-on means is that you can still install custom ROMs, you just have to flash boot.img seperately from fastboot.
As mentioned, you have to return to stock recovery in order to be able to install OTAs. Easiest way is to RUU back to stock. But be completely sure you are not SuperCID, otherwise S-on + SuperCID + Jellybean RUU = BRICK.
Personally, going stock just to install the stock 4.2.2 ROM is a step backward, not forward, as you already have an unlocked bootloader and cutom recovery. But you also seem confused about a number of things. I would suggest reading and more fully understanding the concepts and processes before proceeding with any further mods to the phone.
---------- Post added at 09:17 AM ---------- Previous post was at 09:12 AM ----------
Unlocking the bootloader does't root the phone. You can flash an SU package in recovery to obtain root, or flash a rooted ROM.
You don't need SuperCID for anything but s-off.
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
CleanROM is neither 4.2.2 nor Sense 5. CM10 is an AOSP ROM, so by definition not a Sense ROM at all.
Click to expand...
Click to collapse
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks

Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Thanks
Click to expand...
Click to collapse
No you've got it backwards. The boot.img goes in your fastboot folder on your pc, not on your phone.
You need to fastboot flash the boot.img from each ROM you want to flash. So, if you want to install CM10.2, you must extract the boot.img from the ROM zip and put it in your fastboot folder on your pc (not your sd card in your phone). Then you put the ROM zip on your phone, and install it in recovery (after wiping cache/dalvik cache/factory reset/system), then reboot to bootloader and flash the boot.img using fastboot. You must follow this process for each new ROM you want to flash.
Do a backup of your current setup in recovery before flashing anything new though.
Sent from my Evita
---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------
By the way, even though our phone doesn't have a physical sd slot, we refer to the stage as the sd card.
Sent from my Evita

Desertum said:
Hello there,
Thanks for making things clear, for the time being i need to load the boot.img from fastboot and after that I can install a custom rom like this one?
http://forum.xda-developers.com/showthread.php?p=44053927
Click to expand...
Click to collapse
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
Desertum said:
Hello there,
I remember that you need to copy the IMG file to the sd card but the Htc one xl has not got a Sd card at all, What can i do?
Click to expand...
Click to collapse
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.

redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
Hi there,
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
I was trying to update the RUU, then restart the phone, went into S-off, then into recovery and Wipe factory/data reset, then install the CM10.2 build
Is something missing here?
Thanks.

Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Also, what do you mean you "went into s-off"?
Sent from my Evita
Click to expand...
Click to collapse
Sent from my Evita

Desertum said:
Im trying to Update the RUU as per this thread:
http://forum.xda-developers.com/showthread.php?t=2382933
However, I'm getting an error called 155, which says that Im trying to install the wrong RUU
Click to expand...
Click to collapse
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.

redpoint73 said:
It would be highly beneficial for you to read the top post of any ROM thread you want to install, as the dev usually has some important info. In the ROM you linked, it clearly says:
Installation Instructions (These are all required)
1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU.
Also, at a minimum, I will read the last few pages (most recent) of the ROM thread, just to see if there are any prominent bugs or, issues or useful tips being discussed.
I think you are misunderstanding what I mean when I say "flash the boot.img using fastboot". You need to extract the boot.img from the ROM you want to flash (boot.img us often specific to the ROM). With boot.img on your computer, flash it to the phone using fastboot.
There are ways to flash boot.img without a computer. But since you specifically mentioned fastboot, the file does not go on your SD card in this case.
But again, this is not particularly applicable to CM10.2, since the dev is specifically recommending to have s-off before flashing. S-off means you do not have to flash boot.img seperately (it happens automatically when you flash the ROM in recovery).
Also, the phone does have an SD, its just not removable. Think of it as a virtual SD card.
Click to expand...
Click to collapse
timmaaa said:
Which RUU are you trying to install? The 3.18 RUU suggested at the start of the thread?
My suggestion is to get s-off first, and you need to get SuperCID before you get s-off. Flash any rooted sense ROM from the development section, you need root to get SuperCID.
Sent from my Evita
---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------
Sent from my Evita
Click to expand...
Click to collapse
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.

Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
Click to expand...
Click to collapse
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.

Desertum said:
Hi there, I'm getting confused of what you are saying, Thought that I have already S-OFF and as previous comments, I don't need to touch SuperSid, as per the Root, I believed it was already rooted.
And yes, I'm trying to install the 3.18 RUU, currently using 3.17.
Thanks.
Click to expand...
Click to collapse
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita

John uallowt
redpoint73 said:
Its saying wrong RUU, because its the wrong RUU.
If you are S-on, you can only run an RUU meant for your Telstra version.
It appears you ignored my previous advice to read up on the basic concepts and procedures, before continuing to try to mod the phone.
Click to expand...
Click to collapse
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Are you able to do some prompts in regards of what to do?
So far, IMAO I need to to this:
Flash the Correct RUU (Gotta find it first)
Use S-off to Install the Custom ROM (ROM is already copied to the phone's memory)
Install the new Custom ROM, however, not to sure about the GApps, which are google apps.
http://www.reddit.com/r/Android/comments/1kbeoh/gapps_20130813_for_android_43_and_20130812_for/
I guess that you need to copy them before you install the new ROM?
Thank you for your patience.

redpoint73 said:
I think this is a lost cause. You aren't even reading what people have replied to you. I clearly stated in post #4 above, you DO NOT have s-off.
Right in your second screen shot (white bootloader screen) it says S-ON (third line of text). This means you DO NOT HAVE S-OFF.
Click to expand...
Click to collapse
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?

Desertum said:
I have not ignored your advised, It rather hard to understand all this, since there is no Indication for the right RUU, since the thread i'm looking at, does not mention anything in regards of using a different RUU.
I apologise If you feel like i'm ignoring your advised, I would rather ask you now, What should I do?
Click to expand...
Click to collapse
As you've been told at least 3 times now, what you should do is READ READ READ.
None of this is hard to understand once you start diving into it and learning.
I'm personally not going to spoonfeed you any more steps (and suggest against doing it either), as shortcutting the learning process is only going to turn your phone into an expensive paperweight.

timmaaa said:
Like Redpoint just said, you can't install an RUU from another carrier (the 3.18 RUU is at&t) while you're s-on. You don't have s-off, look at the screenshots you attached earlier, in your bootloader it says s-on. You have an unlocked bootloader which is an entirely different thing.
Unless you've flashed a superuser zip or flashed a rooted ROM you don't have root. Root just means that you have administrative access to system files in a ROM. The real thing you need to install custom ROMs is an unlocked bootloader and a custom recovery.
I'm gonna be honest, you're in over your head and you're ignoring good advice which was given to prevent you from damaging your phone.
You really have two choices: either do a hell of a lot of reading until you have a firm understanding of what you're doing, or leave your phone alone. The way you're going right now you're on track to destroy your phone.
Do yourself a favour and click on the link in my signature. It's a resource thread, it contains all the information you'll ever need. I'll put it this way, I read for a week or two before I even started modifying my phones.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.

Desertum said:
Fair enough, I need to read more about it.
As i Have atm S-ON and I need to have S-off to be able to install the RUU and the custom Rom, I either need to accomplish this :
SuperUser the Phone with the current Stock ROM
or
Install a Rooted ROM, correct?
Click to expand...
Click to collapse
We're getting there, here are the exact steps you need to take:
1) Read a lot.
2) Read some more.
3) Flash a superuser zip on your current stock ROM, or flash a rooted Sense ROM so you have root.
4) Get SuperCID.
5) Get s-off.
6) RUU to latest.
7) Flash whatever ROM you want.
Sent from my Evita
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
Desertum said:
Thank you, If you put it that way then it makes more clear, stay away from your phone before you bricked it!
Will read about you've said before,however I have tried several ways to Super SU this phone and nothing works.
http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/
Tried the one above, and no good.
Thanks for the help, will leave it as it is until I feel more confident about how to get this thing going.
Click to expand...
Click to collapse
Just go to our Android Development section here and flash one of the new Sense 5 ROMs. They're already rooted.
Don't get information/software from anywhere except XDA by the way.
Sent from my Evita

He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app

31ken31 said:
He is already on 2.14 hboot I'm not even sure why he's trying to ruu.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Good catch. I missed that.
To the OP: you don't need to RUU to install cm10.2 on your device as you already have the required hboot/firmware. Without s-off you will need to manually flash the boot.img using fastboot though.
Sent from my Evita

[Q] Brick or not?

HI all,
I tried to flashed the RUU but it seems that the version I flashed was lower than the one I had.
Now the screen is just black and I can not use the power + down vol to get to fastboot at all.
it will be greatly appreciated if I can get some guidance to get to the fastboot.
Cheers

What exactly did you flash? What does the phone show up on windows as? Does charge light come on when plugged into wall? Did the ruu complete? s-on or s-off?
You really didn't give much info.
Sent from my iPhone using Tapatalk

apology - duplicate post

bricked
thanks you for the response.
sorry I was not sure what info to give.
I was trying to flash RUU asia HK because I originally from STOCK turge but everytime I have a conversation my phone keep shuting down.
so I did (quoting from the instruction page):
Download HTC One X Stock Recovery
Download correct HTC One X boot.img and RUU based on CID. Download CID Getter from Google Play Store and run it, it will show your CID.
For this case, cidnum is HTC_044. The correct RUU is X.XX.707.X. Make sure you have downloaded the correct RUU.
Extract Fastboot.zip into a new folder, renamed the folder to Fastboot. Recommended to extract the folder to drive.
Copy and paste the downloaded stock recovery img and boot img into Fastboot folder.
Boot HTC One X into fastboot mode by press and hold Volume Down + Power button.
Connect your phone to the computer via USB cable.
At your computer, open up Command Prompt windows. (To OpenCommand Prompt –> Windows Logo–> Type CMD in search box –>Enter)
Type fastboot flash recovery endeavoru_recovery_signed.img , followed by fastboot reboot-bootloader and fastboot erase cache.
Once you flashed the stock recovery, continue to flash boot.img to your phone. Type fastboot flash boot boot.img, followed by fastboot reboot-bootloader and fastboot erase cache.
Now, relock the bootloader by typing fastboot oem lock, followed by fastboot reboot-bootloader and fastboot erase cache.
Your phone will restart after you have relock the bootloader.
Boot into Fastboot mode.
Double click the RUU, follow the updater instruction.
Wait the sending file to your phone, it normally takes 5-6 minutes.
Once the installation/update completes, your phone will automatically reboot.
when I last look at the details My CID is still 11111111 but status "RELOCKED" - it says also "EVITA PVT SHIP S-OFF RL"
HBOOT 2.14.0000
does this mean that I can safely run RUU:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.7z
If there still more things to do, would you kindly direct me to the correct link to follow.
THank you

Never mind, didn't read properly. Will edit and repost.
Sent from my Evita
---------- Post added at 10:48 PM ---------- Previous post was at 10:44 PM ----------
Your first problem is that you're flashing things that aren't intended for your device. The recovery you flashed is for the Endeavoru, you have the Evita. The second problem is it looks like you're getting your information from the wrong place, to go back to stock you don't need to flash a recovery or a boot.img, all you need to do is flash the right RUU for your device. What RUU did you already run? I need the exact filename. Does your phone power on at all? Can you reach the bootloader?
Sent from my Evita
---------- Post added at 10:51 PM ---------- Previous post was at 10:48 PM ----------
I see you're looking at all kinds of different threads at the moment, that isn't going to help because I don't think you know exactly what you're doing, you don't know what you've done, and you don't know how to recover from it. Your best bet is to stay in this thread and I'll try to help you work out what's gone wrong.
Sent from my Evita

RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers

ardabelati said:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
this is the one I ran earlier.
The progress is that I somehow manage to get to fastboot by pressing the vol down and power .
I am trying to download : RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe at the moment but it seems that the first download did not complete - so I am downloading again,
is this what I need to do? just run the RUU?
Cheers
Click to expand...
Click to collapse
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!

You got seriously lucky. You ran an RUU intended for the HTC One X (codename Endeavoru), you don't have that phone. You have the HTC One XL / at&t One X (codename Evita), they're completely different phones. Note how the first RUU you ran has Endeavoru in the filename, that's bad, really bad, don't ever flash anything that doesn't have the Evita codename within the filename. If it has Evita in the filename it's for your phone, if it has anything else don't touch it, burn it, run away. Like I said, you're incredibly lucky your phone isn't bricked right now.
I can only assume that you're a bit confused and have been hopping between the two forums for these phones. In future stay within this device forum that you're posting in now, don't ever go anywhere else. You don't even need to visit other websites because, seriously, everything you'll ever need is right here within this device forum. Plus other sites don't properly distinguish between the models which causes confusion.
Anyway. The second RUU that you've listed there is perfectly fine for your phone. I can't guarantee that it's going to work though because previously running the wrong RUU could have really messed things up on your phone. But your only hope is to cross your fingers and run it now. Let me know how it all goes.
Sent from my Evita
---------- Post added 28th November 2013 at 12:12 AM ---------- Previous post was 27th November 2013 at 11:49 PM ----------
ndmuni said:
U should download one that has the same radio as yrs also it will take fast download speed otherwise it will keep breaking up. t took me 4 attempts before I manage to download it yesterday (same file as one u r trying) good luck cheers!
Click to expand...
Click to collapse
What are you talking about? He doesn't need to use an RUU with the same radio/baseband that's currently on his device, that's just wrong. Firstly the idea of an RUU is to update your device, therefore traditionally you'd be updating to a newer radio version than the one that's currently installed. With s-on you can only run an RUU that contains a firmware version that's equal to or greater than your current firmware. This user has s-off though so he can run any RUU that he wants to, including earlier ones (RUU'ing backwards). I don't know where you got the idea that you need to run an RUU with the same radio as your existing radio but it's just plain wrong, and you really shouldn't be telling people that.
Sent from my Evita

ndmuni said:
U should download one that has the same radio as yrs
Click to expand...
Click to collapse
False. With s-on, you can only run RUUs for your CID, and with the same or latter hboot and firmware number. So if you were having trouble flashing an RUU, its probably because you were s-on and trying to either flash another carrier's RUU, or an older version.
The OP is s-off, so therefore all security checks are off. He can flash the RUU for any carrier, any version. As long as its meant for our device (EVITA), of course.

Hi guys
Thank you for all the guidance.
I got the 4.1.1 on my phone now and phone is use-able. I can not thank you guys enough for the help.
After i finished RUU flash the phone detected the new firmware update. When i dowloaded and tried to update, it says that the phone has been modified and they can not run/install the update. When i checked my boot it shows :
"relocked"
cid is still 111111.
Evita pvt ship s-off RL
HBOOT: 2.14
radio : 0.23a.32.09.29
Do i need to do more installation before my phone can get the update from HTC like the one coming out from the factory?
Cheers.
Arda
Sent from my HTC One XL using Tapatalk

You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita

timmaaa said:
You need to change your CID back to the stock CID to take the OTA update.
Sent from my Evita
Click to expand...
Click to collapse
I searching in the forum about changing CID. But it seems that is all about how to change CID to 111111. Is there any tutorial to revert back to original CID?
Do i need to sort out my s-off first before changing CID?
Thank you in advance.
Regards
Arda

You said in a previous post that you're s-off. So are you s-off or s-on? Please boot into bootloader and post your bootloader details again.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated.
Cheers

All you need to do is issue a fastboot command:
Code:
fastboot oem writecid xxxxxxxx
The x's represent the new CID.
Sent from my Evita

Hi Timmaa
I believe I am S-OFF - when I look at the bootloader screen it said S-OFF.
Do I need to flash anything at all to get my CID back to original?
On that note I was looking at the RedPoint73 resource guide page but I am not able to find the tutorial to make the CID back to original.
Any info is greatly appreciated. I have attached the screen shot
Cheers

I did :
fastboot oem writecid 622 but it came back with ....INFOfail: [writecid] invalid CID
I flashed the RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed.exe
was the 622 number incorrect?
cheers

No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita

timmaaa said:
No, 622 isn't a CID. A correct CID consists of eight characters, that's why I put eight x's in my example. What model is your phone? You need find the right CID for your model and change it to that. You need to be more careful, you're attempting things without knowing what you're doing again, you're in serious danger of damaging your phone.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaa
My phone is HTC ONE XLTE
I use CID Getter and it came up with HTC__622, so I entered that into the fastboot command and it changed my CID but when I try to flash the new update downloaded directly through the phone it came up with the messsage below after verifying the phone.
not sure why.....( pls see attached)

So you ran the RUU.exe? You didn't extract it or anything? What have you done to the phone since then?
Sent from my Evita

Flashed the kernel now computer can't load it

I flashed the kernel on my phone earlier today, now the computer keeps saying it can't find the driver for it. I'm on windows 7 and if I look under device manager I see HTC One X under "Other devices", I've tried different cable, different computer, uninstalling the driver and install the latest, but it still doesn't work. I can't boot the phone up all the way because the kernel isn't for the ROM I have. I can boot into recovery, which is ClockworkMod. I can't mount it, which is probably because the computer doesn't think the drivers are there. Anyone know how to fix this?
Oh, my phone is rooted and S-Offed.
Thanks.

You need to provide details when asking for assistance. Saying "the kernel" doesn't tell us anything, please tell us exactly which kernel you flashed. You also failed to mention which ROM you're on, your bootloader details, the version of CWM you're running, the os installed on your PC, and whether you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita). All very crucial information, without which it's impossible to help you.
Sent from my Evita

The kernel was for the Cyanogenmod 11. The ROM I was running was a somewhat custom version of the original manufacture version, I don't remember which one exactly. I'm running CWM v6.0.4.6. The bootloader is the default I've never changed it. I'll give you what it says thought:
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.14.002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I believe I mentioned I was run Windows 7 x64 and it's AT&T HTC One X (Evita)
Let me know if there's anything else.

So why not just flash the ROM again?
Sent from my Evita
---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------
That will overwrite the bad kernel. Out of interest, if you knew the kernel wasn't compatible (aosp kernel with Sense ROM will never work) why did you flash it?
Sent from my Evita

timmaaa said:
So why not just flash the ROM again?
Sent from my Evita
---------- Post added at 12:01 PM ---------- Previous post was at 12:00 PM ----------
That will overwrite the bad kernel. Out of interest, if you knew the kernel wasn't compatible (aosp kernel with Sense ROM will never work) why did you flash it?
Sent from my Evita
Click to expand...
Click to collapse
I put an AOSP kernel on because I was trying to get Cyanogenmod on it.
The computer recognizes my phone when I'm in the bootloader and it says Fastboot usb, but the One X One Click utility doesn't recognize that my phone is connected. Is there another utility I should use?

You need the ROM on your phone before you can install the kernel. Forget the utility altogether and just use manual fastboot commands when you need to. Why do you need fastboot at the moment anyway? All you need to do is flash a ROM to get your phone booting again.
Sent from my Evita

timmaaa said:
You need the ROM on your phone before you can install the kernel. Forget the utility altogether and just use manual fastboot commands when you need to. Why do you need fastboot at the moment anyway? All you need to do is flash a ROM to get your phone booting again.
Sent from my Evita
Click to expand...
Click to collapse
Ok, this is gonna sound Noob-ish, but obviously the way I'm use to doing it doesn't work, how do I flash another ROM to it?

You're s-off so all you need to do is perform a wipe in recovery, and install the ROM zip (plus gapps zip if it's aosp). I have detailed instructions in my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita

timmaaa said:
You're s-off so all you need to do is perform a wipe in recovery, and install the ROM zip (plus gapps zip if it's aosp). I have detailed instructions in my How-To Guide For Beginners thread, the link is in my signature.
Sent from my Evita
Click to expand...
Click to collapse
How do I get the Zip to it if I can't access the phone like a drive on my computer?

Can't you mount the sd card to the PC in CWM? If not, didn't you make a backup before messing with the phone? If you have a backup you can restore that. You should always keep a backup or a ROM zip on your phone at all times in case of situations like this. Or you can get fastboot working and flash TWRP 2.6 recovery instead of CWM and you'll be able to use the mount menu to mount usb storage, then it'll show up as a removable drive on your PC.
Sent from my Evita