Hello,
I am unable to unlock the bootloader despite following all the steps. I don't know where I am failing or why. I only get the "adb devices" command to work for me, the rest I get continuously "waiting for device".
The mobile is a ZTE Nubia Z17.
Related
Did a search and couldnt find anything that answers this problem directly. I followed this guide: http://forum.xda-developers.com/showthread.php?t=928370
I can get adb to recognize the device using "adb devices". I reboot to bootloader via the command "adb reboot bootloader" and I get the screen with the 3 little guys on skateboards and it says "FASTBOOT USB" in a red box, but when I type "fastboot devices" it just blinks and goes back to "c:\adb". Then if I try to run a command it says "<waiting for device>". Any help is greatly appreciated. Thanks.
I did everything like in this guide to the point :
"2. open and run "GizFlasher" form the pack
- press 1 then hit enter ("Sblocco bootloader")"
Fastboot dont see my ZTE mini.
https://forum.xda-developers.com/nubia-z17-mini/how-to/zte-nubia-z17-mini-unlock-bootloader-t3650871
I also tried this guide.
https://www.getdroidtips.com/unlock-bootloader-zte/
I even tried on linux. Also on Ubuntu ADB works fine fastboot dont see my phone.
After point 2 when nubia launches the bootloader there is "Now you are in fastboot mode. The phone is fused" and "Nubia device state: locked".
Please help. That original nubia rom is garbage.
Try with this command: "fastboot oem nubia_unlock NUBIA_NX569J/H" J/H depending the model you have.
I had the same problem. I skipped the bootloader part & proceeded to Step 2, installing TWRP. It somehow worked, got my Custom ROM installed.
I have unlocked my bootloader and want installed twarp with fastboot.
I start zhe bootloader with "adb.exe reboot-bootloader"
It do not run, after start on CMD-prompt "fastboot.exe flash recovery twrp.img" shows the return message "< waiting for device >"
I have tested various Tools and Images "Minimal ADB and Fastboot", "fastboots", "TWRP_2.8.7.x_P8Lite_kirin_v2.img", "RecoveryTwrpV3.0.2".
I habe always the same problem.
Please, can help me anyone?
Build: ALE-L21C432B612
EMUI: 4.0.3
Android 6.0
thanks.
forumarbeit said:
I have unlocked my bootloader and want installed twarp with fastboot.
I start zhe bootloader with "adb.exe reboot-bootloader"
It do not run, after start on CMD-prompt "fastboot.exe flash recovery twrp.img" shows the return message "< waiting for device >"
I have tested various Tools and Images "Minimal ADB and Fastboot", "fastboots", "TWRP_2.8.7.x_P8Lite_kirin_v2.img", "RecoveryTwrpV3.0.2".
I habe always the same problem.
Please, can help me anyone?
Build: ALE-L21C432B612
EMUI: 4.0.3
Android 6.0
thanks.
Click to expand...
Click to collapse
Fastboot devices detect your phone in fastboot mode?
Did You install hisuite app for fastboot drivers?
Sent from my Motorola Moto G (5S) using XDA Labs
Adi5 said:
Fastboot devices detect your phone in fastboot mode?
Did You install hisuite app for fastboot drivers?
Sent from my Motorola Moto G (5S) using XDA Labs
Click to expand...
Click to collapse
I have installed on my PC the HiSuite from Huawei and the Universal Adb Driver.
Need I here special drivers?
forumarbeit said:
I have installed on my PC the HiSuite from Huawei and the Universal Adb Driver.
Need I here special drivers?
Click to expand...
Click to collapse
I have still allways the same Problem with rooing from my P8 lite.
I got today a new update with EMUI 4.03.
After the update I got the message that my phone is rooted and it is dangerous.
Root checker basic shows the message "Sorry! Root access is not proberly installrd on this device"
SuperSU shows the message "Root undetected"
How can I root my P8 Lite correct? who can help me?
many thanks.
Sorry for asking:
1.Does your USB cable/port work good?
What does fastboot devices command says are your devices listed?
2.Does your bootloader truly unlocked?(i running ALE-L21C432B614 and bootloader writes unlocked even if locked i think its a bug)
What is the current output of fastboot oem unlock <your bootloader unlock code>?
spaceship said:
Sorry for asking:
1.Does your USB cable/port work good?
What does fastboot devices command says are your devices listed?
2.Does your bootloader truly unlocked?(i running ALE-L21C432B614 and bootloader writes unlocked even if locked i think its a bug)
What is the current output of fastboot oem unlock <your bootloader unlock code>?
Click to expand...
Click to collapse
I think the USB-Port and cable is ok.
1.) Is start my P8 lite with comand "adb.exe reboot bootloader" in fastboot&rescue mode.
The P8 lite screen shows:
"fastboot&rescue mode
Please connect Usb Cable to your Computer and Open Hisuite
More Information:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
reboot_enter_fastboot_common_func
green Android Picture
Phone Unlocked
Keep Pressing Volume Up to Exit this Mode"
2.) I will download the twrp with command "fastboot flash recovery twrp.img"
twrp.img is "RecoveryTwrpV3.0.2.img".
3.) after start the fastboot command shows the prompt the following messages
"C:\fastboot flash recovery twrp.img
< waiting for device >"
and nothing happens anymore.
The UniversalAdbDriverSetup.msi Drivers are installed on my PC.
My current Phone Build: ALE-L21C432B614
EMUI: 4.0.3
Android 6.0
I have no a solution for my problem for root my phone.
Go to fastboot mod and after you see the fastboot&Rescue mod screen run this command in your pc:
fastboot devices
If fastboot detects your phone you should see your serial number.
If not you probably will see nothing in the command line on your PC.
Give me the output please
can you please tell me how can i get build number using adb bootl loader
forumarbeit said:
I have unlocked my bootloader and want installed twarp with fastboot.
I start zhe bootloader with "adb.exe reboot-bootloader"
It do not run, after start on CMD-prompt "fastboot.exe flash recovery twrp.img" shows the return message "< waiting for device >"
I have tested various Tools and Images "Minimal ADB and Fastboot", "fastboots", "TWRP_2.8.7.x_P8Lite_kirin_v2.img", "RecoveryTwrpV3.0.2".
I habe always the same problem.
Please, can help me anyone?
Build: ALE-L21C432B612
EMUI: 4.0.3
Android 6.0
thanks.
Click to expand...
Click to collapse
Works for ALE-L23?!
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?
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Stevie123 said:
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Click to expand...
Click to collapse
Reboot to fastboot using
adb reboot fastboot
Click to expand...
Click to collapse
Then, try to use fastboot cmd
Thanks, before I can try that I have to solve another problem.
That doesn't work. The phone isn't entering a special mode. I can choose fastboot from the bootmenu, too. But nothing happens. The phone does a restart, shows the bootmenu again and boots android after 5 seconds.
@Stevie123
You need to enable fastboot (bootloader) mode since it is disabled by ZTE, so that the selection from menu to be effective (after enabling it, in fastboot mode, your command "fastboot devices" (to check) and "fastboot oem lock" (to lock bootloader) will be accepted).
You can use Axon 7 EDL tool to unlock the bootloader.
It's already unlocked. I have to make another unlock procedure again to get access to fastboot? The EDL Tool tells me that I have to wipe and reset the phone after it. So it seems I can't keep my data and just lock the bootloader.
Either Lock or Unlock will wipe your data. And yes, the unlock procedure by Axon 7 EDL tool includes the enabling of fastboot. So you have to re-unlock if you want to relock.
I think this EDL tool doesn't work very good. It flashed something to make fastboot available, but I had a green ZTE Logo screen and this screen also had errors like white spots. The original ZTE logo is in cyan. But the fastboot worked and I could lock the phone. But I couldn't do anything else anymore. I couldn't reach Android and reflashing also didn't work. So I tried to use the EDL Tool to unlock my bootloader again. It said success, but it didn't work. It was still locked.
Well, I had to wait until the phone was empty. Luckily I could reach EDL Mode again. I used the MiFlash again to Downgrade to Android Nougat B12. I read somewhere that the fastboot is included there. So I had the right ZTE Logo back and it worked. I could leave the Bootloader locked. The final update I did with a SD Card to the lastest Android Software for Axon 7. Luckily without a brick. It's a pity that they don't offer any Updates anymore.