[Q] Help with hboot update [Solved] - HTC One S

Hi everyone, first of all thanks for any support you may give, I was really hoping to figure this out on my own but I've ended up with 20+ tabs open on the subject and don't seem to be getting anywhere.
So on to issue: Recently fished out my old HTC One S as a friend wants to buy it, however the custom ROM I had installed crashed when using the camera so thought I'd get this all updated for him before he takes it off me, but things have moved on a lot since I was last here, and I'm now stuck getting everything updated.
I currently have hboot 1.13, s-on and root, and my CID is HTC__001
It appears most ROMS now require either hboot 2.15 or 2.16. I incorrectly thought hboot was related to recovery, so I tried to flash latest twrp, but now phone reboots everytime it gets to lock screen, I can still get into fastboot using adb, but I can't access recovery, and I'm now stuck. So any thoughts or input on how to proceed from here would be amazing!
TL:DR:
Currently on Hboot 1.13 with s-on, need to update to 2.15. Phone keeps rebooting, can access fastboot but not recovery. help.
Thanks again, Andrew.
Update: Solved
I resolved my issue by re-locking the bootloader, and installing one of the latest RUUs with hboot 2.15. I could then unlock the bootloader again, flash the latest twrp recovery and get back to installing custom ROMs.

You'll need to flash a recovery with adb. I can't remember if you can do that with S-On, but I don't see why not.
The command is something like: adb flash recovery name-of-recovery.IMG but I don't have my notes with me.
FYI, I always had to run the command twice for it to "stick".
You'll also have to find an older recovery.
Sorry I don't have the actual commands handy, but it shouldn't be too hard to find.
Edit:
Or, you can run the RUU.

Awesome thanks, I just need to find the right recovery and RUU now. I've had a look on Teamwins website and oldest version I can find is 2.1.6, but there is no documentation to say which hboot this supports, however I have a funny feeling I'll need an older version than even that, any ideas where I could find the correct recovery to flash? Thanks again.

Related

CID error after flash generic rom, stuck in boot loader

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.

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?
onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.
http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium
tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.
Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium
heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.
an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

[Q] 1.73.502 ruu question

Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?
To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita
What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.
I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...

Stuck at boot loop???

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] [s-off] moonshine s-off for ville_c2

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!

Categories

Resources