[Q] I need help Please Rogers HTC One stuck in h-boot - One (M7) Q&A, Help & Troubleshooting

Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading

SaadQamer said:
Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point. Thankyou for reading
Click to expand...
Click to collapse
Can you still boot in bootloader?
if you can, you can flash a custom recovery (TWRP or CWM) again so you can install a custom rom.
it would be best if you can do fastboot getvar all and post the result here so everyone can have a clearer view on what RUU you need. will definitely help to help you properly.

Are you able to get into fastboot? If you can get into fastboot, you'll be able to flash a custom recovery, and then from there on you can either mount USB storage or use adb sideload to flash a rom onto your phone.

Thyankyou for responding
thanks for responding, if bootloader is the menu with fastboot and factory reset and those options then yes i can boot into that because my phone is off right now and i can hold vol. down and power to go into that. not sure how i can flash a custom rom though or even a recovery any help with that would be greatly appreciated as well. the phone is currently blinking with an orange light leaving me to assume the battery is deal so i cant even turn it on at the moment but i will post the getvar command when it does thankyou so much, by the way the phone is an htc one rogers just for clarification.

getvar
when i typed in fastboot getvar all i got this
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34GW901697
(bootloader) imei: 354439053152296
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(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.064s
again any help with these will be greatly appreciated

Related

please help! htc one possible boot loop of death.

edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(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: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !
Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.
hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom
another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(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: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>
Deleted
garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this
garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.
Deleted
when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.
sorry didnt read your reply, well it didnt initialise so no s off anyway
garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us
im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option
right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now
guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me

[Q] Soft-Bricked HTC One - Want to go 100% stock again.

Solved thanks to @alray
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: (not sure if you need this)
(bootloader) imei: (not showing this to you)
(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: 4262mV
(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!
Click to expand...
Click to collapse
CorcoranM96 said:
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
Click to expand...
Click to collapse
the ruu failed because you need s-off to use them with hboot 1.55 (require hboot downgrade to 1.44 which require s-off)
so now your best option is tu install a guru reset. Use this file
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
video tutorial here
so now your best option is tu install a guru reset.
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
Thanks @alray for the reply! I'm trying that now, I'll let you know how I get on!
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
CorcoranM96 said:
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
Click to expand...
Click to collapse
Move the .zip file to your fastboot/adb folder. boot your phone in recovery. then:
Code:
adb push name_of_file.zip /sdcard/
then in recovery select ''install'' and slect the zip you pushed
no need to use otg cable
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
CorcoranM96 said:
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
Click to expand...
Click to collapse
what recovery are you using? You are doing adb command in recovery right?
Solved!
alray said:
what recovery are you using? You are doing adb command in recovery right?
Click to expand...
Click to collapse
Fixed it, I just changed computer... My phone works perfectly and is returned to stock! :good:
Thanks a million @alray!

[Q&A] |TOOL| HTC One Toolkit [M7] • v3.2.0

Q&A for |TOOL| HTC One Toolkit [M7] • v3.2.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for |TOOL| HTC One Toolkit [M7] • v3.2.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
McCovican said:
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
Click to expand...
Click to collapse
Were both files (firewater and temproot) in the same adb/fastboot folder?
4304
majmoz said:
Were both files (firewater and temproot) in the same adb/fastboot folder?
Click to expand...
Click to collapse
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need S-OFF to root. You just need a unlocked bootloader, custom recovery and SuperSU. Here are the instructions.
Also, I would use the raw adb and fastboot commands without the toolkit. I would recommend the Minimal ADB & Fastboot Tool. Most Dev's and OPs will give the commands for how to do certain things so you could just copy and paste. It also gives you more control on what is happening to your phone.
McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need s-off to root the phone. But with s-on you will be limited to flashing Roms, Recovery and Kernels. Firmware updates are possible but must be Signed firmware and can only be flashed with a 're-locked bootloader.
Just flash TWRP Recovery 2.6.3.3 boot to TWRP then reboot system from TWRP. You will be prompted to root the device Select yes. You may need to update binaries but that's it your done.
Better still just flash a prerooted Rom with TWRP. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Bricked phone using tool
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(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: 4316mV
(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
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
???????????? fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
redlupine said:
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(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: 4316mV
(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
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
????????????fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
Click to expand...
Click to collapse
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu. http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu.
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
redlupine said:
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
Click to expand...
Click to collapse
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
I would however like to bring this to the attention of @nkk71 let's wait to see what he has to say on this subject
I've never seen a getvar so messed up so let's hope nkk71 has some idea :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Danny201281 said:
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
Click to expand...
Click to collapse
You are right, I'm posting this to the bricked help phone thread:
[Unbrick Service] Bricked Phone? Need Help? Look Here.
Lollipop
Hey,
I have a UK M7 (locked to H3G if that matters) currently running Android Revolution w/ Sense (rooted).
I have set my CID to 11111111 , I have S-OFF, HBOOT-1.56.0000 and I am looking load the OTA for the Google Play Edition (Lollipop 5.0.1) on to it using your tool. And then I will re-root.
Really I just wondered if anyone thinks that this is a bad idea for any reason.
htc one stock
I lost my stock back-up for warranty CID- VZW__001
OS- 1.10.605.10
I d like to return to full s-on stock for warranty make a new back-up
Then use tool kit to return to s-Off TWRP CAN you please help
help..
hello there OP , thankyou for the time you have put into this tool, im a noob with smartphones, and once tried 'windroid' one-click/aio type device from xda forums, it ended up with me unlocking the token thingy, but then it would not go frther, it actually put a cross X over the pic of a HDD or looked it, i quickly hit power off/one and it booted automatically into a factory install/reset kind of environment.. since then ive been to scared to even try rooting again... but your kit and hansoon one seem O.K , but my problem is, how do i find what version exactly of phone that i have, the thing lookes like the htc one x, i recall updating the rom couple of times now, so it is on kernel v3.* , but again, i need to somehow find this info and then try again using a app that actually works..i getting good reviews on your thread so i guess im hoping for some magic here, i know the questions ive asked are very nooby, but trust me i thought i had killed it, i remember unlocking the token id, i recall pasting this in and then it showed up as unlocked.. i have kept my .bin file handy if ever i re-needed it.. so i guess that part is done.. i would LOVE to run something wich doesnt kill the battery, as im experincing now is 1day lasting full charged..without many apps :S
i am sorry for the length of this question, its just i had a bad experience once, dont want that again.. but im hanging to try again... feel free to respond, or not respond, i know what im askingshould be here somewhere, although the model, if it is a one or one-x i guess is the only thing i am curious of..is how would i know because a couple of models looked very similar.. i THINK im running android 4.2.2 ,kernel 3.* , i beleive there is a couple.
i know there is a new exploit out for v3 kernel. would this not help make the tool 1000% proof.?? one wich i was told is now being used for android v5 wich apprently roots every device upto v5, so thats all v3/4 and 5 in one exploit...i have 'heard' that xda do have it and are using it for newer phones.. but what an oppurtunity,if this was added into your tool,it would be 100% proof on everything android.. just a thought but, you seem like a happpy go lucky cool op, so im just saying, if i was working on a tool, id work alot more on exploitation of the device/making sure there is no residual pains, and simply adding ballon like tips around the app kinda cool touch... i like your tools look, and i wish to use it.. but i dont want to endup being locked in phone..
i have htc one x , 32g, i believe :S it LOOKS exact same as the htc one-x,it was given to me as a one-x (sold to me),and at that stage,it was on ebay prettymuch on par with the other htc one-x,so it would be one-x im about 99% sure, i just now wonder about the updates i allowed the phone to perform,wich then changed android version/kernel.
I dont know if you have the answer i need, or answers if you wish to answer the entire post,because your going to get it,and really its you i want to ask anyhow, so its fine if it stays private, although since it is noobish, i guess you could go either way... i do raise some issues for some people to scared to get 'bricked' .. my phone uses vodaphones manager,wich i have uninstalled everytime it installs,now it has embedded itself though,and it only deletes down to un updated vodafone manager, i deleted every other voda app on there... so its basiocaallly a question of, do i go ahead with this version, or do i wait for something thats 100%.. im sure alot of people are like me, alittle hesitant to root..or had bad experiences.. ive rooted my samsung duo young fine, but the htc, well.. its got me sofar..i see all the one touch tools,i grabbed them, but wich one will actually work right.. remembeing i have used one wich was labelled windroid from xda ,it only made me paranoid as hell to use a working one, and then, i also think of exploitation, and i seriously wonder if your app can rooot an updated one-x on 4.2.2,and it does not go higher, it seems like two updates to get to this version,no updates now for about 6-12months,so i am looking here at a handful of exploits wich DO work and will root, ie; futex ; or asking you, if you think that would make your app even nicer,and erhaps a cleaner root process is achieved with something new, i know the one mentioned in UG came to xda,so,why is there no updated packs :?
i would hope that things got updated,maybe just me,but if theyre updating theyre firmware, then surely you must update your end to handle this... so is MY phone going to be o.k with this app, or do i wait and hope there is a newer expoloitation achieved ?
its a long post,, but i hope im getting through to some dev, theres alot to be done with these packs,specially with things like google play pad coming out, id like to buy one of those,but again,how do i trust apps wich have not been updated in ages...yet my phone has updated.. it just blurs the mind as to how you would get around kernel patches..i know android has many exploits,but not clean ones like the current one in use.. i will look in on this thread and hopefully someone will explain to me how to get the exact phone info, and alittle more info on how things getting rooted, ie; exploitation , and kernel images/links to GOOD working kernels already tested.. noobs like me dont want to test 5 types, we want one GOOD one
im sorry to write alot,but this is good topic ive been walking around for to long. i even have a spare iphone sitting here just for when i root the one-xx.i am confdent that if anyone will help me on this,its going to be xda forums, simple as that... i dont even bother reading many other blogs nomore,everything android is here..its a great little place,and i love it sofar.. exploring the roms,reading,wanting :[.. i will await some feedback. again, apologies for long post,but i trying to be thorough as i can on each issue. cheers.
dru
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
apologies for the long post... ofc i dont expect it to go public BUT it does raise some issues..i dont see all of xda forum yet, but every search sofar has yielded results..only areas i find lacking is the rooting devices actually explaining wich root method is being used, its not a necessity,but some root methods leave memory leaks/other bugs wich can be phone specific, ome wich dont do anything atall because they bypass aprotections properly.
IF there is a thread on exploiting, i will join there..someone has to be sharing the exploits,and so they should, but alittle more info could be given to public,i guess not all people care,they just want one-click, well, i care about what i stick in my phone, so flashing a custom rom, kernel to me is a big deal i expect done right once..
i look forward to some feedback on my htc issues.
Sense Rom for S-off?
Do I have to install a sense-based rom before i go on s-off with Firewater?
Greez philipp
s-off htc one x
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Griffmiester said:
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Click to expand...
Click to collapse
You are not at the right place, this is the HTC One forum (M7) not the One X (Endeavor or Evita)
If you have an Endeavor One X (Tegra 3 cpu variant) , S-OFF is not possible
If you have an Evita One X (XL) (Qualcom cpu variant), head to this forum: http://forum.xda-developers.com/one-x-att
will i be able to use the toolkit with this phone...
Click to expand...
Click to collapse
No this is not for the One X, anyway better to learn how to use ADB and Fastboot .
Do this toolkit work with last android update?
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
LucaBalzano said:
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
Click to expand...
Click to collapse
Then I would suggest spend a few days to learn. Even if it does work and something goes wrong you won't know how to fix it. Do the proper research and learn to do things the right way instead of using a tool kit.
HTC ONE X+
***LOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
HBOOT
SERIAL: FA2ASW105934
CANNOT GET OUT OF HBOOT SCREEN OR UE ADB FASTBOOT

[Fixed] Bricked Hboot 1.44 with RUU 1.31 (Explanation on how solved in OP)

[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(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.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.
toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you
alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...
nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(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.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.
alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:
alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?
nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.

HTC One m7 sprint Bricked??

Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(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
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(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
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.

Categories

Resources