Anybody found how to disable this?
The phone powers on automatically when a charger is plugged in.
The Mate 9 had that
The Mate 10 solved it
And now it's back.
Not nice imho
According to Apple, it's a feature.
wtf does apple now, lol
nope, can't think why it would be a problem, especially given how quick the thing charges
My Huawei mate 20 pro boots up when connected to charger even if i power it off after i plug it.
I think i have found the solution for this problem from this post
https://forum.xda-developers.com/sho...8&postcount=11
Originally Posted by sid6.8
solve the problem... thanks a lot!! ?
My shot description for noobs like myself ?
- install minimal_adb_fastboot_v1.4_setup.exe on the pc
- boot/start your mobile phone into recovery (vol_down + power, wait until it vibrate) or via the enhanced restart menue (has to be activated in "developer options")
- in recovery choose the option "reboot to bootloader" (you will see different information of you mobile phone e.g. serial number)
- connect the phone to the pc via usb cable
- start the program "minimal ADB and Fastboot on the pc (command promt starts)
- Check the connection state of you mobile phone with the fastboot command:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
98xxxxxx fastboot (serial number of your device)
- type in the following commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem enable-charger-screen
...
OKAY [ 0.004s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem off-mode-charge
...
OKAY [ 0.011s]
finished. total time: 0.014s
power off your mobile phone and plug in the charger !!! ?
Also in youtube video
https://www.youtube.com/watch?v=Zp9G...ature=youtu.be
in the description says to use this command "fastboot oem-off-mode charge 1"
which is a little bit different from the above post.
I don't feel enough confident to try it my self i hope someone with better experience could tell us if this working.
blackspp said:
Anybody found how to disable this?
The phone powers on automatically when a charger is plugged in.
The Mate 9 had that
The Mate 10 solved it
And now it's back.
Not nice imho
Click to expand...
Click to collapse
Can you please tell me where you find that Mate 10 Solved it.
I cannot find it nowhere.
Thanks
I guess a firmware update fixed it
If you have a faulty power button and your battery discharged, how would you turn it on?
This feature could be a saviour in these instances.
Sent from my HUAWEI LYA-L09 using XDA Labs
Related
While trying to root my phone using using briefmobiles instructions (http://briefmobile.com/motorola-atrix-4g-root), i rooted successfully. I then wanted to unlock my boot loader to add a rom using theses instructions http://forum.xda-developers.com/showthread.php?t=1167373&highlight=IHOP
While doing this i go to step 2. H) and my phone did not reboot to andriod it booted to a black screen that said SVF :105:1:2 Failed to boot 0*1000. Occasionally if i take the battery out and put it back in and turn the phone on it will come up with a list of things to do and if i dont choose something on the list in 5 seconds it will go to RSD mode. But it doesn't go to RSD mode it will go to Fastboot protocal support. I also have a choice to push the volume up button and selected something on the list and if i select RSD, i tryed to flash back to the original firmware but the device is not shown on RSD Lite. AM I BRICKED!!!????!!!
You are not hardbricked but softbricked. So don't panic. As long as you have that list you're fine..you want to get into fastboot.
Just follow the fastboot oem unlock instructions ...
Sent from my MB860 using XDA App
Unlock your atrix bootloader
1. Put the phone in RSD MODE
a) power the phone off
b) hold power and hold volume up
2. Flashing pudding
a) open rsdlite
b) connect the phone to the pc
c) click the ...
ATT USERS
d) browse and find C:\atrix\183_pudding.sbf
INTERNATIONAL USERS
d) browse and find C:\atrix\IHOP_Bell.sbf
e) select the phone in the lower panel after the status area says "connected..."
f) click start
g) wait for the flash to complete and reboot the phone
h) after the phone is all the way back in android to the lock screen unplug the phone
i) power the phone off
j) close rsdlite
3. Put the phone in fastboot mode
a) power your phone off
b) hold power and volume down
c) hit volume up (this should start fastboot mode)
4. Unlock the phone
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
fastboot oem unlock
c) it should then display something like the following in your command prompt
Unlocking your device can permenently VOID your warranty.
This process cannot be reversed. If you wish to proceed,
reissue the unlock OEM command containing the unique ID
of your device: XXXXXXXXXXXXXXXXXXX
OKAY [ 0.002s]
finished. total time: 0.002s
d) type the following replacing XXXXXXXXXXXXXXXXXXX with the unique ID from the previous command prompt.
fastboot oem unlock XXXXXXXXXXXXXXXXXXX
e) Type the following to reboot your device
fastboot reboot
This???
yes..
When you boot up your phone and you get that list...you want fastboot..
you should be here...
3. Put the phone in fastboot mode
a) power your phone off
b) hold power and volume down
c) hit volume up (this should start fastboot mode)
4. Unlock the phone
a) open a command prompt on your windows pc
b) type the following in the command prompt
cd C:\atrix
fastboot oem unlock
c) it should then display something like the following in your command prompt
Unlocking your device can permenently VOID your warranty.
This process cannot be reversed. If you wish to proceed,
reissue the unlock OEM command containing the unique ID
of your device: XXXXXXXXXXXXXXXXXXX
OKAY [ 0.002s]
finished. total time: 0.002s
d) type the following replacing XXXXXXXXXXXXXXXXXXX with the unique ID from the previous command prompt.
fastboot oem unlock XXXXXXXXXXXXXXXXXXX
e) Type the following to reboot your device
fastboot reboot
When i try to go into fastboot it says "Starting Fastboot Protocol support"
then under that it says "Battery is too low to flash"
What should i do?
timeshare1234 said:
When i try to go into fastboot it says "Starting Fastboot Protocol support"
then under that it says "Battery is too low to flash"
What should i do?
Click to expand...
Click to collapse
attempt to fastboot oem unlock anyways, if it doesn't work then you'll have to manually charge the battery with a USB cable, or use a battery from someone else's Atrix.
I tried to fastboot oem unlock but when i unpluged it from wall charger to computer, the phone turns off and wont turn back on unless it is connected to wall charger.
timeshare1234 said:
I tried to fastboot oem unlock but when i unpluged it from wall charger to computer, the phone turns off and wont turn back on unless it is connected to wall charger.
Click to expand...
Click to collapse
take out the battery, and plug into wall charger, place battery back into phone after it goes into charging mode and let it charge for half an hour or so. then try fastboot oem unlock again.
Like a wall charger where the battery (and only the battery) is connected to the charger? Kinda like a camera charger?
timeshare1234 said:
Like a wall charger where the battery (and only the battery) is connected to the charger? Kinda like a camera charger?
Click to expand...
Click to collapse
no, the wall charger that came with the phone. plug the phone up to the wall charger, without the battery in it. it will induce a charging mode for the phone, where you can't access anything but the screen will have a battery display on it.
after you get into charging mode, place the battery back into the phone and allow it to charge.
When i plug the phone into wall charger without the battery the screen displays
"SVF:105:1:2"
"Failed to boot 0x1000"
timeshare1234 said:
When i plug the phone into wall charger without the battery the screen displays
"SVF:105:1:2"
"Failed to boot 0x1000"
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=EQ6JNCvIe8k
charge your battery with this method then, and remember to never start modifying your phone without a 100% charge
It wouldn't charge...am i screwed?
I know what battery symbol you are talking about i have seen it on my phone before but i dont hink there is any way of getting that back because on the list of things to chose from at the top it said "no OS is found starting RSD in 5 seconds"
timeshare1234 said:
I know what battery symbol you are talking about i have seen it on my phone before but i dont hink there is any way of getting that back because on the list of things to chose from at the top it said "no OS is found starting RSD in 5 seconds"
Click to expand...
Click to collapse
if you hacked apart the USB cable and attached it correctly, it will feed a current directly into the phone. there is no battery symbol that appears, it's a direct charge and the phone doesn't even know that it's charging.
So even if i correctly attached it the phone won't do anything?
timeshare1234 said:
So even if i correctly attached it the phone won't do anything?
Click to expand...
Click to collapse
the battery will start to warm up, since it's having a current pushed into it. just hook up the positive and negative cables into the correct spots and then let your phone charge for half an hour or so.
My battery isn't heating up if i use another atrix battery will that work?
Yes it will work.
Sent from my MB860 using xda premium
The phone will only turn on when it is plugged into the wall, if i plug it into my computer and try to turn it on the green light turns on and then off after 3 seconds and nothing happens.
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!
hello there, it has been a while (2009) since my last post, forgive me for my sins
I bought a Sony xperia z2 for from ebay, used, from a good seller.
When it arrived, it was slighty strange, great condition but some icons were slightly different and it felt different.
I went through the usual stuff of disabling all the sony privacy phone homes etc.
but when i went to switch the privacy on, it said this was a prototype phone and i could not turn off the phoning home
I didn't like this very much so investigated putting the stock rom on the phone rather than this prototype rom.
i successfully unlocked the bootloader using fastboot (i'm on ubuntu 64) and then i got cocky and tried to put twrp and stuff on
specifically i did this:
Code:
sudo fastboot devices
[sudo] password for magnets:
CB5A21QNUN fastboot
[email protected]:~$ sudo fastboot -i 0x0fce oem unlock 0x64A449C97C90DA50
...
OKAY [ 1.147s]
finished. total time: 1.147s
[email protected]:~$ sudo fastboot devices
[sudo] password for kris:
[email protected]:~$ sudo fastboot devices
[email protected]:~$ sudo fastboot devices
[email protected]:~$ sudo fastboot devices
CB5A21QNUN fastboot
[email protected]:~/Downloads/xperiabuild/workingfolder$ sudo fastboot flash recovery twrp-3.0.2-0-sirius.img
sending 'recovery' (11570 KB)...
OKAY [ 0.365s]
writing 'recovery'...
OKAY [ 0.769s]
finished. total time: 1.133s
[email protected]:~/Downloads/xperiabuild/workingfolder$ sudo fastboot flash boot boot.img
sending 'boot' (8410 KB)...
OKAY [ 0.266s]
writing 'boot'...
OKAY [ 0.576s]
finished. total time: 0.842s
all this seemed to go marvelously, except when i tried to boot it i get the SONY logo with xperia at the bottom and that's it, until the battery dies.
plugging it in charges the battery and then you get the logo again.
I've tried waiting for the battery to die, then plugging it into the computer while holding the down button, but fastboot and ADB don't find the device.
the computer won't charge it, only a 3amp charger will, the phone shows the logo screen BEFORE the red light goes out, so i have no chance to push the down key and try to get it into recover.
i can get the pink light to come on, but as soon as i press anything the light goes red and the phone shuts off. if i plug the charger in... it shows the logo screen before the red light goes out and then i have to wait for the battery to run down again.
Any advice?
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
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.