Phone is not entering adb bootloader - Zuk Z1 Q&A, Help & Troubleshooting

My phone zuk z1 which is operating in zui os not CyanogenMod.. someone in local service center changed this is.. which is not entering adb bootloader mode or fastboot mode .when I enter adb devices it shows the device..while entering
PHP:
adb reboot bootloader command phone starts showing Linux penguin logo and computer shows a message USB is not recognized. I installed all drivers and universal adb drivers...
Zui version:0.9.096
Is there any way to get into twrp to change os

Bro, i was stuck on the same problem and what I did was very simple. You just switch off your device and enter into recover mode, and from there delete the data and cache and restart will help you to run your device.

Related

[Q] Can't ADB in bootloader mode?

I can ADB/fastboot my device most of the time.
But when booting into Bootloader mode, I suddenly can't ADB into it?
The driver appears to be loaded up in my Win7x64 computer. Says it's the Motorola ADB device. And I can open my files on the phone. But ADB just doesn't see the phone for some reason. Any ideas?
Bootloader is fastboot.
Code:
fastboot devices

Huawei P8 not detected by PC in Fastboot mode

I use
adb reboot bootloader
to get into fastboot mode.
the display shows
"Fasboot & rescue mode
please connect and open Hisuite
LINK
phone locked"
I even installed the Hisuite, but nothing happens and
fastboot devices
returns an empty list.
when the devices is booted up, USB works like a charme - but in fastboot mode windows does not even detect a device?!
any ideas?

Bootloop after fingerprint sensor and ROM died

Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish
doebelfish said:
Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish
Click to expand...
Click to collapse
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!
strongst said:
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!
Click to expand...
Click to collapse
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?
doebelfish said:
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?
Click to expand...
Click to collapse
Did you have actually drivers installed for fastboot? See guides like this http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
Also qfil method can help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But consider service center in case of warranty.
same problem. fingerprint died. then after a empty battery shutdown i face bootloop. but hopefully i have TWRP installed and i could recover my data. but i dont know how to access factory reset menue or install another fresh rom

New ROM

Hello there
I had a custom rom on my op2 then i deletet everything over the recorvery. Now i have no OS installed so it only shows the boot screen. I can get into the twrp recorvery and fastboot mode but if i try to fastboot or adb sideload a new rom im unable to connect my op2 to my PC. I doesnt show up.
I tried this guide : https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
I cant make my device show up in my device manager. (I did the windows driver thing).
Can you connect through fastboot? In fastboot mode type in: fastboot devices
If so: flash this https://www.androidfilehost.com/?fid=529152257862717275

Fastboot doesn't detect my phone, please help

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/

Categories

Resources