Related
Hello, I received my Zuk Z1 with Zui rom two days ago and managed to install Cyanogen Os with threads here.
My problem is that OTA updates are downloaded but do not apply. Phone restarts to cm recovery and nothing happens. Any idea?
Glops4 said:
Hello, I received my Zuk Z1 with Zui rom two days ago and managed to install Cyanogen Os with threads here.
My problem is that OTA updates are downloaded but do not apply. Phone restarts to cm recovery and nothing happens. Any idea?
Click to expand...
Click to collapse
Hi, Factory data reset, after that update OTA again!
Thanks for your help. I did a factory reset, still nothing. Also from recovery, then rebooted, and the OTA failed. Then I found out that kingroot was still there! Unrooted from the app, rebooted and it disappeared.
But OTA is still not working. I went in developper option and saw that bootloader is locked. impossible to unlock it. Even with fastboot commands. I am stuck with this preliminary version for now. How to unlock the bootloader now?
Glops4 said:
Thanks for your help. I did a factory reset, still nothing. Also from recovery, then rebooted, and the OTA failed. Then I found out that kingroot was still there! Unrooted from the app, rebooted and it disappeared.
But OTA is still not working. I went in developper option and saw that bootloader is locked. impossible to unlock it. Even with fastboot commands. I am stuck with this preliminary version for now. How to unlock the bootloader now?
Click to expand...
Click to collapse
Hi Glops, click my Google+ profile link in my signature and message me on Hangouts. I will be happy to help out
Ota is working again. I had to re-convert the z1 to cyanogen with the convert rom, cm recovery and adb.
Please DO NOT root your z1 with KINGROOT!!
It will mess up your system and your bootloader.
Glops4 said:
Ota is working again. I had to re-convert the z1 to cyanogen with the convert rom, cm recovery and adb.
Please DO NOT root your z1 with KINGROOT!!
It will mess up your system and your bootloader.
Click to expand...
Click to collapse
Hi, I did same think as you. Rooted my phone with KingRoot and now OTA updates not working. Can you please write a "How-to" to recover my Zuk? I would be very thankfull.
You have to follow this tutorial here and you will get back the OTA updates.
Thank you, i will try it. I'm just trying download all necessary files, but stumbled upon driver downloads. Whole site is in chinese and cannot download anything. If you have those drivers, can you please upload them somewhere? Thx.
And one thing, since i have the international version, which have original CM OS installed (not ZUI), doesnt it mess something on phone?
Cyanogen preview
In my device it show cyanogen preview 12.1 yoga4pap1cg,
Any one guide me how to remove the same
How should bootloader screen looks like on ZUK?
When i restart to Bootloader (adb reboot bootloader or directly from phone) all i can see is logo "ZUK" in the middle and "Powered by Android" in the bottom. And I think this is the problem, since fastboot devices not showing anything. Also fastboot -i 0x2b4c oem get-device-info get stuck on three dots and nothing happens.
In this mode i can see the my phone in device manager as ShenQi Composite ADB Interface.
Yes bootloader screen looks just like yours. If you can boot to bootloader, then you do not need more drivers.
This is how I proceeded, with Cyanogen Os installed and wanting to get rid of Kingroot (for each one having the same problem):
You don't need ShenQi drivers if you proceed this way and you can uninstall them to just auto install Android ADB Interface.
- Enable usb debugging in developpers option
- 1st get the Rsa authorisation. For that download Kingroot for windows, install and run in your computer. Attach device and press blue button. accept "always accept this device" in your phone and close Kingroot
- Detach the phone
- Shut down the phone
- Press volume down and power button, you will open a menu
- attach device to the computer
- open a terminal in windows
- check the exact adress you see, for example C:\Users\Glops4>
- Open Windows Explorer in your computer
- Copy the following files to the same directory you see in terminal: z1.cyanogen.convert.signed.zip , z1.recovery.testkeys.img (you have to rename extension to .img by yourself)
- In terminal, type : "adb devices"
- You should see your device listed
- then type "adb reboot bootloader"
- Zuk screen will remain
- Do not write "fastboot -i 0x2b4c oem get-device-info"
- Skip checking if bootloader is unlocked
- write "fastboot -i 0x2b4c boot z1.recovery.testkeys.img"
- Go back to your phone, you should be in CM Recovery
- "Wipe data/factory reset"
- "Apply update"
- "Apply from ADB"
- Back to terminal on the computer
- "adb sideload z1.cyanogen.convert.signed.zip"
- Wait to completion (very long)
- Do all the updates
- Root?????
____________
(Remix of Modaco tutorial)
Glops4 said:
Yes bootloader screen looks just like yours. If you can boot to bootloader, then you do not need more drivers.
This is how I proceeded, with Cyanogen Os installed and wanting to get rid of Kingroot (for each one having the same problem):
You don't need ShenQi drivers if you proceed this way and you can uninstall them to just auto install Android ADB Interface.
- Enable usb debugging in developpers option
- 1st get the Rsa authorisation. For that download Kingroot for windows, install and run in your computer. Attach device and press blue button. accept "always accept this device" in your phone and close Kingroot
- Detach the phone
- Shut down the phone
- Press volume down and power button, you will open a menu
- attach device to the computer
- open a terminal in windows
- check the exact adress you see, for example C:\Users\Glops4>
- Open Windows Explorer in your computer
- Copy the following files to the same directory you see in terminal: z1.cyanogen.convert.signed.zip , z1.recovery.testkeys.img (you have to rename extension to .img by yourself)
- In terminal, type : "adb devices"
- You should see your device listed
- Adb reboot bootloader
- Zuk screen will remain
- Do not write "fastboot -i 0x2b4c oem get-device-info"
- Skip checking if bootloader is unlocked
- write "fastboot -i 0x2b4c boot z1.recovery.testkeys.img"
- Go back to your phone, you should be in CM Recovery
- "Wipe data/factory reset"
- "Apply update"
- "Apply from ADB"
- Back to terminal on the computer
- "adb sideload z1.cyanogen.convert.signed.zip"
- Wait to completion (very long)
- Do all the updates
- Root?????
____________
(Remix of Modaco tutorial)
Click to expand...
Click to collapse
HI, just to clarify some thinks:
- Press volume down and power button, you will open a menu - this way i boot into EDL menu, right? With the test board, etc...
- Copy the following files... - I have those files named exactly as you mentioned. So which extensions should i change to img? I have ...testkeys.img and ...signed.zip
- fastboot -i 0x2b4c boot z1.recovery.testkeys.img - i once tried this (but booted to bootloader from CM, not from EDL) and its failed to load the file (something about not signed?)
And which exact drivers should I use? Can you please post a link?
- Press volume down and power button, you will open a menu - this way i boot into EDL menu, right? With the test board, etc...
Click to expand...
Click to collapse
Right
- Copy the following files... - I have those files named exactly as you mentioned. So which extensions should i change to img? I have ...testkeys.img and ...signed.zip
Click to expand...
Click to collapse
Those are ok, do not change anything
- fastboot -i 0x2b4c boot z1.recovery.testkeys.img - i once tried this (but booted to bootloader from CM, not from EDL) and its failed to load the file (something about not signed?)
And which exact drivers should I use? Can you please post a link?
Click to expand...
Click to collapse
I think your drivers are ok, please try as I said and you should be fine
Glops4 said:
Right
Those are ok, do not change anything
I think your drivers are ok, please try as I said and you should be fine
Click to expand...
Click to collapse
End up with error:
Code:
C:\android-sdk-windows\platform-tools>Adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot -i 0x2b4c boot z1.recovery.testkeys.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.390s
Any idea?
Need to flash again CM, cuz with Kingroot/Root you can't update over OTA. I hope CyanogenMod will release soon.
Gesendet von meinem Z1 mit Tapatalk
vr43x3m said:
End up with error:
Code:
C:\android-sdk-windows\platform-tools>Adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot -i 0x2b4c boot z1.recovery.testkeys.img
downloading 'boot.img'...
OKAY [ 0.374s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.390s
Any idea?
Click to expand...
Click to collapse
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
vr43x3m said:
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
Click to expand...
Click to collapse
This is the same with the Yu Yunique and Wileyfox Swift phone, which also run CyanogenOS, can someone explain why its unlock-go and not just unlock as for other phones?
othe01 said:
This is the same with the Yu Yunique and Wileyfox Swift phone, which also run CyanogenOS, can someone explain why its unlock-go and not just unlock as for other phones?
Click to expand...
Click to collapse
To answer my own question, if we look in the android kernel sources (aboot.c) we find:
Code:
void cmd_oem_unlock(const char *arg, void *data, unsigned sz)
{
if(!is_allow_unlock) {
fastboot_fail("oem unlock is not allowed");
return;
}
display_fbcon_message("Oem Unlock requested");
fastboot_fail("Need wipe userdata. Do 'fastboot oem unlock-go'");
}
void cmd_oem_unlock_go(const char *arg, void *data, unsigned sz)
{
if(!device.is_unlocked || device.is_verified)
{
if(!is_allow_unlock) {
fastboot_fail("oem unlock is not allowed");
return;
}
device.is_unlocked = 1;
device.is_verified = 0;
write_device_info(&device);
struct recovery_message msg;
snprintf(msg.recovery, sizeof(msg.recovery), "recovery\n--wipe_data");
write_misc(0, &msg, sizeof(msg));
fastboot_okay("");
reboot_device(RECOVERY_MODE);
}
fastboot_okay("");
}
The difference between "oem unlock" and "oem unlock-go" seems to be that the unlock-go one also wipes out the userdata; No idea why it is needed tho.
vr43x3m said:
Finally got it. Apparently the option to unlock bootloader in phone do nothing. I must used "fastboot -i 0x2b4c oem unlock-go". So its finally uploading the image. Thank for all your informations.
Click to expand...
Click to collapse
Good job mate, thanks for the info.
Hello i have the same problem. Im not techy guy i dont know to do it. Anyone who can help me? Please
Hello, I would like to unlock bootloader on my nokia 6 (2017) TA-1033 Android Pie 9.0
First of all, I tested the official unlock but, the application tells me that my device is not supported...
I'm looking on the forum but I can't find a method for unlock bootlaoder and install twrp (then magisk for the root if supported)
Thank you very much for your help !
Are you from Mars?
Sent from my TA-1021 using Tapatalk
Loknic4 said:
Are you from Mars?
Sent from my TA-1021 using Tapatalk
Click to expand...
Click to collapse
Not far away, a planet nearby...
After some research, apparently, there is no longer any free way to unlock the bootloader....
So I went to the cash register hoping it would be reliable XD.
For information, I still contacted nokia support
Dear,
Greetings from Nokia mobile care!
Regarding to your question I would like to inform you that it was only available for a brief period of time and is currently unavailable.
Please, this feature can be unlocked after the update. For now we would like to ask you for your patient, for sure soon will be bootloader unlocked for your model!
Please check this! This is our official website and you can learn more about that!
https://www.nokia.com/phones/en_int/bootloader
If you will have more questions feel free to contact us again.
Have a nice day.
Best regards
Melody Fichte
[email protected] Mobile Care
Click to expand...
Click to collapse
"for sure soon will be bootloader unlocked for your model!"
arl0ng said:
For information, I still contacted nokia support
"for sure soon will be bootloader unlocked for your model!"
Click to expand...
Click to collapse
Don't trust it
Elvaa said:
Don't trust it
Click to expand...
Click to collapse
Yes, I also have doubts, I'm waiting, anyway, my key to unlock the bootloader
Envoyé de mon TA-1033 en utilisant Tapatalk
Bootloader of my successfully unlocked Nokia 6.0 !
I just had a driver problem on my computer.
If you are in the same case, my problem has been solved by installing "OST tool" :
https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
run the "launcher.exe" and restart computer
Thanks Techmesto for the key.
arl0ng said:
Bootloader of my successfully unlocked Nokia 6.0 !
I just had a driver problem on my computer.
If you are in the same case, my problem has been solved by installing "OST tool" :
https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
run the "launcher.exe" and restart computer
Thanks Techmesto for the key.
Click to expand...
Click to collapse
Wanna share the key and instructions?
skooter32 said:
Wanna share the key and instructions?
Click to expand...
Click to collapse
Hello, for the key, I had to buy it on techmesto (thanks to him for the tutorial)
regarding instructions :
Grab the June 2018 OTA file from here => https://android.googleapis.com/pack.../2a84fb0cddebb6ed79e18735740c7386ebd4be1f.zip
Download the full firmware for Nokia 6 => https://drive.google.com/open?id=1twEoVIImRHeFdJ6OQSG4tfkEvtrY_0uJ
Download and install the NOST Tool => https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Download and install OST Tool => https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
(about me, it solved the problem of unrecognized devices)
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Connect the phone to the usb port
Copy June 2018 OTA file to SD Card
You will need the platform-tools from the Android SDK on your computer ==> https://developer.android.com/studio/releases/platform-tools
Or use Minimal ADB ==> https://forum.xda-developers.com/showthread.php?t=2317790
On the computer, navigate to ADB’s folder and open a Command Prompt and type:
Code:
adb devices
check if the device is detected correctly
Code:
adb reboot recovery
If you see a “No Command” screen ==> Press and hold Power key and quickly press and release the Volume Up key
Select apply update from SD card and select the update file (June 2018 OTA)
When the update gives an error, reboot to bootloader by selecting the option from recovery mode
Code:
fastboot devices
check if the device is detected correctly
Now use the unlock key to unlock. Do normal unlock and also critical unlock.
Code:
fastboot flash unlock UnlockFile.bin
(UnlockFile.bin = name of the dedication key you purchased and it's easier to place it in the same folder as platform-tools)
Code:
fastboot oem unlock-go
fastboot flash unlock UnlockFile.bin
fastboot flashing unlock_critical
fastboot reboot
If it doesn't reboot, open NOST and flash the full firmware (nb0)
Warning: the battery must be sufficiently charged for NOST
arl0ng said:
Hello, for the key, I had to buy it on techmesto (thanks to him for the tutorial)
regarding instructions :
Grab the June 2018 OTA file from here => https://android.googleapis.com/pack.../2a84fb0cddebb6ed79e18735740c7386ebd4be1f.zip
Download the full firmware for Nokia 6 => https://drive.google.com/open?id=1twEoVIImRHeFdJ6OQSG4tfkEvtrY_0uJ
Download and install the NOST Tool => https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Download and install OST Tool => https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
(about me, it solved the problem of unrecognized devices)
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Connect the phone to the usb port
Copy June 2018 OTA file to SD Card
You will need the platform-tools from the Android SDK on your computer ==> https://developer.android.com/studio/releases/platform-tools
Or use Minimal ADB ==> https://forum.xda-developers.com/showthread.php?t=2317790
On the computer, navigate to ADB’s folder and open a Command Prompt and type:
Code:
adb devices
check if the device is detected correctly
Code:
adb reboot recovery
If you see a “No Command” screen ==> Press and hold Power key and quickly press and release the Volume Up key
Select apply update from SD card and select the update file (June 2018 OTA)
When the update gives an error, reboot to bootloader by selecting the option from recovery mode
Code:
fastboot devices
check if the device is detected correctly
Now use the unlock key to unlock. Do normal unlock and also critical unlock.
Code:
fastboot flash unlock UnlockFile.bin
(UnlockFile.bin = name of the dedication key you purchased and it's easier to place it in the same folder as platform-tools)
Code:
fastboot oem unlock-go
fastboot flash unlock UnlockFile.bin
fastboot flashing unlock_critical
fastboot reboot
If it doesn't reboot, open NOST and flash the full firmware (nb0)
Warning: the battery must be sufficiently charged for NOST
Click to expand...
Click to collapse
sorry for taking so long in getting bk to u i decided to get rid of this device and got a pixel 3 xl thanks.
stupid Nokia, why bother rooting this with a pay service!
and a bunch of instruction, waste of time!
I own a xiaomi 9 se for unlocking BL just take a week, oneplus 6 just need a second!
I'm not saying anything about techmesto, but I do not know them. Man, do you know the damage someone can do with an IMEI and S/N? Damn Nokia.
arl0ng said:
Hello, for the key, I had to buy it on techmesto (thanks to him for the tutorial)
regarding instructions :
Grab the June 2018 OTA file from here => https://android.googleapis.com/pack.../2a84fb0cddebb6ed79e18735740c7386ebd4be1f.zip
Download the full firmware for Nokia 6 => https://drive.google.com/open?id=1twEoVIImRHeFdJ6OQSG4tfkEvtrY_0uJ
Download and install the NOST Tool => https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Download and install OST Tool => https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
(about me, it solved the problem of unrecognized devices)
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Connect the phone to the usb port
Copy June 2018 OTA file to SD Card
You will need the platform-tools from the Android SDK on your computer ==> https://developer.android.com/studio/releases/platform-tools
Or use Minimal ADB ==> https://forum.xda-developers.com/showthread.php?t=2317790
On the computer, navigate to ADB’s folder and open a Command Prompt and type:
Code:
adb devices
check if the device is detected correctly
Code:
adb reboot recovery
If you see a “No Command” screen ==> Press and hold Power key and quickly press and release the Volume Up key
Select apply update from SD card and select the update file (June 2018 OTA)
When the update gives an error, reboot to bootloader by selecting the option from recovery mode
Code:
fastboot devices
check if the device is detected correctly
Now use the unlock key to unlock. Do normal unlock and also critical unlock.
Code:
fastboot flash unlock UnlockFile.bin
(UnlockFile.bin = name of the dedication key you purchased and it's easier to place it in the same folder as platform-tools)
Code:
fastboot oem unlock-go
fastboot flash unlock UnlockFile.bin
fastboot flashing unlock_critical
fastboot reboot
If it doesn't reboot, open NOST and flash the full firmware (nb0)
Warning: the battery must be sufficiently charged for NOST
Click to expand...
Click to collapse
arl0ng said:
Hello, for the key, I had to buy it on techmesto (thanks to him for the tutorial)
regarding instructions :
Grab the June 2018 OTA file from here => https://android.googleapis.com/pack.../2a84fb0cddebb6ed79e18735740c7386ebd4be1f.zip
Download the full firmware for Nokia 6 => https://drive.google.com/open?id=1twEoVIImRHeFdJ6OQSG4tfkEvtrY_0uJ
Download and install the NOST Tool => https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Download and install OST Tool => https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
(about me, it solved the problem of unrecognized devices)
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Connect the phone to the usb port
Copy June 2018 OTA file to SD Card
You will need the platform-tools from the Android SDK on your computer ==> https://developer.android.com/studio/releases/platform-tools
Or use Minimal ADB ==> https://forum.xda-developers.com/showthread.php?t=2317790
On the computer, navigate to ADB’s folder and open a Command Prompt and type:
Code:
adb devices
check if the device is detected correctly
Code:
adb reboot recovery
If you see a “No Command” screen ==> Press and hold Power key and quickly press and release the Volume Up key
Select apply update from SD card and select the update file (June 2018 OTA)
When the update gives an error, reboot to bootloader by selecting the option from recovery mode
Code:
fastboot devices
check if the device is detected correctly
Now use the unlock key to unlock. Do normal unlock and also critical unlock.
Code:
fastboot flash unlock UnlockFile.bin
(UnlockFile.bin = name of the dedication key you purchased and it's easier to place it in the same folder as platform-tools)
Code:
fastboot oem unlock-go
fastboot flash unlock UnlockFile.bin
fastboot flashing unlock_critical
fastboot reboot
If it doesn't reboot, open NOST and flash the full firmware (nb0)
Warning: the battery must be sufficiently charged for NOST
Click to expand...
Click to collapse
can u tell, about the key sir?
arl0ng said:
Hello, for the key, I had to buy it on techmesto (thanks to him for the tutorial)
regarding instructions :
Grab the June 2018 OTA file from here => https://android.googleapis.com/pack.../2a84fb0cddebb6ed79e18735740c7386ebd4be1f.zip
Download the full firmware for Nokia 6 => https://drive.google.com/open?id=1twEoVIImRHeFdJ6OQSG4tfkEvtrY_0uJ
Download and install the NOST Tool => https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
Download and install OST Tool => https://drive.google.com/open?id=1-iwfKu7PHygVV5Ok4_lSibCW4ATeFpBu
(about me, it solved the problem of unrecognized devices)
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging.
Connect the phone to the usb port
Copy June 2018 OTA file to SD Card
You will need the platform-tools from the Android SDK on your computer ==> https://developer.android.com/studio/releases/platform-tools
Or use Minimal ADB ==> https://forum.xda-developers.com/showthread.php?t=2317790
On the computer, navigate to ADB’s folder and open a Command Prompt and type:
Code:
adb devices
check if the device is detected correctly
Code:
adb reboot recovery
If you see a “No Command” screen ==> Press and hold Power key and quickly press and release the Volume Up key
Select apply update from SD card and select the update file (June 2018 OTA)
When the update gives an error, reboot to bootloader by selecting the option from recovery mode
Code:
fastboot devices
check if the device is detected correctly
Now use the unlock key to unlock. Do normal unlock and also critical unlock.
Code:
fastboot flash unlock UnlockFile.bin
(UnlockFile.bin = name of the dedication key you purchased and it's easier to place it in the same folder as platform-tools)
Code:
fastboot oem unlock-go
fastboot flash unlock UnlockFile.bin
fastboot flashing unlock_critical
fastboot reboot
If it doesn't reboot, open NOST and flash the full firmware (nb0)
Warning: the battery must be sufficiently charged for NOST
Click to expand...
Click to collapse
Thanks for the super indepth guide! I've been waiting for years now for HMD to release the bootloader unlock tool for the OG phones, but that's clearly never gonna happen. Techmesto charges 8 dollars for the key and the downgrade + unlock, but 5 dollars for just the key. So I think I'll follow your guide to downgrade and then purchase the key from them afterwards.
I'm trying to install Google camera.. on trying to enable camera2api by adb method, PC isn't recognizing device at fastboot.. "adb devices " isn't showing any device.. what should I do ?
Can you be more specific. Which instructions are you following? Did you follow all the steps mentioned in it properly?
Method i followed
Power off your phone and enter the bootloader mode. (Hold power and volume down when booting to enter the bootloader screen.)
Open up a command prompt or PowerShell (Windows) or terminal window (macOS or Linux) in the same directory where the fastboot binary is located.
Enter the following command based on your OS:
Windows Command Prompt: fastboot oem enable_camera_hal3 true
Windows PowerShell: .\fastboot oem enable_camera_hal3 true
macOS or Linux Terminal: ./fastboot oem enable_camera_hal3 true
Reboot your device.
Now download the best Google Camera port for your Asus ZenFone Max Pro M1 either from our Hub or from the XDA forum.
I did exactly as above... Windows Powershell isn't recognizing device at fastboot..
.\fastboot oem enable_camera_hal3 true shows waiting for device
Krishjith said:
Power off your phone and enter the bootloader mode. (Hold power and volume down when booting to enter the bootloader screen.)
Open up a command prompt or PowerShell (Windows) or terminal window (macOS or Linux) in the same directory where the fastboot binary is located.
Enter the following command based on your OS:
Windows Command Prompt: fastboot oem enable_camera_hal3 true
Windows PowerShell: .\fastboot oem enable_camera_hal3 true
macOS or Linux Terminal: ./fastboot oem enable_camera_hal3 true
Reboot your device.
Now download the best Google Camera port for your Asus ZenFone Max Pro M1 either from our Hub or from the XDA forum.
I did exactly as above... Windows Powershell isn't recognizing device at fastboot..
.\fastboot oem enable_camera_hal3 true shows waiting for device
Click to expand...
Click to collapse
Check whether the drivers are correctly installed. Go to device manager on your desktop / laptop and check whether your phone is showing on the list. If not first install the drivers than follow the above mentioned steps.
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
Unable to unlock bootloader for realme2pro .
Phone details :
Device Name : RealMe 2pro
Realme UI version : V1.0 | RMX1801EX_11_F.12
Model : RMX1801
Kernel Version : 4.4.194
ColorOS Version : V7
The app recommended by many websites which is "INdepth testing" to apply and after some time it enables the phone to unlock app is not working tried a lot of app for various sources link provided none are working, the app crashes on the phone after clicking on the apply button.
After that used the adb command line on windows 10 where after typing the commands :
-adb devices ==> it shows device connected
-adb bootloader reboot ==> reboots the phone into the fastboot
-fastboot flashing unlock ==> This is the where problem is after typing this command the output in the command prompt is
< wating for any device >
Click to expand...
Click to collapse
and it keeps on like this while nothing also happens on the phone it is on their in the fast boot menu.
after some time clicking on the "start" it boots the phone into normal as it was.
Same Problem
You have to make sure you've fastboot.exe in the same folder.
Type fastboot devices to verify that your device is detected
abhish3k9 said:
You have to make sure you've fastboot.exe in the same folder.
Type fastboot devices to verify that your device is detected
Click to expand...
Click to collapse
I have fastboot.exe on platform tools. However, after using the second command when it reboots to the bootloader page. The device is not shown in the list of devices.