Hi, I'm trying to unlock my phone so I can install Kali Linux on my A466BG. I've read a lot on the web but came to a problem. I've got Android SDK on my PC and installed platform-tools. My device shows up after entering "adb devices." I've enabled developer mode and usb debugging and OEM unlocking. My problem is...I can't unlock the bootloader and use fastboot. After pressing power and up volume I get into the menu (and I actually reset my phone to factory settings so I'll have more space) but I can't find bootloader. My phone shows up fine on my PC and under devices, but when I switch to the other menu (with reset options) it doesn't show up anymore. Not even under "adb devices." I tried entering "adb reboot-bootloader" but it just restarts and goes to the normal android phone screen. I tried "fastboot -i 0x1bbb oem device-info" and it says "waiting for device." I'm not sure how to boot into fastboot and unlock my bootloader. Or why my phone doesn't show up on my PC after pressing power and up volume. Please reply with instructions. Thank you
Hi, me again. I found a video on YouTube on how to install Kali Nethunter on Android phones. I got it and now I'm installing Metasploit. It's just the command line but that should work. Check You Tube on "Nethunter without root" if you want to know. Thanks
I'm back...Not satisfied with Nethunter on Termux. I would like to know how to root the phone and install Kali. Can anyone look at the above question and reply with how to root my Alcatel A466BG? I'll check back tomorrow. Thanks in advance!
Related
unlocking a bootloader is not a piece of cake. You will need to go through some programming codes and you will need to be cautious. Before we proceed further you must remember that doing this will void the warranty of your LG G pro 2 and you yourself will be responsible for any damage.
1. Download Android SDK and install it. It is easily available on internet from any source, install all Google USB drivers.
2. Enable USB debugging as shown in the steps while rooting your device.
3. Plug in the USB cable into your Smartphone and connect it with your PC.
4. Type adb devices > adb reboot bootloader > fastboot devices > fastboot oem unlock.
You have to insert all the commands shown above in the same sequence. Let me make you understand the meaning of these commands.
adb devices: This command will check and navigate whether your device is plugged in and revealed in SDK.
adb reboot bootloader: This command reboots your Smartphone into bootloader.
fastboot devices: This command double checks that your LG G pro 2 is connected.
fastboot oem unlock: This is the final command which will make your device to unlock bootloader.
After typing this command, on you Smartphone a confirmation screen will be shown. You just have to press Volume Up button for yes and Power off button to confirm.
Now you have to just restart your device and your bootloader will be unlocked. Kindly use these tricks with extra care and don’t worry all these tricks are safe and already experimented
What is your opinion on this topic?
unlock already!?
meshk said:
unlocking a bootloader is not a piece of cake. You will need to go through some programming codes and you will need to be cautious. Before we proceed further you must remember that doing this will void the warranty of your LG G pro 2 and you yourself will be responsible for any damage.
1. Download Android SDK and install it. It is easily available on internet from any source, install all Google USB drivers.
2. Enable USB debugging as shown in the steps while rooting your device.
3. Plug in the USB cable into your Smartphone and connect it with your PC.
4. Type adb devices > adb reboot bootloader > fastboot devices > fastboot oem unlock.
You have to insert all the commands shown above in the same sequence. Let me make you understand the meaning of these commands.
adb devices: This command will check and navigate whether your device is plugged in and revealed in SDK.
adb reboot bootloader: This command reboots your Smartphone into bootloader.
fastboot devices: This command double checks that your LG G pro 2 is connected.
fastboot oem unlock: This is the final command which will make your device to unlock bootloader.
After typing this command, on you Smartphone a confirmation screen will be shown. You just have to press Volume Up button for yes and Power off button to confirm.
Now you have to just restart your device and your bootloader will be unlocked. Kindly use these tricks with extra care and don’t worry all these tricks are safe and already experimented
What is your opinion on this topic?
Click to expand...
Click to collapse
if our phone's bootloader can be unlock, we can have twrp now??
false information.
meshk said:
unlocking a bootloader is not a piece of cake. You will need to go through some programming codes and you will need to be cautious. Before we proceed further you must remember that doing this will void the warranty of your LG G pro 2 and you yourself will be responsible for any damage.
1. Download Android SDK and install it. It is easily available on internet from any source, install all Google USB drivers.
2. Enable USB debugging as shown in the steps while rooting your device.
3. Plug in the USB cable into your Smartphone and connect it with your PC.
4. Type adb devices > adb reboot bootloader > fastboot devices > fastboot oem unlock.
You have to insert all the commands shown above in the same sequence. Let me make you understand the meaning of these commands.
adb devices: This command will check and navigate whether your device is plugged in and revealed in SDK.
adb reboot bootloader: This command reboots your Smartphone into bootloader.
fastboot devices: This command double checks that your LG G pro 2 is connected.
fastboot oem unlock: This is the final command which will make your device to unlock bootloader.
After typing this command, on you Smartphone a confirmation screen will be shown. You just have to press Volume Up button for yes and Power off button to confirm.
Now you have to just restart your device and your bootloader will be unlocked. Kindly use these tricks with extra care and don’t worry all these tricks are safe and already experimented
What is your opinion on this topic?
Click to expand...
Click to collapse
Yes this is true for older phones but will NOT work for any variant of the l g pro 2 don't get excited guys....
So I'm wondering how come we can install and use PhilZ Touch recovery if the bootloader is locked. Or has PhilZ recovery image been signed or bumped or what?
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.
bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others
dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.
I've just got a new Z5 and am trying to install LineageOS, like I did on my dearly departed HTC m8.
I've got the android platform tools installed, and the device shows up if I use "adb devices". "adb reboot bootloader" appears to work - it shuts the device down then the LED goes blue (the documented behaviour of being in fastboot mode). However, "fastboot devices" lists nothing.
*#*#SERVICE#*#* indicates bootloader unlock is allowed, I've got dev mode enabled, I've got my unlock code ready and waiting... No fastboot mode though. Any ideas?
Hang on a sec.
It's just occurred to me that something else might be wrong. Booting into "fastboot" is the same as entering recovery mode, right? Well, when I try doing it, all I get on my phone is the blue LED. Just a black screen. That seems obviously wrong, because it should be displaying Sony's built-in recovery mode stuff, right?
While we're at it, I've just tried again on my work computer, holding volume up and inserting a USB cable. The computer recognised and installed "S1Boot Fastboot", and I can see it in Device Manager under "Other devices". However, the status is "The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device."
This was the same on my home machine. I tried installing Sony's drivers, and the Android drivers, but each time I pointed Windows at the directory I'd unzipped to it would just say that it couldn't find any drivers there.
e: #$%&!
I'm trying with Sony's "Emma" tool. It says to hold vol-down and connect the phone, which gives a green light (not a blue one), but says "this phone is locked". But I've unlocked it! Sony's instructions at the address listed in the error message say to enable debugging then select "OEM unlocking" from the dev options, which I have done! What gives?
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Thank you!
Hyperlynx said:
Got it!
I Can't post the URL due to low number of posts, but I found what I needed from the question on the android Stack Exchange called "Windows 10 Fastboot Driver". I grabbed a tool called Zadig, which was able to install a driver for Fastboot, so I could flash recovery.
Right. Now to get set up! Woo!
Click to expand...
Click to collapse
Thank you! I had the same problem. The device showed up as "Android" and I couldn't install the drivers.
You can find instructions and the download link here: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver
Hopefully someone here can help me through my problem,
Device Details: BLU G60/BLU VIVO X6
Android 9/Pie
OEM Unlocking: Allowed
USB Debugging: Enabled
Hey, I'm pretty new to this way of customizing my phone (adb, root, roms etc), and I'm trying to root my phone with Magisk. I have a patched boot.img, my bootloader is allowed to be unlocked and I'm doing exactly what the root guide says (https://www.mobilewithdrivers.com/magisk-root/blu-g60-64gb-3gb-ram) but it wont work, I keep getting different errors and I see all my fellow droid users so happy with their rooted devices, I want to root mine too. So what I'm asking is; Can someone with an actual brain (Mine wont work) to try and help me out or walk me through step-by-step?
Thanks for reading!
Some of the issues I have:
"adb reboot booter" and "fastboot reboot bootloader" both reboot the device but in the top left corner it says "fastboot mode" and just freezes, when I do any command it just says "device null" but when I reconnect the USB cable, it just powers off.
"fastboot flashing unlock" results in "FAILED (remote: Not implemet.)" Yes, spelt like that.
"fastboot oem unlock" says, unkown cmd...
Wrong driver in use. Use the one provided by BLU suitable to your phone.
i couldnt find any drivers for the exact device, only google ones...
any ideas?
If you have a mac, you could try that. They usually don't require drivers.