Related
I've been trying to resurrect a Moto G recently, which is stuck in fastboot with the error "failed to validate boot image".
I tried flashing stock firmware using mfastboot, but when flashing the partition, I get the errors:
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Is there anything else I should try, or is the phone bricked?
I have the same problem, i unlock oem my moto g3 2015 and flashed it directly without renable the oem unlock in developper menu.
i'm stuck to bootloader in secure flashing mode now.
have someone a solution
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work
GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i
GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.
meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.
meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?
I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/
Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )
Go to an independent repair shop. They have the equipment to flash on the motherboard.
Dear people,
First of all, although dilligent and trying to do my homework, I am a total newbie regarding anything Android. Therefore, if I am posting on the wrong section of the site, please let me know and I will try my best to fix it.
That being said, I have a Moto G3 (Moto G 2015), model XT1543 (osprey), that is stuck in the fastboot boot. I have searched a lot of the web trying to find solutions and, after having failed all of them, decided to come here for assistance.
My device only boots and displays:
AP Fastboot Flash Mode (Secure)
version downgrade for recovery
failed to validate recovery image
ERROR: Failed to pass verification, backup to fastboot
Fastboot Reason: Fall-through from recovery boot mode
I already downloaded the appropriate TWRP recovery image for the device (osprey), but the bootloader is locked and, since I can't get into the system properly, I can't switch the "Unlock OEM boot" flag when the full system is running.
In particular, when I try to flash TWRP, this is what I get:
# fastboot flash recovery twrp-3.1.0-1-osprey.img
target reported max download size of 268435456 bytes
sending 'recovery' (7546 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.454s
Indeed, since I am only in fastboot mode, I went away and requested a boot unlock code from Motorola and trying to unlock the bootloader and this is what I get:
# fastboot oem unlock <my-code-here>
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.034s
I already tried looking at similar questions in many, many forums and no answer actually applied to my device (including, for example, https://forum.xda-developers.com/2015-moto-g/help/moto-g3-struck-fastboot-screen-t3542147 and even others for other models and vendors).
Thanks in advance for any help.
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Sent from my MotoG3 using Tapatalk
riggerman0421 said:
At this point your only option to flash the same or newer factory image through fastboot. The is no way to unlock the bootloader without the OEM unlock in developer options checked, and with a locked bootloader you can't flash an older version. See the thread on flashing factory images.
Click to expand...
Click to collapse
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
rtbrito said:
OK. So, now, I know how to direct my energies and avoid useless efforts.
Thank you so very much, @riggerman0421. Now, to find which factory image was the one that was installed on this device (it is actually my father's device).
Click to expand...
Click to collapse
You can follow the guide here. Try it with the latest firmware available here.
Broadcasted from Zeta Reticuli
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
mackenzie121 said:
Hello All,
Please can someone help, I successfully rooted my htc u11 and put a custom rom on to phone . I decided to go back to stock and restore my phone as new. I had unlocked and locked my bootloader all ok.
Now I have the problems, my phone cant seem to unlock bootloader, everytime I try and fastboot recovery or roms. I get this message 9 ru security fail recovery and bootloader isn't bl-unlocke.
Im stuck ,plus when I boot the phone I get the message, your phone is not to be trusted . Please can anyone help.
Click to expand...
Click to collapse
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
paulpier007 said:
Hi, let's see if there's any chance...
Enter the download mode and connect it to the PC then type fastboot devices to make it recognize.
If you recognize it, try typing fastboot oem get_identifier_token and see what happens...
Click to expand...
Click to collapse
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
mackenzie121 said:
yeah fastboot devices sees it and recongnizes it biut when I do oem get identifier I get
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.012s]
finished. total time: 0.012s
Click to expand...
Click to collapse
Did you try running a RUU
thicklizard said:
Did you try running a RUU
Click to expand...
Click to collapse
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
You can find RUU files here(in thread search):
https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048
mackenzie121 said:
as in putting the rom on memory card and booting into download mode? and pressing up on the volume. yes I have tried many , but they all say mismatch. Unless im doing something wrong?
cant seem to find the right RUU.
this is what I have on my phone
****relocked***
***production***
htc_ocnuhl pvt s-on
LK-1.0.0.0000
radio-8998-002772tov-1802241313
openDSP-v11.6.00.347.cb8998_0711
os - 2.33.206.9
Click to expand...
Click to collapse
i had same problem,
start unlocking your bootloader on htcdev website and take new token: (fastboot oem get_identifier_token) until you save NEW "Unlock_code.bin” in fastboot directory then : (fastboot flash unlocktoken Unlock_code.bin)
just start all from the beginning and everything should go right
Or
copy RUU to your external sd card and rename to 2PZCIMG (leave the .zip extension untouched); reboot to download mode and it will ask you (in yellow) to choose UP to start the RUU flash (previously copied to the External SD card) or DOWN to cancel flash and make a normal boot.
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
Install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Hmmm ill help you with your answer if u can get help for me with mine
Zaq1xsw222 said:
Hmmm ill help you with your answer if u can get help for me with mine
Click to expand...
Click to collapse
So help me and give me your answer, let me see if i can help you
CheckS86 said:
So help me and give me your answer, let me see if i can help you
Click to expand...
Click to collapse
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Zaq1xsw222 said:
Ok so you was saying you need a command right to type into linux shell. But hold on did you put a custom rom onto the phone yourself
Also, if your phone randomly stopped working by its self, our issues may be related........
Click to expand...
Click to collapse
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
CheckS86 said:
No, i dont flash nothing in this phone, it just stopped working by itself.
I have a Windows 10 pc and i only can use some fastboot commands, so, i already tried various commands but my outdated recovery only letme run some of them!
Click to expand...
Click to collapse
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Zaq1xsw222 said:
What was the last thing you done on your phone?
The last setting you changed?
Have you tried turning the phone on with the battery out?
Click to expand...
Click to collapse
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
CheckS86 said:
I was playing or using whatsapp maybe, and yes, i tried that, but never start (because of the volt needed), only the LED is on
Click to expand...
Click to collapse
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Ok now its your turn
Zaq1xsw222 said:
Here u go.
Hard Reset HTC Desire 10 Pro, how to - HardReset.info
www.hardreset.info
Click to expand...
Click to collapse
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
CheckS86 said:
The phone make exatly the same, after set the HTC logo the screen and LED turn down (like an animation when lock your screen), i dont know why, but making this led mi to the begining :/
(tell me your question btw)
Click to expand...
Click to collapse
Have you tried to restart your phone in safety mode?
Zaq1xsw222 said:
Have you tried to restart your phone in safety mode?
Click to expand...
Click to collapse
It doesn't work, this just led me to de begining too.
The phone can't start, so maybe re-install his firmware is the best option. I already search the firmware for this phone (to try flash it with SP Flashtool), even here in XDA there is an RUU Collection for this phone, but none of them is compatible with mine. This is the firmware compatible:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip
but is only available to buy... here for example:
2PYAIMG_A56DJ_PRO_DTWL_M60_SENSE80GP_HTC_India_SEA_1.18.400.22_Radio_0.A56DJPV1P32.7900.0216.A56T_release_508642_combined_signed_2_4.zip | Easy Firmware
easy-firmware.com
IDK why this firmware is not in other pages .
Reinstall stock firmware so you can boot into system. Then follow instructions to unlock with unlock code