Hello i have Redmi note 5 pro .. last night i tried to unlock my bootloader but the Mi unlock doesn't detect it.. i searched xda,google and youtube and did every possible solution.. nothing seems to work for me then i also tied to check it under mi flash and also doesn't detect my phone.. searched everywhere for solution and nothing seems to work.. i tried it with another laptop and and it works fine in that.. i tried multiple adb options nothing works and also i did a soft reset of laptop and hard reset my mobile phone and installed the only adb which youtubers were using to unlock there devices and still not working.. what to do now ?
My laptop Acer predator Helios 300
i5 - 8330H
8GB ram
gtx 1050ti
128 gb ssd
1 tb hard disk
Hi , probably is drivers problem , try this :
https://www.drivereasy.com/knowledg...-was-not-successfully-installed-in-windows-7/
Teddy Lo said:
Hi , probably is drivers problem , try this :
https://www.drivereasy.com/knowledg...-was-not-successfully-installed-in-windows-7/
Click to expand...
Click to collapse
Acyually i can transfer files from my laptop to android phone easliy.. it's just that my laptop fails in every "adb" related tasks
Try manually to install and make sure that USB Debbuging is ON .
https://gsmusbdriver.com/xiaomi-redmi-note-5-pro
Teddy Lo said:
Try manually to install and make sure that USB Debbuging is ON .
https://gsmusbdriver.com/xiaomi-redmi-note-5-pro
Click to expand...
Click to collapse
i have tried that too and it still doesn't work for me.
download and install redmi note 5 usb drivers in your laptop after that connect the device to Laptop and see if it appears
Deno_developer said:
download and install redmi note 5 usb drivers in your laptop after that connect the device to Laptop and see if it appears
Click to expand...
Click to collapse
my laptop detects the phone for file transfer.. but when i connect my phone in fastboot mode mi flash and mi unlock or mi pc suite just doesn't detect them .. when run the cmd command " fastboot devices" it shows me the device name.. but as soon as i try to run any other command it gives me errors ..screenshot attached
Akshay09 said:
my laptop detects the phone for file transfer.. but when i connect my phone in fastboot mode mi flash and mi unlock or mi pc suite just doesn't detect them .. when run the cmd command " fastboot devices" it shows me the device name.. but as soon as i try to run any other command it gives me errors ..screenshot attached
Click to expand...
Click to collapse
aaaah powershell is the problem for this because it is restricted to run commands you must change from powershell to cmd like in windows 7 search in youtube how to replace powershell with cmd
Deno_developer said:
aaaah powershell is the problem for this because it is restricted to run commands you must change from powershell to cmd like in windows 7 search in youtube how to replace powershell with cmd
Click to expand...
Click to collapse
i have tried cmd also and it doesn't work.. in attached cmd screenshot too .. seriously i have tried most of the solutions
Akshay09 said:
i have tried cmd also and it doesn't work.. in attached cmd screenshot too .. seriously i have tried most of the solutions
Click to expand...
Click to collapse
Hi , I see from screenshot's device is recognised in FastBoot , so try this command
fastboot reboot edl and press Enter
if everything is fine device will reboot in Download mode and see what is going on : ) .
:fingers-crossed::fingers-crossed::fingers-crossed:
Good luck : )
Teddy Lo said:
Hi , I see from screenshot's device is recognised in FastBoot , so try this command
fastboot reboot edl and press Enter
if everything is fine device will reboot in Download mode and see what is going on : ) .
:fingers-crossed::fingers-crossed::fingers-crossed:
Good luck : )
Click to expand...
Click to collapse
Hello i tried the command and right after this or any other command laptop makes this disconnecting sound.. after this my phone disappear from my laptop.. no other command works even reconnecting the phone doesn't work.. after i have to reboot the" bootloader mode" and then my latop detects the phone.. and this cycles is endless
Again is just on MTP still not in ADB ?
Try to flash the same twrp recovery for your device in fastboot mode , rename twrp.img to recovery.img , drag that custom recovery to adb directory
now write this command :
fastboot flash recovery recovery.img and see if you are able to flash that custom recovery , probably you need first to unlock bootloader but try like that if it's work .
Teddy Lo said:
Again is just on MTP still not in ADB ?
Try to flash the same twrp recovery for your device in fastboot mode , rename twrp.img to recovery.img , drag that custom recovery to adb directory
now write this command :
fastboot flash recovery recovery.img and see if you are able to flash that custom recovery , probably you need first to unlock bootloader but try like that if it's work .
Click to expand...
Click to collapse
this happens.. and i have tried to rename the the file to recovery.img but doesn't work .. i just don't get it what is wrong with it
Very strange to me but , try this :
1. Disable or remove your Antivirus (because sometimes virus can block instaling drivers , ports or running flash tool)
2. Uninstall all the previous drivers you used for flashing or unbrick use free tool called USBDeview
64 bit
https://www.nirsoft.net/utils/usbdeview-x64.zip
3. Put your windows in Test mode
To put your Windows in test mode just Run As Administrator Command Prompt and insert one of the following command:
bcdedit -set testsigning on ( to enable test mode)
http://s000.tinyupload.com/index.php...66266232947643
bcdedit -set testsigning off ( to disable test mode)
http://s000.tinyupload.com/index.php...26094979151761
Or Disable driver signature
Windows 10
https://www.youtube.com/watch?v=71YAIw7_-kg
After that reboot your PC .
4. Uninstall all flash program from your pc like Miflash tool, Mi PCsuite
Use Revo Uninstaller for advanced uninstaling that clean leftover files and registry which is stored inside your Windows registry.
https://www.revouninstaller.com/revo..._download.html
After that reboot your PC .
5. Now make sure that you have enabled USB debugging
Make sure that Windows update is ON
and try like this :
https://www.youtube.com/watch?v=YoNvzm5_V6Q
Good luck : )
Teddy Lo said:
Very strange to me but , try this :
1. Disable or remove your Antivirus (because sometimes virus can block instaling drivers , ports or running flash tool)
2. Uninstall all the previous drivers you used for flashing or unbrick use free tool called USBDeview
64 bit
https://www.nirsoft.net/utils/usbdeview-x64.zip
3. Put your windows in Test mode
To put your Windows in test mode just Run As Administrator Command Prompt and insert one of the following command:
bcdedit -set testsigning on ( to enable test mode)
http://s000.tinyupload.com/index.php...66266232947643
bcdedit -set testsigning off ( to disable test mode)
http://s000.tinyupload.com/index.php...26094979151761
Or Disable driver signature
Windows 10
https://www.youtube.com/watch?v=71YAIw7_-kg
After that reboot your PC .
4. Uninstall all flash program from your pc like Miflash tool, Mi PCsuite
Use Revo Uninstaller for advanced uninstaling that clean leftover files and registry which is stored inside your Windows registry.
https://www.revouninstaller.com/revo..._download.html
After that reboot your PC .
5. Now make sure that you have enabled USB debugging
Make sure that Windows update is ON
and try like this :
https://www.youtube.com/watch?v=YoNvzm5_V6Q
Good luck : )
Click to expand...
Click to collapse
Thank you for your kind reply i have tried it before too.. it doesn't work
Teddy Lo said:
Very strange to me but , try this :
1. Disable or remove your Antivirus (because sometimes virus can block instaling drivers , ports or running flash tool)
2. Uninstall all the previous drivers you used for flashing or unbrick use free tool called USBDeview
64 bit
https://www.nirsoft.net/utils/usbdeview-x64.zip
3. Put your windows in Test mode
To put your Windows in test mode just Run As Administrator Command Prompt and insert one of the following command:
bcdedit -set testsigning on ( to enable test mode)
http://s000.tinyupload.com/index.php...66266232947643
bcdedit -set testsigning off ( to disable test mode)
http://s000.tinyupload.com/index.php...26094979151761
Or Disable driver signature
Windows 10
https://www.youtube.com/watch?v=71YAIw7_-kg
After that reboot your PC .
4. Uninstall all flash program from your pc like Miflash tool, Mi PCsuite
Use Revo Uninstaller for advanced uninstaling that clean leftover files and registry which is stored inside your Windows registry.
https://www.revouninstaller.com/revo..._download.html
After that reboot your PC .
5. Now make sure that you have enabled USB debugging
Make sure that Windows update is ON
and try like this :
https://www.youtube.com/watch?v=YoNvzm5_V6Q
Good luck : )
Click to expand...
Click to collapse
Hello thank you for your kind reply i have tried that too .. it doesn't work for me
Maybe the only way is to re-flash stock firmware but to get your device recognised you need to do test point .
Warning !!! I'm not responsible if you brick your device or do some physical damage !
https://hk.saowen.com/a/af40ed097d659a77c784748604e320c8f2567b6780eea6a3701648a33c4b153c
Let me know if you got fixed : ) . Good luck : )
Teddy Lo said:
Maybe the only way is to re-flash stock firmware but to get your device recognised you need to do test point .
Warning !!! I'm not responsible if you brick your device or do some physical damage !
https://hk.saowen.com/a/af40ed097d659a77c784748604e320c8f2567b6780eea6a3701648a33c4b153c
Let me know if you got fixed : ) . Good luck : )
Click to expand...
Click to collapse
I have re-flashed my phone firmaware.. and my phone works fine with my old laptop.. it's my new laptop which has serious adb drivers issue
Akshay09 said:
I have re-flashed my phone firmaware.. and my phone works fine with my old laptop.. it's my new laptop which has serious adb drivers issue
Click to expand...
Click to collapse
Wait , I understand that on your old laptop ADB works fine on new one not or ?
Teddy Lo said:
Wait , I understand that on your old laptop ADB works fine on new one not or ?
Click to expand...
Click to collapse
Yes my old laptop works fine and detect my phone.. i can run cmd commands with no issues at all .. it's my new laptop with adb driver issues and doesn't detect my phone
Related
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.
In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>
I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.
I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.
Is the problem on the phone? How can I fix it?
Drivers seem to be fine...
Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?
Someguyfromhell said:
Drivers seem to be fine...
Does your phone really go into fastboot? Blue LED stays on, nothing on the screen. If yes, check drivers once again! Does Windows detect the device?
Click to expand...
Click to collapse
Yes, the LED is blue, the screen is off.
Windows does make sound when connecting, and it doesn't pop up "new device" wizard.
Hey! Just noticed something.
When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"
How can I disable it from going to SEMC Flash Device?
And it happens only when I have drivers uninstalled. Seems they install once I connect the phone. Tried again without uninstalling drivers, and it goes straight to "Flash device"
Then maybe wrong drivers installed?
Someguyfromhell said:
Then maybe wrong drivers installed?
Click to expand...
Click to collapse
Maybe:
I've reinstalled the SDK - didn't work
Added .inf file from SE site - didn't work
Installed Flashtool drivers - didn't work
But now, I'm waiting for Lollylost100 to reupload the drivers he once uploaded on Megaupload - I think those ones worked last time (hopefully)
I'll install Debian and try again with new OS, with no installed drivers or whatever...
USB debuging is on?
Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.
Theonewithideas said:
In command prompt, I typed "fastboot -i 0x0fce getvar version"
And, it stays at <waiting for device>
I'd like to point out that I succeeded at flashing custom ROM last time, but now, it won't connect in fastmode.
I've installed the SDK (obviously)
Added the .inf file from SE site
Installed drivers from Flashtool folder
LED goes blue when connecting.
I've tried different ports, different OS, different PC altogether, but everything ends up with <waiting for device>.
Is the problem on the phone? How can I fix it?
Click to expand...
Click to collapse
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
xbox360k550 said:
USB debuging is on?
Click to expand...
Click to collapse
Yes.
hsrbnr said:
Just wait a few seconds after connecting you phone in fastboot mode, sometimes computer takes time process.
Click to expand...
Click to collapse
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Lasanda said:
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
Click to expand...
Click to collapse
Okay, I will try this and post the results.
Actually, will this work with Mini?
Theonewithideas said:
Yes.
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Okay, I will try this and post the results.
Actually, will this work with Mini?
Click to expand...
Click to collapse
I think it also works with mini as well.just try it.
Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".
Could this be a phone-related error?
Theonewithideas said:
Installed everything again, on Ubuntu. I've reached the Windows checkpoint: it again says "<waiting for device>".
Could this be a phone-related error?
Click to expand...
Click to collapse
try my method in windows pc.it dont works in ubuntu.it seems,there is no problem in your device.it may be there is some thing missing what you want.try my method back with windows pc and post clearly the resault with steps.if something wrong.i will help you.don't worry....
Windows drivers do not work on Ubuntu, the same vice-versa also.
Lasanda said:
2 things can be resone for this.first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
https://www.dropbox.com/s/x57ebyha7r65o27/fastboot.rar
Dont forget to thanx if this helpfull...
Click to expand...
Click to collapse
Okay, if you say so:
first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...
This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.
.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...
Can't find the drivers. It will not help, every fastboot folder is the same.
.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
... or, you can just type "cd" and then location to fastboot.
Theonewithideas said:
Okay, if you say so:
first one is u didn't installed your adb drivers well.so it can be easyly fixed if u use xperia mini pro.just download drivers from the link below and unzip it.connect your device on fastboot mode and use device manager to ree update your drivers.when update your drivers,point drivers location to. Unziped fastboot drivers folder.make sure u have pointed x86 or x64 folder inside drivers folder.(x86 for 32bit os,x64 for 64bit os).check the problem is fixed...
This didn't work, it's SEMC Flash Device again, and fastboot doesn't work.
.if not problem depends on second resone.it is u do not have correct fastboot program.(I have personal experience on this).just check the fastboot.zip folder for your device on internet and download it.(this is littlebit difficult but u can)when u download it just ree update your drivers using its drivers folder...
Can't find the drivers. It will not help, every fastboot folder is the same.
.when u use command prompt make sure u have opened correct folder from command prompt which contains fastboot.exe.(open fastboot folder write click while holding shift key and click on open command prompt window)then try using it.problem must be fixed.
... or, you can just type "cd" and then location to fastboot.
Click to expand...
Click to collapse
ok.i got that.another thing i need to know is when u do first step is that the device manager recognized your device,if does,is it updates your device drivers when u point the drivers location to x64 or x86?(when u do that it must show android adb interface drivers installed, when u check device manager)which version of windows u used to do those steps? and tell me your device name and model.i will upload a correct fastboot program for u.just keep your hopes alive....
EDIT
Theonewithideas said:
When uninstall the drivers connect the device, Device Manager says "S1boot fastboot" briefly before going into "SEMC Flash Device"
Click to expand...
Click to collapse
just have to mention u one thing..now i read this post u quoted before.it seems there is no any problem in your device.when u uninstall drivers u says this "S1boot fastboot" shows on your device manager it meens your device works well.S1boot fastboot meen device fastboot hardware it exactly not installed yet.u need to update drivers of this "S1boot fastboot" as my methods first step.just send me the progress and answers for my questions thats all.i will send a fix.
Can't connect in fastboot mode
Hi!
I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?
Thanks.
---------- Post added at 11:37 PM ---------- Previous post was at 11:11 PM ----------
Gioo25 said:
Hi!
I want to unlock the bootloader of my Xperia Arc S (Lt18i) but i can't connect my phone in fastboot mode. When i connect the cable to PC, the LED flashes blue, but just for a few seconds and turns red. The message that appears in command prompt is "waiting for device". I tried so several solutions but no one worked.
Could you help me?
Thanks.
Click to expand...
Click to collapse
Sorry for my last post. When searching in some forums, I discovered that I can not unlock the bootloader. It seems that is a definition of the system.
Thank You And sorry. :crying:
Go to Service Mode to see if it can be unlock.
brixe said:
Go to Service Mode to see if it can be unlock.
Click to expand...
Click to collapse
Thank you! I've done that and the result is this: "bootloader unlock allowed: NO".
SAme Same
Theonewithideas said:
Yes.
Tried that, left phone on fastboot for a few minutes while looking for solution. No difference.
Okay, I will try this and post the results.
Actually, will this work with Mini?
Click to expand...
Click to collapse
Having the same problem with my SE LWW.
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
Hi all,
I want to install TWRP but everytime I try to reboot to bootloader ("adb reboot bootloader" command), it's only restarting the phone just like a normal restart. Is there any other way or steps to take before reboot?
I'm on F600L20e (MM), OEM unlock and USD debugging are active on setting.
Thank you
Are you on lollipop or marshmallow?
ardian1899 said:
Hi all,
I want to install TWRP but everytime I try to reboot to bootloader ("adb reboot bootloader" command), it's only restarting the phone just like a normal restart. Is there any other way or steps to take before reboot?
I'm on F600L20e (MM), OEM unlock and USD debugging are active on setting.
Thank you
Click to expand...
Click to collapse
Lollipop doesn't boot to the bootloader
In Marshmallow you can.
omar2005 said:
Lollipop doesn't boot to the bootloader
In Marshmallow you can.
Click to expand...
Click to collapse
I'm on Marshmallow Android 6.0
oh idk
ardian1899 said:
I'm on Marshmallow Android 6.0
Click to expand...
Click to collapse
maybe because your model is different I have the H960A
Yes, I'm on F600L
Try the command 'adb reboot recovery'
ardian1899 said:
Hi all,
I want to install TWRP but everytime I try to reboot to bootloader ("adb reboot bootloader" command), it's only restarting the phone just like a normal restart. Is there any other way or steps to take before reboot?
I'm on F600L20e (MM), OEM unlock and USD debugging are active on setting.
Thank you
Click to expand...
Click to collapse
I also had trouble rebooting into bootloader. Adb reboot bootloader didn't work for me, even though I have the European H960A variant.
I used the instructions from this thread.
The hardware method where you have to use POWER + VOL DOWN buttons worked for me after a few tries. The crucial thing was to release the button in between I think.
rabie.93 said:
Try the command 'adb reboot recovery'
Click to expand...
Click to collapse
Fushoku said:
I also had trouble rebooting into bootloader. Adb reboot bootloader didn't work for me, even though I have the European H960A variant.
I used the instructions from this thread.
The hardware method where you have to use POWER + VOL DOWN buttons worked for me after a few tries. The crucial thing was to release the button in between I think.
Click to expand...
Click to collapse
Thank you!
I'll try those if I have a chance, can't do that at the moment.
I think I can help with that . There is thread already how to do it here on xda but its not that clear . Few things are overlooked and not explained thoroughly .
Code:
Credit for TWRP Goes to Rudi666
I got stuck little on beginning and after reboot bootloader command . So I'll explain with more details My way = Easy way .
Step 1. You have to have ADB fastboot Installed and lg Driver installed . Follow this link and install adb bootloader . https://forum.xda-developers.com/showthread.php?t=2588979 Follow this link to install LG Driver http://lgusbdriver.com/windows/lg-usb-driver-v4-1-1-0 After you install adb there will be folder in your " My Computer / Local **** C " called adb .
Step 2. Unlock bootloader . This link will help you http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702 Follow all instructions and ignore adb install instructions ( You done that already )
Step 3. Download recovery from here https://forum.xda-developers.com/lg-v10/development/recovery-twrp-v3-0-2-0-unofficial-t3387783 and save this recovery in adb folder that was created when you installed adb and unzip it there into root folder of adb . Also Download super su and put it on sd card of your phone .
On your phone in developer options make sure your adb debugging is activated . And OEM unlock is enabled .
Step 4. Connect your phone and make sure it is set as file transfer and not battery charge or anything . If the phone asks you to allow pc to connect confirm it .
Step 5 . Open your adb folder in c and Holding SHIFT Right-click anywhere ( blank space ) inside that folder , when menu pops up click on Open Command prompt here ( or open power shell window here ) . When it opens go in it and type
Code:
adb reboot bootloader
and hit enter . Your phone will reboot leave the command window open ..... Now THIS is where some people get stuck ! Some pc's don't recognize the phone anymore and they can't flash recovery . This is what you do . Go to DEVICE MANAGER and you will see your phone connected with yellow exclamation mark . It will be either android device or unknown device or usb device , I don't remember . Right click on it and choose update driver , menu pops up go to Browse my pc for software , go to Let me pick from a list of available drivers , go to adb interface ( I think android adb will work too ) click install . When it's done your LG will be recognized by pc once more . go back to command window and type in ( Or copy Paste )
Code:
fastboot flash recovery twrp-3.0.2.0-0-h960a.img
and hit enter . When it's finished , you have to pull battery out .
Now put the battery back in and PUSH AND HOLD POWER + VOLUME DOWN buttons together . When you see LG logo release the POWER button for one second while STILL HOLDING VOLUME DOWN BUTTON and then push POWER button again . When your phone comes back on again release buttons .Your phone will have white screen asking you if you want to factory reset your phone . ( If you got confirmation on your command prompt on your pc that your recovery was installed it will NOT wipe your phone ) Push YES It will ask you if you are sure push YES again and your LG will restart in TWRP . There you find settings , change storage to sd card and go to main menu , install zip , choose SUpERSU , reboot you are done . Works on Lollipop and Nougat same . I hope I helped . Credit for TWRP Goes to Rudi666 .
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
Me too !
Drivers are here: https://developer.android.com/studio/run/win-usb
These are the ones I use for ADB/Fastboot.
May I ask if anybody solved this already?
Having the same issue, tried various drivers, but fastboot won't find my phone
Help is highly apperciated!
Clock
If you using windows 10 have you disable the drivers signature verification.. And search on here (XDA) for Min ADB & Fastboot tools, easier than using SDK tools unless you modding apks ect..
Okay, I got this working.
When in fastboot mode, you have to go to the device manager, update driver, and manually choose the google fastboot driver. Then the ! is gone and it works.
Fastboot drivers for Xperia XZ1
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode.
Click to expand...
Click to collapse
I add a hint to the solution that is working for me (Windows 7, 64 bit): https://forum.xda-developers.com/showpost.php?p=79221714&postcount=44
Redcalibur said:
My PC doesn't detect my phone when I use Fastboot Devices when my phone is on Fastboot mode. I get a blank space in return. Can anyone help me with this? ADB works fine, it's only Fastboot. Is there a Fastboot driver that I might be missing?
Thank you.
Edit: I'm trying to unlock the bootloader of my phone.
when u connect phone to pc choose no data transfer then open cmd and write: adb reboot fastboot
Click to expand...
Click to collapse