Hey I have an Honor 7 PLK-L01 with stock B380 (unlocked Bootloader). If I connect it via USB to my PC (USB debugging on) ADB detects my device after typing "adb devices" but if I reboot into fastboot he doesn't detect my device...
I really don't know why this happens, it worked fine before but then I reseted everything to stock. Now I can't even flash TWRP...
I would be really grateful if someone could help me.
Have you tried accessing CMD as Admin?
Sent from my honor 5X using XDA Labs
adriansticoid said:
Have you tried accessing CMD as Admin?
Sent from my honor 5X using XDA Labs
Click to expand...
Click to collapse
Yes, I always stuck after rebooting to Fastboot. I always get "waiting for device" if I try to flash with "fastboot flash recovery TWRP.img"
Whuut said:
Yes, I always stuck after rebooting to Fastboot. I always get "waiting for device" if I try to flash with "fastboot flash recovery TWRP.img"
Click to expand...
Click to collapse
Try reinstalling the drivers. Or install the Minimal ADB/Fastboot.
Sent from my honor 5X using XDA Labs
adriansticoid said:
Try reinstalling the drivers. Or install the Minimal ADB/Fastboot.
Sent from my honor 5X using XDA Labs
Click to expand...
Click to collapse
First of all thank you for your help, so this is what I did now:
I uninstalled HI Suite and ADB Kit, reinstalled HI Suite, installed Minimal ADB/Fastboot and again the same problem...
Whuut said:
First of all thank you for your help, so this is what I did now:
I uninstalled HI Suite and ADB Kit, reinstalled HI Suite, installed Minimal ADB/Fastboot and again the same problem...
Click to expand...
Click to collapse
There are many users having the same problem. No matter what I suggest them, the problem still persist. I'm sorry man.
Sent from my honor 5X using XDA Labs
No one else can help me?
Whuut said:
No one else can help me?
Click to expand...
Click to collapse
Try to download and install huawei USB drivers. If that does not work, google "manually installing fastboot drivers" and follow the steps. If I remember correctly you need to use Kouch's universal driver pack for that. If your phone was in my hands, it was just an hour's worth of study, trial and error. Did it with my honor 6 about a year back.
Give it a shot.
I did it now but I'm not quite sure how
I connected my phone while beeing on fastboot, opened the device manager (in Windows) and uninstalled the "Android Bootloader Interface". Then I uninstalled "Minimal adb and fastboot", installed "Huawei USB drivers for Honor 7" and installed "Minimal adb and fastboot" again. And now it works...
Seems like I had the wrong "Android Bootloader Interface" drivers.
It wasn't the direct solution but somehow it helped, so thank you
Whuut said:
I did it now but I'm not quite sure how
I connected my phone while beeing on fastboot, opened the device manager (in Windows) and uninstalled the "Android Bootloader Interface". Then I uninstalled "Minimal adb and fastboot", installed "Huawei USB drivers for Honor 7" and installed "Minimal adb and fastboot" again. And now it works...
Seems like I had the wrong "Android Bootloader Interface" drivers.
It wasn't the direct solution but somehow it helped, so thank you
Click to expand...
Click to collapse
Great... Glad I could help.
Glad you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Glad you fixed it.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
Great , you are here too !!
Sent from my KIW-L22 using Tapatalk
---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------
Whuut said:
First of all thank you for your help, so this is what I did now:
I uninstalled HI Suite and ADB Kit, reinstalled HI Suite, installed Minimal ADB/Fastboot and again the same problem...
Click to expand...
Click to collapse
It was a driver's issue .. More over issue exists in Windows 8.1 . better u have to reinstall windows freshly or else install win10
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
Great , you are here too !!
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Cooolll. You're here too! :laugh:
Sent from my honor 5X using XDA Labs
Related
nvm I solved it
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
de.rach29 said:
I have problems " waiting for device",..Need help...
Sent from my LG-P760 using xda premium
Click to expand...
Click to collapse
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Fastboot driver
where can i find it?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Where you can find what?
giviman said:
where can i find it?
Click to expand...
Click to collapse
Drivers? here:
developer.android.com/sdk/win-usb.html
This is also my problem, i try everything allready. Its just stuck on waiting for device after i try to flash recovery.
When phone is in fastboot mode it said unkonwn usb device, flash omap and fastboot and adb drivers are installed.
Is there any other method for root and recovery install?
Im not noob, i rooted and played with many Android phones, but for this i cant find any solution.
OS is Win Xp but there is same problem on Win 7 also.
who can give me the fastboot backup that i can flash !? I have flash recovery at fastboot :S
Need it for LG P760
thanks
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
hiiiiiiii
hii sir, when i type fastboot flash recovery recovery.img cmd show waiting for device for long time plz hlp
i had many problems trying to run adb commands along with fastboot...most recent was sideloading a rom in CWM.....no device detected...then dl pdanet and that driver fixed the problem...win7 x64....seems every computer is different and process to use adb on this phone...took me a while to find this as well...
help
i installed all the drivers but still it shows waiting for device
maxver0 said:
Where you can find what?
Click to expand...
Click to collapse
Waiting for device problem
maxver0 said:
You need to install fastboot drivers. When you are in fastboot you need to go 'device manager' or something like that on PC. Find android and use update drivers bottom option (install manualy) and point where your fastboot drivers are.
Click to expand...
Click to collapse
Can get the link for the drivers for micromax a58 need a heck of waiting for that to be installed with twrp recovery
Hi
I have an AT&T HTC ONE that is stuck in a bootloop. I can go into fastboot mode but not my recovery. I wanted to try to reflash the recovery but whenever I try to flash it on my Win 8.1, it says waiting for device. However, the prompt "adb devices" does not detect my phone.
!) I have installed SDK Tools.
2)I have HTC sync installed for the drivers.
3)I have the recovery image
Any help would be great.
Side Question:
If I factory reset and reinstall clockwork recovery, will I still be able to access my back up or does factory reset wipe everything???
Thanks.
Juice No Pulp said:
Hi
I have an AT&T HTC ONE that is stuck in a bootloop. I can go into fastboot mode but not my recovery. I wanted to try to reflash the recovery but whenever I try to flash it on my Win 8.1, it says waiting for device. However, the prompt "adb devices" does not detect my phone.
Any help would be great.
Thanks.
Click to expand...
Click to collapse
Do you have another computer that is NOT win 8.1?
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have another computer that is NOT win 8.1?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah, I got my roommates computer. Installed HTC SYNC, SDK Tools, used USB 2.0 drivers and the phone was not detected.
Could I have possibly installed SDK tools incorrectly???
hi y'all
i tried to flash my redmi 3s with a official dev rom today but unfortunatelly it seems that I messed things up.
My phone's bootloader wasn't unlocked so I tried the method for locked bootloaders using miflash and getting the phone into download mode. I got all the drivers installed (at least I think so) on Win 10 64 bit (driver signature verification is disabled).
While trying to flash using MiFlash I got at approx. 20% the error message "MiFlash Error "0x80070008 max buffer sector is 256". After that, my phone didn't boot anymore. All I'm seeing is the white Mi-icon.
I also noticed that It's not possible anymore to turn the device off. When I try, it turns on by itself and is stuck at the boot screen.
Download mode isn't working either. I tried the button-combination (Vol+ and -) and the "fastboot oem edl" command from Win command prompt when the phone is in fastboot mode - which does working.
When entering "fastboot oem edl" command I only get "waiting for any device" and nothing happens.
Is there any way to unbrick my phone or can I only use it as a paperweight from now on?
I hope yomebody can help.
Thanks & regards
Connect to your computer and try the power+volume(+)+volume(-)
It will put it in download mode
Sent from my Redmi 3 using Tapatalk
Aether060 said:
Connect to your computer and try the power+volume(+)+volume(-)
It will put it in download mode
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
Thanks for the fast response. I tried this while my phone was connected to my pc. Now I see this on my phone:
http://www.techgrapple.com/wp-content/uploads/2016/02/Unlock-Redmi-Note-3-Bootloader.jpg
and at the bottom it says pcsuite.mi.com.
When I take a look in the Windows device manager it says "Android Phone / Android ADB Interface".
Am I really in download mode now?
regards
Hi, because of that error you got installing new ROM you cant boot your phone anymore. As that happened to me before i might help you.
First, make sure you hold long enought power+VOL- buttons. Hold them for good one minute, you should be able to go into fastboot mode. Fast Boot worked for me when my Redmi had softbrick, also something messed up installing ROM.
Let me know how it goes.
Pauliens said:
Hi, because of that error you got installing new ROM you cant boot your phone anymore. As that happened to me before i might help you.
First, make sure you hold long enought power+VOL- buttons. Hold them for good one minute, you should be able to go into fastboot mode. Fast Boot worked for me when my Redmi had softbrick, also something messed up installing ROM.
Let me know how it goes.
Click to expand...
Click to collapse
Hi,
i can enter fastboot with Power and Vol- without any problems.
What do you mean? What should I do when I'm in fastboot Mode?
Regards
lunatikk said:
Hi,
i can enter fastboot with Power and Vol- without any problems.
What do you mean? What should I do when I'm in fastboot Mode?
Regards
Click to expand...
Click to collapse
You should now download MI flash program, and try to flash your device trough it. You can find tutorials on youtube.( just make sure you have lastest drivers installed.
Pauliens said:
You should now download MI flash program, and try to flash your device trough it. You can find tutorials on youtube.( just make sure you have lastest drivers installed.
Click to expand...
Click to collapse
No, please read my post all the way. I'm not able to flash using miflash at this point because miflash isn't showing my device and I'm also not able to enter bootmode with my device.
Regards
lunatikk said:
No, please read my post all the way. I'm not able to flash using miflash at this point because miflash isn't showing my device and I'm also not able to enter bootmode with my device.
Regards
Click to expand...
Click to collapse
Remember to disable driver signature enforcement
Sent from my Redmi 3 using Tapatalk
---------- Post added at 06:24 AM ---------- Previous post was at 06:21 AM ----------
Aether060 said:
Remember to disable driver signature enforcement
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
And also have you followed the steps? Like have you installed the unsigned drivers for mi flash? To flash using mi flash tool you will need to have your to disable driver signature enforcement, there is a way to disable it with cmd, I recommend you to use that method.
And your phone's screen should be totally black when its on download mode, if it's not helping then try going to the recovery mode at first, (volume(+)+power, then from the built in recovery miui go to the download mode, hope this helps, i use redmi 3 pro, same happened to me the first time
Sent from my Redmi 3 using Tapatalk
Aether060 said:
Remember to disable driver signature enforcement
Sent from my Redmi 3 using Tapatalk
---------- Post added at 06:24 AM ---------- Previous post was at 06:21 AM ----------
And also have you followed the steps? Like have you installed the unsigned drivers for mi flash? To flash using mi flash tool you will need to have your to disable driver signature enforcement, there is a way to disable it with cmd, I recommend you to use that method.
And your phone's screen should be totally black when its on download mode, if it's not helping then try going to the recovery mode at first, (volume(+)+power, then from the built in recovery miui go to the download mode, hope this helps, i use redmi 3 pro, same happened to me the first time
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
When I press Power and Vol+ the phone is simply rebooting. There isn't no Recovery screen.
I noticed, when installing a Version of miflash, a Tutorial said that there are three Popups which ask me if I really want to install an unsigned driver. I always only got 2 of these popups when installing miflash. Is there a way to install all drivers manually?
This got to be some kind of driver issue. I tried connecting the phone on another System (win7, 32bit) in fastboot mode. Here, when in enter fastboot OEM edl, the screen Gies black and the Windows device manager Shows COM3 Qualcomm...
It just ain't working on Win10
I got it now. I messed around in the windows device manager (unsinstalled the android / adb /...devices), reinstalled the drivers. Then, in fastboot mode, I executed the fastboot oem edl command and I got into download mode. From here I had to use the older version of MiFlash (2016.04.01.0 64bit). The newest version always gave me the error "specified cast is not valid" when I clicked the refresh button. Seems to be buggy as hell but the older version of Miflash worked as a charm.
Now, my bootloader is unlocked and I'm rockin the newest global version of official MIUI.
regards
flash the stock rom via mi flash , watch this video , this will surely help u
https://www.youtube.com/watch?v=wf8wg9d8bH8
Jainanjay said:
flash the stock rom via mi flash , watch this video , this will surely help u
https://www.youtube.com/watch?v=wf8wg9d8bH8
Click to expand...
Click to collapse
thanks for nothing dude.
/thread
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
lucasnoman said:
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
Click to expand...
Click to collapse
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
moto999999 said:
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
Click to expand...
Click to collapse
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
Yes, I did it. But a blue screen appear fast and my smartphone turns off. It does not go into recovery at all, only after I start the phone normally. Funny that I only get message of success since the release of the bootloader until the installation of twrp.
Have you tried "fastboot boot <recovery.img>"?
sudloa said:
Have you tried "fastboot boot <recovery.img>"?
Click to expand...
Click to collapse
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
lucasnoman said:
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
Click to expand...
Click to collapse
fastboot could use in fastboot mode (shutdown then vol down + power) only and windows sohuld recognize this.
But I think your adb usb driver got conflict somehow.
You can try "usbdeview" to uninstall all adb usb drivers then use some knid of universal adb usb driver installer.
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
lucasnoman said:
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Click to expand...
Click to collapse
Hi, You should TITLE your post Why does TWRP not stay resident ?
paulsnz2 said:
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
Hi, You should TITLE your post Why does TWRP not stay resident ?
Click to expand...
Click to collapse
You're Welcome
Antisound said:
You're Welcome
Click to expand...
Click to collapse
I have the 820. Could NOT get windows to see this phone on stock rom. Don't recall exact steps I took, but I do remember the ADB feature within TWRP saved my day. Windows would see the phone in TWRP recovery adb mode, but could never get windows to adb connect with stock rom.
Hey people, sry I'm coming back now. Lightning struck my street and burned my pc. But I come back with another problem, when I connect my phone to the pc nothing happens. I mean, I can't transfer cause MTP doesn't work. I tried install unninstall and install again adb, and all the drivers but it did not work. So I'll need to fix this to try to install twrp again
Guys! I was being too stupid! I found my mistake... I was using another smartphone twrp... So, for who are having same issue, pay attention to this. But, thanks everybody and sry for this hahaha
Ive been trying to install TWRP on my Poco F1 but i am receiving an error message saying " failed write to device failed"
Please Help
im on lastest Official Rom for Poco f1
If i try with ADB flash command, its just stuck
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
ekin_strops said:
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
Click to expand...
Click to collapse
I tried, still same and yeah the bootloader is unlocked
ekin_strops said:
Is your bootloader unlocked? Also, you use the command fastboot boot twrp.img
Click to expand...
Click to collapse
below is the attached screenshot of the error
Have you tried different PC?
Same error(FAILED (Write to device failed (Invalid argument)) when I try on AMD.. Try on Intel processor PC
cediedc said:
Have you tried different PC?
Same error(FAILED (Write to device failed (Invalid argument)) when I try on AMD.. Try on Intel processor PC
Click to expand...
Click to collapse
Okay will give it a try, previously i did install twrp on my amd fx series processor, recently got an upgrade to ryzen, guess thats the issue.
muham47 said:
Okay will give it a try, previously i did install twrp on my amd fx series processor, recently got an upgrade to ryzen, guess thats the issue.
Click to expand...
Click to collapse
No, Ryzen has nothing to do with it. I'm using Ryzen long time ago.
---------- Post added at 21:36 ---------- Previous post was at 21:34 ----------
muham47 said:
below is the attached screenshot of the error
Click to expand...
Click to collapse
Try downloading Minimal ADB, instal it to C, and run it with Admin rights. Also, try different USB port, try USB 2.0 port as 3.0 sometimes doesn't recognize the phone when it's in fastboot mode.
wait,, why isyour ADB running in drive G???
shouldn't that be installed on drive C?? you should open ADB FOLDER IN C,, then hit SHIFT + right click of the mouse to open up a commad
OPEN POWERSHELL WINDOW HERE in drive C... where your ADB as well as TWRP RECOVERY is in store..
muham47 said:
below is the attached screenshot of the error
Click to expand...
Click to collapse
What's your fastboot version?
Code:
fastboot --version
fastboot version 28.0.1-4986621
Also try as already mentioned:
different USB port - try USB 2.0 port
different cable (!)
santiagoruel13 said:
wait,, why isyour ADB running in drive G???
shouldn't that be installed on drive C?? you should open ADB FOLDER IN C,, then hit SHIFT + right click of the mouse to open up a commad
OPEN POWERSHELL WINDOW HERE in drive C... where your ADB as well as TWRP RECOVERY is in store..
Click to expand...
Click to collapse
tried, still no luck
ekin_strops said:
No, Ryzen has nothing to do with it. I'm using Ryzen long time ago.
---------- Post added at 21:36 ---------- Previous post was at 21:34 ----------
Try downloading Minimal ADB, instal it to C, and run it with Admin rights. Also, try different USB port, try USB 2.0 port as 3.0 sometimes doesn't recognize the phone when it's in fastboot mode.
Click to expand...
Click to collapse
okay so i downloaded minimal ADB and tried via that and i encountered different error this time, i have attached the screenshot
i tried using the command 'fastboot boot twrp-3.2.3-2-beryllium.img' and its just paused
Make.sure your twrp recovery is stored and located in your adb folder where you'll be running the adbpowershelle menu..
1. Fastboot flash recovery name_of_recovery.img
2. Fastboot boot recovery name_of_recovery.img
Have you tried this??
santiagoruel13 said:
Make.sure your twrp recovery is stored and located in your adb folder where you'll be running the adbpowershelle menu..
1. Fastboot flash recovery name_of_recovery.img
2. Fastboot boot recovery name_of_recovery.img
Have you tried this??
Click to expand...
Click to collapse
yes, as soon as i try the "1. Fastboot flash recovery name_of_recovery.img" i get the message 'Error (Failed....)' and when i directly try the 2nd thing you mentioned, it just stays there nothings happening
muham47 said:
yes, as soon as i try the "1. Fastboot flash recovery name_of_recovery.img" i get the message 'Error (Failed....)' and when i directly try the 2nd thing you mentioned, it just stays there nothings happening
Click to expand...
Click to collapse
AMD Ryzen has an issue with Poco F1. Try an Intel PC.
Hmm.. have you tried downloading any other TWRP IMAGE??
santiagoruel13 said:
Hmm.. have you tried downloading any other TWRP IMAGE??
Click to expand...
Click to collapse
yes tried about three of them. I just wanted to flash a custom ROM and now i'm stuck with this irritated
Are you sure your poco has an unlocked boot loader?? Cant say if its because of amd. Coz my pc. Also has amd a7.. with windows 10 pro. And its working fine with me..
Ah. I forgot.. do you have any antivirus? My SMADAV prevented me from accessing any vbsscript or any windoes script. And cant get to work with powershell or adb.. until i find out SMADAV IS THE CULPRIT..
santiagoruel13 said:
Are you sure your poco has an unlocked boot loader?? Cant say if its because of amd. Coz my pc. Also has amd a7.. with windows 10 pro. And its working fine with me..
Ah. I forgot.. do you have any antivirus? My SMADAV prevented me from accessing any vbsscript or any windoes script. And cant get to work with powershell or adb.. until i find out SMADAV IS THE CULPRIT..
Click to expand...
Click to collapse
yes, bootloader unlocked, debugging enabled, no anti-virus, only windows security enabled. Do you think is it related to latest MIUI update which is preventing TWRP to install ?