Develop Bugs

Complications during CM install. Can't find HTC__Y13 firmware; CWM recovery bootloops

I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.

Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium

Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)

hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom

Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) ERASE backup cid
OKAY [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?

Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium

All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.

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?).

[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

flashing twrp succsess, can not load twrp from recovery

hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(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: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(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
any help is appreciated, thank you

redstonedudeHD said:
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(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: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(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
any help is appreciated, thank you
Click to expand...
Click to collapse
It isnt working for you because you have to boot directly into recovery, you can't let the device boot to any other mode, if you boot to any mode other than recovery, a device will revert back to stock recovery. You are rebooting to bootloader mode instead of recovery mode, this is causing the device to revert to stock recovery instead of booting into the TWRP that you flashed.
After flashing TWRP, instead of using the fastboot reboot-bootloader command, use the adb reboot command, enter it as soon as you are done flashing the recovery.
Use the adb command below:
adb reboot recovery
Then you should boot into TWRP.
Sent from my SM-S767VL using Tapatalk

hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.

redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Ok, let's take a couple of steps back. Do you know if your bootloader is unlocked? Flashing TWRP won't work if the bootloader is locked.
@xunholyx, could there be something that is HTC specific that they are overlooking?
Sent from my SM-S767VL using Tapatalk

bootloader is unlocked

redstonedudeHD said:
bootloader is unlocked
Click to expand...
Click to collapse
Try flashing the TWRP using the fastboot flash recovery command
Then try using this command:
fastboot boot recovery (name of your recovery file)
Sent from my SM-S767VL using Tapatalk

flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory

@Droidriven any idea what i can do?

double send

redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Do you have USB debugging turned on in developer options? ADB commands won't work if you don't.
---------- Post added at 11:55 AM ---------- Previous post was at 11:50 AM ----------
redstonedudeHD said:
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
It seems to have flashed properly with htc_fastboot.
Try flashing it again, then
htc_fastboot reboot bootloader
then select boot to recovery from the bootloader menu on your phone from there.
It should take you to TWRP

hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.

redstonedudeHD said:
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
Click to expand...
Click to collapse
It should work with regular fastboot reboot bootloader then selecting recovery from there via your phone
EDIT: I have never had to use HTC's fastboot myself. It is necessary for flashing large files from your PC. I always flashed the large files (eg: RUUs) via the SD card method. But that wasn't for recovery.img s, it was for RUUs
EDIT #2: I'm going to request to the moderators to have this thread moved to a forum where you might find other help. You don't have to do anything about it. It will just get moved. The forum I'm moving it to is for the regular M8 and not the M8s, but people there will be able to offer help that you won't get here. I'll continue to monitor this thread there and offer help if I can.

hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!

redstonedudeHD said:
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
Click to expand...
Click to collapse
Sorry I haven't responded sooner.
I would suggest you run an RUU. The problem is, I don't know of any RUUs myself for your current firmware version, and since you are S-On, you can't roll back to an older version.
If you can find an RUU for 2.11.161.1 download it and flash it. The only ones I can find are from a previous Android version. (1.xx.xxx.x)
Also, there is a newer TWRP version than the one you are using. Maybe that might be the issue? I can't be sure about this, since I'm familiar with the HTC M8, but not the HTC M8s.
You can download the updated TWRP version from here.
I believe it was updated to work with 2.xx.xxx.x firmware. But I'm not positive. It can't hurt to try it out.

hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/

redstonedudeHD said:
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
Click to expand...
Click to collapse
There's two there. I don't know what the difference between "partial" and the other one is. I would assume the partial one has the boot.img and maybe the recovery.img removed?
Use the other one. There are two ways to flash it since it is an RUU.zip.
#1: In fastboot: fastbbot flash zip **drag and drop the zip here**
#2: Rename the zip by deleting everything in the name of it except for 0PKVIMG (and .zip of course) and place that onto your extSD card (must be formatted to FAT32)
Put that into your phone then bot to bootloader. It should find the file automatically. If it doesn't, boot to hboot from boot loader.
From there it's super easy. Follow the on screen prompts. Volume up to confirm the flash. Power button to reboot after the flash is done.
Good luck! I hope you get everything up and running again.