Database Info

Flashed wrong boot.img, going through bootloop

I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn

shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
Just flash the correct one like you flashed the wrong one. The boot loader does not and should not be relocked, it should be unlocked.

shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
is all you flashed, the boot.img or did you flash leedroid too? If you flashed leedroid then do the following:
plug it in to USB while it bootloops type adb reboot recovery
from there you can access your nandroid backup assuming you made one.
if you didn't make a backup then yeah you'll have to flash the 1.85 RUU. To do this, relock the bootloader from adb fastboot oem lock
run the RUU unlock the bootloader then install your recovery and push root files via recovery.
Much easier than having to re-root 1.85 with the new exploit etc.

If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.

mbh87 said:
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
Click to expand...
Click to collapse
I keep forgetting we have adb through recovery now. Good call. But do we have USB?

Latest TWRP is suppose to have both ADB and USB

You should always back up
Sent from my HTC One XL using Tapatalk 2

kkoshko1 said:
You should always back up
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Amen.
nandroid is always my first step when flashing a ROM

I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.

mbh87 said:
Latest TWRP is suppose to have both ADB and USB
Click to expand...
Click to collapse
I didn't see any need in backing up because I assumed all would go well and also I don't have any data on here that I want. Lesson learned well though. I will always back up. Now I've gotta get it working...

shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2

shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.

kkoshko1 said:
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thats actually why I re-locked. I've read that before installing an ruu, you need to re-lock.
I can get to fastboot. I tried to unlock via fastboot but it quickly timesout. I'm currently downloading 1.85 .exe ruu. I will give that a try as soon as its done downloading unless you guys have a better idea.

rohan32 said:
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
Click to expand...
Click to collapse
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?

shgadwa said:
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin

gunnyman said:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!

shgadwa said:
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
Click to expand...
Click to collapse
Link is correct. Pay attention to the subforum. It specifically says AT&T One X, if that is the section you are in.

Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.

smokin1337 said:
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
Click to expand...
Click to collapse
Thank you. I do know how to get into hboot. I flashed boot.img and it is now working!

NVM saw your edit lol...

Major problems after trying to flash JB on HTC ONE X

Hello, I just tried to install the new JB insertcoin version on my HTC One X. Something went wrong and now I am completely stuck. After having searched the internet for a few hours to avoid asking the same question two times, I decided to finally ask for help here as my case seems to be unique.
I'm currently only have access to hboot and fastboot, when I try rebooting the phone I end up in an endless bootloop just as I reach the home screen.
- I can't flash any .img files whatsoever,
- I can't access "recovery" and I promptly receive a text "security warning" just under "RELOCKED".
- when I try entering hboot mode it says "Failed to open USB Master Mode".
- I have tried flashing RUU but it says I have <30% battery, which is not true as it's nearly full.
I have no idea what I should do from here, is my phone dead or is there still hope? Thanks in advance, I really appreciate any input I can get.
Update. I realize I need to download "recovery.img" and proceed with installing a stock rom. However, when I try flashing the recovery.img it says "FAILED" in cmd.
Update2. Dowloaded the stock rom but received error 140 midway through the installation. Probably has something to do with the "FAILED" I get when using the command "fastboot flash recovery recovery.img". Any help is appreciated, my batteries are probably at 50% now....

You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium

stnguyen09 said:
You say it says "relocked" in hboot? That means your bootloader isn't unlocked. You're gonna have to do that before you can do anything else.
Edit: also, are you sure insertcoin is for our one X and not the international (tegra 3) version? I quick skimmed through both our development sections and didn't see it.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have the EU version, my thread was moved here dunno why. Anyway, I unlocked bootloader and it now works to use the command "fastboot flash recovery recovery.img" and when I run the corresponding RUU I receive error 155 instead of error 140. I am now stuck in an endless bootloop where the phone restarts as soon as the home screen is reached.
Edit: Is there any way I can revert the 1.28 firmware for JB? It says HBOOT-1.28.0000 in the bootloader and maybe this is what's causing problem.

I remember one having to put the new hboot on there before they flashed it. Correct if I'm wrong

Update: I installed an older (ICS) version of insert coin and it worked. I won't touch jelly bean for a while....

This thread should probably get moved to the HTC One X forum though. I would give advice but don't know anything about the HTC Endeavor.

For them to run a jelly bean sense ROM they need to flash a updated hboot.
Hopefully that won't happen to us....
Sent from my Nexus 7 using Tapatalk 2

so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.

DvineLord said:
so you might as well run the ruu then to get jb for the endeavor then flash custom roms? can u still run ics roms afterwards? hopefully they dont have to flash boot.img in fastboot.
Click to expand...
Click to collapse
They have to fastboot flash kernels regardless since their kernel partition isn't writeable in recovery
And I believe they can only run jb roms from that point on
Sent from my HTC One XL using Tapatalk 2

[Q] From ICS to JB

Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.

It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app

Thanks. Is there any way to update the software?

Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB

between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc

With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app

exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One

ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^

exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb

Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?

exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb

Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't

Help with RUU'ing to 2.20

I've been running AOSP ROM's on my evita for a while now, but apparently with the 3.4 kernel you now need hboot 2.14 or higher and mine's at 1.09. My phone was unlocked with S-ON, but I did "fastboot oem lock" this morning because I read that it's necessary for an RUU. I downloaded the 2.20 RUU and tried to run the installer but I always get an Error [170] USB Connection Error. I have the HTC and adb drivers installed successfully and have tried to run the RUU as admin in both Sense and fastboot (bootloader). I'm a bit stumped and would really like to get AOSP back on my phone.

You need to S-off first.
Sent from my HTC One X using xda premium

tlazarus said:
You need to S-off first.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Should I use facepalm for that then?
EDIT
I got s-off, but still no go. Still the error 170.
I know on my old Incredible I was able to rename the rom.zip from the RUU as PB99IMG.zip and put it on the root of my sdcard. Then in hboot it would detect it and ask to flash it. This isn't happening on my evita though. Is there a way to do that, or is that only for older htc devices?

Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium

Venomtester said:
Put phone into fastboot and try again. Check error log to see if it fails to identify your phone.
Open command prompt and type adb devices, if it does not see it then try installing new drivers. If it does see it then enter " adb shell reboot oem-78" that will reboot your phone in to RUU ready fastboot. Open ruu and try running it again.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Where can I find this error log? It did see my device, I did that command (which ended at the black htc screen) and I ran the RUU again but I still get the error 170. I'm also using this RUU http://bugsylawson.com/index.php/fi...320911-2-101053225l-release-271865-signedexe/

Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium

Venomtester said:
Sounds like a bad download. Is it 568.22 mbs? Try roomyshare.com/ruu-evita-ul-cingular.html
You can find it in the list.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It is that size, though I may try the link you gave.
EDIT
Okay, I think I found out what I've been doing wrong. I found this link http://forum.xda-developers.com/showthread.php?t=2119610 and it turns out that the file I've been trying does NOT include the 2.14 hboot that I need. The one I need is the latest JB release, but someone said that if you flash it with superCID and S-ON that it will brick your device. I have superCID but S-OFF, does anyone think that will brick my device? Should I flash the RUU with the 1.09 hboot (which I'm running) first, and then flash the newest RUU? Also, it looks like the link I provided offers flashable OTA's of each update. Would those work/be recommended for TWRP?

Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium

Venomtester said:
Change cid to cingular "cws_001" I think. Super cid can cause brick.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error

dshoe said:
Well I didn't do that...haha. I read on another forum that TWRP doesn't support that cid check function or something and to just remove it from the updater-script so I tried that and flashed the latest OTA zip in TWRP and it failed after a few steps. I tried booting and it didn't get to the boot animation so I rebooted to recovery and restored my backup. I'm going to try a stock zip without the modified updater-script and restore my CID to normal and try again.
EDIT
Well, I restored the CID to CWS__001 and I still get that check_cid error
Click to expand...
Click to collapse
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium

31ken31 said:
To run a ota you need to flash stock recovery image.. and bootloader needs to be unlocked for that
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....

dshoe said:
Hm, okay then, let me ask another question. I'm on hboot 1.09 and I need 2.14 to run AOSP ROM's now. What's the best way to get there if I already have ROM's installed. Is it what I'm doing right now or should it be something else?
EDIT
The latest JB RUU is picking up my device now and offering the update, 2 seconds away from doing it....
Click to expand...
Click to collapse
Just make sure you are s-off before running ruu or risk a brick..
Sent from my HTC One XL using xda premium

Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?

For what it's worth, I was on stock 2.20, got s-off and unlocked bootloader with superCID, and ran the 3.18 RUU with no problems. I didn't need to relock or anything.

knanda said:
Hi. I am looking my update my hboot from 1.09 to 2.14. I am S-OFF now, also running the Sense 5 rom now(TWRP recovery).
I have downloaded the Latest JB 3.18 RUU from instructions here http://forum.xda-developers.com/showthread.php?t=2064621.
What else do I need to do before flashing the RUU to the device?
Click to expand...
Click to collapse
You can go ahead and run the RUU. No real risk because you're s-off. Maybe make a backup though.
Sent from my Evita

[Q] ROm Flashing issue

Hello,
I am trying to flash CleanRom 7.0 or any JB rom on my HTC One X (AT&T) but always gets stuck in bootloop (phone does not go past boot screen after flashing). This is what i have done.
The phone is on AT&T 1.82 stock room (rooted, SuperCID, S-Off). The phone was on some older HBoot version so I upgraded it to 2.15. Radio is 0.17.32.09.12. And I have TWRP recovery.
So I made a nadroid backup in recovery and than tried to install AT&T 3.82 rooted (downloaded from XDA, may be without radio and all). After successful flashing when I tried to reboot the system it got stuck on AT&T boot screen. So I rebooted in recovery and wiped everything. After that I tried to install CleanROM 7.0 R2 and same thing happened and even I tried latest elemental kernel but same thing is keep happening.
Can you please help me with this?
Thanks

At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita

timmaaa said:
At&t 3.82 rooted ROM? Where did you download that? It doesn't look familiar. What are your bootloader details? Which version of TWRP? How did you upgrade your hboot?
Sent from my Evita
Click to expand...
Click to collapse
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks

alex8525 said:
Hey,
Thanks for reply. Sorry I think I mis-wrote it. It's AT&T 3.18 ROM from following link:
http://forum.xda-developers.com/showthread.php?t=2181891
I will check and let you know TWRP version when I get back home. I am not sure about the bootloader details either, what you need to know about the boot loader to help me?
I upgraded hboot by upgrading firmware to 2.15 by using instructions at one of the threads at xda (using adb and fastboot commands and pushing a 2.15 zip to device when it is in bootloader).
Note that I was never able to install any custom ROM on HTC One X. I rooted it before a year or so tried to install CleanROM 5.1 (I guess) but it din't work. I also tried few other ROMs but nothing worked and I gave up. Recently I read that I may need to update Hboot to flash the ROMs. So I did it (had a hard time installing drivers on windows 8 and ultimately have to try winXP!). Still after all this it is not working.
Let me know if you can suggest something based on this.
Thanks
Click to expand...
Click to collapse
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.omg after flashing.
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
Yes I am S-Off. I will let you know the version of TWRP when I get back home since I don't have phone with me right now. By the way I used goomanager to update TWRP, if that helps.
Thanks,

phonegeekjr said:
Ok so you need to give us more info
Are you s-off
What version of twrp do you have
These things matter when you flash a rom. If you are s-on you need to flash boot.img after flashing. Just do
Fastboot flash boot.img
Sent from my HTC Butterfly s using Tapatalk
Click to expand...
Click to collapse
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks

K so if you are s-off then you can just flash it. If you wernt then you would need to flash boot.img. now you can try to flash the boot.img. it might not fix it but start small and work up.
Sent from my HTC Butterfly s using Tapatalk

alex8525 said:
One more thing, I am using TWRP to flash the ROM. Is it a correct way? or I need to flash it using fastboot commands (like you suggested for boot.img)?
I am not much fammilier with TWRP and HTC One X so.
Thanks
Click to expand...
Click to collapse
TWRP is the correct way to install ROMs, but I have a feeling that your current version of TWRP is your problem. Some (2.4.x, 2.5.x) are buggy and have major problems. If your TWRP version is either of those that I've just mentioned you can update it to a known bug-free version like this:
Download the modified version of 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
Sent from my Evita

That's the reason I asked what twrp version he had
Sent from my HTC Butterfly s using Tapatalk