Hello all, here is my situation.
I recently purchased two used HTC One X phones. After a bit of research, I found out that they are actually the international version, the XL or Evita as they also go by. This is not a problem to me. I struggled getting them to take custom ROMs and I was finally able to get Cyanogenmod 10.0 installed. They are working great as is, however I would like to be able to update further, as there are a couple very minor bugs. Whenever I try to install an update through clockwordmod recovery, I always get a bootloader error. The number is spits out is 2.14, which I know is a never version of hboot. So, my question is, should I update my hboot (currently in 1.14.0002) to 2.14 in order to install newer versions of Cyanogenmod? If so, can you please provide detailed step by step instructions, or link me to a forum that does? Thank you.
Other potentially relevant information:
-EVITA PVT SHIP S-ON RL
bootloader unlocked via HTCdev
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
timmaaa said:
Ok, firstly it isn't the hboot you need to update, it's the firmware. It just happens that the firmware contains the hboot, and the hboot version is what's used by the ROM installer to tell whether you've updated or not. First thing you'll need to do is get s-off, that's required for flashing the firmware.
Facepalm S-off
Rumrunner S-off Thread
Once you've done that just head to the How-To Guide For Beginners thread in my signature and follow the directions there to update your firmware.
It might be a good idea to bookmark that thread, and also the Evita FAQ thread. The answer to your question is contained within the FAQ thread, which is actually stickied at the top of the section you've just posted in.
Sent from my Evita
Click to expand...
Click to collapse
Okay, thanks. Yeah I'm aware you can't get boot without a firmware update. Will 2.14 allow me to update to cyanogenmod 11?
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
timmaaa said:
Yes it will but getting that firmware requires you to run an RUU, which also requires s-off, and is a lot harder than just flashing the firmware package.
Sent from my Evita
Click to expand...
Click to collapse
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
asilaydyingdl said:
Major problems. I now have s-off but my phone refuses to boot. It was in a boot loop, tried flashing boot.img again and now it tries to start then fails, black screen until I how the volume and power button to get back into bootloader. Any suggestions on that?
Click to expand...
Click to collapse
Flash a ROM, not really a major problem.
Sent from my Evita
timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Tried it, still fails. Installed the ROM, gapps, and flashboot flash boot boot.img
timmaaa said:
Flash a ROM, not really a major problem.
Sent from my Evita
Click to expand...
Click to collapse
Flashed the right boot.img (somehow had the wrong one) now back in boot loop again. Any ideas? I did have to change my CID because I did not turn on debugging for ADB. Would that have something to do with it?
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
timmaaa said:
What are your bootloader details now? What did you change your CID to? And what did that have to do with debugging? What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT 1.14.0002
Flashed Cyanogenmod 10.0.0. I was unable to use the last command successfully on facepalm's tutorial without allow ADB in android debugging.
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
Ummm... how do I transfer the new files to my phone if I can't get it to boot in the first place? I will need to transfer the files for the new ROM.
timmaaa said:
Ok, but what does changing your CID have to do with that? Update your recovery to the latest version and flash a more recent ROM. You no longer need to flash any boot.img when you have s-off.
Sent from my Evita
Click to expand...
Click to collapse
IM BACK IN!!! Updating the firmware did it! THANKS FOR YOUR HELP!!! KITKAT HERE I COME!
Related
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
jacen72 said:
Hi guys, first time poster - I want to install the following custom rom...
http://forum.xda-developers.com/showthread.php?t=2442946
... and being new to android modding, do not want to brick it by doing something wrong.
I gather i need to set up superCID and then set to s-off - would anyone be able to point me in the right direction on how to do these correctly for a Telstra phone?
My phone is rooted with CWM, from whati gather (it says "ClockworkMod recovery" in recovery mode).
Thanks
Click to expand...
Click to collapse
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
timmaaa said:
You might already have SuperCID, you can use a fastboot command to check. The command is:
Code:
fastboot oem readcid
If it comes back as anything other than 11111111 you can use this method to get SuperCID.
Once you have SuperCID you can use this method to get s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
jacen72 said:
Thanks, i will take a closer look soon. Is it true that for Telstra phones the CID needs to be 22222222, or is 11111111 okay as well?
Click to expand...
Click to collapse
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
timmaaa said:
The 22222222 CID only applies to at&t phones trying to unlock their bootloader via htcdev, this is because at&t stock CID (cws__001) plus 11111111 CID have been blocked at htcdev. For your purposes 11111111 will be fine.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the info - i know i need to superCID as i checked last night and CID was TELST001 (from memory). Will use 11111111.
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
timmaaa said:
No problems, did you use the fastboot command the check your CID? I only ask because there are apps available which claim to display your CID but they show the original CID, not the current one.
Sent from my Evita
Click to expand...
Click to collapse
I tried so many things last night i couldn't tell you exactly what i did, haha! Will try your way and see what it says.
A quick question - in regard to the facepalm link, it says "Download patcher and unzip it in your working directory" - can this be any folder on my phone (eg: Downloads)? I'm also guessing the other file (OneX.zip) goes in the same directory?
No you place the extracted patcher files and the PJ8312000-OneX.zip into your fastboot folder on your pc.
You need to have adb/fastboot and HTC drivers installed on your pc to do the s-off process.
Sent from my Evita
jacen72 said:
I tried so many things last night i couldn't tell you exactly what i did, haha
Click to expand...
Click to collapse
You should keep better track of things you are doing or you will end like NASA on Apollo 1 and not knowing what went wrong.
To repair something you need to know what you did to break it.
Big thanks timmaaa, have upgraded successfully!
twistedddx, you're not wrong - i should have kept an eye on what i was doing. Luckily for me, all went well!
Thanks again.
Glad to see you got it all sorted mate.
Sent from my Evita
Hi guys, since updating Android, i seem to find my service connection (no service) is being lost fairly easily - is there something i need to do in regard to this, or is it just me?!
Cheers
Which ROM are you on?
Sent from my Evita
timmaaa said:
Which ROM are you on?
Sent from my Evita
Click to expand...
Click to collapse
the one from the following link:
http://forum.xda-developers.com/showthread.php?t=2442946
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
timmaaa said:
You either need to update your firmware to 2.15 or just flash the Beastmode kernel.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, when you talk about beastmode, is the following link what you are referring to?
http://forum.xda-developers.com/showthread.php?t=1797251
Also, with firmware 2.15 - i would actually like to keep it as stock as possible, so perhaps the firmware upgrade would be the better option? I have found a link that looks like it goes to the correct download:
http://forum.xda-developers.com/showthread.php?p=45646878 - (see last post)
Would i be right in saying the instructions for updating the kernel would be the same as at the following link:
http://forum.xda-developers.com/showthread.php?t=2423735 - (OPTIONAL: Installing the Firmware)
Thanks again for your help.
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
timmaaa said:
The first link is incorrect, you can find the Beastmode kernel in our development section. The kernel you just install in recovery.
The last link you quoted is where you'll find the 2.15 firmware, and the install instructions see in the first post on that thread (it's a manual install using fastboot).
Sent from my Evita
Click to expand...
Click to collapse
Thanks - looks easy enough. Can i ask what why i would install Beastmode instead of the firmware upgrade? From what i gather, it is to overclock the CPU?
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
timmaaa said:
You can leave the Beastmode settings stock, it's just an easier and safer fix rather than upgrading firmware. You can OC if you wish to of course. There's always a small risk involved with anything that touches your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, maybe i will install beastmode instead then if it will help fix my connection issues. Sorry, but would you be able to point in the direction of where it is in the development section, i cannot seem to find it.
I promise if this works you wont have to hear my noob questions anymore!!
Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!
bobyum said:
Hi all I need help!!!
My HTC OneXL is unlocked bootloader
Android Version ICS
I dont know which firmware I am running (Rogers One X)
PVT SHIP S-ON RL
HBOOT 1.09
I installed TWRP successfully but I can not install roms!
Please help!
Click to expand...
Click to collapse
you have to flash the boot.img of a rom if you are s-on
must also be rooted.
1. plug phone into pc
2. mount sdcard in twrp
3. copy rom to your computer
4. extract boot.img
5. reboot to bootloader (also done in twrp)
6. highlight "fastboot" and press power and the phone should say "Fastboot USB"
7. open a command promt (type cmd into search box on windows7) and cd to your adb/fastboot folder
8. type
Code:
fastboot flash boot boot.img
9. reboot to recovery and install your rom
10. reboot system when done
if you arent rooted, use the toolkit in the development area and root.
What ROM are you trying to install? If it's any recent aosp your current hboot version is the problem. All current aosp ROMs require the 2.14 hboot which you can get by running the 3.18 RUU. S-off is highly recommended, if you run a jb RUU with SuperCID and s-on your phone will brick.
Sent from my Evita
I am trying to get cm10.2. so should my first step right now be getting the 3.18 RUU or getting s-off?
Ok, first, please read the instructions of any ROM you're going to flash, it's stated very clearly in the cm10.2 thread that an update is needed before flashing the ROM. One of the most important rules of XDA is to search before posting, proper searching limits the amount of unnecessary threads.
Get s-off first, if you don't already have SuperCID you will need that in order to get s-off. Use the hex edit method to get SuperCID, then you can get s-off in the Facepalm S-off thread. Your best bet to go through this process is to temporarily flash a Sense ROM, any Sense 4 Android 4.1 ROM should be fine. Once all that's done you can run the 3.18 RUU, then flash TWRP recovery again and flash CM.
Sent from my Evita
S Off dude. Read what @timmaaa said.
Sent from my One X using XDA Premium 4 mobile app
thanks timmaaa!!! I need to head out right now but will try it asap! I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.
got super cid and soff!
ok i got both super cid and soff. so my next step is to flash a sense 4.1 rom correct? any suggestions?
edit: i downloaded RageXL so do i just flash in twrp?
No you don't need to do that, I meant you should try a 4.1 ROM in order to get s-off. If you have SuperCID and s-off now you can go ahead and run the RUU.
Sent from my Evita
bobyum said:
I apologize for not searching before asking but my phone was stuck on ICS and I thought it would be hopeless to install a custom rom.
Click to expand...
Click to collapse
Not sure how you got that notion. Its actually a bit easier to mod older firmware versions, due to the fact that HTC keeps plugging the various exploits with successive (newer) firmware builds.
There is currently no firmware version for this device that would leave you "stuck" not being able to flash custom ROMs.
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Seconded. I've looked for a RUU on and off for the last several months.
808phone said:
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Click to expand...
Click to collapse
What is your CID?
92lucio92 said:
what is your cid?
Click to expand...
Click to collapse
my cid:
TMOBO010
thanks!
808phone said:
my cid:
TMOBO010
thanks!
Click to expand...
Click to collapse
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
92Lucio92 said:
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
Click to expand...
Click to collapse
Thanks! I was told that I needed the same RUU as what I had on the phone or else I could not restore if I didn't have S-OFF.
Are you saying that I can install a _newer_ RUU at any time than what I have?
Thanks,
Aron
Yes, you can always install the same or newer version. To install older you need to be S-off.
Skickat från min One S via Tapatalk
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
808phone said:
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
Click to expand...
Click to collapse
I would look into moonshine s-off first. I've read of some people having problems with firewater.
Moonshine S-Off
You have to be patient with it, but it's completely foolproof. I've used it on two HTC One S models without fail.
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
808phone said:
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
Click to expand...
Click to collapse
It's not spooky at all. Even though it changes the hboot, the hboot is technically still listed as 2.15 and is compatible with any ROM in the dev section (except the ones that require 2.16, of course).
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
808phone said:
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
Click to expand...
Click to collapse
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Brushstroke said:
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Click to expand...
Click to collapse
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
808phone said:
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
Click to expand...
Click to collapse
Hboot version is the version of the bootloader. Radio is the version of the firmware for the equipment in the phone that controls your mobile data/WiFi connection. These usually are upgraded along with a major software update like 3.14.531.11.
Sent from my One S using xda app-developers app
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
OK, never mind. I can't believe it was so easy to find the RUU. Right on HTC's site!
And HTC DOES list the software number:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
OK, I am ready to try S-OFF.
Thanks for the help.
808phone said:
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
Click to expand...
Click to collapse
The software version usually is in the RUU number, actually. The one for yours is:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
It notes that it's for the Ville and not VilleC2, and that it is JB (Jelly Bean), that its for T-Mobile US, then the software number, then the radio version. They're all named pretty much in this order.
Sent from my Nexus 7 using xda app-developers app
Thanks for the help guys but moonshine and firewater s-off didn't work for me.
Moonshine gets stuck with a ton of .............. over and over.
Firewater crashes out of adb shell.
Another user has the same ROM etc... he tried all of the options (except all in one toolkit) and none work.
I thought I saw a manual way of getting s-off but I can't find the link now.