Hello everyone! So here's the deal..
I recently bought an unlocked HTC One XL, which came installed with TWRP and AOKP. I noticed that the device performance was really slow and decided to erase some things. Problem is I deleted the ROM + Recovery. I have tried multiple times to install both recovery and image files. I know how to transfer files using fastboot, but there are a couple of problems:
1.) When I type in "adb devices" it doesn't say 'device not recognized' but instead it shows the apparent list of devices - which my XL is not in. This elevates the problem because I cannot just push files through adb, instead I am stuck on sending files through fastboot every single time.
2.) I have sent recovery.img's and my phone is stuck in "bootloop" - it just turns off and on in the same screen. When I try to access recovery from bootloader, this exact same problem of repetition happens. I can't change the state of the S-On.
3.) I'm still fairly new when it comes to ROM installation, but I wouldn't consider myself a complete retard either when it comes to this.
___________________________________________
Phone State:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.19as.32.09.11+2
OpenDSP-c28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
I don't think I bricked my device, though I might of have softbricked it. I know I messed up by deleting TWRP + AOKP, but I knew that it was (should've been) just as easy as flashing the files back into the phone. If anyone can help me by possibly providing ROMs and recovery files that actually work on boot it would be greatly appreciated.
** Update
I managed to install TWRP = Progress
I would suggest flashing sense 5 stock rom first ..That would get ur adb working n then go for s-off before proceeding further
It worked for me earlier
Sent from my HTC One XL using xda premium
Firstly, you can't just delete the recovery, it doesn't work like that. Anyway, looks like you got TWRP installed again do all you need to do now is install a ROM and away you go. Once you have a ROM installed you can use the phone as normal, but it's pretty strongly suggested you get s-off.
Sent from my Evita
timmaaa said:
Firstly, you can't just delete the recovery, it doesn't work like that. Anyway, looks like you got TWRP installed again do all you need to do now is install a ROM and away you go. Once you have a ROM installed you can use the phone as normal, but it's pretty strongly suggested you get s-off.
Sent from my Evita
Click to expand...
Click to collapse
The problem is I'm having a bit of trouble finding a ROM and getting S-OFF. I have looked up countless guides and I'm either doing something wrong when I follow guidelines, or they just aren't working.
Using firewater method I get an error the file "not being in directory" when it is in the exact same ADB folder.
Also another thing, if I just get a ROM that support HBOOT 1.09, can I install it with S-ON?
You should be able to install any Sense ROM with your current hboot. Aosp ROMs will require a firmware upgrade though which requires s-off. Trust me, you're gonna want s-off in the long run.
Exactly which ROMs have you tried? What errors are you getting upon installation?
Please note: while Sense ROMs will install, they will not run properly without a firmware upgrade (which requires s-off).
Sent from my Evita
timmaaa said:
You should be able to install any Sense ROM with your current hboot. Aosp ROMs will require a firmware upgrade though which requires s-off. Trust me, you're gonna want s-off in the long run.
Exactly which ROMs have you tried? What errors are you getting upon installation?
Please note: while Sense ROMs will install, they will not run properly without a firmware upgrade (which requires s-off).
Sent from my Evita
Click to expand...
Click to collapse
I tried installing the most recent CyanogenMods and ended up stopping because of HBOOT. I then tried installing AOKP most recent ROMs for my device - from their website.
I'm currently installing Sense 5, I'm following all the rules that HTC Support says.
Don't worry about HTC support, their rules don't really apply to modified phones. Just read my Evita FAQ thread and my How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
timmaaa said:
Don't worry about HTC support, their rules don't really apply to modified phones. Just read my Evita FAQ thread and my How-To Guide For Beginners thread, both links are in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Gotcha man, thanks a bunch! I stumbled onto a problem though, How do I enable USB Debugging through TWRP? Using Rumrunenr it says i have to enable it. It says "Debugging On? Latest Drivers?" So yeah.
Friezan said:
Gotcha man, thanks a bunch! I stumbled onto a problem though, How do I enable USB Debugging through TWRP? Using Rumrunenr it says i have to enable it. It says "Debugging On? Latest Drivers?" So yeah.
Click to expand...
Click to collapse
You can't, you can only enable that when booted into Android. So first you need to install a ROM, then you can get s-off. So you're gonna need to install a Sense ROM purely to get s-off, then you can upgrade your firmware and flash whatever you like.
timmaaa said:
You can't, you can only enable that when booted into Android. So first you need to install a ROM, then you can get s-off. So you're gonna need to install a Sense ROM purely to get s-off, then you can upgrade your firmware and flash whatever you like.
Click to expand...
Click to collapse
It says I need the correct rom is there not a HTC One XL from AT&T Sense 5 rom?
Friezan said:
It says I need the correct rom is there not a HTC One XL from AT&T Sense 5 rom?
Click to expand...
Click to collapse
Rumrunner says that? Don't use Rumrunner, try the Facepalm method instead, it's much less temperamental.
Facepalm S-off
timmaaa said:
Rumrunner says that? Don't use Rumrunner, try the Facepalm method instead, it's much less temperamental.
Facepalm S-off
Click to expand...
Click to collapse
Alright this is really frustrating now. I'm getting this error when I'm trying to flash Sturge's Stock Sense 5 ROM. If it's a USB Debugging Problem then how am I supposed to flash it into the SDcard? Should I try pushing it through adb?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That isn't how you flash a ROM. Did you not read the threads in my signature like I suggested?
Sent from my Evita
timmaaa said:
That isn't how you flash a ROM. Did you not read the threads in my signature like I suggested?
Sent from my Evita
Click to expand...
Click to collapse
What I did is just copy and pasted the zip into the Sd card and just installed it from recovery. I've got most of it working timaaa, I get fine signal over WiFi but I'm not getting 3g. Any idea? I've got the Apn settings fine
If you're not getting any data signal, I'd revisit your APN settings, triple check them, they're usually the culprit.
Sent from my Evita
Related
hi guys unfortunately i need to send my phone in warranty (sniff)
previously i'm rooting my ds with revolutionary
and now i follow this
i flashed eng boot and next i use android flasher flashing the hboot in the root of the folder..
anyway i'm now with:
***security warning***
saga pvt ship s-on rl
hboot-0.98.0002
radio-3831.19.00.110
emmc-boot
bla bla bla...
i'm tryng to use the ruu to revert the rom back to stock
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
but it says "unable to update"
now i think i have the h boot 98.0002 and the ruu have 98.0000
so it didn't work but i can't find the ruu thread on xda (i remember there it was some time ago)
any help?
Is it that link you are looking for ? : HTC Saga Shipped Roms
kiss!!!! xD
i have an error....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Husky34 said:
i have an error....
but before i have:
someone have a solution?
i think i have a newer version of the misc version am i right?but what i can do to downgrade it?
i'v try
adb push misc_version /data/local/tmp
but it'says error device not found
Click to expand...
Click to collapse
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
NVardan said:
Do you have goldcard? The same problem I also had. After making a goldcard, I've installed the official RUU successful.
Sent from my HTC Desire XS using Tapatalk 2
Click to expand...
Click to collapse
mmm no...what is it? (i think i'v heard it...is something inside the sd right?)
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
hipp0po said:
[GUIDE] Create a GOLDCARD for your HTC DESIRE S
Click to expand...
Click to collapse
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Husky34 said:
yep but in this condition my phone doesen't boot..only reboot in bootloader...
Click to expand...
Click to collapse
run the ruu in fastboot?
Sent from my supercharged :tank:
hisname said:
run the ruu in fastboot?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
yep is it correct? it works for a while and then bam error 140..
Husky34 said:
yep is it correct? it works for a while and then bam error 140..
Click to expand...
Click to collapse
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
hisname said:
well there is still hopes...
try misc. version? or maybe CID doesn't match?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
i'll put the screen in the first page of this thread...and i even try to change misc version without success..
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
amidabuddha said:
Ok you have made a very common mistake (that I have made once too, but then there was no ICS RUU, so I was forced to do some mumbo-jumbo) - not lowering your version, which is a must-have in the downgrade process
Anyway you have now much easier path now:
1) Run the ICS RUU
2) unlock the bootloader via htc-dev
3) flash a custom recovery
4) root it manually or with the AIO tool (temp root will not work)
5) lower your main version using the misc_version binary
6) relock the bootloader
7) run the RUU
8) disable the update check in the Settings, otherwise if upgraded the SC will spot the relocked bootloader
Good luck
Click to expand...
Click to collapse
but i want to send into warranty man...i can't unlock bootloader via htc dev
Husky34 said:
but i want to send into warranty man...i can't unlock bootloader via htc dev
Click to expand...
Click to collapse
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
Click to expand...
Click to collapse
can i fire my mmc in some way?if my phone doesen't boot i think they can change my motherboard...:'(
i know is a hard decision....but i think is the only one...
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Husky34 said:
OR
i can flash ics ruu and send it into warranty!!!!but when it comes back i can't root it....no?
Click to expand...
Click to collapse
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
amidabuddha said:
Well as far as I remember the ICS RUU disclaimer says that it drops the warranty on the software side. If you have a hardware problem it should be acknowledged and repaired. But you have to recheck that.
Click to expand...
Click to collapse
of course i check
thanks for the info and have a good day all!
amidabuddha said:
I am afraid you are out of options. There is no way to lower your version without root.
If you are lucky and still have the custom recovery you can use the misc_version there (it has root). Otherwise you cannot flash anything with this version, only the ICS RUU. You cannot use Revolutionary again when your OS does not boot
EDIT: as I said I have made the same mistake and now my hardware buttons are almost broken and I cannot take it to a repair due to my Unlocked bootloader. But when you downgrade to 1.28.x or 1.47.x there is no "RELOCKED" flag shown in the booltoader screen. So if you keep the older version and do not update there is a chance that the SC will not check it.
Click to expand...
Click to collapse
What are you talking about? He can just use tacoroot. Either way, he was S-OFF, so he can just S-OFF again, change miscversion, and then roll back to S-ON.
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
The official Build
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for the AT&T HTC One XL.
Click link here>> Link to Development Thread <<Click link here
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
mikelebz said:
For the new kernel is it possible to flash the newest HBoot from this thread just to make life easier? http://forum.xda-developers.com/showthread.php?t=2156368
Would that be the 2.14 HBoot?
thanks again!
BTW I know I already posted this in the AOKP thread...Just wanted clarification from both devs.
Click to expand...
Click to collapse
afaik, you MUST flash the RUU in its entirety. I believe h8 did something like just flash parts of the RUU and that bricked his phone. As long as your s-offed, no reason why you wouldn't want to RUU to 3.18.
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Torch not working
Anyone else getting FC's when trying to use the torch?
Misterowl said:
I don't know if this is the correct place to ask this but I tried to RUU but I keep getting an error.
Click to expand...
Click to collapse
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Is s2w available on this kernel? My power button has been sticky so I've to move to the sense5 rom which I like. But definitely not as much as i love CM10.1
exad said:
What Error?
SuperCID? Yes or no?
S-ON or S-OFF?
Click to expand...
Click to collapse
Error 170
S-OFF
CID 11111111
ClassicalGas said:
Anyone else getting FC's when trying to use the torch?
Click to expand...
Click to collapse
Yeah, I'm pretty sure camera flash is broken too.
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
boot to bootloader/fastboot, ruu
So Girlfriend is finally getting tired of her Sense and is open to the idea of me rooting. Besides the camcorder resolution, hdmi, are there any bugs that would keep this from being a good dd. Thanks for the help guys
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
JayDream said:
Hey whats up everybody I have a couple questions, Is it absolutely necessary to upgrade to 3.18 RUU for this ROM? The only reason I'm hesitating to ditch 1.09, is because I'm a bonafide flashaholic, and I'm not looking forward to fastboot flashing the boot image again, every time I want to try a new rom! (been there done that and it is totally NOT the business ) Which brings me to my second question, Does updating to 3.18 require you to fastboot flash the boot image before flashing new rom's? Evita/hboot 1.09/S-Off
Click to expand...
Click to collapse
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
ClassicalGas said:
Nah, with S-Off you don't need to fastboot flash anything.
Yesterday I was S-On, 1.09, now I'm S-Off 2.14 hboot (after using the 3.18 RUU). I've never had to fastboot flash the boot.img on this phone.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
JayDream said:
OK thanks! Now can I fastboot flash the hboot using this method http://forum.xda-developers.com/showthread.php?t=2156686 or do I have to actually run the ruu?
Click to expand...
Click to collapse
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
So I RUU'd and downgraded the touch panel firmware and tried to flash a new recovery but my bootloader is locked.
I tried unlocking the bootloader in HTCdev and I keep getting this in my terminal.
ERROR: could not get pipe properties
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.013s]
finished. total time: 0.013s
ClassicalGas said:
I RUU'd as per H8's recommendations, so can't confirm if that method works or not.
Sent from my One X using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Misterowl said:
Error 170
S-OFF
CID 11111111
Click to expand...
Click to collapse
I kept getting an error that "Android phone is not connected"
Then i booted the phone into bootloader mode and tried it
That seemed to get it to work.
Still in the procees of downgrading and getting back to CM10.1
Just wanted to let you know
JayDream said:
Thanks man I appreciate it. But I think I'm gonna have to sit back on this one tho :/ at least until I have a better idea of what I'm getting into...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah I was a bit worried but was patient and followed all instruction instructions below (from the CarbonRom thread).
InflatedTitan said:
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp.
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I used the RUU from here
I used a windows computer instead of a Mac to unlock and it worked. So yeah Mac bad.
Sent from my One X using xda app-developers app
Hi. Ok here is the story.
I was trying to install Cyanogenmod to my HTC One X ATT&T. When i was erasing the data (factory reset, dalvik cache, etc...), i forgot to make a back up. Now the cyanogen installation failed and left me with a phone without OS. I've trying EVERYTHING i could find. I tried flashing it again (Of course if you guys were wondering, I followed the instructions for that, used the boot.img first on my pc and all that.). Trying to reinstall it didn't work. Then i tried to go back to the stock ROM, and this happend. It won't let me install any ROM i tried. (Cyanogen, Stock ROM, user-made ROMS). It always says that fails, I tried unrooting and locking the bootloader again using a guide. When i was following the instructions, the cellphone didn't let me lock the bootloader back therefore i couldn't install the stock ROM. I'm kinda out of ideas or options. So i'm asking for help. I'm gonna write below the information of my phone so you guys can have a reference. This is the information that my bootloader displays. The only thing i haven't done is wiping the internal storage (A.K.A /SDCARD). <-- Now that i wrote that i think that may be the problem.
***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
HBOOT
(here goes the navigating instructions.)
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
POWER DOWN
Note: The recovery i have installed is the custom one TWRP 2.4.1.0
couldn't flash using recovery either. It always give me the failed message. To be more specific it gives me this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please any help is appreciated.
I'm going to be tracking this thread, I enable the email notification option. So if anyone see this thread and is able to help me. Please don't hesitate.
Link what you were trying to flash. Plug your phone into a windows computer. Does it ask you to format the card?
Sent from my VENOMized HoxL
area51avenger said:
Link what you were trying to flash. Plug your phone into a windows computer. Does it ask you to format the card?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I won't and i can't post link since i'm a junior poster
I was trying to flash Cyanogenmod version 10.1.2 the latest one for the HTC One X
First solution that comes to mind: Update recovery to 2.6.0
In addition I recommend not jumping to conclusions such as relocking your bootloader etc. Research dude. For one thing, almost everyone in these threads is on TWRP 2.6+
Also I believe that more recent AOSP ROMs (not positive about Cyanogen 10.1.2) will require you to run the 3.18 RUU which requires S-off or you will brick your device. These are the sort of dangers associated with jumping to conclusions. After performing sufficient research around our forum and you feel confident in your ability, join us on the cutting edge
Sent from my One X using XDA Premium 4 mobile app
CM10.1 failed because hboot 2.14 is required. Can't tell you why the other ROMs failed, since you only vaguely described them instead of telling us exactly what you did.
You need to be as specific and detailed as possible if you want us to help properly.
Sent from my HTC One XL using xda app-developers app
IYour problem is the version of TWRP recovery you're using, it's full of bugs. 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 and the ROM should flash ok.
[EDIT] You need to update your firmware first.
Sent from my Evita
Still active. Please don't hesitate
Posting every few minutes that the thread is active isn't helping get answers any faster. Please be patient, we all have lives outside of XDA, you wouldn't be in this predicament if you had researched properly and knew what you were doing.
As I pointed out you're using the wrong recovery version, and as Redpoint pointed out you have the incorrect firmware version to flash the ROM you're trying to flash (that information is stated very clearly in the ROM thread).
Sent from my Evita
timmaaa said:
Posting every few minutes that the thread is active isn't helping get answers any faster. Please be patient, we all have lives outside of XDA, you wouldn't be in this predicament if you had researched properly and knew what you were doing.
As I pointed out you're using the wrong recovery version, and as Redpoint pointed out you have the incorrect firmware version to flash the ROM you're trying to flash (that information is stated very clearly in the ROM thread).
Sent from my Evita
Click to expand...
Click to collapse
I apologize for seen needy, that wasen't what i intended by posting those reply. it was just to let know that if theres anyone with time that could help me. And yeah i forgot to state that i don't have too much experince with this.
I'm not looking for fast answers, just an answer, if there's one.
About the recovery version. i tried to change it to CWM but it didn't let me. After that i started looking for other option and i read in another page that you could use TWPR for cyanogen aswel.
redpoint73 said:
CM10.1 failed because hboot 2.14 is required. Can't tell you why the other ROMs failed, since you only vaguely described them instead of telling us exactly what you did.
You need to be as specific and detailed as possible if you want us to help properly.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
When i tried other ROMS ( Clean ROM from theunlockr, Stock ROM from the HTC official updater Htc one x RUU 2.20,)
I also used One x ATT all in one kit v2.1.1 to root and installed the recovery, before all this, and after to try to reinstall CWM and cyanogen
Didn't mean to be captain obvious but come on man!
Sent from my HTC One XL
First you need to follow my instructions and install TWRP 2.6. Once you've done that you need to install a Sense ROM (Android 4.1 / Sense 4+, NOT Sense 5), this is only temporary and is purely so you can get s-off. You need s-off so you can run the 3.18 RUU which will update your firmware to the firmware required to run CM. If you run the RUU while s-on you'll brick your phone so having s-off first is very important.
So, once you have TWRP 2.6 and a Sense ROM installed you can go to the Facepalm s-off thread and get s-off. It's pretty simple if you follow the instructions. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
timmaaa said:
First you need to follow my instructions and install TWRP 2.6. Once you've done that you need to install a Sense ROM (Android 4.1 / Sense 4+, NOT Sense 5), this is only temporary and is purely so you can get s-off. You need s-off so you can run the 3.18 RUU which will update your firmware to the firmware required to run CM. If you run the RUU while s-on you'll brick your phone so having s-off first is very important.
So, once you have TWRP 2.6 and a Sense ROM installed you can go to the Facepalm s-off thread and get s-off. It's pretty simple if you follow the instructions. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my Evita
Click to expand...
Click to collapse
I'm gonna follow this and i will post the results. Thanks for everyone that replied.
By the picture I think he is trying to flash an endeavoru rom.
Yeah you're absolutely right.
@OriginalLazy, the screenshot you have posted shows that the ROM you tried to install is not for our phone. You got lucky and the installer stopped it, if it had succeeded it would have bricked your phone. That ROM is for the HTC One X (codename Endeavoru), you have the HTC One XL / at&t One X (codename Evita). I'm not sure where you downloaded that ROM from but it was the wrong place, in future make sure you only download ROMs from links within this forum you've posted in. Anything with Evita in the filename is ok, a filename with anything other than Evita is bad news.
Sent from my Evita
falcon66 said:
By the picture I think he is trying to flash an endeavoru rom.
Click to expand...
Click to collapse
Good catch. I tried to look at the photo last night, but it was much too small to be legible when viewing on my phone.
The CM zip the OP is trying to install is not for the right version of the One X. Its for the quad coare Tegra3 ENDEAVORU, which is a completely different device internally.
That's where I was going with my first post. He's following guides for the one x and getting lucky that he's not bricked yet
Sent from my VENOMized HoxL
OriginalLazy said:
About the recovery version. i tried to change it to CWM but it didn't let me.
Click to expand...
Click to collapse
You may have been trying to install CWM for the ENDEAVORU, instead of your phone, which is EVITA.
Check out my Index thread, and only install mods listed there to avoid this confusion: http://forum.xda-developers.com/showthread.php?t=1671237
UPDATE: What's going on.
Ok i followed @timmaaa instruction and installed the recovery whidout any problems, now i'm having some "trust" issues with the ROM i been looking for in order to fully fix my phone. In other words, i don't trust myself to select a proper ROM for my phone. I've been looking to some ROM here in the forums but when i look at their threads (note: I used in the searchbar the code words "EVITA","SENSE 4") they won't say which phone is supported or anything like that. I assume since i'm new to this that people just know for which phone is the ROM by just looking, but i'm like i said, having trust issues.
Now this are the ROM i looked at since i wasn't able to find a stock one that wouldn't make me think twice.
HatkaXL-evita-v4.7.1.
[ROM][4.2.2][RC2.1 STABLE] Official LiquidSmooth ROM - evita - 3|17|13
Now i know a lot of you will think like i'm sounding like an idiot but well, better safe than sorry right?
Hello, my HTC ONE S is soft bricked, its stuck now at boot loop. I have done many many tutorials, many custom tools tryed, no luck. I don't know what else to do.. The only hope is you guys, could please someone would supervise me on step by step instructions on what to do?
I would try to respond in details as fast as i can about the situation and wait for later instructions.
STATUS:
S4 class device
CID O2___001
TAMPERED
UNLOCKED
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.12.50.05.05
OpenDSP-v31.1.0.45.0815
eMMC-boot
TWRP v2.6.3.0
Last installed rom: cm-10-2.0.-ville.zip When device boots in to a rom, after HTC logo boot-loop appears, and all over again.
Booting in to HBOOT Works, booting in to a Recovery also works.
SDK platform-tools installed, USB ADB drivers installed.
FASTBOOT commands works,
ADB commands - does not, adb device not found because rom wont boot.
Adb sideload works.
what i should do?
Did you flash kernel when installing the rom?
Sent from my HTC One S
ka_55 said:
Did you flash kernel when installing the room?
Sent from my HTC One S
Click to expand...
Click to collapse
as far as i remember - yes, but cm 10 did not provide separate boot.img or instructions about it.
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
ka_55 said:
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
This should fix your problem, good luck!
Sent from my One S
ka_55 said:
You have to flash it separately since you are s-on. There should be a boot.img in the rom's zip, extract it and flash via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
OMG, it just booted in to a CyanogenMOD!! but how lol , i mean, i could swear i had done this before and no luck. lol but i did it now anyway exact what u said anyways, and it works!! lol this phone was unused for a month and a half just because i tough i did everything lol thank you!
gab1one said:
This should fix your problem, good luck!
Sent from my One S
Click to expand...
Click to collapse
thanx, it should did! :victory:
Good to know I could help.
By the way you said that you installed cm-10, and strongly recommend you to try cm-11. I think it's far more stable right now.
Anyway have fun
Sent from my HTC One S
ka_55 said:
Good to know I could help.
By the way you said that you installed cm-10, and strongly recommend you to try cm-11. I think it's far more stable right now.
Anyway have fun
Sent from my HTC One S
Click to expand...
Click to collapse
oh yes yes, i only used cm10 as a base rom, something clean to wake this phone up now what i will do is supercid, s-off and then go for something like maximus hd
It can be tough to supercid for you. Hboot 2.15 is a little problematic cause it has write protection. I hope you can do it. You shouldn't forget to enable root access to adb from developer options or you won't be able to use adb.
S-OFF
Saiyaru said:
oh yes yes, i only used cm10 as a base rom, something clean to wake this phone up now what i will do is supercid, s-off and then go for something like maximus hd
Click to expand...
Click to collapse
If you use rummrunner.us to S-OFF you wont need supercid.
I used it and it worked fine. You might need to experiment with the ROM.
Some aren't compatible, but you will only use it for the S-OFF.
Hope this helps you :good:
ka_55 said:
It can be tough to supercid for you. Hboot 2.15 is a little problematic cause it has write protection. I hope you can do it. You shouldn't forget to enable root access to adb from developer options or you won't be able to use adb.
Click to expand...
Click to collapse
Lol i did it! its now SUPERCID and S-OFF with Hboot 2.15
it was not easy... i did first supercid with hex editing trick, was hard to pull the special file, but i did some actions with manual pulling by recovery and build in file manager, but i managed to change and push back in with adb shell su.
the s-off part was the hardest. i tryed first rumrunner 0.5.0, dint worked, then moonshine 3.16 - dint worked, got error pretty quick, then i did soffbin3 method - no luck, but it might did some shanges in system anyways. Then, i did revone method by chmoding and sending revone commands with adb shell su. it did something but failed, but i told myself - hey, its still s-on, but maybe now i did some changes to the system anyways and now rumrunner will do is job more easily, well, here is what happened: i actually laughed my ass off reading this lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it took long time, BUT IT DID THE JOB! XD
finally i can install pretty much anything i want :victory:
oh by the way: a little tip: if anybody would get trouble to install HTC ADB drivers with error (as windows cant find the patch specified), i installed samsung drivers instead by force (from galaxy s3 adb) cause i dint find any solution to solve htc driver issue.., but samsung adb drivers works perfectly with HTC!
Just got an unlocked HTC One X to replace my old T989 and I have not been into switching ROMS since the days of the HD2 Leo. I tried to update to Kit Kat and sense 5.0 through ATTs OTA update. Now the phone will not boot up and only gets so far as the HTC screen.
All I want to do is just revert back to stock for now. Should I just reinstall the stock or is there more to this.
Boot loader works and the phone does indicate that it is charging. Any help would be awesome.
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Sent from my Evita
g29er123 said:
Just got an unlocked HTC One X to replace my old T989 and I have not been into switching ROMS since the days of the HD2 Leo. I tried to update to Kit Kat and sense 5.0 through ATTs OTA update. Now the phone will not boot up and only gets so far as the HTC screen.
All I want to do is just revert back to stock for now. Should I just reinstall the stock or is there more to this.
Boot loader works and the phone does indicate that it is charging. Any help would be awesome.
Click to expand...
Click to collapse
Need bootloader details. Post what is in the first 5 lines of bootloader.
Also, the latest AT&T OTA updates to 4.2.2, not KitKat (although it is Sense 5).
---------- Post added at 02:29 PM ---------- Previous post was at 01:36 PM ----------
timmaaa said:
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Click to expand...
Click to collapse
Beat me to it by 2 minutes . . .
redpoint73 said:
Beat me to it by 2 minutes . . .
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^^^
Sent from my Evita
timmaaa said:
There is no official KitKat update for this phone, Android 4.2.2 is the latest official update available. Anyway, more information required. Please post your bootloader details, and did you use the build in updater in settings or did you apply the update manually?
Sent from my Evita
Click to expand...
Click to collapse
Oops you are right..it is 4.2.2 I updated the phone through settings...software update. It will only one note of the start up jingle and the top quarter of the screen flashes white on occasion.
Boot loader:
EVITA PVT SHIP S -ON RL
HBOOT-2.18.0000
Radio-0.19as.32.09.11.2
openDSP-v29.1.0.45.0622
eMMC-boot
It looks like the OTA has somehow only done half the job. Before I advise you any further I need to know what it says above the bootloader info you gave, it'll be locked, relocked, or unlocked. I'm also going to need you to check your CID using fastboot. If you don't have adb and fastboot installed you'll need to do that, there are plenty of guides available on XDA.
Sent from my Evita
timmaaa said:
It looks like the OTA has somehow only done half the job. Before I advise you any further I need to know what it says above the bootloader info you gave, it'll be locked, relocked, or unlocked. I'm also going to need you to check your CID using fastboot. If you don't have adb and fastboot installed you'll need to do that, there are plenty of guides available on XDA.
Sent from my Evita
Click to expand...
Click to collapse
Locked
CID: CWS_001
Ok. What method did you use to get your CID? Fastboot?
Sent from my Evita
timmaaa said:
Ok. What method did you use to get your CID? Fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Downloaded Minimal ADB and Fasboot.
Went into fastboot and typed: fastboot getvar cid
Cool, that's what I wanted to hear. I think your best option is probably to run the official 5.18 RUU, which you'll find here:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
Sent from my Evita
timmaaa said:
Cool, that's what I wanted to hear. I think your best option is probably to run the official 5.18 RUU, which you'll find here:
Sent from my Evita
Click to expand...
Click to collapse
For some reason my device is not recognized by my computer unless I am in boot loader options.
The phone needs to be in bootloader mode to run an RUU anyway, but it's probably a good idea to fix your problem first. What OS are you running on your PC?
Sent from my Evita
timmaaa said:
The phone needs to be in bootloader mode to run an RUU anyway, but it's probably a good idea to fix your problem first. What OS are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
Windows 7. Running the RUU now from bootloader for the last 15 minutes and the install wizard is still updating rom image and only HTC logo showing on the phone.
Did you confirm a proper connection before starting the RUU?
Sent from my Evita
timmaaa said:
Did you confirm a proper connection before starting the RUU?
Sent from my Evita
Click to expand...
Click to collapse
Yes. according to HTC sync manager.
Ok, but did you confirm your drivers are ok by testing adb and fastboot?
Also, you need to uninstall HTC Sync Manager (but leave the drivers installed), it interferes with the RUU process.
Sent from my Evita
timmaaa said:
Ok, but did you confirm your drivers are ok by testing adb and fastboot?
Also, you need to uninstall HTC Sync Manager (but leave the drivers installed), it interferes with the RUU process.
Sent from my Evita
Click to expand...
Click to collapse
No I didnt do that. How do I test the drivers in adb and fastboot and how do I leave only the drivers for HTC sync manager. Do I put them in a folder or something? And yeah the the install never got past installing ROM image. Now the phone just has the backlight on.
You choose to uninstall Sync Manager, but don't choose HTC drivers (they're separate). Test your connection by using the "adb devices" command while booted into Android, and "fastboot devices" while connected in fastboot usb mode.
Sent from my Evita
timmaaa said:
You choose to uninstall Sync Manager, but don't choose HTC drivers (they're separate). Test your connection by using the "adb devices" command while booted into Android, and "fastboot devices" while connected in fastboot usb mode.
Sent from my Evita
Click to expand...
Click to collapse
Uninstalled HTC Sync but I had no option to keep drivers. In my program mananger there is a file that says that says HTC driver installer. I did check the connection in android boot.
I got:
daemon started sucessfully
List of devices attached
When I check in fastboot it says
ht2b3w303351 fastboot
I am assuming maybe I am missing the drivers?
I also want to thank you for helping me thus far, I have learned alot and hopefully I can get it working.
How about when you use the adb command? In the start menu under the HTC section it should have HTC Sync Manager and HTC drivers as separate options, in any case it looks like they're still there if your commands are working.
Sent from my Evita