[Solved] Soft Brick HTC One (M7ul) Recovery won't boot

Search This thread

Davidpearl

Member
Jan 28, 2014
20
0
Hi Guys,

I am in a bit of a pickle.

I decided to Install Cyanogenmod today to see what the fuss was all about - I managed to do this successfully but then after using it for a while actually didn't like it and preferred using Sense 5.

I tried to flash stock to my HTC One (UK M7ul) via the RUU method but this failed twice.

The phone is currently will only boot into Bootloader regardless of what I try so will not even boot into Cyanogenmod at all, when ever i click recovery as CWM was installed the phone will flash for a second saying starting recover and then go straight back into bootloader.

I am currently on Bootloader 1.55 with S-On - Phone is locked and will not allow me to unlock it.

I really need some help to get my phone fully functional again on HTC Sense Stock Firemware.

CID: HTC__001
MID: PN0710000

C:\platform-tools>fastboot getvar all
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4304mV
(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
all: Done!
finished. total time: 0.047s
 
Last edited:

alray

Inactive Recognized Contributor
May 22, 2012
8,932
3,593
Hi Guys,

I am in a bit of a pickle.

I decided to Install Cyanogenmod today to see what the fuss was all about - I managed to do this successfully but then after using it for a while actually didn't like it and preferred using Sense 5.

I tried to flash stock to my HTC One (UK M7ul) via the RUU method but this failed twice.

The phone is currently will only boot into Bootloader regardless of what I try so will not even boot into Cyanogenmod at all, when ever i click recovery as CWM was installed the phone will flash for a second saying starting recover and then go straight back into bootloader.

I am currently on Bootloader 1.55 with S-On - Phone is locked and will not allow me to unlock it.

I really need some help to get my phone fully functional again on HTC Sense Stock Firemware.

CID: HTC__001
MID: PN0710000

C:\platform-tools>fastboot getvar all
(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: REMOVE
(bootloader) imei: REMOVE
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4304mV
(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
all: Done!
finished. total time: 0.047s

good thing you posted a ''fastboot getvar all'' but never post IMEI and SN, remove them from your post.

To restore the phone back to stock with a ruu, you need to be s-off to downgrade hboot to 1.44. So you will have to unlock bootloader from htcdev, install twrp custom recovery, flash arhd 31.6, s-off with rumrunner, downgrade hboot and then run the ruu.

all details can be found in this guide.
 
  • Like
Reactions: Davidpearl

Davidpearl

Member
Jan 28, 2014
20
0
Thanks for the help guys - I have issues with my computer not recognising my phone.

I have managed to unlock it again and am trying to get either one of the two methods you guys suggested to work.
 

Davidpearl

Member
Jan 28, 2014
20
0
The adb push command or side load is not working in TWRP.

Dunno how I am going to get this file on there?
 

Davidpearl

Member
Jan 28, 2014
20
0
GOT IT WORKING!!!!! I reinstalled CWM and that worked via side loading the image.

up and running all is right with the world!
 

Davidpearl

Member
Jan 28, 2014
20
0
IS there anything I need to do now as matter of good practie?

The bootloader is currently still inlocked - S-On is still activated and I still have the *tampered* logo.

Do I need to A) Lock the boot loader?
Should i turn S-Off?
How do I get rid of the tampered logo so its fully stock and I can get it repaired from HTC again?
 

alray

Inactive Recognized Contributor
May 22, 2012
8,932
3,593
IS there anything I need to do now as matter of good practie?

The bootloader is currently still inlocked - S-On is still activated and I still have the *tampered* logo.

Do I need to A) Lock the boot loader?
Should i turn S-Off?
How do I get rid of the tampered logo so its fully stock and I can get it repaired from HTC again?

detail on how to go back 100% stock without tempered flag can be found in the guide in linked to you i my previous post
 

Davidpearl

Member
Jan 28, 2014
20
0
detail on how to go back 100% stock without tempered flag can be found in the guide in linked to you i my previous post

I get this error when trying to S-Off my device? what do i need to do?

==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?
(Yes/No)
Yes

Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (36/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (37/120)
must ferment longer...

ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
 

Davidpearl

Member
Jan 28, 2014
20
0
Seems that root is missing. Install SuperSu

I rooted it today and got all the way to the last step and its saying this:



==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?
(Yes/No)
Yes

Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (36/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...........
.........................................
..........
pouring (2)...........
..................................
.
pouring (3)...........
....................................
pouring (4)...........
...................................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit

What do I do?
 

Davidpearl

Member
Jan 28, 2014
20
0
I rooted it today and got all the way to the last step and its saying this:



==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?
(Yes/No)
Yes

Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (36/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)...........
.........................................
..........
pouring (2)...........
..................................
.
pouring (3)...........
....................................
pouring (4)...........
...................................
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit

What do I do?

Tried again and got this:



==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?
(Yes/No)
Yes

Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (34/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (35/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1).........
...............................
pouring (2).........
..................................
pouring (3).........
.................................
pouring (4).........
.....................................
pouring (5).........
...................................
pouring (6).........
...................................
pouring (7).........
....................................
pouring (8).........
.........................................
Wait 30 seconds, power on device, pray, run rumrunner again.
Press ENTER to exit
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut

Davidpearl

Member
Jan 28, 2014
20
0
did you flash an unsecured kernel?

"(bootloader) version-main: 3.62.401.1" or just install ARHD 31.6 http://xdaforums.com/showthread.php?t=2183023 which has all the prerequisites.

if you're having problems with Windows, try Ubuntu Live USB: http://xdaforums.com/showthread.php?t=2606577

I am using the Guru_Reset_3.62.401.1 from the link - I assume that this Stock rom is secured?

I could flash ARHD 51.0 and I may even stay on that if the perform is much superior..... at least If I S-Off on that I can fully stock if there are any issues.

ARHD 51 is basically Kitkat with Sense on it right?

Thanks for all your help it is greatly appreciated.
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
I am using the Guru_Reset_3.62.401.1 from the link - I assume that this Stock rom is secured?

I could flash ARHD 51.0 and I may even stay on that if the perform is much superior..... at least If I S-Off on that I can fully stock if there are any issues.

ARHD 51 is basically Kitkat with Sense on it right?

Thanks for all your help it is greatly appreciated.

Use ARHD 31.6 (because it's inline with your firmware 3.62.401.1), then use rumrunner to get S-Off
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi
    My HTC M7 is stuck in boot mode. I tried to install the Google Play Edition Rom with S-on.
    I had CWM but it seems to have diappeared after i used Guru_Reset_M7_3.62.401.1.zip
    I have tried Squabbi's HTC ONE toolkit but it gives me an error 01 when i try to push revone.

    fastboot getvar all
    (bootloader) version: 0.5
    (bootloader) version-bootloader: 1.44.0000
    (bootloader) version-baseband: 4A.21.3263.04
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main: 1.29.401.16
    (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__016
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 3790mV
    (bootloader) partition-layout: Generic
    (bootloader) security: on
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    getvar:all FAILED (status read failed (Too many links))
    finished. total time: 0.041s
    adb push revone /data/local/tmp/
    error: device not found
    I cannot seem to be able to get a stock South African Vodacom ROM to sideload

    Please help me get S-OFF so that i can load any rom that will make the phone work.

    adb sideload works in custom recovery, not in bootloader mode.
    1
    Hi Guys,

    I am in a bit of a pickle.

    I decided to Install Cyanogenmod today to see what the fuss was all about - I managed to do this successfully but then after using it for a while actually didn't like it and preferred using Sense 5.

    I tried to flash stock to my HTC One (UK M7ul) via the RUU method but this failed twice.

    The phone is currently will only boot into Bootloader regardless of what I try so will not even boot into Cyanogenmod at all, when ever i click recovery as CWM was installed the phone will flash for a second saying starting recover and then go straight back into bootloader.

    I am currently on Bootloader 1.55 with S-On - Phone is locked and will not allow me to unlock it.

    I really need some help to get my phone fully functional again on HTC Sense Stock Firemware.

    CID: HTC__001
    MID: PN0710000

    C:\platform-tools>fastboot getvar all
    (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: REMOVE
    (bootloader) imei: REMOVE
    (bootloader) meid: 00000000000000
    (bootloader) product: m7_ul
    (bootloader) platform: HBOOT-8064
    (bootloader) modelid: PN0710000
    (bootloader) cidnum: HTC__001
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 4304mV
    (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
    all: Done!
    finished. total time: 0.047s

    good thing you posted a ''fastboot getvar all'' but never post IMEI and SN, remove them from your post.

    To restore the phone back to stock with a ruu, you need to be s-off to downgrade hboot to 1.44. So you will have to unlock bootloader from htcdev, install twrp custom recovery, flash arhd 31.6, s-off with rumrunner, downgrade hboot and then run the ruu.

    all details can be found in this guide.
    1
    flash twrp recovery, and then type fastboot erase cache

    Then try booting into recovery, and adb push this rom.. http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
    1
    Have you tried rooting it? Watch the screen, it will ask for su permissions
    1
    Hi
    My HTC M7 is stuck in boot mode. I tried to install the Google Play Edition Rom with S-on.
    I had CWM but it seems to have diappeared after i used Guru_Reset_M7_3.62.401.1.zip
    I have tried Squabbi's HTC ONE toolkit but it gives me an error 01 when i try to push revone.

    fastboot getvar all
    (bootloader) version: 0.5
    (bootloader) version-bootloader: 1.44.0000
    (bootloader) version-baseband: 4A.21.3263.04
    (bootloader) version-cpld: None
    (bootloader) version-microp: None
    (bootloader) version-main: 1.29.401.16
    (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__016
    (bootloader) battery-status: good
    (bootloader) battery-voltage: 3790mV
    (bootloader) partition-layout: Generic
    (bootloader) security: on
    (bootloader) build-mode: SHIP
    (bootloader) boot-mode: FASTBOOT
    getvar:all FAILED (status read failed (Too many links))
    finished. total time: 0.041s
    adb push revone /data/local/tmp/
    error: device not found
    I cannot seem to be able to get a stock South African Vodacom ROM to sideload

    Please help me get S-OFF so that i can load any rom that will make the phone work.

    So is your phone stuck in bootloader or does it boot to a rom? You can't s-off without a working rom... so why are you trying to push revone anyway?

    push and flash a rom 1st, then s-off and after you'll be able to flash gpe rom.

    and like sahilzz said above, adb commands=custom recovery or booted rom, fastboot commands=bootloader so you can't use adb push from bootloader.

    btw better to use adb and fastboot from terminal instead of using toolkits ;)