Database Develop

[GUIDE] Updating HBOOT after XTC-CLIP from 0.x to 1.01.0001 for AlpharevX WITHOUT RUU

Thought I'd write this up, as it applied to me also.
If, like me, you used XTC Clip to S-OFF your Wildfire, and then flashed an old RUU (0.X HBOOT) to run Unrevoked to gain ROOT, and have since then flashed a custom ROM (CM7 for instance), and don't particularly want to run an RUU to gain 1.01.0001 HBOOT.
Now, you're probably wondering... Why do I need to run AlpharevX if I'm already S-OFF via XTC-CLIP?? Simple...
AlpharevX HBOOT has some nifty fastboot commands enabled, such as being able to flash RADIO images, RECOVERY, etc etc all from Fastboot. By default, even being S-OFF via XTC-CLIP, you're still pretty restricted on what you can do. So if you do want to flash RADIO images via FASTBOOT, or alternative recovery versions, then you will be much better off with AlpharevX!
This works for all platforms (Windows, Mac, Linux)
LINUX USERS - MAKE SURE YOU RUN COMMANDS VIA 'sudo'
You need a knowledge of how FASTBOOT works! THERE IS ALSO A CHANCE YOU MAY BRICK, BE WARNED! PLAYING WITH HBOOT IS A RISKY BUSINESS
1) If you use Windows (unsure on mac) MAKE SURE HTC SYNC IS INSTALLED!
2) Get yourself a copy of fastboot. - http://developer.htc.com/adp.html
3) Download the file "firmware.zip" attached to this post.
4) Reboot the phone into Bootloader - Power off device, now hold VOLUME-DOWN and keep holding while you press Power to turn it back on.
5) Select the option FASTBOOT on the Phone, and press POWER to go into it.
6) Connect the phone to your PC via USB Cable. Your phone should now display FASTBOOT USB
7) Open a command prompt/terminal and 'cd' to the folder where you downloaded both fastboot AND firmware.zip
8) Ensure that you can connect to the device:
Code:
# fastboot devices
should return something like
Code:
SH13HPY05183 fastboot
IF YOU GET NOTHING LISTED, YOU ARE EITHER NOT IN FASTBOOT, OR YOU DON'T HAVE HTC SYNC INSTALLED
9) Issue the following commands:
Code:
# fastboot erase cache
# fastboot reboot oemRUU
(wait now until there is a big grey HTC logo on the screen with a black background)
# fastboot flash zip firmware.zip
You should get the following display:
Code:
sending 'zip' (196 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
OKAY [ 7.837s]
finished. total time: 8.071s
Now type:
Code:
#fastboot reboot bootloader
You should now have 1.01.0001 HBOOT and still be S-OFF ready to run AlpharevX.
10) Reboot back into Android (with whatever flavour ROM you are running), and now run AlpharevX - there you go! AlpharevX HBOOT should now install flawlesly, and you've not had to run either an RUU, or a Wipe and lose all your stuff
Code:
=============================
| AlphaRev-X HBOOT S-OFF tool |
=============================
Waiting for device...
Found your device: HTC Wildfire (buzz-1.01.0001, Android: 2.3.4)
This is a beta release and requires a beta release key.
Please visit: http://alpharev.nl/x/beta for more information.
Enter beta key [serial: ************]: ****************
Beta key accepted - thank you for participating!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
Waiting for fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Rebooting to fastboot (again)...
Waiting for fastboot...
SUCCESS - Life gave us lemons, we didn't make lemonade!

Can this be flashed through CWM recovery?

I presume this won't work if you're not already S-OFF?
I started out with a 0.80 HBOOT and never upgraded so I could continue to use Unrevoked.

Hello!
I have rooted my Wildfire and i am on HBoot 0.80.
Can I use your Guide also to became a bigger HBoot Version than 0.80 to use the Alpharev Tool for S-off?
Sorry for my bad English....
Greets Hollux

Hollux74 said:
Hello!
I have rooted my Wildfire and i am on HBoot 0.80.
Can I use your Guide also to became a bigger HBoot Version than 0.80 to use the Alpharev Tool for S-off?
Sorry for my bad English....
Greets Hollux
Click to expand...
Click to collapse
No, as the title states this is only for those who have S-OFF'ed previously using XTC Clip.

Im stuck here:
# fastboot reboot oemRUU
(wait now until there is a big grey HTC logo on the screen with a black background)
I dont think thare's a command with extension oemRUU buildin (Win version)

DeCex said:
Im stuck here:
# fastboot reboot oemRUU
(wait now until there is a big grey HTC logo on the screen with a black background)
I dont think thare's a command with extension oemRUU buildin (Win version)
Click to expand...
Click to collapse
Same here, fastboot reboot oemRUU isn`t recognised. Am i missing something ?
I need this because mu wildfire is stuck in hboot and i cannot enter recovery and when powering on it goes straight into fasboot. Power and vol up/down don`t work while in hboot or recovery. I`m on the xtc clip hboot 0.80.0007 s-off and i thought to give it a try.
Well, i managed to update my hboot to 1.01.0001 s-off but there`s still something wrong with my phone. It doesn`t boot into android not even after typing in fastboot reboot oem, it hangs on the htc green logo and the white background. I successfully flashed the latest wwe ruu without warnings so i suppose there`s nothing wrong with the phone`s hardware.
Please help

[Q] Specific RUU

Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte

Linte said:
Hello there! First: Thanks for every answer in return - I'm currently a little bit in a pitch...and appreciate any help.
My problem is: my HTC One is currently stuck in a bootloop, due do some (my own) failures, when I tried to use a ROM.
In my own idioty I didnt made any backups or anything else.
Long story short - I would like to try to install a RUU for my version, but there is absolutely noone.
I'm on version-main 1.29.111.16 with the CID T-MOB101 and HBoot 1.44. I tried to search everywhere possible for a download,
even tried to personal message a few people who maybe could have the needed RUU, but so far no answers / no luck.
Tried to get S-OFF and use another RUU, but whatever I do, I cannot see my device under "adb devices". Tried everything /latest driver, cables and so on) so far but it absolutely wont show under adb and so I cannot see any other way to get S- OFF. Thats why I rely on the RUU for my version. So im here to ask, if someone else could give me a hint on where to find this RUU...or any tips on getting my ONE S-off. But like I said, I guess I tried almost everything I have read about (countless hours on google and xda- forum).
I know, I may write complete and utter nonsense - toying with my precious phone was like the biggest failure in my last few months and I regret it. :l
Thanks in advance!
Greetings,
Linte
Click to expand...
Click to collapse
There is a Guru reset here
http://www.htc1guru.com/downloads/stock-rom-downloads/
Read the instructions on how to flash
http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/
Sent from my HTC One using Xparent Skyblue Tapatalk 2

Thanks for the fast reply.
The problem is: I cannot get into recovery. I tried to flash the the recovery and the boot via fastboot from the corrospending
Guru, but I'll only get an "signature verify fail" error. I hoped for the fitting RUU- version for my 1.29.111.16, because it seems
to me that it may be the easiest solution for my problem.
Greetings,
Linte

Hi. Can you post your actual command and output?

SaHiLzZ said:
Hi. Can you post your actual command and output?
Click to expand...
Click to collapse
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\adb>fastboot flash recovery rec.zip
error: cannot open 'rec.zip'
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.062s
C:\adb>fastboot flash rom Guru.zip
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4D.14.3250.26
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.111.16
(bootloader) version-misc: PVT SHIP S-ON
(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: 4252mV
(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.043s
C:\adb>
Click to expand...
Click to collapse

First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.

Seanie280672 said:
First of all, your drivers are missing or outdated, download HTC sync manager from the HTC site and install, then remove HTC sync from your computer, just leaving the drivers.
Next question is do you have usb debugging enabled on the phone in developer options ?
If you can't see developer options then goto menu, settings, about, software information, more, then tap build number 7 times, it should say you are now a developer and you will have a new menu in settings called developer options where you can enable usb debugging.
When you type adb devices it should list your phone's serial number not just say list of devices attached.
It could also be that you need to update your adb and fastboot, I had to do it recently after getting this phone, after using the same fastboot and adb for years.
Click to expand...
Click to collapse
Again sorry for the late reply, business struck again. :l
To your points: Already installed the latest HTC drivers from their homepage more than four times so far. Im pretty sure I have the latest version and after installing, I deinstalled the Sync Manager, like you told me to do. Still no changes.
I cannot see any developer options, simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Also I got the latest fastboot and adb from the (SDK- Manager) Android Developer Tools- Bundle. That's why I am so clueless about my phone not getting recognized by my PC with "adb devices". Strange thing is, I get the ID of my phone in "fastboot devices"...
Later this da I will try to connect my phone to my new, clean Laptop, with the lastest HTC Drivers and adb/fastboot. Maybe this will help.
Thanks so far!
Linte
Edit: tried it with a clean Laptop, latest ADB, latest HTC Sync (installed and deinstalled) and different USB- slots. No success. Adb sill only says
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
Absoluteley no clue where I go wrong here... :l

Linte said:
Hey! Sorry for the delayed anwser (was on a short holiday trip),
I tired almost everything possible, as far as I know. So far I tried to flash allmost everything, from the .img (recovery/boot/) inside the Guru, wich bored_stupid sent me in his post, aswell as the whole .zip.
No matter what I try, I always get this "signature verify fail"- error. Thats why I was hoping for someone with the mentioned RUU, because they seem to work so far - except my HTC says something similiar: "RUU Error [132]: Signature error."
Greetings,
Linte
Btw, here's my getvar, in case it's needed:
Click to expand...
Click to collapse
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2

bored_stupid said:
I'm assuming your using Windows 8 or 8.1. They have an issue with hboot 1.44. Can you use a PC with Windows 7 or read here to make a Ubuntu USB live OS
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Hmm...nope. So far I have only used Windows 7. But like I said, no progress at all. Everythings updated, even on a freshly installed system. Different USB- Ports and so on. No success... :l

Tried to get S-OFF and use another RUU
Click to expand...
Click to collapse
You need a working rom to s-off the phone.
simply because I can't get any further than the bootscreen. Im stuck within a bootloop.
Click to expand...
Click to collapse
Linte said:
Code:
C:\adb>[B][COLOR="Red"]adb devices[/COLOR][/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
ADB commands only works from a booted OS with usb debugging ON or from custom recovery. So ADB will never output your device is connected if you are not in the OS or in custom recovery. From bootloader, use FASTBOOT commands
i.e:
Code:
fastboot devices
Code:
C:\adb>fastboot flash recovery rec.img
sending 'recovery' (9136 KB)...
OKAY [ 1.121s]
writing 'recovery'...
(bootloader) signature checking...
FAILED[B][COLOR="Red"] (remote: signature verify fail)[/COLOR][/B]
finished. total time: 2.062s
Click to expand...
Click to collapse
Looks like your bootloader is locked, you need an unlocked bootloader to flash the recovery partition
Code:
[COLOR="Red"][B]C:\adb>fastboot flash rom Guru.zip[/B][/COLOR]
sending 'rom' (1056149 KB)...
OKAY [ 41.443s]
writing 'rom'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1174.768s
Click to expand...
Click to collapse
This one is a custom rom (reset rom). You can't flash custom rom from fastboot. You can only flash custom rom from custom recovery.
from fastboot, all you can do is
flashing a custom recovery (with bootloader unlocked)
flashing a RUU.zip in ruu mode
flashing a firmware.zip in ruu mode
all roms (except RUUs) are flashed from custom recovery, including guru reset roms.
btw, there is no RUU for your phone.
unlock bootloader
flash twrp recovery 2.6.3.3
download and save this file to the same folder you have adb and fastboot in
open a cmd prompt from you fastboot/adb folder and boot your phone in bootloader mode (fastboot usb)
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb push the guru reset rom to your /sdcard/ from twrp recovery
download this guru reset rom: http://www.htc1guru.com/dld/guru_reset_m7_2-24-111-3-zip/ and save it to your adb/fastboot folder
boot phone in twrp recovery
open a cmd prompt form your adb/fastboot folder
Code:
adb push guru_reset_m7_2.24.111.3.zip /sdcard/
wait for the file to transfer (5-10 min, there is no progress bar, just wait until adb says it complete)
install the reset rom using twrp

Wow! Thanks a lot!
After unlocking my bootloader again I was able to get into recovery. From there it was easy going to install the Guru.zip via sideload ("Install zip" didnt work for some reason, said something similiar to "Couldn't mount /sdcard/". But sideload worked fine.). Updated everything and my phone runs now like it always had!
Again: really, really thanks a bunch! Thought I somehow ruined my phone, but thanks to you all I got it done. I really appreciate your effort in helping me! You guys are awesome.
Greetings,
Linte
PS: I won't do anything stupid with my phone again, learnd this the hard way.

[URGENT] Phone Stuck in Fastboot !!! Can't Reboot !!! Can't RUU

I was running my rom fine an hour ago, until I decided to try and reboot into recovery to make a backup. Instead of recovery, I ended up in bootloader. I then tried to enter recovery through the menu. It rebooted into bootloader and flashed the "3 Skating Androids" in the middle of the screen. I then tried to simply restart, and it did the same. All buttons did this. I then tried to run the RUU, and lock the bootloader from command prompt. I entered "fastboot oem lock", and it returned the following:
Code:
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [PG_ERROR] htc_pg_hdr_get(117):
(bootloader) sd_read_sector error
(bootloader) [PG_ERROR] htc_pg_part_hdr_get(169):
(bootloader) htc_pg_hdr_get failed
(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 = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.094s
I am unable to relock the bootloader, therefore I am unable to return to stock. I can't boot, and I have no way of recovering. I am sick and tired of these situations with my phone. What on earth could I possibly do to fix this ****?!

Your bootloader is unlocked correct? Do you have S-off? You can flash the RUU without re locking the bootloader if you have S-off.

chuckwago88 said:
Your bootloader is unlocked correct? Do you have S-off? You can flash the RUU without re locking the bootloader if you have S-off.
Click to expand...
Click to collapse
Unfortunately I don't have S-OFF, and I was unable to get it. I was running ViperOne 6.2.1 with Elemental X 14.12.
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
OS-4.19.661.8
eMMC-boot 2048MB

HTC1V said:
Unfortunately I don't have S-OFF, and I was unable to get it. I was running ViperOne 6.2.1 with Elemental X 14.12.
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
OS-4.19.661.8
eMMC-boot 2048MB
Click to expand...
Click to collapse
Try reading through this http://forum.xda-developers.com/showthread.php?t=2633276 . And you can find more instructions and information here http://forum.xda-developers.com/showthread.php?t=2632351 . I had a hard time getting it done, I was HBOOT 1.57, but firewater is what got it done for me.

chuckwago88 said:
Try reading through this http://forum.xda-developers.com/showthread.php?t=2633276 . And you can find more instructions and information here http://forum.xda-developers.com/showthread.php?t=2632351 . I had a hard time getting it done, I was HBOOT 1.57, but firewater is what got it done for me.
Click to expand...
Click to collapse
Thanks for trying to help. But my device appears to softbricked. I don't have access to my operating system, so S-OFF is not even remotely possible. Anyone else have any possible solutions?

I am pretty sure the term soft bricked means you can still boot into your bootloader. Hold down the power and volume down buttons until it gets there, mine took 20+ seconds when I was soft bricked. From your bootloader you can flash a recovery and then you should be able to get S-off. If you can't get into recovery or the bootloader I don't know what else to tell you.

chuckwago88 said:
I am pretty sure the term soft bricked means you can still boot into your bootloader. Hold down the power and volume down buttons until it gets there, mine took 20+ seconds when I was soft bricked. From your bootloader you can flash a recovery and then you should be able to get S-off. If you can't get into recovery or the bootloader I don't know what else to tell you.
Click to expand...
Click to collapse
Unfortunately I cannot boot into recovery. Every time I hit an option, the bootloader restarts. I will try leaving my phone turned off for the next day, to see if draining the circuits does anything.

HTC1V said:
Unfortunately I cannot boot into recovery. Every time I hit an option, the bootloader restarts. I will try leaving my phone turned off for the next day, to see if draining the circuits does anything.
Click to expand...
Click to collapse
If you can get into the bootloader you should be good to flash a recovery through fastboot. Try looking at this link, get all the correct files for your phone and computer, and look towards the end of the page where it talks about download via fastboot, this is what you need to do. http://teamw.in/project/twrp2/164 . After you get the TWRP installed, you will be able to sideload a rom from there.

chuckwago88 said:
If you can get into the bootloader you should be good to flash a recovery through fastboot. Try looking at this link, get all the correct files for your phone and computer, and look towards the end of the page where it talks about download via fastboot, this is what you need to do. http://teamw.in/project/twrp2/164 . After you get the TWRP installed, you will be able to sideload a rom from there.
Click to expand...
Click to collapse
As I said earlier, I am unable to boot into recovery. I've tried CWM, TWRP, and stock. Every time I try to use a command, I get an error. I get "FAILED (remote: image update error)" every time I try to flash a recovery. It's like my fastboot mode is broken. I also tried booting directly into recovery with "fastboot boot twrp.img" but this didn't work, and just froze the device.

HTC1V said:
As I said earlier, I am unable to boot into recovery. I've tried CWM, TWRP, and stock. Every time I try to use a command, I get an error. I get "FAILED (remote: image update error)" every time I try to flash a recovery. It's like my fastboot mode is broken. I also tried booting directly into recovery with "fastboot boot twrp.img" but this didn't work, and just froze the device.
Click to expand...
Click to collapse
What stock recovery are you using ?
Here's the steps I would take
from bootloader choose shut down
wait about 5 min reboot to the bootloader fastboot USB
then fastboot erase cache
fastboot reboot-bootloader
now flash Stock recovery
fastboot flash recovery stock_recovery.img
fastboot erase cache
fastboot reboot-bootloader
now enter stock recovery (power + volume up after you choose it in the bootloader)
when you see the menu choose factory reset
now start over with the custom recovery
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery 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 this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
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:
What stock recovery are you using ?
Here's the steps I would take
from bootloader choose shut down
wait about 5 min reboot to the bootloader fastboot USB
then fastboot erase cache
fastboot reboot-bootloader
now flash Stock recovery
fastboot flash recovery stock_recovery.img
fastboot erase cache
fastboot reboot-bootloader
now enter stock recovery (power + volume up after you choose it in the bootloader)
when you see the menu choose factory reset
now start over with the custom recovery
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery 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 this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=One_5.11.401.10_odexed.zip
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'm using the telus stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2545227 and unfortunately, I get an error every time I try to wipe the cache. I get:
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.015s
I also get errors when I flash the stock recovery, I can't access anything it seems. My cord is fine, it's worked for me forever.
There must be a way to fix this!

HTC1V said:
I'm using the telus stock recovery from here: http://forum.xda-developers.com/showthread.php?t=2545227 and unfortunately, I get an error every time I try to wipe the cache. I get:
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.015s
I also get errors when I flash the stock recovery, I can't access anything it seems. My cord is fine, it's worked for me forever.
There must be a way to fix this!
Click to expand...
Click to collapse
sounds like your bootloader is locked

clsA said:
sounds like your bootloader is locked
Click to expand...
Click to collapse
:silly: No my bootloader is not locked. It says *** UNLOCKED *** right on the screen. Just because I'm a junior member doesn't mean I'm a noob. I have tried many commands, including "fastboot oem lock" but nothing works. Read my first post again. Let me clarify for everyone! My bootloader is not fully fuctional. I am able to check barcode, and shutdown. Any fastboot commands don't seem to really work (with exception of "fastboot devices," and "fastboot oem unlock_token token.bin"). I've been trying to relock my device, so I can run the RUU.exe, but I this gives me an error. I tried unlocking my device for a second time, and it says unlock successful, but I don't get the warranty, and prompt on screen. I've only had this phone for about 4 months, and I'd like to get a little more life out of it before turning to ebay to find another.

HTC1V said:
:silly: No my bootloader is not locked. It says *** UNLOCKED *** right on the screen. Just because I'm a junior member doesn't mean I'm a noob. I have tried many commands, including "fastboot oem lock" but nothing works. Read my first post again. Let me clarify for everyone! My bootloader is not fully fuctional. I am able to check barcode, and shutdown. Any fastboot commands don't seem to really work (with exception of "fastboot devices," and "fastboot oem unlock_token token.bin"). I've been trying to relock my device, so I can run the RUU.exe, but I this gives me an error. I tried unlocking my device for a second time, and it says unlock successful, but I don't get the warranty, and prompt on screen. I've only had this phone for about 4 months, and I'd like to get a little more life out of it before turning to ebay to find another.
Click to expand...
Click to collapse
I wasn't implying your were dumb ..i was pointing out that your phone acts the same as one with a locked bootloader.
the bootloader partition seems corrupt, fixing it is out of my league. Maybe @nkk71 or @alray has some advice

clsA said:
I wasn't implying your were dumb ..i was pointing out that your phone acts the same as one with a locked bootloader.
the bootloader partition seems corrupt, fixing it is out of my league. Maybe @nkk71 or @alray has some advice
Click to expand...
Click to collapse
Sorry. Thank you very much for the help dude. I'll see what I can do about getting it fixed, I hope there's nothing wrong on the hardware side.

HTC1V said:
Sorry. Thank you very much for the help dude. I'll see what I can do about getting it fixed, I hope there's nothing wrong on the hardware side.
Click to expand...
Click to collapse
like cIsA said, it looks like your eMMC is corrupted, at least the partition where your bootloader is. Ive never seen that kind of error before (SD_HW_ERR] read data fail in CMD18) so I don't have any idea how to help you. Probably re-flashing the firmware or a complete ruu will fix it but its not possible with a non-relockable bootloader + S-ON.
sorry

alray said:
like cIsA said, it looks like your eMMC is corrupted, at least the partition where your bootloader is. Ive never seen that kind of error before (SD_HW_ERR] read data fail in CMD18) so I don't have any idea how to help you. Probably re-flashing the firmware or a complete ruu will fix it but its not possible with a non-relockable bootloader + S-ON.
sorry
Click to expand...
Click to collapse
So it's time for a new phone?

HTC1V said:
So it's time for a new phone?
Click to expand...
Click to collapse
You should wait to see what nkk71 think about your situation.
Code:
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [[COLOR="Red"]SD_HW_ERR[/COLOR]] [COLOR="red"]read data fail in CMD18[/COLOR]
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
only speculating here but I think that CMD is a master/slave protocol used to send commands to the eMMC chip (I might be wrong, I'm not an expert in this matter) So this could mean you have a defective or corrupted eMMC. that would explain why you got these error codes and that you are not able to do anything useful from the bootloader.
Maybe a jtag/riffbox flash could fix this....

HTC1V said:
So it's time for a new phone?
Click to expand...
Click to collapse
Sorry for the late reply, but yep, i think it's time for a new phone.
from what i've seen (and/or):
* "image update error"
* unable to relock bootloader
* "fastboot oem rebootRUU" doesn't actually go to RUU mode (gives some kind of CMDxx / SD error)
== fried phone
sorry to be the bearer of bad news

nkk71 said:
Sorry for the late reply, but yep, i think it's time for a new phone.
from what i've seen (and/or):
* "image update error"
* unable to relock bootloader
* "fastboot oem rebootRUU" doesn't actually go to RUU mode (gives some kind of CMDxx / SD error)
== fried phone
sorry to be the bearer of bad news
Click to expand...
Click to collapse
Thank you nkk71
There's no way I can repair it? Jtag is jot an option?

Stuck in fastboot - No running ROM, recovery , ADB

Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Some more info:
- ADB does not work currently. I tried Win and OSX , so I believe its the phone rejecting it.
- With stock recovery, reading in the 0P8BIMG.zip RUU file containing a 2.19.401.2 or 2.18.401.3 system fails.
- Flashing recovery TWRP 2.8.5.0 / 2.8.1.0 works, but the phone will not start it.
Code:
C:\Users\USER>fastboot flash recovery "Z:\Installs\HTC Mini 2\recovery-twrp-2.8.5.0.img"
sending 'recovery' (11796 KB)...
OKAY [ 1.393s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 1.790s
- My bootloader is ***Unlocked*** according to the fastboot screen. However, I cannot lock it :
Code:
C:\Users\USER>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 8
(bootloader) [INFO] Reset reason in IMEM is 0x77665501
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.056s
- Output of getvar all :
Code:
C:\Users\USER>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if I missed to provide important information.
Is there any way for me to start over on a lower level ? Or is a mobile shop / HTC my only solution left?
Thanks a lot for any feedback!
Greetings,
faiv

faiv said:
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Click to expand...
Click to collapse
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.

kativiti said:
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.

faiv said:
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
Click to expand...
Click to collapse
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?

kativiti said:
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
Click to expand...
Click to collapse
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?

faiv said:
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
Click to expand...
Click to collapse
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.

kativiti said:
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
Click to expand...
Click to collapse
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !

blu3sm4n said:
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
Click to expand...
Click to collapse
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.

kativiti said:
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
Click to expand...
Click to collapse
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks

blu3sm4n said:
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
Click to expand...
Click to collapse
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.

kativiti said:
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
Click to expand...
Click to collapse
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)

blu3sm4n said:
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
Click to expand...
Click to collapse
thx for the picture.
you hboot shows that nothing has been done to the phone. so it was NEVER unlocked as stated in original post.
At this point im gonna suggest get your self an original usb cable because the one you using its no good. its giving you wrong info and it seems some get to the phone but corrupted and thats why unlock fails.
im trying to create a new updated RUU but might take some time.
please get OTA cable and try to unlock

You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

blu3sm4n said:
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know

Ok I'll try and let you know
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

kativiti said:
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Click to expand...
Click to collapse
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).

blu3sm4n said:
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
Click to expand...
Click to collapse
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.

kativiti said:
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
Click to expand...
Click to collapse
in hboot when I try to enter recovery, red warning comes and pressing power+vol up, it says "device cw install:cant mount/data" and then black screen.
I tried second step and added your file into sdcard and update. it says press power button. After that white htc screen is coming. It is waiting since 15 minutes but still nothing and still white screen [emoji21]
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

Sorry but it seems I'm unable to help you.
The picture shows green letters behind the red ones. It means the flashing fail, maybe it rejected the recovery or because its locked.
Either way your problem is, your system and recovery are corrupted.
My advice is contact HTC and send for repair. They usually don't charge you.

Ok dude thanks a lot. I'll contact HTC, i hope they can help ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

Broke the Bootloader???

Long time lurker first time poster, but I need help!!!
Getting tired of waiting for my OTA 7.11 and after a long night at work decided rather than just manually flashing the file that I would use the NRT. I must've encountered an error as it left me in Fastboot so I try to manually flash everything with it being stuck on the "Google" pre-boot screen. I try again with the version that I was on prior to update (NBD91X) and still the same results. Looking at the log from my Command Prompt I notice upon flashing the bootloader I have this error:
sending 'bootloader' (4071 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
(bootloader) Motoboot: invalid GPT
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.408s
I am only able to boot into Fastboot and unable to boot into Recovery. What are my options to getting my N6 back?
Thank you all for the help.

Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!

5.1 said:
Hi. Download last adb + fastboot executables here:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract the files somewhere.
Download Google factory image and extract it in the same folder you have the fastboot executable.
Boot in bootloader "power + volume down" and follow this guide:
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I always choose the second option (manually flashing all files).
Good luck..!
Click to expand...
Click to collapse
Thanks for your reply. Even after getting a fresh download of adb/fastboot files I'm still encountering this error when trying to flash the bootloader;
c:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
c:\Users\matt\Downloads\platform-tools>fastboot flash bootloader C:\Users\matt\D
ownloads\platform-tools\shamu-n6f26r\bootloader-shamu-moto-apq8084-72.01.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.433s
Any other suggestions?

bootloader is locked correct?

SynisterWolf said:
bootloader is locked correct?
Click to expand...
Click to collapse
The bootloader has been unlocked from the day I took it out of the box. I still have the little "unlocked" icon at the bottom of the "Google pre-boot" screen that it stays stuck at when I try to boot the phone.

Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry

5.1 said:
Can you issue this command while in bootloader:
fastboot oem device-info
"Remote failure" sounds like as the bootloader is locked...
Also your problem sounds similar to this one:
https://forum.xda-developers.com/nexus-6/help/bricked-t3523844
I really don't know what you can do now sorry
Click to expand...
Click to collapse
I just issued the command and got this back:
C:\Users\matt\Downloads\platform-tools>fastboot devices
ZX1G3249HB fastboot
C:\Users\matt\Downloads\platform-tools>fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) 'device-info' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
I hope I'm not screwed like the thread you suggested. At this point if I could just get a fresh install I'd be happy with that. Otherwise I guess I could start looking for an N6 replacement...I've put my sim card in my old MotoX 2013 and boy is this phone smaller than I remember.
AGGHHHHH!!! Thanks for your help and please let me know if there is anything else you could suggest for me to try.

Try: fastboot getvar all
Paste the result. Just hide you imei...

5.1 said:
Try: fastboot getvar all
Click to expand...
Click to collapse

I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????

coremania said:
I'm not sure, but wasn't it possible to unbrick the n6 by flashing the 7.0 developer preview image????
Click to expand...
Click to collapse
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.

the200sx said:
That's interesting. I'd be game for whatever weird ass technique there is to get it up and running.
Click to expand...
Click to collapse
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335

coremania said:
But I can't find a download of any early preview, maybe a member here has made backup. If you get a copy, try to flash it step by step without inserted simcard
Edit: may najoor has the original file for you
https://forum.xda-developers.com/nexus-6/general/android-n-preview-2-npc91k-flashable-t3358335
Click to expand...
Click to collapse
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks

Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
I'll give it a shot

the200sx said:
I just read through the entire thread, while it sounds like method 2 would most likely be the option considering how I can't get into recovery, I wasn't able to find where anyone talked about it unbricking the phone. At this point I'm ready to try just about anything, but I had hoped there would be a method to keep data. It may have to wait until tomorrow so I can dedicate enough time to it. In the meantime, if anyone can point me into the direction of someone being stuck similarly to me and what they did to get out of it, I would be extremely grateful.
Thanks
Click to expand...
Click to collapse
Ok, I didn't remember this right, the developer preview ota sideloading with adb was for fixing the Google ota update which bricked some devices as the n previews were released.
But you have nothing to loose, so you may try to do this. Here's a working download in the link, if you don't sideloading the userdata your data may stay intact. https://www.reddit.com/r/nexus6/comments/49txh3/bricked_nexus_6_after_android_n_ota_update_stock/

5.1 said:
Hmm... Could you just try to flash twrp?
https://dl.twrp.me/shamu/twrp-3.0.3-0-shamu.img
Place the file in fastboot folder open a cmd, cd in fastboot folder and flash it:
fastboot flash recovery twrp-3.0.3-0-shamu.img
There's 0.01% it works but doesn't anything to try at this point...
Click to expand...
Click to collapse
It looks like it pushed the TWRP recovery but I still can't seem to get it to boot it into recovery. Only the main fastboot screen pops up trying to Power + Vol and when I VOL select it recovery, it will just reboot back to the main fastboot screen.

Damn... Try:
fastboot erase cache
And try to boot in twrp again?

5.1 said:
Damn... Try:
fastboot erase cache
And try to boot in twrp again?
Click to expand...
Click to collapse
That didn't work either. However it made it take a split-second longer to restart, which gave me a moment of hope. Hope Crushed!!!

Last question... When you power your phone, does it stay on Google logo, or boot animation forever? Or directly bootloader?
If one of the first two, is the phone detected on your computer device manager? If yes, how?