Related
I have an HTC One (AT&T)
Originally, I s-offed it, unlocked bootloader and converted to a GPE HTC One, thereby changing the CID to GOOGL001
Like an idiot, I s-oned again, only after flashing CM11.
Now, when I try to s-off again, it fails, even though I am on HBOOT 1.54
Whenever I try to flash back an RUU or GPE, it also fails. Am I stuck?
arsrattan said:
I have an HTC One (AT&T)
Originally, I s-offed it, unlocked bootloader and converted to a GPE HTC One, thereby changing the CID to GOOGL001
Like an idiot, I s-oned again, only after flashing CM11.
Now, when I try to s-off again, it fails, even though I am on HBOOT 1.54
Whenever I try to flash back an RUU or GPE, it also fails. Am I stuck?
Click to expand...
Click to collapse
What's the Error message you're getting when trying to S-Off and which Tool are you using (rurunner?)
Frask3r said:
What's the Error message you're getting when trying to S-Off and which Tool are you using (rurunner?)
Click to expand...
Click to collapse
FIXED!
I flashed "Guru_Reset_M7_2.24.401.8.zip" which surprisingly didnt result in an error, after which i ran rumrunner again and got the following output:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your dev
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (27/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (27/120)
Waiting for device
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
pouring (1)............................
pouring (2).........
Waiting for ADB (27/120)
Waiting for device
All Done, hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
I hope this helps somebody with a similar problem, but thank you for your help!
arsrattan said:
FIXED!
I flashed "Guru_Reset_M7_2.24.401.8.zip" which surprisingly didnt result in an error, after which i ran rumrunner again and got the following output:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your dev
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (27/120)
Device detected.....................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (27/120)
Waiting for device
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
pouring (1)............................
pouring (2).........
Waiting for ADB (27/120)
Waiting for device
All Done, hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
I hope this helps somebody with a similar problem, but thank you for your help!
Click to expand...
Click to collapse
I can confirm this working as it helped me with a similar problem a few days ago.
Good Guy Google:good:
EDIT: Remember: Disable Fast Boot in your ROM's Power Settings while using rumrunner. If Fast Boot is enabled rumrunner WILL NOT WORK. This is what did it for me in some cases. Maybe you can avoid the reset with Guru then
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.
==================== 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 (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (54/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
Click to expand...
Click to collapse
What's Wrong.. ? I already have the latest package installer..
Hi ! My htc one was in service, change main board and came back with last hboot 1.56 and stock 4.4.2 ,I have unlock boot loader ,costum Rom insertcoints last, I tried s-off from rumruner,monsine,firwather, I tried everything, please help to get s-off.
costinn9 said:
Hi ! My htc one was in service, change main board and came back with last hboot 1.56 and stock 4.4.2 ,I have unlock boot loader ,costum Rom insertcoints last, I tried s-off from rumruner,monsine,firwather, I tried everything, please help to get s-off.
Click to expand...
Click to collapse
could i ask why you think you need s-off ? It seems you have done everything you can to your phone already
clsA said:
could i ask why you think you need s-off ? It seems you have done everything you can to your phone already
Click to expand...
Click to collapse
I need s off to change firmware to 4.19.401.11 now I have 4.19.401.9
costinn9 said:
I need s off to change firmware to 4.19.401.11 now I have 4.19.401.9
Click to expand...
Click to collapse
your firmware is fine
clsA said:
your firmware is fine
Click to expand...
Click to collapse
I want the firmware because is better for my region, please help to get s off
costinn9 said:
I want the firmware because is better for my region, please help to get s off
Click to expand...
Click to collapse
theirs almost no difference in the 2 firmwares .. your wasting your time
Firewater is your only real option ... if it's not working move on
What about with these specs:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Will I be able to acheive S-off with Firewater or am I just wasting my time?
I want to upgrade my firmware, I am having alot of problems with my cell data that will turn off and then I have to reboot the phone to get it to turn back on.
I wish I could run GPE edition with Root for 4.4.4 but I do not know how to accomplish this or GPE edition (rooted) for Lollipop but all the roms demand that I have upgraded firmware. Please give me advice
fc3211 said:
What about with these specs:
** Tampered **
** unlocked **
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RaDIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014, 09.32.41.0
Will I be able to acheive S-off with Firewater or am I just wasting my time?
I want to upgrade my firmware, I am having alot of problems with my cell data that will turn off and then I have to reboot the phone to get it to turn back on.
I wish I could run GPE edition with Root for 4.4.4 but I do not know how to accomplish this or GPE edition (rooted) for Lollipop but all the roms demand that I have upgraded firmware. Please give me advice
Click to expand...
Click to collapse
Firewater has been discontinued and will no longer work. But as your on hboot 1.56 you should try rumrunner :good:
Danny201281 said:
Firewater has been discontinued and will no longer work. But as your on hboot 1.56 you should try rumrunner :good:
Click to expand...
Click to collapse
Thanks. I am currently using OmniRom 4.4.4 but on the rumrunner instructions it says to disable fastboot inside of settings > power
But I do not have a fastboot option in there or in any other menu item. Is it okay to proceed?
fc3211 said:
Thanks. I am currently using OmniRom 4.4.4 but on the rumrunner instructions it says to disable fastboot inside of settings > power
But I do not have a fastboot option in there or in any other menu item. Is it okay to proceed?
Click to expand...
Click to collapse
I guess so most likely it's disabled by default or removed all together. Ideally though you should make a backup of your current Rom and flash a stock Rom. But there's no harm in trying with your current rom. It will either work or it won't but it shouldn't damage your phone in any way. :good:
OmniROM is based on stock Android, the fast boot feature is in Sense-only
fc3211 said:
Thanks. I am currently using OmniRom 4.4.4 but on the rumrunner instructions it says to disable fastboot inside of settings > power
But I do not have a fastboot option in there or in any other menu item. Is it okay to proceed?
Click to expand...
Click to collapse
Stock rooted Rom is here if you need http://forum.xda-developers.com/showthread.php?t=2676986
Danny201281 said:
Stock rooted Rom is here if you need http://forum.xda-developers.com/showthread.php?t=2676986
Click to expand...
Click to collapse
Thanks! I have been up for 7 hours working with different ROMS that have all failed.
Now let me try the one you have linked here. I want the deodex version, yes?
fc3211 said:
Thanks! I have been up for 7 hours working with different ROMS that have all failed.
Now let me try the one you have linked here. I want the deodex version, yes?
Click to expand...
Click to collapse
odex or deodex I don't think matters to much. Aslong as its thecorrect stock rom for your firmware and its rooted :good:
---------- Post added at 05:06 PM ---------- Previous post was at 05:01 PM ----------
There's also this one. This is a true stock rom with the option to install with root http://www.htc1guru.com/2014/03/att-ruu/
Here is my most recent failure: (Using Venom 6.0.2)
Code:
[email protected] ~/Downloads/rumrunner_HTC_0.5.0 $ sudo ./soju
==================== 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 (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (17/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)................
pouring (2)...............
pouring (3)...............
pouring (4)................
pouring (5)...............
pouring (6)................
pouring (7)................
pouring (8)...............
Wait 30 seconds, power on device, pray, run rumrunner again.
---------- Post added at 10:25 AM ---------- Previous post was at 10:13 AM ----------
Aw.....Crap! (With the AT&T stock Rom)
Now it appears I am moving backwards........ Sheesh, this is so frustrating
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
[email protected] ~/Downloads/rumrunner_HTC_0.5.0 $
---------- Post added at 10:38 AM ---------- Previous post was at 10:25 AM ----------
Man....sorry for the rant. I am so frustrated by this because I dont understand it
I bought this phone USED 4 months ago and the battery is weak and I feel so foolish for buying a used phone that was probably for sale because the battery was dwindling and im the idiot that paid $200 for this
I feel like such a chump, such a sucker for wasting my money and now just want to at least upgrade the firmware because I am having troubles with the data connection just drops and I have to reboot the phone to restore the data.
ANd now I see they are selling this phone NEW for $200 at BEST BUY and I will probably just have to bite the bullet but I tell you this: I will never again be such a fool to buy a used cell phone, I need my head examined to make such a mistake.
Im really feeling crummy about this situation =(
And I am taking the 70-410 exam on Monday, should be studying for that but went off on this tangent and would hate to FAIL at turning the S-OFF.
I work with Linux so am no stranger to frustration and hours of modifications to get things working.....but this here might have me licked
I fix everyone's computers for free in this town but this problem here has humbled me. S-ON =(
fc3211 said:
Here is my most recent failure: (Using Venom 6.0.2)
Code:
[email protected] ~/Downloads/rumrunner_HTC_0.5.0 $ sudo ./soju
==================== 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 (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (17/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)................
pouring (2)...............
pouring (3)...............
pouring (4)................
pouring (5)...............
pouring (6)................
pouring (7)................
pouring (8)...............
Wait 30 seconds, power on device, pray, run rumrunner again.
---------- Post added at 10:25 AM ---------- Previous post was at 10:13 AM ----------
Aw.....Crap! (With the AT&T stock Rom)
Now it appears I am moving backwards........ Sheesh, this is so frustrating
Code:
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
[email protected] ~/Downloads/rumrunner_HTC_0.5.0 $
---------- Post added at 10:38 AM ---------- Previous post was at 10:25 AM ----------
Man....sorry for the rant. I am so frustrated by this because I dont understand it
I bought this phone USED 4 months ago and the battery is weak and I feel so foolish for buying a used phone that was probably for sale because the battery was dwindling and im the idiot that paid $200 for this
I feel like such a chump, such a sucker for wasting my money and now just want to at least upgrade the firmware because I am having troubles with the data connection just drops and I have to reboot the phone to restore the data.
ANd now I see they are selling this phone NEW for $200 at BEST BUY and I will probably just have to bite the bullet but I tell you this: I will never again be such a fool to buy a used cell phone, I need my head examined to make such a mistake.
Im really feeling crummy about this situation =(
And I am taking the 70-410 exam on Monday, should be studying for that but went off on this tangent and would hate to FAIL at turning the S-OFF.
I work with Linux so am no stranger to frustration and hours of modifications to get things working.....but this here might have me licked
I fix everyone's computers for free in this town but this problem here has humbled me. S-ON =(
Click to expand...
Click to collapse
There is no exact science to using rumrunner unfortunatly, It does tend to be a little trial and error on the older hboots. It's normal to get some problems like this. Firewater was even worse. If you want super easy s-off then Sunshine app is the way to go although you do have to pay $25 to use it.
Well neither of these attempts actually were so bad the first appears to have worked (as in the exploit completed) But unfortunate didn't get you s-off.
In the second attempt it's telling you what to do
Code:
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) [B]flash an unsecure kernel that's compatible with your ROM [/B]and retry rumrunner (preferred and most reliable method).
2.) [B]flash a different rom[/B].
Try that rom again but with an Unsecured Kernel I recommend Bulletproof kernel. You'll want the 4.4.2 Kernel here http://www.androidfilehost.com/?fid=23329332407588021 :good:
Thanks man
Quick question: If somebody had never rooted the device from stock and had accepted the OTA update to Lollipop would the firmware be upgraded as well? Or is it the same firmware that stays?
---------- Post added at 12:11 PM ---------- Previous post was at 12:04 PM ----------
What is HTC's major intention anyway to make it so difficult to achieve S-off? If it was a closed-source OS like Apple I would understand but it seems like they went out of their way to make this so extremely difficult (Based on all the posts I have read).
Its these same guys that left the OS at 4.4.2 without updates until most recently. They didnt want to "be bothered" to make the code for 4.4.3 or 4.4.4 but yet they want to brickwall any independent programmers that are trying to add value to their product and not even getting paid?
---------- Post added at 12:21 PM ---------- Previous post was at 12:11 PM ----------
This phone was designed from the ground up with built-in functional obsolence...... They stuff the battery so far deep to make it almost impossible to replace knowing full well that this would be the achille's heel to make the phones fit for disposal in the trash bin after the 1 year warranty had expired., after the battery would fail.
Its bad for the environment and a disturbing trend with modern day electronics. I will not be buying an M8 knowing what these crooks are up to. They spit in the face of their customers when they DESIGN a product to expire like a carton of milk
fc3211 said:
Thanks man
Quick question: If somebody had never rooted the device from stock and had accepted the OTA update to Lollipop would the firmware be upgraded as well? Or is it the same firmware that stays?
Click to expand...
Click to collapse
If you update a phone via official OTA updates the firmware will be updated as well as the rom.
What is HTC's major intention anyway to make it so difficult to achieve S-off? If it was a closed-source OS like Apple I would understand but it seems like they went out of their way to make this so extremely difficult (Based on all the posts I have read).
Its these same guys that left the OS at 4.4.2 without updates until most recently. They didnt want to "be bothered" to make the code for 4.4.3 or 4.4.4 but yet they want to brickwall any independent programmers that are trying to add value to their product and not even getting paid?
Click to expand...
Click to collapse
This question has been asked more than once before and the answer quite simply is HTC really don't care if your device is s-on or s-off. You can even send your phone for warranty repair with s-off as long as the bootloader is Locked and the Software is stock and untampered with when they receive it they will repair the device according to your warranty. The Android OS is indeed open source and you do not need to have s-off to modify the OS all you need for that is an Unlocked Bootloader which as you probably know HTC offer as a free service :good:
So why do we have s-on and s-off? I hear you ask. There are two main reasons HTC supply phones with s-on.
Reason #1 - To safe guard them as a manufacturer, against false warranty claims. It's very difficult to do any pertinent damage to a phone that is s-on. As the major Partitions that house the devices firmware are protected by the s-on. With s-off you can if your not careful completely brick your device, and why should HTC honor the warranty in such a case. If everyone who gains s-off and flashes things wrecklesly and borks their device can just send for a replacement under warranty where would that leave HTC. They'd be bankrupt in a few years.
Reason #2 And as far as i can tell the main reason we have s-on. To sell more handsets HTC need to have supply contracts with all the major carriers (Orange, O2, H3G and T Mobile and so on) Carriers demand that these devices be supplied with s-on. Because with s-off we have the power to change the firmware. Completely rebranding or debranding a device without there permission or consent. The carriers don't like this so to keep them happy HTC supply there devices with s-on
And just to expand on this, The truth is although contrary to popular belief you do not need s-off to update your firmware. As long as you use HTC signed firmware from OTA updates and you relock your bootloader you can flash firmware UPDATES manually through fastboot.
The advantages of s-off are, You can flash firmware without relocking your bootloader. You can also downgrade firmware which is not possible with s-on, and you can flash customized firmware packages that aren't signed by HTC. Also you can change the CID and MID of your device allowing you to rebrand the phone. You can also sim unlock without a sim unlock code and many more wonderful things
This phone was designed from the ground up with built-in functional obsolence...... They stuff the battery so far deep to make it almost impossible to replace knowing full well that this would be the achille's heel to make the phones fit for disposal in the trash bin after the 1 year warranty had expired., after the battery would fail.
Its bad for the environment and a disturbing trend with modern day electronics. I will not be buying an M8 knowing what these crooks are up to. They spit in the face of their customers when they DESIGN a product to expire like a carton of milk
Click to expand...
Click to collapse
I do agree that most electronic devices these days are designed to fail though. And in most cases it's normally cheaper to replace than to repair. Which I think is wrong. The electronic industry has become a bit of a throw away society and I think its somthing that should be more tightly regulated. :good:
fc3211 said:
What is HTC's major intention anyway to make it so difficult to achieve S-off? If it was a closed-source OS like Apple I would understand but it seems like they went out of their way to make this so extremely difficult (Based on all the posts I have read).
Click to expand...
Click to collapse
Well see that is what you are missing. HTC distro is closed sourced. Sense is Closed sourced. Heck even android is closed sourced except for the AOSP project, and even some of those aspects are closed.
fc3211 said:
I bought this phone USED 4 months ago and the battery is weak and I feel so foolish for buying a used phone that was probably for sale because the battery was dwindling and im the idiot that paid $200 for this
I feel like such a chump, such a sucker for wasting my money and now just want to at least upgrade the firmware because I am having troubles with the data connection just drops and I have to reboot the phone to restore the data.
ANd now I see they are selling this phone NEW for $200 at BEST BUY and I will probably just have to bite the bullet but I tell you this: I will never again be such a fool to buy a used cell phone, I need my head examined to make such a mistake.
Im really feeling crummy about this situation =(
Click to expand...
Click to collapse
Sorry you had such a bad experience buying a used phone. I myself have both bought and sold used phones without any regrets to speak of.
My wife / Daughter / and Granddaughter are all using Samsung Note 2 phones I bought used without any problems (replaced one battery). I have bought and sold an M7 and 3 iPhones that all looked and worked flawlessly. I have also bought/sold an LG Optimous G that was in perfect working condition.
I guess it's just luck really ... the M7 I sold had the pink camera issue and I warned the buyer and they did not care at all.
As for the S-off issue I had best luck with hboot 1.54 and stock rooted 3.x software, ARHD 31.6 if i recall.
Hello all, so i want to s-off my HTC One, i tried everything, but still cant get s-off, my CID 9001, android 4.4.2, unlocked bootloader, phone is rooted, firewater shows whelp, any ideas for my situation?
Change ur kernel for elementalx 14.11 not other must be this one and use firewater. When firewater ask u to write " yes" do it with BIG leeter "Y" like this : Yes
Edit : dont forget to have Internet connection
Good luck ?
pawslo1984 said:
Change ur kernel for elementalx 14.11 not other must be this one and use firewater. When firewater ask u to write " yes" do it with BIG leeter "Y" like this : Yes
Edit : dont forget to have Internet connection
Good luck ?
Click to expand...
Click to collapse
I'm still get whelp...
Make a photo and show me please
Wysłane z mojego HTC One przy użyciu Tapatalka
pawslo1984 said:
Make a photo and show me please
Wysłane z mojego HTC One przy użyciu Tapatalka
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\AsRock>adb reboot
C:\Users\AsRock>adb wait-for-device push firewater /data/local/tmp
4980 KB/s (4522136 bytes in 0.886s)
C:\Users\AsRock>adb shell
[email protected]:/ # su
su
[email protected]:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.7.24 ===========================
firewater 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 firewater 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.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]:/
Sorry m8 but probbaly memory chip is incompatible and there is no way to soff ur device at the moment ? If im wrong please correct me anyone
pawslo1984 said:
Sorry m8 but probbaly memory chip is incompatible and there is no way to soff ur device at the moment ? If im wrong please correct me anyone
Click to expand...
Click to collapse
Theres a photo
That way i wrote that THERE IS NO WAY TO S-OFF UR DEVICE AT THE MOMENT (for free) ur chip is incompatible so sorry dude i cant help U more