Database Develop

Request to Revolutionary - Hboot 1.16.000

Since Hboot 1.16.000 is not supported by Revolutionary yet, I thought that maybe we can make a formal request via this thread.
Hopefully, the number of users with Hboot 1.16.000 is big enough to turn their attention towards the Incredible S Hboot 1.16.000.
So, how many of you want the - Inc S - Hboot 1.16.000 unlocked?
PS: If my idea seems out of line, you can just delete the thread.

katu2006 said:
Since Hboot 1.16.000 is not supported by Revolutionary yet, I thought that maybe we can make a formal request via this thread.
Hopefully, the number of users with Hboot 1.16.000 is big enough to turn their attention towards the Incredible S Hboot 1.16.000.
So, how many of you want the - Inc S - Hboot 1.16.000 unlocked?
PS: If my idea seems out of line, you can just delete the thread.
Click to expand...
Click to collapse
I'm guessing phones with hboot 1.16.000 are really new ones since i got mine about a month ago and it had hboot 1.13.000.

Yep, my inc S is 2 weeks old...

katu2006 said:
Yep, my inc S is 2 weeks old...
Click to expand...
Click to collapse
I'm sure it will not be long ;-D

katu2006 said:
Since Hboot 1.16.000 is not supported by Revolutionary yet, I thought that maybe we can make a formal request via this thread.
Hopefully, the number of users with Hboot 1.16.000 is big enough to turn their attention towards the Incredible S Hboot 1.16.000.
So, how many of you want the - Inc S - Hboot 1.16.000 unlocked?
PS: If my idea seems out of line, you can just delete the thread.
Click to expand...
Click to collapse
Ya,I do hope revolutionary will have support on hboot 1.16 too,wait for it
Sent from my HTC Incredible S using Tapatalk

My HTC IncS was manufactured in June/11.
My boot is H1.16...
I bought an XTC Clip. I receive today in my house.

I have HBOOT 1.16.0000 and S-ON.
no need to do S-OFF to put on custom ROM.
I got someone else to do it for me, he remote controlled my computer and typed in all the commands. I'm happily using cyanogenmod 7.
Sorry I can't tell you how to do it exactly, as I didnt do it myself.
If someone here knows a lot about fastboot etc, here is a few commands I think he tried to do. see if you can fill in the blanks.
First, unlock the bootloader at HTC dev site. you need to log in and follow steps. once that is done it will say s-on so don't panic!!! Then what he did is flash a custom recovery/bootloader so I can flash ROM'S and zips. I copied the ROM onto the root of the SD card and installed it using the interface and it worked.
When I did this it was *supposed* to work but it still did not boot. I couldn't boot any ROM's except a 'MiUi', but it was really buggy. So my friend got me to install cyanogenmod on my phone using the bootloader, he flashed the boot.zip from the MiUi to the phone and it booted up with cyanogenmod! Then he put back the previous boot.zip from cyanogenmod and it worked! dunno why, but something must've gave it a kick.
sorry if it's a bit confusing, but it is a long process and a lot of trial and error. be sure what you're doing. You do not need revolutionary hack to do it. ALso, everyone says you need S-OFF, this is not true, it only matters if you want to flash complex things such as RADIO's which are protected. But to access root files and to install custom ROM's it's fine.
Hopefully someone can fill in the blanks here and come up with steps on how to do it
good luck

Thanks for sharing with us. I've replied to your other thread.
Cheers

And I have replied back

Anyone tried rumrunner for radio s off?

Rumrunner has a tool for the HTC one v,wich is very similar hardware. It may work on the sensation xl.
Install a rom with an insecure kernel,and run the one v tool.
I tried it on htc flyer,no harm will be done if the tool doesn't work.
Just wanted to throw it out there if no one has tried it
http://rumrunner.us/
Sent from my HTC PG09410 using xda app-developers app

scotty1223 said:
Rumrunner has a tool for the HTC one v,wich is very similar hardware. It may work on the sensation xl.
Install a rom with an insecure kernel,and run the one v tool.
I tried it on htc flyer,no harm will be done if the tool doesn't work.
Just wanted to throw it out there if no one has tried it
Sent from my HTC PG09410 using xda app-developers app
Click to expand...
Click to collapse
I tried it and it didnt work for me. i sued it in Ubuntu.
I set it up just fine but it didnt s-off me.
i got s-off using the XL Multitool

alexfadhili2 said:
I tried it and it didnt work for me. i sued it in Ubuntu.
I set it up just fine but it didnt s-off me.
i got s-off using the XL Multitool
Click to expand...
Click to collapse
how far did it get,and what errors did it give you?
i assume the xl multitool is just intalling the patched hboot?

I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Sent from my Sensation XL using xda app-developers app

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Sent from my Sensation XL using xda app-developers app
Click to expand...
Click to collapse
Did you already have the patched hboot installed?
Sent from my HTC6435LVW using Tapatalk

Yes sir.
Sent from my Sensation XL using xda app-developers app

alexfadhili2 said:
Yes sir.
Sent from my Sensation XL using xda app-developers app
Click to expand...
Click to collapse
Then it probably worked, and you just do not know it. it is not installing a new hboot on the one v
If you install a stock hboot you may well find that you are still s off
If you do not want to do that, you can dump p7 for me and I can look at the radio flag
Sent from my HTC6435LVW using Tapatalk

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work
Click to expand...
Click to collapse
The same things EXACTLY happened to me.
I am on Runny-Kitkat 4.4.2 V8 and those are my data before and after the process:
*** UNLOCKED ***
RUNNYMEDE PVT SHIP S-ON
HBOOT-1.28.0006
RADOI-3831.18.00.26_M
eMMC-BOOT
Apr 24 2012,18:59:39
My output:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (3/120)
Waiting
Test 2: Booting device
Waiting for ADB (6/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit

Hasan.Z said:
The same things EXACTLY happened to me.
I am on Runny-Kitkat 4.4.2 V8 and those are my data before and after the process:
*** UNLOCKED ***
RUNNYMEDE PVT SHIP S-ON
HBOOT-1.28.0006
RADOI-3831.18.00.26_M
eMMC-BOOT
Apr 24 2012,18:59:39
My output:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (3/120)
Waiting
Test 2: Booting device
Waiting for ADB (6/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[TTTT********************************************************]
Press ENTER to exit
Click to expand...
Click to collapse
ahhhh,the tool did not run. the test 1 and test 2 reboots do not count.
when it works,the tools output should be this:
Code:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (18/120)
Waiting
Test 2: Booting device
Waiting for ADB (38/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (17/120)
Waiting for ADB (38/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1).....................
Waiting for ADB (39/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
[email protected]:~/Downloads$
you may need to be on a different rom. when i ran it on the flyer,i had similar issues until i installed a sense 4 ICS rom. it would not work on the flyer due to lack of a new enouf kernel since the xl went to ICS it should theoretically work.
if anyone feels adventurous,try it with different roms,and/or dump mmcblk0p7 and ill make sure the board layout is the same:
adb shell
su (if needed to get a # prompt)
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
upload the file that appears on your sd card and pm me a link to it

alexfadhili2 said:
I got no errors from it. Everything went well. It rebooted thrice and when it was done nothing had changed.
I had the exact same hboot.
The the fact that it roots as well didn't work.
Click to expand...
Click to collapse
This is my dump file.

[Q] Downgrade from 4.4.2 to 4.3 using Mac OS.

Hello Xda-Developers, im new in the Android world, since i've been an iPhone user since the original iPhone all the way to the iPhone 4 (then things got pretty boring with). I used to Jailbreak my iPhone to have a more flexible experience with it... about 8~9 months ago i bought my first Android, an HTC One (M7) and it worked like a charm and never wanted to look back to iPhone, UNTIL one day i made an OTA update to 4.4.2, i've been having troubles with the signal, it shows full bars, i have 3G signal, but it shows "No Service" and i can't make/receive calls/SMS, i've been searching for 2 weeks or so, on how to fix it and i even sent it to warranty, and had my Sim replaced... twice. The problem persists, reading further i found that many users have been having this issues (and others) since the Kit Kat Update... So i decided to go beyond the world of a normal user... i want to downgrade from 4.4.2 to 4.3 (by the way i'm a Mac user), before making this thread i've been looking other threads and forums to help me on how to do it This is my first post on XDA Developers. Trust me, i've been looking for answers everywhere, the most similar thread i found was this thread.
And at the end the guy went for a new device, so that thread didn't help me out that much.
What i was able to do (hey, at least its a start) is to Unlock the Bootloader via HTCdev.
i think i've read pretty much to know some terms already, also thanks to Lifehacker
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).

Update
hzlx said:
Hello Xda-Developers, im new in the Android world, since i've been an iPhone user since the original iPhone all the way to the iPhone 4 (then things got pretty boring with). I used to Jailbreak my iPhone to have a more flexible experience with it... about 8~9 months ago i bought my first Android, an HTC One (M7) and it worked like a charm and never wanted to look back to iPhone, UNTIL one day i made an OTA update to 4.4.2, i've been having troubles with the signal, it shows full bars, i have 3G signal, but it shows "No Service" and i can't make/receive calls/SMS, i've been searching for 2 weeks or so, on how to fix it and i even sent it to warranty, and had my Sim replaced... twice. The problem persists, reading further i found that many users have been having this issues (and others) since the Kit Kat Update... So i decided to go beyond the world of a normal user... i want to downgrade from 4.4.2 to 4.3 (by the way i'm a Mac user), before making this thread i've been looking other threads and forums to help me on how to do it This is my first post on XDA Developers. Trust me, i've been looking for answers everywhere, the most similar thread i found was this thread.
And at the end the guy went for a new device, so that thread didn't help me out that much.
What i was able to do (hey, at least its a start) is to Unlock the Bootloader via HTCdev.
i think i've read pretty much to know some terms already, also thanks to Lifehacker
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).
Click to expand...
Click to collapse
UPDATE:
I just rooted it with TWRP and SuperSU
also the bootloader has a ***TAMPERED*** flag (if this is somehow harmful, how can i remove it?)

hzlx said:
UPDATE:
I just rooted it with TWRP and SuperSU
also the bootloader has a ***TAMPERED*** flag (if this is somehow harmful, how can i remove it?)
Click to expand...
Click to collapse
Tampered is not harmful, just ugly to see. It's a flag for service to know your phone is not unlocked out of the box. You can just flash a 4.3 ROM, no need to s-off

hzlx said:
So... as i said before, im a Mac user, unfortunately i don't find much answers on how to do stuff with my HTC One and my Mac.
Let's get to the point:
I'd like to downgrade from 4.4.2 to 4.3 (the original HTC version, or a 4.4.2 stable custom version, whatever you think is better)
PS. Do i reeeeaaly need to S-Off and/or downgrade my HBoot?
i have:
*** Unlocked ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.000
RADIO-4A-25-3263-21
OpenDSP-v32.120.274.0909
OS-4.19.401.11
eMMC-boot 2048MB
Feb 26 2014, 12:32:09.0
my CID is HTC__405 (Italy)
Please remember i am on Mac OS X, i (guess) i cant use RUUs.
Im so Noob, so if you could give me steps in order or redirect me to other threads on how to do a step, i'd be sooo thankful. I'm sorry if there's already a thread solving my doubt please redirect me there (i swear i've been searching for 2 days).
Click to expand...
Click to collapse
Yes, s-off is required to downgrade. Ruu is possible with a mac if you use a ruu.zip instead of a ruu.exe. S-OFF is more difficult to achieve on hboot 1.56, so maybe you'll have to use a custom rom if you can't s-off.
If you already unlocked bootloader and rooted your phone, I assume you can use adb and fastboot from your mac. If not then read this thread: http://forum.xda-developers.com/showthread.php?t=1917237
Then s-off the phone using rumrunner or firewater.
There is also a discussion here about S-OFF and hboot 1.56: http://forum.xda-developers.com/showthread.php?t=2567727
If you can s-off you'll be able to downgrade using a ruu.zip from your mac.

donkeykong1 said:
Tampered is not harmful, just ugly to see. It's a flag for service to know your phone is not unlocked out of the box. You can just flash a 4.3 ROM, no need to s-off
Click to expand...
Click to collapse
So, i can flash any 4.3 ROM (regardless of my phones software version [4.19.401.11] and/or my CID)?
After this, will i be able to make OTA Updates?

hzlx said:
So, i can flash any 4.3 ROM (regardless of my phones software version [4.19.401.11] and/or my CID)?
After this, will i be able to make OTA Updates?
Click to expand...
Click to collapse
You can flash anything you like. If you flash stock rooted 4.3 ROM you will get OTA but you can't upgrade just like that. You need to relock your bootloader, flash stock recovery and stock kernel. On the other hand, you have great choice of custom kitkat ROMs which work great, so you can flash one of them. ARHD 53 would be my recomendation

alray said:
Yes, s-off is required to downgrade. Ruu is possible with a mac if you use a ruu.zip instead of a ruu.exe. S-OFF is more difficult to achieve on hboot 1.56, so maybe you'll have to use a custom rom if you can't s-off.
If you already unlocked bootloader and rooted your phone, I assume you can use adb and fastboot from your mac. If not then read this thread: http://forum.xda-developers.com/showthread.php?t=1917237
Then s-off the phone using rumrunner or firewater.
There is also a discussion here about S-OFF and hboot 1.56: http://forum.xda-developers.com/showthread.php?t=2567727
If you can s-off you'll be able to downgrade using a ruu.zip from your mac.
Click to expand...
Click to collapse
Thanks a lot!
So far i managed to Unlock bootloader (with a Tampered Flag), S-OFF with firewater on hboot 1.56 and root it via TWRP and SuperSU.
I cant find a RUU for my CID HTC__405 though i have this stock ROM and it says it can restore to stock radios (which hopefully will solve my problems)... stock radios will be restored now that i have S-Off... right?
and a last question... once i am back in 4.3 will i be able to download further OTA updates (say... when 4.4.3 comes out)? if not, what should i do now?

Stuck on boot scren htc one logo
I got stuck on the HTC Logo boot screen... i installed a 4.3 ROM via TWRP, im S-Off now and unlocked hboot 1.56 ... why am i stuck? i've been reading i need the correct kernels, but where do i find them and how do i install them?
PLEASE HELP :crying:

NEVERMIND
hzlx said:
I got stuck on the HTC Logo boot screen... i installed a 4.3 ROM via TWRP, im S-Off now and unlocked hboot 1.56 ... why am i stuck? i've been reading i need the correct kernels, but where do i find them and how do i install them?
PLEASE HELP :crying:
Click to expand...
Click to collapse
Nevermind i managed to solve it :fingers-crossed:

Did you check your md5's??? I've had a multitude of my friends phones get stuck on boot screen.. Tell them to check md5 and it works.. One, as others have said, I would suggest flashing a couple Roms. See what you like, if you don't like any of them, then ruu back to stock. Also what twrp are you using? Did the ROM you installed request for a certain recovery to be used? I'm a Mac user so I understand lol. But what ROM??
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF

pball52998 said:
Did you check your md5's??? I've had a multitude of my friends phones get stuck on boot screen.. Tell them to check md5 and it works.. One, as others have said, I would suggest flashing a couple Roms. See what you like, if you don't like any of them, then ruu back to stock. Also what twrp are you using? Did the ROM you installed request for a certain recovery to be used? I'm a Mac user so I understand lol. But what ROM??
Click to expand...
Click to collapse
i managed to solve it, i re installed this ROM which matches my CID (HTC__405), the ROM didnt ask me for any recovery to be used..... anyway.. so far i haven't had any luck fixing my first issue, which is that whenever i lose signal it wont reconnect, it will say "No Service" but still have 3G/4G working, i cant make/receive calls/SMSs.
Any idea on how to fix this issue?

hzlx said:
i managed to solve it, i re installed this ROM which matches my CID (HTC__405), the ROM didnt ask me for any recovery to be used..... anyway.. so far i haven't had any luck fixing my first issue, which is that whenever i lose signal it wont reconnect, it will say "No Service" but still have 3G/4G working, i cant make/receive calls/SMSs.
Any idea on how to fix this issue?
Click to expand...
Click to collapse
So, the issue is not resolved with custom ROM? I guess it's a hardware problem then

62 382926
donkeykong1 said:
So, the issue is not resolved with custom ROM? I guess it's a hardware problem then
Click to expand...
Click to collapse
Nope, before making this whole thread i sent it to warranty and they supposedly repaired it, i changed sim twice.
im going back further, trying 2.24.401.8 with android 4.2
Let's see if that works, or else i'll start trying custom ROMs... so far i've been using stocks.

hzlx said:
Nope, before making this whole thread i sent it to warranty and they supposedly repaired it, i changed sim twice.
im going back further, trying 2.24.401.8 with android 4.2
Let's see if that works, or else i'll start trying custom ROMs... so far i've been using stocks.
Click to expand...
Click to collapse
Well, good luck. I just want to say - if you have the same problem with more than one ROM, no matter if it's stock or modified there is a hardware issue.
Supposedly is what bothers me the most in your case. Maybe your service doesn't care for their customers. It wouldn't be the first

True ^^ I agree with @donkeykong1 If you've had two SIMs and all that......its a hardware issue that is malfunctioning....

pball52998 said:
True ^^ I agree with @donkeykong1 If you've had two SIMs and all that......its a hardware issue that is malfunctioning....
Click to expand...
Click to collapse
Ok... i'm just trying with this last ROM... if it doesn't work... what are the steps to go back to full stock (Locked, S-ON, remove TAMPERED, unrooted)? so i can send it back to warranty
Thanks @pball52998 & @donkeykong1

hzlx said:
Ok... i'm just trying with this last ROM... if it doesn't work... what are the steps to go back to full stock (Locked, S-ON, remove TAMPERED, unrooted)? so i can send it back to warranty
Thanks @pball52998 & @donkeykong1
Click to expand...
Click to collapse
You're s-off correct? Ive seen people not needing to go back s-on for warranty purposes. But pretty much if you want to go back to stock, its just ruu, it does it all for you. Takes you back Locked with factory recovery and full just straight stock.

pball52998 said:
You're s-off correct? Ive seen people not needing to go back s-on for warranty purposes. But pretty much if you want to go back to stock, its just ruu, it does it all for you. Takes you back Locked with factory recovery and full just straight stock.
Click to expand...
Click to collapse
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks again!

hzlx said:
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
Thanks again!
Click to expand...
Click to collapse
Okay, well a ruu can be placed on the internal memory.....but...... the way that I've always seen it done, or a lot of times is
Code:
./adb reboot bootloader
Code:
./fastboot oem rebootRUU
Code:
./fastboot flash RUU.zip
the RUU.zip could be named anything so you might have to rename the RUU or change the RUU.zip in terminal to what ever the foop you named it, although I wouldn't do the RUU with those instructions just yet.... Can someone else confirm it??

hzlx said:
Ok, so i know where to find some RUUs but i know using a mac i have to use a .zip, right?
my question is... how do i use a RUU.zip? do i install it placing it in the internal storage then use TWRP?
So far i haven't lost signal.
Thanks again!
Click to expand...
Click to collapse
you might want to reset your phone using a ruu before to make sure your issue is really related to an hardware defect.
This ruu.zip will reset your phone to stock 1.28.401.7 (android 4.1.2) and hboot 1.44.
Then if you see the phone still have the issue, remove the tampered flag and set the bootloader back to ''LOCKED'' using this tool. Then s-on and send for warranty repair/replacement. This procedure must be done before you take any ota that will update your phone to hboot 1.55 or the tampered flag will come back and you'll have to s-off again and redo the entire procedure.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
pball52998 said:
Okay, well a ruu can be placed on the internal memory.....but...... the way that I've always seen it done, or a lot of times is
Code:
./adb reboot bootloader
Code:
./fastboot oem rebootRUU
Code:
./fastboot flash RUU.zip
the RUU.zip could be named anything so you might have to rename the RUU or change the RUU.zip in terminal to what ever the foop you named it, although I wouldn't do the RUU with those instructions just yet.... Can someone else confirm it??
Click to expand...
Click to collapse
Make sure the ruu.zip is in the same folder where adb and fastboot are.
Code:
./adb reboot bootloader
or manually reboot the phone in bootloader using power + vol down
Code:
./fastboot oem rebootRUU
make sure ''RUU'' are capital letters
Code:
./fastboot flash name_of_ruu.zip
First time it will output a failed message, do the same command again:
Code:
./fastboot flash name_of_ruu.zip

[Q] S-OFF on HBOOT 1.57

Hello
Basically I'm attempting to S-OFF my HTC One so I can flash on different stock firmware, namely the GPE firmware. Simply put I can't seem to find a straight answer on how to achieve S-OFF on my HBOOT version. I've tried both Firewater and Rumrunner with no success. I attempted both on CM11 and an un-official CM12 ROM with zero success, all I get are messages telling me to switch my phone off and start again.
What is the most successful method to achieve S-OFF on the given HBOOT? Should I be using another ROM perhaps?

acnak said:
Hello
Basically I'm attempting to S-OFF my HTC One so I can flash on different stock firmware, namely the GPE firmware. Simply put I can't seem to find a straight answer on how to achieve S-OFF on my HBOOT version. I've tried both Firewater and Rumrunner with no success. I attempted both on CM11 and an un-official CM12 ROM with zero success, all I get are messages telling me to switch my phone off and start again.
What is the most successful method to achieve S-OFF on the given HBOOT? Should I be using another ROM perhaps?
Click to expand...
Click to collapse
Firewater + ARHD + Bulletproof kernel worked for a lot of people

clsA said:
Firewater + ARHD + Bulletproof kernel worked for a lot of people
Click to expand...
Click to collapse
ARHD version? I need S-off too:cyclops:

clsA said:
Firewater + ARHD + Bulletproof kernel worked for a lot of people
Click to expand...
Click to collapse
Hi friend, my hboot is 1.57 and i have the latest firmware which is 6.09.401.11 .
For making s-off with ARHD +Bulletproof combination, do i have to downgrade my firmware or hboot or will it work directly ?
thanks

clsA said:
Firewater + ARHD + Bulletproof kernel worked for a lot of people
Click to expand...
Click to collapse
Well Firewater has been discontinued so that's of little use, any other known methods/combinations?

Discontinued yes but it still works for some people. If it doesn't then go sunshine. It will cost you $25 but it will do compatibility tests first to see if it works

nateboi81 said:
Discontinued yes but it still works for some people. If it doesn't then go sunshine. It will cost you $25 but it will do compatibility tests first to see if it works
Click to expand...
Click to collapse
Can't see how it can work as it relies on some remote content. Any attempt to use it is hanging on the very first steps of initialization.
Regarding Sunshine I find so shocking to read everyone advising to go for it. $25 to get 100% access to our phone, that is just so ridiculous. And even if it's guaranteed.

TBagwell said:
Can't see how it can work as it relies on some remote content. Any attempt to use it is hanging on the very first steps of initialization.
Regarding Sunshine I find so shocking to read everyone advising to go for it. $25 to get 100% access to our phone, that is just so ridiculous. And even if it's guaranteed.
Click to expand...
Click to collapse
Well it depends on the urgency. Some need quick s-off to return device to stock for warranty, and that's cool I guess. Its worth it then. I on the other hand like some others need s-off to maybe convert to GPe to try out lollipop. However seeing as its only a matter of short time until its released for stock sense devices, the wait isnt bad at all...

Well it's currently easily the cheapest way to s off. You can take it to a shop that uses a java card and pay more. HTC like to lock their phones down good. Which for the average user is a good thing. Has lots of safeguards

TBagwell said:
Can't see how it can work as it relies on some remote content. Any attempt to use it is hanging on the very first steps of initialization.
Regarding Sunshine I find so shocking to read everyone advising to go for it. $25 to get 100% access to our phone, that is just so ridiculous. And even if it's guaranteed.
Click to expand...
Click to collapse
If you find it so shocking then blame HTC, and other OEM's because is their fault that our devices are locked. This guy's found a vulnerability in these devices and with hard work, money invested and free time lost they put up this amazing tool that help us.
If you work for something and invest money and time in that then you would give it for free?
I say thanks to them because at least even if is paid EXISTS. They could renounce to develop S-off and then we won't have to blame them that they sell us freedom for our devices.

cyrusct82 said:
If you find it so shocking then blame HTC, and other OEM's because is their fault that our devices are locked. This guy's found a vulnerability in these devices and with hard work, money invested and free time lost they put up this amazing tool that help us.
If you work for something and invest money and time in that then you would give it for free?
I say thanks to them because at least even if is paid EXISTS. They could renounce to develop S-off and then we won't have to blame themthat they sell is freedom to our devices.
Click to expand...
Click to collapse
I am usually part of those who support devs for their good work by donating. But 25$ is for me way to much for supporting such a hack. I am not saying their work is not good, it looks quiet nice in fact. If they would make their first price around 5$ and still opened to donations it would be much more reasonable. But hey, that's just my opinion.
On a side note I totally agree with you on the HTC responsibility in that, they totally suck and I think it's the last time I go for their devices. This S-OFF thing is so much giving me the feeling I don't own the device I paid for... (not to mention I have a barely usable camera)

Yes, I agree. I would be happy to pay if it were something along the lines of $5-10, but $25 is a bit too much for myself.
Firewater doesn't work anymore for me either, makes sense given that it relies on some content stored on their servers.

[SOLVED] Stock O2 UK Nandroid or Zip?

Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.

fade2black101 said:
Hi guys
Basically I need to send my device into HTC for repair. It is S-OFF and I have a stock HTC European _001 rom on it. I really really need to restore to the UK O2_001 stock rom and get back to S-ON to avoid any possible issues with the warranty.
The problem is I can't find any O2 UK zips or nandroid backups to flash. For some reason the RUU files do not work for me, and I really don't have the time to be troubleshooting this.
I would really appreciate it if someone could upload a nandroid backup that I can use very soon? Otherwise I'll need to stick with the unbranded HTC Europe rom and risk them knowing I've unlocked the device.
Thanks for any help.
Click to expand...
Click to collapse
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware

nkk71 said:
if you want to follow my guide http://forum.xda-developers.com/showthread.php?t=2541082
Files you'll need are in post #7 under "HTC One M7_UL - modelid=PN0710000 - cidlist=O2___001,O2___102"
EDIT: there's also this RUU http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353143_signed_2.exe
but as mentioned in my guide, i don't encourage going s-off to s-on on newer firmware
Click to expand...
Click to collapse
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.

fade2black101 said:
Hello, thanks for that
Unfortunately I can't seem to downgrade the bootloader. I'm on 1.61.
Not entirely sure what to do now.. Will it be possible to achieve S-ON again and lock the bootloader without downgrading the hboot?
I don't really have time to spend ages on this, as the phone will be getting collected on Friday and I'm busy with work. I also don't really have time to troubleshoot the 100000 reasons why RUU.exe files aren't working for me and why I can't downgrade the bootloader. May just have to send it in unlocked and hope for the best.
Click to expand...
Click to collapse
so quick and dirty? (and hope for the best)... did you use sunshine to s-off? before i post the steps.

haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time

fade2black101 said:
haha
And yes I did. And I plan to use it again when I get phone back. Let me know your suggestion and I'll give it a go when I have some time
Click to expand...
Click to collapse
okay cool, i only asked because sunshine will work again (without needing to pay again), in case that infamous "tamper detected - rebooting" happens (shouldnt in your case but just in case it does)
gimme a few minutes, and i'll post instructions with links....

Thanks
I will check this out tomorrow when I have some time

fade2black101 said:
Thanks
I will check this out tomorrow when I have some time
Click to expand...
Click to collapse
okay, should be easy enough:
1) download Guru_Bootloader_Reset_1.0.zip and put it on your virtual storage
2) download 4.19.401.9-TWRP2633_combined_nowipe.zip
if need be change cid to a compatible one:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
flash firmware
Code:
fastboot oem rebootRUU
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot flash zip 4.19.401.9-TWRP2633_combined_nowipe.zip
fastboot reboot-bootloader
set back O2 UK cid:
Code:
fastboot oem writecid O2___001
fastboot reboot-bootloader
3) go to RECOVERY (it should be TWRP 2.6.3.3 from the file above) and run the Bootloader Reset
--> remove TAMPERED
--> set LOCKED
4) go back to bootloader, and check it says LOCKED, and no more TAMPERED
5) download RUU_4.20.206.16.EXE
and run it
(if it "exits" for some unknown reason, make sure you have this installed vcredist)
6) reboot the phone to make sure it boots up fine, do not take OTA updates
7) if you really insist, go s-on
Code:
fastboot oem writesecureflag 3
8) reboot three times (do not take any OTAs, especially above 6.xx), and make sure no TAMPERED is triggered

nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!

fade2black101 said:
nkk71
You're a star! Thank you so much for that. After hours spent fumbling about I spent 20 minutes following your instructions today and everything worked perfectly. The Visual C++ file you suggested did the trick too, even after I installed several other (wrong ones) yesterday. Really happy this is finally sorted
Just a quick question. I haven't gone back to S-ON yet. I think it may not be neccessary for the warranty, but maybe I shouldn't risk it as I can always just gain S-OFF again via Sunshine once I get the phone back (unless they inexplicably change the motherboard). I'm wondering if there is a high risk of bricking my device if I run that S-ON command?
Cheers once again!
Click to expand...
Click to collapse
there's no risk in bricking using that "fastboot oem writesecureflag 3" command to set s-on; the RUU would have set everything back to stock; if in the unlikely event the "TAMPERED" comes back, you'll need to s-off again, and use my guide with the 1.xx RUU + nandroid method
as for sending it in S-OFF, it's really country/carrier/service centre/person specific.... from what i've seen UK is one of the most tolerant countries (some people have even sent the phone in with tamperd and running a custom rom, and still got the camera fixed)
but it's your call, i cant really say for sure how they would react.
and if all is good now, could you also edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks and good luck