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?
Related
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.
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
Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
coolcoder001 said:
Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
Click to expand...
Click to collapse
R u able to use twrp???
Error: fastboot oem unlock on SHIELD TV 2017 (16GB) with Nvidia OS 7.2.1 (Dev & Rec)
I have a SHIELD TV 2017 (16GB, remote only) device that currently has Nvidia's Developer OS 7.2.1 installed. The same error occurs with the Factory (OS installed on device originally) and Recovery OS installation.
After gaining access to the device through ADB, when I enter the command fastoob oem unlock I receive the following error. It's unclear why this error occurs since there isn't any other information made available.
fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
FAILED ()
Finished. Total time: 113.891s
Has anyone else experienced this as well? Is it something to be concerned about? Does anyone know why this failure is occurring?
Edit: The ADB software package I found and installed is "15 seconds ADB Installer 2.0" which I installed on Windows 10 Pro. I don't know if this may have something to do with it.
nadia p. said:
I have a SHIELD TV 2017 (16GB, remote only) device that currently has Nvidia's Developer OS 7.2.1 installed. The same error occurs with the Factory (OS installed on device originally) and Recovery OS installation.
After gaining access to the device through ADB, when I enter the command fastoob oem unlock I receive the following error. It's unclear why this error occurs since there isn't any other information made available.
fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
FAILED ()
Finished. Total time: 113.891s
Has anyone else experienced this as well? Is it something to be concerned about? Does anyone know why this failure is occurring?
Edit: The ADB software package I found and installed is "15 seconds ADB Installer 2.0" which I installed on Windows 10 Pro. I don't know if this may have something to do with it.
Click to expand...
Click to collapse
I am in the process of trying to root my 2017 Nvidia shield myself and having difficulty flashing the modified boot image while in fastboot (after unlocking) so if you can shed some light on that issue I'd appreciate it.
For yours my suggestion is to ADB reboot bootloader and plug a keyboard in then navigate to unlock bootloader from the menu.
This is how I did mine.
[SOLVED] Use Minimal ADB & Fastboot 1.4.1 tools or later.
I have resolve this issue, another member here was kind enough to point me to another ADB software named Minimal ADB & Fastboot 1.4.1.
Using Minimal ADB & Fastboot 1.4.1 instead of 15 seconds ADB Installer 2.0 resolved the failure issue.
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader...
(bootloader) Bootloader is unlocked now.
OKAY [ 48.891s]
finished. total time: 48.891s
fastboot oem lock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Locking bootloader...
(bootloader) Bootloader is locked now.
OKAY [ 53.344s]
finished. total time: 53.344s
Having the proper tool(s) for the job is always key.
sconnyuk said:
I am in the process of trying to root my 2017 Nvidia shield myself and having difficulty flashing the modified boot image while in fastboot (after unlocking) so if you can shed some light on that issue I'd appreciate it.
For yours my suggestion is to ADB reboot bootloader and plug a keyboard in then navigate to unlock bootloader from the menu.
This is how I did mine.
Click to expand...
Click to collapse
Hello sconnyuk, I attempted to use the OS menu option "Unlock Bootloader" that appears on the screen of the Shield TV after executing adb reboot bootloader from the Command Prompt (Administrator) window. It's unclear to me that this method works. From what I have attempted and experienced so far is it does not (lock or unlock) the bootloader.
I believe it doesn't execute the same "oem" command which is why, although this is only my speculation.
I feel the the reason so many senior members here advise us to use the ADB & Fastboot tools is because it works.
nadia p. said:
Hello sconnyuk, I attempted to use the OS menu option "Unlock Bootloader" that appears on the screen of the Shield TV after executing adb reboot bootloader from the Command Prompt (Administrator) window. It's unclear to me that this method works. From what I have attempted and experienced so far is it does not (lock or unlock) the bootloader.
I believe it doesn't execute the same "oem" command which is why, although this is only my speculation.
I feel the the reason so many senior members here advise us to use the ADB & Fastboot tools is because it works.
Click to expand...
Click to collapse
Yes I can confirm now the menu lock and unlock do work, I've just finished flashing my modified boot.img after unlocking the bootloader this way.
?
Hey,
After a series of mess ups on my HTC-10, i am now stuck in bootloader mode, S-on with relocked. When i try to unlock my bootloader using flash unlocktoken, i get this:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I cant boot into the system so cant toggle oem unlocking. I was running LOS (9.0). any solutions?
Edit: if i try to flash anything from download mode, i get: "9 RU_Security_Fail zip from usb command in download mode"
Khizar Amin said:
Hey,
After a series of mess ups on my HTC-10, i am now stuck in bootloader mode, S-on with relocked. When i try to unlock my bootloader using flash unlocktoken, i get this:
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I cant boot into the system so cant toggle oem unlocking. I was running LOS (9.0). any solutions?
Edit: if i try to flash anything from download mode, i get: "9 RU_Security_Fail zip from usb command in download mode"
Click to expand...
Click to collapse
Why didn't you answer me here
https://forum.xda-developers.com/ht...atch-error-t3894789/post78787393#post78787393
I tried to help you there but instead you wandered off and got yourself in a really bad situation. S-on and relocked......for heaven's sake why did you relock it, that's the dumbest thing ever and a 100% not needed for anything !!!
Maybe you can put your device back to stock if you find a ruu.exe that matches your original OS and firmware, but since you didn't followed my directions i have no clue where to start and frankly i am afraid you can't fix this anymore.