Database Info

[Q] HOX Jelly Bean questions

Hi guys, been reading through the threads. Fixing to try flashing this rom soon. Have a couple of quick questions tho.
My phone is bootloader unlocked, twrp installed, and rooted. Will flashing this rom change any of that? From the looks of that thread it seems the answer is no, but just wanted to confirm.
Also, I see that this rom does not come with a radio. Should I download just the radio, or do I need the radio + RIL?
Am I fine with the HBOOT that came with 2.20?
And as far as installing...boot into recovery, wipe dalvik, factory reset, and then flash the zip?
Oh...and this is for a AT&T HTC One X

You're fine. Just flash it. You can flash the radio if you like. The RIL is in the rom.

Well the biggest thing bothering me is the HBOOT. It's from the AT&T 2.20 Ice cream sandwich update. I for sure won't have any problems with that? Oh, also...like I said I am bootloader unlocked, but as far as I know I'm not S-OFF. Is that ok?

jrphoenix77 said:
Well the biggest thing bothering me is the HBOOT. It's from the AT&T 2.20 Ice cream sandwich update. I for sure won't have any problems with that? Oh, also...like I said I am bootloader unlocked, but as far as I know I'm not S-OFF. Is that ok?
Click to expand...
Click to collapse
Should be fine, you just need to flash the boot image manually using a computer. After you get everything up and running I'd s-off and then flash the 1.09 hboot from here for convenience sake.
http://forum.xda-developers.com/showthread.php?p=38210444
Sent from my HTC One X

So I need to adb the boot.img first, then flash the rom?

Yeah.
Sent from my HTC One X

What a pain. I miss the days of my Captivate and Infuse where root + custom recovery = unlimited flashing fun.

If you do like I suggested it will be like that. It just takes a little while to setup.
Sent from my HTC One X

jrphoenix77 said:
Hi guys, been reading through the threads. Fixing to try flashing this rom soon. Have a couple of quick questions tho.
My phone is bootloader unlocked, twrp installed, and rooted. Will flashing this rom change any of that? From the looks of that thread it seems the answer is no, but just wanted to confirm.
Click to expand...
Click to collapse
Correct. If you are stock rooted, it's a good idea to do a backup in twrp just in case.
Also twrp 2.3.3 is suggested as 2.4 seems to have issues wiping.
jrphoenix77 said:
Also, I see that this rom does not come with a radio. Should I download just the radio, or do I need the radio + RIL?
Click to expand...
Click to collapse
I would only flash radios if you notice low signal strength or battery drain from radio usage.
If you check the radio thread it tells you if you need RIL's or not
http://forum.xda-developers.com/showthread.php?t=1694012
jrphoenix77 said:
Am I fine with the HBOOT that came with 2.20?
Click to expand...
Click to collapse
I believe that's HBOOT 1.14? You would need to S-OFF or downgrade to 1.09 using the JET Tool to flash radios but you may not even need to flash radios, it's your call.
jrphoenix77 said:
And as far as installing...boot into recovery, wipe dalvik, factory reset, and then flash the zip?
Click to expand...
Click to collapse
I would wipe system too or flash the wipe tool, then flash the zip. Then fastboot flash the boot.img (You can flash it before the rom too, either works) from the rom if you are indeed on hboot 1.14 which I am pretty sure you are.
.

Thanks for all the help guys. It appears I was over worried. After spending the day reading threads and getting an idea of what I needed to do and in what order to do it I finally decided to just do it. I pulled the boot.img from the rom and flashed it with fastboot. Then flashed the rom with twrp (yes I had 2.3) and did a backup before all that. Let the rom boot and then rebooted to bootloader and fastboot installed the new radio. Everything is up and running great. Will look into S-OFF and downgrading my HBOOT later. Thanks for all the help!
Sent from my HTC One X using xda app-developers app

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.

Can't S-Off for the life of me

Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.

I got s-off with viper
Sent from my VENOMized HoxL

area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?

Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita

timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)

Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita

timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.

The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita

timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2

Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.

timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.

Did you flash the boot.img via fastboot?
Sent from my Evita

timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.

It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita

timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.

It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita

timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0

Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita

timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP

HTC One X AT&T Stuck in Boot Loop After Flash

Hi, my AT&T HTC One X is running CM10.2 with S-ON. However, on boot, sometimes the device puts itself into a boot loop. You then need to reflash the boot.img from the computer to the phone. Is there any way I can stop this? Thanks.

Nope, not with your current setup. If you're s-on you need to flash the boot.img with fastboot every time you flash a ROM. Don't even bother trying to boot into a ROM after flashing it without first flashing the boot.img via fastboot. If it has booted sometimes without flashing the boot.img, it's because the boot.img that was left over from the previous ROM is somewhat compatible with the new ROM you flashed, this is not optimal of course. If you don't want to have to flash the boot.img anymore, get s-off. Having s-off removes the restriction that causes the boot.img to not be flashed in TWRP when flashing the ROM.
Sent from my Evita

timmaaa said:
Nope, not with your current setup. If you're s-on you need to flash the boot.img with fastboot every time you flash a ROM. Don't even bother trying to boot into a ROM after flashing it without first flashing the boot.img via fastboot. If it has booted sometimes without flashing the boot.img, it's because the boot.img that was left over from the previous ROM is somewhat compatible with the new ROM you flashed, this is not optimal of course. If you don't want to have to flash the boot.img anymore, get s-off. Having s-off removes the restriction that causes the boot.img to not be flashed in TWRP when flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
You misunderstood me. I did flash boot.img and I'm still having boot loops.
Sent from my SGH-I337 using Tapatalk

Have you read the cm10.2 thread? There have been major problems with getting that ROM to boot recently.
Sent from my Evita

timmaaa said:
Have you read the cm10.2 thread? There have been major problems with getting that ROM to boot recently.
Sent from my Evita
Click to expand...
Click to collapse
Where is the CM10.2 thread?
Sent from my SGH-I337 using Tapatalk

Really? It's in the development section. If you don't even know where the thread is I think I can pretty safely assume you haven't read it. If you're having problems with a ROM please read the ROM thread before cluttering up the forum with an unnecessary new thread. To be honest, recovering from a bootloop is about as simple as it gets, you should know how to do that before beginning to flash ROMs.
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