I have tried to use both rumrunner and firewater to s-off my htc one m7. At first, rumrunner complained of my kernel, so I installed carbon (based off of android 4.3) and elementalX. This combination causes rumrunner to tell me to wait and pray, and firewater exits in the middle.
I think that the firewater problem is due to the adb shell exiting when the phone reboots: it's unable to maintain the connection, and continue to run firewater when my phone is rebooting.
I have no idea why rumrunner isn't working.
Any help would be appreciated.
science_man said:
I have tried to use both rumrunner and firewater to s-off my htc one m7. At first, rumrunner complained of my kernel, so I installed carbon (based off of android 4.3) and elementalX. This combination causes rumrunner to tell me to wait and pray, and firewater exits in the middle.
I think that the firewater problem is due to the adb shell exiting when the phone reboots: it's unable to maintain the connection, and continue to run firewater when my phone is rebooting.
I have no idea why rumrunner isn't working.
Any help would be appreciated.
Click to expand...
Click to collapse
With firewater are you using a USB 2.0 connection?
Do you have a good internet connection with the phone & PC?
Have you tried a different port? Cable? PC?
majmoz said:
With firewater are you using a USB 2.0 connection?
Do you have a good internet connection with the phone & PC?
Have you tried a different port? Cable? PC?
Click to expand...
Click to collapse
I am using a USB 2.0 connection
I have a good internet connection with the PC, and I assume my phone can access my wifi.
I have tried different cables and ports, but not computers. It seems like this isn't my problem, but I'll give it a try just to be safe.
science_man said:
I am using a USB 2.0 connection
I have a good internet connection with the PC, and I assume my phone can access my wifi.
I have tried different cables and ports, but not computers. It seems like this isn't my problem, but I'll give it a try just to be safe.
Click to expand...
Click to collapse
I'm going to assume that ADB is up to date. Some have reported that ARHD 81.0 is a good candidate because it is close to stock. So, you might give it a try. If you read thru the firewater thread you may get some ideas on what combinations to try. If you get the "Whelp this sucks..." message then firewater will not work and you next option is sunshine with it's $25 fee.
majmoz said:
I'm going to assume that ADB is up to date. Some have reported that ARHD 81.0 is a good candidate because it is close to stock. So, you might give it a try. If you read thru the firewater thread you may get some ideas on what combinations to try. If you get the "Whelp this sucks..." message then firewater will not work and you next option is sunshine with it's $25 fee.
Click to expand...
Click to collapse
Before I try ARHD (my internet is slow and I'm not looking forward to the download), what do you mean by the "Whelp this sucks..." message? I have never gotten an explicit error message from firewater; rather it just exits when the phone first reboots without any effect.
science_man said:
Before I try ARHD (my internet is slow and I'm not looking forward to the download), what do you mean by the "Whelp this sucks..." message? I have never gotten an explicit error message from firewater; rather it just exits when the phone first reboots without any effect.
Click to expand...
Click to collapse
You should keep trying until you get that message. You say your internet is slow, could it be the cause of the communication error in that firewater is not waiting long enough to get a reply via the internet?
majmoz said:
You should keep trying until you get that message. You say your internet is slow, could it be the cause of the communication error in that firewater is not waiting long enough to get a reply via the internet?
Click to expand...
Click to collapse
I have tried several times to run firewater, and when it does fail, it doesn't give the impression that it almost succeeded; adb shell exits when the phone reboots. That doesn't seem like it would change randomly, unlike an actual error. Also, my internet isn't so slow that I have connectivity issues, usually. I will try again, but mostly right now I'm just waiting for this ROM to download.
Thanks for trying to help, by the way!
While trying to install Android Revolution, the installer tells me "set_metadata_recursive: some changes failed" just after it tries to set permissions. Then, when I try to boot, I get stuck in a boot loop, where my phone enters recovery instead of booting the system. I am using twrp recovery, by the way. On the ARHD page, there is something mentioned about a custom firmware, but I don't know how to find out which firmware would be the correct one.
I'm assuming the reason I can't install ARHD is because I don't have s-off. But that is what I am trying to get by installing it, so there is no point. Can I install ARHD without s-off? If so, what do I need to do differently?
science_man said:
While trying to install Android Revolution, the installer tells me "set_metadata_recursive: some changes failed" just after it tries to set permissions. Then, when I try to boot, I get stuck in a boot loop, where my phone enters recovery instead of booting the system. I am using twrp recovery, by the way. On the ARHD page, there is something mentioned about a custom firmware, but I don't know how to find out which firmware would be the correct one.
I'm assuming the reason I can't install ARHD is because I don't have s-off. But that is what I am trying to get by installing it, so there is no point. Can I install ARHD without s-off? If so, what do I need to do differently?
Click to expand...
Click to collapse
Use TWRP 2.6.3.3 recovery.
cyrusct82 said:
Use TWRP 2.6.3.3 recovery.
Click to expand...
Click to collapse
Although 2.6.3.3 does get rid of the error message, my phone still gets stuck in a boot loop when trying to boot ARHD.
Do you think my problems installing ARHD stem from not having s-off? It is stated somewhere that it is possible to install it with s-on, but I don't know what else I would have to do to get that to work.
science_man said:
Do you think my problems installing ARHD stem from not having s-off? It is stated somewhere that it is possible to install it with s-on, but I don't know what else I would have to do to get that to work.
Click to expand...
Click to collapse
You don't need s-off to flash AHRD ..only the google play edition requires s-off
post your fastboot getvar all (minus your serial no and IMEI)
clsA said:
You don't need s-off to flash AHRD ..only the google play edition requires s-off
post your fastboot getvar all (minus your serial no and IMEI)
Click to expand...
Click to collapse
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
science_man said:
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
Click to expand...
Click to collapse
You have the developers edition CID
theirs no reason why ARHD shouldn't work
try an older version like arhd 53 or 62
https://www.androidfilehost.com/?w=files&flid=9984
I managed to install Android Revolution 53 after installing twrp 2.6.33 (2.8.0.2 gave me that error about permissions I had earlier). However, this didn't appear to get me any closer to getting s-off. The exact same error happens with rumrunner as happened when I had carbon installed.
science_man said:
I managed to install Android Revolution 53 after installing twrp 2.6.33 (2.8.0.2 gave me that error about permissions I had earlier). However, this didn't appear to get me any closer to getting s-off. The exact same error happens with rumrunner as happened when I had carbon installed.
Click to expand...
Click to collapse
Try ARHD 53 with compatible Bulletproof Kernel
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Try ARHD 53 with compatible Bulletproof Kernel
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I am already using ElementalX kernel, and "For Sense 5 Android 4.2.2:
Install ElementalX with vanilla settings and you will have Bulletproof Kernel". So I think I already am.
science_man said:
I am already using ElementalX kernel, and "For Sense 5 Android 4.2.2:
Install ElementalX with vanilla settings and you will have Bulletproof Kernel". So I think I already am.
Click to expand...
Click to collapse
No Elemental x is not bulletproof kernel no matter how you install it. Both kernels come from the same Dev, why would he make 2 kernels if you could get the same thing from just one.
Bulletproof kernel has proven to be far more successful with firewater than Elemental x. It's worth a try :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
No Elemental x is not bulletproof kernel no matter how you install it. Both kernels come from the same Dev, why would he make 2 kernels if you could get the same thing from just one.
Bulletproof kernel has proven to be far more successful with firewater than Elemental x. It's worth a try :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
You have fixed every single one of my problems. My phone is now s-off. Thank you so much.
science_man said:
You have fixed every single one of my problems. My phone is now s-off. Thank you so much.
Click to expand...
Click to collapse
Your Welcome and Congrats on the s-off it's kind of a great feeling huh! :highfive: enjoy the s-off goodness
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Related
I'm trying to get S-Off on my One with rumrunner, but nothing seems to be working, i've tried several stock rom's , also Custom roms , several insecure kernels. But none seem to be working. I'm currently on:
HBOOT: 1.55
CID: T-MOB101
ROM: 2.24.111.3
This Stock ROM at least gives shell requests, and keeps pouring till >8 and repeats if i restart.
Support would be greatly appriciated, have already spent 15 hours for S-Off with no succes.
Thanks
Gixy said:
I'm trying to get S-Off on my One with rumrunner, but nothing seems to be working, i've tried several stock rom's , also Custom roms , several insecure kernels. But none seem to be working. I'm currently on:
HBOOT: 1.55
CID: T-MOB101
ROM: 2.24.111.3
This Stock ROM at least gives shell requests, and keeps pouring till >8 and repeats if i restart.
Support would be greatly appriciated, have already spent 15 hours for S-Off with no succes.
Thanks
Click to expand...
Click to collapse
hboot is 1.55, but ROM is 2.24??
please post a "fastboot getvar all" (remove IMEI and s/n)
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ############
(bootloader) imei: ################
(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: 4297mV
(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
Gixy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) cidnum: T-MOB101
Click to expand...
Click to collapse
this seems to be the bad combination for alot of folks in the Rumrunner thread - http://forum.xda-developers.com/showthread.php?t=2487888&page=55
Gixy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
oh, very uncool, no firmware version.
hboot 1.55 would lead me to assume a 3.xx firmware, so try using ARHD 31.6: http://forum.xda-developers.com/showthread.php?t=2183023
(it's rooted, and unsecured kernel)
if you're still having trouble with rumrunner, maybe give Ubuntu a shot, seems to be working, eg: http://forum.xda-developers.com/showthread.php?t=2567727
nkk71 said:
oh, very uncool, no firmware version.
hboot 1.55 would lead me to assume a 3.xx firmware, so try using ARHD 31.6: http://forum.xda-developers.com/showthread.php?t=2183023
(it's rooted, and unsecured kernel)
if you're still having trouble with rumrunner, maybe give Ubuntu a shot, seems to be working, eg: http://forum.xda-developers.com/showthread.php?t=2567727
Click to expand...
Click to collapse
I have tried ARHD 31.6 also, no succes ;(
Got ABD , fastboot & HTC drivers installed correctly.
clsA said:
this seems to be the bad combination for alot of folks in the Rumrunner thread - http://forum.xda-developers.com/showthread.php?t=2487888&page=55
Click to expand...
Click to collapse
Gixy said:
I have tried ARHD 31.6 also, no succes ;(
Got ABD , fastboot & HTC drivers installed correctly.
Click to expand...
Click to collapse
maybe @clsA is right.
if it was me, and i (really) wanted to do it, i would go for an Ubuntu Live USB, and give it a shot. (if at first you dont succeed try, try again)
nkk71 said:
maybe @clsA is right.
if it was me, and i (really) wanted to do it, i would go for an Ubuntu Live USB, and give it a shot. (if at first you dont succeed try, try again)
Click to expand...
Click to collapse
Are there any threads about running Rumrunner on Ubentu?
I've already got Ubuntu installed on other hard drive, and can boot it up right now.
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
But managed to startup soju xD. Am not getting ADB connection
Is there some thread about Rumrunner ubuntu ?
Thanks for all your support though !
Gixy said:
Are there any threads about running Rumrunner on Ubentu?
I've already got Ubuntu installed on other hard drive, and can boot it up right now.
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
But managed to startup soju xD. Am not getting ADB connection
Is there some thread about Rumrunner ubuntu ?
Thanks for all your support though !
Click to expand...
Click to collapse
have you checked the instructions for the rumrunner Linux package: http://rumrunner.us/instructions/
and best to use 32bit Ubuntu (from what I recall) not 64.
let us know how it goes.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
Gixy said:
But i'm quite new to ubuntu, couldn't get ADB drivers working for my One.
Click to expand...
Click to collapse
Sorry, my bad thought you said "could get adb working", look here: http://forum.xda-developers.com/showthread.php?t=2560130
nkk71 said:
have you checked the instructions for the rumrunner Linux package: http://rumrunner.us/instructions/
and best to use 32bit Ubuntu (from what I recall) not 64.
let us know how it goes.
---------- Post added at 07:02 PM ---------- Previous post was at 06:59 PM ----------
Sorry, my bad thought you said "could get adb working", look here: http://forum.xda-developers.com/showthread.php?t=2560130
Click to expand...
Click to collapse
Iḿ saying ADB drivers on windows are fine, I´ve just tried linux, and end up in Pouring... 8
Gonna give Rumrunner another try.
Gixy said:
Iḿ saying ADB drivers on windows are fine, I´ve just tried linux, and end up in Pouring... 8
Gonna give Rumrunner another try.
Click to expand...
Click to collapse
32bit ubuntu seems to work better that 64, just in case, good luck
nkk71 said:
32bit ubuntu seems to work better that 64, just in case, good luck
Click to expand...
Click to collapse
I just created one for myself here on a 4GB Kingston Flashdrive
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
http://www.ubuntu.com/download/desktop/thank-you?distro=desktop&bits=32&release=latest
Using linux, running ARHD 31.1 iḿ not getting Shell-requests at all :s
clsA said:
I just created one for myself here on a 4GB Kingston Flashdrive
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
http://www.ubuntu.com/download/desktop/thank-you?distro=desktop&bits=32&release=latest
Click to expand...
Click to collapse
still downloading (for 40 minutes) another 10 minutes...
nkk71 said:
still downloading (for 40 minutes) another 10 minutes...
Click to expand...
Click to collapse
Linux doesn't work for me as well, another 2x pouring... 8
Using ARHD 31.6 and tried stock as well
nkk71 said:
still downloading (for 40 minutes) another 10 minutes...
Click to expand...
Click to collapse
lol i booted it and installed rumrunner 10 min ago
Gixy said:
Linux doesn't work for me as well, another 2x pouring... 8
Using ARHD 31.6 and tried stock as well
Click to expand...
Click to collapse
well, crap!!
have you tried 41.0? ... I know this is getting sh*tty, but some combination should work... have you checked in rumrunner thread, and see if someone had the same issue with solution.
clsA said:
lol i booted it and installed rumrunner 10 min ago
Click to expand...
Click to collapse
Why install Ubuntu and Rumrunner, you're already S-Off or am i wrong xD
nkk71 said:
well, crap!!
have you tried 41.0? ... I know this is getting sh*tty, but some combination should work... have you checked in rumrunner thread, and see if someone had the same issue with solution.
Click to expand...
Click to collapse
I've checked the thread, Tried some solutions : Several stock roms , some of them SHOWED Shell requests, other just rebooted a few times . 31.6 Doesn't show shell requests, lookedup SuperSU settings, tried requesting root acces, and simply granting all acces. Also checked with RootChecker, root seems to be fine.
41.0 Was my daily driver for a month, this was my first try with Rumrunner, which failed, no shell requests.
EDIT: I'm gonna give 41.0 another try, didn't tried linux with that one. But i don't expect much difference honestly xD
Gixy said:
Why install Ubuntu and Rumrunner, you're already S-Off or am i wrong xD
Click to expand...
Click to collapse
practice ...i work on others phone's
this is from the link I posted
Quote:
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/show....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
Hey Guys,
I want to make my HTC ONE a Google Play Edtioin, so.I am currently trying to make my HTC ONE (international) S-Off with Soju. i hae USB- Debugging turned on, my Bottloader is unlocked and my phone is rooted.
Everytime i try to run soju i get this Erreor:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (16/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
Does anyone know how to fix this?
Fabivons said:
Hey Guys,
I want to make my HTC ONE a Google Play Edtioin, so.I am currently trying to make my HTC ONE (international) S-Off with Soju. i hae USB- Debugging turned on, my Bottloader is unlocked and my phone is rooted.
Everytime i try to run soju i get this Erreor:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (16/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
Does anyone know how to fix this?
Click to expand...
Click to collapse
just do what the output tells you to do!
Go to www.rumrunner.us and use the updated version.
LibertyMarine said:
just do what the output tells you to do!
Go to www.rumrunner.us and use the updated version.
Click to expand...
Click to collapse
Thanks for your reply!
I already have the newest version so that doesn't seem to be the problem :/
Fabivons said:
Thanks for your reply!
I already have the newest version so that doesn't seem to be the problem :/
Click to expand...
Click to collapse
hmm, what OS did you install? Try to install a 4.3 zip from here: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
And could you please provide a "fastboot getvar all"?
thanks
P.S.
Just in case you don't know... censor the IMEI and the build number... just everything that is unique on your phone!
LibertyMarine said:
hmm, what OS did you install? Try to install a 4.3 zip from here: http://android-revolution-hd.blogspot.ch/p/android-revolution-hd-mirror-site-var.html
And could you please provide a "fastboot getvar all"?
thanks
P.S.
Just in case you don't know... censor the IMEI and the build number... just everything that is unique on your phone!
Click to expand...
Click to collapse
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(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.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: /
(bootloader) imei: /
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3941mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Fabivons said:
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(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.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: /
(bootloader) imei: /
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3941mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
then I think you should try the STOCK 4.3 ROM... this should definitely work. I tested it twice.
http://www.androidrevolution.nl/downloader/download.php?file=One_3.62.401.1_odexed.zip
(Thanks @mike1986.)
Then download the newest version of rumrunner s off:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
BUT carefully listen to the instructions on the site!
http://rumrunner.us/instructions/
Fabivons said:
I recently installed Android Revolution HD 41 and the ElementalX-m7-10.10.1 Kernel.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
LibertyMarine said:
then I think you should try the STOCK 4.3 ROM... this should definitely work. I tested it twice.
http://www.androidrevolution.nl/downloader/download.php?file=One_3.62.401.1_odexed.zip
(Thanks @mike1986.)
Then download the newest version of rumrunner s off:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
BUT carefully listen to the instructions on the site!
http://rumrunner.us/instructions/
Click to expand...
Click to collapse
Sorry to bug in, but may I recommend ARHD 31.6 (already rooted and unsecured kernel): http://forum.xda-developers.com/showthread.php?t=2183023
nkk71 said:
Sorry to bug in, but may I recommend ARHD 31.6 (already rooted and unsecured kernel): http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
No problem... I tried this one too but none of the ARHD worked for me.. anyways... rumrunner roots and flashed a unsecured kernel..
LibertyMarine said:
No problem... I tried this one too but none of the ARHD worked for me.. anyways... rumrunner roots and flashed a unsecured kernel..
Click to expand...
Click to collapse
When you got s-off, were you using the universal tool, or the firmware specific tools? as far as i can see, the universal tool (unlike the specific versions), need root and unsecured kernel (which the previous fw specific packages did by themselves).
nkk71 said:
When you got s-off, were you using the universal tool, or the firmware specific tools? as far as i can see, the universal tool (unlike the specific versions), need root and unsecured kernel (which the previous fw specific packages did by themselves).
Click to expand...
Click to collapse
I used both... for the new phone I used a universal tool... but I didn't root the phone previously...
Where did you see that? I read again through the whole page and couldn't find a order to install supersu or/and a unsecured kernel...
Maybe we shouldn't discuss this in the thread... we're highjacking this thread^^ Anyways, would be interesting where you got this information form
LibertyMarine said:
I used both... for the new phone I used a universal tool... but I didn't root the phone previously...
Where did you see that? I read again through the whole page and couldn't find a order to install supersu or/and a unsecured kernel...
Maybe we shouldn't discuss this in the thread... we're highjacking this thread^^ Anyways, would be interesting where you got this information form
Click to expand...
Click to collapse
I think it's okay, as long as we don't go forty posts on it; i saw it on while using rumrunner 0.5.0, ........ "ERROR: looks device is not rooted AND lacks an unsecure kernel. su or Fu!!!"
in fact ROM was rooted (odexed), but stock kernel, after installing custom kernel it was ok.
nkk71 said:
I think it's okay, as long as we don't go forty posts on it; i saw it on while using rumrunner 0.5.0, ........ "ERROR: looks device is not rooted AND lacks an unsecure kernel. su or Fu!!!"
in fact ROM was rooted (odexed), but stock kernel, after installing custom kernel it was ok.
Click to expand...
Click to collapse
Hmm... that's weird^^ but to be sure, I'd also do what you recommend... I just didn't have this problem.. don't know why.. the One was just out of the box, unlocked.. not even rooted^^ don't know how this exactly happend. Maybe I was on a previous verison of rumrunner s off... but I am pretty sure it was one of the universal.. I'm gonna dig around in my logfiles.. I stored everything somewhere on my HD...
LibertyMarine said:
Hmm... that's weird^^ but to be sure, I'd also do what you recommend... I just didn't have this problem.. don't know why.. the One was just out of the box, unlocked.. not even rooted^^ don't know how this exactly happend. Maybe I was on a previous verison of rumrunner s off... but I am pretty sure it was one of the universal.. I'm gonna dig around in my logfiles.. I stored everything somewhere on my HD...
Click to expand...
Click to collapse
AFAIK, rooted rom should work, and unsecured kernel is only "preferred".
nkk71 said:
AFAIK, rooted rom should work, and unsecured kernel is only "preferred".
Click to expand...
Click to collapse
sorry, because of a lack of English knowledge, I didn't understand what you meant with this message. Sorry, could you please try to say it with different words ?
LibertyMarine said:
sorry, because of a lack of English knowledge, I didn't understand what you meant with this message. Sorry, could you please try to say it with different words ?
Click to expand...
Click to collapse
yes, sorry: as far as i know (AFAIK), when rumrunner switched from specific to universal, the first thing that was needed was a rooted rom, with an unsecured kernel "preferred, but not necessary",
now (as the number of devices, etc. have been added), rumrunner works best with a ROM compatible with firmware, also rooted and unsecured kernel (ie kernel with write-protection disabled)
nkk71 said:
yes, sorry: as far as i know (AFAIK), when rumrunner switched from specific to universal, the first thing that was needed was a rooted rom, with an unsecured kernel "preferred, but not necessary",
now (as the number of devices, etc. have been added), rumrunner works best with a ROM compatible with firmware, also rooted and unsecured kernel (ie kernel with write-protection disabled)
Click to expand...
Click to collapse
Aha, ok.. thanks! Thank you very much for updating my knowledge!
I'm on stock, rooted, custom recovery and HBoot 1.55... This is what I did....
http://forum.xda-developers.com/showthread.php?t=2606577
Sent from my LG-D803 using xda app-developers app
Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?
Fabivons said:
Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?
Click to expand...
Click to collapse
oh mate.. what luck that I randomly saw your post... otherwise noone would have seen it.. remember: If you want to have an answer, quote or the other person won't be notified! This is just the way this forum works.. I am sorry.
Yes there is a fix:
Download Xposed Installer and install it on your device. Then install the framework... and search in the store(the one in xposed) for 3dot menu Mod... install it and the 3dot menu is away! To get the 3dot menu working, i can recommand Gravity box which you can use to remap the softkeys(longpress, doublepress)...
Edit:
Xposed doesn't work on ART Engine at the moment! Only dalvik works. Running it on ART will lead into a bootloop... but Xposed know this and disables ART before you run into further errors
Fabivons said:
Thank you so far!
I am going to try it out!
But I have one more question.. is there a fix for the big black menue button which appears in the Google Play Edition?
Click to expand...
Click to collapse
is everything fine?
Hey all,
A while back I made the jump to CM using the CM installer. Everything is working fine but I want to give the Google Edition a shot.
I'm having problems getting S-off done. Tried a couple different methods. Anyone else made the jump?
Thanks
Sent from my One using XDA Premium 4 mobile app
Basttrax said:
Hey all,
A while back I made the jump to CM using the CM installer. Everything is working fine but I want to give the Google Edition a shot.
I'm having problems getting S-off done. Tried a couple different methods. Anyone else made the jump?
Thanks
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
gonna need more info like what bootloader your on and some other things. also maybe the error your running into when you try to S-off. what s-off method are you using?
Sorry about then lack of info.
Tampered
Unlocked
S-On
CWM v6.0.4.6
CM installer version.
Sent from my One using XDA Premium 4 mobile app
Install a sense based rom, ARHD is a good choice, try the 41 series, and not the 51 series.
Then S-OFF. Once you are on google edition, do NOT S-ON or lock your bootloader
SaHiLzZ said:
Install a sense based rom, ARHD is a good choice, try the 41 series, and not the 51 series.
Then S-OFF. Once you are on google edition, do NOT S-ON or lock your bootloader
Click to expand...
Click to collapse
It seems that the ARHD links are dead at the moment. Any other suggestions?
Does anyone else know any other ROMs other than ARHD (Links dead). That they know can have soff done to them?
Thanks
Sent from my One using XDA Premium 4 mobile app
the roms themselves dont contain S-OFF or on. its just that if you want to a complete update you'll have to have S-OFF to do it. you can flash ARHD with or without S-OFF but since ARHD and all the other latest roms mostly likely have 4.4.2 you'll want the latest firmware to go along with it since it tends to play better with each other. to update your firmware your going to have to be S-OFF this is the reason why most roms like ARHD and viper say its a good idea to be S-OFF
what is the output of fastboot getvar all ? (remove imei)
SaHiLzZ said:
what is the output of fastboot getvar all ? (remove imei)
Click to expand...
Click to collapse
So I tried using both Firewater and Rumrunner with no luck. Both just time out during the pouring process or chugging.
Installed both ARHD Sense version and JB version.
C:\sdk-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3BVW901799
(bootloader) imei: (Removed)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4300mV
(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
all: Done!
finished. total time: 0.043s
Basttrax said:
So I tried using both Firewater and Rumrunner with no luck. Both just time out during the pouring process or chugging.
Installed both ARHD Sense version and JB version.
Click to expand...
Click to collapse
I just did a firewater S-OFF on Telus 4.4 Kitkat. Worked straight forward. No issues.
Maybe try to go back to stock rom and try again. Rumrunner did not work on 4.4/1.56 hboot for me.
Just doing the Nandroid backup now. I'll get back to you.
So the Nandroid worked well. Now I'm trying to get the OTA update to 4.4. Unfortunately it just brings me to TWRP when I try. Any ideas?
Tried using firewater however and got stuck with this;
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..........
C:\sdk-tools>
as always
You need stock recovery to install an OTA. Once you have updated hboot without S-Off, you can't downgrade it, which will reduce the S-Off options you have. It's worth exhausting the options on the lower hboot before upgrading it.
You will need a ROM that is close to stock, ARHD 31 has been known to work. Also, before running the commands that run on the phone (usually after adb shell) to S-Off, type
su
On a rooted ROM, like ARHD, it will give you superuser permissions. The S-Off programs have a temproot, but the exploit has been closed, so elevating first will help it along.
You can't be alone in this and the S-Off threads have a lot of info in them.
So just in case anyone was following this, turns out I have one of those rare Htc Ones that cannot soff. Spoke to a couple of those guys over on the Rumrunner irc chat.
Sent from my HTC One using XDA Premium 4 mobile app
First of all, my predicament continues from this thread
http://forum.xda-developers.com/showthread.php?t=2725647
Previous situation: (Skip if you're not interested in what got me into this)
I originally intended to return to 100% stock and send it back to HTC to get my purple camera fixed, but after 3 days of trying, I messed up.
Since it took up so much of my time and I was frustrated, I decided to send it back regardless of warranty. I send it to my carrier after wiping everything. HTC demanded about 450USD for a 730USD phone, my carrier suggested sending it to a workshop since they'd have a much more reasonable price. The workshop demanded 150USD(about half for the software and half for the camera replacement). I didn't care whether my phone came back in stock or not, so I told them to go ahead and fix the camera ONLY. But they strongly suggested that I fix my software first, so I took it back. Now I'm stuck exactly where I left it.
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.709.14
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Current situation:
S-ON with hboot 1.44. I can't S-OFF with revone since it only works with 4.2.2 ROMs.
I tried using revone to s-off again by installing a Guru_Reset_M7_2.24.709.1 ROM, but then I got a "revone failed (error code = -6)" during the process. Also couldn't install an RUU, always got a "ERROR[140]: BOOTLOADER VERSION ERROR".
What I need:
S-OFF and upgrade to latest hboot.
All I can do now is restore my nandroid backup(ARHD 63.0) during the day when I need my phone, and try fixing it whenever I have time.
I have tried everything I can think of, and I'm completely stuck right now. PLEASE HELP.
Please help
BUMP
theplaypig said:
What I need:
S-OFF and upgrade to latest hboot.
Click to expand...
Click to collapse
Install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
then use revone to S-Off
PS: and edit your first post and remove IMEI, not to be shared publicly
EDIT: Why is (bootloader) version-main: 4.20.709.14 ??
nkk71 said:
Install the ROM mentioned here: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
then use revone to S-Off
PS: and edit your first post and remove IMEI, not to be shared publicly
EDIT: Why is (bootloader) version-main: 4.20.709.14 ??
Click to expand...
Click to collapse
I think it's because I downgraded my hboot from 1.56 to 1.44 while running a ARHD 62.0 ROM?
Will this method still work? Waiting for download to finish...
theplaypig said:
I think it's because I downgraded my hboot from 1.56 to 1.44 while running a ARHD 62.0 ROM?
Will this method still work? Waiting for download to finish...
Click to expand...
Click to collapse
okay, just read the other thread, and now i see the problem.... but i don't know if revone will work or not with this combination of hboot + firmware + ROM.
give it a try, otherwise also try both rumrunner and firewater.
nkk71 said:
okay, just read the other thread, and now i see the problem.... but i don't know if revone will work or not with this combination of hboot + firmware + ROM.
give it a try, otherwise also try both rumrunner and firewater.
Click to expand...
Click to collapse
Just tried using revone with the rom you mentioned, I get the same "revone failed (error code = -6)" during the process.
Firewater doesn't work too(via HTC One Toolkit). When I click "Start Firewater", the pop out cmd window(which informs you the of the risks)
won't let me insert "Yes", it doesn't respond to any input.
Trying rumrunner...
What's my next step if it doesn't work?
theplaypig said:
Firewater doesn't work too(via HTC One Toolkit). When I click "Start Firewater", the pop out cmd window(which informs you the of the risks)
Click to expand...
Click to collapse
don't use toolkits, use it via command prompt, download latest version, and follow the adb instructions: http://firewater-soff.com/
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things )
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
uuzi said:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly my phone (before brick, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone was in a bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 354436054678733
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
Click to expand...
Click to collapse
First of all and as I'm sure you've discovered going back to S-on is never a good fix for anything except warranty
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before. Don't know if this is a hardware issue. Flashing firmware may solve it but with s-on and super cid I'm not even sure thats possible or which firmware you can use with your version main that way. Going back to s-on may well have been the nail in the coffin here I'm afraid.
If your able to boot recovery you can push a rom to flash but you need to fix the firmware first as I fear that's the cause of your bootloop. Hopefully @nkk71 @clsA or @majmoz have somthing to add here :good:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
uuzi said:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
Click to expand...
Click to collapse
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
uuzi said:
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
Click to expand...
Click to collapse
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
i'm not really sure right now, i'm trying again now
Danny201281 said:
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before.
Click to expand...
Click to collapse
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
uuzi said:
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
Click to expand...
Click to collapse
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Result:
Code:
C:\unbrick>fastboot oem rebootRUU
(bootloader) Start Verify: 3
OKAY [ 0.030s]
finished. total time: 0.031s
C:\unbrick>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 32.802s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Unknown error))
finished. total time: 801.973s
nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Click to expand...
Click to collapse
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
Click to expand...
Click to collapse
Yeah I got that after he had said he'd changed it manually. Just caught me off guard thought it was something bigger. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------
uuzi said:
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
Click to expand...
Click to collapse
What about TWRP 2.6.3.3 If it's still working maybe you can flash ARHD to get it booting maybe.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
uuzi said:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
Click to expand...
Click to collapse
Glad to here your back up good job :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good: