Develop Bugs

htc oem unlock not working

i wanted to unlock my htc one m9
i created the unlock code and recieved the Unlock_code.bin from htc - but when I try to flash that one during fastboot to the device I get some strange output:
Code:
sudo ./fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)... OKAY
writing 'unlocktocken'... INFOHOSD CL#493992
FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT unlocktocken)
on the device is written on the bottom the whole time the strange message:
Code:
Security checking failed NOT_FIND_SMART
IO
SD NOT MOUNTED
tried the ubuntu fastboot and the one from the htc site...
after the flashing there is written on the Device:
Code:
End flashing, Press power key to contin
this is the 8th htc device - and I've never had problems like this before...
any ideas?

Mr.Gosh said:
i wanted to unlock my htc one m9
i created the unlock code and recieved the Unlock_code.bin from htc - but when I try to flash that one during fastboot to the device I get some strange output:
Code:
sudo ./fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)... OKAY
writing 'unlocktocken'... INFOHOSD CL#493992
FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT unlocktocken)
on the device is written on the bottom the whole time the strange message:
Code:
Security checking failed NOT_FIND_SMART
IO
SD NOT MOUNTED
tried the ubuntu fastboot and the one from the htc site...
after the flashing there is written on the Device:
Code:
End flashing, Press power key to contin
this is the 8th htc device - and I've never had problems like this before...
any ideas?
Click to expand...
Click to collapse
are you in download mode or on bootloader when you try.you have to be in download mode.

Of course i've been in download mode - in bootloader mode you'll get an "unknown ..."

Mr.Gosh said:
i wanted to unlock my htc one m9
i created the unlock code and recieved the Unlock_code.bin from htc - but when I try to flash that one during fastboot to the device I get some strange output:
Code:
sudo ./fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)... OKAY
writing 'unlocktocken'... INFOHOSD CL#493992
FAILED (remote: 35: SD_PARTITION_NOT_SUPPORT unlocktocken)
on the device is written on the bottom the whole time the strange message:
Code:
Security checking failed NOT_FIND_SMART
IO
SD NOT MOUNTED
tried the ubuntu fastboot and the one from the htc site...
after the flashing there is written on the Device:
Code:
End flashing, Press power key to contin
this is the 8th htc device - and I've never had problems like this before...
any ideas?
Click to expand...
Click to collapse
Could be because of the typo?
I noticed you used the command:
"fastboot flash unlocktocken Unlock_code.bin".
When it should be :
"fastboot flash unlocktoken Unlock_code.bin"
(no c in token )

spikeydoo2006 said:
Could be because of the typo?
I noticed you used the command:
"fastboot flash unlocktocken Unlock_code.bin".
When it should be :
"fastboot flash unlocktoken Unlock_code.bin"
(no c in token )
Click to expand...
Click to collapse
omfg!
thx - how can i be so stupid. THX! - that solved it...
but what about these sd card messages? something to worry about?

You just saved my entire evening! I have been banging my head against the wall trying to figure out why I was getting:
remote: 35: SD_PARTITION_NOT_SUPPORT unlocktoen)
Then I noticed you mentioned spelling and I looked at mine. I had left out the "k" in token -_-
Worked like a charm after.

Cannot flash recovery

OK I have a problem. Till now:
1. Installed drivers
2. Bootloader unlocked
3. ADB enabled. PC authorised.
4. OEM unlocking permitted confirmed.
5. Command fastboot devices shows phone connected in fastboot mode.
EDIT: Solved. Experimented with different drivers on different laptop.
Now trying to send official twrp with command fastboot flash recovery recovery.img and I get error:
sending 'recovery' (18680 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.004s
Can't seem to get a solution to this
Any help?

Bricked Pixel C - No Recovery, No OS & Fastboot Errors

Hi all,
I've seemed to have bricked my Pixel C. I tried flashing the stock ROM after installing LineageOS.
I wiped everything using fastboot (recovery, data, system, bootloader, cache, etc) and now I am just stuck with fastboot.
When I try and use
Code:
fastboot boot twrp.img
, I get the following:
Code:
creating boot image...
creating boot image - 12974080 bytes
Sending 'boot.img' (12670 KB) OKAY [ 0.320s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
I did have this error before, but I had TWRP and used fwtool to fix it. But I have no OS, no recovery and I am getting these issues with fastboot.
I have tried various cables, my drivers are up to date and my software is up to date. I have also tried flashing the stock image from Google but that just does the following:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.445s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
--------------------------------------------
Bootloader Version...: ***********************************************************
Baseband Version.....: N/A
Serial Number........: unknown variable
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.010s]
Checking 'version-bootloader' FAILED
Device version-bootloader is '***********************************************************'.
Update requires 'Google_Smaug.7900.139.0'.
fastboot: error: requirements not met!
Press any key to exit...
Is this tablet totally bricked or can anyone help me out?
Thanks

Vartom said:
I fixed such a lock by flashing a chip with a bootloader. To do this, I had to peel off the screen and buy a programmer on Ali. Risky operation.
Click to expand...
Click to collapse
Hi, can you give more details on how you proceeded

Have you tried this?
https://download.dirtyunicorns.com/?device=dragon
Google smaug vendor image
Gesendet von meinem Nexus 6P mit Tapatalk

Doesn't work. It's not the image that's the issue anyway, its the command being unrecognized:
Code:
Sending 'bootloader' (16384 KB) OKAY [ 0.438s]
Writing 'bootloader' FAILED (remote: 'unsupported command')
fastboot: error: Command failed

Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.

matonka007 said:
Bricked.
I solved same problem but I was able to boot system and used this in adb:
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
You must somehow boot recovery and flash system. Without recovery you are screwed.
Click to expand...
Click to collapse
Yeah. I have been searching for hours but it seems impossible without recovery.

Tried this?
https://forum.xda-developers.com/pixel-c/help/bootloader-reports-unlocked-unable-to-t3483513
Gesendet von meinem Nexus 6P mit Tapatalk
---------- Post added at 06:13 PM ---------- Previous post was at 06:11 PM ----------
And this?
https://forum.xda-developers.com/pixel-c/help/flash-factory-image-t3599367/amp/
Gesendet von meinem Nexus 6P mit Tapatalk

Yes but with no joy.
Fastboot doesn't work at all so I cannot even boot to recovery. Therefore, I am unable to use ADB to fix fastboot

Sad, maybee this?
https://forum.xda-developers.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863
Gesendet von meinem Nexus 6P mit Tapatalk

Doesn't work. But AGAIN... I cannot access recovery for ADB

Sorry no more ideas
Gesendet von meinem Nexus 6P mit Tapatalk

Are you sure that your BL is unlocked? Try to lock it and unlock it again.
Code:
FAILED (remote: 'image verification failed')
This error looks like it can not boot unsigned image. But I do not know why.

Bootloader is definitely unlocked. I have tried locking and unlocking multiple times

JustDarren said:
Hi all,
If I try and flash recovery using
Code:
fastboot flash recovery twrp.img
, I get the following:
Code:
Sending 'recovery' (12668 KB) OKAY [ 0.347s]
Writing 'recovery' FAILED (remote: 'unsupported command')
fastboot: error: Command failed
[/code]
Click to expand...
Click to collapse
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.

TheInitialCommand said:
This is a longshot, but I was getting very similar errors trying to do anything. All this happened on a Windows 10 Laptop using the Google Drivers. I tried it again on a Mac Book Pro running Catalina and it worked just fine with latest platform tools.
Perhaps you want to try a Linux or Mac if you have access to one, or try a Linux live edition on your current machine, something like this:
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started
Just worth a shot. Still an awesome tablet to lose just yet. Hope it is not too late for you.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a go and let you know what happens

Good luck!

TheInitialCommand said:
Good luck!
Click to expand...
Click to collapse
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it ?

JustDarren said:
No joy. Still getting unknown command. Even tried manually erasing and formatting the partitions with no luck. Thanks for the suggestion though.
Really bummed out because I still love this tablet. Shame I bricked it
Click to expand...
Click to collapse
I have similar problem ..
you need to extract the rom zip file, inside you have img files ...
a) you need tablet in fastboot mode . i have made the process in linux. also i have downloaded this rom
ryu-opm8.190605.005-factory-25b457f3.zip downloaded from google.
b) Tablet needs to be unlocked .. for that you need to do fastboot oem unlock .. and after you return to fastboot mode.
And here you have my steps ..
All made in linux but if you use windows remove the command "sudo" it ahould work
1) sudo fastboot flash bootloader bootloader-dragon-google_smaug.7900.139.0.img
2) sudo fastboot reboot bootloader
3) sudo fastboot flash boot boot.img
4) sudo fastboot flash cache cache.img
5) sudo fastboot flash recovery recovery.img
6) sudo fastboot flash system system.img
7) sudo fastboot flash vendor vendor.img
8) restart the tabler pressing button.
Check if these works for you ..
bye

Thanks for your reply but as o have said many times, fastboot is unresponsive and returns "Command not found". This isn't an error on my part with inputting the commands but I think moreso, corrupt storage

Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.

rhmanoa said:
Did you try to use fusée gelée like on the nintendo switch, i think it will may solve your problem.
Click to expand...
Click to collapse
I don't think that will work. Unless you have a guide for using it on android devices other than the switch.

fastboot problems?

edit3: managed to flash orangefox back(MTP now works in recovery) i should be able to flash a stock rom now
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
edit: i don't have access to an intel machine nor an usb hub(i have a ryzen cpu)
edit2: for some reason i have 3 different errors i can get
Code:
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
C:\adb>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (47472 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1.911s

You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it

SunilSuni said:
You haven't downloaded proper fastboot file..
What's your device name ?? Does it have dual camera ? If so it is redmi note 5 pro or redmi note 5 global codenamed whyred
If your phone has single camera then it is Redmi 5 plus global or Redmi Note 5 india codenamed Vince
Download proper package and flash it
Click to expand...
Click to collapse
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp

ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
ijheaven said:
im sure i have whyred because i have flashed some whyred roms before and they worked
also i have whyred twrp
Click to expand...
Click to collapse
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz

SunilSuni said:
Check the error message, it's says -- mismatch image and device
Download latest fastboot image for whyred from below link
https://bigota.d.miui.com/V11.0.3.0...XM_20191108.0000.00_9.0_global_f128798d03.tgz
Click to expand...
Click to collapse
that's the file i downloaded and tried

ijheaven said:
recently tried to upgrade my rom to lineage 17.1 when doing that i accidentally wiped everything(including os)
i have the newest official twrp installed so i thought i could sideload the stock rom but when i tried that turns out sideloading is not working for some reason(stuck at "Starting ADB Sideload feature..." and after about 10 minutes it fails)
then i tried flashing the stock rom with fastboot but any command i try disconnects my phone from my pc("press any key to shutdown" also appears in the top left corner of my phone)
also when i tried following this guide h t t p s://c.mi.com/oc/miuidownload/detail?guide=2
i get this error in the flash tool:
Code:
$fastboot -s 5ed0da1f getvar product 2>&1 I findstr /r /c:"`product: •whyred" II echo Missmatching image and device
Click to expand...
Click to collapse
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem

Sidgup1998 said:
Which platform are u using to flash.Is it Amd/intel
If it's amd then amd breaks support for fastboot as i also have amd ryzen 2500u and whenever i flash the same i get the same errror.
Buying USB hub solved the problem
Click to expand...
Click to collapse
i'll try that thanks!

or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.

gursewak.10 said:
or you can try this
flash twrp or orangefox recovery with fastboot and boot into it
then get recovery rom zip and flash that zip using recovery
link is here if you need it.
Click to expand...
Click to collapse
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s

ijheaven said:
i have tried this already but i can't flash/boot with fastboot
Code:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (47472 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
and im also getting this error
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
Click to expand...
Click to collapse
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly

gursewak.10 said:
try changing fastboot+adb files
and try this command fastboot getvar all
check if bootloader is unlocked properly
Click to expand...
Click to collapse
bootloader is unlocked and reinstalled adb still no luck

ijheaven said:
bootloader is unlocked and reinstalled adb still no luck
Click to expand...
Click to collapse
Its working , but khmmm use miui flash tool... stop using adb, becouse you don't know what are you doing..You gonna brick it and than you'll cry again.??
Tip: dummy file. ?
Good luck.
Sent from XDA Labs

TWRP failed install on 3a XL Android 9

I have been trying and failing to get TWRP installed on my Pixel 3a XL running Android 9 stock image
Trying the recommended install instructions from the TWRP website, I keep getting the following error;
Code:
C:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\platform-tools>fastboot recovery twrp.img
fastboot: usage: unknown command recovery
C:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
I have ensured the bootloader is unlocked, I have updated drivers from the OEM package, I can see devices properly with fastboot and adb, and I've even flashed stock images with fastboot. I've tried looking up this error, but all results point to solutions that don't work, or deleted posts. If anyone has some insight, I'd very much appreciate it.

Update to the latest version of Android or try an older version of TWRP. The latest version of TWRP doesn't like Android 9 (possibly other versions as well).

I believe this was the last update for twrp on android 9
Download twrp-installer-3.5.2_9-0-bonito.zip
Download page for twrp-installer-3.5.2_9-0-bonito.zip
dl.twrp.me