Database Info

hboot 1.14 issues switching ICS <--> JB

Hi,
After wasting precious hours on this, I was wondering why this thing doesn’t get more attention.
Long story short, some (all?) ROM installers through recovery have problems flashing the boot.img file (the kernel) when hboot version is 1.14.
The kernel can however be flashed from fastboot : fastboot flash boot.img
To make matters worse, JB roms don’t work with ICS kernels and vice-versa. So it’s very easy to reach a non-bootable state by moving from one to the other.
I learned that here:
http://forum.xda-developers.com/showpost.php?p=35891164&postcount=1
While on ICS Rom , copy ROM and Kernel installer to sdcard
Run Kernel Installer First reboot and after kernel installs (you will know because ICS will on boot to ROM)
you might have to hold down on power button until soft lights flash like 12 times, then hold down volume down button and press power button
when phone boots into bootloader volume down button to recovery option then press power button to get to recovery to flash JB ROM
Click to expand...
Click to collapse
The following procedure seems reliable (probably for every ROM):
http://forum.xda-developers.com/showpost.php?p=35755205&postcount=761
wipe system. wipe cache. wipe dalvik.
factory reset.
flash rom.
have twrp boot into bootloader.
fastboot flash boot.img
reboot
Click to expand...
Click to collapse
You can get the boot.img from the zip of the ROM you’re installing if you need it.
The major problem however is ROM installers that don’t offer the option to skip the kernel flashing. When the installers try to flash the kernel, it takes a LONG time for it to give-up.
During this time you're left wondering if it's ever going to finish or it needs to be interrupted.
Also, this time is completely wasted, because by the time it finishes, the kernel hasn't changed and it still needs to be done from fastboot.
A good example for one installer that does have the option to skip kernel flashing is here:
http://forum.xda-developers.com/showthread.php?t=1655011
All the ROMs that I found have incomplete information about this or neglect to mention this completely on their front page. I wish they didn’t.
I hope this will be useful to someone... it sure would have been for me.
ystavi

Wrong section ??
Sent from my HTC One XL using xda app-developers app

This will be moved/closed soon
Sent from my HTC One XL using xda premium
---------- Post added at 04:11 PM ---------- Previous post was at 04:08 PM ----------
Or you could download flash img gui and preflash the boot.img b4 flashing Rom. Simple as that.
Sent from my HTC One XL using xda premium

Where is cheesy nutz

I hate to say everything you just stated is common sense...
If you're having issues with your hnoot then downgrade and avoid all these so called problems
Sent from my One X using Tapatalk 2

superchilpil said:
I hate to say everything you just stated is common sense...
If you're having issues with your hnoot then downgrade and avoid all these so called problems
Click to expand...
Click to collapse
So you think that if a ROM installer assumes that I'm not using a specific hboot then there's no need to bother to say so on the front page of the ROM or during the installation?

I agree all installers for HTC One XL should offer the choice to not try to install boot.img inside their script.
The problem is super common and simple to resolve.
Many do not want to install boot.img from recovery, make it an option. Downgrade of hboot is not supported by HTC and is not at all required to install custom ROM's so why try beating a dead horse when the answer from HTC is simple, "flash boot.img from fastboot."

New to One S and need some help

Hi,
Normally, I try to troubleshoot things myself without bothering others, but I'm in need of help this time. The tricky part is, I just bought this HTC One S from a stranger, so I don't have its complete history. With that said, here's what I need help with. The phone came with Pacman installed (v18.0.0). But, I would like to install this ROM: http://forum.xda-developers.com/showthread.php?t=2082451
It's basically a stock ICS ROM (the lite version mentioned with stuff removed). In attempt to do this myself, I found this post on here:
Yes the only other solution for you involves rooting. It is possible to go back to ICS by rooting your phone, going through a bootloader downgrade, hexediting a particular partition, then running an older compatible RUU... Its all possible, but requires some time to understand and do. And definately requires a few wipes of phone data in the mean time (which can be backed up through titanium and custom recoveries).
Only need to do that if you want to downgrade hboot. All you have to do is root and flash a rom, I have JB radio and hboot and run ICS Trickdroid 8.1.0.
So, I put the ICS ROM in the internal sdcard, did the usual wiping stuff (I've owned several HTC phones, so this part I know how), then installed the ROM. Unfortunately, it didn't work. When I rebooted the phone, it got stuck in boot loop. It would go to HTC logo screen with the development purpose only warning and just keep turning off and on. Fortunately, I was able to get back into recovery and restored it to Pacman. So, apparently, you can't just flash any ICS ROM over JB setup... Can someone help me figure out what I need to do to install that modified stock ROM please? I very much appreciate your help. My One S is S4 from T-Mobile.
Thank you,
GT

Did you flash boot.img?
Sent from my HTC VLE_U using xda app-developers app

thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.

dr_rick13 said:
thats weird.. if you wipe cache, dalvik, factory reset and system.. it should be fine.
which recovery do you have? cwm or twrp? flashing the rom after wiping everything i stated before, and then flashing boot.img depending on your hboot [btw, go to bootloader and see what it says for hboot. if it is higher than 1.13, you need to fastboot boot.img.
Click to expand...
Click to collapse
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.

goldentequila said:
Thank you for tending to my thread. The recovery installed is CWM 5.8.3.1
Here's what it says on fastboot:
Tampered
Unlocked
VLE PVT SHIP S-On RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Please let me know what exactly I need to do in step by step or point me to a thread that contains the steps. Thank you so much.
Click to expand...
Click to collapse
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.

dr_rick13 said:
no prob, i HIGHLY suggest you flash TWRP recovery.. it's a loot better.
2. are you trying to install a TMOUS ROM?
3. since your hboot is higher than 1.13, you will need to fastboot boot.img [let me know if you know how to do that]
4. also since your hboot is higher than 1.13, you will need to flash some partitions or else your WiFi won't work.
Let me know if you need help doing any of the above, but start out with installing TWRP first.
Click to expand...
Click to collapse
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,

goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
If the Toolkit can't see your phone then you might need to install the drivers that come with it for it to work.

goldentequila said:
Thank you for such a prompt reply. Here are some of my answers.
2. Yes, the ROM I want to install is this one: http://forum.xda-developers.com/showthread.php?t=2082451
It's the light version mentioned in that first post.
3. I just read up on this page: http://forum.xda-developers.com/showthread.php?t=1752270
I think I got the idea, but just to double check, is this what I need to do after every time I install a custom ROM?
4. The partition files exist on the phone already, and I read some, so I have a basic understanding of it. But, the developer of the ROM I want to install says it is not necessary with that ROM, so hopefully that's true.
I am amazed by how different everything is from a HTC phone to another HTC phone even when they seem so similar!
A quick question. Does EXT4 exist for HTC One S? I used to use that for HTC Sensation and loved it. I'm guessing no, but I thought I'd ask.
So, to sum it up, is this what I need to do?
1. Flash TWRP recovery (please tell me how to find the right version for S4. all in one toolkit doesn't work on my phone).
2. Wipe everything and install the ROM
3. Flash boot.img
4. If wifi is not working, try the partition files
Please let me know if I got this right. Thank you,
Click to expand...
Click to collapse
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files

dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Ya 4EXT is coming soon.

dr_rick13 said:
3. Yes, since your hboot is higher than 1.13, you will need to fastboot boot.img everytime you flash a ROM, unless you want to downgrade?
3.5: like Darknites said, you will need to install drivers for your the One S if you haven't already. You can download HTC Sync, and they'll install automatically [this is needed for being able to fastboot the boot.img]
4. They do exist, but everytime you wipe before flashing a ROM, they also get deleted, but try using the ROM without flashing the partition files and see if it works, if not then flash the partition files.
5. Yes, I'm pretty sure EXT4 exists with the One S, but am not 100% sure, maybe someone else can confirm this?
Lastly, here is where you download TWRP:
http://teamw.in/project/twrp2/100
scroll down and download the link for the S4 VARIANT, but you need to have drivers installed before doing this. and you will need to fastboot the recovery, since the download is an image: to do so, go into cmd, type cd c:\ (whatever your fastboot folder is called) and enter
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash.
BTW, here are the drivers:
http://d-h.st/users/Inferi0r/?fld_id=2736#files
Click to expand...
Click to collapse
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!

goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Also try rebooting the computer if its still not working.

goldentequila said:
Thank you so much. Yes, I tried installing the drivers using the toolkit's function, but I haven't tried HTC Sync option. Maybe that'll work better. I think I know what I need to do now. Thanks a bunch!
Click to expand...
Click to collapse
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT

goldentequila said:
Thank you, dr_rick13 and other kind members who responded to my call for help.
I was able to troubleshoot this, and now my phone's working the way I wanted it. Just one correction on dr_rick13's instruction:
then, type: fastboot flash [name of recovery, which is the name of the file you downloaded).img. Should take about 2 seconds to flash
recovery is missing in that line, so it should be fastboot flash recovery [name of recovery, which is the name of the file you downloaded).img
I know it was just a typo or forgot to write it, but I wanted to point this out in case some other user finds this thread and follows that instruction.
All in all, thanks for everything! You guys rock!
GT
Click to expand...
Click to collapse
oops, it was late last night when I wrote that.. my bad
Sent from my HTC One S using xda premium

I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
we do not have S-OFF yet, so until we do.. people with hboots 1.13+ will need to flash boot.img. But HTC still hasn't said anything about when we will get S-OFF or if we will get it.

pnut22r said:
I'm new here too. I understand that you need to flash the boot.img with that hboot, but why? And will it ever be fixed?
I've owned and rooted many a phones and never had to do that. Just curious why it's like that, and if it will be fixed. It's just easier to not be that way. Again, I'm new here, just trying to understand
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.

Darknites said:
Its just the way HTC wants us to do it and maybe they feel it be better for us but mostly them. There is a way round it but you have to downgrade the Hboot.
Click to expand...
Click to collapse
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
Thanks. Is there any downside to downgrading the hboot? Why don't people do that instead?
When I had the Amaze, the recovery 4ext had "smart flash" which did this same thing because it was s-on
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.

Darknites said:
Because of Linux and the fact you brick it to do it too. We meant to be getting 4ext but don't know when.
Click to expand...
Click to collapse
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2

pnut22r said:
Thanks
http://forum.xda-developers.com/showthread.php?p=33233125
This seems like out would make things so much easier. I'm not always around a pc when wanting to flash things. If I use this, I should be able to flash away.
But what about resorting nandroids. This doesn't work with that. Hmmm
Just trying to wrap my mind around it
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yep very good app I did use it in till I downgraded.

[Q] HTC One XL Telstra No OS flashed stock rom but need help!

Hi all I was given a HTC One XL telstra version it had no OS not a thing on it and I have managed to flash rom and TWRP but have no idea where to go from here I can use fastboot and also mount the SD card via TWRP now how do i get an OS onto it and what am I looking for exactly?

Ok so you have TWRP recovery? If so just download a ROM on your PC, then enter recovery on your phone, connect your phone to the PC and go to the mount menu then mount usb storage. Copy a ROM to the phone. Enter the wipe menu in recovery, perform a full wipe (cache/dalvik cache/system/factory reset). Enter the install menu in recovery, locate the ROM zip you copied to your phone, swipe to install. If the phone is s-off you can reboot now and it should boot into the OS. If you're s-on you need to flash the boot.img via fastboot, so reboot to the bootloader. Locate the boot.img in the root of the ROM zip on your PC and copy it into your fastboot folder. Issue this command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the OS.
Sent from my Evita

timmaaa said:
Ok so you have TWRP recovery? If so just download a ROM on your PC, then enter recovery on your phone, connect your phone to the PC and go to the mount menu then mount usb storage. Copy a ROM to the phone. Enter the wipe menu in recovery, perform a full wipe (cache/dalvik cache/system/factory reset). Enter the install menu in recovery, locate the ROM zip you copied to your phone, swipe to install. If the phone is s-off you can reboot now and it should boot into the OS. If you're s-on you need to flash the boot.img via fastboot, so reboot to the bootloader. Locate the boot.img in the root of the ROM zip on your PC and copy it into your fastboot folder. Issue this command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the OS.
Sent from my Evita
Click to expand...
Click to collapse
Hi Mate thanks for the quick reply
yep sure do
So I have downloaded Stock Telstra JB 4.2.2 - 5.06.841.1 Rom with Root access
but already had OTA_EVITA_UL_JB_45_S_Telstra_WWE_3.17.841.2_0.23a.32.09.29_10.128.32.34a_release_2997538hizl4svcm80o4g1
as i am s-on can i use the ota file?
Sorry new to the world of HTC

No worries, if you have any problems just ask here.
Sent from my Evita

timmaaa said:
No worries, if you have any problems just ask here.
Sent from my Evita
Click to expand...
Click to collapse
if i use a stock telstra rom i need to relock the bootloader right? but if i do that it doesnt allow me to enter TWRP so i should use some other rom?

No, if you use one of the stock Telstra ROMs found within our development sections you don't need to relock your bootloader at all. You just flash it in recovery and away you go. If you're talking about an RUU it's a different story, with more preparation involved. There's really no need to run an RUU at this point though so just stick with the Telstra ROM (in zip form) and you'll get the full experience.
Sent from my Evita

timmaaa said:
No, if you use one of the stock Telstra ROMs found within our development sections you don't need to relock your bootloader at all. You just flash it in recovery and away you go. If you're talking about an RUU it's a different story, with more preparation involved. There's really no need to run an RUU at this point though so just stick with the Telstra ROM (in zip form) and you'll get the full experience.
Sent from my Evita
Click to expand...
Click to collapse
Seriously Timmaaa I could kiss you right now! you are an absolute legend! got it sorted my main issue was findint which file to use I ended up using Stock_Telstra_3.17.841.9 and flashing the boot as you explained you made my HTC noob experience so much less frustrating Thank you so much!

Lol :sly:
So you got it booted up ok?
Sent from my Evita

timmaaa said:
Lol :sly:
So you got it booted up ok?
Sent from my Evita
Click to expand...
Click to collapse
sure did! thanks mate

No problems, glad to hear it. Welcome to the community by the way, it's good to see another Aussie (I'm guessing) in here.
Sent from my Evita
---------- Post added at 07:33 PM ---------- Previous post was at 07:27 PM ----------
Oh, something I did want to mention. You're not limited to using Telstra ROMs, there are some great ROMs with great features here in our forums. We're very lucky that there are some great devs still providing us with ROMs even though the device is over 18 months old, they're keeping this phone relevant. Just make sure you stay within this device forum and you'll be super duper. Here are the links to our two development sections:
One XL Android Development (mainly Sense)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (mainly aosp)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my Evita

MissCrittie said:
Seriously Timmaaa I could kiss you right now! you are an absolute legend! got it sorted my main issue was findint which file to use I ended up using Stock_Telstra_3.17.841.9 and flashing the boot as you explained you made my HTC noob experience so much less frustrating Thank you so much!
Click to expand...
Click to collapse
Looks like Timmaaa might get lucky! only kidding
Welcome to the XDA forums from another aussie!

[Q] [Help Please] How to install Custom Rom in HTC one x (AT&T)

I have HTC One x (At&T) US Version and using it in India.
It has Stock ICS 4.0.4 and Already Rooted,
Already S-OFF,
has Custom Recovery TWRP and
SCID is 111111111 and
Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 .....
Now my Questions is :
1. How to Update is to jelly Bean and if i Update it to Stock/Custom jelly bean then do i have to unlock/S-off it again? If Yes then How to do it? Any Given Link will be Highly Appreciated.
2. I read some Posts/Comments on some 4.2.2 Custom roms threads that "Highly recommend latest Jellybean firmware".. what does that mean? (my confusion is if i already have latest jelly Bean Firmware then why would i search update for jelly bean? )
3. if it is recommended to have latest jelly bean firmware before update to 4.2.2 then can anybody give me the link for that?
4. HTC One x AT&T has beats Audio.. if i update it to Any 4.2.2 Custom Rom.. then will beats Audio Work on new Rom? (I know it is Noob Question but i really want to know because i want Beats Audio For Music)
Thanks in Advance

1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita

timmaaa said:
1. All you need to do is install a stock 4.1 ROM from our Android Development section. Or you can install a custom ROM if you want to. The How-To Guide For Beginners link in my signature details how to do this, along with other basic operations.
2. The reason there are recommendations to flash the 2.15 firmware is because many people with a modified phone don't have the latest firmware even though they might have the latest ROM. In the world of modified phones it's completely normal to switch ROMs without changing your firmware. For someone with an unmodified phone the only way to upgrade your ROM is to also upgrade your firmware. Before deciding if you need to do this (you most likely do) I need your bootloader details, the first five lines.
3. You'll find the firmware package along with install instructions in the first post of this thread.
4. Yes, Beats is incorporated into all current Sense ROMs. If you decide to install an aosp ROM it isn't incorporated.
Further to all those answers, I'd strongly recommend you do a lot of reading before proceeding with anything. Modifying a phone requires a certain level of knowledge, without knowing what you're doing (and the consequences) you can quickly get in over your head and end up with a device that won't boot, or worse.
Click the Everything Evita link in my signature, it's a resource thread that contains links to everything you'll need, make sure you bookmark that thread. Click the other links in my signature too, you'll find a wealth of very useful information in those threads. I'd also suggest you browse our forum for a few days to get a firm grasp on things. I'll put it like this, I researched for two weeks before modifying my phone.
Sent from my Evita
Click to expand...
Click to collapse
First of all thanks a lot for replying So fast and giving your time to help me...
my bootloder details:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-1.14.0002
and also my Software number/Build Number is 2.20 and
Kernel version is 3.0.8-01558 ..... is it ok or first i need to update both ?

If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita

timmaaa said:
If you want to update to Android 4.2.2 and Sense 5 you first need to flash the 2.15 firmware found in the thread I linked you to before. Do you have a custom recovery installed? If so all you need to do after flashing the firmware is to install a ROM of your choosing. If not, just look in my How-To thread for instructions on how to do that. There's no need to worry about your current ROM/kernel, flashing a ROM will update those.
Sent from my Evita
Click to expand...
Click to collapse
i have build number 2.20.502.7.. do i still need 2.15 firmware?

For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita

timmaaa said:
For the third time, yes. Your build number is irrelevant anyway.
Sent from my Evita
Click to expand...
Click to collapse
i am stuck at firmware...this error comes everytime... screenshot attached... please see ...

Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita

timmaaa said:
Try opening the command prompt from within the fastboot folder. To do this just navigate to the location on your PC where fastboot.exe is located, then shift + right click anywhere within that folder, then select open command prompt here. Now start the process from the beginning. Then when you get to the part where you flash the firmware you don't need to cd to the location, you just do this:
Code:
fastboot flash zip firmware.zip
Sent from my Evita
Click to expand...
Click to collapse
everything has done successfully... thanks a lot for you help...
but
when i rebooted my phone (ICS) and gone to Settings>about>Software Information... it still showing 2.20.502.7 710RD.... is it normal or something is wrong..... Attached Screenshots both.. phone and my command window.... please check this.. (i am sorry i am disturbing u
a lot coz i am noob :'( )

You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita

timmaaa said:
You still have the 2.20 build number because that's the ROM version that is currently installed on your device. All you have done so far is update your firmware, that's completely separate to your ROM.
At this point all you need to do now is install a ROM. You'll find Sense 5 ROMs in our Android Development. You'll find instructions on installing a ROM in my How-To Guide For Beginners thread in my signature.
To install a ROM you first need a custom recovery, go into your bootloader and select recovery, tell me what happens.
Sent from my Evita
Click to expand...
Click to collapse
Yes, i have already installed Custom Recovery TWRP... now i think all i need to do is install a ROM .... so should i directly install any 4.2.2 custom ROM or first i should install 4.1 then after 4.2 ?

You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita

timmaaa said:
You can install any custom ROM you like, no need to install a 4.1 ROM first. But you should make a backup, check my How-To Guide For Beginners thread for instructions on how to do that.
Sent from my Evita
Click to expand...
Click to collapse
Oh!! yehhh .. nice nice nice... thanks a lot a lot a lot......u r really nice person... u made my Day...

No problems, glad I could help.
Sent from my Evita

timmaaa said:
No problems, glad I could help.
Sent from my Evita
Click to expand...
Click to collapse
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
and i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?

info2shail2010 said:
last Questions .. hope u dont mind...
1. if i install Any "STOCK" Rom then do i have to S-OFF/Unlock/Super CID Again?
2: I chose this ROM http://forum.xda-developers.com/showthread.php?t=1655011
But it says it is with At&T settings ... my confusion is , my phone is US version.. and i am using it in India.. AT&T is not in india... so if i install this rom then will my sim work after installing this ROm....
Click to expand...
Click to collapse
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita

timmaaa said:
Installing a stock ROM doesn't affect your bootloader or your s-on/s-off status, it only writes to the /system partition.
That ROM does contain some at&t elements, but whatever SIM card you're currently using should be perfectly fine. Once you've SIM unlocked a device you can use any SIM card on it.
Basically you can use any ROM found within our device forum and you'll be ok.
Sent from my Evita
Click to expand...
Click to collapse
i downloaded this Rom and tried to flash in TWRP recovery.. but it is failing everytime.. and i did factory reset (wipe data, cache and dalvik .android_secure)... now i am unable to use my old rom...what should i do now?

Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita

timmaaa said:
Exactly which version of TWRP have you installed? Did you make a backup earlier like I suggested? If so you can use the restore feature in TWRP to restore that backup of your previous ROM. I do need to know which TWRP version you're using though.
Sent from my Evita
---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------
Also, did you check the md5 of the ROM after downloading it?
Sent from my Evita
Click to expand...
Click to collapse
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5, where to find and what to check in it and how to check ?

info2shail2010 said:
TWRP : 2.5
Back Up : No ( i thaught back up is for my personal data.. that i already have in ma pc )
MD5.. i didnt get it... what is md5 and what to check in it ?
Click to expand...
Click to collapse
Ok there's your problem, TWRP 2.5 is full of bugs. 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
Now you should be able to install the ROM.
An md5 is like a digital fingerprint of a file. It will be listed on the download page for a ROM/kernel/radio. What you do is use an md5 checking app/program to check that the md5 of the downloaded file matches the md5 listed on the download page. If it matches you're all good, if it doesn't match it means the file became corrupted during the download. You should always check the md5 of anything you're about to flash, a corrupt file could damage your phone if you install it.
Once you have installed the ROM you should reboot back into TWRP and use the backup feature to backup system/data/boot. Then if you have any problems in the future you can use the restore feature to restore it and you'll have a working OS.
It's also a good way to have your favourite ROMs backed up. Once I decide I like a ROM I set it up with all my apps and settings and then make a backup. That way if I ever want to use that ROM in future I can easily restore the backup and have a fully setup ROM ready to go. It's much easier than installing a ROM from scratch and setting it up all over again.
Sent from my Evita

HTC one XL evita deleted restore via factory reset

I was running a rom on my phone working fine until the new update came and I tried to install which sent me to my recovery page (TWRP v2.5) I then factory reset hoping this would work and managed to delete my recoveries and now whenever i restart my phone i either get the message of no os installed or when i install a rom and it actually works i get stuck in a boot loop. im not sure if it is the rom or not (KickDroidXL v5) any help would be appreciated, Thankyou

Your problem is your recovery version, TWRP 2.5 is very buggy and has major issues with wiping and with flashing. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can flash the ROM again and you should be fine.
Sent from my Evita

thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy

Guested said:
thanks for that, successfully running twrp 2.6 however when i attempt to install my rom it loaded into recovery as if i chose it from the bootloader screen. when i skipped that one and tried another it got to the htc screen then turned off
thanks again, its now working after looking at your q&a thread! was stuck on the boot loop without the boot.img file, too easy
Click to expand...
Click to collapse
Yeah, you should get s-off either here or here. Then you won't have to worry about flashing the boot.img anymore. You're gonna need s-off to upgrade your firmware anyway, otherwise you're gonna suffer signal losses and random reboots.

so trying to use s-off at the moment and i am not able to boot into recovery (just goes to htc startup screen and phone turns on) i then tried usb debugging where i got the response, needs to be formatted, tried that and said it was impossible as i didnt have any permissions! any ideas?

Neither of the s-off processes need to boot into recovery, what do by mean by that?
Sent from my Evita

so i tried the rum runner method which got stuck when on test 2 it tells me it must ferment longer, i wait in this process for awhile and it attempts to start my phone however it doesnt start up only a black screen with no led (i assume the phone is off) the only way to start is by holding down the power and waiting for the 15 flashes from the buttons then putting it into bootloader, from there i chose recovery and it starts normally without entering the twrp screen.
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit

Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita

timmaaa said:
Do you have SuperCID? If so you could try the Facepalm method instead.
Sent from my Evita
Click to expand...
Click to collapse
no CID, i tried using http://androidforums.com/sensation-4g-all-things-root/636482-guide-how-supercid.html
didnt work came up with an error of too many links after getting to this stage -change CID
fastboot oem writecid 11111111 (eight ones)

okay so i assume it has something to do with the rom, i flashed twrp 2.6 back and recovery works fine! any suggestions on a battery low and stable rom?

Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita

timmaaa said:
Asking which ROM is best/most stable/fastest/prettiest question isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Sent from my Evita
Click to expand...
Click to collapse
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected

Guested said:
thanks for that, didnt know! got a new rom running smoother, however rum runner doesnt work and no method to change the CID works? when changing it to 11111111 it gets an error that the device is not connected
Click to expand...
Click to collapse
You need to get adb/fastboot and your drivers sorted out. Try using an app called pdanet+ from the Play Store, you download it to your phone and then another component on your PC. When you open the PC component it'll install drivers, it's what got everything working for me.
Sent from my Evita