Database Info

[SOLVED] One S - a little stuck between roms

Hello.
I'm coming from HD2 and Sensation recently and wanted to get a custom rom for my new One S. I'm inexperienced with this model.
I followed the unlock / cwm / root procedure in the excellent guide sticky. Everything went very well and I tried Jellybam. Got the boot anim but no full boot. I forgot to back up the stock rom so there I was with no working rom and no way to copy a new one onto the sdcard partition.
After some research I've been able to push new rom files to the sdcard partition through adb but I can't seem to get anything to boot on this thing.
I also tried relocking but I cant find which RUU to match my CID (HTC__Y13), I tried all the EU RUU's but they all give me the signature error upon flashing.
So I'm not bricked, I can still install different recoveries and use fastboot. It's just that nothing boots. What am I missing out on here? Oh, and QuickADB tells me that I am not rooted and busybox is missing although I've ran SuperSU CWM.
Any thoughts?

QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.

Goatshocker said:
QuickADBPusher is unable to acquire root because you are on stock rom/kernel. The Q&A section tells you that
Have to fastboot flashed boot.img? Its required for hboot above.... urm.. Dunno, but 1.14 needs it anyway.
Click to expand...
Click to collapse
I now tried to follow the instructions for flashing custom rom on HBOOT > 1.09. So I extracted the boot.img from my desired ROM package. Then I went for another adb push of the rom file (I had done a clear memory in the meantime) and now I'm getting protocol error all over the place.
I miss my HD2. I even miss my Pyramid now...
EDIT: The boot.img flashed fine though.

Wait wait! It worked!
Finally got MIUI (my secret lover) pushed and boot.img extracted and flashed.... and voila!!
Goatshocker! Major respect and bigups for your little advice for the n00bs but first and foremost for all the work you do for our community. You rock man.

Oh thanks. I dont think I do that much though but I try to help where I can

Goatshocker said:
Oh thanks. I dont think I do that much though but I try to help where I can
Click to expand...
Click to collapse
It's always those little things that pass us by.
Hope this thread can help other EU users though. Many of the posts on One S kind of imply that your'e on a low hboot. (Other markets, branded and so forth) But the phones we get these days up here are unbranded 2.15 by stock and you'd always have to manually flash boot as I understand.
Hopefully theres enough food in here for the search engines so that others might find it. Ah. A great day after all.

[Q] Htc one s telus RUU?

I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!

IsaacDroid said:
I made the mistake of running a cm10 rom on my htc one s that didnt work on i so now i can only access TWRP and my phones bootloader from my One S so I'm trying to find my phone's stock RUU but there are so many out there! Can anyone tell me how to find one? Or another way to get into my phone using another ROM? My phone is rooted with Twrp recovery, Unlocked bootloader obviously and S-on. All my phone does is show the htc bootscreen and then go black but I can still enter bootloader and the TWRP menu and I can connect it to my computer fine. Any help would be VERY greatly appreciated!
Click to expand...
Click to collapse
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!

Thanks!
new_convert said:
Don't give up. I had the same issue with my telus One S. I think I fixed it by falshing boot image separately and after flashing CM10. I believe this happens if the phone is rooted but is in S-ON mode, whatever that means. I remember it really gave me a hard time and as I was going to give up i flashed the boot image and it worked. You have to do it through a command window on your PC. There should be an all-in-one tool in this forum somewhere to simplify the steps a bit. Good luck!
Click to expand...
Click to collapse
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!

IsaacDroid said:
Thank you very much! Could you tell me what boot image you flashed and maybe how to get it and also how you flashed it? Thank you so much for the response!
Click to expand...
Click to collapse
It is in the zip file that you download to flash, i.e. your new ROM. So when you download CM10, open the zip file. BOOT.IMG will be there. Extract it and flash it to your phone. I believe everything was in One_S_All-In-One_Kit_v3.4. Look it up in the forum and it has all the tools you need. I admit that it was a pain and nothing was straight forward. I always root my android devices and install new ROMs. But HTC One S was particularly tricky.
Good luck!

Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon

seoman81 said:
Hello there! Fellow HTC One S user here! Don't give up on CM10! It's way better than stock on your one S! What you need to remember is that HBoot versions higher than 1.09 can't flash the boot while installing the rom, so you need to do that after flashing a rom! The boot for your version is going to be included in the rom's zip file. Look for the boot.img file located in the zip file's root. Every rom should have this. Place this boot.img file in the kernel folder of the One S all in one kit and flash it. You should be good to after that!
Don't hesitate to ask for more help if needed!
Simon
Click to expand...
Click to collapse
When I try to flash a ROM through fastboot it sends it fine but then it says: FAILED (remote: not allowed), and I tried pushing the ROM with adb but when I tried to put it on the sdcard, it said permission denied, do you know why? I am S-ON, would that be a problem? Thanks!

[Q] Modded Rom vs CM10, JuopunutBear vs Revolutionary

Hi everyone,
I got tired of waiting for any info regarding "official" JB on the Sensation.
In the family we have a Nexus4 and I am quite impressed with stock JB, so I decided to go for it on my Sensation.
I have unlocked the bootloaded but I haven't gained S-OFF yet.
I was about to go with the JuopunutBear trick but I am still not sure about which rom to flash, so I started looking ...
I went to CyanogenMod website and I see that there are nightlies available of CM10 for the Sensation. Looking at the guide on how to install CM on the phone, there are references to the "Revolutionary" tool which doesn't require any wire, or anything like that.
At the same time I am following the thread "CyanogenMod 10.1 Jellybean 4.2.2 - KANG" and I see that the modded 4.1.2 (made to look like 4.2.2) is in the work but there are "still" major updates coming out quite regularly. Basically, it is a work in progress.
Note: this is by no means a complain: these modded roms are awesome and the work of the devs is amazing: I am just stating matter-of-factdly that the rom is not "ready" yet.
So I came with two questions:
1) Why would I pick the Revolutionary tool (as suggested on the CM pages) vs the JuopunutBear trick?
2) Which ROM to pick? I definitely would like JB. I don't care for Sense (at all). 4.2.2 would be preferable but I understand it does not exist. My Sensation is my "primary" phone, so I need "everything" to work: bluetooth, reasonable battery life, camera, panorama, video ...
Why would I pick a modded vs "stock" CM10? And anyone has a clue of how "stable" is the nightly CM10 for the Sensation?
Do you have any suggestion?
Thanks!

yankeeDDL said:
Hi everyone,
I got tired of waiting for any info regarding "official" JB on the Sensation.
In the family we have a Nexus4 and I am quite impressed with stock JB, so I decided to go for it on my Sensation.
I have unlocked the bootloaded but I haven't gained S-OFF yet.
I was about to go with the JuopunutBear trick but I am still not sure about which rom to flash, so I started looking ...
I went to CyanogenMod website and I see that there are nightlies available of CM10 for the Sensation. Looking at the guide on how to install CM on the phone, there are references to the "Revolutionary" tool which doesn't require any wire, or anything like that.
At the same time I am following the thread "CyanogenMod 10.1 Jellybean 4.2.2 - KANG" and I see that the modded 4.1.2 (made to look like 4.2.2) is in the work but there are "still" major updates coming out quite regularly. Basically, it is a work in progress.
Note: this is by no means a complain: these modded roms are awesome and the work of the devs is amazing: I am just stating matter-of-factdly that the rom is not "ready" yet.
So I came with two questions:
1) Why would I pick the Revolutionary tool (as suggested on the CM pages) vs the JuopunutBear trick?
2) Which ROM to pick? I definitely would like JB. I don't care for Sense (at all). 4.2.2 would be preferable but I understand it does not exist. My Sensation is my "primary" phone, so I need "everything" to work: bluetooth, reasonable battery life, camera, panorama, video ...
Why would I pick a modded vs "stock" CM10? And anyone has a clue of how "stable" is the nightly CM10 for the Sensation?
Do you have any suggestion?
Thanks!
Click to expand...
Click to collapse
Number 1:
The S-OFF tool you use depends on your stock firmware/HBOOT.
If you want to use Revolutionary, which is by far easier. Then you must have Gingerbread (Android 2.3) / HBOOT 1.17.0006 to 1.18.0000.
If you have ICS (Android 4.0.3/4.0.4) and a HBOOT above 1.18.0000 then JuopunutBear is the path to follow.
Number 2:
4.2.2 does exist. (Branch: android-4.2.2_r1)
The CM10.1 (4.2.2) Kangs are brilliant and basically fully functional minus a few bugs here and there (LPA and video glitches seem to be the main bugs). The devs are fantastic at fixing and generally updating the device to make it run smoothly. The CM10 nightlies (4.1.X) work great if you want to use them and are fully functional as far as I can tell. (I've been using them for a few days now.)
Modded/kang is basically an enhanced version with more modules, optimization and bloat removal (CM10 has almost none, depending on how you see some apps). Most kangs come with a custom over-clocked kernel and several kernel fixes and governors which I personally prefer.
The choice between Cyanogen's nightlies and a kang is up to you. I generally download a kang ROM if I see something I like such as the kernels (and their governors) or their module support (NTFS/CIFS/USB-OTG). However kangs are generally a little more prone to bugs as the developer kangs features and then fixes them to work properly. If you see something in the ROM you want or need, then you should download it.
CM10 Nightlies are good if you want light-weight, out of the box stock android without sense. Battery life is good in general with CM10/CM10.1.
Since you're starting off, I suggest you try Albinoman887's CM10.1 (4.2.2) ROM. (http://forum.xda-developers.com/showthread.php?t=2115520)
If you just want simple "It works!", try CM10 Nightlies, or CM9 Stable.

Revolutionary tool is used to root and gain s-off if you're coming from a gingerbread Rom. The hboot is easily hacked. The ics hboot is more difficult, hence the need for the wire trick.
Go with CM10. As far as I know, its pretty stable. Strictly speaking, all cm roms are modded, the nightly versions tend to be more experimental and almost a beta stage. CM10.1 is probably less stable.

Thank you both for your suggestions: I didn't know about the "limitations" of the Revolutionary tool: I am on ICS and I think you guys saved me a whole bunch of time
I'll give CM10 a try then: i I don't like it, I'll try something else.
One last question, if I might: what's with the GApps?
Certain roms include them, other have a separate installer ... Wouldn't I be able to install any app via the play store anyway?
Thanks again, I really aprpeciate teh help.

yankeeDDL said:
Thank you both for your suggestions: I didn't know about the "limitations" of the Revolutionary tool: I am on ICS and I think you guys saved me a whole bunch of time
I'll give CM10 a try then: i I don't like it, I'll try something else.
One last question, if I might: what's with the GApps?
Certain roms include them, other have a separate installer ... Wouldn't I be able to install any app via the play store anyway?
Thanks again, I really aprpeciate teh help.
Click to expand...
Click to collapse
GApps includes the Google Play Store and other Google Apps. CyanogenMod was asked not to include Google Apps. I'm not quite sure why other developers do the same, but it's their choice and I'm sure they have a reason.

DennisBold said:
GApps includes the Google Play Store and other Google Apps. CyanogenMod was asked not to include Google Apps. I'm not quite sure why other developers do the same, but it's their choice and I'm sure they have a reason.
Click to expand...
Click to collapse
This is correct. When you flash a cm Rom, you need to flash gapps too, which includes gmail, play store, and othmp Google related apps like g+ and Google search.

Ok, but I do see several versions of the Gapps (a search on XdaDev shows several hits) and most of them look to be phone-specific, which makes little sense to me.
Shouldn't there be a "generic" Gapps (ok, maybe a different one per ICS, one for JB ... )?

Usually compatible gapps will be posted in the CM thread along with the rom itself.

Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium

james1196 said:
Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
There's no garauntee it will work. Fastboot can fail writing the boot image while S-ON. It's why 4EXT has SmartFlash.
Install 4EXT if you want to use HTCDev, and enable SmartFlash.

james1196 said:
Hey guys, i have an Incredible S. My mate is running a Sensation XE. I have my phone completely modded (S-OFF, Blackrose Hboot etc). My mate wants to root his.
If i just Unlock the bootloader via HTC Dev. Flash a custom recovery using the fastboot etc files from the ones i used. Can i just flash the ROM and use the command fastboot flash boot boot.IMG? Thanks
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.

icanttinkofaname said:
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.
Click to expand...
Click to collapse
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium

james1196 said:
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Please correct me if I'm wrong.
Flash your boot image, your Incredible S boot image on his Sensation?
Kernels don't work like that.
Use JuopunutBear and the wire trick to S-OFF. It's less complicated, and doesn't require HTCDev unlock anymore (there's a guide here on xda somewhere).

icanttinkofaname said:
DON'T for the love of god flash the hboot you use for your incredible S on his sensation! You'll hard brick his phone! use the sensation versions. If he's still on gingerbread, the the revolutionary tool to unlock the bootloader and gain s-off in one.
Click to expand...
Click to collapse
DennisBold said:
Please correct me if I'm wrong.
Flash your boot image, your Incredible S boot image on his Sensation?
Kernels don't work like that.
Use JuopunutBear and the wire trick to S-OFF. It's less complicated, and doesn't require HTCDev unlock anymore (there's a guide here on xda somewhere).
Click to expand...
Click to collapse
both of you are confused i think
(he is talking about boot.img not bootloader )
he meant that after flashing a ROM for sensation XE he will flash the boot.img of the same rom
which is perfectly fine and also correct way of doing as he has unlocked bootloader
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
james1196 said:
Okay. I wanna flash the boot.IMG on mine before s-off I had to do it manually. For me I had to downgrade.
He's on latest ICS
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
you can flash the ROM for the sensation XE using custom recovery
then yes ..you need to flash boot.img of the same rom from fastboot
then its a perfect flash
now the same flashing boot.img process (in case of HTCDEV unlocked bootloader ) has been automated in 4EXT recovery ..via an option called "smartflash"
so
you can use that recovery ..go to tools section and enable smartflash
then flash the ROM (and dont reboot from the ROM flash itself if an option like that is given after flashing the ROM)
come back to recovery ..then reboot from recovery
this will take care of manually flashing the boot.img
---------- Post added at 04:40 PM ---------- Previous post was at 04:24 PM ----------
DennisBold said:
There's no garauntee it will work. Fastboot can fail writing the boot image while S-ON. It's why 4EXT has SmartFlash.
Install 4EXT if you want to use HTCDev, and enable SmartFlash.
Click to expand...
Click to collapse
I think you kinda said it reverse way
if the person did HTCDEV then fastboot flash of boot.img of a particular rom before or after flashing the ROM can never fail (unless the rom has multiple kernel options and the person fastboot flashed one kernel's boot.img while he chose another kernel when flashing the ROM)
there are multiple instances when smartflash (which actually does the same fastboot flash of boot.img but its automated in recovery ) failed (happens always when moved from GB to ICS/JB , also due to user choosing to reboot from ROM flash (couple of ROMS give this reboot option after rom flash happened ) itself which should not be done ..they should manually come back to recovery then do the reboot )

ganeshp said:
both of you are confused i think
(he is talking about boot.img not bootloader )
he meant that after flashing a ROM for sensation XE he will flash the boot.img of the same rom
which is perfectly fine and also correct way of doing as he has unlocked bootloader
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
you can flash the ROM for the sensation XE using custom recovery
then yes ..you need to flash boot.img of the same rom from fastboot
then its a perfect flash
now the same flashing boot.img process (in case of HTCDEV unlocked bootloader ) has been automated in 4EXT recovery ..via an option called "smartflash"
so
you can use that recovery ..go to tools section and enable smartflash
then flash the ROM (and dont reboot from the ROM flash itself if an option like that is given after flashing the ROM)
come back to recovery ..then reboot from recovery
this will take care of manually flashing the boot.img
---------- Post added at 04:40 PM ---------- Previous post was at 04:24 PM ----------
I think you kinda said it reverse way
if the person did HTCDEV then fastboot flash of boot.img of a particular rom before or after flashing the ROM can never fail (unless the rom has multiple kernel options and the person fastboot flashed one kernel's boot.img while he chose another kernel when flashing the ROM)
there are multiple instances when smartflash (which actually does the same fastboot flash of boot.img but its automated in recovery ) failed (happens always when moved from GB to ICS/JB , also due to user choosing to reboot from ROM flash (couple of ROMS give this reboot option after rom flash happened ) itself which should not be done ..they should manually come back to recovery then do the reboot )
Click to expand...
Click to collapse
Thanks for your time. Yes that's what I meant. Smartflash doesn't work on my device so I wasn't sure.
Sent from my HTC Incredible S using xda premium

[Q] Phone Noob Needs a Hand! :)

Hello everyone,
I have used you guys in the past for other devices but never needed serious help, so here I am stuck in a looping hell
I have an HTC One X that I am trying to root and install the TWRP (I want to have an android that is factory set without the carrier info and bloatware ect)
The utility I am using is the HTC One X (Tegra 3/International) AIO Kit By Hasoon2000 v2.5. Here is my main issue:
I have successfully navigated all the steps to root the phone (Steps 1-5) and now when I boot into the bootloader I see the following,
***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
nov 26 2012,18:37:14:-1
Now from here it was my understanding that under "next, flash a recovery" I would simply pick "TWRP" and then click "flash recovery". This seems to work as the green bar in the top right loads briefly. After that I am at a loss. If I go to "bootloader" then go to "recovery" like the instructions say the phone just restarts and I see the Rogers splash screen again...
If it helps, when I try to flash the recovery using the "clockwordmod" it gives me an error "cannot load recoveries/cwm.img"
So to make this easier all I want is my phone to have nothing to do with the carrier on it, all traces of that wiped off at the single file level if possible.
Any help would be greatly appreciated as I have been at this for almost 6 hours straight

The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium

You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
31ken31 said:
The phone is boot looping because you don't have a tegra3 international one x. You have the evita (one xl). Stop what your doing i will post you a link with correct software in a minute.
Read this and then try again.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ninja!
Sent from my Evita

timmaaa said:
You're using the wrong toolkit, the Tegra 3/International is the Endeavor. You have the Evita, which is why it says Evita in your bootloader. You can flash TWRP 2.6 by following the below steps:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash a custom ROM. You've been looking in the wrong forum, that's how your ended up with the toolkit for the wrong device. So always stay in this forum (the one you've posted in), and only ever download ROMs from here for Sense based ROMs or here for aosp ROMs. Don't ever download from a different forum or a different site. That leads to bricked phones.
Oh, and next time, do some more reading before you attempt to alter your phone, you're lucky you didn't brick it. It pays to spend 12 hours reading before trying anything, rather than spending 6 hours trying to fix a mistake because you didn't have the necessary understanding of what you were doing in the first place.
Sent from my Evita
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Ninja!
Sent from my Evita
Click to expand...
Click to collapse
you guys are amazing.... im going to try this now... I hope its not too late because I just noticed that I have no network connection to the provider and no signal I will update as soon as im done

WOW its working.... I cant believe its that easy lol....
On a side note I am in the screen that has install/wipe/backup ect.... so I am kinda lost on what to do from here. When I go to install it has a folder view of the internal phone. Is there something else I need to do to have it boot normally?

If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita

timmaaa said:
If you want to keep the stock ROM but have root, you'll need to download a superuser zip and flash that using the install menu in recovery. Wipe cache and dalvik cache afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Do I need to download superuser.zip from somewhere special or does it matter?
As an update when I try to open up SuperSU it says "The SU binary needs to be updated. Continue?" I select continue and it gives me two choices, either "normal" or twrp/cwm"
I clicked twrp/cwm and it just restarts my phone to the recovery mode and I don't know where to go from there.
(I hate asking so many questions, is there a how-to for the recovery that I just installed? I am hunting around and cant find much)
UPDATE: I have successfully installed super user and everything is good to go, the only thing im still struggling with is the superuser.zip to set the phone to factory settings and get rid of all the providers bloatware/splashscreen ect

Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita

inisings very
timmaaa said:
Ok, so you've already got a ROM on there with superuser? You can just try the normal method of updating instead of recovery method.
Sent from my Evita
Click to expand...
Click to collapse
I have the TWRP Recovery installed and also now have on my phone SuperSU installed, the only thing now is to figure out where I download a ROM to wipe out the cell providers bloatware and splash screens ect, I just want an "android" phone with nothing else on it lol

If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita

timmaaa said:
If you want to keep the stock ROM, you can use an app called Titanium Backup to remove bloatware. Or you can go to either of the development sections I listed before to find a ROM you think might suit you.
Sent from my Evita
Click to expand...
Click to collapse
Yea I bought awhile ago titanium backup pro so I will use that for the bloatware, and as for the ROMS that you listed you mentioned Sense based ROMs or aosp ROMs... what is the difference? Is there one I should use over the other?

It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita

timmaaa said:
It really comes down to personal choice. Sense ROMs are what is installed on the phone when you buy it, they contain the HTC Sense UI.
Aosp ROMs are pure android, if you've ever seen a Nexus phone, that's essentially what it looks like. Aosp ROMs are generally a bit snappier.
There are some really good ROMs in both categories. The devs for our device do an outstanding job. I'm fond of both types of ROM. But, right now I'm using MagioRom, I've always disliked Sense ROMs but this one is Sense 5 and it looks a lot better than previous Sense versions, and is nice and smooth with great battery life.
Sent from my Evita
Click to expand...
Click to collapse
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)

jlambe7 said:
very interesting... I am a huge minimalistic fan... greys and whites are nice too... I appreciate all the help you have given me and I told my buddies who are jumping on the android bandwagon to come to this site...
is there anything special I need to do to install the ROMs? I assume there will be a guide in those links (at work cant view them yet)
Click to expand...
Click to collapse
If you like minimalistic, then aosp is probably the way to go for you. If your buddies are gonna get into modding their phones, I have some golden advice: read, read, read, and read some more before attempting anything. Modding is not hard if you know what you're doing, but it it's very easy to turn your phone into a paperweight if you rush in. Also, only ever get information and software from XDA, other sites don't properly distinguish between our model (HTC One XL/Evita) and the HTC One X (Endeavor).
In terms of installing, it's pretty simple:
1: Make a backup of your current setup using the backup function in recovery. That way if something goes wrong, you can restore it and have a working OS.
2: Perform a full wipe (cache/dalvik/factory reset/system).
3: Install the ROM using the install function. Aosp ROMs also require you to install a gapps package specific to the Android version of the ROM (4.1/4.2). Sense ROMs don't require this step.
4. You are s-on (security on) so you need to flash the boot.img for each ROM manually. Extract the boot.img from the ROM zip and copy it into your fastboot folder on your pc. After you've flashed the ROM and/or gapps, reboot to bootloader and connect your phone, make sure it says fastboot on your phone screen. Then you can issue the following command:
Code:
fastboot flash boot boot.img
Now you can reboot your phone into the ROM.
Sent from my Evita

[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