When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
kayaven said:
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
Click to expand...
Click to collapse
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Will_Xda said:
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Click to expand...
Click to collapse
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
kayaven said:
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
Click to expand...
Click to collapse
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
What are you trying or wish to do?
Which command?
Will_Xda said:
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
Click to expand...
Click to collapse
I'm using Windows 7 Ultimate x64, fastboot and adb are both running normal for the rest.
RuudM said:
What are you trying or wish to do?
Which command?
Click to expand...
Click to collapse
Well, i am trying to unlock my bootloader, but any command that writes to the phone will freeze it.
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
RuudM said:
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
Click to expand...
Click to collapse
I've already done that, but the command I need to run in order to get that code freezes it.
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
RuudM said:
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
Click to expand...
Click to collapse
I've got the original Android SDK fastboot, but that won't really matter, I suppose. The rest is the same. Furthermore, when i use the 'fastboot devices', it responds, but when i use something like 'fastboot oem get_identifier_token', it says FAILED (command write failed (Unknown error)), and the phone gets stuck.
I really have no idea why this is happening, i will now test if the official HTC fastboot works... :fingers-crossed:
-----------
Omg I'm an idiot, i just had it open on hboot and not fastboot >.<
I didn't know the difference Thanks a lot anyway everyone!
Related
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
shaiwon said:
I neglected to flash vendor.img when installing the M preview and did "fastboot reboot" after flashing everything else manually. Now whenever my N9 boots, it only shows the Google logo. I've tried going into Recovery and wiping/factory reset with no success.
Is there any way I can a) flash the remaining vendor.img; or b) return my N9 back to 5.1.1?
Click to expand...
Click to collapse
Boot back into your bootloader, and "fastboot flash vendor vendor.img"
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
shaiwon said:
That's what I'm trying to do but I don't know how to connect the tablet with my Mac to run the command in fastboot. When I type "adb devices", it no longer lists my device as attached. Would appreciate instructions in how to connect again through USB to flash the vendor image.
Click to expand...
Click to collapse
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
cam30era said:
There's not enough information here to help you.
So if I understand well, you previously were able use ADB and fastboot on this computer?
Does your computer recognize your N9? Can you see the N9's SDcard from your Mac?
If yes, then is "USB debugging" enabled in Developer Options?
When you try ADB devices, did you click the "always allow/trust connection with this computer" popup on your N9's screen?
Click to expand...
Click to collapse
Before flashing the preview image using fastboot, I had USB debugging enabled. When rebooting after flashing all the files (except vendor.img), the tablet would power on and show only the "Google" logo and go no further. So I tried booting into fastboot and recovery, but when I plug in the tablet to my Mac and try "adb devices", it doesn't recognize it being connected.
Since I cannot turn the N9 on fully to go into Developer Options and enable USB debugging again, how do I connect it to my Mac again so I can flash the remaining file and complete the setup?
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
Hi, sogrady...
You don't need ADB to flash anything... All you need is FASTBOOT and a working connection to your PC/Mac.
----
ADB debugging is irrelevant when it comes to running fastboot flash commands. ADB is only meaningful when running a fully booted version of Android OR when running a Recovery... Stock or Custom.
Providing your Nexus 9 bootloader is unlocked, you should be able to run fastboot flash commands without problem.
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
sogrady said:
In the same boat here. Enabled USB debugging, OEM unlocked, flashed the device manually (build failed, did the .img's sequentially), now the device gets stuck on the Google logo at boot. Attempted recovery and reset, no joy. Gets stuck on the Google logo. When back in the Fastboot menu, meanwhile, my Mac - previously able to see the device via adb - lists no connected devices so I can't reflash.
I assume I'm going to have to go the RMA route?
Click to expand...
Click to collapse
I thought so too, but I found a solution.
Check out my post here: http://forum.xda-developers.com/nexus-9/help/help-boot-loop-os-n-t3122167#post61051773
Hopefully, it helps.
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
GedBlake said:
Hi, sogrady...
To confirm you have a working fastboot connection, and with the device booted into it's bootloader, type...
Code:
fastboot devices
This should return your N9s unique device id... If it doesn't, you likely have a driver/connectivity issue... but it has nothing to do with ADB debugging - On or Off.
Rgrds,
Ged.
Click to expand...
Click to collapse
sogrady said:
Unfortunately, fastboot can't see the device either:
Code:
ferro$ fastboot devices
ferro$
This is with the Nexus 9 connected and in fastboot mode. As for it being a driver issue, everything that I've seen suggests that specific to Windows, and I'm on Mac. Is that accurate, or are there drivers I need to install on a Mac?
Click to expand...
Click to collapse
No drivers on a Mac. And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
cam30era said:
No drivers on a Mac.
Click to expand...
Click to collapse
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
cam30era said:
And the command should be "./fastboot devices". You need the "period" and "backslash" before the command.
Click to expand...
Click to collapse
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
sogrady said:
So assuming fastboot doesn't see the device, then, I'm out of options and looking at an RMA?
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them without the ./ preference is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Hi, again sogrady....
Don't give up so easily...
When you say "I'm out of options", what options have you tried exactly?
Another computer? Another USB cable? A different USB port on a computer?? There could be several variables causing problems for you.
One other point, are you certain your Nexus 9 is fully booted into fastboot mode, and not just the HBOOT bootloader...
You should see something like my attached screenshot...
If you see this, then all things being equal, fastboot commands should work without problems.
Hope this helps...
Rgrds,
Ged.
sogrady said:
Why would this be? I've placed both adb and fastboot both in the machine's PATH, so executing them with the ./ prefix is unnecessary. Certainly worked just fine the first time around without them.
Click to expand...
Click to collapse
Update the binaries, they may be outdated.
You can use my script for this: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
Happy to report success - well, partial success anyway. Per @GedBlake, I swapped in a new machine and cable, and per @simmac I made sure my binaries were updated. As it turns out, this was unnecessary: my mistake, after looking at @GedBlake's screenshot was that I was not down in fastboot, I was in hboot. As soon as dropped down into fastboot, voila:
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
HT4CRJT01274 fastboot
So, problem solved I figured. I re-downloaded the M image to my new machine, checked the MD5 and attempted to flash all. As with the previous iteration, it failed due to a new (to me) set of errors:
Code:
error: cannot load 'system.img'
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
sending 'vendor' (147127 KB)...
ERROR: usb_write failed with status e000404f
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
ERROR: could not get pipe properties
ERROR: could not get pipe properties
rebooting...
ERROR: usb_write failed with status e0004061
finished. total time: 0.000s
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting...
ERROR: usb_write failed with status e00002ed
At which point I figured that I would simply load the *.img's manually, one by one. But fastboot had by this point become squirrelly about even seeing the machine.
Code:
Macintosh-3:volantis-MPZ44Q sogrady$ fastboot devices
ERROR: could not get pipe properties
ERROR: could not get pipe properties
???????????? fastboot
At which point I decided to simply see if I could go back and load 5.1.1 and deal with M later. While that flash-all.sh script failed as well, I was able to put 5.1.1 back on via the following manually:
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
unzip image-volantis-lmy47x.zip
cd image-volantis-lmy47x
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash cache cache.img
fastboot reboot
At which point the device booted back up into 5.1.1. So big thanks folks for helping me restore an otherwise bricked machine! Much appreciated. Hope the steps help anyone else caught in a bricking cycle.
And if anyone has any idea why my M load failed, I'd be all ears because I would like to load that up at some point. For now, though, I'm just happy to have a working machine again.
Update: Ok, strike the above. Re-ran that process for the Android M build and it went off without a hitch this time, although the setup wizard failed so the build itself looks to be buggy. That at least is not related to the flashing process, however, so proceed to flash M onto the device if you're willing to try and get past those issues.
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead.
I can get a black screen with the blue led by running adb reboot bootloader and the phone is recognised from fastboot devices but when I try to unlock the bootloader I get an error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed)
finished. total time: 0.042s
Any help appreciated.
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
I suspect that it is a USB problem at one end or another.
If I connect up the phone to the PC using the original lead I can find it using adb devices and the device is showing up as error free "Sony sa0113 ADB Interface Driver" in Windows 10 device manager.
However the phone isn't charging and I can't get it into Fastboot by holding the up vol key and plugging in the USB lead or by running adb reboot fastboot
If feels like I haven't go the fastboot USB drivers but I can't see how or where I can add them.
Any help appreciated.
Click to expand...
Click to collapse
Disable driver signature enforcement then reinstall sony drivers
tapiwasam said:
Disable driver signature enforcement then reinstall sony drivers
Click to expand...
Click to collapse
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
adb reboot bootloader just goes into bootloader mode and not fastboot mode which is needed to unlock it. Go directly into fastboot by typing adb reboot fastboot
Then when your phone led is flashing blue, run your fastboot "oem unlock" command.
Saw now that you already tried that sorry about that.
Tried running cmd with admin privileges to see if that shows any difference?
Also from sony:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
PhilG57 said:
My Z5 compact was updated to Nougat using the OTA service.
The bluetooth integration to my car stopped working and I read that this was a noted problem I decided to flash my phone back to Marshmallow.
I'd installed custom ROMs on previous HTC phones following info from XDA so was pretty confident.
After following the Sony guidelines and obtaining my unlock key I am unable to get it to work in fastboot mode.
.... snip....
Click to expand...
Click to collapse
You don't need to unlock your bootloader to simply downgrade to official MM! Just use flashtool to flash the appropriate MM ftf. There are plenty guides available on XDA and elsewhere.
I'm lost in your explanation.
You wanted to unlock your bootloader to be able to downgrade your phone? That's right? And it's fine to me, but you don't need to do that if you don't feel like. Unlocking your bootloader is nog necessary to downgrade to MM via flashtool.
So you tried to unlock your bootloader. But what you write what happened afterwards is completely unclear to me, because it contradicts itself.
-->> "Also I can see the phone with both adb devices and fastboot devices"
Fine. This means your connected with your phone and fastbook recognizes your phone. So bootloader is unlocked and software to control that works fine.
-->> "However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led."
Fine, so you unlocked your bootloader, and rebooted in fastboot.
-->> Obviously. It's an unlocked bootloader, you can double unlock it or something like that. You can relock it if you want (which doesn't make any difference for what you want to do) but that's a different method.
Is there any reason that you absolutely need to a second method to enter fastboot mode? Or any fastboot mode? It could be possible with another kernel, but I don't see the point to flash another kernel. I would just leave it like it is.
PhilG57 said:
Thanks. I think I am OK there because I accepted the drivers from an unverified source during installation.
Also I can see the phone with both adb devices and fastboot devices
However when I run adb reboot bootloader the phone reboots but comes up with a blank screen with the blue led.
Click to expand...
Click to collapse
that is notmal behaviour, that is fastboot mode, indicated by that blue LED
Thanks for the clarification that I don't need to unlock the bootloader to downgrade using flashtool. What I didn't say was that I couldn't reinstall Nougat using the Sony tool software restore option or get anywhere with flashtool because the phone won't go into the blue led mode by inserting the USB and holding the up vol button. I did try running flashtool in one window and the command line tools in another with the idea of running flashtool first and then unplugging the phone and replugging it to use command line to get the blue LED state, but that doesn't work because the command line tools can't see the phone once flashtool is running and has addressed the phone.
From what i read, i assume you are on nougat and want to go back to MM, right?
So you would need flashmode instead of fastboot mode.
You get there with holding Vol down button and plugging in USB cable on turned off phone.
Flashmode also shows a green notification light instead of the blue one.
If you having Problems to get there, please check following:
make sure to have latest version of flashtool installed http://www.flashtool.net/downloads.php
install drivers from your flashtool\drivers folder
don't use an USB 3.0 port or cable(have heard of some people having trouble with)
PhilG57 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0fce oem unlock 0xB4D9AxxxxC359F2C
...
FAILED (remote: Command did not succeed) <- this
finished. total time: 0.042s
Any help appreciated.
Click to expand...
Click to collapse
OP, I had the exact same problem as you. At the time I tried absolutely everything but never found the culprit. So after several months I actually succeeded today
This is the guide I followed - https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388 and it worked perfectly.
A few pointers:
- Go to the service menu (*#*#SERVICE#*#*) before you begin, before you turn OEM Unlocking ON from Dev Options .
- Take note of what it says in Configuration and Firmware.
- Now enable OEM Unlocking and take note again, it should say stuff like Model Number: Unknown and other unknown stuff.
- Reboot - IMPORTANT.
- Use the guide I gave you and you will be fine, it took me ages to find a solution but now I'm on MM and rooted
Hope I helped :fingers-crossed::fingers-crossed::fingers-crossed:
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.
Hi
I recently upgraded a Honor 5c to Nougat(which works)NRD90M test keys build. I did this through Flashfire to try and preserve root. It failed(what a surprise).
The device is recognised now with 'fastboot devices', by running ADB using root in Linux.
I can get into bootloader screen using fastboot and have unlocked the phone AGAIN to be sure. BUT, cannot flash TWRP which is vital. The error now is:
Sending 'boot.img' (24464 KB) OKAY [ 0.869s]
Booting FAILED (remote: 'Command not allowed') fastboot: error: Command failed
This suggests the phone is locked which is absurd. I think this is a permission problem within Android, it that possible?
It doesn't matter how I'm going to root, if I can't communicate the whole thing is usesless.
The same issue continues with ADB in Win10
Any thoughts hear, because I've trawled Google.
thanks
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
jwoegerbauer said:
To clarify things: ADB and Fastboot are 2 completly different things. Fastboot deals with device's bootloader, whereas ADB deals with device's Android OS.
Run this command sequence
Code:
fastboot devices
fastboot getvar all 2>%TEMP%\phoneinfo.txt
fastboot reboot
type "%TEMP%\phoneinfo.txt" | more
which will get you a list of various variables on the phone with model and such useful things.
Click to expand...
Click to collapse
Excuse if this format is incorrect
Thanks for that.
ADB and Fastboot are 2 completly different things
Click to expand...
Click to collapse
Sure
fastboot devices
Click to expand...
Click to collapse
MQH4C17330000094 fastboot
fastboot getvar all 2>%TEMP%\phoneinfo.txt
Click to expand...
Click to collapse
Returns to prompt
fastboot reboot
Click to expand...
Click to collapse
Works
type "%TEMP%\phoneinfo.txt" | more
Click to expand...
Click to collapse
getvar:all FAILED (remote: 'Command not allowed')
Finished. Total time: 0.005s
Same thing again
Cliff
cliffhanger54 said:
getvar:all FAILED (remote: 'Command not allowed')
Click to expand...
Click to collapse
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
jwoegerbauer said:
That a Fastboot cmd does not work ( e.g. error Command not allowed ) is not unusual because Fastboot is different from version to version and also depends on how OEM/Carrier implemented it.
Again:
Bootloader and Android OS are different things, as this is same on PC where UEFI/BIOS and Windows OS are different things, too. A device's bootloader doesn't depend on any permissions granted within device's OS. A bootloader is a kind of software that runs as soon as you start up your phone. It tells the phone which programs are loading in order to make your phone run smoothly. This software packages all the instructions that are supposed to boot the Android OS, and initializes hardware and serves as security checkpoint.
Don't mix things up.
BTW:
Whether device's bootloader is unlockable / is already unlocked or not is stored in system file named build.prop.
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then unlocking bootloader is supported otherwise it's not.
or
Code:
fastboot devices
fastboot oem device-info
If "Device unlocked: true" is shown then bootloader is unlockedd.
Click to expand...
Click to collapse
Thanks again for answering. I understand what you say. I've used Linux for 20 years and understand the differences. But where does this leave us/me. I should be able to flash TWRP into the recovery partition surely? Or are we dependent on software versions here as you say? It would be relatively easy in Linux and of course Android is based on it.
cliffhanger54 said:
I should be able to flash TWRP into the recovery partition surely?
Click to expand...
Click to collapse
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
jwoegerbauer said:
TWRP completely removes device's default /recovery partition if it exists ( exists only on A-only Android devices), TWRP creates its own in device's /boot partition.
To flash TWRP on A-only ( or on current active boot slot if it's an A/B ) device
Code:
fastboot devices
fastboot flash boot <PATH_ON_PC_TO_YOUR_TWRP_IMAGE_HERE>
Click to expand...
Click to collapse
Thanks I think I've tried this one. I do get a different response though:
'fastboot: error: cannot get boot partition size'
I've seen suggestions that formating the boot partition is required - sounds extreme.
Why not simply re-flash device's Stock ROM to restore it to its original state ?
:good:
Sukrus said:
:good:
Click to expand...
Click to collapse
Yes wouldn't that be great. Have tried that from the beginning when I couldn't flash TWRP.
Put the Update.app on the SDcard, reboot the phone, hold down the buttons(tried them all), Bingo, it always takes me to eRecovery and how useless that is.
I have backups of Marshmallow with TWRP and Flashfire, which is why I took the flash TWRP route.
Wish I'd never upgaded now, although was forced to because of banking.
thanks
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
jwoegerbauer said:
@cliffhanger54
I have noticed that current thread basically is a duplicate of this thread you started on XDA some days ago, too.
Click to expand...
Click to collapse
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
cliffhanger54 said:
Yes, couldn't really get anyone to answer, needed more info. Apologies. Will cease other question
Cliff
Click to expand...
Click to collapse
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
cliffhanger54 said:
Right. After many attempts at other things I became convinced this was a locked bootloader problem despite the phone saying it was unlocked. Anyway have persisted in unlocking the phone several times and am now at a screen saying 'Your device is unlocked' but it also says 'you device is booting now'. But that's as far as it goes. If I turn the phone off it comes back to this screen and holding the power button+-volume also comes back to this screen, i.e I can't turn it off. How do I get back to the bootloader/fastboot mode or is this a genuine brick?
thanks
Cliff
Click to expand...
Click to collapse
Okay finally solved it. Let the battery run down as all I was getting was a bootloop. I was then able to get into fastboot mode with the necessary keys. From here i flashed TWRP but this required numerous attempts with different versions, finally got '3.1.1 venus' to load and the rest was straight forward!
thanks to everyone