Hi there,
I just got my X720 shipped from China and try to flash EONS/openpilot on it,
I have done the following:
Have ADB/Fasboot tools on your computer
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device
Make sure adb can see your device when you run "adb devices" --> will show my device
Run "adb reboot bootloader" --> reboot into fastboot
Run "fastboot devices" to make sure you see your device --> nothing show here!!
I had also try the "All in one tool" but get same result.
Any advice?
Related
I just got a new grey LeMax2 X822 with 16S stock rom. I have enabled USB debugging and bootloader unlocking, enabled MTP device when plugged, I can see it as "Le Max2" MTP and can browse internal storage. I've tried different android adb drivers and two computers (win10 and win7). There is no yellow question mark, and device is recognized as "Le Max2" on win10 and "Android ADB" on Win7. However when i run cmd and type "adb devices" the list is empty, and when I type "adb usb" - I get "device not found". I've tried everything I could think of. What's the problem?
I want to install CWM recovery and a rom. But I can't! Please help, I don't know what else to try.
Update: updated to stock 20S via stock recovery. "Fastboot devices" works and I was able to install TWRP with "fastboot recovery twrp.img" command. So I guess I will try to flash the custom ROM now... ADB still doesn't work.
midirt said:
I just got a new grey LeMax2 X822 with 16S stock rom. I have enabled USB debugging and bootloader unlocking, enabled MTP device when plugged, I can see it as "Le Max2" MTP and can browse internal storage. I've tried different android adb drivers and two computers (win10 and win7). There is no yellow question mark, and device is recognized as "Le Max2" on win10 and "Android ADB" on Win7. However when i run cmd and type "adb devices" the list is empty, and when I type "adb usb" - I get "device not found". I've tried everything I could think of. What's the problem?
I want to install CWM recovery and a rom. But I can't! Please help, I don't know what else to try.
Update: updated to stock 20S via stock recovery. "Fastboot devices" works and I was able to install TWRP with "fastboot recovery twrp.img" command. So I guess I will try to flash the custom ROM now... ADB still doesn't work.
Click to expand...
Click to collapse
Did you click YES on the Popup dialog von your phone that your phone is allow to communicate with your computer?
Did you click YES on the Popup dialog von your phone that your phone is allow to communicate with your computer?
Click to expand...
Click to collapse
Yes, I remember doing that.
Dial UP *#*#76937#*#*
Try dialing *#*#76937#*#* and enable AT port, this worked for me!
GL
OK, problem somehow solved. As I had fastboot command access I flashed CWM recovery. After I've done that and booted to recovery, and connected to PC, there was a unknown MTP device in device manager with yellow exclamation mark, as if there is no drivers. However "adb devices" suddenly returned "device code - recovery". So I pulled full CWM backup to PC and was able to flash madsurfer's 20S ROM. So far so good. Will test how it works...
MrakMrakMrak said:
Try dialing *#*#76937#*#* and enable AT port, this worked for me!
GL
Click to expand...
Click to collapse
Had me stumped, Thank you for that nugget. (should be pinned somewhere in here ?)
MrakMrakMrak said:
Try dialing *#*#76937#*#* and enable AT port, this worked for me!
GL
Click to expand...
Click to collapse
Excellent Post!
Worked a treat for me
Just to note, you need to do this after a reboot too....well I did after flashing recovery and rebooting.
MrakMrakMrak said:
Try dialing *#*#76937#*#* and enable AT port, this worked for me!
GL
Click to expand...
Click to collapse
Had this issue on my just received Le Max 2, and this did it. Thanks a lot.
When I go to fastboot mode and try to use platform tools it doesn's see my phone when i type "fastboot devices", and when i type "fastboot oem unlock" it responds "< waiting for any device >".
Your pc hasn't recognized your phone. Make sure that you have installed the drivers correctly. If you haven't install drivers first then try again "fastboot devices" with powershell
I tried installing all drivers i found and they all got installed and it sees my phone correctly when I am in normal boot. If u can send good drivers. With powershell it's the same. The drivers version is 1.4.3
It works i had to open device menager when i was in the fastboot and there was a device called "android" in category "other devices" and i had to search for drivers online and it worked.
komin77 said:
When I go to fastboot mode and try to use platform tools it doesn's see my phone when i type "fastboot devices", and when i type "fastboot oem unlock" it responds "< waiting for any device >".
Click to expand...
Click to collapse
Did you enable "OEM Unlocking" & "USB Debugging" options in Developers option?
I want to install LineageOS so I closely followed the fastboot and adb instructions on the official site. During my first (failed) attempt, there were some old Google USB and ADB things on my PC, so I deleted everything and started again with a clean slate.
I managed to make ADB work (adb devices detects my device, could authenticate the computer, all seems good there). But if I start the phone in fastboot mode, connect and run fastboot devices, I get nothing back. It doesn't give any sign of the connected device. Windows's "Devices" window lists a device called "Android", but it's under "Unspecified" and has the yellow triangle/exclamation mark on the icon.
1. Am I right to assume that this will stop me from unlocking the bootloader (if I will use the unofficial method) and flashing TWRP and a custom ROM on the device?
2. More importantly: What could be wrong, how can I make fastboot see my phone?
Many thanks for the suggestions!
hi,
first do you have latest ADB and Fastboot
then connect your device and run adb devices. check if it detect the device means from the command prompt run "adb reboot bootloader" (without quotes)
now once after device reboots to bootloader check fastboot devices it will detect now
if not then goto device manager,right click on the device and click on update driver software and choose android fastboot interface
you are done now run fatboot devices,it will detect the device
Solved!
adbdriver com/downloads/
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Sure. You are allready in that mode. Just type fastboot devices and check..
I did that but no response.
The cursor jumps to the next line but there is no response from the phone.
If I type adb devices the phone is listed but the fastboot command doesn't return anything.
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Restart to bootloader, then fastboot should work. If your phone is still on, and you can access adb, you should also be able to type adb reboot bootloader
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Docomoco said:
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Click to expand...
Click to collapse
The option in the power menu is called bootloader (fastboot only will work there) the hint was in the adb command I gave you, adb reboot BOOTLOADER. Not sure why they changed what the menu was called but I'm glad you got it sorted. To give you a short summary, adb will only work when your phone is powered on and booted into android, or if you have recovery mode open and on the adb section, and fastboot only works in the bootloader hope that could help!
Edit: fastboot devices should work but only in bootloader mode, not when your phone is started normally
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
You have to insert a SIM card, boot of the device and make a phone call to get it to register your device. Wait a few minutes and then restart your phone. Go into settings under about phone and enable developer options. Back out and go into developer options and you will see OEM unlock. You need to turn that on and USB debugging. Both of them must be turned on. Now you can boot into fastboot and unlock your bootloader. It will wipe the device so if you have any data you want to save you better do it now.
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
SourPower said:
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
Click to expand...
Click to collapse
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
dladz said:
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
Click to expand...
Click to collapse
thanks for the reply, i am on windows 10 and i dont know what is causing the issue when the phone goes in fastboot, but i went on my wife's laptop and got it working within a few minutes after installing adb...
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
tema_ka said:
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
Click to expand...
Click to collapse
If you type fastboot reboot what happens? If nothing then either you're device doesn't have usb debugging on, could be the cable/usb slot (some people have had issues with this)
Or its the driver installed for fastboot.
Show hidden devices in device manager you may have multiple devices, remove them all and start over.
Your also need to have used ADB and have trusted the device (prompt will appear on your phone the first time you connect it successfully whilst in your phones system, not fastboot)
for windows 10:
firstly download the google adb driver:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
then do the following:
1. adb devices [you should see your device ] > adb reboot bootloader
2. device manager > update driver > chose from list [android device]
3. still in device manager got the newly populated Android device and then update driver > choose adb interface
3. fastboot oem unlock
etc.
hope this helps
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
shweta007 said:
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
Click to expand...
Click to collapse
Secure Boot means your Bootloader is locked.
Setup fastboot correctly, open a cmd window, navigate to fastboot.exe and enter fastboot oem unlock, follow instructions on phone screen
I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
CurlyTemple said:
I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
Click to expand...
Click to collapse
When I try to give a fastboot command, the powershell just returns
<waiting for device>
and then nothing happens.