[HELP] Unlock Android bootloader without OEM Unlock (Phone doesn't start)

[HELP] Unlock Android bootloader without OEM Unlock (Phone doesn't start) - General Questions and Answers

¡ 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

Related

fastboot bricked my device and it's not fixing it back

hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
If you are developing a kernel, you may find it helpful to delete your boot.img and recovery.img to force booting into fastboot:
fastboot erase boot
fastboot erase recovery
You can then manually boot from your custom kernel and a ramdisk:
fastboot boot <kernel> <ramdisk>
Once you have a working kernel and ramdisk, you can automagically combine them within fastboot:
fastboot flash:raw boot <kernel> <ramdisk>
Click to expand...
Click to collapse
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.

y2012 said:
hello.
I tried to test a custom kernel today. So I followed the advice in cyanogenmod's wiki:
The erase steps worked happily! But when I reached the boot step:
Code:
% fastboot boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
creating boot image...
creating boot image - 5416960 bytes
downloading boot.img...
OKAY [ 1.688s]
booting...
FAILED (remote: ()
finished. total time: 1.689s
And now, no matter what I try, I get:
Code:
Unrecoverable bootloader error <0x00000000>.
Flashing the previous (working) boot.img or recovery-jb-touch.img does not work. After finishing what appears to be a successful flash, the device gets unidentified for some reason. So I can't `fastboot reboot`.
Here is the full output:
Code:
% fastboot devices
015d262e983c120f fastboot
% fastboot flash recovery ../recovery-jb-touch.img
sending recovery (6942 KB)...
OKAY [ 1.961s]
writing recovery...
OKAY [ 3.136s]
finished. total time: 5.098s
% fastboot devices
???????????? fastboot
So every time I flash, I have to manually restart to the bootloader. And hence nothing gets fixed, I'm back to square one.
I understand that unlocking voids the warranty. But I expected the extra functionality to actually work if I follow the correct procedure. I didn't expect things to blow up in my face. The fact that I live overseas and there is probably no Asus tech support around here adds an insult to my injury.
I really hope there is a way to fix this.
Click to expand...
Click to collapse
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking! I suggest to flash back to full stock firmware then start over.

buhohitr said:
You need to flash the correct kernel and such for the tf700, don't flash anything available out there, you are asking for bricking!
Click to expand...
Click to collapse
It was a CM10 kernel I compiled myself.
buhohitr said:
I suggest to flash back to full stock firmware then start over.
Click to expand...
Click to collapse
Explaining how this can be done from fastboot would be great. Especially when I can't even make recovery work.

Try flashing NVidia blobs instead of raw images ... AFAIK the TF700 bootloader's fastboot implementation only understands blobs.

You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz

ostar2 said:
You also forget the usb ID. Try this
Code:
fastboot -i 0x0B05 boot boot_old.img-kernel.gz boot_old.img-ramdisk.cpio.gz
Click to expand...
Click to collapse
I tried with and without the ID.
Is it really damaging if the ID is not included?

y2012 said:
I tried with and without the ID.
Is it really damaging if the ID is not included?
Click to expand...
Click to collapse
No. There were just some bootloader versions which never showed a serial number, just question marks, when issuing "fastboot devices", and then you needed to specify the ID to get anything to work.
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.

_that said:
The fastboot implementation in the TF700 is a bit strange. I also could not get "fastboot boot ..." to work, but I never erased my boot and recovery partitions. Just flashing blobs worked fine.
Click to expand...
Click to collapse
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?

For reference:
Code:
% fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 015d262e983c120f
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.082s

y2012 said:
Can you elaborate on flashing blobs?
What blobs should I flash and where/how can I obtain them?
Click to expand...
Click to collapse
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
y2012 said:
For reference:
Code:
% fastboot getvar all
...
Click to expand...
Click to collapse
I am getting the same output on mine, the only differences are the serial number (greetings from Captain Obvious) and the size of the userdata partition (I have a 64 GB tablet).

_that said:
TF700 fastboot likes to flash blobs that start with a "-SIGNED-BY-SIGNBLOB-" header, followed by an "MSM-RADIO-UPDATE" header.
Try flashing the TWRP recovery from here (see "Fastboot method"): http://www.teamw.in/project/twrp2/105
Click to expand...
Click to collapse
Flashing TWRP didn't work.
I think I'm giving up on this.

y2012 said:
Flashing TWRP didn't work.
Click to expand...
Click to collapse
Details?

Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
guess Im not the only one who has this problem now we need solutions
Edit: I just remembered I had plan to use Ubuntu to write recovery image see if you can flash ubuntu as the files are on SD rather then on tablet
also skythra had a similar problem he/she said that the fastboot unlocker for jellybean you cannot write you can only read and boot
I also want to ask you have a 64 GB as well?

_that said:
Details?
Click to expand...
Click to collapse
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.

4SHR4F said:
Ive started the same thread erased the recovery it says it writed recovery image but i think the tablet freezes as any command after writing recovery will not work but before that it will an example:
try adb reboot the tablet will reboot
but after writing the recovery image try entering that command and see what happens
Click to expand...
Click to collapse
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
guess Im not the only one who has this problem now we need solutions
Click to expand...
Click to collapse
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
I also want to ask you have a 64 GB as well?
Click to expand...
Click to collapse
No. 32GB here.

y2012 said:
Assuming you meant fastboot not adb. This is true. The device gets unidentified (see `fastboot devices` output). Whether the freeze is caused by the unidentified device, or both symptoms are caused by something else, I don't know.
Well, Asus will not help. They provide half-assed unlocking feature, broken fastboot, and void your warranty in the process. Way to go winning developers and advanced users!
No. 32GB here.
Click to expand...
Click to collapse
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat

4SHR4F said:
Let me know what happens someone suggested downgrading to ICS then use debugfs and then use custom rom root and terminal to send the recovery that way either way my computers PCI card decided to stop working so I have to tether it and then download the tools which is a problemsince I formatted my whole computer to get this transformer workin best of luck but like I said please post ur method cause im in the same boat
Click to expand...
Click to collapse
Bump any solutions cant use flash or boot so cant do anything could someone send us bootlocker tool or something i dont know please help

y2012 said:
Same as the OP. Flashing looked like it succeeded. The device gets unidentified in fastboot after that. Manual restart. And choosing recovery shows the same error.
It looks like the only options left are:
1] fastboot flash -- I don't know where to get an update.zip that works with this.
2] fastboot flashall -- I don't know how this command works as it doesn't take any arguments.
Click to expand...
Click to collapse
fastboot -b flashall
-b (specify a custom kernel base address)
in the same boat

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

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

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.

Bootloader & download mode not working!

Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off

SpeziesTR said:
Hi everyone,
I hope someone can. Help. Unfortunately I flashed a bad firmware and therefore have the problem, that download mode doesn't work (power button + vol down --> gets to the dark screen with htc logo but then goes completely off) AND bootloader also doesn't work (power + vol up --> gets to white screen with green HTC logo but also goes completely off)! Any chance to get my A9 back to life? Any ideas? Thanks!
Original cid/mid
cid: HTC__034
mid: 2PQ910000
Now on super cid, s-off
Click to expand...
Click to collapse
You flash which version of firmware? A9 original version of what? now you can into bootloader mode?

Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...

SpeziesTR said:
Hi thanks for answering. I flashed 1.57.617.20 firmware, but saw too late thats not for my model...
I cannot enter bootloader. When I press Power + Vol up, white screen and green HTC logo shows for 1-2 seconds and then the phone turns off completely...
Click to expand...
Click to collapse
When you at the "dark screen with htc logo" . enter cmd command "fastboot reboot-bootloader" can you into bootloader mode?

Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...

SpeziesTR said:
Hi, the dark screen is also only there for 1-2 seconds, then device turns off again...
Click to expand...
Click to collapse
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Now unable into bootloader mode is the biggest problem.

@ nenebear: Thanks for your help so far!
Has anyone else a clue how to start into bootloader?

i have almost the same problem. my screen is black all the way but all the buttons work and i can hear it boot but the screen does not turn on

I managed to get into bootloader and from there into recovery. I had to press vol up + vol down + power so the device would boot into bootloader. Very strange as this is not the normal combination. I restored my previous image, it will boot but is somehow slow and sluggish.
Nevertheless I did flash
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
but I'm still not able to go to download mode. Furthermore beeing in bootloader reading basic information is not possible. For example:
...\HTC One A9\mini-sdk>fastboot devices
HT******** fastboot
...\HTC One A9\mini-sdk>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: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT********
all:
finished. total time: 0.080s
...\HTC One A9\mini-sdk>fastboot oem readcid
...
FAILED (remote: unknown command)
finished. total time: 0.004s
...\HTC One A9\mini-sdk>fastboot oem readmid
...
FAILED (remote: unknown command)
finished. total time: 0.011s
Anyone a clue how to fix my A9 completely?

Hi,
i just tried to flash system.img (which I decrypted from 1.56.401.70 ROM.zip) but unfortunately got the following error.
Code:
fastboot flash system system.img
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
htc_fastboot finished. total time: 134.464s
Flashing Boot.img, aboot.img etc. is working....
Has someone a clue?

I fixed the problem. I flashed firmware and rom from 1.27.401.5. After that download mode was working again and I could flash 1.56.401.70 without a problem.
Now I'm on Icanas ROM and my A9 is working better than ever...

I did the same flashed a bad firmware. I can access bootloader but not download mode. I have restored a backup I had in twrp so I am running a rooted stock rom but I still can't update my phone thru RUU or Download mode. I have tried flashing the 2p9qimg ( firmware img/ zip ) thru fastboot thru bootloader but no go. All I want to do is flash the correct file so I can access download mode
S-Off
At&T converted to Unlocked
CID & MID changed

nenebear said:
You need to flash 1.56.401.70 of aboot_signed.img & hosd_signed.img.but this must be in bootloader mode .
A9_1.56.401.70.rar
HTC SYNC adb tools
Code:
fastboot flash aboot aboot_signed.img
fastboot flash hosd hosd_signed.img
fastboot reboot
Click to expand...
Click to collapse
which img files do I need to flash if I'm on 1.12.617.6 S- off US Unlocked converted from S-On At&t. I can't get into download mode, it turns off after the HTC logo with black background. Bootloader, recovery and my phone work though.
Nevermind figured it out! =)

Good day guys,
This is my first post in xda, and i'm a little bit nervous. and please bear with my english and i am a noob to some terms too. anyway, my unit is htc one a9. it was sent to me by my brother here in philippines. it is a sprint htc and i think it is a cdma with a sim slot and memory on the side. after reading some of your topics in some forums, i manage to unlock the the network. i can make outgoing and incoming calls and sms. but GPRS is disconnected. i then found another topic by jianC on how to Convert Sprint/Boost HTC One A9 to Dev Unlock. for it says that it can solve No mobile data (but have voice/sms) on sprint firmware after sim unlock. i followed the instructions but unfortunately it brick my phone. i flashed the 2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip, to my phone. My old firmware was 2PQ9IMG_HIA_AERO[email protected]51002_15.00_F_CNV_CNV_HIAE_SPCS_1.15_003_release_453002_signed.zip. Now my problem is that i can get in to bootloader mode by pressing power+vol up+vol down together which is awkward.......but i cannot get in to download mode and recovery mode. the phone can still display the htc logo but 15 seconds later it shutsdown. i tried your advice to type fastboot erase system but it says FAILED<remote:device is locked. cannot erase. But my phone is Bootloader Unlocked and S-Off from sunshine. CID/MID (SPCS_001/2PQ93000) before. I change it to (11111111/2PQ912000) after. Then i tried to flash. I really don't know where to start until i found this forum. I hope somebody could help me in this problem i have.
Thanks and sincerely yours,
kramned

Cannot run "fastboot boot img" successfully.

I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Here is the output of fastboot getvar all:
boot-mode:FASTBOOT
unlocked:yes
off-mode-charge:0
charger-screen-enabled:0
battery-soc-ok:yes
battery-voltage:3911
version-baseband:
version-bootloader:
variant:MSM UFS
partition-type:cache:ext4
partition-size:cache: 0xE000000
partition-type:userdata:ext4
partition-size:userdata: 0x1C3C800000
partition-type:system:ext4
partition-size:system: 0x101000000
secure:yes
serialno: *removed*
product:HTC_Phone
max-download-size:536870912
kernel:uefi
Click to expand...
Click to collapse
Any clue on what is happening?

Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.

Prot02018 said:
Exactly the same is happening for me when I just try and boot it rather than flash it. I'm on the Chinese variant of the phone with Chinese firmware. I get exactly the same message on adb (successfully booted) but just a black screen on the phone.
Click to expand...
Click to collapse
How did you do ? rebooting is not as simple as we think ,

afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp

DeeZZ_NuuZZ said:
afaik, fastboot boot does not work anymore on recent HTC devices , so you have to flash it in order to boot into twrp
Click to expand...
Click to collapse
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?

Prot02018 said:
Oh, well that makes sense! Thanks.
Does anybody know if RUU.zips contain the stock recovery too? As well as everything else needed to get the phone back to stock?
Click to expand...
Click to collapse
A ruu contains everything
Sent from my HTC 10 using XDA Labs

aurelienlux said:
I've tried everything, Windows and Mac, standalone adb and fastboot as well as full SDK version, different USB ports, and I'm at a loss on what to do.
I got a Hong Kong version U11+ (CID: HTC_622, Asia-HK-CHT)
Whatever I do every time I try to boot via the fastboot boot command in bootloader mode it seems to work at first and then nothing, just a black screen.
The terminal output seems to indicate all went well and yet that's not the case:
Here is the output of fastboot getvar all:
Any clue on what is happening?
Click to expand...
Click to collapse
Hi. I have the same phone but my max download size is 2399200000. Is there any reason why yours is lots higher than mine? I tried flashing a RUU and I keep getting messages saying file size larger than device limit. Is there a way we can change this max download limit? Thanks.

bricked htcu11 i think, please help !!!

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.

Database Info

welcome