Database Info

[Q] Please help. Stuck in Bootloop!

Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:

You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium

craven667 said:
You are 1.27 boot your kinda stuck you have to soff and that's not easy with 1.27 some ruu need super cid and soff
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Thanks for the reply.
I figured this would be hard as I've tried alot already..
I read somewhere there was a way to get soff involving connecting a wire somewhere and it can be risky. Can you affirm this is the best bet to recover my device?
By the way when relocked bootloader gives me these details..
Radio-11.23.3504.07_M2
OpenADSP-v02.6.0.2226.00.0131
Using ADB CMD I discovered the Android Image is version: 3.32.707.1
I hope someone can give my a clue as to what my best bet is here.. at this point I just want a usable phone again.

There's a new unlock out there but I never used it unlocked 3 at hboot 1.18 sorry
Sent from my Sensation using xda premium

Shunun said:
Hi there.
Bootloader details are
***Unlocked***
PYRAMID PVT SHIP S-ON RL
HBOOT- 1.27.0000
eMMC- boot
Jan 13 2012, 17:33:34
I'm trying run a RUU which I downloaded and have had an
'ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
The error may be because my bootloader is unlocked? But when I try to re-lock it it shows the "security warning" below "re-locked"
and then the RUU gives me ERROR [140]: BOOTLOADER VERSION ERROR
The RUU I'm trying to use is called RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9 007.00U_10.51.9007.27_M3_release_198358_signed
Please help! I've been trying to Install MIUI all day and it is turning into a nightmare.. I don't want to lose this phone D:
Click to expand...
Click to collapse
the RUU you are using wont run...because you are s-on...right now based on your HBOOT ...you might have 3.32 firmware....and the RUU you are using has 1.35 firmware (see after WWE_<this is firmware> in the RUU name)...
that's why you are getting that bootloader error..
the best solution for your case is to use ICS RUU..
to get that i need your cid
steps to get cid
1.keep the phone in fastboot and connect it to pc (phone reads "fastboot usb")
2.go to your adb/fastboot folder and type
"fastboot getvar all" without quotes
and post all the results...except serial number and imei
I'll find you the correct RUU for you..which might/will avoid bootloop..after you gave me those details

Okay, I ran the command. Here is what I have.
C:\AndroidSDK\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.707.10
(bootloader) serialno: ************
(bootloader) imei: **************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.516s
C:\AndroidSDK\tools>
You might want to know that since trying that RUU I have also tried one called
RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_TW_3.32.709.108_R1_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251682_signed
It gave me ERROR [156]:IMAGE ERROR
Thanks for your help

please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem

So u know there's a kinda beta s-off but I would wait if it was me your call
Sent from my Sensation using xda premium

ganeshp said:
please edit your post by removing,,,the serial number and imei present in the list
also the other RUU...wont run because the cid's are not matching...and there is No ICS RUU ...yet in your case...
so the choice left is ...to run a custom rom ?
fine with you ?
this the guide ...you need to follow to get ARHD custom rom
guide to flash roms with S-oN
please follow this guide step by step...and you'll have a custom ROM by end of it
.That guide is wriiten by a friend of mine ...and i helped him to make it pretty noob-free...follow that guide and let me know ..if you got any problem
Click to expand...
Click to collapse
THANKS!!!
Through following your friends/your guide I was able to flash rom
rmk-pyramid-stock_ics_3.32.401.3-v1
I really don't understand why I couldn't do this before when I was using clockworkmod recovery... Although it may have been because I didn't flash the appropriate Boot.img..?
So from what I've read, being S-on on FW3.32 I cannot flash roms that aren't 3.32 as well, would that be correct?
I don't understand how I'm supposed to know which are 3.32 or not..
I really want MIUI still.
Perhaps you could provide link to the MIUI rom which is 3.32..? would it be the latest?
kind regards and thanks for you help and time

Any stable roms on xda......

Admin, please remove/delete this tread, I am starting a new one to fully address my issue...... Sorry about the inconvenience.

Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Running magio sense 5... Stable as they get. Sounds like you have other issues if you can't get viperxl to boot. What recovery version do you use?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
twrp 2.6.3.0. The viper rom is always good at android 4.1. When I upgrade my hboot to 2.15, viper rom for sense 5 still work, it's just not stable. After I upgraded to RUU 3.18 today, viper rom doesn't even boot.

Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Have you wiped everything before flashing?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did...... wipe data, cache, system, dev cache

For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
For hahas I just flashed viper on 2.15 hboot and it's working fine
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you RUU 3.18?

Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
Yes I ruu to 3.18 a while back, to play with the new cm roms. Now I'm using the 4.2.2 hboot (2.15 and the 3.18 radio)
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sigh, I'll see what I can do

I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app

31ken31 said:
I'd start over with ruu. And double manual wipe everything before install, after flash wipe cache n dalvik. And factory reset in twrp before first boot.
And verify md5 on rom your flashing, it would suck if your glitches are from a slightly corrupt download.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.

snake3276120 said:
I just RUU to 3.18 and flashing hboot 2.15 right now...I will check md5 on the rom. Thanks for all the advise.
Click to expand...
Click to collapse
after I flash hboot 2.15, the ruu becomes 5.08.111.2 ......

I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita

timmaaa said:
I think you're getting your terminology mixed up, do you mean the build number becomes 5.08.111.2?
Sent from my Evita
Click to expand...
Click to collapse
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.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.
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.

snake3276120 said:
After I ran the RUU 3.18 upgrade in this tread: http://forum.xda-developers.com/showthread.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.
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.
Click to expand...
Click to collapse
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.
Sent from my Evita

timmaaa said:
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.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for my broken English, and thanks for the reply...... I will start another tread to fully address my problem.

There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita

timmaaa said:
There's no need to start another thread, you're already getting help in here. The threads don't just get deleted, creating a new one just means you're duplicating the post which is unnecessary.
Sent from my Evita
Click to expand...
Click to collapse
Sigh,I have already started a new one... Please take a look at http://forum.xda-developers.com/showthread.php?p=46229767#post46229767

So to summarize and to be clear: It turns out the OP is having some issues possibly due to updating hboot, and not problems with the stability of the ROMs themselves.
I know the OP deleted the content in the top post and started another thread (which is in itself not the right way to go about things). But it was in pretty bad style to title this thread the way it is, and imply that the ROMs are unstable, when you don't even know what the root cause of the problems is. If you have flashed several ROMs, and having the same issue on all, its most probable the problem is not with the ROMs, but with something you did (or didn't do), or else a hardware issue.

HTC ONE S (S4) - Need Expert Assistance

Hi fellow XDA members. I am new to the HTC community so i can be considered as noob. A friend of mine gave me his HTC One S to try and fix it.
Currently i can get into the bootloader (its unlocked with HTC dev, and shows as tempered). I did a factory reset but this does not change anything. When i try to start the phone it sometimes loads correctly, but it can't last more that a minute in android. It freezes and starts rebooting several times. After that i can only shut it down through the bootloader.
These are the phone details:
(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: 3.16.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3987mV
(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
After a lot of reading over the pass 2 days i realised that this phone is an S4 version (vle and it has a 1,5 processor).
From what i see the previous owner has flashed an S3 rom to an S4 handset.
If this is the case, can the phone be recovered from the DEAD????:angel:

Pretty much from what I can tell SOL for now. Tampered with s-on means that it was S-off previously. Plus the 3.16 firmware can only be flashed with S-off. Currently there is method to S-off 3.16. The easiest way to fix most issues is with a RUU but since 3.16 firmware was leaked and not official, there is no RUU at this time either.
I had the same problem previously but I was able to send it back to tmob for a warranty exchange.
Sent from my HTC One S using XDA Premium 4 mobile app

mjsheldon4 said:
Pretty much from what I can tell SOL for now. Tampered with s-on means that it was S-off previously. Plus the 3.16 firmware can only be flashed with S-off. Currently there is method to S-off 3.16. The easiest way to fix most issues is with a RUU but since 3.16 firmware was leaked and not official, there is no RUU at this time either.
I had the same problem previously but I was able to send it back to tmob for a warranty exchange.
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply. I do have some good news and bad news.
Good news is that i have managed to flash a 3.16 RUU.exe for S4. Tampered has gone (relock is still present).:victory:
Bad news is that phone does not boot to android and when it does is only for a few seconds. The more time is left switched off, the more time it can last in android. Even with safe mode, it still reboots.
I guess is a hardware problem.:crying:

What happens when it boots. Full android then turns off or stuck on HTC white screen. Does it say any thin?
Sent from my CM 10.1 Motorola Xoom Wingray!

mjsheldon4 said:
What happens when it boots. Full android then turns off or stuck on HTC white screen. Does it say any thin?
Sent from my CM 10.1 Motorola Xoom Wingray!
Click to expand...
Click to collapse
It stucks on the HTC logo and it keeps rebooting until i turn it off through the bootloader.

original21 said:
It stucks on the HTC logo and it keeps rebooting until i turn it off through the bootloader.
Click to expand...
Click to collapse
Hi.
Looks like a hardware issue to my, but there is more things to try.
It's good you have ran 3.16.401.8 JB RUU. You can S-OFF your phone now.
Can you run fastboot getvar all again and paste it here. Just to make sure the firmware in RUU was flashed correctly. If it was your hboot should be 2.15 and radio 1.11.
Sent from HTC One S using android 4.2.2 sense 5

tominozh said:
Hi.
Looks like a hardware issue to my, but there is more things to try.
It's good you have ran 3.16.401.8 JB RUU. You can S-OFF your phone now.
Can you run fastboot getvar all again and paste it here. Just to make sure the firmware in RUU was flashed correctly. If it was your hboot should be 2.15 and radio 1.11.
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
I have a 2.15 hboot and 1.15 radio. Today I got an update for 3.16.401.9
Sent from my HTC One using XDA Premium 4 mobile app

So the phone's working now properly?
Sent from HTC One S using android 4.2.2 sense 5

tominozh said:
So the phone's working now properly?
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
No. I still have the same problems. When its in android (even safe mode)after a few minutes it starts rebooting. When it reboots it stays at the HTC logo.
Sent from my HTC One using XDA Premium 4 mobile app

tominozh said:
So the phone's working now properly?
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
Ok. I would try this. Run .8 RUU again. After that get root (or flash some jb 4.1.1 sense Rom) and flash unsecure kernel, like bulletproof for JB.
Then make sure you have supercid
and use facepalm method to get S-OFF. Then try downgrade to ics or upgrade your firmware to jb 4.2.2. I think it's worth a try.
Sent from HTC One S using android 4.2.2 sense 5

[Resolved] Problems updating X920d Android 4.3 version 3.15.707.4 from 2.33.707.3

Resolved!
Apparently it was due to the fact that I installed Xposed Framework that causes the update process to fail.
I try to manually update the OTA.zip via stock recovery and found out that the process stopped at
"assert failed apply_patch_check( /system/bin/app_process."
Click to expand...
Click to collapse
Further checks showed that Xposed replaced the app_process file and causes it to fail checksum. I then copied /system/bin/app_process.orig back to /system/bin/app_process.
After that, the update was a breeze. The recovery used was from 3.15.707.4 (extracted from OTA.zip).
I've also S-OFF and Super-CID during my testing process.
If your update process stops after 25%, usually some checksum error has happened. Use manual update to determine the error message.
________________________________________________________________________
I'm having a problem updating my Butterfly to Android 4.3 from 4.2.2
My current firmware is 2.33.707.3 and the upgrade version is 3.15.707.4.
On my current phone, I have unlock my bootloader, flash recovery to TWRP 2.6.3.0 as well as rooted it. Due to inexperience, I did not backup my original recovery.
As per gleamed from this forum, I've tried to flash recovery from other stock ROM to proceed with the OTA update.
Steps taken:
Clicked Install now on the OTA message
Phone reboots to recovery
Phone icon with Green exclamation mark appears
Bottom part blue progress bar appears
Upon 30 to 40% progress, the screen changes to Red exclamation mark and update is stopped.
Edit: Did a Factory reset, problem remains.
I've tried the following recovery from other stock ROM without success.
Recovery from 3.15.707.4 (extracted OTA zip in phone's Download folder)
Recovery from 1.19.707.1 (extracted from DLXB1_U_JB_45_hTC_Asia_WWE_1.19.707.1_V0.0)
Recovery from 2.28.709.2 (extracted from OTA_DLXB1_U_JB_50_S_hTC_Asia_TW_2.28.709.2-1.18.709.3)
Recovery from 1.12.707.1
Recovery from 2.33 (from @Bassie39's OTA collection)
Recovery from 2.28.709.3
I've searched high and low for stock Recovery from 2.33.707.3 but unable to locate it.
Any tips or suggestion apart from S-OFF and update firmware, PL99img.zip update via bootloader, look in the OTA collection?
Code:
Model: Butterfly x920d
Android Version: 4.2.2
HTC Sense: 5.0
Software number: 2.33.707.3
CID: 044
[I][B]Bootloader Menu[/B][/I]
*** TAMPERED ***
*** UNLOCKED ***
DELUXE_UB1 PVT SHIP [B]S-ON[/B] RH
[B]HBOOT-1.54.0000[/B]
RADIO-3A.28.306.09
OpenDSP-V10.120.274.0520
[B]OS-2.33.707.3[/B]
eMMC-boot 2048MB
Aug 16 2013
[B][I]Fastboot getvar all results[/I][/B]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 3A.28.306.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.33.707.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: x
(bootloader) imei: x
(bootloader) meid: x
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3856mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0c6295fdaf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
A list of posts with the same problem:
[Q] Help In Updating To 4.3 - Unsolved
Followed @bluheart suggestion - Not working

Try this buddy
Do everything as written.

bluheart said:
Try this buddy
Do everything as written.
Click to expand...
Click to collapse
@bluheart, How do I go from S-OFF to update my OTA? Is Rumrunner better?

Any help or advice would be very appreciated.
Sent from my HTC Butterfly using Tapatalk

Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.

What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk

kemikelx said:
What's the next step after having S-Off?
Sent from my HTC Butterfly using Tapatalk
Click to expand...
Click to collapse
Super cid
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.

abhinav.tella said:
After supercid flash the TW (Taiwan) firmware not the WWE (World Wide Edition) so that you get faster updates as this is a Taiwanese company. WWE gets updates a lot later (2-4 months later) so think about that.
Click to expand...
Click to collapse
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?

kemikelx said:
Yes, This means I have to change the CID to HTC__621? But would this affect my Carrier settings?
Click to expand...
Click to collapse
No, I have done this with my old Butterfly without any bad effects or signal problems.

bluheart said:
Firewater or Rumrunner are equally effective.
I liked Firewater as its very simple to use.
Click to expand...
Click to collapse
Firewater didn't work. Instead I used Rumrunner.

Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app

abhinav.tella said:
Hope things worked out, and also I hope you took my advice and switched to Taiwan RUU.
You don't have to change CID if you are supercid which is 11111 something like that, you can install any RUU.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?

kemikelx said:
I'm trying to find a way to install the Taiwanese RUU on my phone. Looking around this forum but some of the instructions are contradictory.
Any help or useful links to share?
Click to expand...
Click to collapse
Go to the unlock thread page 9, I posted a detailed S-Off procedure. Any further questions regarding TW firmware they can answer.

[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