Database Develop

Problem bootloader shows in OS-

The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
On the device ViperOne running 3.5.0 (4.3)
Now to the problem:
Flashing a recovery is performed, also displayed as OK, but it remains the old (TWRP 2.6.3.3)
Bootloader not lock possible:
(bootloader) Lock successfully ...
(boot loader) mipi display off
(boot loader) mipi_dsi_cmds_tx_ext
(boot loader) pm8921_vreg_disable function, vreg_id = 38
(boot loader) pm8921_vreg_disable function, vreg_id = 1
(boot loader) TZ_HTC_SVC_DISABLE ret = 534 642 044 (0x1FDDFD7C)
(boot loader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.139s
Flashing via sideload possible, unfortunately, according to Rome, it passes through or terminates. After the restart, but is ancient Rome it.
Getvar all the following shows:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(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.047s
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you

Fooox1 said:
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Click to expand...
Click to collapse
So if I understand correctly, you don't like the fact that firmware version not showing up; so I guess you have a couple of options:
1- (recommended in my opinion) get s-off using rumrunner
2- download this OTA: http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
and extract the "firmware.zip" inside, then flash that in fastboot ruu mode (TWICE in a row)
(you may need to relock bootloader for that)

Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.

Fooox1 said:
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Click to expand...
Click to collapse
rumrunner should work just fine, but you're not on 4.3 (firmware); you're hboot 1.54 would imply that you are running a 2.24 firmware, so you need a ROOTED 2.24 ROM with unsecured kernel; try this one: oops, looks like mega is down at the moment
find a 2.24 based ROM, rooted, with unsecured kernel, and rumrunner should work fine. maybe try Maximus 10 or 11: http://llabtoofer.com/category/devices/htc-one/page/2/

However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.

Fooox1 said:
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Click to expand...
Click to collapse
1- I understand your current ROM is 4.3, but that has nothing to do with firmware; firmware is <empty>, but hboot is 1.54, so it implies a 2.24 ROM.
2- to get rumrunner to work, you will need a 2.24 RUM
3- can you please boot to bootloader screen and make sure it says UNLOCKED (a screenshot would be nice )

So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.

Fooox1 said:
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Click to expand...
Click to collapse
keep bootloader UNLOCKED!!
download TWRP 2.6.3.0: http://techerrata.com/browse/twrp2/m7
verify MD5
go to bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, then flash one of the maximus 10 or 11 roms.
then go for rumrunner.

Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.

Fooox1 said:
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Click to expand...
Click to collapse
sounds too much like a locked bootloader, would you mind copy/paste command prompt, for example:
Code:
C:\ADB2>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/COLOR][/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\ADB2>

No problem:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C: \ Windows \ system32> cd ..
C: \ Windows> cd ..
C: \> cd fastboot
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.

Fooox1 said:
No problem:
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Click to expand...
Click to collapse
1- yes, i am aware that it can be renamed, though I usually just type the first letter of the filename (for example "o") and then press tab, eg:
Code:
C:\ADB2>fastboot flash recovery o
then press TAB, and:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
2-
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
Click to expand...
Click to collapse
mine gives me a lot more info:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
3- 8432KB

What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made ​​a backup is running, I want to restore it, is nothing.

Fooox1 said:
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made ​​a backup is running, I want to restore it, is nothing.
Click to expand...
Click to collapse
thanks for your kind comments, can i ask one more thing: MD5 of your "recovery.img"

The MD 5 Total:
84F04BFE70C03825689A457009235AD4

Fooox1 said:
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Click to expand...
Click to collapse
hmm, interesting I now have two versions of 2.6.3.0, one 10570KB and one 8432KB, but both worked fine:
Code:
C:\ADB2>fastboot flash recovery "openrecovery-twrp-2.6.3.0-m7 (2).img"
sending 'recovery' (8432 KB)...
OKAY [ 1.216s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.897s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.059s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.054s
-> bootloader -> recovery and it's there
have you tried using the unlocktocken again? maybe the phone is "semi-locked"

Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?

Fooox1 said:
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Click to expand...
Click to collapse
1- so i just tried the lock command:
Code:
C:\ADB3>[B]fastboot oem lock[/B]
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.126s
--> it rebooted back to the ROM, i went back to bootloader and sure enough it said RELOCKED
2- "I have the internal SD card into suspicion", we could check the partitions, but I doubt that it has anything to do with it, otherwise you would be experiencing a lot of random reboots.
3- also, have you tried other "tools" that work in custom recovery, such as: http://forum.xda-developers.com/showthread.php?t=1646108
just to see if recovery is working
4- did you flash any "boot.img" (kernel)?
5- have you tried "fastboot oem unlock"
6- have you tried flashing firmware (extracted from signed OTA) in ruu mode as mentioned in post #2?

2 The suspicion arises for me, since deleted, can be moved, but the device is, after rebooting, does not run or crashes. I have already backup, Rom.zip placed on the SD, but after rebooting into recovery they're gone.
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
4 I have already tried e.g. from Vodafone Rome. As usual, Ok, Ok, but not adopted.
5 At the command fastboot oem unlock:
C: \ fastboot> fastboot oem unlock
... INFO [ERR] Command error!
OKAY
6 I have tried (OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso) unzipped and used the firmware.zip.
Have the One_All-in One_Kit tried using the. But yes you use Flash Factory RUU zip. In this case, however, the device can not connect. About sideload's not the point. Will be transmitted to mobile phones, but the flash stops.
I also tried to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe . Device is detected and goes to the black screen (HTC ), of course aborts then , since it is not the correct CID .

Fooox1 said:
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
Click to expand...
Click to collapse
It almost sounds like a secured kernel, can u post exact details of the ROM you're running, including link.
Did u ever flash a "boot.img" ?
Sent from my HTC One using Tapatalk

[Solved]Htc one not opening after changind rom

hi. i tryd to change my rom to this rom - http://forum.xda-developers.com/showthread.php?t=2183023
wanted to do it because i need to do s-off and this was the only way. so i flashed it via recovry and did reboot to phone and everytime i do system reboot threw recovery the phone starts, it shows the htc one logo , and then reboots back to recovry.
+ i did factory reset so i dont have the rom on my phone anymore to try to install the rom again. so pretty ****eddd.
any help plz

guyeee said:
hi. i tryd to change my rom to this rom - http://forum.xda-developers.com/showthread.php?t=2183023
wanted to do it because i need to do s-off and this was the only way. so i flashed it via recovry and did reboot to phone and everytime i do system reboot threw recovery the phone starts, it shows the htc one logo , and then reboots back to recovry.
+ i did factory reset so i dont have the rom on my phone anymore to try to install the rom again. so pretty ****eddd.
any help plz
Click to expand...
Click to collapse
let's start with a nice "fastboot getvar all" (excluding IMEI and s/n), and what recovery (name and version) you are using

nkk71 said:
let's start with a nice "fastboot getvar all" (excluding IMEI and s/n), and what recovery (name and version) you are using
Click to expand...
Click to collapse
whats fastboot getvar all ?
and im using the touch recovry version. "Team win recoverry project v2.6.3.0

guyeee said:
whats fastboot getvar all ?
and im using the touch recovry version. "Team win recoverry project v2.6.3.0
Click to expand...
Click to collapse
1) well, a "fastboot getvar all", tells you (and us) a lot of information about your phone, and an example is pretty much in almost every single thread in this forum, be it the Q&A section, the general section, etc.
so it's time to do a little reading and googling, shouldn't take more than a few minutes.
we are here to help and assist you, not to teach you about fastboot/adb etc. there are more guides/how-tos/tutorials/etc around than i care to count... sorry if that doesn't sound nice of me, but you are expected to do some research yourself
2) if you have an m7_u/ul model then that recovery won't work with a 4.4 ROM, that's why we need the above output.

nkk71 said:
1) well, a "fastboot getvar all", tells you (and us) a lot of information about your phone, and an example is pretty much in almost every single thread in this forum, be it the Q&A section, the general section, etc.
so it's time to do a little reading and googling, shouldn't take more than a few minutes.
we are here to help and assist you, not to teach you about fastboot/adb etc. there are more guides/how-tos/tutorials/etc around than i care to count... sorry if that doesn't sound nice of me, but you are expected to do some research yourself
2) if you have an m7_u/ul model then that recovery won't work with a 4.4 ROM, that's why we need the above output.
Click to expand...
Click to collapse
ok well i searched for what it means but still dident find to much.
i have m7 android 4.2.2
this is what i know
EDIT : i understand its some button i press or something to get phone DETAILS. how do i get in to it?.

guyeee said:
ok well i searched for what it means but still dident find to much.
i have m7 android 4.2.2
this is what i know
EDIT : i understand its some button i press or something to get phone DETAILS. how do i get in to it?.
Click to expand...
Click to collapse
okay, hold on, are you on Windows? which version?

nkk71 said:
okay, hold on, are you on Windows? which version?
Click to expand...
Click to collapse
windows 7

guyeee said:
windows 7
Click to expand...
Click to collapse
okay download this: http://www.androidfilehost.com/?fid=23329332407585867
extract those files into a separate folder... i like to keep things simple, so I use: C:\ADB
then open a command prompt in the folder you extracted the files, connect your phone, and in bootloader, when it says FASTBOOT USB,
in the command prompt type:
fastboot getvar all
then copy/paste that output here (excluding IMEI and s/n)

nkk71 said:
okay download this: http://www.androidfilehost.com/?fid=23329332407585867
extract those files into a separate folder... i like to keep things simple, so I use: C:\ADB
then open a command prompt in the folder you extracted the files, connect your phone, and in bootloader, when it says FASTBOOT USB,
in the command prompt type:
fastboot getvar all
then copy/paste that output here (excluding IMEI and s/n)
Click to expand...
Click to collapse
< 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: 4.20.709.14
(bootloader) version-misc: PVT SHIP S-ON
(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: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f6d46eca
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
hereee

guyeee said:
< waiting for device >
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.20.709.14
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
hereee
Click to expand...
Click to collapse
you see, that wasn't too hard :good:
okay, so you have an m7_u (PN0711000), so you are free to flash anything for M7_U and M7_UL (they are both compatible, only the LTE hardware is missing in your phone, but that doesn't affect the software)
so, if you want to flash 4.4 ROMs, you need to update your recovery:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY and install the ROM
if the ROM is not on your phone, then you can use:
1- OTG
2- adb push
3- adb sideload
and example of adb push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Please remember to check MD5 on your downloads to make sure they are not corrupt
.

nkk71 said:
you see, that wasn't too hard :good:
okay, so you have an m7_u (PN0711000), so you are free to flash anything for M7_U and M7_UL (they are both compatible, only the LTE hardware is missing in your phone, but that doesn't affect the software)
so, if you want to flash 4.4 ROMs, you need to update your recovery:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY and install the ROM
if the ROM is not on your phone, then you can use:
1- OTG
2- adb push
3- adb sideload
and example of adb push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Please remember to check MD5 on your downloads to make sure they are not corrupt
.
Click to expand...
Click to collapse
ok so i downloaded the 2.6.3.4 RECOVERY and downloaded the 2.7.0.4b .
first tryd the 27.0.4b and when i get into recory it shows me TeamWin Recovryproject and it just blinks for endless amout of time. waited 5 minutes and still blinking.
then i tryd the 2.6.3.4 recovry and did the same.
whats up with that?
EDIT - now its even not recognizing the phone. i tryd to get back to the bootloader/fastboot page and it says "waiting for device" but my phone is stuck on the recovry that blinks all the time

guyeee said:
ok so i downloaded the 2.6.3.4 RECOVERY and downloaded the 2.7.0.4b .
first tryd the 27.0.4b and when i get into recory it shows me TeamWin Recovryproject and it just blinks for endless amout of time. waited 5 minutes and still blinking.
then i tryd the 2.6.3.4 recovry and did the same.
whats up with that?
EDIT - now its even not recognizing the phone. i tryd to get back to the bootloader/fastboot page and it says "waiting for device" but my phone is stuck on the recovry that blinks all the time
Click to expand...
Click to collapse
First: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Second, did you check MD5 on the downloads?
Third, if yes and they are OK, please reflash recovery and copy/paste your command prompt output

nkk71 said:
First: Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Second, did you check MD5 on the downloads?
Third, if yes and they are OK, please reflash recovery and copy/paste your command prompt output
Click to expand...
Click to collapse
did what u said. still doesnt work.
what do u mean MD5 ? i think its ok . the end of the file is .img and looking ok.
Anyway - heres the commant prompt :
C:\Users\user\Desktop\adb>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.i
mg
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'recovery' (4 KB)...
OKAY [ 0.213s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.235s
C:\Users\user\Desktop\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.052s
C:\Users\user\Desktop\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
Click to expand...
Click to collapse
maybe its because the "FAILED (remote: image error! (BootMagic check fail))"
whats that?

guyeee said:
did what u said. still doesnt work.
what do u mean MD5 ? i think its ok . the end of the file is .img and looking ok.
Anyway - heres the commant prompt :
maybe its because the "FAILED (remote: image error! (BootMagic check fail))"
whats that?
Click to expand...
Click to collapse
oh c'mon, you can't even be bothered with typing "how do i check MD5" into google? http://www.lmgtfy.com/?q=how+do+i+check+md5
and a "sending 'recovery' (4 KB)..." ... a 4KB recovery?? when it's supposed to by like 10MB (look at post #10 http://forum.xda-developers.com/showpost.php?p=52703915&postcount=10 )
.

nkk71 said:
oh c'mon, you can't even be bothered with typing "how do i check MD5" into google? http://www.lmgtfy.com/?q=how+do+i+check+md5
and a "sending 'recovery' (4 KB)..." ... a 4KB recovery?? when it's supposed to by like 10MB (look at post #10 http://forum.xda-developers.com/showpost.php?p=52703915&postcount=10 )
.
Click to expand...
Click to collapse
ok, checked and ur right , the codes dose not match. what should i do?

nkk71 said:
you see, that wasn't too hard :good:
Click to expand...
Click to collapse
triple thread:
http://forum.xda-developers.com/showthread.php?t=2753787
http://forum.xda-developers.com/showthread.php?t=2753780

Always good to ask multiple times

I think that if you are s-on you need to flash the boot.Img throungh fastboot... But I'm not sure
(Sorry for my english)

nkk71 said:
oh c'mon, you can't even be bothered with typing "how do i check MD5" into google? http://www.lmgtfy.com/?q=how+do+i+check+md5
and a "sending 'recovery' (4 KB)..." ... a 4KB recovery?? when it's supposed to by like 10MB (look at post #10 http://forum.xda-developers.com/showpost.php?p=52703915&postcount=10 )
.
Click to expand...
Click to collapse
could it be maybe because i did reset to all my phone so now i dont have root so it dont work/ maybe its the problem?

guyeee said:
ok, checked and ur right , the codes dose not match. what should i do?
Click to expand...
Click to collapse
you should download again, and don't use a download manager, once md5 is ok you can flash it... i'll upload a copy to dropbox in a minute
and my apologies if i wasn't online the whole time, seems my kids wanted a bit of attention too

[Q] Bricked HTC One M7 after attempting to restore to stock using YouTube video guide

I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(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: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

TexMachina said:
I am looking for some help in getting my HTC One M7 back up and working.
I used the online Cyanogenmod installer on my at&t HTC One M7 and it worked for the most part including where it contacts the HTC site to place the phone in developer mode.
Unfortunately the radio was far weaker and was losing it's signal all the time. I tried a few nightly's in hopes it was a bug that would be addressed but the issue with radio strength continued. Then an alert about an update from Cyanogen popped up and I trustingly clocked OK thinking that perhaps THIS would fix the radio stregth issue and I can keep my rooted ROM. Instead it broke Bluetooth entirely.
So I watched a YouTube video on restoring to stock. Apparently I can't post the link,
I got all the way to the part where I use fastboot to install the zip, HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
It failed but not in the manner described in the video I believe it is due to the phone security set to S-ON but I have yet to find a way to set it back to S-OFF from where things are now.
This was the steps from the video I followed starting with fastboot getvar version-main and the fastboot oem lock
I then went through the following commands
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.054s
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\fastboot>fastboot flash zip HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip
sending 'zip' (1249780 KB)...
OKAY [ 47.434s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.191s
And so it failed. The HTC screen came up but there was no progress bar so I know that fast boot is talking to the phone. I have been looking for a fix ever since and I am presently using a flip phone while working on getting the HTC One back.
Presently the phone boots directly into fastboot and will not allow me to do anything but reboot or power down but I can still use fastboot.
Revolutionary just sits at waiting for device.
The HTC One Toolkit is of no use as it also cannot see the device.
This is what is on the screen presently. Any help would be appreciated.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4M.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.12.502.2
eMMC-boot 2048MB
Apr 22 2014,01:10:58.0
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Here is the results for fastboot getvar all
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxxxxxxxxxx
(bootloader) imei: 354xxxxxxxxx
(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: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Ok
First thing .. edit your post above and remove the Serialno and IMEI
second the file you downloaded is my TWRP Backup and has to be restored using TWRP ...not flashed
it would be easier for you to use the Guru Reset I made
here >> http://www.androidfilehost.com/?fid=23501681358545274
So unlock your bootloader and flash TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload the Guru Reset from within TWRP
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Ok
First thing .. edit your post above and remove the Serialno and IMEI
Click to expand...
Click to collapse
Whooops!
Thanks for the heads up on that. I'll get to work on the fix and post an update later.

I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes

TexMachina said:
I am getting the signature verify fail error when attempting to load the recovery image now. Is this due to security being set on, S-ON?
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.
3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.116s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.863s
I made sure the images were in the fastboot directory.
Directory of C:\fastboot
08/23/2014 12:56 PM <DIR> .
08/23/2014 12:56 PM <DIR> ..
04/05/2012 05:49 AM 162,816 adb.exe
04/05/2012 05:49 AM 96,256 AdbWinApi.dll
04/05/2012 05:49 AM 70,144 fastboot.exe
08/23/2014 12:48 PM 986,880,264 Guru_Reset_M7_5.12.502.2_clsA.zip
08/23/2014 12:42 PM 9,404,416 openrecovery-twrp-2.6.3.3-m7.img
5 File(s) 996,613,896 bytes
Click to expand...
Click to collapse
no your doing fine.. just unlock the bootloader

clsA said:
no your doing fine.. just unlock the bootloader
Click to expand...
Click to collapse
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Stupid me, sorry. I had Cyanogenmod do it for me last time. I am on HTCDev getting my unlock token now.

TexMachina said:
I'm not sure I am doing this right. I am getting what appears to be a syntax error.
C:\fastboot>fastboot devices
HT34XXXXXXXX fastboot
C:\fastboot>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.023s]
finished. total time: 0.023s
This is the command I sued from the original YouTube video on locking it for stock ROM. It shows it as having already been locked now.
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.002s]
finished. total time: 0.002s
Click to expand...
Click to collapse
no you have to go back to HTCDEV.com and get the unlock token from htc

clsA said:
no you have to go back to HTCDEV.com and get the unlock token from htc
Click to expand...
Click to collapse
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password

TexMachina said:
Sorry about that. I had the Cyanogenmod install site do it for me last time.
I completed the unlocking but the Android Debug Bridge does not recognize the sideload command. It just spits back the help menu.
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
finished. total time: 0.146s
C:\fastboot>fastboot devices
HT34xxxxxxxx fastboot
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
sending 'recovery' (9184 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.718s]
finished. total time: 1.833s
C:\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.050s]
finished. total time: 0.050s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.034s
C:\fastboot>adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip
Android Debug Bridge version 1.0.29
... <entire help menu>
Perhaps my adb version is not correct. I did find reference to a push command in the help menu.
adb push <local> <remote> - copy file/dir to device
Also, there is that fastboot command I attempted to use before I unlocked the bootloader.
Also also, thanks for all the help.
edit: I didn't reboot into recovery. I did now but it is asking for a password
Click to expand...
Click to collapse
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
theirs no password on TWRP
To sideload
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
edit 3: I tried using the HTC One Toolkit which comes with adb 1.0.31. It gave me the following error
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT34xxxxxxxx recovery
adb sideload "File Path..."
* cannot read 'sideload' *
adb sideload "C:\fastboot\Guru_Reset_M7_5.12.502.2_clsA.zip"
error: closed
I am going to the gym to clear my head. Thanks again for all the help so far.

TexMachina said:
I appreciate all the help and I don't want to appear difficult but when I run the adb sideload Guru_Reset_M7_5.12.502.2_clsA.zip with the rom in the same folder adb simply refuses to recognize the sideload command. It spits back the help menu and I can't find sideload in said menu.
edit: I am using adb push to place the rom on the phones /sdcard directory and I am gong to use TWRP to install while in recovery mode. The copy is taking a while so if this is going to brick my phone let me know.
edit 2: now I don;t think I want to do this. The online resource don't mention anything specifically about installing a ROM using this method.
Click to expand...
Click to collapse
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone

clsA said:
your doing fine ..what was the error and why is sideload not in your version of TWRP ?
Is this the same resource that suggested flashing a TWRP recovery file with fastboot ? ... trust me you in good hands now ..just push the rom and flash it
during install choose no to install stock recovery and yes to Root the phone.
unless of coarse you want a stock unrooted phone
Click to expand...
Click to collapse
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.

TexMachina said:
I didn't realize the thread went to page 2. I thought you just dropped off the tread.
Sideload is in TWRP but it does ask for a password. I loaded TWRP 2.6.3.0 and it doesn't ask for a password.
I am pushing the Guru_Reset_M7_5.12.502.2_clsA.zip to /sdcard again. I will try the install once it is there.
Click to expand...
Click to collapse
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away

clsA said:
I can't tell you if TWRP 2.6.3.0 will work with the Guru Reset ..it's very old and untested
if you saw a password in TWRP 2.6.3.3 you just swipe to make it go away
Click to expand...
Click to collapse
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them

TexMachina said:
I loaded TWRP 2.6.3.3 again and I have to hit cancel to get past the password. I then can go to ADB Sideload but it always says Failed at the top while the only thing in the terminal window is Updating partition details.
I loaded TWRP 2.7.1.1 and was able to load up ADB Sideload and attempt a sideload from HTC One Tools which uses adb 1.0.31. I still get a syntax error when trying to use sidelaod from the command line.
It got as far as 77% before failing with this error message
sending: 'sideload' 77%
* failed to write data 'protocol fault (no status)' *
I also keep getting unable to mount /data and unable to mount internal storage errors on the TWRP ADB Sideload terminal.
I need to quit for the night. It seems like I am getting closer to a solution though.
I'll use the backup flip phone and I'll just have to talk to people while out tonight I guess. Thanks for your help.
Click to expand...
Click to collapse
Point D here: http://forum.xda-developers.com/showpost.php?p=53270352&postcount=21

clsA said:
Yeah have a great night.
When you get back >>
Is you phone sdcard full ?
have you done factory reset and or format data partition in TWRP?
If it's too full to push / sideload a rom.
TWRP does have a file manager feature you may need to free up space using it. adb 1.0.31 is the version i use all the time... never an issue.
you would get mounting errors if the partitions were formatted or erased...it's ok the new rom recreates them
Click to expand...
Click to collapse
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
Great !! Thank you !

TexMachina said:
That final instruction did it. With the partitions cleared I was able to sideload the ROM and it installed without issue in from TWRP 2.7.1.1
Thanks for all the help.
Click to expand...
Click to collapse
clsA said:
Great !! Thank you !
Click to expand...
Click to collapse
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now

xaviergreaux said:
a few months late to the party but how did you clear the partitions because I'm getting
E: Unable to mount '/cashe'
edit: Finished the adb push but HTC One still goes into Cyanogenmod......hopefully i can just leave this alone for a while cause atleast it turns on now
Click to expand...
Click to collapse
after pushing a file you still have to install it
adb sideload copy's the file and installs it. Push does not

[Q] Softbricked the M7, made it even worse afterwards. Do'nt know what to do

So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version, so I did that. But here's where it went from bad to worse.. I flashed what I thought was a new ROM, but apparently there was no OS installed now.. It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes.. So now I'm stuck here in fastboot without recovery and I can't flash a new recovery since I also did fastboot oem lock, and when I try to unlock bootloader all I get is "cannot open Unlock_code.bin" Any help would be greatly appreciated! I'm quite familiar with rooting, I've had similar ROMs on my phone before. The phone is from december 2013. Anyone knows what I can do

RichardFilipino said:
So, I've tried to get S-Off for a while, but my OS had to be the same as ROM version
Click to expand...
Click to collapse
not entirely necessary, sometimes helps, S-Off options (depending on your situation)
revone/moonshine -> rumrunner -> firewater -> sunshine (sunshine is by far the easiest and most reliable, but does cost $25)
RichardFilipino said:
It asked me if I wanted to unroot my phone in recovery, I unknowingly swiped yes
Click to expand...
Click to collapse
it asked you if you wanted to root, not UNroot.
RichardFilipino said:
"cannot open Unlock_code.bin"
Click to expand...
Click to collapse
cannot open / cannot load is usually MyFileNameIsWrong, or not in the same folder etc.

Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..

RichardFilipino said:
Sorry, I meant root yes..
The code name is right and it's in the right folder.. I've checked that multiple times even when trying to fastboot other files, recovery.img is able to read but not able to flash since I locked it..
Click to expand...
Click to collapse
please:
1- post a "fastboot getvar all" (excluding IMEI and s/n)
2- post the directory contents
3- also, please post the complete command line output as you try to flash the unlock token

getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can't post pictures yet is what it says .

RichardFilipino said:
getvar all:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
I can't post pictures yet is what it says .
Click to expand...
Click to collapse
Edit you post and remove your IMEI and s/n.
don't do screenshots, copy/paste command prompt
example:
Code:
C:\ADB2>cd \ADB3
C:\ADB3>dir
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB3
10/10/2014 16:37 <DIR> .
10/10/2014 16:37 <DIR> ..
30/09/2014 19:41 1,482 .twrps
06/02/2014 13:30 513,791 1.29.401.12_hboot_1.44.zip
21/03/2014 15:34 <DIR> 1.29.401.12_hboot_1.44_v2_old
28/03/2014 22:28 0 2014-03-28-adbsync.txt
21/12/2013 13:26 819,200 adb.exe
19/09/2013 22:17 98,304 adbsync.exe
21/12/2013 13:26 96,256 AdbWinApi.dll
21/12/2013 13:26 60,928 AdbWinUsbApi.dll
03/09/2013 13:05 4,164,094 aroma-2.70RC2.zip
30/09/2014 18:31 <DIR> BACKUPS
04/08/2014 18:47 493,416 blink.txt
06/06/2014 21:06 26,904 dmesg.txt
02/05/2014 18:39 0 enter
21/12/2013 13:26 160,256 fastboot.exe
07/03/2014 15:27 <DIR> fw
29/01/2014 18:58 25,271,322 fw_4.19.401.8_custom.zip
22/06/2014 17:22 30,308,418 fw_5.11.401.10_custom.zip
09/09/2014 19:09 30,305,900 fw_6.09.401.5_custom.zip
14/11/2013 21:54 3,645,591 Guru_Bootloader_Reset_1.0.zip
01/05/2014 11:51 1,047,040 mmcblk0p19_bak__xx.img
22/02/2014 14:18 1,047,040 mmcblk0p19_donkeykong1_repaired__xx.img
13/09/2014 13:45 1,047,040 mmcblk0p19_misc.img
02/05/2014 18:40 1,047,040 mmcblk0p19_repaired.img
01/07/2014 16:46 671,088,128 mmcblk0p36_cache.img
12/06/2014 12:22 262,144 mmcblk0p6_bak.img
19/11/2013 16:13 297,289,697 one-1.28.401.7-preloaded-modaco-withoutmovie.zip
09/06/2013 14:21 498,167 orig_hboot_1.44.0000_M7_RUUmode.zip
31/01/2014 11:35 <DIR> partitions
02/05/2014 15:31 <DIR> partitions_2014-01-13
29/04/2014 15:17 <DIR> partitions_2014-02-22
01/05/2014 16:41 <DIR> partition_x1
30/09/2014 18:31 <DIR> RECOVERIES
09/06/2013 16:02 648,208 revone
03/11/2013 21:56 249,028 Screenshot_2013-11-03-20-51-36.png
26 File(s) 1,070,189,394 bytes
10 Dir(s) 26,743,398,400 bytes free
C:\ADB3>
Code:
C:\ADB3>adb version
Android Debug Bridge version 1.0.31
C:\ADB3>fastboot devices
HT34xxxxxxxx fastboot <- you are in bootloader
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s

Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'

RichardFilipino said:
Oh it said excluding.. That was dumb.. Quite new to this all..
c:\adb>fastboot flash unlocktoken unlock.bin
error: cannot open 'unlock.bin'
Click to expand...
Click to collapse
file name is wrong

I named it that myself.

RichardFilipino said:
I named it that myself.
Click to expand...
Click to collapse
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s

RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
In your fastboot command window type
Code:
fastboot flash unlocktoken
Leaving a space on the end
Then drag and drop the unlock_code.bin into the command window, and hit enter.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Ah, I have to remember that one
Danny201281 said:
Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
Click to expand...
Click to collapse
RichardFilipino said:
That worked!
Although I tried to flash a stock RUU with the bootloader still locked..
c:\adb>fastboot flash zip "C:\adb\fastboot\RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3
.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.z
ip"
target reported max download size of 1514139648 bytes
sending 'zip' (1180768 KB)...
OKAY [ 47.548s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 166.616s
Click to expand...
Click to collapse
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x

nkk71 said:
You can't use those RUUs, those are for US T-Mobile (MID= PN0713000 + CID: T-MOB010), you have a German T-Mobile (MID= PN0710000 + CID: T-MOB101)
so you should currently be on 4.xx.111.x
Click to expand...
Click to collapse
Ahh yes that makes more sense , i thought it should be with identifier 111 after searching cid and mid.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
The fact that dragging and dropping the file worked indicates that previously there was a problem with the files name or location. Check your using the correct fastboot/adb folder for both storing your files and running your commands.
You can't downgrade untill your s-off. Your hboot suggests your on 4.xx.531.x so you can't use that ruu.
If your phone is not booting you need to push a Rom and try to s-off first. The initial problem you had (with no os installed) was probably due to rom/recovery incompatibility.
Download Twrp 2.6.3.3 form here
http://techerrata.com/browse/twrp2/m7 and flash it in fastboot.
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Then boot to twrp recovery home screen and push your Rom
Code:
adb push "nameofrom".zip /sdcard
You can use the drag and drop method for these commands also (if you need) just remember to leave spaces in the appropriate places. The command window will appear unresponsive until the push completes. Once it's done install the Rom with twrp recovery.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..

RichardFilipino said:
TWRP 2.6.3.3 didn't work.. Recovery still gets me to the screen of fastboot usb..
Click to expand...
Click to collapse
So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

So you flashed TWRP 2.6.3.3 and fastboot erase cache which were successful?
But when you boot to Recovery it goes back to the bootloader, Is that correct?
Click to expand...
Click to collapse
Yes, that is correct. Don't really know what options are left at the moment

RichardFilipino said:
Yes, that is correct. Don't really know what options are left at the moment
Click to expand...
Click to collapse
It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

It's possible something has been flashed that maybe shouldn't have and made a mess of the partitions.
Try this :- Download this stock recovery
http://d-h.st/Eq1
And flash it with fastboot remember to fastboot erase cache, then try boot to Recovery. If it boots the screen will be blank for a short while, then display an image of a phone with red exclamation this is normal. Holding volume up and press the power button to reveal the stock recovery menu. Ignore the Mount sd card errors that's also normal in stock recovery. Now perform a factory reset and wipe cache.
Reboot the phone back to the bootloader and flash twrp 2.6.3.3 then fastboot erase cache. Hopefully now twrp will boot. :finger-crossed:
If it does go into the "Wipe" options and select " Format Data" you will be prompted to type yes to confirm. Then 're-push the Rom and install with TWRP.
Click to expand...
Click to collapse
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.

RichardFilipino said:
Tried that:
Code:
c:\adb>fastboot flash recovery C:\adb\recovery_4.20.111.21.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12422 KB)...
OKAY [ 1.527s]
writing 'recovery'...
OKAY [ 0.928s]
finished. total time: 2.456s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.527s]
finished. total time: 0.527s
Went from fastboot USB to bootloader, tried to enter recovery.. Nothing, straight into fastboot USB again.
Click to expand...
Click to collapse
sorry man I'm running out of ideas here. Only options left really is to flash firmware or an ruu. Unfortunately I can't find anything that will work for you with s-on.
What was the last recovery you had working on the phone?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] bricked?

hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?

Reflash factory imagine

Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.

uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk

and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.

uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979

ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!

uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!

Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.

12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>

uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.

yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.

uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.