Develop Bugs

[Q] Any way to unlock a bootloader again (currently showing "relocked")

So I am new to the posting aspect of xda but have been around checking out other peeps info for a while. Basically I've gotten into a weird situation, and have no idea now how to fix it. Sorry if there is already a thread for this issue, but I have been looking for 2 days, and decided I was in over my head.
I have a HTC One M7 Verizon (blue Best Buy model) which I got AFTER HTCDev had locked Verizon from unlocking bootloader via their website.
One a exploit was found to unlock the bootloader and gain root, I jumped and ran through the process using a CWM recovery and a Cyanogenmod as my ROM. Everything was peachy until a few days ago when an update, auto updated over night, and created a problem where my phone would reboot show the lock screen, but when I swiped up to unlock it, the green HTC came back up and eventually the thing would reboot.
So I started looking around to see what other ROM's were out there at the moment and flashed ViperOne, all was well, updated my radio, firmware, and such. However, every-time my phone would go into a regular boot after setting up the ViperOne ROM, it would freeze.
So desperate for a fix I hurriedly wiped the system, used CWM recovery to reinstall the stock rom.
Upon doing this I decided I should take advantage of the stock status of the phone and get the OTA's. This is where I became stupid!!!!!
Apparently doing such a thing re-locks your bootloader. Since I wiped the system SU was not longer installed and I lost root as well. Now I cannot issue ANY fastboot FLASH commands from my adb/fastboot CMD.
HELP, pretty, pretty please!!!
I really don't like sense at all, and think that Blinkfeed is the largest piece of #[email protected]*&^% I have ever seen.
Thanks in advance for even reading!
***Edit***
Forgot to mention what's currently running on my phone:
Build/OS: 4.3 JB CL278010 2.10.605.1
Kernal: 3.4.10-g40851b1
[email protected] #1
Baseband v. (Radio) : 1.12.41.1112_2
Basically stock jelly bean, used a stock RUU version flashed via fastboot flash command. Once phone rebooted with stock then applied the 2 previous OTAs I had missed coming from 1.10.605.10 (4.2)

Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?

cmlusco said:
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
Click to expand...
Click to collapse
Yes I am still s-off, thank goodness!
I just can't get any flash commands to work, even in oem rebootrRUU.
I can try going through the process your suggesting and see if it works, will update with results.

What errors do you get when trying fastboot cmds?

"What errors do you get when trying fastboot cmds?"
Once I am in bootloader and go into fasbootusb this is what I have tried:
fastboot oem rebootRUU (phone flashes and comes up with the silver HTC on the screen)
Send the command for recovery:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8786 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.199s
If I try to flash a zip:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip superuser.zip
target reported max download size of 1526722560 bytes
sending 'zip' (4538 KB)...
OKAY [ 0.697s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.972s
It will respond (obviously) when I give it:
fastboot reboot-bootloader
But am not able to enter any adb commands as there isn't a recovery installed!!
Here is the info from the phone:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxx
(bootloader) imei:xxxxxxx
(bootloader) meid:xxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
The fastboot system will let me do things like, change my CID from VZW_01 to a super CID11111111 and back again, no errors, but not sure how much help that is...
I worry about trying to flash a new RUU because I can't back anything up right now....also just to be sure I heard I shouldn't upgrade further to Kit-Kat as there isn't a unlocked bootloader exploit yet...correct? (Obviously if I was still unlocked, and not relocked it wouldn't be an issue)
Click to expand...
Click to collapse

Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.

cmlusco said:
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
Click to expand...
Click to collapse
YAY!!!! That worked
:good:
Thank you for all of your help!! I really appreciate it, I knew there was probably a way to get a custom recovery installed, I just had run out of plays in my own knowledge book!!
I will now be able to do a nandroid b/u and get rid of the stupid sense Blinkfeed, belch! lol

[Q] HTC ONE V sim unlock

Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!

XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk

htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>

XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk

fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>

XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk

Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!

XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.

GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?

XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk

help plzzz my m9 dead failed to boot to download mode

no recovery
no download mode
***LOKED***
***S-ON***

Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?

computerslayer said:
Details please.
What can you boot into, if anything? (Bootloader, system, recovery & download mode).
What variant do you have (CID & MID, if possible)?
What did you do that brought your phone to this point?
Click to expand...
Click to collapse
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed

aboelgasim said:
Reading information...
Using Fastboot mode...
Reading common information
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT53SYJ09030
Execution time is 140(ms)
all:
Reading secure flag information
... (bootloader) read secure flag: 3
Execution time is 15(ms)
OKAY
Reading CID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Reading MEID information
Execution time is 15(ms)
... FAILunknown command
FAILED (remote: unknown command)
Read information failed
Click to expand...
Click to collapse
mod- 0PJA110
CID 11111111

aboelgasim said:
mod- 0PJA110
CID 11111111
Click to expand...
Click to collapse
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?

Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)

extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.

side_flip15 said:
extract hosd.img from your firmware.zip and flash via fastboot in bootloader. You should be able to boot to DL mode again.
Click to expand...
Click to collapse
Awesome! I would never have thought of that. Another reason I love XDA.

computerslayer said:
Excellent. Tell us about what happened to get to this point. Also, what can you boot into, if anything?
Click to expand...
Click to collapse
after back s-on

computerslayer said:
Awesome! I would never have thought of that. Another reason I love XDA.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (38128 KB)...
OKAY [ 1.544s]
writing 'hosd'...
OKAY [ 0.671s]
finished. total time: 2.231s
but i still cant open download mode

I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk

My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.

shivadow said:
I notice there is still no explanation on how the device got to this stage. I advise waiting until op explains before committing.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I wanted to back s-on

side_flip15 said:
My suggestion was based from my experience. I got the same problem before. Not sure how it happened but flashing hosd fixes my device.
You can try flashing hosd from any 3.35.xxx firmware. I'm on dev edition firmware but hosd does not work, tried hosd from 401 and it worked.
Click to expand...
Click to collapse
search abote 3.35.401 firmware ???

So what did you do? Tell us the steps you took that caused your phone to be in this state.

aboelgasim said:
no recovery
no download mode
***LOKED***
***S-ON***
Click to expand...
Click to collapse
What have you done to get the phone into this state?.
If you do not tell us what you have done so far, we cannot help you.
computerslayer said:
Your MID indicates that you have the unlocked/developer edition of the phone, so my advice would be to use the RUU for that device. You'll have to boot into the bootloader and connect your phone to a PC (this RUU won't run on any other operating system), but it should restore your phone completely to stock.
Be aware that using a RUU is a destructive restore - it'll wipe everything on the phone.
(It's weird that you're S-ON and yet have a CID of 11111111, which is the SuperCID. Changing the CID is only possible after S-OFF.)
Click to expand...
Click to collapse
Borked it trying to get supercid on an s-on phone?
Sent from my HTC One M9 using Tapatalk

computerslayer said:
So what did you do? Tell us the steps you took that caused your phone to be in this state.
Click to expand...
Click to collapse
try back s-on by xtc2clip by SD mode editor

aboelgasim said:
try back s-on by xtc2clip by SD mode editor
Click to expand...
Click to collapse
Right. So, what steps did you take? Describe, in detail, what you did.
Then describe the state of your phone right now. For example, can your phone boot into the a)system or b)the bootloader or c)download mode or d)recovery or e)more than one of these (which ones)?
One sentence descriptions are not enough - you're giving answers with so little detail that we can't give reliable advice.

Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.

side_flip15 said:
Exactly what happened to me.
Was playing with the xtc2clip returning back to s-on using sd mode. Ended up with corrupted download mode.
Try flashing hosd from .401. It should fix the problem.
Click to expand...
Click to collapse
send any link blzzz

Sprint M9 - Can't boot to recovery, can't flash recovery, S-ON, Unlocked bootloader.

I'll try my best to be as detailed as possible.
I have an HTC One M9 from Sprint. Custom rom on it, I believe it was either Viper Rom or BadBoyz. Running a TWRP PRE 3.0 recovery.
My phone had a pattern lock screen.
I had let the phone sit for about a month with out use, after which I attempted to turn it back on to use it, what I got was a continuous HTC loading screen. So I'm thinking no big deal, all I gotta do is boot into recovery and reflash it.
I boot into recovery, It won't format a number of partitions (I.E. data, system, cache) to allow the flash.
I follow instructions in this video:
with no luck, still won't flash.
So after a few hours of research and attempting different versions of twrp and cwm, it no longer has a bootable recovery. any TWRP 3.0 and up wouldn't run at all, no CWM recovery would run.
My understanding is that those partitions were encrypted and pre 3.0 for twrp can't handle the encryption or some such. I flash a few different versions, going from pre 3.0 to post 3.0, with post 3.0 still not booting but pre 3.0 booting.
THEN
After trying to flash back to a pre 3.0 twrp, it acts as it takes it, but when i go to boot into recovery i get:
"Failed to boot to recovery mode"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\PropertyCO\twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 3.063s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.562s]
finished. total time: 5.629s
is what fastboot returns, yet it won't boot to recovery.
So, my next attempt was to run an RUU.
RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.41
I run it, starting with my phone in download mode, RUU sees it just fine, goes to reboot into bootloader. with out assistance when it reboots it just brings up a metalic HTC logo and sits there, so when it reboots i'll hold volume up and down to get it to the boot loader. after some processing from the RUU it gives me the error 170 - USB connection error. Me thinking it's either some drivers messing it up or the cable, i try another laptop, and a series of different cables, no luck there.
I find out that I have to have the bootloader locked to run a RUU, so I attempt to relock the bootloader to see if that fixes the error.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELOCK device
OKAY [ 0.286s]
finished. total time: 0.287s
phone reboots, i force it into bootloader cause it doesn't automatically go to it, still says "*** UNLOCKED ***" up at the top.
fastboot getvar all:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXX
(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
all:
finished. total time: 0.048s
Thanks in advance!
Edit:
Attempted the ZIP method in this forum and failed too:
https://forum.xda-developers.com/showthread.php?t=1928439

Your nand is corrupt. Dead phone.
Beamed in by telepathy.

My M9 Bricked please Help

Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.

I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help

freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.

computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much

Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.

my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?

If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.

shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.

freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.

obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.

freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip

blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s

freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?

blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.

is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s

freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?

sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.