Database Info

[Q] Trying to get HTC one S on stock rom? Please help ?

I have this HTC one S, I am not sure which network phone is it. I bought is from someone else and he had no idea about network.
Right now when i press factory reset from volume down + power button. it brought me at this screen which say clockwork Mod recovery v 5.8.1.5
I am able to select only first 2 options which are reboot system now and install zip from sdcard . When i pressed install zip from sdcard its not doing anything and bringing me back on same screen
Could you please help me installing stock rom on this phone. ?
Thanks in advance guys

AW: [Q] Trying to get HTC one S on stock rom? Please help ?
If you turn ur phone on with holding power and volume down you should be in your bootloader.
Can you tell us what stands on the top?
Locked/unlocked/relocked and which hboot version?
Sent from my HTC One S using xda premium

this is the info
Tampered
Unlocked
VLE PVT ship s-on RL
HBOOT-1.08.0000
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323
eMMC boot
Mar 21, 2012, 16:01:09
Just curious to know what this information means , please let me know each line if possible. Appreciate your help

AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Tampered: no stock recovery
Unlocked: your bootloader is looked
VLE: Ville: HTC One S
S-ON: security on
Radio: your radio Version
You have to lock your bootloader.
Download the all in one toolkit which you can find in the development section. There are all necessary files.
Be sure you have installed the HTC sync driver.
1. Connect your mobile To your pc when your are in the screen where you can see hboot version etc.
2. There should be "hboot USB" in blue.
3. Navigate to hboot and press power.
4. It should change to "fastboot USB" in red.
5. Then open the all in one toolkit on your PC.
6. Open the folder where ADB and fastboot exe are located.
7. Press shift and right click somewhere in the folder and open the command line.
8. Then type in "fastboot oem lock"
9. If you take a look to your phone you should see that the "unlock" changed To "relocked"
That was the first step.
10. Go To the development section in this forum and look for the wwe europe ville ics ruu 2.31 or sth like that.
11. Download the file
12. Doubleklick the file
13. Follow the instructions
14. Let the ruu install everything
15. If everything works fine you should be on official ICS 4.0.4 with Sense 4.1 now
Good luck!
I hope I wrote an easy understandable instruction.
If u experience any problems feel free to post it here.
I'm sure I or someone else can help you.
Sent from my HTC One S using xda premium

NQNH , thanks a lot for this easy and nice explanation, its really helpful for a noob like me. I have few more questions but lets resolve this issue first. Okay I tried all steps you mentioned and it worked like a charm. just got stuck at final step. Please help.
In CMD i got this
'C:\Users\Owner\Desktop\HTC' is not recognized as an internal or external comman
d,
operable program or batch file.
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>fastbo
ot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.941s
C:\Users\Owner\Desktop\HTC custom rom procedure\One_S_All-In-One_Kit\data>
This is the error message when i tried step 8, but when i checked the screen it shows relocked now , seems like it worked okay.
i tried this file
http://forum.xda-developers.com/showthread.php?t=1941402
Everytime i runs this RUU application file , after passing thru all steps it says ROM utility stopped working, Seems like i am almost done but just stuck at last point.

Hello NQNH, i tried it one more time and finally passed thru that screen. it started ROM update utility but got back with this error msg
Error (131) customer ID error
The ROM update utility cannot update your android phone
please get the correct ROM update utility and try again
I am using RUU : 1.0.6.2012
please let me know if i can use any other utility

AW: [Q] Trying to get HTC one S on stock rom? Please help ?
What do you get when you type in
fastboot getvar cid
?
Try this RUU
http://www.androidfiles.org/ruu/sec...02.31_10.09a.50.04L_release_275655_signed.exe
Sent from my HTC One S using xda premium

I tried RUU which you suggested , Thanks NQNH but sorry this time it came back with error (130) , model ID error.

fastboot getvar cid : BM___001

AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Seems that you have a branded phone. (Bell Mobile Canada?)
This ruu should run fine:
http://www.androidfiles.org/ruu/sec...02.04_10.08g.50.04L_release_280275_signed.exe
Sent from my HTC One S using xda premium

Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..

bindudhindsa said:
Thanks Thanks Thanks Thanks a lotttttttttt, I don't know if pressing thanks button is good enough to appreciate your help. I learnt a lot from this session. If you don't mind , just for curiosity can i ask you few more questions,
Tampered (Does it mean somebody tried to install custom rom on it or something else ? )
Unlocked
VLE PVT ship s-on RL ( does S-on means this phone is unlocked or some thing else ? )
HBOOT-1.08.0000 ( is it same like version number in iphone , is it baseband version number, where i can find this number in phone settings ? )
Radi-0.16.31501S.06_3
open DSP-v23.1.0.32.0323 ( don't know what it means , please explain )
eMMC boot ( don't know what it means , please explain )
Mar 21, 2012, 16:01:09 ( is it manufacturing date or date when it was tempered )
Thanks again for your help ..
Click to expand...
Click to collapse
glad to hear that I helped you.
Tampered means that someone already changed something on the phone (unlocked/relocked/custom recovery)
A comparison should be.. if you bought a new pc and if you open the case you have to break the seal. The "Tampered" say that you had break this seal on the phone (e.g. by unlocking the bootloader)
S-ON means that the security flags are on. Its a system protection so nobody can manipulate system data.
S-ON + locked bootloader -> you can do nothing, no root, no custom things
S-ON + unlocked bootloader -> you can flash custom recovery, root, custom rom (you can see an unlocked bootloader as a compromise between S-ON and S-OFF
S-OFF -> you can do everything what you want, change bootloaderGUI, bootanimations, splashscreens.
Unlocked means that you bootloader is unlocked. If its locked you cant install custom recovery, root and custom firmware. It has to be locked when you install a RUU.
You cant find your HBOOT version in your phone settings because its the version of the bootloader.
the bootloader is independed from the rom you are on. Its like the BIOS from your PC and your ROM is Win7 where you either cant find the bios version.
Radio is the module which is responsible for mobile data etc.
no/wrong/corrupt radio = no network/no signal
openDSP .. i don't know
eMMC boot, I guess that this is the partition where the bootloader is located.. but I'm not sure.
Mar 21, 2012, 16:01:09 is the date when .. difficult to explain .. when the development of the RUU was finished?
if I wrote something wrong please correct me.

Thanks a lot for this very helpful information. Appreciate your help. Kind of person like you are the reason these forums are running successfully and helping novice people like me. Thanks again.

AW: [Q] Trying to get HTC one S on stock rom? Please help ?
Thanks for your words
Sent from my HTC One S using xda premium

Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?

auronn said:
Hello.
I'm having same problem with getting back on stock firmware...
After trying to flash into CM10, i got stock in CM boot logo.
So trying to get back to original using RUU.
But it just looks like I can not get right one...
I did everything like in posts above, and when I enter "fastboot getvar cid" I got "HTC_Y13"
Any idea which RUU is correct for that?
I'm still trying, so maybe it will be fools luck... Or maybe someone can put me on point?
Click to expand...
Click to collapse
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)

Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23NW410019
(bootloader) imei: 359901040772549
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?

real187 said:
your cid is a unbranded eu cid.
try any unbranded eu ruu (3.16 or earlier)
Click to expand...
Click to collapse
Thank you a lot!!!
This one worked:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release_301814_signed_2_4 .exe

auronn said:
Hello everyone,
So, 2 days in front of PC, reading forums and trying. No luck... So try to post it here.
I want to flash to CM10.
Bootloader is unlocked.
Recovery is installed (TWRP S4)
Root is done.
Security S-ON.
When I try to install CM10, everything went fine, but when It have to reboot it just stuck in CM booting logo loop...
And since you can't remove memory card on HTC One S, I think I have no other option how to reinstall stock firmware. And my problems starts...
I relocked bootloader.
Download already like five different RUU's...
The problem is, I can not locate my version, it's blank...
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23.......
(bootloader) imei: 3599...............
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4124mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
So everytime I start RUU, in the screen Current information about your Android phone" "Image version" is blank and the one with "Verify that you want to update the ROM version" "From Image Version" is blank...
When I push "Next" it goes "Checking", then "Rebooting Bootloader", "Erasing User Data" and "Sending".
When it comes to "Updating Signature" I'm getting error code...
Phone is bought in Norway, and by checking cid: HTC_Y13, I can see that it's HTC-Nor. So which one of RUU's I have to use?
I also tried to flash zip RUU, using One_S_All-In-One_Kit_v3.5 with same no luck...
Really don't know what to do... Any help would be appreciated...
Thank you in advance!
Thank you, I'm downloading and will try this now:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
Already tried those:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed.exe
RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe
RUU_VILLEPLUS_U_JB_45_HTC_Generic_1.14.999.50_Radio_1.10r.50.05.19_10.22a.50.08L_release_294323_signed.exe
And also:
OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
using One_S_All-In-One_Kit_v3.5 with no luck...
Does any body can tell me the difference between Ville, VilleC2 and VillePlus?
Click to expand...
Click to collapse
Firstly, I would recommend removing part of your IMEI and Serial Numbers from your post, it could be used in bad ways by other people.
Ville is the HTC One S with a Snapdragon S4 chipset, clocked at 1.5GHz (dual core) otherwise known as z520e. (You have this phone)
VilleC2 is what became of the HTC One S when HTC ran out of Snapdragon S4 chipsets in many parts of the world due to a shortage. It has a Snapdragon S3, clocked at 1.7GHz (dual core) otherwise known as z560e.
VillePlus is a Special Edition version of the HTC One S, only available in Taiwan. It has the same processor as the Ville, except comes in a white body instead of the normal grey or black options and has 64GBs of internal storage. The other two have 16GBs internal storage. This phone is quite rare.
You should try RUUs only that say ville, and not VillePlus or VilleC2. These won't work and may even irreversibly damage your phone.
OTAs only work when you already have a previous firmware version. Let's say you were on ICS, a Jelly Bean FOTA is released (firmware over the air) and installs ("flashes") on top of your existing ICS installation, keeping your apps and data.
RUUs wipe all data and wipe everything on the phone when installing through a USB connection.
Could you specify what error code you get on the RUUs?
----
The reason why CM10 didn't boot is because you didn't flash the boot.img.
You need to extract the boot.img from the CM10 zip and put that into your "working folder" (the folder with adb and fastboot files in it)
Open up a command prompt / terminal in that folder and type
fastboot flash boot boot.img
when you are in FASTBOOT USB mode in the bootloader.

Go to Fastboot. Plug in your USB with the phone. Now, ctrl and r --> type cmd --> cd to C:/where your adb is --> fastboot read cid
Then type the 8 digit string that you get. It would help us determine your network provider.

Current ROM is not stable, unable to flash most of the roms via TWRP with S-Off

Ok, I'll start from the beginning.
I purchased my phone from Rogers at April 2012. So it was Rogers stock 4.0.x rom, everything was locked at that time. I FORGOT the stock hboot/ruu version number for Rogers ONE XL.
From the time being, I rooted it, superCID, unlocked via HTC DEV. After these, I flashed customer recovery, and successfully flashed several roms from time being. Finally I stayed with ViperXL.
Then, facepalm s-off is released, and I s-offed my phone. Everything worked just fine.
The problem occurred when I started to flash sense 5 roms about couple weeks ago. I did not upgrade my firmware and I flashed sense 5 based roms (this is my bad), so I'm experiencing random reboot and signal drops. Then I upgraded my firmware using the instruction in this tread: http://forum.xda-developers.com/showthread.php?t=2423735 . I verified my installtion with ./fastboot gervar all . At this time, there were two warnings on the top of my bootloader: "tampered" and "unlocked".
So, at this time, I tried several sense 5 roms. My recovery at this time was TWRP 2.6.3.0. All the roms have one common problem on my phone: after I locked the screen and left my phone for a while, if I wanna wake my phone/display, nothing happened by pressing the power button. I have to press the power button for 10+ seconds to restart my phone. If I just left my phone for a short time and wake it, it will work properly.
I was thinking are these sense 5 problems, so I tried to flash cm roms yesterday. I followed the instructions in http://forum.xda-developers.com/showthread.php?t=2382933 to upgrade my RUU to 3.18. I flashed TWRP 2.6.3.0, and tried to flash cm 10.1 and 10.2. For cm 10.2, there were a lot of force close when I boot my phone. For cm 10.1, it is so unstable with random reboots as well as did not respond when I try to wake up the phone. I am not questioning CM's roms, I am sure there were something wrong with my phone or what I've done to it.
So, I tried to flash viper rom again with ruu 3.18 installed. The rom won't even boot...... However I found something interesting when I am flashing the viper rom. The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.
Then I re-installed the RUU 3.18 update on my phone. Right now, the AT&T stock rom also will not respond after I left my phone idle for a moment......
User timmaaa kindly reminds me about something. I am posting the original post I started in another tread.
Originally Posted by snake3276120 View Post
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/show....php?t=2382933
I boot into bootloader, and ran fastboot getvar all, the result is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT246W304864
(bootloader) imei: 359691041684351
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4122mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I'm assuming "(bootloader) version-main: 3.18.502.6" is the RUU version. I also flashed an hboot 2.14, it became 3.17.xxxxxxx. That'w why I am assuming this is the RUU number.
Ok, regardless of the build number or ruu...... I think there is something wrong with my bootloader. It doesn't matter which hboot I flash (hboot 2.14 with version-main 3.17/3.18, or hboot 2.15 with version-main 5.08), and I tried several twrp (2.4.4.0 and 2.6.3.0). The time it took to flash viper xl is really short while viper xl has 700MB. It is even shorter than the time I flash CM, which is around 180 MB. (Sorry for the bad English, I actually mean "The size of ViperXL is 700+ MB while the size of CM 10.1 or 10.2 is around 180MB. The time it took to flash ViperXL was shorter than the time it took to flash CM roms.")
I guess I'll start with the current AT&T stock rom (which still lose respond after I left the phone open for a while, and I have to press the power button for 10 secs to reset my phone)on hboot 2.14 and ruu 3.18. Root it, try to s-off again. Not sure if this will solve the problem.
Something interesting when I'm booting my phone, when the phone displays only the green HTC in the middle of the display, there is some text below it... saying something like "This is an internal build, do not distribute outside of HTC, failure may cause to law action". However, the AT&T stock rom I'm running right now does not have this.
timmaaa:
It's a bit hard to follow what you're saying there but here goes. It's not the RUU number it's the build number. An RUU is the program that updates your phone, the reason you see them referred to as the 3.18 RUU is because they're known by the build number that they update your phone to.
Did you check the md5 of the downloaded file as someone else suggested? It might be corrupt. Also, maybe you should try TWRP 2.6, versions 2.4.x and 2.5.x are well known as being very buggy, and I've seen people have issues with version 2.6.3 too. 2.6 is rock solid though.
The red text you see when the phone boots up is completely normal for a modified phone so you needn't worry about that. The reason the stock ROM doesn't have it is because the RUU has returned your phone to being completely stock, therefore not modified, therefore no red text.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I am wondering where I can get my RUU number......
Also, in this case, what I should do now? Install TWRP 2.6.0.0 and try to flash everything again?
Currently "tampered" is gone from my bootloader, only "unlocked" stays there.

Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
Because some posts are saying RUU 3.17 or 3.18, so I got confused...... but as long as it's a program, I will assume they are talking about the firmware or bootloader after running RUU 3.17 or 3.18 upgrade.

timmaaa said:
Lol you've kinda mashed my quote in with your post there so it's hard for people to see where they begin and end.
What do you mean you want to get your RUU number? Like I said an RUU is a program, what exactly do you mean?
Sent from my Evita
Click to expand...
Click to collapse
I fixed the qoute

Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita

timmaaa said:
Just to be clear, after you ran the 3.18 RUU you booted the phone without making any modifications and the problem was still occurring, right? It seems to me that it might be some kind of hardware problem that's causing a sleep of death every time the phone goes into sleep mode.
Sent from my Evita
Click to expand...
Click to collapse
That's right, I didn't even flash recovery... Well, my stock rom just self-rebooted, and stuck at booting animation while adb is still able to recognize it, and I can issue a reboot from adb. This also applies to my sense 5 roms.
If it's hardware problem, looks like upgrading to hboot 2.15 ruined my hardware, which is hard to believe...... Everything works fine before I upgrade my hboot to 2.15

Unfortunately it isn't under warranty anymore either.
Sent from my Evita

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I know... it is unfortunate...

timmaaa said:
Unfortunately it isn't under warranty anymore either.
Sent from my Evita
Click to expand...
Click to collapse
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.

snake3276120 said:
I upgraded my hboot to 2.15 and I flashed MaginRom 4.0. At least it's booting...... looks like my recovery hates aroma installer.
Click to expand...
Click to collapse
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.

Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita

timmaaa said:
Yeah I can confirm I've seen folks with bugs on 2.6.3 but I've been using 2.6 for months and not a single problem (and no reports of bugs from others).
Sent from my Evita
Click to expand...
Click to collapse
I used 2.6.0.0 to flash my current magiorom 4..... well at least it is usable now, with app/sense/notification bar/wake phone do not respond sometimes... I'm not blaming the rom, I am blaming my phone... probably now it's the time to get a new one lol

redpoint73 said:
Confirm your hboot and baseband version and post here. You said it upgraded, but let's make sure it actually was completely successful.
Also, I think TWRP 2.6.3 has some bugs, not sure if AROMA is one of them. You might check the TWRP thread. But I believe other 2.6.x versions are very stable. I've been on 2.6.0 for a while, and everything seems to be working great, and don't remember any bug reports on that version.
Click to expand...
Click to collapse
Here you are, boss.
PS E:\Program Files (x86)> cd '.\Minimal ADB and Fastboot'
PS E:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3874mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
PS E:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
I think the result is the same in thread http://forum.xda-developers.com/showthread.php?t=2423735
Quoted from the thread:
Install:
Installing the rom:
Download the rom and copy to your sdcard
Reboot to Recovery
Flash rom
I recommend you wipe data before or after flashing the rom
For root access, flash this: Flash this in recovery for root access
Reboot
OPTIONAL: Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this! Flash at own risk!)
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android: fastboot reboot or into recovery: fastboot reboot-recovery
Click to expand...
Click to collapse
Please refer to the attachment for a photo of my bootloader

Will TWRP 2.3.3.0 solve my problem? It looks like most roms recommend this recovery.... btw I'm running 2.6.0.0 at the moment.

No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita

timmaaa said:
No, changing TWRP won't solve your problem. You said you're using TWRP 2.6 now and that version is fine. I'd suggest trying one more time to do a clean flash, so wipe cache/dalvik cache/factory reset/system and install the ROM. Hell, do the wipe two or three times to be sure before installing.
Sent from my Evita
Click to expand...
Click to collapse
lol thanks... Every time before I flash a new rom, I just format everything...

I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita

timmaaa said:
I don't know what to tell you then. There's nothing wrong with the ROMs you're using so it's either a case of user error or hardware failure of some kind.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...

snake3276120 said:
Thanks for all the help... I think it is hardware error... because I'm an electrical/computer engineer, I don't think I can't even handle flashing roms... Maybe I need to do more research lol
One XL is a nice phone, I don't wanna switch yet...
Click to expand...
Click to collapse
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4

sandys1 said:
Could you also try one last thing? Could you upgrade your twrp to latest release and try flashing cm 10.2 0310 nightly please.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Ok I'll do a backup and try tonight....latest twrp do u mean 2.6.3.0, or there is another new release?

[Q] How do I remove S-On, Super CID, unroot and get completely back to stock

My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.

DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
IIRC the RUU for your device reverts all of that. Not 100% sure about the S-ON though.

I've read somewhere in another guild that it's necessary to first Relock your bootloader (using the oem lock command) and afterwards use the right RUU for your device...
I thought this could be helpful

Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader first will cause this to not be the case?

DRUMROT said:
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader it first will cause this to not be the case?
Click to expand...
Click to collapse
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself

FantasyGamer said:
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
Click to expand...
Click to collapse
Yeah, I'm assuming I'd have to do some more then just run the RUU.
I'd gladly give it a go but like I posted earlier, I'd like to know if there is a certain order to do this in. If I run the RUU before removing s-off, will that make things easier? Harder? No different?
Anyone?

Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.

FantasyGamer said:
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
Click to expand...
Click to collapse
Hmmm, all right. I've never used the all-in-one kit but I've noticed it has a "back to s-on" function so I'll give it a try. I'm on Linux so I need to run it in Wine (Windows emulator) so hopefully there's no hiccups.

DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
1)If you have put on a modified HBoot (such as to remove tampered or red warning) return to stock.
(only added this because if you S-on with modified HBoot it will brick your phone)
2)Run RUU.exe
3)Reset lock status flag
http://forum.xda-developers.com/showthread.php?t=2155955
4)S-ON your phone
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
---------- Post added at 01:15 PM ---------- Previous post was at 01:05 PM ----------
Edited that, If anyone notices a problem please post.

So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)

FantasyGamer said:
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
Click to expand...
Click to collapse
No, it doesn't need to be locked when S-OFF.
The most important is running the RUU that matches your CID. (since you are s-off it is easy to change the CID to whatever you want, and thus run whatever RUU you want)

i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot

[Q]

I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S off
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?

You don't need root access, because you have s-off. You can simply use fastboot to change the CID to SuperCID.
Code:
fastboot oem writecid 11111111
Next time, do a bit of research before creating a thread. Pretty much every question you could think of asking has been asked, and answered within our forum. Check out all of the links in my signature, almost everything you'll ever need can be found there.
Sent from my Evita

Again Question sir
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?[/QUOTE]

jezi251 said:
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
Click to expand...
Click to collapse
The at&t CID is blocked at htcdev, so you need to get SuperCID in order to unlock your bootloader. Reading the stickied threads (specifically the Evita FAQ thread) in the section you've just posted in world have uncovered this information. You're gonna want to read all of the threads in my signature so you can familiarise yourself with this device, and so you don't ask a question that's already been asked and answered a million times before.
Please post your hboot version, you'll find that in your bootloader screen.
You said earlier that you have s-off, why it s-on now?
Sent from my Evita

Evita pvt ship s-on
HBOOT-2.14.0000
Earlier mistaken s off written
Sent from my HTC One X using Tapatalk

Have you read the threads I mentioned?
Sent from my Evita

First I have to root it for cid change whts the procedure in this situation??
Sent from my HTC One X using Tapatalk

You need to use the 3.18 root method. Full instructions in my How-To Guide For Beginners thread.
Sent from my Evita

recovery
when i follow the procedure of rooting...when it goes to recovery screen (white one) its wait for 5 to 8 seconds and then restart normally..i can't goto recovery ..why??

That doesn't really make sense. The recovery screen isn't white, are you talking about the bootloader? And can you please be more specific about what's happening? I can't help you if you're giving vague two sentence posts like that.
Sent from my Evita

twrp
when i install twrp 2.7..after enter the recovery mode white htc scree appears...when i install twrp 2.2.0..on recovery it opens but touch screen don't works no button works just power button works which locks the twrp...can u send me valid link of twrp 2.7 because at twrp website at 99% downloading stops...

Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita

details of my evita
timmaaa said:
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?

jezi251 said:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
imei: xxxxxxxxxxxxxxxx
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
Click to expand...
Click to collapse
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita

rom
timmaaa said:
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
Click to expand...
Click to collapse
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..

jezi251 said:
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
Click to expand...
Click to collapse
I actually meant do you want a Sense ROM or an aosp ROM? Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Our dev sections are as follows:
One XL Android Development (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (aosp ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Have a look through the available ROMs and pick one you think will suit you.
Sent from my Evita

evita
thanks buddy

recovery
jezi251 said:
thanks buddy
Click to expand...
Click to collapse
i want to update my recovery from 2.7.0.0 to 2.7.1.0..when i insert fastboot flash recovery openrecovery-twrp-2.7.1.0 in CMD
error:cannot open 'openrecovery-twrp-2.7.1.0'...
because i want to install A.P rom or carbon or candy cat..
justnow i have 4.1.1 stock version,s-off,tempered, hboot 2.15
help me!!
when i try to install any rom by twrp 2.7.0.0 it gives error ..only cm11 snapshot installs but sometimes it hangs ...so i restore to 4.1.1...

Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita

recovery
timmaaa said:
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
Click to expand...
Click to collapse
i have also tried with .zip ext but it not works

[Q] Super CID and S-OFF not working (3.16.111.10, HBOOT 2.15)

Hey Everyone,
after I nearly bricked my One S4, I now would like to flash any custom rom.
Unfortunately, I can't change my CID to 11111111 and also I can't get S-off.
I tried / made the following:
1. I got root & unlock.
2. I tried to change the CID with ADB-push etc. - for some strange reason, I can write the changed mmcblk0p4 to the dev-folder, but immediately after I have written it (no write error!) and if I reopen it - no matter with a root explorer or by pulling it via ADB it has not changed.
I also tried to copy the file from the SD with a root explorer to the folder - same thing, copy works and immediately after it, the old CID is inside.
3. For obtaining S-off I tried all available options, the appropriate version of Moonshine (which stucks with pages and pages of dots - as far as I remember after step 3) and also Rumrunner 0.5 - which says I should update to a newer version.
Facepalm is no option as it is only for SuperCID.
Has anyone an Idea what I could do?
Here is additionaly the fastboot getvar all:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.15.50.05.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...............
(bootloader) imei: ..............
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4181mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Regards & thanks,
Matthias

http://forum.xda-developers.com/showthread.php?t=2558334
Sent from my One S using XDA Premium 4 mobile app

Bad.Fish said:
http://forum.xda-developers.com/showthread.php?t=2558334
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope - I told already in my first post:
3. For obtaining S-off I tried all available options, the appropriate version of Moonshine (which stucks with pages and pages of dots - as far as I remember after step 3) and also Rumrunner 0.5 - which says I should update to a newer version.
Click to expand...
Click to collapse
Any other ideas?

I was in your shoes until I found the link I posted. Maybe you didn't follow directions for rumrunner properly. Use rumrunner downloads from that link and try again. Won't hurt
Sent from my One S using XDA Premium 4 mobile app

Bad.Fish said:
I was in your shoes until I found the link I posted. Maybe you didn't follow directions for rumrunner properly. Use rumrunner downloads from that link and try again. Won't hurt
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the same problem. I can't get S-OFF after unlocking bootloader and rooting. Same Hboot (2.15), tried rumrunner: on Windows it says I need to download updated version, on Ubuntu it won't go past pouring (1). Also tried firewater without success.
I was going to flash ViperOne S 3.2.0 after getting S-OFF. Should I try to flash it before getting S-OFF? Thanks for help!
(My software version is 3.16.401.10)

ZioRò said:
I have the same problem. I can't get S-OFF after unlocking bootloader and rooting. Same Hboot (2.15), tried rumrunner: on Windows it says I need to download updated version, on Ubuntu it won't go past pouring (1). Also tried firewater without success.
I was going to flash ViperOne S 3.2.0 after getting S-OFF. Should I try to flash it before getting S-OFF? Thanks for help!
(My software version is 3.16.401.10)
Click to expand...
Click to collapse
I have flashed 3.1.3 yesterday with a unlocked device and then extracted the hboot2.15 from this rom and flashed it afterwards again.
It runs so far good!
And this with S-On and without SuperCID.
The Hboot is in the folder "kernel" of the ZIP file.
Nevertheless - S-Off and SuperCID would be cool.
BTW - I tried rumrunner again (3-4 times) with a very detailled following up of the requirements listed on the website etc. Did still not work.
Regards,
Maeffjus

Maeffjus said:
I have flashed 3.1.3 yesterday with a unlocked device and then extracted the hboot2.15 from this rom and flashed it afterwards again.
It runs so far good!
And this with S-On and without SuperCID.
The Hboot is in the folder "kernel" of the ZIP file.
Nevertheless - S-Off and SuperCID would be cool.
BTW - I tried rumrunner again (3-4 times) with a very detailled following up of the requirements listed on the website etc. Did still not work.
Regards,
Maeffjus
Click to expand...
Click to collapse
Did you flash directly from TWRP? Thanks!

ZioRò said:
Did you flash directly from TWRP? Thanks!
Click to expand...
Click to collapse
The ROM yes, the boot is a img file - you have flash it with fastboot (fastboot flash boot xxxhbootxxx.img - however the file name is)

Maeffjus said:
The ROM yes, the boot is a img file - you have flash it with fastboot (fastboot flash boot xxxhbootxxx.img - however the file name is)
Click to expand...
Click to collapse
Managed to flash the rom! It's awesome, so many customizations available
Anyway, I'll try to S-Off again and let you know..

Maeffjus said:
I have flashed 3.1.3 yesterday with a unlocked device and then extracted the hboot2.15 from this rom and flashed it afterwards again.
It runs so far good!
And this with S-On and without SuperCID.
The Hboot is in the folder "kernel" of the ZIP file.
Nevertheless - S-Off and SuperCID would be cool.
BTW - I tried rumrunner again (3-4 times) with a very detailled following up of the requirements listed on the website etc. Did still not work.
Regards,
Maeffjus
Click to expand...
Click to collapse
I finally managed to get S-Off some days ago. It was just due to my antivirus, Bitdefender. Even though I disabled it, any way to s-off wouldn't work. Uninstalled it and then ran Rumrunner again. Everything went fine!!

Did you try moonshine S-OFF?For your Firmware and cid no: http://moonshine.io/download/di7ki1txf7jq.html
And instructions:
http://forum.xda-developers.com/showthread.php?t=2325590

Unfortunately both did not work AGAIN - I disabled the AV software and disabled the services etc as well.
Rumrunner says Error und Moonshinhe runs forever (see attachement).
Any Ideas?

Maeffjus said:
Unfortunately both did not work AGAIN - I disabled the AV software and disabled the services etc as well.
Rumrunner says Error und Moonshinhe runs forever (see attachement).
Any Ideas?
Click to expand...
Click to collapse
Read moonshine instructions carefully and try again.

hmgurbuz said:
Read moonshine instructions carefully and try again.
Click to expand...
Click to collapse
I really really did - it is not that complicated to foolow them up - for instance, i have never ever installed the HTC Sync Manager (Laptop is one month old)

Remove all of antivirus programs.It should if you are on 3.16.111.10