Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
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
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,
Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment
stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita
timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.
Maybe he meant cm10.2 and it was a typo?
Sent from my Evita
timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse
With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app
Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita
stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.
stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.
Q&A for [s-off] moonshine s-off for ville_c2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [s-off] moonshine s-off for ville_c2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello everyone.
I tried using Moonshine to S-OFF my HTC One S (villec2), which didn’t quite go as intended and now I’m stuck in a boot loop.
I downloaded Moonshine from the Moonshine website, under HTC One S – S3 model (ville_c2), first download for ROM version 3.19.401.101 (I got that version number from Software information somewhere in Settings). I then made sure that the phone had Fast boot disabled under power options, turned off the screen lock, connected the phone to the desktop (running Ubuntu 14.10) via the USB cable, and did sudo ./distiller. Moonshine did its magic for a few minutes and, in the end, the phone was powered off. However, when I powered it on, it got stuck in a boot loop.
Now, to solve this, I rebooted into recovery mode (I’ve got something that says CWM-based Recovery v5.5.0.4, not quite sure where I got that) and tried restoring the backup I had previously made and/or wiping caches, none of which seemed to help.
So here’s where I am now: I can boot into bootloader just fine. The bootloader says moonshine S-OFF on top. Normal boot is stuck in a boot loop; it shows the regular splash screen for a few seconds, then a window entitled Android is upgrading… and a spinning progress thingy along with Optimizing app 1 of 24. for a second, then Starting apps. for a few more seconds, then the screen just turns off and the loop begins anew. Occasionally I can see, for a brief moment, an error message right at the end; I can’t quite discern what it says, but it is about a crash of something with gapps in its name.
During the boot loop, I can connect to the phone using ADB (and by that I mean that I can access the shell with adb shell or reboot into bootloader or recovery with adb reboot bootloader or adb reboot recovery). Oddly enough, when I try to power down, the phone doesn’t power down but reboots into recovery instead. I tried powering it down by: holding the power button for a really long time (this, however, just restarts the boot loop); FASTBOOT → POWER DOWN from the bootloader; adb reboot -p; adb shell → reboot -p.
So, what do I do now? (I apologize if I made some obvious mistake with the procedure described above, or with making this post…)
EDIT: I also forgot to mention that the Moonshine directory seems to contain a file called boot_backup.img; can it help me with anything?
i have a problem with s-on. this app solved.
thanks for s-off
Hi, i want to thank all the people involved into moonshine's s-off solution for villec2. I've run it on 64-bit Debian Wheezy. It worked perfect. Finally my One S is free .
I can't thank you on solution thread because i have not enough posts to post anywhere.
The CID for my One S was ORANGB10. It was bought in ORANGE PL.
Thanks again.
moonshine on stock ICS
Moonshine on stock ICS?
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Moonshine on stock ICS 4.0.4?
moonshine on stock ICS
Moonshine on stock ICS 4.0.4?
Aleksic82 said:
Moonshine on stock ICS 4.0.4?
Click to expand...
Click to collapse
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!
JavierG123 said:
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!
Click to expand...
Click to collapse
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...
Rapier said:
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...
Click to expand...
Click to collapse
i have 4.1.1. 3.20.518.102 CL175688 release-keys. can i use rumrunner?
moonshine on stock ICS
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Search a RUU for your phone. maybe that work
moonshine on stock ICS
Yes i m, flash RUU and after that, i try to unlock bootloader, but i can't , many time i try... After that, in software update find last update, and downloading, every ok, but can't install, variant system version-raport. Any solution?
Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Here is the thread for Ville S4 dunno anything about C2 and I won't recommend you to flash or use any procedure from here unless it's stated that works for C2. You might risk bricking your device otherwise
Sent from nowhere over the air...
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...
Rapier said:
I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...
Click to expand...
Click to collapse
Thanks man.
Flash kernel after RUU exe ICS update? I can't OTA install, phone its find, download but cat't, verifact- variant system version, can't install. From recovery, recovery error flash zip, cant find update, i think this problem caused s-on.
Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
1-. if you want to install another RUU different at you CID you need be a S-OFF and SuperCID.
2-. if you want to install .zip rom flashed from recovery you DONT need be a S-OFF, but, after flash a rom you need flash boot.mg from fastboot.
3-.The problem with unlock boot loader its very strange, i relock and unlock boot loader a lot of time and no problems.
Hey guys
I sincerely apologize in advance if this is wrong thread to post such question in. Please be so kind to redirect me to the right thread, I just got registered
Here's my problem. Couple of days ago my phone (HTC One S, villec2, S-ON, here's the picture from bootloader http://tinypic.com/r/qo87k6/8) started behaving somewhat out of the order. Every process that was there, everything started throwing out errors with the likes of Google play has stopped working, Music has stopped working, Messages has stopped working, nothing was the same as it was before that. And nothing else like cleaning the phone with some apps from Google Play didn't help. Therefore, I decided to install myself a custom ROM
Phone was already rooted two days after I got it. It was pretty straightforward process really. That was two years ago. I needed root acess to install some app that required root acess, don't ask me which app was this because I don't remember, honestly. It also installed TWRP 2.6.0.0 and SuperSU
I downloaded ROM (this one in particular http://www.android.gs/update-htc-one-s-to-android-5-1-1-lollipop-with-resurrection-remix-5-4-4-custom-rom/), followed instructions, got into TWRP and this is when the turd hit the fan. Instructions said that I need to wipe my phone. I did just that, with one exepction - I wiped everything from my phone. Spare me saying that I'm an idiot, I've got over that fact already
Basically, TWRP said that no OS is installed. Everything was wiped out from internal SD card aswell, including my ROM file that I put on the phone. I tried with mounting USB storage, which got me into the SD card on my PC and I've put ROM file on it again. So I tried flashing the ROM with TWRP but it kept telling me that my device is not supported to install this ROM
So I was stuck in bootloader with option to flash TWRP.img file from fastboot enviroment on PC, nothing more than that
I've tried at least 4 different ROM-s. One got installed on my phone but when I rebooted my device it got stuck on HTC logo screen and kept rebooting (boot loop I think it's called) until I manually got into bootloader with combination of power down+volume down button
So I started looking for solutions. I found out, that there's two different "flavours" of HTC One S. One is ville, the other one is villec2, which I have. I've read all about RUU files that can help me recover my phone but after searching through http://androidruu.com/?developer=VilleC2 I found nothing that can help me. I've downloaded two different RUU's, locked and unlocked bootloader twice, rebooted RUU but none of them was compatible with my phone
I've seen something about OTA manual updates, which I also tried but it didn't do anything. I've tried flashing firmware.zip that I got from OTA update file, flashed boot.img but then the phone got to the point where it should update but it kept showing me red triangle. The only option was, again, to boot it into bootloader and I was back at square one
Then I read something about turning your phone S-OFF with that moonshine software and about installing any RUU I want without complications. So I got one and realized that I can't do anything with it because my phone only boots in bootloader and as far as I understand, you need to run distiller.exe while the device is turned on and it has to be in Android OS. Which is not an option with me, because as I said, I can only boot my phone into bootloader and then boot something else via fastboot commands on my PC
Am I screwed here? I've tried literally every single thing, I've looked over dozens of recovery guides for this phone but none of them worked for me. I heard that I need exactly the same ROM (matching CID and everything) that was previously installed on the device. Thing is that I didn't do any backup of stock ROM before all that fiasco. I've tried this site too http://forum.xda-developers.com/showthread.php?t=2200930 but all links seem dead, because it only shows me some advertisement things and nothing else
I know I got myself in a situation where anyone with a bit more brain than me would use this bricked phone as a paperweight but I'm stubborn enough to try just about everything to revive my device. At this moment it's stuck in bootloop. I can't boot into recovery because it only keeps rebooting over and over and over again. Fastboot recognizes my device if I type fastboot devices into command prompt but that's just about it
So please, if somebody has the slightest idea what am I to do, tell me all about it because I've ran out of ideas and there's nothing more to my knowledge to try at this point. Thanks in advance!