Develop Bugs

Quastion regarding [ S-OFF Firmware flashing (Fastboot) (Current: 3.35.617.12) ]

hi every one ,,
I'm new in this forums >> this is why I'm posting my quastion here
anyway :
my HTC M9 on viper rom 3.5.0 ,, since I want to upgrade to viper 4.2.1 >> I tried many time to flash the firmware ( 3.35.401.12 ) & ( 3.35.617.12 )
I tried many times but unfortunately , FAILED
first I tried with the firmware ( 3.35.401.12 ) & it was telling me like this :
target reported max download size of 800000000 bytes
sending 'zip' (64357 KB)...
OKAY [ 4.110s]
writing 'zip'...
(bootloader) HOSD CL#576582
FAILED (remote: 9: SD_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 5.131s
I change my phone mode into RUU mode , then I tried again and this what I was told :
target reported max download size of 800000000 bytes
sending 'zip' (64357 KB)...
OKAY [ 3.788s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) ERR [SD_UPDATE_ERR] Parse zipped android_info fail!
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 7.735s
I changer My MID & CID in ( android info.txt ) >> but without any change
then I tried with the firmware ( 3.35.617.12 ) & this is what shows up :
target reported max download size of 800000000 bytes
sending 'zip' (64357 KB)...
OKAY [ 4.392s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 7.478s
pleeeeeeeeeeeeeease >> HELP !!!
thanks

manea_q1 said:
[...]
(bootloader) ERR ZIP signature checking failed...
[...]
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
[...]
Click to expand...
Click to collapse
Is your phone really S-OFF? (If I look at those errors I guess not.)

Sorry brother >> what do you mean by S-off ?! ?

manea_q1 said:
Sorry brother >> what do you mean by S-off ?!
Click to expand...
Click to collapse
That was the answer I expected to get...
By unlocking the bootloader you only gain control over 3 partitions: Recovery, System and Bootloader. If you want to flash firmware packs which are not officially signed by HTC (like the 3.35.401.12 one) you need to unlock the rest of the phone beforehand. Otherwise the phone's security mechanisms will prevent you from flashing those files. (In other words the Security is ON.) That's why you need to set them OFF (S-OFF). Either you get the Sunshine app or you find someone with a java card.
Oh and changing the firmware to other versions (as you tried from whichever version you got to the developer edition) isn't possible with S-ON, either.

Thank you so much bro ,,,
I will try ?

yes bro , done
every things work now :good:
thanks alot

no os no recovery can fastboot

cant flash a custom recovery or stock recovery keep getting this message:
OKAY [ 1.911s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.943s
i have found two that install but if i try booting into them i either get kicked right back to bootloader or it hangs then tries to boot into OS (which doesnt exist)
any help would be appreciated!
p.s ive read the majority of m8s threads
also get this error when i try to update ruu
C:\Users\Daniel\Desktop\platform-tools-latest-windows\platform-tools>fastboot flash flashall 0PKVIMG.zip
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2259689442 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2242916322 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2226143202 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2209370082 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2192596962 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2175823842 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2158964706 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2142191586 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2267365346 is not a multiple of the block size 4096
sending sparse 'flashall' 1/9 (16380 KB)...
error: write_sparse_skip_chunk: don't care size 2259689442 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2259689442 is not a multiple of the block size 4096
OKAY [ 1.625s]
writing 'flashall' 1/9...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.708s

Try using htc_fastboot.exe

Thijs_Rallye said:
Try using htc_fastboot.exe
Click to expand...
Click to collapse
I will try and get back with results!
Thanks!!
OKAY!!! back to stock recovery but im not sure how to get stock OS back? should i send to sd card then try in bootloader or RUU? which file do i need? firmware, kernal or RUU?
Thanks again!

Sorry, can't help you any further since I don't have any experience with this. You can RUU the phone, that is about as far as my knowledge reaches.
Edit: try reading the whole root topic by El-Conkistador. I know it's a lot, but it is a good start finding all the common "pitfalls". (like not using htc_fastboot.exe )

Thijs_Rallye said:
Sorry, can't help you any further since I don't have any experience with this. You can RUU the phone, that is about as far as my knowledge reaches.
Edit: try reading the whole root topic by El-Conkistador. I know it's a lot, but it is a good start finding all the common "pitfalls". (like not using htc_fastboot.exe )
Click to expand...
Click to collapse
im making progress now but really would be nowhere with out that bit of information!
https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238
thanks again ive been scratching my head for weeks just needed some clarity!
P.S if you think there is any point of posting my results then i will! :good::good::good:

Small update custom recovery and stock recovery working! able to install custom rom... but exhausted every stock firmware available found one that almost worked but wrong CID!!! tried changing .txt file to include mine but corrupt the archive :/ if any one has a dump of there's would be great! looking for CID ORANG001 [email protected]

Any additional information is always welcome on a forum imho. There are already way to many dead ends at XDA. (I.e. people found a solutions for themselves and never bothered to post it.)
Changing the txt will change the checksum, so that trick won't work. Have you already looked at the RUU's?
https://ruu.lalleman.net/HTC_M8S(QL_UL)/RUU/
Can you post a getvar -all (remove the IMEI and serial)

Thijs_Rallye said:
Any additional information is always welcome on a forum imho. There are already way to many dead ends at XDA. (I.e. people found a solutions for themselves and never bothered to post it.)
Changing the txt will change the checksum, so that trick won't work. Have you already looked at the RUU's?
https://ruu.lalleman.net/HTC_M8S(QL_UL)/RUU/
Can you post a getvar -all (remove the IMEI and serial)
Click to expand...
Click to collapse
I didnt think it would work as it changes the size of the archive drastically.
as you will see from the getvar none of the RUU's match my radio and the one that matches my CID makes progress but eventually fails...
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: ORANG001
(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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 661(ms)
sorry if im being really stupid and missing something obvious and again thanks for caring! :good:

Checksum isn't solely about size .
Maybe this RUU works:
https://ruu.lalleman.net/HTC_M8S(QL...10.1G50408_15.00_016_F_release_431629_signed/
You can try searching here: http://ir-file.com/ , but the service for downloading isn't free. (not ridiculously expensive either considering buying a working phone otherwise )
Use the search terms: M8_QL_UL_L50_
You can only reinstall (RUU) the same version or a newer one. If you upgrade to Marsmallow you will be stuck with Marshmallow since there is no way to downgrade. (because there is no S-off, and also not likely there will come one)
Good luck

Thijs_Rallye said:
Checksum isn't solely about size .
Maybe this RUU works:
https://ruu.lalleman.net/HTC_M8S(QL...10.1G50408_15.00_016_F_release_431629_signed/
You can try searching here: http://ir-file.com/ , but the service for downloading isn't free. (not ridiculously expensive either considering buying a working phone otherwise )
Use the search terms: M8_QL_UL_L50_
You can only reinstall (RUU) the same version or a newer one. If you upgrade to Marsmallow you will be stuck with Marshmallow since there is no way to downgrade. (because there is no S-off, and also not likely there will come one)
Good luck
Click to expand...
Click to collapse
i will download and try and of course post my results, and if not will look at your other link! :good:

Slugnut25 said:
i will download and try and of course post my results, and if not will look at your other link! :good:
Click to expand...
Click to collapse
\[email protected]50408_15.00_016_F_release_431629_signed>htc_fastboot flash zip rom.zip
sending 'zip'... (163869 KB) OKAY
sending time = 8.050 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 20(s)

Slugnut25 said:
\[email protected]50408_15.00_016_F_release_431629_signed>htc_fastboot flash zip rom.zip
sending 'zip'... (163869 KB) OKAY
sending time = 8.050 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
Execution time is 20(s)
Click to expand...
Click to collapse
You can't use HTC_fastboot for flashing a RUU. (as far as I know) There should be an executable included in the zip file. And don't forget to check the MD5 before you start .
Edit: if you extract the ROM.zip from the RUU, you can rename it to 0PKV.zip (verify!) and put in on a SD card. The exact method (google it here in XDA) is described step by step.

I had a no os problem eventually fixed it by side loading the Android Revolution rom to the phone, look on youtube for instructions on how to do this

You can flash same or latest RUU.zip with fastboot with following commands.
htc_fastboot oem lock
htc_fastboot oem rebootRUU
htc fastboot flash zip RUUZIPNAME.zip
Click to expand...
Click to collapse
Note: you cant flash stock rom until you relock your bootloader, and reboot into RUU mode with command will startup with black screen and green logo.
Post the Progress

provide getvar log so I can help you

[HELP] AUS/Optus Model - Deleted OS

This is probably the dumbest thing I have to date :C
At the start of last year I rooted my device and unlocked it, fast forward to the start of this week I tried updating my device but it kept on launching TWRP, so I decided to factory reset it.
However I was a big spud and used advanced wipe - and now the phone will boot straight to the bootloader.
Before I post anything else here is the getvar from download mode.
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 2.9.710.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: OPTUS001
The device is currently in s-on, and I can't remember if it was ever in s-off because it was a long time ago when I rooted it.
I have tried flashing a custom rom with no success, and just recently I have downloaded and tried to flash "0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_AUS_1.32.710.16_Radio_01.01_U11440261_56.02.50306G_2_F_release_427214_signed.zip"
This is the error I receive while trying to flash the device in fastboot.
Code:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.017s]
finished. total time: 0.018s
C:\adb>fastboot flash zip 0PJAIMG.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096
OKAY [ 1.013s]
writing 'zip'...
(bootloader) HOSD CL#573756
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_n
(bootloader) A2AxZ
FAILED (remote: 99: SD_UNKNOWN_FAIL to flash via downloadzip)
finished. total time: 2.048s
I don't have any backups of any sort - basically I just want to be able to get this phone running back on stock and leave it at that.
Does anyone have any ideas of how I can fix this? My phone has been broken for 3 days and I've wasted a lot of time downloading roms that won't flash (takes a while to download on my crappy ADSL connection).
I should also note I do not have an external SD card, hoping to do it without buying one.
Thanks heaps.

Please read the ReadMe thread. Its RUU section explains why you can't flash the RUU that you mentioned in your OP and why flashing M9 RUUs in general fails if you use fastboot.
After you downloaded the correct files you can try to flash a RUU with the modified fastboot instead of using an SD card. Troubleshooting tips can be found in the FAQ of the same thread. Be aware, that using an SD card is the recommended method since many users aren't able to set up a fastboot environment correctly and using an SD card is less time-consuming than trying to find the user error that prevents fastboot from working correctly.

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

TWRP flash failing on Moto-Z Play unlocked

I unlocked the moto-z play. In fastboot it says 'flashing_unlocked'. I tried flashing twrp 3.1.1-addison and I get:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (23452 KB)...
OKAY [ 1.613s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.618s
[email protected]:/mnt/hgfs/vmshare
I then tried:
[email protected]:/mnt/hgfs/vmshare# fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 1.115s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.313s]
finished. total time: 1.429s
[email protected]:/mnt/hgfs/vmshare#
I downloaded the image three times and all three times I got not signed or corrupt.
Any help here is appreciated.
Y-

use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum

TeamMex said:
use moto fastboot https://forum.xda-developers.com/attachment.php?attachmentid=2427667
The Next time post in Q&A not in development forum
Click to expand...
Click to collapse
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#

The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?

YileKu said:
Thanks but it failed for me.
[email protected]:/mnt/hgfs/vmshare# ./linux-fastboot flash recovery recovery-TWRP-3.0.2-20161010-MOTO_Z_PLAY-CN-wzsx150.img
target max-sparse-size: 256MB
sending 'recovery' (16198 KB)...
OKAY [ 1.164s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.310s]
finished. total time: 1.474s
[email protected]:/mnt/hgfs/vmshare#
Click to expand...
Click to collapse
More easy
Do
fastboot boot twrname.img
Copy the recovery and flash from the recovery
Note:
If you flash via fastboot you can get these lines but the flash works
Sent from my Motorola Moto Z Play using XDA Labs

tag68 said:
The message that it is not signed out corrupt may be one you need to get used to. As far as I understood: Only Motorola would be capable of signing. But Motorola does not publish any signed does, they only release OTA. At least until now.
Does it work if you just take the message as success?
Click to expand...
Click to collapse
I am unable to access twrp after rebooting the phone, so I assume it didn't actually flash.