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!
Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.
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
I need help. so if anyone could help, that would be much appreciated. I had my desire s unlocked, but S-ON. HBOOT-2.00.0002. So i tried to downgrade it and get it S-OFF,to flash new roms. I don't pretty much know what i did, but i followed step "Modifying the version of your phone" from this thread: forum.xda-developers(dot)com/showthread.php?t=1318919 and step 3 from this one: mihaiush.wordpress(dot)com/2012/08/20/htc-desire-s-s-off-hboot-2-00-002/ all i did was downloading misc_version from the first one, pushed the codes in adb then i downloaded zergrush from the second one, followed by the codes. Then i added "fastboot oem lock". Now, on bootloader, it shows me ***RELOCKED*** and ***Security Warning***. Tried to downgrade, but my RUU detects 14.something for a version, instead of 1.27.405.6, as said in the first thread ("c. The RUU must detect your phone version as 1.27.405.6") so i didn't click on upgrade ROM. Now i can't even install twrp recovery to try to restore the backup i had.. Anyone knows what should i do? Shall i click update ROM when asked by RUU? I forgot to mention when i choose reboot or recovery on fastboot it just reboots into fastboot.
I unlocked the bootloader again and it works now! so this thread may be deleted.
Hello! Third HTC I'll (potentially) root, so I'm not sure why I'm stuck on this, but here goes....
I have an AT&T (Evita) on 2.20. It seemed the first step was to unlock using the X-Factor root exploit, so I did. When I was done, my bootloader said *UNLOCKED*, but it still said "S-OFF".
When I read any of the rollup/Q&A/FAQ threads, they all seem to indicate that my next step should be to flash a custom recovery. The first time I installed GooManager, then settings/Install OpenRecoveryScript. It said recovery had been installed, but when I selected Reboot Recovery, it wouldn't reboot.
So I powered down and came back up in the bootloader. I clicked recovery from there and after a few seconds I wound up with a mostly black screen with a drive or something in the middle and a red X over the middle. Something's clearly not working.
So I manage to get out of that, get the phone booted back into Android, back to the bootloader and into Fastboot USB to try and install the TWRP img file I downloaded from their site. did "fastbook flash recovery nameofmyimage.img" and it appeared to have moved the IMG to my device. Typed "fastboot reboot" and I wound up rebooted back to Android. Went back into GooManager to see if the "reboot into recovery" command would work now, it doesn't. Powered bown and back into the bootloader screen, select Recovery and I wind up back in Android.
What am I missing or doing wrong? Anyone?
finallygreen said:
I have an AT&T (Evita) on 2.20. It seemed the first step was to unlock using the X-Factor root exploit, so I did. When I was done, my bootloader said *UNLOCKED*, but it still said "S-OFF".
Click to expand...
Click to collapse
You mean S-off or S-on? S-on is the stock condition, and S-off is the modified condition (all security off).
finallygreen said:
So I powered down and came back up in the bootloader. I clicked recovery from there and after a few seconds I wound up with a mostly black screen with a drive or something in the middle and a red X over the middle. Something's clearly not working.
Click to expand...
Click to collapse
That is the stock recovery. GooManager is a big quirky when installing TWRP, the fastboot way is safer. Of course, you tried that way and still having trouble.
Try:
fastboot erase cache
Also, what version of TWRP exactly are you trying to install by fastboot (exact filename)?
redpoint73 said:
You mean S-off or S-on? S-on is the stock condition, and S-off is the modified condition (all security off).
That is the stock recovery. GooManager is a big quirky when installing TWRP, the fastboot way is safer. Of course, you tried that way and still having trouble.
Try:
fastboot erase cache
Also, what version of TWRP exactly are you trying to install by fastboot (exact filename)?
Click to expand...
Click to collapse
I typed it correctly....when I'd finished the process of unlocking the bootloader, my bootloader screen said:
***UNLOCKED***
EVITA PVT SHIP S-On RL
And that's what it still says. Is this what's stopping me from proceeding? Did I miss something because I can't find a step I missed in any of these tutorials...they all say to move on to installing a custom recovery right after you unlock the bootloader.
Oh, and the img I was flashing:
openrecovery-twrp-2.6.3.0-evita.img
Can you post the text from the command prompt on an attempt so we can try troubleshoot it?
Sent from my Evita
which text?
The text from the command prompt when you're trying to flash TWRP recovery.
Sent from my Evita
timmaaa said:
The text from the command prompt when you're trying to flash TWRP recovery.
Sent from my Evita
Click to expand...
Click to collapse
OK, so today I go back to the bootloader screen and I see this:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Yesterday, I didn't have *** TAMPERED *** at the top.
Anyways, I've tried flashing TWRP again. here's the command prompt text:
Code:
c:\android>fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
sending 'recovery' (8176 KB)... OKAY
writing 'recovery'... OKAY
And that's it. But this time, my results are different. I rebooted the bootloader, selected recovery, and now I'm IN TWRP!
So, I guess that's a good thing. However, since I don't at all understand why doing the same thing gave a different result today (and that *** TAMPERED *** thing that wasn't there yesterday), I'm a bit confused at to where to go next. So that I don't muck this up, could you tell me what the next logical step should be now?
Make a nandroid backup. Download an evita Rom and flash away
Sent from my VENOMized HoxL
area51avenger said:
Make a nandroid backup. Download an evita Rom and flash away
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
OK, so I made a backup (just data/system/boot...hopefully that was the right choice), and when I went to reboot, it said that SuperSU was not yet installed. Now I'm not sure why none of the writeups mentioned that part because I know that every HTC I've ever rooted in the past needed that. Anyways, I said yes, it installed, and now I'm back in Android. I went back to the bootloader to check what it was saying...it still says "Tampered/Unlocked/S-On". I then went into TWRP and told it to reboot, this time it didn't prompt me to install SuperSU, so I guess that's good.
So:
1. Will the backup I made prior to the SuperSU install be good or will I need to redo that now that SuperSU is installed?
2. Why still S-On? Are HOX users sticking with S-On or....is this another step I've missed or is it even necessary with this device?
3. I keep seeing something about SuperCID...something that never came up in my previous HTC rooting adventures. What is this? How can I tell if I have it? Do I need it?
4. If this does indeed mean I'm fully rooted now and it's time to select a ROM, could anyone recommend one? I tend to prefer the latest Android that's known to run well on the device, running as close to stock and least amount of bloatware possible. But then again, I've no clue what the ROMs for this device can do since I just got it, so I'd certainly try something outside those parameters if it was extremely well-recommended.
Thanks!
Yeah that backup configuration looks fine to me. TWRP 2.6 has a feature where it detects if you don't yet have root installed when you're about to reboot, so it can install it for you, makes rooting a lot easier. You don't need to backup again, the one you made is fine.
The phone is still s-on because you haven't gone through the s-off process yet. Having s-off and unlocking the bootloader are two different things.
SuperCID is needed to get s-off, so you'll need to get SuperCID before you attempt the s-off process. The hex edit method is the best method for you to achieve SuperCID. One you've done that you can go to the Facepalm S-off thread and get s-off.
You are now fully rooted and can install custom ROMs. Asking for best/favourite/most stable/recommended ROMs isn't really allowed here, this is because saying one ROM is superior infers that the others are inferior in some way which isn't fair to the devs who spend a lot of time developing them for us. Take a look through our two development sections which are here and here. Pick one you think you'll like and give it a shot. Make sure you read the OP for the ROM you select because some have firmware upgrades prior to flashing them, these firmware upgrades usually need s-off to be done.
My suggestion is to do this: get SuperCID, get s-off, find a ROM, make sure you meet any requirements stated, and then flash it. If you have any questions dying be afraid to ask.
Sent from my Evita
timmaaa said:
Yeah that backup configuration looks fine to me. TWRP 2.6 has a feature where it detects if you don't yet have root installed when you're about to reboot, so it can install it for you, makes rooting a lot easier. You don't need to backup again, the one you made is fine.
The phone is still s-on because you haven't gone through the s-off process yet. Having s-off and unlocking the bootloader are two different things.
SuperCID is needed to get s-off, so you'll need to get SuperCID before you attempt the s-off process. The hex edit method is the best method for you to achieve SuperCID. One you've done that you can go to the Facepalm S-off thread and get s-off.
You are now fully rooted and can install custom ROMs. Asking for best/favourite/most stable/recommended ROMs isn't really allowed here, this is because saying one ROM is superior infers that the others are inferior in some way which isn't fair to the devs who spend a lot of time developing them for us. Take a look through our two development sections which are here and here. Pick one you think you'll like and give it a shot. Make sure you read the OP for the ROM you select because some have firmware upgrades prior to flashing them, these firmware upgrades usually need s-off to be done.
My suggestion is to do this: get SuperCID, get s-off, find a ROM, make sure you meet any requirements stated, and then flash it. If you have any questions dying be afraid to ask.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you very much for explaining things so clearly...I really appreciate that!
Second, I honestly didn't stop to think about the full ramifications of asking for a ROM recommendation. Based on your explanation, I completely understand why I shouldn't ask!
I'm gonna take your suggested route (SuperCID/S-Off) then start exploring for ROMs.
Thanks again for all the help!
No problems, glad to help. About the ROM question, you didn't know so it's all good, no harm no foul.
PS. If someone helps you around here, please press the thanks button.
Sent from my Evita
OK, so maybe I'm not as clear as I thought I was.
I did the X-Factor thing to unlock the bootloader at the beginning, and that involved spoofing my CID to get the unlock code from htcdev.com, right?
In any case, right now when I type: fastboot getvar cid
I get:
cid: 11111111
But you told me I still needed to do some hex editing?
You are good with the vid, time to achieve s-off
Sent from my HTC One XL using xda app-developers app
Yeah, you already have SuperCID do you can go for s-off now.
Sent from my Evita