Database Info

Att One X Stuck on Hboot. HElP?

CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??

Andriod_Kuki_ said:
CAN ANY BODY HELP??? I tried flashing the beta Jellybean Custom Rom. I installed the G Apps first by accident in trwp When i tried installing the actual rom. It failed
# I tried again.
Factory rested it first. So it erased my back ups
It failed again
#Now my phone was bricked
read some forums. tried unbricking it my self by using the ARU wizard and RRU.
All it did was secruity lock it.:crying::crying::crying:
# Now My One X is stuck on Hboot. But i can still get into twrp.
Ive been a fan android forever but new to rooting,.
Can anybody hellp me Please??
Click to expand...
Click to collapse
if u can get into twrp...
mount sd copy a rom
wipe everyrhing except sdcard
and flash the rom... u should be good
Sent from my HTC One X using xda app-developers app

i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping

Andriod_Kuki_ said:
i tried doing that but my phone wont show up on my computer. ILL Try again. But what rom would u recommend.
Also is there another way i can fix it??
Thank you for helpping
Click to expand...
Click to collapse
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...

niceppl said:
one promising fix would be relock your bootloader ...run a ruu....unlock ...twrp...
Click to expand...
Click to collapse
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?

Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
?
what do u mean?

niceppl said:
?
what do u mean?
Click to expand...
Click to collapse
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/

Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app

Andriod_Kuki_ said:
Im Using
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
When i run it. It tries to update the rom and it says rom up date fail. then closes.. Do i need to do anything before i run it??/
Click to expand...
Click to collapse
yes..relock your bootloader..
also are you att hox? or rogers hox
did you get supercid?
how you running the ruu?
if you running the .exe...did you install htc sync?(need to install this and have it running before running ruu)

Ok thanks ill try it thank u
Sent from my HTC VLE_U using xda app-developers app

Andriod_Kuki_ said:
Ok.. Run an RUU but it didnt get past the rom update. Am i doing it right.?
Click to expand...
Click to collapse
rpomponio said:
Yes, you most likely need to run the 1.85 ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
suggestion to re lock his hox was mentioned but his reply didn't say if he locked it, just said he tried to run the ruu. Bet it still needs locking! Also OP do you have super cid? If so he doesnt need 1.85 right? He can use the 1.73. I would still probably use the 1.85 like rpopo recommended though. Also if you have done everything correct (re locked and 1.85 if not super cid) the USB drivers can make a difference. I was super cid and locked and ruu kept failing. uninstalled my HTC drivers and ran the HTC sync program and used those drivers...Worked first time after that! Just have to remember to not actually have HTC sync running!

Wats a super cid..? Srry I'm new to rooting
Sent from my HTC VLE_U using xda app-developers app

Try the 1.85 ruu. Relocking and running the 1.85ruu usually gets you back up and running.
Sent from my HTC One X using xda app-developers app

You have to be able to use adb on your computer to relock. There is a sticky with the info on how to install drivers, use adb and relock your phone.
Sent from my HTC One X using xda app-developers app

I have used adb to relock it
Sent from my HTC VLE_U using xda app-developers app

Then run 1.85 ruu, make sure you have the USB drivers for the phone installed and then once you do that, re-root and unlock the bootloader.

It works ran the 1.85 ruu. Ten minutes later running perfectly/ :laugh::good::good::good:
Thanks :laugh::laugh::good::good::good:

If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.

Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium

lmnope1 said:
If you flashed a good ROM and your stuck in hboot, use fastboot and use the following command 'fastboot oem boot' that will force your phone to boot.
Click to expand...
Click to collapse
8125Omnimax said:
Stay unlocked push recovery in fastboot again
fastboot oem rebootRUU
Start the RUU. Finish the install, then back into hboot, select recovery
Invest in a copy of titanium backup and use between rom flashing hence there isn't a micro sd card slot in the HOX
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
fyi, This is an old thread. It looks like he got what he needed the 2nd day of august.

Help - stuck on HTC screen

Okay - I did a really dumb thing - I flashed CM7 with S-on
I tried RUUing it - but my battery is below 30%
It all started when I was on 2.3.4 and my battery wouldn't charge past 15%. So I rooted it, ignored the s-on, and flashed cm7 thinking a different rom might fix the battery issue. I fixed it alright - it stays stuck on the white screen with the HTC Logo. Can anyone direct me to an unbrick without using RUU because it will not charge past 15%
Arrrrrrggggggg- I'm a newb

Any suggestions...
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Ok - got it to charge tried ruu again - 2.3.4 ruu fails & 2.2 ruu gets stuck at 13% reading header. Any thoughts?
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Try THIS take it back to Stock 2.3.4 . Then start the whole rottoing process over.

Ok i'll try running ruu 2.3.4 again tonight. Im skeptical though because as i posted earlier ruu 2.3.4 kept failing.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

prboy1969 said:
Try THIS take it back to Stock 2.3.4 . Then start the whole rottoing process over.
Click to expand...
Click to collapse
I really appreciate your input prboy1969
When I run ruu 2.3.4 I get this errror:
ERROR [155]: UNKNOWN ERROR
Please get the correct ROM Update Utility and try again.
Kind of a crazy error because before the update process starts it compares roms and they match.
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT-0.99.0001
RADIO-1.08.01.0111
eMMC-boot
Dec 29 2011, 10:29:48

Try this. Get adb/fastboot and take the boot.img from the cm7 ROM and move it to where adb/fastboot are. Once there power down and reboot to bootloader and select fastboot USB.
Plug the phone in and open terminal and navigate to where your adb/fastboot are. For me its home/strapped365/android/android/platform-tools
Then use this command
fastboot flash boot boot.img
S-ON Unlocked users can't flash to the boot partition.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

strapped365 said:
Try this. Get adb/fastboot and take the boot.img from the cm7 ROM and move it to where adb/fastboot are. Once there power down and reboot to bootloader and select fastboot USB.
Plug the phone in and open terminal and navigate to where your adb/fastboot are. For me its home/strapped365/android/android/platform-tools
Then use this command
fastboot flash boot boot.img
S-ON Unlocked users can't flash to the boot partition.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
so your saying change directory to my adb folder (c:\program files\android\andrroid-sdk\platform-tools)/extract contents of cm7 to platform-tools folder/fastboot flash boot boot.img
ok I'll try - although I've flashed it so many times with ruu 2.3.4 that I'll have to first re-flash cwm/su/& cm7 - I'll give it a try tonight. thx

mook_ said:
so your saying change directory to my adb folder (c:\program files\android\andrroid-sdk\platform-tools)/extract contents of cm7 to platform-tools folder/fastboot flash boot boot.img
ok I'll try - although I've flashed it so many times with ruu 2.3.4 that I'll have to first re-flash cwm/su/& cm7 - I'll give it a try tonight. thx
Click to expand...
Click to collapse
Not the whole ROM. Just open it with 7zip or similiar and move its boot.IMG to where fastboot is then run the fastboot command I gave. I was under the impression none of the RUUs worked for you so I thought you were s-on unlocked with cwm
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

strapped365 said:
Not the whole ROM. Just open it with 7zip or similiar and move its boot.IMG to where fastboot is then run the fastboot command I gave. I was under the impression none of the RUUs worked for you so I thought you were s-on unlocked with cwm
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
That's right - S-on. I'm going to have to reload cwm because RUU deletes but then fails during update
So this is what I'm going to try:
- reflash cwm from fastboot
- flash boot.img only from CM7 from fastboot
Then what after that?

mook_ said:
That's right - S-on. I'm going to have to reload cwm because RUU deletes but then fails during update
So this is what I'm going to try:
- reflash cwm from fastboot
- flash boot.img only from CM7 from fastboot
Then what after that?
Click to expand...
Click to collapse
Well like after cm7 is flashed and you fastboot its boot.img it should boot
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

strapped365 said:
Well like after cm7 is flashed and you fastboot its boot.img it should boot
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Dude - that freaking worked!!!
I noticed when I go to settings/about phone it crashes "Sorry! The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again.
what next? ruu back to 2.3.4...do the s-off?

mook_ said:
Dude - that freaking worked!!!
I noticed when I go to settings/about phone it crashes "Sorry! The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again.
what next? ruu back to 2.3.4...do the s-off?
Click to expand...
Click to collapse
Well since your booted in, atleast your phone is up and working, even though the settings are crashing. I wouldn't ruu from aosp or anything but that's just me. Being s-on unlocked won't keep you from anything, but you have to fastboot flash boot boot.img of every ROM that has a custom kernel, so its a pain for flashaholics. The choice is yours though, you could just need to do a full wipe a fresh flash and a fresh flash of the boot.img
Sent from my HTC MyTouch 4G Slide using Tapatalk 2

[Q] HTC One XL - Telstra

Hi All,
I am fairly new to all this, I have read countless posts and done everything I can but I am stuck.
I have a HBOOT 2.14 currently with S-ON.
I have installed TWRP in recovery but no custom mods work due to the HBOOT version.
SuperCID is 111111111 and is already set.
I want to be able to S-OFF my device so i can downgrade the HBOOT and use the custom roms.
I ran through the facepalm S-OFF procedure, it all runs correctly, although upon reboot it still says S-ON.
Does anyone know why this would be? Is there something I am missing?
I am doing this some the TWRP recovery mode as that is the only place I can access adb commands currently.
There is no working ROM currently installed, CM 10.1 is installed although it can't be used because the touchscreen doesn't work.
Any information people can provide me to get all this working would be of great help.
Happy to donate/pay someone to help me via teamviewer or whatever.
Thanks,
Tabmowtez

What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium

Venomtester said:
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
v2.4.4.0

I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium

Venomtester said:
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Really? I haven't seen this said anywhere? Do you have any references to the procedures or the TP firmware?

There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium

Venomtester said:
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes that's the one I posted, it still requires S-OFF.
It seems all the fixes need S-OFF and that is the one thing I can't seem to get working as there is no ROM installed so I can't use supersu?

Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium

Venomtester said:
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I will download ViperX3.4.0.zip and use the boot.img to flash it from adb and see how it goes.
I have tried AOSP and CM Roms and all have had the same issue of the TP not working though.
I'll see how this goes.

Just to confirm, it seems all ROMS based off of the 3.17 kernel and higher work with S-ON.
I have the HatkaXL-evita-v4.2.5_Sense5Elements ROM working after I did the following steps:
Place boot.img in sdk platform tools folder
Boot phone into fastboot usb
open your command prompt from the sdk files folder. (shift+right click-select open command window)
type: fastboot erase cache
type: fastboot flash boot boot.img
type: fastboot erase cache (just to be safe)
On phone select bootloader, then recovery.
Once TWRP loads (I'm using 2.4.4.0) go to wipe and select factory reset then wipe system and both caches
Then install the rom and go through setup
once setup is complete, UNCHECK restart now so it leaves the rom and goes back to TWRP.
Click on clear cache/davlik and then click reboot
Settings application keeps on crashing so I am going to try the aokp_evita_jb-mr1_build-4 ROM now after a backup.
I still have issues getting adb to recognise the device once the ROM is booted but that's a separate issue for now...

Are you sure your getting error 92 and not 99 when you flash the zip for s-off cause if your getting 99 you need to fastboot write your cid then reboot and try again
Sent from my One X using Xparent Green Tapatalk 2

I'm definitely getting the error 92. My CID is already a SuperCID so would I have to do that again?
I have the ViperX ROM running now so I am happy, would still like to S-OFF though so I can try CM etc. after a hboot downgrade.
Sent from my HTC One X using xda app-developers app

When I did the s-off to my One XL, the error 92 is normal and I just followed the steps in this thread and it worked fine
http://forum.xda-developers.com/showthread.php?t=2155071

That is the same thread I follow, I will try again now that I have a working ROM and see how it goes.
Sent from my HTC One X using xda app-developers app

All good, I successfully S-OFF'd my device and downgraded my hboot to 1.09. Hopefully this means I can put any mod on now without flashing from fastboot first and having the touchscreen work!
Sent from my HTC One X using xda app-developers app

[Q] Post root unable to access phone through ADB

AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.

alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!

Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app

Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.

You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app

exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.

Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app

Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium

exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***

Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app

exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium

Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app

Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium

31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.

Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium

31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18

If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?

Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.

So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?

Bootloader hangs / OS hands

Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!

xatomicx said:
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
Click to expand...
Click to collapse
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium

31ken31 said:
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe

xatomicx said:
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
Click to expand...
Click to collapse
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium

31ken31 said:
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.

This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita

xatomicx said:
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
Click to expand...
Click to collapse
Did you verify the md5 of the downloads? Could be a corrupted file
Sent from my HTC One XL using xda premium

timmaaa said:
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
Click to expand...
Click to collapse
Yes i am
I tried Cyanogen, just for fun of trying another room, i get the same boot freeze as with Sense 5

I don't know why it's looping, it shouldn't be if you're following the correct procedure. Are you doing a full wipe, then flashing the ROM, and then flashing the boot.img from that ROM in fastboot?
Sent from my Evita

What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium

31ken31 said:
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot

So you're wiping system/factory reset/cache/dalvik cache? Then flashing ROM, then rebooting to bootloader and flashing boot.img?
Sent from my Evita

xatomicx said:
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium

31ken31 said:
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, i am always flashing the boot included in roms, but somehow my bootloader always show 2.14 after flashing ... that might be why i cant get it to work

Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita

timmaaa said:
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Well anyone knows what's the solution? flashing the embedded boot.img did not help.

It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita

timmaaa said:
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
Click to expand...
Click to collapse
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs

xatomicx said:
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
Click to expand...
Click to collapse
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium

31ken31 said:
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i tried nightly 10.1
And sense 5 3.6,
i am now on sense 5 3.6, flash the 3 first, then 3.6 and 3.6.1
ill see for your "scott's clean rom", never heard of it, will try.