Develop Bugs

[Q] HOX stuck in bootloader/NO Rom/NO recovery

Im looking for a RUU to make my Hox stock again im so sick of these custom roms.
Stuck at bootloader and can't flash anything because of these errors:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7156 KB)...
OKAY [ 1.063s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: err = 0x30000)
finished. total time: 1.328s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (remote: err = 0x19000008)
finished. total time: 0.172s
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
Can you tell me please which stock RUU I can flash on my device and give a download link, i tried some but they were alway not for my version, downloads were offline etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its the international Hox version.
Update
After 5 hours of browsing the internet and trying on my own I made it to downgrade my phone to this
Just flashed Philz recovery 5.15.9 and trying to find a RUU should be much easier too.
I got my Hox unstuck from APX mode by using this tool
PHP:
https://drive.google.com/file/d/0B2bytCPhOCX4ZzI1bm1hdHB2d00/edit
And TripNdroiD-hox-apx-driver
PHP:
https://drive.google.com/file/d/0B68TO7ojvzL_R2l2Xzlpd25RTjQ/edit
Hope my device won't crash into APX mode again.
Please feel free to ask me anything!
=====

Razorback55 said:
Im looking for a RUU to make my Hox stock again im so sick of these custom roms.
Stuck at bootloader and can't flash anything because of these errors:
Can you tell me please which stock RUU I can flash on my device and give a download link, i tried some but they were alway not for my version, downloads were offline etc.
Its the international Hox version.
Update
After 5 hours of browsing the internet and trying on my own I made it to downgrade my phone to this
Just flashed Philz recovery 5.15.9 and trying to find a RUU should be much easier too.
I got my Hox unstuck from APX mode by using this tool
PHP:
https://doc-0s-64-docs.googleusercontent.com/docs/securesc/a013hkdkg0vpokugg4pvi4933uueb4o0/pnhvo7ph3cln7ius0it5r89qvr66smb9/1421877600000/15424132795040343173/12488348193355370217/0B2bytCPhOCX4ZzI1bm1hdHB2d00?e=download&nonce=c7qf18v2jovjc&user=12488348193355370217&hash=kg3dijrugamdaepap4a9o1mnu7olibda
And TripNdroiD-hox-apx-driver
Hope my device won't crash into APX mode again.
Please feel free to ask me anything!
=====
Click to expand...
Click to collapse
Give the result from command fastboot getvar version-main. Please give the correct lilnk for the tool for repair HOX from APX

Thant said:
Give the result from command fastboot getvar version-main. Please give the correct lilnk for the tool for repair HOX from APX
Click to expand...
Click to collapse
Updated download link!
Didnt have flashed anything new data right after recovering device from APX mode
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.28.2000
(bootloader) version-baseband: 1.1204.58.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.15.999.1
(bootloader) serialno: 123456789012
(bootloader) imei: 355195000000010
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3749mV
(bootloader) devpower: 29
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.472s
Click to expand...
Click to collapse
Updating RUU atm and going to post results
Installed RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio_2.1204.127.19_release_271851_signed now and cant get past HTC ONE screen, it doesn't boot. Bootloader got updated but rom wont load that sucks
(bootloader) version: 0.5a
(bootloader) version-bootloader: 0.95.0000
(bootloader) version-baseband: 2.1204.127.19
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) serialno: 123456789012
(bootloader) imei: 355195000000010
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: None
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) devpower: 42
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.853s
Click to expand...
Click to collapse
Seems like it bricked on different levels

Razorback55 said:
Updated download link!
Didnt have flashed anything new data right after recovering device from APX mode
Updating RUU atm and going to post results
Installed RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.12_Radio_2.1204.127.19_release_271851_signed now and cant get past HTC ONE screen, it doesn't boot. Bootloader got updated but rom wont load that sucks
Seems like it bricked on different levels
Click to expand...
Click to collapse
Give the result from this command fastboot oem readcid or fastboot getvar cid because I see you are with CID 11111111 before run the RUU after that you are with NONE something wrong with this.
Try with newer RUU next one after1.29.401.12 this ONE
And again I cant see the tool in your link maybe try to upload some other place like google drive?

Thant said:
Give the result from this command fastboot oem readcid or fastboot getvar cid because I see you are with CID 11111111 before run the RUU after that you are with NONE something wrong with this.
Try with newer RUU next one after1.29.401.12 this ONE
And again I cant see the tool in your link maybe try to upload some other place like google drive?
Click to expand...
Click to collapse
The first link not working? Its google docs i got the links from another thread here on XDA ill check them again.
I tried to flash another RUU and I think its finally bricked now. It wont load past a black screen with a silver HTC logo on it like the one when you install a RUU.
But it still responds to fastboot commands

Razorback55 said:
The first link not working? Its google docs i got the links from another thread here on XDA ill check them again.
I tried to flash another RUU and I think its finally bricked now. It wont load past a black screen with a silver HTC logo on it like the one when you install a RUU.
But it still responds to fastboot commands
Click to expand...
Click to collapse
try flash latest rru for one x 3.14.401.31 or manually update your hboot to latest firmware then unlock bootloader then flash recovery Philz 5.15.9 then copy your custom rom to sd card flash it go in fastboot and flash boot.img and report
yes whan I copy the link I can't see anything give the link to the xda thread from where you take the link

Thant said:
try flash latest rru for one x 3.14.401.31 or manually update your hboot to latest firmware then unlock bootloader then flash recovery Philz 5.15.9 then copy your custom rom to sd card flash it go in fastboot and flash boot.img and report
yes whan I copy the link I can't see anything give the link to the xda thread from where you take the link
Click to expand...
Click to collapse
Its in APX mode again but this time I want to replace the files in APX flash tool with some newer RUU files like system.img and boot.img and all the stuff. The first time I used Nvflash tool i got the old ass Hboot and Radio flashed
Have you tried another browser maybe ? I can see the files well here ill put them withouth
PHP:
code
Tool: https://drive.google.com/file/d/0B2bytCPhOCX4ZzI1bm1hdHB2d00/edit
Driver: https://drive.google.com/file/d/0B68TO7ojvzL_R2l2Xzlpd25RTjQ/edit
UPDATE
Soo now im at the old hboot again same as in the second picture of my first post. I made it somehow to flash some new RUU files with Nvflash BUT i dont really get it which files i have to include into Nvflash folder to make a working clean install with good hboot and working ROM, seems like I make big mistakes every time. But i got it somehow booting into bootloader again that is nice.
Im stuck at black screen with silver HTC logo on it and these are the numbers that fastboot gives me
[QUOTE]C:\android-sdk-windows\platform-tools>fastboot getvar version-main
version-main: 1.15.999.1
finished. total time: 0.045s
C:\android-sdk-windows\platform-tools>fastboot oem getcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.020s
C:\android-sdk-windows\platform-tools>fastboot oem readcid
...
(bootloader) DEBUG: cid: 11111111
OKAY [ 0.088s]
finished. total time: 0.089s[/QUOTE]
Do you know how to flash a new RUU now / or how to update my hboot to a newer version fist? Thx

Razorback55 said:
Its in APX mode again but this time I want to replace the files in APX flash tool with some newer RUU files like system.img and boot.img and all the stuff. The first time I used Nvflash tool i got the old ass Hboot and Radio flashed
Have you tried another browser maybe ? I can see the files well here ill put them withouth
PHP:
code
Tool: https://drive.google.com/file/d/0B2bytCPhOCX4ZzI1bm1hdHB2d00/edit
Driver: https://drive.google.com/file/d/0B68TO7ojvzL_R2l2Xzlpd25RTjQ/edit
UPDATE
Soo now im at the old hboot again same as in the second picture of my first post. I made it somehow to flash some new RUU files with Nvflash BUT i dont really get it which files i have to include into Nvflash folder to make a working clean install with good hboot and working ROM, seems like I make big mistakes every time. But i got it somehow booting into bootloader again that is nice.
Im stuck at black screen with silver HTC logo on it and these are the numbers that fastboot gives me
Do you know how to flash a new RUU now / or how to update my hboot to a newer version fist? Thx[/QUOTE]
Download 3.14.401.31 and run it
Click to expand...
Click to collapse

Thant said:
Download 3.14.401.31 and run it
Click to expand...
Click to collapse
Tried, but cant flash anything because battery too low. I found a batch script to charge by booting into bootloader and reboot but it wont pass 3350Mv and thats not enough to flash anything yea

Razorback55 said:
Tried, but cant flash anything because battery too low. I found a batch script to charge by booting into bootloader and reboot but it wont pass 3350Mv and thats not enough to flash anything yea
Click to expand...
Click to collapse
change cable or USB port and the process is slow for charging try on different computer. The bach script work 100%

Thant said:
change cable or USB port and the process is slow for charging try on different computer. The bach script work 100%
Click to expand...
Click to collapse
Ok thanks but this time it looks like im stuck at APX mode for ever getting this error over and over:
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x81
chip uid: 0x015d15b4ff080610
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: flash_enc.bct
- 6128/6128 bytes sent
flash_enc.bct sent successfully
odm data: 0x40080105
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: hboot_enc.img
- 2097168/2097168 bytes sent
hboot_enc.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: DIA
creating partition: BIF
creating partition: GP1
creating partition: WLN
creating partition: WDM
creating partition: RCA
creating partition: LNX
creating partition: SOS
creating partition: PG1
creating partition: PG2
creating partition: PG3
creating partition: SIF
creating partition: SP1
creating partition: RV1
creating partition: APP
creating partition: CAC
creating partition: ISD
creating partition: UDA
creating partition: DUM
creating partition: MSC
creating partition: RFS
creating partition: DLG
creating partition: PDT
creating partition: GPT
failed executing command 13 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x8 (0x9) flags: 0
Z:\Users\Razor\Desktop\RD_release(with_sbk)without sis>pause
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse

Thant said:
change cable or USB port and the process is slow for charging try on different computer. The bach script work 100%
Click to expand...
Click to collapse
It wont charge ffs im so done with this HOX. Maybe a new battery will work again? It either wont charge like you can see below OR it goes completely off and wont turn on unless I push the power ON button for 30seconds.
Why Htc made it impossible to charge the device in bootloader.
C:\android-sdk-windows\platform-tools>" @echo off
Der Befehl "" @echo off" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
battery-voltage: 3428mV
finished. total time: 0.162s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.293s]
finished. total time: 0.294s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3439mV
finished. total time: 0.042s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.279s]
finished. total time: 0.280s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3434mV
finished. total time: 0.043s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.274s]
finished. total time: 0.275s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3437mV
finished. total time: 0.049s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.278s]
finished. total time: 0.279s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3442mV
finished. total time: 0.044s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.276s]
finished. total time: 0.277s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3440mV
finished. total time: 0.047s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.276s]
finished. total time: 0.278s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3439mV
finished. total time: 0.050s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.275s]
finished. total time: 0.276s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3443mV
finished. total time: 0.045s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.276s]
finished. total time: 0.278s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3440mV
finished. total time: 0.049s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.277s]
finished. total time: 0.279s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3432mV
finished. total time: 0.050s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.273s]
finished. total time: 0.274s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3434mV
finished. total time: 0.046s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.277s]
finished. total time: 0.278s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3433mV
finished. total time: 0.052s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.275s]
finished. total time: 0.277s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3429mV
finished. total time: 0.047s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.277s]
finished. total time: 0.278s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3429mV
finished. total time: 0.042s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.274s]
finished. total time: 0.275s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
battery-voltage: 3435mV
finished. total time: 0.045s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.271s]
finished. total time: 0.272s
C:\android-sdk-windows\platform-tools>ping /n 6 localhost 1>nul
C:\android-sdk-windows\platform-tools>goto start
C:\android-sdk-windows\platform-tools>fastboot getvar battery-voltage
< waiting for device >
Click to expand...
Click to collapse

Razorback55 said:
It wont charge ffs im so done with this HOX. Maybe a new battery will work again? It either wont charge like you can see below OR it goes completely off and wont turn on unless I push the power ON button for 30seconds.
Why Htc made it impossible to charge the device in bootloader.
Click to expand...
Click to collapse
Are you change the port use USB2.0, change the cable, change the computer don't use laptop! the process is slow

Thant said:
Are you change the port use USB2.0, change the cable, change the computer don't use laptop! the process is slow
Click to expand...
Click to collapse
Thanks for your help ! You gave me some good advise until today
I got it into Bootloader right now with enough battery to flash and flashed philz recovery first to let that damn thing charge full
But if Im ever going to repair it and start some Rom , what about that problem with no IMEI its still generic like in the first page of this thread, you maybe have a working method to fix that?

Razorback55 said:
Thanks for your help ! You gave me some good advise until today
I got it into Bootloader right now with enough battery to flash and flashed philz recovery first to let that damn thing charge full
But if Im ever going to repair it and start some Rom , what about that problem with no IMEI its still generic like in the first page of this thread, you maybe have a working method to fix that?
Click to expand...
Click to collapse
Try and see if the phone work with this IMEI if the phone work leave it like this

Thant said:
Try and see if the phone work with this IMEI if the phone work leave it like this
Click to expand...
Click to collapse
WOW this night I made it to boot up my phone and it went to the RUU I flashed. Everything went fine, i chose a WIFI network, chose my language and set the time and date.
Then it was on homescreen and I thought finally I made it but after like 2min I was browsing the settings it went off.
It went just off suddenly like when you unplug the battery. I put it on my computer with usb and the device manager said: APX mode again.
That just sucked so much. But now I have tried everything and know its completely bricked.
I dont remember what ROM i have installed but I think it was after I have flashed Maximus HD Rom. I was playing around with the build-in Xposed settings that the ROM had and then it crashed and that was the reason for my device to go into APX.

I accidentally flashed recovery to boot portion:crying:. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
now i cant boot into recovery, when i try to it just shows twrp logo nothing else!
please help....
Unlocked bootloader
HBOOT: 1.12.0000
RADIO : 2.1204.135.20

Can't Flash TWRP "Signature Verify Fail"

This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s

Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.

Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>

Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.

Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>

Try the HTC_fastboot adb package. It's posted several times here on xda.

Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)

Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.

Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html

joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions

rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?

rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.

Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks

foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).

Please help my htc 10 is dead

I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .

What's your CID and latest ROM version? And what did you try to flash?

Dont know anything here... I dont know what was the ROM version at the time of root... now no information available... what can I do ...

When I try to flash anything via fastboot it says partion not exist
RUU also not working says battery is less than 30% but actually battery is full...

Does charging led turns green..
@Sneakyghost could help

cutecool said:
Does charging led turns green..
@Sneakyghost could help
Click to expand...
Click to collapse
no it doesnt... the battery icon comes up and then boot loop starts again...

Since you're in Qatar, you're probably on the 401 software. Did you get a software update in the last 2-3 weeks?
If not, download this: https://www.androidfilehost.com/?fid=24686681827312455
Relock your bootloader (fastboot oem lock), and flash this RUU (fastboot flash zip "name of zip").
If you got the recent update, then you're likely on 1.95, and you'll have to wait until there's an RUU, or take it to a service center.
This is as much help as I can give. Good luck.

I wouldn't lock the bootloader until you know your device fully boots.

Stephen said:
I wouldn't lock the bootloader until you know your device fully boots.
Click to expand...
Click to collapse
The 401 RUU zip won't flash on unlocked. This has been documented and I have gone through it myself. Do you have any alternate suggestions?
Why wouldn't you lock without a working system? My understanding is that unlocking via HTCdev would still be possible.

I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>

abidpioneer said:
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
Click to expand...
Click to collapse
You need to be in download mode then use the getvar all command. All fastboot commands are done in downlaod mode. How are you trying to flash RUU?

I am unable to use download mode..it says download mode failed in red

abidpioneer said:
I am unable to use download mode..it says download mode failed in red
Click to expand...
Click to collapse
You'll need a service center.

Yes. Service center. I don't think it's a brick since there's still a boot process but at this time I also wouldn't know how to force it to flash stuff, since it seems at least one vital partition is broken. So, call it a semi-brick with currently no way out...
Sorry that I can't offer any help here...

abidpioneer said:
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
Click to expand...
Click to collapse
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk

I will check dear..thanks

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Click to expand...
Click to collapse
What is hosd.. ? Never heard about it...

I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...

abidpioneer said:
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
Click to expand...
Click to collapse
What happened? Did it flash successfully? Any errors?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Interesting facts there, mate. Thought you retired. Obviously I'm much more retired than you, considering I never knew HOSD is directly flashable like aboot...
Good to see you around!
(Besides, is it a true story that you retired? People were telling me that...)

Pixel XL bricked, bootloader locked and recovery doesn't work.

Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Useful logs:
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:352693081633543
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012901-1702171013
(bootloader) version-bootloader:8996-012001-1704121145
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT7370201155
(bootloader) kernel:lk
(bootloader) product:marlin
all:
finished. total time: 2.243s
./flash-all.sh (8.0.0-stock-opr3.170623.007):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32268 KB)...
OKAY [ 1.076s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.175s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'radio_a' (57272 KB)...
OKAY [ 1.952s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.050s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.150s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device
failed to extract 'vendor.img': I/O Error
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
error: file_write: write: No space left on device
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is '8996-012001-1704121145'.
Update requires '8996-012001-1706221457'.
finished. total time: 0.300s
./flash-all.sh (7.1.2-stock-njh47d):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32380 KB)...
OKAY [ 1.088s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.187s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.247s
target reported max download size of 536870912 bytes
sending 'radio_a' (57240 KB)...
OKAY [ 1.924s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (26001 KB)...
OKAY [ 0.951s]
writing 'boot_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.401s

zades9 said:
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Click to expand...
Click to collapse
I assume that you have tried fastboot boot with the correct twrp image?

I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".

mikefnz said:
I assume that you have tried fastboot boot with the correct twrp image?
Click to expand...
Click to collapse
I get this log:
Code:
[cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.001s

Pain-N-Panic said:
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
Click to expand...
Click to collapse
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.

zades9 said:
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20

mikefnz said:
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
Click to expand...
Click to collapse
I can't enable Bootloader Unlocking from the developer settings because the device is bricked.

@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.

Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?

comat0se said:
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
Click to expand...
Click to collapse
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

tdct12 said:
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Click to expand...
Click to collapse
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!

Bryanx86 said:
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Click to expand...
Click to collapse
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/

zades9 said:
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.

zades9 said:
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
Click to expand...
Click to collapse
I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope

Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as
~$ fastboot --version
fastboot version -4022467
I would also give the November image a try.

Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!

Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b

dictionary said:
Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
Click to expand...
Click to collapse
Code:
C:\Users\cristian>fastboot --set-active=_b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.076s
C:\Users\cristian>fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.292s
I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer

Restoring to stock *LOCKED*

ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>

tonnytech said:
ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>
Click to expand...
Click to collapse
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.

errikosd said:
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.
Click to expand...
Click to collapse
thanks for the reply i sorted it as you suggested already appreciate reply thou