Database Info

Please Help!

Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?

Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Someone more knowledgeable than myself can give you step by step instructions to get you out of this pinch. But in the mean time read the link I posted about flashing with s on. It will help in the future. Best wishes not to worry I'm sure you can fix this.
Sent from my HTC Sensation using xda premium

daz1uk said:
Ok,
So I've used roms on my hd2 and one x, so I thought this would be simple on a friends sensation, oh how wrong was I.
I have unlocked the sensation via htcdev, installed clockworkmod and installed pyramids jellybean rom.
Now I have all sorts of issues, the rom boots then drops somehow straight to clockworkmod. I can't mount the sd card within clockworkmod to try a different rom and the phone is now useless, doh.
How can I fix this please guys?
Click to expand...
Click to collapse
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.

realsis said:
Did you update the firmware? Are you s off or s on? If your s on you must flash boot image. Download 4 ext recovery, enable smart flash in 4ext. This way you can flash boot image. Please read flashing roms with s on. Also for that rom the firmware must also be upgraded. Let me link you to the guide to flashing roms with s on. This will help http://forum.xda-developers.com/showthread.php?t=1631861
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?

Yes it should
Also some roms require 4ext it's a super easy touch recovery to use. You can download from here or the playstore.
Sent from my HTC Sensation using xda premium

Skipjacks said:
HTC Dev doesn't really unlock it. It only partially unlocks it.
It doesn't s-off the device so you don't have access to the system partition, meaning you can't properly install a custom ROM without a few extra steps. And I don't think you can do it at all with clockworkmod. You need 4EXT Recovery which can flash a ROM with s-on. There's a few extra steps to doing it but it works.
You also have to make sure you have the correct firmware. So if the device was previously on a Gingerbread ROM and you didn't upgrade firmware, it won't work.
Now, the part where it boots then drops back into recovery is weird.
Tell us exactly what steps you did so we can better determine where something went flukely.
I'm CERTAIN it's fixable though.
Click to expand...
Click to collapse
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.

It is universal 3.33 let me get link also 3.32 will work on most ics roms but 3.33 is the newest I'm running jelly bean and use 3.33
http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation using xda premium

daz1uk said:
Thanks for responding.
I've got S-OFF and flashed boot.img with adb.
Will 4EXT allow me to mount the sd card?
Click to expand...
Click to collapse
If you are s-off you shouldn't have to flash boot.img separately. It will do all that with the ROM flash.
Maybe that's what's screwy. Though a borked up ROM still shouldn't affect SD card mounting in recovery...that is really weird. Do you have a card reader that you can use to check the card out in your computer? I'm wondering if somehow you screwed up the card when flashing the ROM. Maybe it wont' mount because the card isn't formatted properly anymore. Stuff like that has happened before.

daz1uk said:
Yeah I'm certain it's fixable too , just not sure how, lol. I'll give 4EXT a shot. I have no idea how or why it drops straight to clockworkmod either, I would expect it to reboot to clockworkmod if anything, but it just kind of switches from the rom straight to it, very odd.
If you could point me to a firmware I might need I would be very grateful.
Click to expand...
Click to collapse
Hi,
What does your bootloader say?
hboot etc.

Yes if your s off you simply flash from recovery without boot img. But do update your firmware.
Sent from my HTC Sensation using xda premium

malybru said:
Hi,
What does your bootloader say?
hboot etc.
Click to expand...
Click to collapse
Bootloader says:
S-ON

Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.

daz1uk said:
Ok, so I think I need to update the firmware?
I've installed EXT4, still cant mount sd, so can't revert to another rom.
Click to expand...
Click to collapse
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?

malybru said:
Hi,
If you are s-on,you cannot update your firmware.
What is your hboot?
Click to expand...
Click to collapse
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
Click to expand...
Click to collapse
Hi,
It is a pity you went to HTC to unlock your phone.
I wonder if you can still s-off using revolutionary.
You are going to need to run a RUU,and hopefully get a working phone again.
Try and find a RUU HERE that matches your area and carrier.

daz1uk said:
hboot 1.18.0000
Unlocked
S-ON
As far as I was aware S-ON just prevented the boot.img from being written via recovery, which can be done with adb. So the only reasons for these issues must be firmware version right?
Click to expand...
Click to collapse
Yup. If you have the 1.18 hboot you have Gingerbread firmware, which won't support Jellybean or ICS.
The good news is that you can flash a gingerbread rom and get the phone back to a working state right away if you need to get the phone back to the owner.
The RUU to restore is pretty simple. Then Revolutionary s-off proceedure is also extremely painless.
Reverting back to stock and starting over to s-off shouldn't take more than 15 minutes if you do it right. Then flashing the ICS/GB firmware (3.32 or 3.33) takes 3 minutes. Then the new rom takes 3 more minutes.
Just make sure you RUU to gingerbread and not to ICS. The ICS Hboots are harder to s-off. It's worth adding the extra step to flash the ICS/JB firmware later.

This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Hi,
Are you Sensation,or Sensation XE?

daz1uk said:
This is driving me nuts, tried 2 ruu's, both failed, if it was my phone it would be out the window!
Click to expand...
Click to collapse
Doh, my fault forgot to re-lock it, update is installing as I type, phew!
Sent from my HTC One X using Tapatalk 2

Most Roms Boot Loop - How to correct?

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.

[Q] Upgrade HBOOT - Roger001 CID

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?

How to obtain s-off for One S(S4) Hboot 2.15

I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?

S1pk3 said:
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
Click to expand...
Click to collapse
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.

Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app

S1pk3 said:
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah. It is just recommended that you are s-off.
As the guy said before you need to flash boot.img (the kernel) afterwards.
Sent from my One S using xda app-developers app

Will give it a try. Thanks.
Sent from my HTC One S using xda app-developers app

Stuck while flashing firmware in htc one s
I got stuck while installing htc one s with maximus hd..
http://forum.xda-developers.com/showthread.php?t=2445392&highlight=sense+5
I did till fastboot flash recovery TWRP2.6.1.0.img ...but aftr fast boot reboot it dint take memory...without that i cant copy ROM to memory...i did unlock bootloader not s off.... i got an error99 while flashing firmware.. icant on the device now....please help me...

tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?

sylvantino said:
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
Click to expand...
Click to collapse
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.

Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.

sylvantino said:
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
Click to expand...
Click to collapse
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.

tivofool said:
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
Click to expand...
Click to collapse
thanks for the information. i read through magiorom thread. trying to download now.seems a flaky webhost

tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
Hi would moonshine work for hboot 2.16 ?

cyberusman said:
Hi would moonshine work for hboot 2.16 ?
Click to expand...
Click to collapse
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)

tivofool said:
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
Click to expand...
Click to collapse
Well i have hboot 2.16 and i need to s-off i get this error when trying to flash the ruu its error 99 unknown fail i get it twice

tivofool said:
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Click to expand...
Click to collapse
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.

santo_2k said:
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
Click to expand...
Click to collapse
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app

rolo143 said:
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I tried Maximus with CWM, did i using sideload and them flash the boot.img file. but it was a disaster as my device didn't connect to wifi and had some call drops then I tried flashing twrp and then sideloaded magicrom 4.0 and flas boot.img, it looks lot better now but only issue right now is my phone keeps on rebooting and am still waiting for a stable rom to be released.

I read MagioRom comments and they say with that ROM phone reboots a lot. So I think the only way is with MaximusHD. The WiFi problem I think it can be fixed. I don't know about the call drops, but many have this ROM as daily use so I guess it's ok. I will try S-off with moonshine method, then try install Maximus. Hope my phone survives.
Sent from my One S using xda app-developers app

Can't S-Off for the life of me

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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