Database Develop

trouble with bootloader unlock

Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.

KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done

KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.

Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app

I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.

sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd

Stuck in Teamwin after system restore

I just gave my KF HD 7" to my friend and he wanted me to set it back up as a KF since i had Cyanogen Mod cm-12.1-20160126-NIGHTLY installed on it but haven't used it in a while (read 1-2 years). He was messing around with it before i could get to it and thought hitting Restore to Factory settings would fix it. The device is now stuck on a flashing teamwin logo screen and wont go any further no matter what i've tried. My computer wont recognize the kindle to let me in from cmd so i've reached the limits of my modding knowledge. Could someone please point me in the right direction so i can fix this for him.

If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)

Or once you get fastboot working you could use the SRT tool to flash it back to stock with root.

install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?

TheN3wguy said:
install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?
Click to expand...
Click to collapse
Are you running Windows 8, 8.1, or 10?
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Are you running Windows 8, 8.1, or 10?
Click to expand...
Click to collapse
Oh god sorry i thought i had said im running windows 10

TheN3wguy said:
Oh god sorry i thought i had said im running windows 10
Click to expand...
Click to collapse
No worries. All you need to do to get the fastboot drivers to install is to follow these instructions to temporarily disable driver signature enforcement. Once you've done that, install the drivers and reboot. After that, fastboot should recognize the kindle.

Above steps worked and KF is now working correctly thanks!

monster1612 said:
If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)
Click to expand...
Click to collapse
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after

AndroidLove231 said:
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after
Click to expand...
Click to collapse
Once you're in fastboot mode (rebooting into the bootloader from Android, for example), does fastboot -i 0x1949 devices show that the Kindle's connected?

Stuck in everything, need help

I have tried toolbox after installed amazon fire's driver, it says no device was found, tried changing usb configuration, nothing works
I have tried installing twrp recovery in fastboot mode, it says FAILED (remote: the command you input is restricted on locked hw), tried typing fastboot oem unlock, it STILL says failed
I really want to root, install twrp recovery
I need help with this

mkjhwvsrb said:
I have tried toolbox after installed amazon fire's driver, it says no device was found, tried changing usb configuration, nothing works
I have tried installing twrp recovery in fastboot mode, it says FAILED (remote: the command you input is restricted on locked hw), tried typing fastboot oem unlock, it STILL says failed
I really want to root, install twrp recovery
I need help with this
Click to expand...
Click to collapse
What device? You are likely going to have to unlock VIA the hardware method. Is it a fire 7 (2019)? Then start here, hardware method....
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
If you are not sure, run a adb shell and it should show the device.

Michajin said:
What device? You are likely going to have to unlock VIA the hardware method. Is it a fire 7 (2019)? Then start here, hardware method....
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
If you are not sure, run a adb shell and it should show the device.
Click to expand...
Click to collapse
Yes it's fire 7 9th generation I don't have a Linux I don't know anything....

mkjhwvsrb said:
Yes it's fire 7 9th generation I don't have a Linux I don't know anything....
Click to expand...
Click to collapse
Download a live disk, make a live disk on a flash drive. Reboot and boot from the live disk. Follow the steps for unlocking. Here is Ubuntu for example...
https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started

boot loader will not unlock

In the past I have unlocked the boot loaders for Pixel, Pixel 2 and Pixel 3 always on first try and I know how to do it. But my new Pixel 5, US unlocked version, arrived today, will not boot loader unlock. I have dev options enabled, USB debugging on, and allow OEM unlock set on. I'm using a Mac so my fastboot commands are ./fastboot___. With the Pixel 5 in fastboot mode, ./fastboot devices gives a correct response, the device responds with its serial number. But then with ./fastboot flashing unlock nothing happens. Just sits there. When I give the command the terminal cursor moves down to the next line but there is no response from the device. I've turned off, rebooted, repeated multiple times, same result. I tried the old ./fastboot oem unlock and that does not work either (as expected).
Has anyone else encountered this? Advice?

Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!

Michael1200 said:
Using latest adb/fastboot? I had problems flashing/unlocking the device because I tried it with an old adb/fastboot version.
If that doesn't help then try using another computer. Often windows doesn't (I know you're probably using mac) correctly recognize devices in fastboot mode, which is why you have to manually add google drivers in windows device manager if 'fastboot devices' doesn't detect the device.
Good luck!
Click to expand...
Click to collapse
Thanks, Michael. I am using the latest SDK with current platform-tools, and don't have another computer. Tried several different cables, no luck. However, I've decided to forgo unlocking the BL and just set it up locked. I no longer use root nor custom ROMs and future TWRP is very unlikely so I'm going to stay boot loader locked for the first time in many years. Will see how it goes. I really have not needed/used it since OS10.
Thanks again.

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.