Database Info

Help flashing roms

So I need some help. I'm not new to android or adb or anything, just confused with this. Here's some background info:
HTC One S (Cincinnati Bell)
S4 Variant
Unlocked boot loader
Rooted (on stock ROM)
TWRP installed
Hboot 1.14
SuperCID
Problem: tried installing the latest CM10 and also CM10.1 with no success(endless boot animation, and 10.1 gets stuck on the HTC screen). I read I news to flash a boot.IMG to get it to work since I'm not S-off. Where can I find this boot.IMG that needs to be flashed?
Any help is much appreciated! Couldn't find anything from my searches.

Extract it from the ROM zip
HTC_One_S | Xparent_ICS_Blue_Tapatalk 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel | S-OFF

Pip513 said:
So I need some help. I'm not new to android or adb or anything, just confused with this. Here's some background info:
HTC One S (Cincinnati Bell)
S4 Variant
Unlocked boot loader
Rooted (on stock ROM)
TWRP installed
Hboot 1.14
SuperCID
Problem: tried installing the latest CM10 and also CM10.1 with no success(endless boot animation, and 10.1 gets stuck on the HTC screen). I read I news to flash a boot.IMG to get it to work since I'm not S-off. Where can I find this boot.IMG that needs to be flashed?
Any help is much appreciated! Couldn't find anything from my searches.
Click to expand...
Click to collapse
If you are able to access TWRP recovery, you should be able to mount your SD card and transfer a new rom onto your phone via your computer(download it onto your computer and transfer it using your USB cable), or if you made a nandroid backup from a point in time when your phone was working, that should do the trick. If you really want to flash a custom boot.img, I recommend using this to flash it.

He already had the ROM installed, he just needs to fastboot the boot.img to get it to boot.
HTC_One_S | Xparent_ICS_Blue_Tapatalk 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel | S-OFF

ryanshew said:
Extract it from the ROM zip
Click to expand...
Click to collapse
Yeah, before I went to bed I figured it was was in the ROM. Thank you! I'll have another go at it.
Why is it that the boot.IMG doesn't get flashed properly? Is anyone working on a fix?
Edit: worked perfectly! Thanks guys!

Its because of your hboot. hboot 1.14 and higher dont flash it properly.
Fix for it? Downgrade to a lower hboot, or flash the boot.img from the phone before flashing a new rom with flash image gui, or just live with it.
S-OFF might also remove the need for seperate flash of the boot.img, I havnt bothered looking into it so I dunno...

Right now I'm on CM10, and let's say I want to switch to the 10.1 nightly's. I shouldn't have to flash the boot.IMG for each new nightly since its the same ROM, correct?

Pip513 said:
Right now I'm on CM10, and let's say I want to switch to the 10.1 nightly's. I shouldn't have to flash the boot.IMG for each new nightly since its the same ROM, correct?
Click to expand...
Click to collapse
It depends on which rom you stay with. If you stay on CM10, then you do not have to flash the boot.img everytime you flash a new nightly. But if you go to 10.1, then you will have to flash that boot.img first. If you have S-Off the boot.img will be flashed from TWRP when the rom is flashed, and you wont have to do it from Fastboot. I don't suggest you try to downgrade you Hboot, especially because we have S-Off now. Although some people are finding that they can no longer connect to any signal above Edge/2g after S-Off.

That's why I didn't want to go s-off just yet. I saw some people having trouble with it, and since I've got a different model (Cincinnati Bell version) than the s-off guide has, I decided not to until it was 100% stable. Thanks for the help though guys! As long as I've got to a way to flash roms without too much headache, I'm happy.

[Q] I need help with S-Off/Installing ROMs on hboot 1.14. See my problem?

So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
Did you try fastboot flashing the boot.img?

dbrewer24 said:
Did you try fastboot flashing the boot.img?
Click to expand...
Click to collapse
Yes, I did that before flashing the ROM zip in twrp

dinodustin said:
Yes, I did that before flashing the ROM zip in twrp
Click to expand...
Click to collapse
Have you tried doing it after? I have seen different instructions that say to do it different ways.

I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck

dbrewer24 said:
Have you tried doing it after? I have seen different instructions that say to do it different ways.
Click to expand...
Click to collapse
Like which instructions? I've tried to flash through TWRP, but I've seen other people have problems with flashing through TWRP with hboot 1.14, which includes me. So, I've tried that method and using CMD to fastboot it. Both didn't go so well. I also haven't tried testing other ROMs cos I've tried to flash 2 different ROMs (BB7, Liquid Smooth, JellyBam 4.1.0), but all 3 of them stayed on the boot animation screen and I never got to use my phone. My solution to those not working since I'm not able to flash any ROMs was to Go into Bootloader> Relock Bootloader > Go to Fastboot > & Ran RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
Ryandroid86 said:
I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck
Click to expand...
Click to collapse
I'll try changing my network settings and get back to you on that.
How long would you wait on the Boot Animation screen? Cos I waited for about 5 minutes for it to load and it never loaded all the way.
I've tried the final step +3 times. The last few times I've tried it, it looked successful when I saw that my CMD sent the file and it said "OKAY", so I rebooted into my Bootloader like the very last step Facepalm's S-Off guide had said, but I didn't see what I was looking for ):
I've tried hard reset and flash, no luck. I'll try the old ROM thing.
It's such a hassle to get back to a working ROM, which you all know is phone's stock ROM I've been using, with the RUU exe.

suggestion
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
I have a Tmous too, the only way i got S-off was installing previously all t-mobile updates, ithen was easy getting s-off, but i don't know if that will solve your 4G problem, because i never had that.
(sorry about my english)
charly

Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip

Ice Master Ben said:
Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip
Click to expand...
Click to collapse
The very first time i get 92 an then failed in the second part of "pushing soffbin", when i tried again, i get error 99, but then i read some post about powering off the device, and it worked i get again error 92 and worked fine.

I had the same error and situation, first time error 92 but not after that,keept getting error 99 keept trying with diffrent Roms until I got the 92. I was on the 1.09 hboot the funny part is since I have s off I upgraded to the latest hboot 2.15( thanks to the flashable zips in the theam section) to my surpprize I could not flash viperon that hboot, so I went back to my 1.09 hboot and everything worked really good like always, so my poqint is were still having problems on higher hboots even with s off why?????, the only good thing about s off I have found is thanks to the flashable zips we can upgrade or downgrade the hboot just by flashing it, now its back to the 1.09 hboot

Ice Master Ben said:
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off
Click to expand...
Click to collapse
Related to this, i have S-Off and Hboot 1.09, yet am still having problems flashing the latest daily CM 10.1 roms to by One XL, any suggestions?
I'm getting an immediate FAILED error in TWRP 2.6

Try twrp 2.3.3.0 it's supposed to be the most stable
Sent from my HTC One S using xda app-developers app

Unable to install ROMs after failed ViperRom Install? Possibly now a paperweight.

Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...

Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.

watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.

Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?

Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.

redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14

Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.

exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".

./

Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.

Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app

exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.

Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app

exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,

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.

HTC ONE S4 No Operation System, I PAY FOR HELP

Hello i have big problem with my HOS. I did facotry reset in revcovery and im without any Operation System.
I have no Operation System on my HOS and any ROM on SD. Is any way to help me?
My CID: 02_001
HBOOT: 2.15.0000
Radio 1.11.5005.28
Open DSP v31.1.0.45.0815
S-On
Locked Bootloader beocuse i relock him.
How to find good RUU?? It will help me? I can offer even cash for help

parowka22 said:
Hello i have big problem with my HOS. I did facotry reset in revcovery and im without any Operation System.
I have no Operation System on my HOS and any ROM on SD. Is any way to help me?
My CID: 02_001
HBOOT: 2.15.0000
Radio 1.11.5005.28
Open DSP v31.1.0.45.0815
S-On
Locked Bootloader beocuse i relock him.
How to find good RUU?? It will help me? I can offer even cash for help
Click to expand...
Click to collapse
It was one stop destination for all my RUU needs.
http://bugsylawson.com/files/category/52-ruus/
If RUU din't help.. unlock bootloader, flash custom recovery, mount sd card and transfer ROMs. :good:

I cant flash custom recovery. I flash TWRP 2.5.0 but i need some password wich i dont have, withot is i cant enter to TWRP. I cant flash even CWM 6.0.3.1.
Look. My situation is :
Unlocked bootloader but i can lock it.
S-On
Cant use custom recovery
Cant root
I have no mounted any storage coz i cant do that.
I have no ROM, i have no OS on my phone. My phone is totaly clean, even TWRP doesnt work, cant flash CWM becouse it says
"The filename, directory name, or volume label syntax is incorrect.
C:\Users\Phalanx\Desktop\One_S_All-In-One_Kit_v3.5\data>"
But i do step by step and check every move. My situation is very bad
I have CID 02_001 and i found possible good RUU RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed
Im using All in one Kit. I cant do nothing more than unlock/relock bootloader.
If anyone help me i can pay for help, that is not the problem.

If you have stock recovery still then click recovery and that USUALLY will get external storage working. If not, then click "clear storage" Then try flashing TWRP. I would only recommend version 2.3.3.0, however, least buggy. Don't bother with CWM.
Sent from my One S using xda premium

parowka22 said:
I cant flash custom recovery. I flash TWRP 2.5.0 but i need some password wich i dont have, withot is i cant enter to TWRP. I cant flash even CWM 6.0.3.1.
Look. My situation is :
Unlocked bootloader but i can lock it.
S-On
Cant use custom recovery
Cant root
I have no mounted any storage coz i cant do that.
I have no ROM, i have no OS on my phone. My phone is totally clean, even TWRP doesn't work, can't flash CWM because it says
"The filename, directory name, or volume label syntax is incorrect.
C:\Users\Phalanx\Desktop\One_S_All-In-One_Kit_v3.5\data>"
But i do step by step and check every move. My situation is very bad
I have CID 02_001 and i found possible good RUU RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed
I'm using All in one Kit. I can't do nothing more than unlock/re-lock bootloader.
If anyone help me i can pay for help, that is not the problem.
Click to expand...
Click to collapse
You have to download and put cwm.into the correct folder before you flash it.
I find fastboot commands simpler and easier, but up to you.
And that ruu is way to old...won't run with your current firmware.
Here's a video, just replace fastboot flash boot boot.img with fastboot flash recovery recovery.img
http://www.youtube.com/watch?v=5xVl2dBTnmI&feature=youtube_gdata_player
hTConeS | SoFF | CharmAnDroiD | eleMeNtal
*INveRTeD sENsE 5 ROM+ThEmE+TwEAkS*
*CharmAnDroiD 3.0 FULL ROM UPDATE*

ryanshew said:
You have to download and put cwm.into the correct folder before you flash it.
I find fastboot commands simpler and easier, but up to you.
And that ruu is way to old...won't run with your current firmware.
Here's a video, just replace fastboot flash boot boot.img with fastboot flash recovery recovery.img
http://www.youtube.com/watch?v=5xVl2dBTnmI&feature=youtube_gdata_player
hTConeS | SoFF | CharmAnDroiD | eleMeNtal
*INveRTeD sENsE 5 ROM+ThEmE+TwEAkS*
*CharmAnDroiD 3.0 FULL ROM UPDATE*
Click to expand...
Click to collapse
But my phone is out of any firmware. There is no any android inside phone. He is totaly clean.
If my RUU is too old so where can i find newer one? How can i keep my phone in this case? Look, i dont have any backup, i cant do superCID and S-off wich help me to instal any RUU. And as i mention in name of topic, i can PAY for help in $. All i need is to know that there is solution for me, if someone tell me step by step how to bring my phone to live i will pay, there is no problem with money.
For me problem is that i really love this phone and i dont want to lost him

parowka22 said:
if someone tell me step by step how to bring my phone to live
Click to expand...
Click to collapse
Just follow what I said, if you have stock recovery then follow my steps. If you don't then you can definitely flash the stock recovery, because you don't need any external storage for it. Just Google "Ville stock recovery" and you'll get it. That will fix the external storage problem and in turn the rest of them.
Sent from my One S using xda premium

SOLVED
Stock Recovery>Then Flash TWRP 2.5.0.0>Mounted SD>ADB Sideload>Instal ROM+Kernel(boot.img)>Rooted
And still S-On but i dont have time to S-Off
Now all is good.

S-Off is easy now though. You might as well, it makes flashing ROMs far easier.
Sent from my One S using xda premium