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
Related
The only thing that's happening is I'm getting the htc screen with the development warning
Nothing else
I've tried turning off when I do it restarts
Please help
thanks
Now I've gotten the phone to go into the bootloader screen
but i don't know what to do from there.
I'm not sure if i attempt reflashing the rom using fastboot?
What do you guys suggest?
Even if I can put on a different ROM would be great as well but that I'm not sure of doing either as I can't restart the phone (if i do go back into the HTC dev boot screen)
let me know please thanks
G
Definitely gonna need more info. What rom, what recovery and version, any errors, hboot version, s-on/off?
Sent from my evita
RollTribe said:
Definitely gonna need more info. What rom, what recovery and version, any errors, hboot version, s-on/off?
Sent from my evita
Click to expand...
Click to collapse
Ok the phone was running stock Rom so firstly i was trying to get a custom recovery installed no luck. It wouldn't take it so i tried a file named insecurebootandroot
After flashing this via bootloader and HTC ONE X All in one tools I'm just getting the the HTC screen with the red text below
But I was able to get back into bootloader by holding down vol- then power then releaseing power button and it goes back to the fastboot screen
the phone is saying
TAMPERED
UNLOCKED
Evita PVT Ship S_ON RL
HBoot-1.14.0002
Radio-0.19as. 32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
June 11, 2012, 14:36.28
thanks
G
Alright not sure what that bootandroot file is, but I don't know if that's for this phone even. Anyways, you're already rooted so what have you tried? Did you try asking another rom or wiping data from recovery (NOT BOOTLOADER).
Sent from my evita
RollTribe said:
Alright not sure what that bootandroot file is, but I don't know if that's for this phone even. Anyways, you're already rooted so what have you tried? Did you try asking another rom or wiping data from recovery (NOT BOOTLOADER).
Sent from my evita
Click to expand...
Click to collapse
The phone wasn't rooted I was trying to root it.
I don't mind putting on another rom but no luck I've tried clearing cache and I still get this same screen and I guess the only way to wipe data is from fastboot but then after doing this what would happen?
positiveg said:
The phone wasn't rooted I was trying to root it.
I don't mind putting on another rom but no luck I've tried clearing cache and I still get this same screen and I guess the only way to wipe data is from fastboot but then after doing this what would happen?
Click to expand...
Click to collapse
No, your phone is rooted. It has an unlocked bootloader. The problem with fastboot erase cache is it formats cache the wrong way. Just go into your custom recovery and format cache and you should be good.
Sent from my evita
RollTribe said:
No, your phone is rooted. It has an unlocked bootloader. The problem with fastboot erase cache is it formats cache the wrong way. Just go into your custom recovery and format cache and you should be good.
Sent from my evita
Click to expand...
Click to collapse
Sorry I did get it root but like SU wasn't working and stug
I don't have a custom recovery i even tried putting one one it acts like it goes on and still nothing
positiveg said:
Sorry I did get it root but like SU wasn't working and stug
I don't have a custom recovery i even tried putting one one it acts like it goes on and still nothing
Click to expand...
Click to collapse
Did you try both TWRP and CWM?
Sent from my evita
did you flash the kernel separate since you're still s-on?
Download a ROM onto your pc. Download TWRP 2.6 recovery from here. Put it in your fastboot folder. Use the following fastboot commands:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Go into recovery on phone, mount usb storage, copy a ROM from PC onto phone. Flash ROM from install menu. Reboot to bootloader. Extract boot.img from copy of ROM still on pc and put it in your fastboot folder, flash it using this command:
fastboot flash boot boot.img
fastboot reboot
Enjoy.
PS. Don't post your problems twice in different locations please.
PPS. Do some research so you actually know what you're doing before you attempt to do anything else to your phone. Don't get any information from anywhere except this forum on XDA, other sites do not distinguish very well between our phone and the Endeavoru.
Sent from my Evita
timmaaa said:
Download a ROM onto your pc. Download TWRP 2.6 recovery from here. Put it in your fastboot folder. Use the following fastboot commands:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Go into recovery on phone, mount usb storage, copy a ROM from PC onto phone. Flash ROM from install menu. Reboot to bootloader. Extract boot.img from copy of ROM still on pc and put it in your fastboot folder, flash it using this command:
fastboot flash boot boot.img
fastboot reboot
Enjoy.
PS. Don't post your problems twice in different locations please.
PPS. Do some research so you actually know what you're doing before you attempt to do anything else to your phone. Don't get any information from anywhere except this forum on XDA, other sites do not distinguish very well between our phone and the Endeavoru.
Sent from my Evita
Click to expand...
Click to collapse
Thank you appreciate the help
I relocked the bootloader should i unlock it again or relock it?
and doing it from fastboot how do I unlock it?
Why did you relock the bootloader? That's the opposite of what you want to do. Stop trying random things. You need to unlock it again now, and follow the instructions I posted above.
Sent from my Evita
timmaaa said:
Why did you relock the bootloader? That's the opposite of what you want to do. Stop trying random things. You need to unlock it again now, and follow the instructions I posted above.
Sent from my Evita
Click to expand...
Click to collapse
Cause I got that from another thread.
Will try unlocking it from fastboot but don't know what command to use as I have the unlock_code bin in the fastboot folder already
positiveg said:
Cause I got that from another thread.
Will try unlocking it from fastboot but don't know what command to use as I have the unlock_code bin in the fastboot folder already
Click to expand...
Click to collapse
You'll have to get a new code for each time.
Sent from my evita
RollTribe said:
You'll have to get a new code for each time.
Sent from my evita
Click to expand...
Click to collapse
Thanks I didn't have to I used the unlock that I had before I'm at the stage where I just mounted
Did everything you said to do I'm trying to flash the ROM from teh install menu but it keeps failing.
I am using SD Clean Base from Android Revolution.
Or must I install a stock ROM?
positiveg said:
Did everything you said to do I'm trying to flash the ROM from teh install menu but it keeps failing.
I am using SD Clean Base from Android Revolution.
Or must I install a stock ROM?
Click to expand...
Click to collapse
Android Revolution is not for this phone. Please do not try to flash anything for the Quad Core One X. Stay within THIS SUBSET OF THE FORUM or you will brick. This phone is One XL evita.
Sent from my evita
Like Rolltribe said, please stay within this forum (att one x) or you'll brick your phone.
To clarify, only download ROMs from the following two sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my Evita
timmaaa said:
Like Rolltribe said, please stay within this forum (att one x) or you'll brick your phone.
To clarify, only download ROMs from the following two sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541
http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my Evita
Click to expand...
Click to collapse
thanks all I knew that the phone was a One X didn't know they had variations. or that the variations could lead to bricking
thanks a lot I'll take a look at the links you posted for ROMS then let you know how it goes
Again appreciate it from you and the rest of the guys here
G
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
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
I have a HTC ONE X LTE - Rogers. I was running hboot 1.11 with Viper Custom ROM. I decided it was time to update my rom but I have not done any flashing in a while. I tried installing the newest Revolution HD ROM without any luck and realized it maybe because my hboot was out of date. So I tried to re-lock my bootloader and flash a newer RUU with JB but I feel like this is where I went wrong. I think I flashed the wrong RUU. I can no longer boot into Recovery. Even if I try flashing for it again I still can not boot into it.
Its status is currently UNLOCKED, hboot is 2.14. I don't want to mess this up, what do I do now?
Version-main 3.17.631.2
When I run fastboot and adb commands, fastboot works but it isn't recognized as a device for adb commands.
Windroid HTC One XL Toolkit:
Android Version: Not Found!
Sense Ver: Sense ROM not installed!
SU Version : Not Rooted!
Busybox: No Busybox Found
Carrier: Not found!
Revolution HD isn't for our phone, that's for the Endeavoru (HTC One X), you have the Evita (HTC One XL). You're lucky you didn't brick the phone.
After the RUU does the phone boot up into Android? Have you manually flashed TWRP recovery since you ran the RUU?
Sent from my Evita
timmaaa said:
Revolution HD isn't for our phone, that's for the Endeavoru (HTC One X), you have the Evita (HTC One XL). You're lucky you didn't brick the phone. Also, which RUU did you run?
Sent from my Evita
Click to expand...
Click to collapse
Yeah... I realize the differences now. Even posted asking for help on the wrong board till they redirected me to this one. Hmm I was on this thread
http://forum.xda-developers.com/showthread.php?t=1859714
and Im pretty sure I downloaded this file
http://www.androidruu.com/getdownlo...128.32.34a_release_299850qstr7rxdbfuofl6j.zip
and inside that I extracted the firmware.zip and flashed that onto my then RE-locked phone.
Everything was fine except I was following another thread that stated how and I just typed the commands. The guy said after it said "Okay" in the cmd window it was fine but on my phone the progress bar didn't go all the way and was actually stuck on the last bit for a good while so I thought since he said it was "okay" it was done and I restated my phone. Thats when the problems came.
That's a zip file so it's an OTA, not an RUU, an OTA will not work unless you already have the correct system already installed for it to build on. An RUU is an exe file. Go back to androidruu and download an RUU exe file then connect your phone in fastboot mode and run the exe program. Don't extract it, just run the program.
Sent from my Evita
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
Also, that thread you linked to is in the wrong forum, you don't have that phone. Don't ever go to that forum (or any forum other than this one), stay in this forum that you're posting in now or you're gonna brick your phone.
Sent from my Evita
timmaaa said:
That's a zip file so it's an OTA, not an RUU, an OTA will not work unless you already have the correct system already installed for it to build on. An RUU is an exe file. Go back to androidruu and download an RUU exe file then connect your phone in fastboot mode and run the exe program. Don't extract it, just run the program.
Sent from my Evita
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
Also, that thread you linked to is in the wrong forum, you don't have that phone. Don't ever go to that forum (or any forum other than this one), stay in this forum that you're posting in now or you're gonna brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
Oh ok, cool. Is there a difference between Evita and EvitaRE? Is it ok if the RUU is a lower number(Im assuming a less up to date) firmware than the one I have right now? Then what should I do after? What Custom rom would you recommend? I was thinking a stable CM rom since I really like the look of AOSP. My only problem was I tried it before and my battery only lasted around 6 hours. With Viper I could get around 7-14 depending on usage.
When I run the RUU (1.0.6.2012) it says From :IMG V 3.17.631.2 To: Image V 1.94.631.3. Is this correct?
Evita and EvitaRE are two completely different phones. Only ever use ROMs/kernels/radios/RUUs that are for Evita specifically. You can't run an older RUU if you're s-on, are you s-on or s-off? Asking for a recommended ROM isn't allowed here, to say one is better infers that the others are inferior in some way. This isn't fair on the devs who spend their spare time bringing us great ROMs free of charge. You need to have a look through the ROMs on offer and find one you think you'll like. Also I asked you before if you've tried flashing TWRP recovery with fastboot? You never answered.
Sent from my Evita
---------- Post added at 04:34 PM ---------- Previous post was at 04:32 PM ----------
It looks like you're running an older RUU, are you s-off?
Sent from my Evita
timmaaa said:
Evita and EvitaRE are two completely different phones. Only ever use ROMs/kernels/radios/RUUs that are for Evita specifically. You can't run an older RUU if you're s-on, are you s-on or s-off? Asking for a recommended ROM isn't allowed here, to say one is better infers that the others are inferior in some way. This isn't fair on the devs who spend their spare time bringing us great ROMs free of charge. You need to have a look through the ROMs on offer and find one you think you'll like. Also I asked you before if you've tried flashing TWRP recovery with fastboot? You never answered.
Sent from my Evita
---------- Post added at 04:34 PM ---------- Previous post was at 04:32 PM ----------
It looks like you're running an older RUU, are you s-off?
Sent from my Evita
Click to expand...
Click to collapse
I am S-ON. Sorry about that, didn't realize. Yes I did try flashing TWRP recovery with fastboot but I am not able to acces it and I am not sure if I am flashing it correctly. I just put it into the folder with my fastboot files and cmd fastboot flash recovery recovery.img (I renamed it to recovery.img)
I downloaded RUU 1.0.6.2012 (it was the only exe in the list for my region) and I tried installing it. I get an Error 155:Unknown error. Telling me to get the correct RUU and try again.
Where did you download TWRP? Maybe we should start again to make sure you've got the right version. 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 hopefully you can enter recovery on your phone.
Sent from my Evita
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
Forget about the RUU for the moment, I believe if we can successfully get TWRP on your phone you can flash an Evita ROM and you'll be fine.
Sent from my Evita
timmaaa said:
Where did you download TWRP? Maybe we should start again to make sure you've got the right version. 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 hopefully you can enter recovery on your phone.
Sent from my Evita
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
Forget about the RUU for the moment, I believe if we can successfully get TWRP on your phone you can flash an Evita ROM and you'll be fine.
Sent from my Evita
Click to expand...
Click to collapse
Wonderful, I have successfully booted into recovery!:victory:
Cool. From now on just make sure you stay in our forum. You'll find the main page here:
http://forum.xda-developers.com/one-x-att
Bookmark that page. The two development sections are here:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
As long as you only download ROMs etc from those two development forums you can't really go wrong. Now just find a ROM you like and you can flash it. Remember if it's an aosp ROM you need to flash gapps as well. And don't forget to flash the boot.img afterwards too because you're s-on. If you have any further problems just ask here.
Sent from my Evita
timmaaa said:
Cool. From now on just make sure you stay in our forum. You'll find the main page here:
http://forum.xda-developers.com/one-x-att
Bookmark that page. The two development sections are here:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
As long as you only download ROMs etc from those two development forums you can't really go wrong. Now just find a ROM you like and you can flash it. Remember if it's an aosp ROM you need to flash gapps as well. And don't forget to flash the boot.img afterwards too because you're s-on. If you have any further problems just ask here.
Sent from my Evita
Click to expand...
Click to collapse
Cool, thanks for all the help! I think Im just going to do a quick install of cleanrom, make sure everything is stable and get S-OFF. After that I'll update my RUU to 3.18 and make a backup from there. Thank you again!
Well no I'm stuck again. I am trying to get S-OFF in order to get a clean RUU install so that the kernel isn't messed up like it is right now. Except The only two methods of getting S-OFF required either SuperCID or adb commands. The only way I can find to get SuperCID is through ADB commands so regardless I need to use adb commands. It isn't so bad except that my phone is not recognized when I try to run adb commands. Ive done everything to reinstalling multiple times yet nothing seems to work.
Try installing an Android 4.1 ROM, folks have had some trouble with adb on the Android 4.2.2 Sense 5 ROMs.
Sent from my Evita
timmaaa said:
Try installing an Android 4.1 ROM, folks have had some trouble with adb on the Android 4.2.2 Sense 5 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
Im using CleanROM 6.5 and under software information it says android 4.1.1 and Sense 4+. Should I use an older one?
Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita
timmaaa said:
Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita
Click to expand...
Click to collapse
I'm pretty sure I have but just in case what should I exactly to update it? I am running windows 7-x64. No, the one that came with my phone is starting to not work so I am using one from a differ phone. On my laptop, on the left side. The side with more USB ports.
timmaaa said:
Ah ok, I thought you were using the latest version of CR which is an Android 4.2.2 ROM. So you've updated both your HTC drivers and adb/fastboot? What version of Windows are you using? Are you using the HTC usb cable that came with the phone? Are you using a front or rear usb port?
Sent from my Evita
Click to expand...
Click to collapse
Tested on my Desktop running Windows 7-x64 as well and all the drivers are fine except for the MTP drivers. They don't install correctly. Thats the problem with my laptop as well.
Is there anyway I can do a clean wipe or start over from scratch?
An RUU will start you over from scratch, the only problem is that you're s-on so you can run an older RUU and there isn't an RUU that's equal to or greater than your current firmware. Are you able to mount your sd card in TWRP?
Sent from my Evita
timmaaa said:
An RUU will start you over from scratch, the only problem is that you're s-on so you can run an older RUU and there isn't an RUU that's equal to or greater than your current firmware. Are you able to mount your sd card in TWRP?
Sent from my Evita
Click to expand...
Click to collapse
Yes I am
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