Develop Bugs

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

Htc one M9 stuck in bootloader

Hi,
My one year old htc one M9 used to work fine, until a day when it discharged and went off (because of no charge). I recharged turned it on but it ended up stuck on the htc start up logo. I thought it was a hardware issue so I took it to a technician who tried to flush but they couldnt get it working. Instead the phone now starts up to the bootloader with these infos:
*******Software status: Modified******
******* LOCKED*******
******* S-ON*******
*******Security Warning*******
<vol up> .......
<vol down> ...
<power>....
REBOOT
REBOOT TO BOOTLOADER
REBOOT TO DOWNLOAD MODE
REBOOT TO RECOVERY MODE
POWER DOWN
Being completely new to this field, after searching around the web, found I could restore back to stock by installing RUU firmware. Went ahead and installed adb, fastboot and htc sync.
I also downloaded 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip from www dot androidfilehost dot com /?fid=24415232478675953 and renamed it to firmware_M9.zip, but running fastboot oem rebootRUU then fastboot flash zip firmware_M9.zip returns :
>target reported max download size of 800000000 bytes
>Invalid sparse file format at header magi
>error: write_sparse_skip_chunk: don't care size 2435476345 is not a multiple of the block size 4096
>sending sparse 'zip' 1/1 (0 KB)...
>error: write_sparse_skip_chunk: don't care size 2435476345 is not a multiple of the block size 4096
>error: write_sparse_skip_chunk: don't care size 2435476345 is not a multiple of the block size 4096
>OKAY [ 1.005s]
>writing 'zip' 1/1...
>(bootloader) HOSD CL#671758
>(bootloader) ERR lzipv1_init : Cannot read header len bytes
>(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_j
>(bootloader) EHyWh
>OKAY [ 1.039s]
Tried to redownload the file but still, looks like it doesnt work.
PS:
fastboot getvar all returns
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
I have tried to factory reset using button combinations (power, vol up and down) and stuffs to get the phone back on but nothing worked.
Any ideas? A way to reinstall the whole system may be? I would just want my phone on again, I dont care bout the data.
Thanks.

Looks like that file may be corrupt. Check the md5 hash matches what is on the site you got it from.
There is a significant chance that the phone nand is dead.
Beamed in by telepathy.

The file isn't corrupt. That happens if you try to flash a RUU with fastboot instead of htc_fastboot.
However, the infos from the bootloader indicate that the nand of the phone is indeed dead.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
The file isn't corrupt. That happens if you try to flash a RUU with fastboot instead of htc_fastboot.
However, the infos from the bootloader indicate that the nand of the phone is indeed dead.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hi, Thanks for your reply. Is Nand reparable/replaceable? or does it mean the phone can never be useful again?

shivadow said:
Looks like that file may be corrupt. Check the md5 hash matches what is on the site you got it from.
There is a significant chance that the phone nand is dead.
Beamed in by telepathy.
Click to expand...
Click to collapse
Md5 matches the original. Can I replace nand? Or I just have to throw away the phone?

i bought a used htc m9 att version after seeing all these people posts about he nands of the phone dying after some time im quite terrifeid btw which varaint was ur m9

Flippy498 said:
The file isn't corrupt. That happens if you try to flash a RUU with fastboot instead of htc_fastboot.
However, the infos from the bootloader indicate that the nand of the phone is indeed dead.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Htc_fastboot.exe completely slipped my mind, I'm actually ashamed that I didn't spot that!.
mega_man said:
i bought a used htc m9 att version after seeing all these people posts about he nands of the phone dying after some time im quite terrifeid btw which varaint was ur m9
Click to expand...
Click to collapse
Had mine nearly 2 years and sh***ing it incase I wake up one day but my phone doesn't..
keyrocker120 said:
Md5 matches the original. Can I replace nand? Or I just have to throw away the phone?
Click to expand...
Click to collapse
Try using htc_fastboot.exe to flash the phone. If no joy then it'll be buggered.
Beamed in by telepathy.

Bricked M9, Impossible to flash any firmware? Any suggestion?

This is my device situation so far:
Bottloader: LOCKED
Oem Unlocked: NO (Can't flash any recovery)
Security: S-ON
Main version: 3.36.709.9
CID: HTC__621
Recovery: STOCK
Impossible to boot into OS even after wiping data through recovery.
When trying to flash OTA zip corresponding to the same main version or higher I always get Error 22. I've tried SDCard method, adb sideload and flashing zip through fastboot (rebootRUU, flash zip, etc).
Is there any other way to flash an official firmware for this device? It'd be great to have an official RUU for my version or higher. Or maybe some software from HTC to "restore upgrade errors"?
Thanks in advance!

Check the md5 hash of the file you downloaded and cross reference it on Google. You need to make sure the file you have is complete.
Beamed in by telepathy.

Monrad said:
This is my device situation so far:
Bottloader: LOCKED
Oem Unlocked: NO (Can't flash any recovery)
Security: S-ON
Main version: 3.36.709.9
CID: HTC__621
Recovery: STOCK
Impossible to boot into OS even after wiping data through recovery.
When trying to flash OTA zip corresponding to the same main version or higher I always get Error 22. I've tried SDCard method, adb sideload and flashing zip through fastboot (rebootRUU, flash zip, etc).
Is there any other way to flash an official firmware for this device? It'd be great to have an official RUU for my version or higher. Or maybe some software from HTC to "restore upgrade errors"?
Thanks in advance!
Click to expand...
Click to collapse
What firmware are you attempting to flash? Recall that the final number in the RUU (xx.xx.xx.yy) does not have to match your phone's OS version.
The 709 SKU has a compatible RUU available in the readme thread (3.36.709.3). Since the file is hosted on Android File Host, the MD5 is posted there (look under download information). On your computer, you can install a MD5 checker (I use File Hasher) to verify that they match.

computerslayer said:
What firmware are you attempting to flash? Recall that the final number in the RUU (xx.xx.xx.yy) does not have to match your phone's OS version.
The 709 SKU has a compatible RUU available in the readme thread (3.36.709.3). Since the file is hosted on Android File Host, the MD5 is posted there (look under download information). On your computer, you can install a MD5 checker (I use File Hasher) to verify that they match.
Click to expand...
Click to collapse
I've tried that file, hash is ok but file will not get flashed. This is the log:
Code:
fastboot flash zip 0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_TW_1.40.709.4_Radio_01.02_U11440261_60.03.50505G_F_release_431851_signed.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 2322433715 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2322433715 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2322433715 is not a multiple of the block size 4096
OKAY [ 1.031s]
writing 'zip' 1/1...
(bootloader) HOSD CL#676746
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_m
(bootloader) ar4HL
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.083s
I downloaded the file more than 4 times and it's always the same result.
I'm downloading another fastboot version because maybe the one I'm using is not compatible.

Same problem with htc fastboot...
Code:
htc_fastboot.exe flash zip 0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_TW_1.40.709.4_Radio_01.02_U11440261_60.03.50505G_F_release_431851_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (261353 KB)...
OKAY [ 15.207s]
writing 'zip'...
(bootloader) HOSD CL#676746
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(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, 19
(bootloader) [email protected]
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
finished. total time: 23.551s
htc_fastboot finished. total time: 43.310s
EDIT: I've beenf lashing the wrong image, I'll try with the right one, sorry!
EDIT: it worked, problem was fastboot version!!! Use HTC FASTBOOT and everyithing is fine Thanks! You've inspired me into the solution

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

Recovery/System Bootloop - Fastboot Doesn't Flash

I am suffering from a bootloop in my phone, lineage suddenly decided to crash trebuchet, and phone turned off. Bootloader works, download mode works, recovery absolutely DOES NOT, It gives me the black HTC logo and turns off and on when I put the "fastboot oem lock" option, and just redirects back to the bootloop when I don't. I can use fastboot to flash files to it, I flashed TWRP old and new, but nonetheless, it bootloops when picking recovery once more. I have S-ON, with the bootloader unlocked. I'd love to buy the sunny license and turn S-OFF, but have no way of accessing my OS anymore.
Here are my details.
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
Here is my recovery flashing log
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
I've tried flashing a signed stock ROM, but I know I need to re-lock the bootloader, the "fastboot oem lock" option doesn't work too well either, it just resets without actually locking anything. It can't hold a flash it seems.
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp (bootloader) [KillSwitch] Last Byte is 0X01, enable unlock (bootloader) RELOCK device
I've tried the "0PJAIMG.zip" method in download mode, but it just gives me these errors as well.
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
If my phone gets a file that matches up, it freezes for a bit, THEN goes back to another bootloop. It's frustrating.
9 RU_SECURITY_FAIL is also another error I get when trying to flash the .zip by fastboot, they're so annoying.
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2136250206 is not a multiple of the block size 4096
OKAY [ 1.028s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.053s
Then after that, I tried flashing "0PJAIMG_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.17_Radio_1.10.C1144022_50312.5_NV_SPCS_0.23_003_release_425355_signed_RYDAH805.zip" via download mode with the SD card, and it gave me a FAIL19 RU_MAIN_VER_FAIL error that I don't understand that well, but I did find a reddit thread on it. I may have messed up my partitions.
https://www.reddit.com/r/AndroidQuestions/comments/69i53h/help_with_htc_m9_fail19_ru_main_ver_fail/
HOSD is also yet another method that ends up in failure
sending 'hosd' (38148 KB)... OKAY
writing 'hosd'... (bootloader) HOSD CL#695981
FAIL35 RU_PARTITION_NOT_SUPPORT hosd
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
Execution time is 4(s)
Here are a list of things that DIDN'T work
-Firmware Flashing
-Boot/TWRP Flashing
-fastboot oem unlock
-the "Power then Volume up" trick, it just redirects me to a white HTC splash screeen
-Recovery from bootloader option
-signed .img files
https://androidforums.com/threads/htc-one-m8-brick-stuck-on-boot.927336/
After finding the thread above, I'm starting to think it might be a hardware error, it now gives me a "Failed to boot to recovery mode" error,. The eMMc may be messed up, ughhhhhhhh
Any way to recover my files, at least? If anyone here has any clues on getting my phone to working condition, I'd appreciate it a ton, hell, I might even pay you for helping me, better than losing all my data!
Will add as much info as possible and update my current status if asked.

Stop before you break it.
Find the official stock signed firmware ruu in .zip format that matches your current firmware. Ie 3.41.651.x (x can be any number but the other 3 octets MUST MATCH). Rename it to 0PJAIMG.ZIP and copy to the external sdcard.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..

shivadow said:
Stop before you break it.
DO NOT relock/lock the bootloader and DO NOT s-on.
Boot to download mode (Black screen red writing) and at the bottom, in yellow text, you should see "press vol up to flash"..
Click to expand...
Click to collapse
That's unfortunately the issue, I AM S-On, never turned it off, which has pretty much sealed this poor phones fate I assume. If not, I'm betting I would have already flashed a no wipe .zip successfully. It's a shame, since this could have been prevented if I knew this phone was prevalent to system corruption, now the only thing I can depend on is obtaining a compatible recovery, since mine isn't working, download/fastboot is the only thing I have now.
It also seems I cannot find the "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4.zip" over the web, would an .exe work if I rename the extension as .zip?

S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
Exe or zip but sometimes exe fails. Exe must be run on a pc and have the phone connected via USB. Zip must be run from external sdcard. It MUST be that version regardless.
Your only way without buggering it further is to flash the stock firmware. It will replace the recovery etc itself and will be safer than messing around with it, if it flashes OK.

shivadow said:
S-on or s-off doesn't matter. What i meant is if you go s-off there is no need to ever s-on again. Same for bootloader. If it's unlocked then you don't ever need to lock/relock it.
.
Click to expand...
Click to collapse
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?

RebeccaSugar said:
Then I'm assuming the correct fw "0PJAIMG.zip" would flash successfully even with an unlocked bootloader?
Click to expand...
Click to collapse
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Correct.
If you prefer the *.zip over the *.exe then take a look at the "further reading" section of the ReadMe thread. There's a link to a decryption tool. Download the correct version for your computer. If you use windows, you can drag and drop the *.exe onto the decryption tool and it will extract the *.zip for you. On Linux and Mac you'll probably need to use some commands.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Done, though, after doing the "0PJAIMG.zip" method once more, it interrupts the flash with a very fast error(?) message highlighted in white then quickly reverts to bootlooping the recovery splash screen (Black Background with Silver HTC Logo)
I decided to flash the boot.img and system.img
target reported max download size of 800000000 bytes
sending 'recovery' (20084 KB)...
OKAY [ 2.097s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.838s]
finished. total time: 3.939s
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: 990005027515833
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
C:\Users\Infinity>Documents\Pack\fastboot.exe flash system C:\Users\Infinity\Documents\James\HTC\OUT_0PJA_3.41.651.21\system\system.img
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.232s]
sending sparse 'system' 1/6 (743090 KB)...
OKAY [ 40.331s]
writing 'system' 1/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 28.653s]
sending sparse 'system' 2/6 (725823 KB)...
OKAY [ 39.600s]
writing 'system' 2/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 27.937s]
sending sparse 'system' 3/6 (776453 KB)...
OKAY [ 42.390s]
writing 'system' 3/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.090s]
sending sparse 'system' 4/6 (764994 KB)...
OKAY [ 41.446s]
writing 'system' 4/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 30.371s]
sending sparse 'system' 5/6 (775925 KB)...
OKAY [ 42.348s]
writing 'system' 5/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 29.562s]
sending sparse 'system' 6/6 (546809 KB)...
OKAY [ 31.210s]
writing 'system' 6/6...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 21.738s]
finished. total time: 405.943s
They were successful, apparently, but I've seen no changes. When booting, it just hangs on the white splash screen with the green htc logo and the "This build is for development, etc" warning.
If only I had a way to boot a working recovery, the more I do this, the more it seems like it is without a shadow of a doubt, a hardware problem.
Here are some logs, the fw seems to match up with my phone just fine, nonetheles...
View attachment RUU_Decrypt_LOG-0PJA20000_3.41.651.21_2018-04-01_025319.txt
View attachment android-info.txt
View attachment android-info2.txt
View attachment backup_android-info.txt

I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
I noticed that you used fastboot. Be aware that flashing RUUs isn't possible with the generic fastboot files. You'll need htc_fastboot. A download link can be found in the RUU section of the ReadMe thread.
Are you sure that the SD card isn't broken? (Never use old cards for flashing RUUs. They can corrupt the files.) Did you try another one? Normally the extracted *.zip should flash just fine via an SD card.
I'd try a different SD card and flashing the RUU via htc_fastboot. (Flashing only the system and the boot.img might not be sufficient.) If both methods fail then the phone's hardware is most probably damaged and there's nothing you could do.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I used a different SD card, formatted it to fat32 then exFAT, and nothing happened, it just gave me another error and rebooted. Though, after the reboot I manually booted the download mode and the same happened. Except this time, it gave me a list of all the .img files at 0% inside the "0PJAIMG.zip" before abruptly shutting off.
I took your advice on using the manual htc_fastboot to flash the "0PJAIMG.zip", even with the powershell, and it still fails.
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 3.41.651.21
found large-zip header, file count: 8
processing file 1/8...
sending 'zip' (88845 KB)...
OKAY [ 5.992s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 7.195s
htc_fastboot finished. total time: 8.782s
I did a bit of spelunking and came across this users post, that had the same issue as I.
repl1ca said:
Ok...so hopefully I didn't foobar something. I went to go back to stock since I'm returning my phone soon (1 year lease), so I relocked my bootloader before trying to flash the RUU (I'm S-ON by the way). Relock went fine, but the phone immediately returned to the bootloader with a "*** Security Warning***" message and now the phone won't boot into the ROM or recovery. I tried booting into download mode and flashing the RUU zip, but I am getting the following message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip d:\downloads\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 2330284468 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of the block size 4096
OKAY [ 1.015s]
writing 'zip'...
(bootloader) HOSD CL#695981
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 2.017s
I also tried running the RUU exe in download mode, but that didn't work either.
Hopefully I am doing something wrong and didn't mess the phone up! I will be forever in debt to whoever can help me.
P.S. - I also tried unlocking the bootloader again but that is failing as well!! (Even though it says successful...)
_____________________________________________________________________________
EDIT: Ok, so I gave my Windows account full access to the platform-tools folder (which includes fastboot and the unlock token) and tried unlocking again, and it worked?! ROM is booting now, but how do I avoid having this happen again and return to stock? TIA
Click to expand...
Click to collapse
What did he mean by "Full Access to the platform-tools folder"? That may be my meal ticket to getting my phone working or nothing else.

You have to go into Windows Explorer on your computer and find the platform-tools folder. Once you find it, right click on it and go to Properties, then the Security tab. On that tab, add your Windows username in there and make sure the Full Access box is checked. Hit Apply, then OK.
My post is really old, so I'm having a hard time remembering what the actual issue was [emoji23]
Sent from my SM-G965U using Tapatalk

Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.

shivadow said:
Security fail means the ruu is corrupt. Remote:9 I think is unsigned ruu. You need to be flashing a signed ruu.zip.
Click to expand...
Click to collapse
That's what bothers me the most, the ruu I have IS signed, you sure I don't need S-OFF, or to lock the bootloader?

Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?

shivadow said:
Security or bootloader make no odds. If you had s-off life would probably be easier..
Exactly which file are you flashing? Have you checked the md5 hash?
Click to expand...
Click to collapse
I'll probably buy the XTC 2 Clip chip thing needed to manually turn S-OFF, I don't care about paying a little extra, as long as I can recover all my files in the phone.
I am flashing a "3.41.651.21" .zip from extracted from "RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.21.exe"
The MD5 hash for it is "f41f1b941eb3f9f9ecaebcbf235e87af"
Which looking up the hash reveals to be the version for my exact same hardware, kernel and software version
https://androidfilehost.com/?fid=312978532265363975
I'm more than confident S-OFF is the only way to fix it. Unless there are cases of android bricking, even with a working fastboot. Something, a type of security, is preventing files from being read/flashed, unless It's an eMMc error. Two verdicts now.

You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken.
Sorry for the bad news.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
You most probably won't be able to recover any files at this point. Flashing a RUU will delete everything that's stored on your phone. Even S-OFF won't change that. S-OFF will only enable downgrading with older RUUs. Converting the phone isn't recommended unless you're willing to risk getting a paperweight since it's a CDMA device.
Click to expand...
Click to collapse
At this point, it's already a paperweight, what's an extra $100 invested on the XTC 2 Clip going to do? Haha! If I can't recover the files, I'll just make an attempt at salvaging this phone and giving it away to someone else.
Flippy498 said:
I haven't seen error 9 before I read about it in this thread. Since you already tried different methods and the md5 checksum of your manually extracted RUU seems to match the one of the AFH RUU, chances are high that the phone's hardware is broken..
Click to expand...
Click to collapse
That IS a fear, especially about hearing about the "horrors" of the Hynix eMMc from people in the the thread I linked in the OP, and others in gsmhosting, this device might have just been another victim of faulty circuitry, which actually has me steamed.
http://forum.gsmhosting.com/vbb/f961/htc-one-m9-bootloop-2214236/#3
This is going to be my brave (read: foolish) attempt.

The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
The biggest problem of the M9 is the Snapdragon 810 processor. Although later firmware revisions fixed the overheating (more or less) the heat damages that emerged from to the usage of older firmware versions aren't fixable.
Most phones that got sold with this processor suffer from similar issues, sooner or later. If you check the xda forums from other 2015 flagship devices with the SD810 you'll see that they all have some kind of sudden bootloop death problem.
Click to expand...
Click to collapse
I've heard things like that before! It shorts out the board or something above those lines, if heating is an issue, then it certainly did that to mine, which may be the fault of the missing recovery and bootloop, along with one crash I remember! Yes, I remembered I had one crash, the screen had all sorts of garbled colorful static on it and the phone made a beeping noise, why didn't I remember that!? I'm an idiot. That should have been a clear warning to back up everything, I should have reminded myself of the issues with the 810 Processor. Whether the crash months earlier had anything to do with what might have either been a sign of decay, or just a coincidence is beyond me, but knowing my current position with this phone, I'll go with the former.
Flippy498 said:
And as said before, getting S-OFF won't change your situation. If you really want to try a method that has a slightly chance of being successful you should search for a jtag device like e.g. a riff-box. The thing is I personally don't have any experiences with jtagging. I only know that it can still help in situations in which there already seems to be no hope, anymore. Check sneakyghost's firmware thread in the development section. If I remember correctly, post #5 contains info or at least a link with further info about the topic. Be aware that these devices can be quite expensive.
Click to expand...
Click to collapse
Lucky for you (and me) I do! I've successfully soldered about 5 things in the past, so this phone should be familiar territory! I just cancelled the XTC 2 Clip order, and instead ordered myself a Riff Box, I saw that it supports my HTC 9, and I thank you for telling me this! I work much better under hardware than software (Thanks ADHD), I'll check out. I immensely appreciate your help, and you taking time out of your day to give me sources, it truly, honestly means a lot. The device is around $120, not horribly expensive, my wallet can take it, I'll update you on my progress later in the thread! Thanks again!
Woah, apparently I don't NEED to solder? Well, this just makes it easier I'd say! BUT, I don't trust myself enough to risk destroying the sensitive data inside my device, so I will e-mail Tecardo and offer him a price for helping me instead. Can't trust myself enough not to screw up!

Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Oh, only 120 bucks? Don't ask me why but I had a higher price in mind. Either my mind betrayed me or the riff box got cheaper...
Click to expand...
Click to collapse
Well, in your defense, there ARE bundles that are priced ridiculously high (In the $500's for some damned reason) even though you can get the same bundles separately, for less than half of what they ask.