Database Info

AT&T One X bricked downgrading bootloader, im fully S-OFF Help!!!

So i dont know what happend, i succesfully make my hox S-OFF, use the phone and everything was working fine, then a try to downgrade my bootloader with Jet but everything went wrong from there, the process didnt finish, i try to relocked my bootloader to install the 2.20 RUU thinking it would fix it but know the RUU procesos finishes with a 131 error because my cid is diferent, this is what i have:
******tampered*****
******relocked******
jewel pvt ship s-off rl
cid-spcs_001
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
I can put fastboot commands but its shows FAILED (remote: not allowed), i cant go into recovery, also on jet i cant go into QHSUSB_DLOAD anymore.

You really didn't need to downgrade being you were s-off.............
Sent from my HTC One X using Tapatalk 2

Did you try this command to unbrick?: sudo ./jet -u
Edit: hmm just noticed your cid changed to stock. Sorry idk where to go from there
Sent from my HTC One X using xda premium

Yes i did try the ./jet -u command but i cant get in to QHSUSB_DLOAD anymore that is the stock cid for the one x ? if thats the case maybe i can run de 1.85 RUU?

pikul said:
i cant get in to QHSUSB_DLOAD anymore
Click to expand...
Click to collapse
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.

No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium

redpoint73 said:
Did you try the hardware key way? Same as bootloader, but power and vol +
Practically gave myself a heart attack yesterday. Someone here was having trouble getting into bootloader, and mentioned power and vol +. I couldn't remember what that did (knew it wasn't bootloader) so I did it, and put the phone in Qualcomm download mode!
I was able to get back to bootloader, recovery, and reflashed the ROM that happened to be on my phone.
Click to expand...
Click to collapse
I guess i could run the ./jet -u command and press those keys, its that what you mean?
panda_mode said:
No. What I meant was your cid isn't supercid anymore. And I wouldn't use that RUU since your hboot is 1.14; wait till someone more experienced helps you out
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ooooooooo :good: at least i can get into bootloader and put fastboot commands, i guess thats something

pikul said:
I guess i could run the ./jet -u command and press those keys, its that what you mean?
Click to expand...
Click to collapse
I've actually never used JET, and not quite sure how it works.
But power and vol + will put the phone in QHSUSB_DLOAD in most situations (nothing to do with JET), if that is all you are trying to do. Similar to how power and vol - boots into bootloader. Just curious if it would still worked in your "bricked" condition.

Are you able to get into fastboot? If so just use stock RUU to get back to stock,

thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?

pikul said:
thats the thing, i can get in to fastboot, try to run the 2.20 RUU starts and maybe 1 minute later it fails, and gives a ERROR [131] i google it and it seems to be because the cid its not the correct one anyone knows if there its a way to bypass the cid verification?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/HTC_One_X
Try this thread. I think there is a way to use the stock recovery and the cid you used to unlock it. May give you some ideas.
AT&T HTC OneX
Andriod 4.1.1
ViperXL

i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader

pikul said:
i check all of them, but i just cant get to unlock my bootloader again or flash a different cid, not even flash the recovery, y guess its because i relock my bootloader
Click to expand...
Click to collapse
Have you tried to get a new identifier token and unlock the phone to get TWRP again?
http://onexroot.com/one-x-root/how-to-unlock-bootloader-and-root-att-htc-one-xhtc-one-xl/
AT&T HTC OneX
Android 4.1.1
ViperXL

is it posible to get it in bootloader mode? cause thats all i can access :/
Everytime i try to flash a file in fastboot it shows FAILED (remote: not allowed)

pikul said:
is it posible to get it in bootloader mode? cause thats all i can access :/
Click to expand...
Click to collapse
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.

mirGantrophy said:
download a ROM.. put it in your fastboot folder,
boot into fastboot and try this
fastboot flash zip name_of_rom.zip <-- this works with HTC RUUs, may work with an actual ROM.. Use at your own risk, I have never tried it with a custom ROM.
Click to expand...
Click to collapse
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s

pikul said:
I took the .img files from the rom.zip that you get from the RUU, but it doesnt work.
C:\Programas\Fastboot>fastboot flash boot boot_signed.img
sending 'boot' (6156 KB)...
OKAY [ 0.966s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.000s
C:\Programas\Fastboot>fastboot flash system system.img
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.309s
Click to expand...
Click to collapse
If you have the RUU.zip, do this then:
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip rom.zip
see if that works..

This is what i get:
C:\Programas\Fastboot>fastboot flash zip rom.zip
sending 'zip' (576544 KB)...
OKAY [ 24.368s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 26.975s

this sucks, i have to go to work and i dont have another cellphone :/

pikul said:
this sucks, i have to go to work and i dont have another cellphone :/
Click to expand...
Click to collapse
You can try to find the cidnum for the htc onexl and see if you can trick it by editing android-info.txt file to match cid num.
Example:
edited android-info file
modelid: PG3213000
cidnum: KT___901
cidnum: HTC__004(this edited file only)
mainver: 2.32.1010.1
hbootpreupdate:13
boot again into fastboot
AT&T HTC OneXL
Android 4.1.1
ViperXL

Stock GT-I9020A: Won't boot, can't unlock bootloader

Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!

Same issue
stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
I have the same problem wit an I9020T for australia and would appreciate any advice available as well.

Send to samsung service

stevz34 said:
Hi all,
Looking for some insight here. I have a second-hand Nexus S GT-I9020A that was replaced because it would no longer boot. I took on the challenge of trying to fix it. Based on the reading I've done so far it may have bad a bad NAND chip, but I'm too stubborn to give up on it just yet. Here are the symptoms:
When booting normally, it hangs on the Google screen with all 4 hardware buttons lit up.
Fastboot works, however I can't flash anything because its bootloader is locked, which brings me to my next point.
When issuing the command fastboot oem unlock, I am prompted with the familiar Yes/no screen but when selecting Yes, nothing seems to happen. I've left it for about 6-7 hours and came back to a message in my PC command window stating "Status read Failed (too many links)".
I can get into the stock recovery but that's really of no help at all. I can wipe cache partition without an issue but get an error when trying to wipe data/factory reset.
I've attempted the One-Click UnBrick software which I read somewhere is compatible with the Nexus S. It did recognize the phone, send a command, and give a success message. The phone rebooted but nothing changed.
So, this leaves me with nothing left to try but to post here. It seems that since I cannot even unlock the bootloader that my hands are tied. Are there any other tools that I should be aware of that can diagnose bad NAND flash? I don't want to toss the phone until I know I've tried everything I can to troubleshoot.
Any help is greatly appreciated. I tried to give as much detail about the problem as I could but if I left out any important info let me know.
Thanks!
Click to expand...
Click to collapse
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...

Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.

Spanner127 said:
Tried this but as said fastboot is not recognised by my pc. Have installed almost all the drivers I can find to no avail. Must be something else to try.
Click to expand...
Click to collapse
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?

Dark_Eyes_ said:
Well, you should be able to flash official Google images in stock recovery too... Have you tried that?
Click to expand...
Click to collapse
mY COMPUTER ONLY RECOGNISES abd IN SIDELOAD MODE. tHE FASTBOOT ANYTHING IS NOT RECOGNISED SO i CANNOT UPDATE OR FIX anything. Thanks for trying.

Can you try doing all the stuff you did in some another PC.
Worth a try.

Dark_Eyes_ said:
Try flashing the official Android 4.1.2 image from Google in fastboot. See if it boots... Then maybe you will have more luck unlocking it! I would also try to wipe as many thing as possible before doing it. Try system, data, boot, cache, dalvik... Even sdcard might help...
Click to expand...
Click to collapse
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked

stevz34 said:
Tried as suggested, received the following output:
C:\Users\Steven\Downloads\sojua-jzo54k>flash-all
sending 'bootloader' (1536 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.203s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.543s]
writing 'radio'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.543s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKA3
Baseband Version.....: I9020UCKF1
Serial Number........: 33311A4C1F8500EC
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
FAILED
Device version-bootloader is 'I9020XXKA3'.
Update requires 'I9020XXLC2'.
finished. total time: 0.016s
Press any key to exit...
It would seem that I can't flash anything, including official firmware, if the bootloader is locked?
On the plus side, the phone responds fine to the fastboot commands and seems to transfer the images to it just fine, just still no luck getting the darn bootloader unlocked
Click to expand...
Click to collapse
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!

Dark_Eyes_ said:
Normally it is possible to flash official ota from Google even if the bootloader is locked. What version did you have prior to your problems? Try flashing the ota package that came just after your version as it seems that the package your are trying with cannot be flashed over the version that you have right now!
Click to expand...
Click to collapse
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?

stevz34 said:
Currently the phone has 2.3.6. I tried flashing 4.0.4, which was the next one, and it failed with the same error, indicating I need to unlock my bootloader. Also tried flashing the 2.3.6 firmware, received the same error. I'm starting to think I should probably give up on this phone.
Any more suggestions?
Click to expand...
Click to collapse
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664

Dark_Eyes_ said:
Did you try the OTA update from Google? That's weird cause I flashed it back then and I was on stock 2.3.6 with locked bootloader and stock recovery and it worked. Have you don't anything particular with your phone or is it pure stock 2.3.6? Start there
http://forum.xda-developers.com/showthread.php?t=1063664
Click to expand...
Click to collapse
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?

stevz34 said:
Thanks for posting that link. Still no luck though. I tried the 2.3.6 (GRK39C) -> 2.3.6 (GRK39F) OTA file and the 2.3.6 (GRK39F) -> 4.0.4 one as I am not sure which version of 2.3.6 that I have. Basically I am trying to use fastboot to apply the OTA update using fastboot -w update filename.zip however it is failing with the following message:
C:\Users\Steven\Downloads>fastboot -w update d1be8195481a.signed-sojua-GRK39F-fr
om-GRK39C.d1be8195.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Steven\Downloads>
The OTA updates indicate they can be flashed using stock recovery. However when I enter the recovery on the phone and select update from sdcard, I get the message indicating that it cannot mount /sdcard. Is there another way I should be doing this?
Click to expand...
Click to collapse
You have to rename the file to update.zip and place it on /sdcard. It will install it automatically. Stock recovery won't install custom zip file so that's why you need to do that. Let me know if it works...

[Q] Not quite sure what to do...

So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s

CinemaGFX said:
So I'm in the process of getting my phone back to original to so I can edge up my phone. I accident relocked the bootloader with oem relock, and now I'm stuck with S-OFF and "relocked." I'm not quite sure what to do now, as I also uninstalled SU. How do I go about getting "Locked" and S-ON. I tried the sdb shell and all that stuff, but when you type SU I can't since it is no longer installed. Also if I try to push a recovery it fails.
Code:
C:\ADB>fastboot flash recovery cwm_v6.0.4.8_m8vzw-3.img
target reported max download size of 1830612992 bytes
sending 'recovery' (12564 KB)...
OKAY [ 1.175s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.193s
Click to expand...
Click to collapse
So what you need to do is. Supercid your phone to 11111111 an go to htcdev.com an unlock your bootloader. Then once that is done. You need to downgrade to 1.55 so then you can lock your bootloader turn s-on an ruu the encrypted ruu that posted. Do NOT TURN S-ON till you find this ruu that's posted an understand it completey an ask dottat any question in that thread. Once you r downgraded locked an s-on an run the encrypted ruu your phone should be all stock an lock an s-on no tampered no nothing.

I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?

CinemaGFX said:
I was able to get back to stock except I have the tampered flag. I did this last night so I was unable to follow your steps. What should I go about now, as I have S-ON, locked bootloader, no root and a tampered flag?
Click to expand...
Click to collapse
I think he specifically said do NOT turn s on. You cannot do anything unless you s off again. What Rom do you have loaded? Turning s off is the LAST step because it's like locking the door and throwing away the keys

I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...

CinemaGFX said:
I actually did that stuff before I saw his message, I followed: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Guess now I'm going pay to get the s back off...
Click to expand...
Click to collapse
Well. We got something else to try. What version os are you on?

Bootloop! Unable to flash stock rom or lock bootloader (Help)

Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.

You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk

Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.

bootloader fail to unlock

Hello I have trouble unlocking the bootloader on HTC One SV (K2_UL) I went to htcdev.com and downloaded the unlock key on Unlock_code.bin and by fastboot it flashed and pops up the question whether to unlock the bootloader, then click YES and the phone is restarted but it still shows the message in pink *** LOCKED *** I will add that I have damaged software on your phone. Instead of normally booting the system, it will take a moment for the HTC logo and the phone goes into HBOOT mode When flashing the system through fastboot pops up
Sending 'system' (661993 KB) ... OKAY [33.105s]
Writing 'system' ...
(Bootloader) signature checking ... FAILED (remote: signature verify fail)
Finished. Total time: 100.578s
And it's just the fault of this bootloader Please help! Thanks in advance and I greet all forum members
Sorry for my English

metteorek said:
Hello I have trouble unlocking the bootloader on HTC One SV (K2_UL) I went to htcdev.com and downloaded the unlock key on Unlock_code.bin and by fastboot it flashed and pops up the question whether to unlock the bootloader, then click YES and the phone is restarted but it still shows the message in pink *** LOCKED *** I will add that I have damaged software on your phone. Instead of normally booting the system, it will take a moment for the HTC logo and the phone goes into HBOOT mode When flashing the system through fastboot pops up
Sending 'system' (661993 KB) ... OKAY [33.105s]
Writing 'system' ...
(Bootloader) signature checking ... FAILED (remote: signature verify fail)
Finished. Total time: 100.578s
And it's just the fault of this bootloader Please help! Thanks in advance and I greet all forum members
Sorry for my English
Click to expand...
Click to collapse
It is possible that you have problems with partitions.
Before unblocking, do order using RUU.
Have you tried to install fresh ROM by RUU?
Have you read this post for example?

ze7zez said:
It is possible that you have problems with partitions.
Before unblocking, do order using RUU.
Have you tried to install fresh ROM by RUU?
Have you read this post for example?
Click to expand...
Click to collapse
I am typing in fastbooot
Fastboot oem rebotRUU and jump me out
(Bootloader) Start Verify: 3
(Bootloader) SD: write failed in CMD25.
OKAY [1.229s]
Finished. Total time: 1.230s
This is the case when there is an SD card, and without the sd card the same is only sequentially
Start Verify 1,2,3 and the phone resets it stands for a moment on the logo and enters again into hboot mode and the same is true. I also tried the file
Ruu "filename etc" .exe and when i'm in fastboot mode it asks if i update ROM memory YES i choose phone resets stands for logos and back to hboot mode and the program crashes error that i can not get a phone call
Please help Regards
I have also heard that sd card can upload system. I tried it but after uploading the system in zip I jump
PL80DIAG.zip not found
PL80IMG.nbh
PL80IMG.img ... etc
And after rename the zip file on the PL80DIAG.zip goes in the upper right corner of the green bar, then the brown and the message "Press power button to reboot" and the phone is resetting stands and moments on the logo and again HBOOT. If you have original PL80DIAG.zip file with nbh file formats,
This is to be posted on the forum
Thank you