Related
Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol
Hello,
As the title indicates, I am a complete noob when it comes to rooting, flashing, etc. I know the first thing many of the experienced folks here will say is to go research before posting any question, and believe me I have! I found a lot of information that are supposedly for noobs but I am confused because I am unable to see the big picture!
On a very high level I understand that you have to root your device before installing custom ROM. The next level I read about is the detailed steps for each activity such as how unlock bootloader, SuperCID, achieve S-Off, use ADB, etc. What is not clear to me is the order in which these activities are supposed to be done (i.e. big picture). Frankly, I am not sure if there are other activities that a required that I have not come across. I have read the FAQ's and there is a link to what appears to used to be a very good guide but the OP "rage quit a few months back and deleted it all".
Would one of you be so kind to put together map of the activities required?
I am using HTC One X Evita. So ideally this proverbial map should be for the HTC One X Evita. Thanks in advance.
magnity said:
I am using HTC One X Evita. So ideally this proverbial map should be for the HTC One X Evita. Thanks in advance.
Click to expand...
Click to collapse
First even if you know it it still doesn't harm to reconfirm your exact device details by going into boot loader so do that!
once you know you have EVITA now you can follow guides on this forum.
go to http://forum.xda-developers.com/showthread.php?t=1671237 a.ka Redpoints compilation of everything!
1. Install HTC drivers. (ADB and fastboot recommended most toolkits have that option to install them)
2. Unlock Bootloader essentially a code your phone uses when it starts up.
once you have an unlocked bootloader you can install TWRP recovery (CWM is not recommended) and just download a superuser zip file and simply flash it.
3. Get SUPERcid. CID is carrier identifier string,super cid enables you to flash an RUU supplied by other carriers [BUT wait if you are SON and you get SUPERcid and run a JB RUU you will BRICK your device.]
4. So for many reasons you need SOFF which is basically to disable your security flags and to gain access to some restricted partitions,this will also help you upgrade downgrade firmware,change radios and flash ROMS without separately flashing boot.img.
5. Now you can flash ROMS. and RUU as well.
6. For flashing Roms perform factory wipe prior to and after installation you may do dalvik and cache wipe.
All that info is great but it might not apply to this user, if he has the at&t model this is all irrelevant.
@magnity, we need your bootloader details before advising you any further. To get to the bootloader power off your phone, once it's off hold volume down and then power (so you're holding them together), after a few seconds let go of power but keep holding volume down until you reach the white screen with text, this is your bootloader, please post the first five lines.
Sent from my Evita
timmaaa said:
All that info is great but it might not apply to this user, if he has the at&t model this is all irrelevant.
@magnity, we need your bootloader details before advising you any further. To get to the bootloader power off your phone, once it's off hold volume down and then power (so you're holding them together), after a few seconds let go of power but keep holding volume down until you reach the white screen with text, this is your bootloader, please post the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
ya that actually is quite important!
Thanks for the quick reply. Below are the first 5 line:
Code:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
My device is originally from Rogers but I sim unlocked it and I am using in it in Europe on other carries.
Ok, and is your phone the at&t branded model? If so it'll have the at&t logo at the top of the screen instead of the HTC logo.
Sent from my Evita
timmaaa said:
Ok, and is your phone the at&t branded model? If so it'll have the at&t logo at the top of the screen instead of the HTC logo.
Sent from my Evita
Click to expand...
Click to collapse
It has HTC at the top ... I got it from Rogers.
Good news, that makes the whole process a little easier. First step is to install HTC drivers and adb/fastboot. You can get the drivers by installing HTC Sync Manger, just Google search it. Once it's installed on your PC just connect your phone to your PC and the drivers should install automatically. You can get adb/fastboot by searching too, I believe the easiest way is to search for something called minimal adb/fastboot, it's a thread on XDA with full instructions.
Next you need to go to htcdev.com and unlock your bootloader, it's pretty simple as long as you can follow instructions. Once you've unlocked your bootloader you can install a custom recovery, a custom recovery allows you to install custom ROMs, kernels, radios etc. My suggestion for recovery would be TWRP, here's how to install it:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have a custom recovery on your phone. Once you've completed all this post back here.
Sent from my Evita
@timmaaa I am using a Mac so I had to figure out how to enable adb/fastboot on OS X. Also, the link for TWRP was not working because goo.im is down (I think) so I got it of techerrata.com. Although there were more recent versions (latest is 2.6.3.0 for my device), I got the same version you referred me to (2.6.0.0).
Also, the last step in HTCdev is to relock the bootloader. I was not sure if I was supposed to to do that or not but since this whole excerise is to unlock the bootloader, I skiped the last step (I also did a google search to confirm that!).
Anyways, I have run the commands you gave me and my phone seems to work ok
Good work. I'm aware there are more recent versions of TWRP available but I've seen people report bugs on those so 2.6 is the best one.
At this point your next step will be to make a backup of your current stock ROM. Go into the bootloader using the method I described earlier in the thread, once there select recovery and it'll boot into TWRP recovery. Use the volume keys to move the cursor and the power button to select the highlighted option. Here's a tip, instead of moving the cursor down, use volume up and move the cursor up through the options until you reach recovery. There's a good reason for this, sometimes there's a bit of lag and it's really easy to accidentally select factory reset instead of recovery. You don't ever want to do a factory reset from the bootloader as it corrupts your sd card.
Ok, anyway, now that your phone should be successfully booted into TWRP you can select the backup option from the main menu. Once you're in the backup menu you should check the System, Data, and Boot options, then swipe to backup. This makes an image of your current setup, should you ever want to return to it you can restore it pretty easily.
Now that you have your backup you can either root your stock ROM or you can install a custom rooted ROM, which way do you want to go?
Sent from my Evita
I made a backup but the after it was completed TWRP only gave me one option and that is to reboot system. I selected and it said I don't have SuperSU (which I assume stands for Super Super User) and the only option it gave was to "slide to install". I was not sure what that would do so I just shutdown the phone and rebooted and everything look fine. I hope that did not corrupt the backup.
Regarding what option to go from here, I just want to try a new android experience (other than Sense) and I like how Paranoid Android 3 looks and works. But I am not sure how stable it is because people here are saying it works just fine but elsewhere on the net some are having trouble. I would appreciate your input if you've used it. If it is indeed not stable, then I want to try CyanogenMod.
Although I want to install a custom ROM, I would like to know how to root my stock ROM. So I would be appreciate it if you also give those instruction too (or point me to them). To be honest I do not know what the benefits are of rooting the stock ROM.
Thanks you very much for your help so far.
Shutting down the phone won't have corrupted your backup at all, it should be fine. It was asking if you wanted to install Superuser because TWRP had detected that your current ROM (the stock one) isn't rooted. Superuser is the app that grants root access, so if you want to root the stock ROM the best way to do it is to enter recovery and then just hit reboot and it should prompt you again. Unless you want to stay stock but have root access I wouldn't bother with this. You'll have a much better experience on a custom ROM.
Having root is handy, but opposite to what most people assume it isn't the most important part of modifying your phone, the most important parts are having an unlocked bootloader and a custom recovery, which allow you to install custom software (ROMs/kernels). Being rooted really only equates to having access to the root directories on your device, much like having administrative rights on Windows. This is great for modifying system files and installing apps that require root.
Paranoid Android is usually a pretty good ROM. It's stability will differ from device to device and also from build to build. At the moment we don't have a current version for our phone as no devs have picked it up, there are some older builds if you dig back through the Original Android Development section within our forum though. We do have some other great aosp ROMs on offer though, off the top of my head I can think of CodefireX, Beanstalk, Slimbean, Carbon, Illusion, CM. There are more but I can't remember them. Have a look through them, check out their features, and pick one you think you might like, if you end up not liking it you can always flash another. Here are links to our two development sections:
One XL Android Development (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (aosp ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Before you actually install a ROM you might want to get SuperCID and s-off first. Some ROMs have certain requirements, which in turn require s-off, which requires SuperCID, which requires root. So maybe quickly root your stock ROM by entering recovery and hitting reboot, that should initiate the prompt to install Superuser. One you've done that you can get SuperCID by using this method:
http://forum.xda-developers.com/showthread.php?t=2212737
One you have SuperCID you can get s-off by using this method:
http://forum.xda-developers.com/showthread.php?t=2155071
If you have any problems or questions just ask here.
Sent from my Evita
I followed the steps for SuperCID but I wanted to confirm that it worked before progressing into S-Off. So I entered the follwoing:
Code:
fastboot getvar cid
But I don't get "11111111" and instead I get "< waiting for device >" and nothing happens (I waited 20 minutes and nothing) it is almost as adb/fastboot crashes.
I know adb/fastboot works fine because when I enter the following:
Code:
adb devices
I get my device listed. I tried rebooting my device a bunch of times but I still get "< waiting for device >".
I did not go ahead with S-Off yet. Not sure if I am screwed the pooch on this one!
Your input would be appreciated and thanks for everything you have been very helpful
Are you booted into the ROM while giving the "fastboot getvar cid" command? If so that might be your problem, fastboot commands only work while the phone is in bootloader (fastboot mode). So you can use this command to get it to bootloader first:
Code:
adb reboot bootloader
Once it's finished rebooting into the bootloader try giving the command again.
Sent from my Evita
Thanks! I got the right CID.
I followed the step for S-Off and everything seems to have gone smoothly. But when I loaded the bootloader the top lines say:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
Does having the S-ON there means that the method did not work?
Yeah that means you're still s-on. This process can be a little tricky. Do you have usb debugging enabled in developer options in the settings menu? Try again, and if possible copy the text from the command prompt and post it here, it'll make diagnosing the problem easier. If you happen to get error 99 instead of error 92 after flashing the PJ8312000 zip, force a reboot to the bootloader by holding volume down and power together then start again (without the adb reboot bootloader command because you'll already be in the bootloader), you should get the correct error 92 now.
Sent from my Evita
According to the instructions by @beaups for S-Off, I am supposed to get "FAILED (remote: 92 supercid! please flush image again immediately)" after entering
Code:
fastboot flash zip PJ8312000-OneX.zip
but instead I get "FAILED (remote: 99 unknown fail)"
Phone still works fine.
That was it and now I am S-Off! Now, I assume, all that is left is to install another ROM.
Yep, you've completed all the preparation work now. I must say you pretty much did it on your own, many people would have needed their hands held through all that, so well done.
Now all you gotta do is choose a ROM and install it. Once you've decided which one you want to flash have a read of the first couple of posts for any instructions, and read about the last ten pages too, this will make you aware of any possible bugs on the latest builds. Aosp ROMs require you to install the ROM plus a gapps (Google Apps) package. This isn't required for Sense ROMs.
Once you've downloaded the file(s) just copy them to your phone. You can do this by entering TWRP, select mount, then mount usb storage, now your sd card will show up as a removable drive on your PC. Once it's copied over unmount. Go back to the main menu, select wipe then advanced wipe, check cache, dalvik cache, factory reset, and system then swipe to wipe. Go back to the main menu and select install, navigate to the file and select it then swipe to install, repeat with gapps. Then just hit reboot and it should boot up into your new ROM.
Sent from my Evita
hello everyone, android user and my device s-off in the first year I want to do but how to do it without the support of htcdev? Is there a program available? When I unlock my device also has root? Am I going to root sturdy at the same time to s-off? I just want to get rid of device applications that official. 5 4.2.2 installed on my device, this device can sense it possible to root for?
Thank you.
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
You don't need s-off to delete bloatware (pre-installed apps). Just use HTCDev.com to unlock the bootloader. Then install custom recovery, then either flash SU or a rooted ROM to get root.
The process to s-off is simple (see Facepalm method in the Original Android Development subforum). However, it requires SuperCID. Since the CID is protected on Sense 5, you will not be able to SuperCID (and therefore S-off).
But as already mentioned, you don't need S-off to root and delete bloatware.
I'm at a loss and somewhat confused.
I read in one place that I need to s-off to update my radio, but in order to do that I need super-cid.
so I'm trying to change my cid from ROGER001 to 11111111.
Now I'm reading that I can s-off without super-cid? All I'd like to do is update my radio and kernel so my phone stops losing signal and stops rebooting. I should also mention that I already went to htcdev and unlocked my bootloader.
What I see in fastboot:
TAMPERED
UNLOCKED
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Viper Xl 4.2.0(amazing Rom btw)
HTC Sense 5.0
I have tried the script, it failed, manual method, that failed.
manual method gets me this result after I fastboot oem readcid(ok), fastboot oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
FAILED (status read failed (No such file or directory))
I'd like to resolve this as my signal stops, and device reboots randomly.
telaphoneguy said:
Now I'm reading that I can s-off without super-cid?
Click to expand...
Click to collapse
Nope, wherever you read that, its completely incorrect.
It says right in the s-off method instructions, in big bold print that SuperCID is required: http://forum.xda-developers.com/showthread.php?t=2155071
If you are having trouble with s-off, the other solution to random reboots on Sense 5 is to install the Beastmode kernel.
Release the hounds!!
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
Release the hounds!!
Click to expand...
Click to collapse
I actually started to type "as mentioned in a bazillion different places" after my Beastmode statement in the previous reply. But I decided to be nice!
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
telaphoneguy said:
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
Click to expand...
Click to collapse
The x-factor exploit fails since its looking for the AT&T CID. For other CIDs, you need to edit it manually using the hex edit method.
If you have trouble with installing Beastmode, I think some folks have had to install Beastmode 2.0 before installing 3.5.
After many attempts, boot loops beastmode reloaded 3.5 finally took.
So now I need to ask if I need s-off, i've done everything except upgrade my radio.
I'll only update my radio if the antenna drops keeps dropping out.
Well, radio went out, no reboots yet, I'll see what else I can try.
no i want to only rooting device, this video help me ? cause title for htc one."but my device hox"
www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
timmaaa said:
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
Click to expand...
Click to collapse
Tnx so much if i think rooting need to s-off but you say "thats two entirely different" .. then why people use to s-off? for change rom ? and i find this video for root its working for my hox ? or only working htc one.. https://www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02 again tnx. sorry for english
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
some people say me "when using htcdev for unlock your warranty get void" thats true ?
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa said:
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1732980 i searched someone info for s-off "s-off, hboot and radio flash only happens if I need to make" sorry i ask much question cause im noob; then give me root link for sense 4.3.3 and hasoon2000's working for me ?
What are your bootloader details?
Sent from my Evita
Cid: htc_m27; Softwarenumber:4.18.401.2 , radio: .51204.167.31 hboot: 1.72.0000 s-on RL htc one x
You're not even in the right forum, this is the HTC One XL / at&t One X (Evita) forum. You need to ask in the HTC One X forum. They're different phones.
Sent from my Evita
Hi guys,
My sister sent me her HTC One SV aka K2-UL i offered her from expansys on june, it is stuck on Hboot
*** LOCKED***
K2_UL XA SHIP S-ON RL
HBOOT-2.00.0000
eMMC Boot
...
I can go to Fastboot USB ( or AC )
She 's worst than a noob so phone is stock, up to date but non-root non-unlock, still S-ON and so on.
just once phone reboot and stay stuck...
From here i can navigate but after reboot i'm still here.
I tried :
factory reset and recovery (with rom renamed PL80DIAG but would be too easy...)
RUU but RUU asked for bootloader so stuck on "waiting for bootloader"
go to htc dev to unlock bootloader but after flash unlock token ( unlock token check successfully) but : Nothing happens and still writtten ***Locked*** then if I "fastboot oem unlock" it says failed :<remote : loading custom splash failed>
fastboot flash boot.img but nothing works since still S-on and locked bootloader (superCID is out too)
flash custom recovey or even fresh stock recovery but nothing worked for the same reasons...
Do you guys have any idea of something i could do?
Thanks for your answer and forgive my English I'm French
As long as you are ***LOCKED*** you can quiet do nothing.
To use our available RUU you must also be unlocked & S-Off.
Somewhat the same situation
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
I can get into Fastboot as well as bootloader, I CANNOT GET INTO RECOVERY. I have tried to restore with the respective RUU files from the All things HTC ONE SV forum. I have also tried to flash the recovery boot and radio img files through fastboot usb. NONE of this has worked for me. I really enjoyed this phone before I went and made it all FUBR. If there is anyway to get it to boot to any recovery or rom, i will much appreciate it. Thanks for all your help from previous posts as well as any future help I get from information posted here.
Related to your hboot, you should be able to flash any recoveries, but i usually recommend this one.
What command do you use to flash recovery and do you get an output from "fastboot devices"?
Thedc24 said:
I am stuck here:
***Tampered***
***Unlocked***
K2_PLC_CL PVT Ship S-ON RL
HBOOT -1.01.0000
Radio - 1.12.00.0208
OpenDSP - v.7.2.0221.1123
eMMC - boot
Feb 8 2013, 16:29:40:-1
Click to expand...
Click to collapse
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
eduardog131 said:
Oops you already are 4.2.2. I have a system.img and a boot.img that I can make into a rom.zip to flash via the OEM-RUU mode.
Click to expand...
Click to collapse
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Modding.MyMind said:
HBOOT 1.01 is ICS (4.0.x).
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Well then I was right then I was wrong. Sorry. HBOOT versions for the Sensation are stuck in my mind.
Sent from my HTC Sensation
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Thedc24 said:
Thanks a million for the replies. I was able to lead the recovery and get into it (the most progress i have had in a year with this phone). With that being done. When I go into recovery I am unable to mount the internal storage. I am not too sure of the procedures I need to go through to get this thing functional again. I have been tinkering with my S3 for the last few months, but with KNOX on now I am looking to Jump ship completely from both verizon and samsung. Enough rambling, Like I said thanks for the help, any assistance in getting this thing to boot to a ROM would be much appreciated.
BTW
I used the fastboot flash recovery recovery.img
I have tried this before with no success. This time it worked.
I also flased the Radio and Boot img for ICS.
Thanks.
Click to expand...
Click to collapse
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
old.splatterhand said:
He first needs to be S-off, to flash radio & hboot. I have made a 4.1.2 rom for cricket, must be linked in my index thread. Wipe all, flash the rom, flash boot.imgwith fastboot and hope that little baby is booting.
If yes, use moonshine.io or rumrunner.us to get S-off.
Then we will do next steps.
Click to expand...
Click to collapse
Wow! Awsome! This bad boy booted. I was able to flash the rom through recovery. This is much further than I expected to get with this device. Now when I try to go S-Off with either moonshine or rumrunner I get an error saying not able to make adb connection. When I use fastboot devices my device will show up...if i do adb devices nothing...Would love to have S-Off and SU installed. But like I said this is much further than I expected to get so anything further is icing on the cake. Thanks in Advance.
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
old.splatterhand said:
Is Usb-Debugging enabled?
Any output from adb devices? HTC Sync installed (for the drivers)?
Click to expand...
Click to collapse
He can just use the Naked Driver for the adb driver. http://forum.xda-developers.com/showthread.php?t=2263822
Ok I DID have USB debugging enabled. After messing with the drivers and my Windows 8 computer, I have came to the conclusion that it is something with the drivers and their compatibility with Windows 8. Either way moonshine or rumnunner never worked for me in a windows 8 environment. I dual boot ubuntu 12.04 anyway, it saw my device just fine adb and fastboot. I ran moonshine and it went through all the testing stages, but was never able to completely run...so I still have no S-Off. Do I need to update Hboot or anything? Also am I able to load a custom rom on this device with S-ON? I have been looking but I do not see many out for this device at all, which is a shame because I feel as though it is very comparable to my GS3. It would be nice to see a nice AOSP ROM on this device. But all take any updates I can for the device, hopefully it will help with the issue I have will cell reception dropping all the time. Thanks
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
old.splatterhand said:
To answer some of your questions:
- you can't update hboot because you are not stock and not S-off
- there are indeed not much roms to flash, but you could do with S-on (and unlocked bootloader)
- if you would flash the Sense 5/Android 4.2.2 rom, you would have noizy sound, without the firmware files (which you need S-Off to flash)
Another way for getting S-off (which should work with your hboot), is facepalm.
But the part of changing CID to SuperCID is very risky, read carefully and only do, when you are sure you understand, what to do!!!
Click to expand...
Click to collapse
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
eduardog131 said:
If you want I can just skip you to 4.2.2. You don't need to reflash recovery and stuff. I will make a package that will update HBOOT and radios. And system/boot.img.
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea that would be cool. I am assuming I would just flash it through recovery?
Thedc24 said:
Thanks for all the help! I am now SuperCID with S-OFF, Facepalm worked like a charm. Would it be possible to put slimrom on this device? Anyway thanks for all the help, I am going to check out some ROMS..as far as flashing goes, I am assuming how I have my phone now I should be able to flash any rom that is compatible with the device.
---------- Post added at 05:46 PM ---------- Previous post was at 05:24 PM ----------
Yea that would be cool. I am assuming I would just flash it through recovery?
Click to expand...
Click to collapse
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
eduardog131 said:
You're completely S-OFF? The radios and new HBOOT update need to be flashed in RUU mode. Let me get my bearings and you can flash everything. (adb reboot oem-42 or fastboot oem rebootRUU is a way to get to RUU mode.)
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Thedc24 said:
Yes I am completely S-OFF with CID 111111 and SU. The phone has been working good, Cricket service is not all that great in my area. I see there is a software update 2.04.1050.5 (15.1 MB), I am assuming if i run this update it will most likely wipe everything I just did. Is this correct?
Click to expand...
Click to collapse
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
eduardog131 said:
I think. Anyways, download this: http://www.mediafire.com/download/maa60jha4eod834/rom.zip
Contents of said rom.zip:
4.2.2 system.img with root.
4.2.2 stock boot.img.
4.2.2 stock recovery.
New HBOOT and radios and stuff.
If you get an error (flush again or something.), then just resend the command. (fastboot flash zip path/to/rom.zip)
Click to expand...
Click to collapse
Downloading now. I will let you know how it goes...thanks a million.
This is what I got when I tried to flash the rom:
sending 'zip' (691470 KB)...
OKAY [ 37.267s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 37.301s
I dont understand if I am S-Off and super CID.
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!