Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
adin59 said:
Hi there
i wiped data to install a new rom. But i wiped the recovery and also the rom so now i only see the bootloader
i see bootloader version 4.18
fastboot mode in red
lock state unlocked
The problem is : my computer won't recognize the n7 though ADB
when i try driver test with nexus root toolkit it says adb device was not found
Si now i'm stuck and i can't install any rom or recovery to boot in
please anybody help
Click to expand...
Click to collapse
Somehow i managed to install a rom. It's Fixed
adin59 said:
Somehow i managed to install a rom. It's Fixed
Click to expand...
Click to collapse
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
kktvr4 said:
I hate to bring this thread back to life but, how did you manage to do it? I am in the exact same situation but bootloader 4.23. Did you manage to install the ROM through Nexus Root? Or platform tools?
Any help is appreciated.
I am attempting to flash the factory image. Found here. http://forum.xda-developers.com/showthread.php?t=1907796
ADB devices does not list my device and Nexus Root tool says not found. Not sure what else to do at this point.
Click to expand...
Click to collapse
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
korockinout13 said:
"
I'm assuming you're in the bootloader while trying to do this. ADB stands for "Android Debug Bridge". The bootloader really has nothing to do with the Android operating system, thus ADB isn't running. You need to use fastboot commands. Try "fastboot devices".
Click to expand...
Click to collapse
Thank you very much, that worked for me. :good:
I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.
I'm having the same problem as well.
I installed adb + Fastboot,
I'm able to issue the command adb reboot bootloader
But once the device is in bootloader, fastboot and adb are not detecting it anymore.
I tried installing the ADB android drivers in the device manager, but still same problem, device not getting detected while in bootloader
I wonder if anyone had the same problem, and was able to solve it?
I am also not able to use fastboot because of driver, but able to use adb.
Try latest version 1.17 from here:
http://leshcatlabs.net/downloads_usb_unifl/
did it work?
It's not working for me either. I've installed all the drivers and "adb reboot bootloader" reboots the phone into "CYANOGEN FASTBOOT MODE" but "fastboot devices" returns nothing. What am I doing wrong?
swarimk said:
I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
I managed to finally get it to work with Win 10 using the drivers from here http://forum.xda-developers.com/zuk-z1/help/files-zuk-z1-drivers-qpst-roms-twrp-t3221629 I'm not sure if was just these drivers that solved it because I had an absolute bear of a day trying to get it to work and some odd stuff happened. But I just know it worked shortly after installing them. Now I'm very pleased with NuleaRom installed
edulus91 said:
did it work?
Click to expand...
Click to collapse
I Have the same problem.
But, although i can't send fastboot devices, i can send revovery.img
And now i can unloack bootloader
Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).
someoneelse999 said:
Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).
Click to expand...
Click to collapse
This morning I had the same problem, I installed All in one tool and reinstalled all with the tool. Zuk's driver didn't work but i tried in fastboot mode and it worked.... I don't know how but it worked.
Hi,
I have the same problem. ADB commands work but Fastboot ones don't and even a "fastboot reboot" returns with a "waiting for device". I have tried updating the drivers manually but the response is always that the best drivers are already installed. Today, I got the Zuk Z1 in fastboot mode and then installed the recommended drivers as in this link given by the user XQ55 using the executable file in the link. I don't know whether it was because of this driver update or the fact that I had connected the Z1 for the first time after a major Windows 10 update (the phone was set up as a new device), now, in the Fastboot mode, I can see the device shown as "Shenqi Composite ADB Interface" in the Device Manager as against just "Android" earlier. Also, now when in ADB mode, the phone shows as "MTP USB Device" as against "Z1" earlier in the Device Manager.
However the fastboot commands don't work. Can someone help with this; the stock ROM isn't good at all and want to unlock bootloader, root and then install a new ROM
someoneelse999 said:
Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).
Click to expand...
Click to collapse
swarimk said:
I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
uninstall zuk usb driver from your pc and then reinstall it in your pc it may solve your problem.if problem still persists then try using all in one tool to install the drivers again it will definetly solve.
I want to install TWRP and new roms on my X829 device. I can access the device through adb , but not fastboot
When i list adb devices the device is detected, but when i list devices in fastboot the device is not detected.
When I press adb boatloader reboot the device reboots.
Anyone experienced anything similar?
travelguy78 said:
I want to install TWRP and new roms on my X829 device. I can access the device through adb , but not fastboot
When i list adb devices the device is detected, but when i list devices in fastboot the device is not detected.
When I press adb boatloader reboot the device reboots.
Anyone experienced anything similar?
Click to expand...
Click to collapse
Its probably a driver problem on you PC install this: https://forum.xda-developers.com/showthread.php?t=2588979
Heyyo, just to double check you are using adb when in the ROM or recovery and fastboot when in bootloader?
So when in the ROM you would use... adb devices
When in bootloader you would use... fastboot devices
Or... fastboot flash recovery TWRP.img
I'd recommend following this guide for doing it all. Works good
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I am attempting to root with magisk method, and everything appears to be good to go... (from cmd when i enter adb devices, i get the serial number back...) and the samsung drivers are all present and up to date...
BUT this is what happens when i try to reboot adb bootloader, or try fastboot devices commands...
C:\adb\platform-tools_r28.0.1-windows\platform-tools>adb devices
List of devices attached
3300e8b83538b2d5 device
C:\adb\platform-tools_r28.0.1-windows\platform-tools>adb reboot-bootloader
**after this command, my device just restarts without entering into bootloader menu**
C:\adb\platform-tools_r28.0.1-windows\platform-tools>fastboot devices
C:\adb\platform-tools_r28.0.1-windows\platform-tools>
PLEASE, help a lady out?
I have the same situation when I use any app with option "restart to bootloader",BTW. why do you want to get into bootloader menu? Don't you need just to get into recovery?
Hello,
I am trying to flash an alternative ROM on my Samsung J3 SM-J320F using an ubuntu OS. I got adb and fastboot installed, but fastboot doesn't seem to recognize my device as the command
Code:
fastboot oem unlock
only has me waiting endlessly with
Code:
< waiting for any devices >
As far as I have searched the internet, I understand that I am missing drivers to communicate with my Samsung phone, is that correct? I can only seem to find driver packages for Windows, but none for Linux/Ubuntu. Can anyone please help me?
adb seems to find my device just fine, as
Code:
adb reboot bootloader
worked fine.
Any help appreciated. Thank you.
t