Hello XDA-Users,
I have a Question for what I can't find any awnswer...
I have an International HTC One with CID T-MOB101, HBOOT 1.55 and I want to S-OFF.
I already unlocked via HTCDev and flashed a custom Rom.
But with rumrunners S-OFF method it failes every time.. I used many various custom roms, but with no it works.
I can't go back to really stock to try it then, because for this I need S-OFF...
Sometimes it poures 8 times and write then, I have to wait 30 seconds, pray, (...) and try it again. When I tried it again it fails again...
Another time it says you have to flash an other Rom or something else.
So I don't know what Rom to try for getting S-Off..
If someone knows how to fix it, or what Rom to try, write me please.
Please help me
Thanks.
I am having the exact same issue!
My Bootloader Info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3997mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried the rumrunner tool on 4 different PCs, each of them with Windows 7 Ultimate x86 or x64 and always on USB 2.0 port without any Hubs or something like that. The phone was always directly connected to an USB 2.0 port. I also tried different usb cables.
I always ran soju.exe as Administrator and accepted every Superuser request.
ROMs I tried it with: Stock Android 4.3 Sense 5.5, Android Revolution HD 41.0 and ViperOne 3.5.0
I even used an Ubuntu 13.10 Live CD but it never worked.
My bootloader is of course unlocked, TWRP 2.6.3.3 is installed and the phone is/was rooted on every rom I tried.
I attached the linux terminal log and the windows cmd log.
EDIT: I used the latest rumrunner v0.5.0.
Yep
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...
judufu said:
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...
Click to expand...
Click to collapse
try flashing this 4.3 sense 5.0 rom
http://www.scottsroms.com/downloads.php?do=file&id=466
and here's an even older one 4.1.2 you may try
http://www.scottsroms.com/downloads.php?do=file&id=442
Does it work for you?
judufu said:
Does it work for you?
Click to expand...
Click to collapse
I have had s-off since revone was released
Ok, I'll test it at the morning.
Thanks, hope it works
judufu said:
Ok, I'll test it at the morning.
Thanks, hope it works
Click to expand...
Click to collapse
you might want to read this
http://forum.xda-developers.com/showthread.php?t=2487888&page=55
reprekuc malay
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?
TheHellSite said:
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?
Click to expand...
Click to collapse
How do you mean it ??
judufu said:
How do you mean it ??
Click to expand...
Click to collapse
he's referring to this post that was removed
Originally Posted by maspro View Post
Woohoo, I'm a happy person right now.
I made a partition dump of my phone according to this guide: http://forum.xda-developers.com/showthread.php?t=2488772 and provided some additional information about my specific configuration and send it to the Rumrunner devs to see if it was possible to add support for S-OFF. After some emailing back and forth the last couple of days, I agreed to accept the risks and be a test case to see if it was possible to S-OFF my device, since my firmware was to new to make use of the existing exploits Rumrunner 0.5.0 is using. So we had a remote session together..... and a couple of minutes later my phone was S-OFF.
Don't ask me what the devs did, I looked at the adb screen, saw lots of commands and screen output flying around, but for the most part didn't understand it... Anyway my phone is still alive and I'm S-OFF.
Thx devs and I also made a donation (1HE93648R1560915F)!
Click to expand...
Click to collapse
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Great
TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Oh beatiful, when this is like you say...
Wait and hope for the best
Thanks.
TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Am i in the same boat as you? i'm Three (H3G_001) International.
Im getting the same problems as what you described earlier.
Just boot your device into bootloader and then run this command in terminal/cmd "fastboot getvar all".
If the following 3 lines match yours, you very likely are in the same situation.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-main: 3.63.111.3
This it says on my device:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I think some data are nonrelevant for S-Offing, but for completeness.
Hope there are something usefull data for the further process...
Related
Hello friends. First of all, I apologize if I am not very clear, but I have little knowledge of English, and to be faster I'll use a translator...
Since about a week ago, my HTC One Developer Edition is showing me errors with WiFi and Bluetooth. These are off steadily even when in use. At first I thought it was a failure of the last installed ROM (ARHD 40.1), but I've tried others such as CM11 without installing any mod and restore my latest nandroid backup, but I have had the same result.
Apart from changing the ROM all I remember doing is to update the firmware, so yesterday I upgraded to the new firmware version to see if solved, but still follows the failure. Do not think it's a hardware failure because the mobile is not second hand, has not suffered any drop and was always working perfectly, so I ask your help and attached the information that shows the phone using fastboot getvar all command if serving them for a diagnosis. Thanks in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3993mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
You are Soff. Why not reflash official dev ruu?
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
[email protected] said:
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
Click to expand...
Click to collapse
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
Well, thank you very much. Be right back after process.
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
I downgrade to hboot 1.44 and reflash the official ruu (RUU M7 JB UL 50 BrightstarUS WWE 1.29.1540.16), but still blinking on and off wifi and bluetooth.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3994mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s
Time to call HTC for warranty support. No other ideas.
Hey this is off topic but SaHiLzZ, is your name Sahil?
Sent from my HTC_PN071 using Tapatalk
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
Well, I bought this phone in the United States.... I live in Dominican Republic...
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
[email protected] said:
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
Click to expand...
Click to collapse
did u try changing some of the advanced settings i mentioned?
nkk71 said:
did u try changing some of the advanced settings i mentioned?
Click to expand...
Click to collapse
Yes, but I don't see changes. (Later, I change the "Keep WiFi on during idle" to Always), but just keeps running and then switching off when it want, and when it goes off, just says "activating", infinite loop until I restart.. Same for bluetooth.
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
@nkk71
Well, without ideas, I sent the phone to HTC America, for guarantee. I had to pay $ 70 shipping because I live in Dominican Republic (No HTC), but after 15 days I received my phone in perfect working (they did not even scratch), and by the way, apparently they changed my camera ... It's not purple! :laugh:
Thanks for all your help friends. :highfive:
So I'm relatively new to the whole rooting & roming scene. I did however root my HTC One recently, (S-On, Superuser, Unlocked bootloader through HTCDev) (Can't remember what recovery, running CWM at the moment). However somewhere through the process i lost some Pre-installed apps. I've tried searching, and installed apps through what's been posted on different sites, but they give me "app not responding" problems whenever i try to run them. I'm also a fan of the stock apps so wouldn't like to download "3rd party" app. So i was wondering if there is way to get them back. here's my environment variables/ whatever they are called if they help.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1a757b8b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Kasi!995 said:
So I'm relatively new to the whole rooting & roming scene. I did however root my HTC One recently, (S-On, Superuser, Unlocked bootloader through HTCDev) (Can't remember what recovery, running CWM at the moment). However somewhere through the process i lost some Pre-installed apps. I've tried searching, and installed apps through what's been posted on different sites, but they give me "app not responding" problems whenever i try to run them. I'm also a fan of the stock apps so wouldn't like to download "3rd party" app. So i was wondering if there is way to get them back. here's my environment variables/ whatever they are called if they help.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1a757b8b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
unlocking the bootloader removes them
you should be able to find them in any of the 4.3 roms
just extract them from the zip file under /system/apps and copy them to your phone sdcard and install them
clsA said:
unlocking the bootloader removes them
you should be able to find them in any of the 4.3 roms
just extract them from the zip file under /system/apps and copy them to your phone sdcard and install them
Click to expand...
Click to collapse
Thanks, will try this. My internet sucks so gotta wait.
Also got another question, is it advised to S-Off using rumrunner? / can i do it with my device?
Edit: worked! thanks, Thanked
Kasi!995 said:
Thanks, will try this. My internet sucks so gotta wait.
Also got another question, is it advised to S-Off using rumrunner? / can i do it with my device?
Edit: worked! thanks, Thanked
Click to expand...
Click to collapse
Yes by all means get s-off while it's still possable
your phone seems to have everything required
clsA said:
Yes by all means get s-off while it's still possable
your phone seems to have everything required
Click to expand...
Click to collapse
I've tried it twice now, disabled everything (antivirus, firewall etc), it pours 8 times then it fails, it gives this error in a separate command window after each pour,
"adbd cannot run as root in production builds"
any ideas?
Thanks again.
Edit: i did manage to google earlier on, it said something about write protection? but im rooted so i don't quite understand why im getting this error.
Kasi!995 said:
I've tried it twice now, disabled everything (antivirus, firewall etc), it pours 8 times then it fails, it gives this error in a separate command window after each pour,
"adbd cannot run as root in production builds"
any ideas?
Thanks again.
Edit: i did manage to google earlier on, it said something about write protection? but im rooted so i don't quite understand why im getting this error.
Click to expand...
Click to collapse
you need to flash a rom with an insecure boot.img/kernel
try something simple like Android Revolution HD 31.6 -> http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
clsA said:
you need to flash a rom with an insecure boot.img/kernel
try something simple like Android Revolution HD 31.6 ->"link to ARHD 31.6"
Click to expand...
Click to collapse
So i've flashed ARHD 31.6, but still no dice, still can't manage to s-off successfully, i've tried both the latest HTC drivers and earlier ones (3.0.0.007), Still can't manage it, any advice? followed the instructions to the last detail.
Has anyone else managed to recently S-off a HTC One International ed?
Edit: also tried on a different machine with no htc sync ever installed.
I cannot seem to get s-off with rumrunner. I'm rooted on hboot 1.55. I've tried on xp and Windows 8 on a few different pc's to no avail. I last followed a guide and did it on a live Ubuntu USB as my laptop runs the 64bit distribution. I get to a line that says "sanitizing, skunky rum" and then says wait. Then periods fill across the line and it sits for a while. Then several T's are displayed and the command prompt comes back up. S is not off.
I'm at a loss here. Anyone have any ideas? I've read pretty exhaustively and I'm not finding any solution.
Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Try this... It's actually really easy... Good luck
http://forum.xda-developers.com/showthread.php?t=2606577
Sent from my LG-D803 using xda app-developers app
I tried that. That resulted in the line of T's and did not give me s-off.
Sent via MobileBlast!
Bradlees said:
I tried that. That resulted in the line of T's and did not give me s-off.
Sent via MobileBlast!
Click to expand...
Click to collapse
Could be because you ran it on 64bit and it's stated on rumrunner 's site and in step one of my instructions to use a 32bit version. For some reason 64bit isn't supported. You don't have to install it just throw it on a disk and boot into the "try" mode.
Anyways, good luck
Sent from my LG-D803 using xda app-developers app
No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!
Bradlees said:
No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!
Click to expand...
Click to collapse
what's your "version-main"? or even better post a "fastboot getvar all" (excluding IMEI and s/n)
Bradlees said:
No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!
Click to expand...
Click to collapse
That sucks... The only other suggestion is something I was just informed of but didn't have to do myself.
In Ubuntu they had to open the Ubuntu software Centre, edit tab, software sources and make sure that "supported free and open source software" is selected.
Sorry wish I had more ideas
Sent from my LG-D803 using xda app-developers app
nkk71 said:
what's your "version-main"? or even better post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
version: 0.5
version bootloader: 1.55.0000
version baseband: 4A.21.3263.03
version cpld: none
version microp: none
version-main: 3.24.531.3
Bradlees said:
version: 0.5
version bootloader: 1.55.0000
version baseband: 4A.21.3263.03
version cpld: none
version microp: none
version-main: 3.24.531.3
Click to expand...
Click to collapse
and the rest please , eg:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also what ROM are you on?
nkk71 said:
and the rest please , eg:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also what ROM are you on?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm on just on stock rooted. Is that why? Do I just need to flash a ROM?
Bradlees said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm on just on stock rooted. Is that why? Do I just need to flash a ROM?
Click to expand...
Click to collapse
from rumrunner: "as long as you have root) and also custom roms. We DO prefer users have an unsecure kernel", so try ARHD 31.6 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (it's already rooted & unsecured kernel)
though I have to mention that other T-Mobile users are having issues, but usually on firmware 3.63.111.x
Good luck
nkk71 said:
from rumrunner: "as long as you have root) and also custom roms. We DO prefer users have an unsecure kernel", so try ARHD 31.6 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (it's already rooted & unsecured kernel)
though I have to mention that other T-Mobile users are having issues, but usually on firmware 3.63.111.x
Good luck
Click to expand...
Click to collapse
So I'm sure I'm reading this right: I don't need a custom ROM, correct? Its not listed as a prerequisite on the rumrunner site, just root. I could perhaps just flash an unsecure kernel over my stock rom?
Thanks, btw
@nkk71 for the win...the kernel was going to be my next suggestion. After doing some googling lol
Hope it works. If anyone can helps its nkk71
Bradlees said:
So I'm sure I'm reading this right: I don't need a custom ROM, correct? Its not listed as a prerequisite on the rumrunner site, just root. I could perhaps just flash an unsecure kernel over my stock rom?
Thanks, btw
Click to expand...
Click to collapse
yes you could try it that way (ie flash custom kernel), but why not go for ARHD 31.6? it's already rooted, unsecured kernel, has USB debugging enabled, has Power->Fast boot disabled (I think), has adb shell su already granted.
if it's just about not wanting to erase apps+data+settings, then just do a nandroid of your current setup, flash ARHD 31.6, get S-Off (hopefully) and restore nandroid afterwards.
I just picked up a new ONE after returning it for the camera colors in dark light (had it for 3-4 months HBOOT 1.44)
this new one is on HBOOT 1.55 to use rumrunner I had to:
1) HTC DEV unlock
2) flash custom recovery
3) install CM 10.2 (the final release works best CM 11 did not work)
4) flash SU zip
5) run rumrunner
With this process it had to pour less than with hboot 1.44 and cm 10.2. went pretty quickly if you have done it before. But the kernel is almost definitely the problem.
have faith it can be done
nkk71 said:
yes you could try it that way (ie flash custom kernel), but why not go for ARHD 31.6? it's already rooted, unsecured kernel, has USB debugging enabled, has Power->Fast boot disabled (I think), has adb shell su already granted.
if it's just about not wanting to erase apps+data+settings, then just do a nandroid of your current setup, flash ARHD 31.6, get S-Off (hopefully) and restore nandroid afterwards.
Click to expand...
Click to collapse
Success! First try it worked after flashing the ARHD ROM on windows xp pc. Thanks.
tobesedated said:
@nkk71 for the win...the kernel was going to be my next suggestion. After doing some googling lol
Hope it works. If anyone can helps its nkk71
Click to expand...
Click to collapse
It worked with a custom ROM. Didn't even need to do it on Ubuntu, it worked on winxp. Thanks
tmckenn2 said:
I just picked up a new ONE after returning it for the camera colors in dark light (had it for 3-4 months HBOOT 1.44)
this new one is on HBOOT 1.55 to use rumrunner I had to:
1) HTC DEV unlock
2) flash custom recovery
3) install CM 10.2 (the final release works best CM 11 did not work)
4) flash SU zip
5) run rumrunner
With this process it had to pour less than with hboot 1.44 and cm 10.2. went pretty quickly if you have done it before. But the kernel is almost definitely the problem.
have faith it can be done
Click to expand...
Click to collapse
That was the solution. I'm now S-Off. Thanks.
Bradlees said:
Success! First try it worked after flashing the ARHD ROM on windows xp pc. Thanks.
Click to expand...
Click to collapse
Congrats, good to hear
can you edit main thread title to include [SOLVED] so others can refer to it too. thanks
Bradlees said:
It worked with a custom ROM. Didn't even need to do it on Ubuntu, it worked on winxp. Thanks
Click to expand...
Click to collapse
That's great... Isn't it awesome how so many people are willing to help someone out?
Sent from my LG-D803 using xda app-developers app
Hi everyone! I have a problem, I tried to make S-off with all available here on the site, and it did not work out (rumrunner hanging on pounding ........ and firewater is also something same on bottle 1). Bootloader is in state tampered.
Here is my data
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.51 (this version was set by misctool, (before there was 4.19.401.8) I thought that perhaps i can flash older firmware tht can make rumrunner to work)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AGW901978
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not know what else can help make S-off, probably tried all possible methods. Maybe, someone also went through this agony with S-off
I would also add that I tried to restore the firmware using Guru_Reset_M7_2.24.401.8 and then OTA update but it only caused permanent bootloot
pankozin said:
Hi everyone! I have a problem, I tried to make S-off with all available here on the site, and it did not work out (rumrunner hanging on pounding ........ and firewater is also something same on bottle 1). Bootloader is in state tampered.
Here is my data
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.51 (this version was set by misctool, (before there was 4.19.401.8) I thought that perhaps i can flash older firmware tht can make rumrunner to work)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AGW901978
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not know what else can help make S-off, probably tried all possible methods. Maybe, someone also went through this agony with S-off
I would also add that I tried to restore the firmware using Guru_Reset_M7_2.24.401.8 and then OTA update but it only caused permanent bootloot
Click to expand...
Click to collapse
There is already a thread discussing about s-off on hboot 1.56 here
you'll probably find an answer there.
Afaik you'll need a rooted rom + an unsecured kernel to achieve s-off.
alray said:
There is already a thread discussing about s-off on hboot 1.56 here
you'll probably find an answer there.
Afaik you'll need a rooted rom + an unsecured kernel to achieve s-off.
Click to expand...
Click to collapse
I tried 5 different roms. dont know about kernels, i think this roms have unsecured kernels. but mb i need to install it separately??? I read this thred u suggested, but it didnt help. Now im on ARHD 62.0. what kernel should i try?
I really literally read all posts over internet but nothing helped. Or i dont understand something about this process. so i created a thread for it
pankozin said:
I tried 5 different roms. dont know about kernels, i think this roms have unsecured kernels. but mb i need to install it separately??? I read this thred u suggested, but it didnt help. Now im on ARHD 62.0. what kernel should i try?
I really literally read all posts over internet but nothing helped. Or i dont understand something about this process. so i created a thread for it
Click to expand...
Click to collapse
arhd already comes with the required kernel. have tried arhd 53?
alray said:
arhd already comes with the required kernel. have tried arhd 53?
Click to expand...
Click to collapse
I tried 53 and 31.6. just dont know what can i do more. I feel like i changed something crucial in firmware or something so now nothing works (
pankozin said:
I tried 53 and 31.6. just dont know what can i do more. I feel like i changed something crucial in firmware or something so now nothing works (
Click to expand...
Click to collapse
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
alray said:
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
Click to expand...
Click to collapse
Where can i find firmware to flash in S-ON state? i heard tht signed one may suite.
alray said:
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
Click to expand...
Click to collapse
Hey i got this problem when using rumrunner "adbd can not run as root in production builds"
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
adkz25 said:
So, here's the thing, I already posted on a thread but it seems it's actually full of people asking and the guys answering there are stumped with our problems so I came here.
Click to expand...
Click to collapse
Actually they guy there, me, was really busy in the past days and wasn't able to answer everyone. You can't imagine how much PM and Quote I had in the last week And yes I agree with you, its really hard to troubleshoot in that thread since there's so many discussions going on at the same time.
My bootloader is locked because I (stupidly ) relocked it while trying to install a newer firmware via RUU so then it just locked me out and couldn't do anything until I installed the RUU update of the same version I was running.
It's working but not as intended.
I tried unlocking the bootloader again after installing the RUU but no luck, the token works but it just won't detect my power button when I try to accept but the button works perfectly while running the system.
Here's my getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: X
(bootloader) imei: X
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
Click to expand...
Click to collapse
Its a pretty uncommon problem. When flashing a RUU, all partitions (except some partitions that are unique to each devices) are flashed back to stock, even the bootloader which make me believe its not a corrupt bootloader problem. So if after flashing a RUU, your phone still have some problems, its most likely an hardware problem... If the RUU flashed fine there is nothing more you can do on the software side.... THe only thing I can think is to use Sunshine S-OFF to unlock your bootloader but unfortunately it cost 25$ to use Sunshine but at least it will bypass that "power button not working only in bootloader" problem
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
adkz25 said:
Yeah, I figured you were real busy. )^:
I really don't mind paying for Sunshine to get S-Off but when I tried running it to get temp root it just says it failed and closes. Is there any way for me to get it working?
Click to expand...
Click to collapse
I would try the same method they are using in the Verizon HTC One forum, get temp root using kingRoot then launch sunshine
http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-OFF
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
adkz25 said:
Yay! It worked. I'm S-Off and unlocked right now so I might try to install TWRP and stuff.
KingRoot worked like a charm, I didn't even need to re-run it and try to get some prompt, it just... worked and gave me temp root.
.
Anyway, I still have a little doubt (unrelated to this issue but you seem to know your way around). Everything I posted in this and that thread went down because I tried to install this ROM and it said I needed some firmware flashed.
What I'm trying to get to is:
Do I really need to flash that firmware?
Is it flashed via TWRP?
Are those GPE roms worth it?
Anyways, thank you for helping me out.
Click to expand...
Click to collapse
Glad it worked!
Firmware files are flashed with fastboot in ruu mode:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip "file name".zip
fastboot flash zip "file name".zip
fastboot reboot-bootloader
Then go in recovery and flash the rom
Better to flash the latest firmware without stock recovery so you don't overwrite twrp recovery with the stock recovery.
Note that this firmware is the latest GPE firmware and that if you want to go back to stock rom using a ruu you'll have to reflash a hboot 1.57 or 1.61 firmware before running a 7.xx.xxx.xx Sense ruu.
GPE roms is perfect if you want something closer to a nexus experience, otherwise stay with a Sense rom.
Sent from my HTC One using XDA Labs