Related
I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
I've been trying to get back to stock so I can send my phone in for warranty, I'm one of the unfortunate ones who is constantly stuck on edge. Current hboot is 2.15 and cid is ROGERS001, unfortunately there's no ruu out there for my hboot, so I had to use the method mentioned in this thread to get back onto a stock rom.
My problem now is even after unrooting using SuperSU, flashing the stock recovery and relocking my bootloader, it still says "tampered". One thing I've notice is that SuperSU is still present under my apps, when I try to open it it says the binary needs to be updated, and my options are to install the SU binary via cwm/twrp, or "normal". The cwm/twrp method just attempts to reboot into recovery and the "normal" method proceeds to an installation screen where it fails immediately.
Am I forced to s-off and SuperCID, then run a different ruu in order to get back to completely stock?
I updated hboot to 2.16, and now i regret that. So i wanted to get back to 2.15.
This is what i've done so far.
Following all the guides and whatever i could find on the forums.
1. downgrade hboot to 2.15
2. oem relock
3. installed org RUU, downloaded on of the exe's (RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe) and let it do it's thing.
4. Here i wanted to get root back and all that so i could start over with flashing. So i unlocked the phone again.
5. installed twrp and rooted after this the org RUU still boots and everything works.
6. This is where things go wrong, when i flash CM11 and gapps i get installations fails, don't know why. (error executing updater binary in zip)
I don't know why it's not working, but in the bootloader it says unlocked, but "tampered" is gone, and that might be the problem, but i cannot remember what that is. s-off and cid is still there.
Any help would be welcome.
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!
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
BrandonBaskin said:
For some reason I am unable to install the ROM via RUU OR OTA update (manual or auto). I am getting a Error 132 (signature error). I am S-ON and RELOCKED.
Things I have already done/tried:
Made sure I have the correct RUU (it's the only one available as far as I know and it is for the HTC unlocked US variant).
Made sure my device is RELOCKED and stock recovery installed.
Tried multiple methods - including RUU (tried inside of the OS as well as in download mode/bootloader mode); OTA tried to flash manually inside of stock recovery, tried to download OTA (no update found), tried to flash firmware and OTA in custom recovery as well stock recovery.
Searched the forums relentlessly for answers to the 132 signature error. There doesn't seem to be a consensus answer.
Of note: My 'Software Status' is flagged as "MODIFIED," I'm wondering if that is preventing me from updating the HBOOT via RUU.
Please let me know if you can think of any solutions because I am stumped, and I'm sure the community could use a more definitive answer about the 132 Error as it seems to have been mention several times over the course of quite a few years.
Thanks guys
Click to expand...
Click to collapse
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
salvy' said:
You need to be S-OFF for flash the Firmware and the 2.18 will not run if you dont have flashed the firmware. If you have an Unlocked USA you need tu run the 1.57 (the last one before 7.0), the status will be OFFICIAL and you can just update whit OTA in setting, information, update like a normal device or flash ota in the recovery stock, but you steel need 1.57.617.60 version and OFFICIAL status.
Click to expand...
Click to collapse
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
BrandonBaskin said:
Hi, thanks for your response. I have run the latest RUU multiple times but it has failed to reset the software status to 'OFFICIAL.' I have even rolled back to the previous RUU, downloaded and installed the OTA for 1.57.617.60 and that too failed to reset the software status to official. Getting S-OFF for me is not currently an option so I'm wondering if there is a practicable alternative.
Thanks again
Click to expand...
Click to collapse
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
MGfusion said:
Take the ota.zip file and try to install it via the stock recovery, and see what errors you get. That is how I figured out what was wrong with mine ( wrong CID)
Click to expand...
Click to collapse
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
BrandonBaskin said:
OK. Attempted to flash OTA in recovery and it appeared to be successful, however after rebooting out of recovery there was no OS loaded. Do you know of any way to reset the software status to official - because running the RUU(s) for the current base doesn't seem to work.
Thanks
Click to expand...
Click to collapse
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
MGfusion said:
Flash 1.57 ota, and relock boot loader if unlocked. Unlocked boot loader might be what is making the software status say modified
Click to expand...
Click to collapse
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
BrandonBaskin said:
Bootloader status is: "RELOCKED"
1.57.617.60 RUU is installed
Software Status is still: "MODIFIED"
Could it be that there is no way of resetting this status while S-ON?
Click to expand...
Click to collapse
I'm not sure, I don't understand what could still be "modified"
MGfusion said:
I'm not sure, I don't understand what could still be "modified"
Click to expand...
Click to collapse
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
MGfusion said:
Try installing this zip file with the stock recovery and relocked bootloader. This is how I upgraded to nougat, no problem
https://drive.google.com/file/d/0B53pV_Dn96x1aDJZU2l5MWdmeFk/view
(This is the extracted ota zip file)
Click to expand...
Click to collapse
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
BrandonBaskin said:
Thanks! I will try again with this file. Just curious... do you remember if you "Software Status" was 'MODIFIED'? And are you S-OFF?
Click to expand...
Click to collapse
Can't remember if it said modified or not, but I am definitely s-off.
MGfusion said:
Can't remember if it said modified or not, but I am definitely s-off.
Click to expand...
Click to collapse
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
BrandonBaskin said:
I don't either. This is extremely frustrating just to get an update. If I've run the proper RUU I'm not sure how HTC doesn't make sure that it resets the software status.
At any rate, I will keep digging around the forums because I think this Error [132] deserves a proper solution.
Click to expand...
Click to collapse
Try installing the OTA, then flashing ruu. Thats how I did I it.
BrandonBaskin said:
It may literally be no way to update it with S-ON. It's cool because Sunshine is an option when I get a some extra cash but this seems to be a bit of a programming flaw on HTC's part.
Click to expand...
Click to collapse
Oh, you are s-on? I would definitely try sunshine and then install ota or ruu then
The_scam said:
Try installing the OTA, then flashing ruin. Thats how I did I it.
Click to expand...
Click to collapse
Hey, thanks for the response. What is Ruin?
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
kommoncents said:
I've got S-OFF, Software Status: Official, Relocked boot loader, CID: BS_US001, Current ROM: 1.57.617.60
I've been getting the same "Error 132: Signature Error" when trying to flash the 2.18.617.1 RUU.
Attempted to flash the most recent RUU I had (1.57.617.41), which was successful. Attempted the 2.18.617.1 RUU again, same issue.
Tried changing the CID to 11111111 and tried flashing the RUU, still getting Error 132.
Tried pushing the 2.18.617.1 OTA via ADB Sideload and got "assert failed: check_cid("00000000", etc...)" error
Changed CID back to BS_US001 and started pushing the OTA updates (1.57.617.52, 1.57.617.60, 2.18.617.1) one by one via ADB Sideload
All of the OTA installs were successful.
Now, only getting the white screen with the HTC logo.
Ran 2.18.617.1 RUU again, ran fine this time.
Still only getting the white screen with the HTC logo.
Not terribly excited about the direction this is going...
Click to expand...
Click to collapse
download the zip file I had given a link to above and try installing it with the stock system recovery
BrandonBaskin said:
Hey, thanks for the response. What is Ruin?
Click to expand...
Click to collapse
Lol sorry, meant to type ruu. Using my phone and autocorrect ?
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
MGfusion said:
download the zip file I had given a link to above and try installing it with the stock system recovery
Click to expand...
Click to collapse
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
The_scam said:
Lol sorry, meant to type ruu. Using my phone and autocorrect
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
Try installing the TWRP, look around at the system files. Is anything there? You might have to wipe everything and try the ruu again.
Maybe try rebooting into "fastboot OEM rebootRUU" then once that loads, type "fastboot flash <name of your ruu.zip>" from your computer
Click to expand...
Click to collapse
lol ohh! ok...I thought it was something like Odin haha
so just so I'm clear:
Flash OTA (in Recovery)?
Then immediately start the RUU?