Develop Bugs

Official update bricked phone

Update: This is an AT&T carrier unlocked phone. Bootloader says INVALID_VER_INFO for RADIO and OpenDSP.
Doing research on this INVALID_VER_INFO, your phone can be functioning normally with this issue: http://forum.xda-developers.com/showthread.php?t=2715056
Most results for this are those who tried doing something unofficial with their phone. My phone updated an official update over the air (wasn't trying to root it or anything). Somewhere it must have failed, and I can only get to the recovery portion. I read that part of recovering your phone would be to first unlock the bootloader, but that hasn't worked. I registered, followed every step on HTCDev, even the final command completed successfully. My phone still reads LOCKED. I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO". Right now I'm downloading the M8's RUU, but that'll be another hour (big file, slow Internet). The phone is not under warranty.
Am I on the right path?

tmontney said:
Most results for this are those who tried doing something unofficial with their phone. My phone updated an official update over the air (wasn't trying to root it or anything). Somewhere it must have failed, and I can only get to the recovery portion. I read that part of recovering your phone would be to first unlock the bootloader, but that hasn't worked. I registered, followed every step on HTCDev, even the final command completed successfully. My phone still reads LOCKED. I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO". Right now I'm downloading the M8's RUU, but that'll be another hour (big file, slow Internet). The phone is not under warranty.
Am I on the right path?
Click to expand...
Click to collapse
Yes you are. As long as you are downloading the correct RUU for your device/carrier, you are doing exactly what you should do. There's no need for an unlocked bootloader if the RUU was meant for you.

tmontney said:
=Right now I'm downloading the M8's RUU
Click to expand...
Click to collapse
Be aware that the RUU needs to match your CID. You can't run an RUU for just any M8 version.
Otherwise, as indicated above, if you phone is not modified already (bootloader unlock, root, etc.) and an RUU is available for your CID, there is no need to unlock the bootloader. In fact, an unlocked bootloader will prevent the RUU from working unless the phone is s-off.

My bootloader is still locked. I never saw a disclaimer message, and I still see the locked string on my screen. I can even verify it is locked with "fastboot oem lock". It will say "Device was already locked".
Seems like RUU is actually working. Before I could never get past "battery less than 30% message" when it had been charging forever.
RUU made it reboot, never rebooted, then asked for QHSUSB_BULK driver on my PC. Second time, it did eventually reboot. It took quite a while for it to do so. By that time the software must have timed out. I don't know why it has to reboot to bootloader, because it's already in the bootloader (that's all I can get to).
Every time it reboots to the bootloader, I get "USB CONNECTION ERROR".

tmontney said:
I also noticed the RADIO and OpenDSP say "INVALID_VER_INFO".
Click to expand...
Click to collapse
Radio not reading a number is a bad sign; as is the RUU not working.
Seeing as your phone is fully stock, and the problem was caused by an official update, you may be a candidate for a warranty replacement/repair.
I also wouldn't personally recommend further attempts to unlock the bootloader for that reason (may void warranty).

Running fastboot oem rebootRUU gives this output...
Code:
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.043s]
finished. total time: 10.043s
If it helps, I just remembered it was an unlocked AT&T phone. It's been some time since I've tried to fix this phone. If I didn't use the correct term, I mean it's an unlocked carrier (not bootloader).
I also noticed I must have downloaded a very old RUU. Its version was much lower than my phone's (version 1.5 RUU to version 3 something on my phone). I'm downloading the most recent.

redpoint73 said:
Radio not reading a number is a bad sign; as is the RUU not working.
Seeing as your phone is fully stock, and the problem was caused by an official update, you may be a candidate for a warranty replacement/repair.
I also wouldn't personally recommend further attempts to unlock the bootloader for that reason (may void warranty).
Click to expand...
Click to collapse
Where would I go to replace a carrier unlocked phone? I'm no longer trying to unlock the bootloader. I was never successful in unlocking it anyway. I don't believe it's under warranty, and I have no idea where or how to check.

tmontney said:
Where would I go to replace a carrier unlocked phone? I'm no longer trying to unlock the bootloader. I was never successful in unlocking it anyway. I don't believe it's under warranty, and I have no idea where or how to check.
Click to expand...
Click to collapse
If the device version is intended for your region, you may be able to get warranty service through HTC for a period of 1 year. So for the AT&T version, if you are in the US, you may still be able to get warranty.
I say "may" since I am not sure how SIM unlock affects the warranty. You can contact HTC warranty department, and they can probably answer the question (of whether you have warranty or not) and if so, guide you through that process.
Where did you purchase the phone from? Was it a 3rd party seller? How old is the phone, and did you check the seller's return policy?
Alternately, if you have no warranty, you may be able to find a repair service in your area with JTAG, which may bring the phone back to life, for a price.
---------- Post added at 02:16 PM ---------- Previous post was at 02:12 PM ----------
tmontney said:
Code:
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.043s]
finished. total time: 10.043s
Click to expand...
Click to collapse
I don't know much about these types of error outputs, but there are plenty of folks here who know more (so hopefully they can chime in).
But from what I can gather, the output looks to somewhat verify the idea that the update somehow damaged/corrupted some emmc partitions (maybe a radio brick?).
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
tmontney said:
Doing research on this INVALID_VER_INFO, your phone can be functioning normally with this issue: http://forum.xda-developers.com/showthread.php?t=2715056
Click to expand...
Click to collapse
That issue is known and related to using TWRP (custom recovery). You never did that, so its not the same issue.
Not sure whether there are instances of the issue (radio version not listed) for stock devices, and the device still working properly.
You don't have a lot of options with a stock device, aside from RUU.
Again, I'd suggest to check with HTC whether you have a valid warranty, and go from there.

Bought it not more than 2 months ago off eBay. Said it was new, but I feel it was refurbished.

Try this site to check your device warranty status
http://imeidata.net/warranty/htc

ckpv5 said:
Try this site to check your device warranty status
http://imeidata.net/warranty/htc
Click to expand...
Click to collapse
My God, it says I still have a month left. There may be hope if this RUU doesn't work.
Never mind, out of warranty.

The proper RUU failed. RUU says it's rebooting my phone, when my phone comes back RUU says USB CONNECTION ERROR.
Is there nothing left? Unlocking the bootloader failed. I can't flash recovery because bootloader is locked. Recovery and factory defaults are broken.

tmontney said:
The proper RUU failed.
Click to expand...
Click to collapse
What do you mean by "proper RUU"? What were you using before, and which one are you using now (full filename, or link it).
Try to but your phone in bootloader - fastboot mode. Since you phone is not booting, it will need to be in this mode for the RUU to run.

redpoint73 said:
What do you mean by "proper RUU"? What were you using before, and which one are you using now (full filename, or link it).
Try to but your phone in bootloader - fastboot mode. Since you phone is not booting, it will need to be in this mode for the RUU to run.
Click to expand...
Click to collapse
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe

tmontney said:
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Click to expand...
Click to collapse
So what RUU were you trying to run before?
What is your present hboot number?
What is your present main version number?

redpoint73 said:
So what RUU were you trying to run before?
What is your present hboot number?
What is your present main version number?
Click to expand...
Click to collapse
The RUU I linked is the one I tried running.
HBOOT: 3.19.0.0000
I assume "main version number" is the OS version: 3.42.502.1

tmontney said:
The RUU I linked is the one I tried running.
Click to expand...
Click to collapse
Got it. For some reason, I was under the impression you tried to run 2 different RUUs. Probably just misinterpreted your wording.
tmontney said:
HBOOT: 3.19.0.0000
I assume "main version number" is the OS version: 3.42.502.1
Click to expand...
Click to collapse
Yes, main version and OS version are the same. The terminology just varies depending on what method you use to look it up.
The RUU you are using is okay to run based on your hboot and OS number. I asked before if you tried to run the RUU while you phone is in bootloader-fastboot mode. Try that, and see if you still get the USB connection error.

redpoint73 said:
Got it. For some reason, I was under the impression you tried to run 2 different RUUs. Probably just misinterpreted your wording.
Yes, main version and OS version are the same. The terminology just varies depending on what method you use to look it up.
The RUU you are using is okay to run based on your hboot and OS number. I asked before if you tried to run the RUU while you phone is in bootloader-fastboot mode. Try that, and see if you still get the USB connection error.
Click to expand...
Click to collapse
Fastboot is the only mode I can go in (well that and HBOOT). It will give me an error when it tells the phone to reboot.
Take a look at this thread: http://androidforums.com/threads/htc-one-m8-stuck-in-bootloader.917358/ I started a thread for this issue there, and they're pretty certain my phone is bricked.

tmontney said:
Fastboot is the only mode I can go in (well that and HBOOT). It will give me an error when it tells the phone to reboot.
Take a look at this thread: http://androidforums.com/threads/htc-one-m8-stuck-in-bootloader.917358/ I started a thread for this issue there, and they're pretty certain my phone is bricked.
Click to expand...
Click to collapse
By "they" you mean the one guy that is helping you there.
I'm not giving up just yet.
As long as the phone is in fastboot mode, USB connection error is usually due to issues on the PC side. Try uninstalling HTC drivers,and re-installing. Try a different USB port, cables, etc.

redpoint73 said:
By "they" you mean the one guy that is helping you there.
I'm not giving up just yet.
As long as the phone is in fastboot mode, USB connection error is usually due to issues on the PC side. Try uninstalling HTC drivers,and re-installing. Try a different USB port, cables, etc.
Click to expand...
Click to collapse
Alright, but I tried using the ROM.zip on my SD card and that failed. By "failed", it failed step 1 in the update process. Doesn't that rule out any PC-side issues? I'm out of town until Sunday, so I'm unable to try anything right now.
Post #9 and #20 should be of interest.

M9 Unlock Token Verify Fail?

Not new to the scene here, just getting back into it. My M9 is giving me trouble; I've been through all the threads Google knows about in English and other languages.
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
[KillSwitch] Last Byte is 0X01, enable unlock - I enabled the bootloader unlock option in developer settings.
Using Download mode, as this is the new correct way. fastboot devices works and get_identifier_token works.
I tried several unlock codes from HTCDev.
Tried rebooting and all combinations of rebooting + getting new code.
Tried HTCDev fastboot.exe and android platform tools fastboot.exe.
Tried cmd and powershell.
Tried different folder locations (desktop and C:\Android)
Note that every time I get_identifier_token, the token is different. I don't remember if that's normal.
I've used HTCDev to unlock many devices, never had problems.
Output of every attempt to flash unlocktoken:
Code:
C:\Android>fastboot.exe flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.035s
What am I screwing up here?

xfinrodx said:
** This is a "One M9 Unlocked" GSM phone; not developer version or carrier-specific **
Click to expand...
Click to collapse
I am confused. Why are you trying to unlock a phone that is already unlocked?

Thanks for your question: It is the factory carrier unlocked version. It works with any GSM card without needing a carrier unlock code - however, the bootloader is still locked. Whereas it's nice to not be tied to a carrier, I'd also like to get involved with cyanogenmod again.

For whomever else finds themselves in this situation: Good luck, I have no idea what happened.
I tried and retried this process several times. Finally gave up in exasperation and tried later on a different machine because that makes no sense but why not... Here's my winning magic combination (that I already tried, but on a different machine)
Front panel USB port.
Complete HTCDev unlock procedure with caveats:
I used the Google Bootloader Interface driver; HTCSync has never been on this machine.
I used the Google platform tools fastboot application.
Everything else exactly as HTCDev prescribes.
Do this on two totally different machines; it might help to be exasperated the second time. Did literally nothing different... on to the roms now.

unlocking bootloader help

i am getting this error please help
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.016s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.059s

why you don't go to http://www.htcdev.com/bootloader to open it
I don't know if work or not cuz I not get the phone and never use htc before
Sent from my iPad using Tapatalk

double check you have entered your serial number etc correctly on the htc dev site, any mistakes will generate the wrong unlock code.

DinarQ8 said:
why you don't go to http://www.htcdev.com/bootloader to open it
I don't know if work or not cuz I not get the phone and never use htc before
Click to expand...
Click to collapse
That is the website I am getting my unlock, I am a long time HTC user and I have done this hundreds of times, the thing is just not working out for me this time, but thanks for trying to help

Doesnt HTC 10 also have option in developer options to block bootloader unlocking?
Here on mine M9
OEM unlocking
Allow the bootloader to be unlocked (unchecked by default)

alexp999 said:
double check you have entered your serial number etc correctly on the htc dev site, any mistakes will generate the wrong unlock code.
Click to expand...
Click to collapse
Will try again tomorrow...

I'm having the same problem. Allow unlocking is ticked

rampage101 said:
I'm having the same problem. Allow unlocking is ticked
Click to expand...
Click to collapse
Did you allow unlocking before you tried?Or after it failed u tried ticking it on?
Because if u allowed bootloader unlocking you need to generate new unlock token all over!

Before. I've tried several times, still can't get it

rampage101 said:
Before. I've tried several times, still can't get it
Click to expand...
Click to collapse
Well try contacting HTC support than.

Just got it to work. Not sure what exactly solved it. Did another reboot of the laptop, used Chrome instead of Microsoft Edge. Waterfox (Firefox) didn't work properly with HTC Dev, so not sure what was going on.

No OEM unlock on the Verizon 10 in developer settings

rampage101 said:
Just got it to work. Not sure what exactly solved it. Did another reboot of the laptop, used Chrome instead of Microsoft Edge. Waterfox (Firefox) didn't work properly with HTC Dev, so not sure what was going on.
Click to expand...
Click to collapse
not sure that was reason but used Microsoft edge and it worked Thanks!!!!!!!!!!!!!!

Surprisingly, I am running into this issue as well. I have done this several times before and never had this issue. I am doing it on Linux and I have done it from Linux before. The developer option for unlock is enabled.
I have tried several times now, with different browsers, and the same result.
Does anybody know how to get out of the download mode? I can't even reboot this device at this time. Holding power does not power off - fastboot reboot helps.

yes I was in the same boat. I had to generate 4 unlock.bin files till it finally accepted it.

Looks like 4th time is the charm... It finally did unlock it.

Power button and vol down held down for a while will reboot it. Also, "fastboot reboot" will do it too.
Sent from my HTC 2PS6200 using Tapatalk

JEANRIVERA said:
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.059s
Click to expand...
Click to collapse
I had the same thing happen to me. I rebooted the phone, went into developer settings to verify OEM Unlocking was checked (it was). Powered off the phone, held down volume down, took it into download mode and tried again. This time it worked. I only ever got one Unlock_code.bin file, so I know it was good even when it was failing.

Make sure you are including the <<< >>> lines, both above and below? Off the top of my head I cannot remember what they say, but there are lines of texts before the code begins and after it ends.

Same here, it was the third time for me, but I did notice each time I'd run the get_identifier_token, that the token would come out differently each time. Eventually submitting through Edge got me the proper unlock.bin
First time Firefox said invalid error
Second Chrome said success, but unlock bin did not work
Third used edge, Success, unlock bin worked.
This was not this much of a pain on both Motorola Moto X and Moto MAXX

Error while unlocking phone

I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
C:\Users\Ben-Desktop\AppData\Local\Android\sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.005s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) Device is unlocked
OKAY [ 0.013s]
finished. total time: 0.020s
Click to expand...
Click to collapse
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0

ganeran said:
I just bought an HTC One M9 - Developer edition. I wanted to unlock it and followed all of the directions from the HTCDev site. The only difference was that I used the fastboot program from my Android Studios instead of their fastboot zip. When I run the command fastboot flash unlocktoken Unlock_code.bin, I get an unusual response:
When this happens I am stuck on a screen that says "download 100%" and "Start downloading" highlighted in blue. The HTCDev site says that I should get a pop-up that says whether I want to unlock the bootloader, but I just get stuck here. I know how to get out of this screen using the up arrow and power button. What I'm trying to figure out is how to actually unlock my phone.
Any thoughts?
P.S. It may be worth noting that I fully updated my phone beforehand so I don't know if its setup to work for an easier version, but fails for 6.0
Click to expand...
Click to collapse
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!

Fain11 said:
If u got a dev edition it's already unlocked.
It says u are unlocked.
If not, check the oem unlock in the developer settings.
Good luck!
Click to expand...
Click to collapse
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?

ganeran said:
Okay, I guess I'm trying to turn the machine to S-OFF then. I still don't have root access (or at least that's what titanium backup says). Do you know of a place with instructions for that?
Click to expand...
Click to collapse
Start reading here:
http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133

Moto Z Play Unlocked Bootloader Issue

I have been trying to unlock my bootloader on my Moto Z Play for awhile now without any luck. It is running Android 7.1.1 Nougat and the carrier is Verizon. I've gotten the unlock string and went to Motos official cite and tried getting an unlock code I could use in adb, but it said my bootloader could not be unlocked. Can someone please tell me how to work around this or fix this?

jbaker14111 said:
I have been trying to unlock my bootloader on my Moto Z Play for awhile now without any luck. It is running Android 7.1.1 Nougat and the carrier is Verizon. I've gotten the unlock string and went to Motos official cite and tried getting an unlock code I could use in adb, but it said my bootloader could not be unlocked. Can someone please tell me how to work around this or fix this?
Click to expand...
Click to collapse
The Verizon version is not eligible for bootloader unlock. Thank your carrier for this.

dandrumheller said:
The Verizon version is not eligible for bootloader unlock. Thank your carrier for this.
Click to expand...
Click to collapse
On T Mobile, I have the XT1635-02
I had relocked my Bootloader successfully now I am trying to unlock again on Oreao 8.0 using ABD as I did originally a year a go but it seems not to be working for me.
What am I missing here... Can anyone make any suggestions.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223LX6NN fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock "CODE IS PLACED HERE I RECEIVED"
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.172s]
finished. total time: 0.172s
If I go with the idea that my bootloader never really relocked, than I figured I just try flashing TWRP and I get invalid or corrupt file. So that is not working either.

Any suggestions.

On my -03 model, when I flash TWRP I always get the message the file is invalid, bit it always flashes!

okaban said:
On my -03 model I relocked and now trying to unlock again, when I flash TWRP I always get the message the file is invalid, bit it always flashes!
Click to expand...
Click to collapse
I had tried that and after a reboot when I try to boot into twrp it gives me the lying down android figure, letting me know it did not flash permanently.
I see in my developer options my unlocking toggle is greyed out, which makes you believe it is unlocked. So why can I not get TWRP to flash... I just want to flash some custom roms.
What am I missing here... Thanks.

I don't believe anyone has unlocked the -01 model.