Develop Bugs

fastboot oem lock CRITICAL?

Hellooow!
I noticed i got an message when relocking my bootloader.
It is relocked but still wondering what this means?
see bold text
hope someone knows! Thnx!
I'm S-OFF
HTC one m8 stock android 4.4.4
3.28.401.9
Radio 1.22.21331147A1.29G
ps: already searched foru and google and www etc...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully…
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again…
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s

0kk0 said:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully…
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again…
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either

mato123 said:
Hi,
i have the same problem- searched the web etc, i didnt find what is the problem.
and it is not relocked on my phone, so i suppose its not on yours either
Click to expand...
Click to collapse
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?

0kk0 said:
Hi!
No mine relocks fine.. it says RELOCKED and i can unlock it again and relock etc.. but everytime got that "error" message.
Are you s-off?
Click to expand...
Click to collapse
no, im S-ON and every time i try it says ***UNLOCKED***

mato123 said:
no, im S-ON and every time i try it says ***UNLOCKED***
Click to expand...
Click to collapse
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?

0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?

mato123 said:
Sorry, what is 0P6BIMG.zip? how can i find one for myself? im at&t one m8.
Also what should i write in fastboot command?
Click to expand...
Click to collapse
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854

0kk0 said:
That zip is all in one file to flash stock system/os firmare recovery etc...
Here is more info for flashing RUU for your device: http://forum.xda-developers.com/att-htc-one-m8/general/lolipop-ruu-htc-att-m8-t3075854
Click to expand...
Click to collapse
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb

mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
strange...
have you tried:
1) From a powered off state, hold VOLUME DOWN while powering on the device.
2) Use the volume buttons to scroll to FASTBOOT and then press the POWER button to select it.
3) Connect the device to the PC while in this state and attempt the ROM update again.

0kk0 said:
I noticed i got an message when relocking my bootloader.
I'm S-OFF
Click to expand...
Click to collapse
There is no reason to relock the bootloader, since you are s-off.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
0kk0 said:
you could try to download correct 0P6BIMG.zip for your device and place it on sdcard in your phone.
Then flash it from bootloader...
It flashed correctly on mine(unlocked) without fastboot oem lock
And then try to relock it again?
Click to expand...
Click to collapse
It won't work for that guy, since he is s-on.
The reason it flashed for you with the bootloader unlocked, is since you are s-off.

redpoint73 said:
There is no reason to relock the bootloader, since you are s-off.
Click to expand...
Click to collapse
thnx for your answer but doenst answer my question
i got an "error" ans whas wondering what it means etc...

mato123 said:
i ran RUU.exe and this is what i get:
capture.png where it rebooted to bootloader, fastboot usb mode, took it quite a while, cca 1 min
capture1.png says sth is wrong with usb
Click to expand...
Click to collapse
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.

redpoint73 said:
You have a USB connectivity issue, so this is probably the reason why fastboot oem lock does not work.
Make sure you run the command while the phone is booted into bootloader-fastboot mode.
Click to expand...
Click to collapse
tnx for your answer.
i was in bootloader in fastboot usb mode already.
i sent you PM regarding whole situation. should i continue to write here or make a new thread?

Is there any possible way to unlock the OEM?

Is there any possible way to unlock OEM without going to developers option? Why i ask that? because I factory reset my HTC One M9 and im stuck on Google account login and I forgot what gmail i used to it. So i dont have access to my phone's settings to go to developer's setting and unlock the OEM there. And now i tried to unlock my bootloader with the help of Htcdev i follow all the steps until step 5 when I try to put the fastboot oem get_identifier_token i got this message appeared on my cmd
C:\adb>fastboot oem get_identifier_token ...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
and i tried this commands fastboot erase userdata and fastboot erase frp and this is the result
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.031s
So is there a possible way to unlock oem without going to developer's settings/option? I's still hoping there's a way to fix my phone. btw im S-ON

Help! My HTC One M9 is bricked and not sure what to do!

Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
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!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :

PlumpPanda said:
Hello everyone,
My phone boots straight into bootloader and I only have access to bootloader and download mode (no recovery). My phone is S-ON and Re-locked. Unlocking again doesnt seem to work and I get this error message when I try:
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.015s]
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!!)
Any help on how to get S-OFF as well would be awesome!
I cannot find an RUU that matches my phone. My details are:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226065287278
(bootloader) version-main: 2.10.61.6
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: ORANG001
Any help would be greatly appreciated so thank you in advance! :good :
Click to expand...
Click to collapse
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.

shivadow said:
Factory Reset Protection is stopping the unlock. You should have removed your google account before messing with it.
Now you're locked out of your OS which is preventing you from flipping the bootloader unlock switch.
I honestly don't know how to get around that. I'm not sure an ruu flash will help either..
S-off, you need to run an app called "sunshine" and pay $25 or buy an xclip or the likes.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's true that this is a security feature but the google account has nothing to do with it. It's the option "OEM Unlock" in the developer options that seems to be inactive in this case. And yes, a RUU could fix this issue.
@PlumpPanda: That usually happens if the phone gets relocked although it's not completely stock. Security checks notice that the software isn't original (e.g. if TWRP is installed) and prevent the phone from booting so that it doesn't get "damaged" by the "faulty" software. (The software actually isn't faulty in reality but the security checks only distinguish between original software and not-original=faulty software if the bootloader is locked or relocked.) There seems to be no publicly available RUU for your firmware so all you can do is contacting Llabtoofer's RUU service and ask whether he can help you out. (Chances are high that he can.) Sunshine is no alternative since you have no booting system and java cards or xtc clips are way more expensive than the RUU service (unless you have friend that already owns one ).

Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.

shivadow said:
Note the red highlight.. Frp = factory reset protection. If you have seen this error before then ignore me, I'm talking rubbish but as far as I can tell it wouldn't have frp if it was just the unlock killswitch stopping it. Would it?.
It does say that "enable unlock" then rejects it, probably due to the frp?.
Something tells me that this rabbit hole may go deeper if you keep digging but one thing is for sure.. Bye bye data.
Beamed in by telepathy.
Click to expand...
Click to collapse
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
Click to expand...
Click to collapse
If OEM Unlock was disabled the output would be the following:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
Click to expand...
Click to collapse
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?

Flippy498 said:
Yeah, I noticed the part that you highlighted in red. And it is a factory reset protection since it prevents the factory reset that gets triggered by a bootloader unlock. However, it has nothing to do with google accounts and it doesn't prevent you from flashing RUUs. But you're right, since a RUU completely wipes the phone the currently saved data (e.g. contacts, pictures, messages, etc.) is lost.
That error is not new. It exists since the M9 received firmware 2.x. You can't unlock the bootloader unless OEM Unlock is activated in the developer options. The oldest threads which deal with this problem got started around august 2015.
Edit: Wait a minute. I missed that part:
If OEM Unlock was disabled the output would be the following:
@PlumpPanda did you maybe try to use your old unlock token? Can you try to get a new one, please?
Click to expand...
Click to collapse
Yeah I used the 'htcdev' website to get a new unlock code after my old one didn't work and it still doesn't unlock it. Thank you for all your help so far guys :good:
Edit:
@Flippy498 I've just got an email back saying Llabtoofer's RUU service can flash my phone so I'll let you know when all is said and done Thanks!
Phone is now fixed!! I used the Llabtoofer's RUU service and it worked perfectly. Highly recommended as it took roughly half an hour and now it works perfectly!!!! Thanks for you rhlpe guys!

Unlock a blocked M9

Hello,
I apologize if I won't be very precise, but I don't know the history of this phone. It's a friend of mine's phone.
i can boot it just in download mode or bootloader. It stucks on the boot animation.
The information, from download mode, is:
Code:
***LOCKED***
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U114401011_117.00.611176_2
OpenDSP-20.7.3.00535.8994_1012
OS-4.14.401.7
Nov 26 2016,00:36:11(836547)
I've tried
Code:
fastboot oem get_identifier_token
but I got this error:
Code:
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.073s]
finished. total time: 0.073s
because I think the debug mode isn't enabled.
I would want to be able to flash any new firmware, without, if it's possible, flash any Custom ROM.
Is there a way to fix it?
Thank you in advance.

The clue is in the error. Oem unlock isn't enabled. It must be enabled from the os under "settings/developer options/oem unlocking"
It needs to be enabled if you have unlocked or intend to unlock the bootloader.
Beamed in by telepathy.

shivadow said:
The clue is in the error. Oem unlock isn't enabled. It must be enabled from the os under "settings/developer options/oem unlocking"
It needs to be enabled if you have unlocked or intend to unlock the bootloader.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you.
So, there's no way to set "oem unlock" without accessing the os?

.Fè said:
Thank you.
So, there's no way to set "oem unlock" without accessing the os?
Click to expand...
Click to collapse
Correct. But you can try to fix the phone by flashing a RUU. Instructions and downloads are located in the ReadMe thread.

Help with HTC D728H

Hi guys,
My friend's HTC Desire D728H is stuck in a boot loop. I tried the following without success:
- Downloaded the Stock Flash for it (2PQ8IMG_A50CMG_DWG_L51_DESIRE_SENSE70_HTC_Europe_1.09.401.2_Radio_NA_release_482339_signed_2_4.zip) and tried to update from SD card from Download menu, didn't work. Tried flashing it with RB Soft, it gets to just before the end of the progress bar and then the phone reboots into the same boot loop.
There is no fastboot mode in the recovery menu. So I started the phone in download mode. From the command prompt on my Windows PC, typed Fastboot Devices and the PC detects it as LC5C3Z703897.
I cannot enable OEM Unlocking cos the phone won't boot.
I have HTC drivers installed.
adb in command prompt does not detect the phone.
I can boot it in RUU mode.
if I try to get the Token to unlock bootloader, it returns the following error:
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.006s]
finished. total time: 0.007s
As far as I know the phone has a stock rom, bootloader locked with S-ON.
How can I flash this phone and get it working again? I don't have lots of experience with HTC phones, so please provide me with details.
Thank you All in advance.

No one?