Q&A for [DEV] Bootloader unlock procedure and software
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV] Bootloader unlock procedure and software. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No unlock partition on KFSOWI
I tried to flash the unlock image on my KFSOWI.
This is the result:
target reported max download size of 1005584384 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.006s]
writing 'unlock'...
FAILED (remote: partition does not exist)
finished. total time: 0.011s
I know this is the HDX forum - but perhaps you can help me out nevertheless
About Windows
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
pablo1036 said:
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
Click to expand...
Click to collapse
Yes
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
murso74 said:
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
Click to expand...
Click to collapse
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
i actually did get it working... removed the device from the manager, unplugged and plugged it back it (showed up as fastboot device with the exclamation point) manually added the driver, using existing windows drivers, and used the adb driver for the fastboot driver.
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
I successfully unlocked my bootloader from Win 8.1 x64 using the method outlined here but not without some challenges. Like others I could not get my device to communicate at the fastboot prompt. Adb worked fine. Assuming it was driver related I deleted everything (included hidden devices), rebooted both devices multiple times and tried various adb/fastboot driver combinations and connection sequences. Nothing. My device knew when the USB cable was connected as evidenced by the 'ready' prompt but was otherwise unresponsive. Even tried a fastboot cable which of course didn't work. Then I tried rebooting into TWRP using power+volume-up+volume-down (three button salute) and from there rebooted the bootloader. Bingo! Everything has worked since. I restarted from TWRP many times as well via adb reboot. Hard to believe the three button salute did the trick but have no other explanation at this time. Maybe Murphy got distracted. Maybe I just got lucky.
murso74 said:
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
Click to expand...
Click to collapse
As you probably discovered deleting the entry under "Android Devices" (can retain the driver) and then replugging your fully booted device restores the MTP driver and associated explorer mapping.
Hopefully this post will help others.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
Gonna try this. got ubuntu on a usb. now got to find the linux commands.
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
holeshot77 said:
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
Click to expand...
Click to collapse
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
jeryll said:
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
Click to expand...
Click to collapse
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
holeshot77 said:
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
Click to expand...
Click to collapse
Yes, go for it! I suppose you have all prerequisites done and you have your signed unlock img ready, then all you need is working fastboot... :good: :highfive:
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
davekaz said:
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
Click to expand...
Click to collapse
If you are doing this in windows try open cmd, make sure you have working fastboot, then type
Code:
fastboot -i 0x1949 flash unlock
open explorer, find location of your xxxxxxxxxxx.unlock file and drag and drop it to cmd, then it should look like this
Code:
fastboot -i 0x1949 flash unlock path_to_your_xxxxxxxxxxx.unlock
then press enter and it should unlock (if the error is based on non defined path to your xxxxxxxxxxx.unlock file)
Working now I must of not spaced it correctly... I tried it again and unlocked ..green is beautiful
Sent from my Kindle Fire HDX using Tapatalk
syntax error
hey guys, i got a stupid syntax error... im doing everything exactly as it says in this thread http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
any way this is what i get:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\FBI>C:\Python27\python.exe
Python 2.7.9 (default, Dec 10 2014, 12:24:55) [MSC v.1500 32 bit (Intel)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>> cuberhdx.py 0x*********
File "<stdin>", line 1
cuberhdx.py 0x*********
^
SyntaxError: invalid syntax
>>>
Click to expand...
Click to collapse
iv tried uppercase, lowercase, moving periods around, and various other things, but still no cigar. any help is appreciated
I think the syntax error is that the script is looking for your devices codes. Try the easy scripts from the regular dev section if you are on Windows. They are much simpler.
Sent from my KFTHWI using Tapatalk
Related
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse
This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
eriknors said:
The title pretty much says it all. I have tried every single method on this site to get my computer to recognize my phone while in fastboot mode with no luck. It works in adb mode just fine I can even reboot to boot loader but once it gets there I get "device enumeration failure" or "device not recognized" when I was on the 1.57 hboot it worked just fine so it has to be something with the 1.39 eng hboot but what I'm not sure. If anyone could help or if anyone else has this problem maybe we could help each other in fixing this cause my only other option is downgrading to win7 which I'm not sure I'll be able to do.
Click to expand...
Click to collapse
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
dottat said:
Check to make sure that Windows installed the correct driver in device manager. Also, in bootloader adb doesn't work. Only fastboot and only on the fastboot USB side of bootloader.
Click to expand...
Click to collapse
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
eriknors said:
Windows installed the correct drivers or I should say I installed the correct drivers. Depending on if I plug into a USB 3.0 or a USB 2.0 port is when my computer tells me whether or not I have "device enumeration failure".
Plugged into USB 3.0 in device manager shows "HTC MTP device" but with a yellow triangle on it obviously meaning the driver needs to be updated or is incorrect, but when trying to update it I'm given "windows has installed the correct drivers already" which in fact by checking it manually it has. HTC driver 2.07xx
Plugged into USB 2.0 gives me "device enumeration failure" and doesn't find any HTC MTP device.
Mind u this is while in fastboot mode not in ADB mode. I'm well aware of the difference between the 2. And fwiw ADB mode works flawlessly while fully booted and in recovery. It's only fastboot mode my computer will not recognize.
Click to expand...
Click to collapse
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
Unzip and try this fastboot/adb.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
eriknors said:
As soon as I get home I will. Quick question where should I install it? Meaning should I install it directly to the C:/ drive? or should I make a sub folder? Or does it matter?
Click to expand...
Click to collapse
Not an install. Unzip and run cmd prompt from there. Note that your fastboot commands will start HTC_fastboot
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
eriknors said:
Ok sorry if I sound lame but I want to make sure I get this right. So unzip the file, open a cmd prompt window from where I unzipped the file correct (eg: C:/downloads/HTC_fastboot/ ) then from there see type in fastboot devices?
Click to expand...
Click to collapse
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Got it
dottat said:
Once you extract it simply browse to the new folder, hold shift key and right click. Select open cmd prompt here.
Click to expand...
Click to collapse
No dice. ADB worked just fine but still no fastboot
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Uzephi said:
Are you typing in "fastboot" or "HTC_fastboot"?
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Acoustichayes said:
Are you trying on usb 2.o or 3.o? Last I read, 3.o didnt have support for fastboot yet. But I could be wrong.
Click to expand...
Click to collapse
Well tbh I've been trying on both just to see if anything works.
eriknors said:
I don't follow. Do u mean the command?
Eg: (HTC_fastboot devices) or (fastboot devices)
I'm just typing fastboot (cmd)
Click to expand...
Click to collapse
He asked that because if you use mine you need to use htc_fastboot devices
Otherwise you will be using the fastboot from sdk install.
eriknors said:
No dice. ADB worked just fine but still no fastboot
Click to expand...
Click to collapse
Had the same issue tried every thing, but eventually end up installing uBuntu that solved every thing.
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
Its due to the missing device descriptor.
Royal PITA, I have yet to get it working. I just keep a win7 laptop around.
The only way this could be "fixed", would be if we had a newer eng-hboot that had the descriptors set.
Hey All,
I'll keep this short. I can issue fastboot commands on my work computer (windows 10), but can't do them on my home computer (8.1). Can you surmise what's going on? I have a bootloader unlocked lg v30 (used work computer to unlock). I know that fastboot commands CAN work, I'm just guessing there's something going on with my home comp. Adb Devices and Fastboot devices always shows the device connected. But below is one of the errors I get. When I get this, the screen goes black with the LG V30 logo and In tiny text it says "press any key to shutdown". Any help would be appreciated.
Desktop\platform-tools>fastboot getvar all
getvar:all FAILED (command write failed (No error))
finished. total time: 0.016s
What did you use to install the adb and fastboot commands? The one from the xda fourms or from Android SDK?
Bowserman16162 said:
What did you use to install the adb and fastboot commands? The one from the xda fourms or from Android SDK?
Click to expand...
Click to collapse
I'll be honest, at this point I don't even remember. I feel like I've tried many different adb versions, the latest (if I remember correctly) was an exe file "adb-setup 1.4.3.exe" that I grabbed from a thread here. Happy to wipe my system clean of anything resembling adb, but the latest file I used installed it across the system.
AliLaPointe said:
I'll be honest, at this point I don't even remember. I feel like I've tried many different adb versions, the latest (if I remember correctly) was an exe file "adb-setup 1.4.3.exe" that I grabbed from a thread here. Happy to wipe my system clean of anything resembling adb, but the latest file I used installed it across the system.
Click to expand...
Click to collapse
If you have done that uninstall all adb drivers via device manager in should be under Android ADB for the adb I don't know on the fastboot you can maybe refer to the thread where you downloaded it from and it may have some uninstall instructions. Let me know if that helps!
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.