I don't normally post in the forums however I figured this may be important.
Lets hope that this time we may be able to get our bootloaders unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Saw same, subscribed to thread!
Searching for the exact phrase, not much out there I found other than a G4 question regarding the same...
Copied and pasted this from a source I found..
For those new to “OEM unlock,” just know that this is a part of the command used to unlock a Nexus phone’s bootloader. After installing the Android SDK, plugging your phone into a computer, opening adb, and rebooting to the bootloader, a simple command in adb of “fastboot oem unlock” will start the process of phone freedom.
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
My understanding is that this is hard built into the developer mode, so stock vanilla Google phones like nexus and I'm guessing probably the moto lines are the only phones for which this will work. Basically, you're telling the phone whether to ignore the command altogether or to actually execute the command when it's toggled on. Think of this like the following: oem unlock toggle : permit execution of 'oem unlock' command :: USB enabled toggle :: being able to use the adb command
As @51ngular1ty said above, Sam phones have a completely different recovery architecture, so they respond to different commands/software.
51ngular1ty said:
It's a command used in fastboot unfortunately samsung phones don't have a fastboot they have a recovery that you can use adb in and they have odin mode that as far as I can tell fastboot doesn't work in. So I am unsure of how we would test this.
Sent from my SAMSUNG-SM-N920A using Tapatalk
Click to expand...
Click to collapse
Fastboot is a commandline tool used through adb. You plug you phone in while its on and you can use adb commands but you have yo enable it in the dev settings
Related
well i had no problem what so ever making fastboot work, sadly though there are certain times were one has to use ADB! anyway, i have htc sync installed, and i know that the computer recognizes my device because of this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so obviously there is a problem that i do not understand, because when i check in my sdk (fastboot) folder by typing "adb devices", the list of devices is empty!
please help i really need this!
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
tomascus said:
ADB detects your device while it's inside the OS (running) or in recovery mode. Make sure to install latest version of HTC Sync.
Click to expand...
Click to collapse
so it cant detect my device while it's in fastboot mode? so it's impossible to use ADB if your bootloader is relocked right? cuz i am trying to follow this guide: http://www.flow-wolf.net/2012/10/install-jelly-bean-on-htc-one-x-maximus.html
however i cant find a way to successfully install PJ46IMG.zip !
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
tomascus said:
That guide is extremely outdated and I don't suggest you use it. To flash the firmware zip package use the fastboot command 'fastboot oem rebootRUU' and then type 'fastboot flash zip (name of zip here)'
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
yeah when i did that before i also got an error, cant remember actual wording, but the good new is i gave up on OrDroid and Maximus, decided to try out Jeffix and it worked, i am guessing it was an issue related to Hboot, but happily all my issues have been resolved, thanks for the help though!
Hey guys, I finally got my phone!
I want to install a custom ROM but first I need to unlock the bootloader and I'm having a nightmare doing it. Is there an specific thread where I can ask for help with, since I didn't find any I created this one but feel free to delete it.
On the FAQ thread I found this:
"First you need to unlock your bootloader. To do that, go to http://www.htcdev.com/bootloader. On the supported devices list, choose "HTC One (M8)"
If I go there, i am able to get up to step #5, but when I enter the command "fastboot oem get_identifier_token" I get that "fastboot" is not a recognized command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've searched on Google, but all thread (or most of them) only point to old devices or another brands. I also tried to use a root toolkit, but everything takes to that #5 step.
What am I missing here?
pinktheater said:
Hey guys, I finally got my phone!
I want to install a custom ROM but first I need to unlock the bootloader and I'm having a nightmare doing it. Is there an specific thread where I can ask for help with, since I didn't find any I created this one but feel free to delete it.
On the FAQ thread I found this:
"First you need to unlock your bootloader. To do that, go to http://www.htcdev.com/bootloader. On the supported devices list, choose "HTC One (M8)"
If I go there, i am able to get up to step #5, but when I enter the command "fastboot oem get_identifier_token" I get that "fastboot" is not a recognized command.
I've searched on Google, but all thread (or most of them) only point to old devices or another brands. I also tried to use a root toolkit, but everything takes to that #5 step.
What am I missing here?
Click to expand...
Click to collapse
This will help you set up adb/fastboot in your System path, the rest is as you've already done...
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
EddyOS said:
This will help you set up adb/fastboot in your System path, the rest is as you've already done...
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Click to expand...
Click to collapse
Thanks mate! I finally did it, but damn it took a lot of work
pinktheater said:
Thanks mate! I finally did it, but damn it took a lot of work
Click to expand...
Click to collapse
If you now have adb in your system path you can run the commands in any location - makes life a LOT easier moving forward (and it applies to ALL Android devices)
Good morning all.
I've a problem during the flashing of TWRP.img
- adb-Driver installed
- Mi A2 lite booted into fastboot
- computer and phone can't connect
- phone aborted the fastboot mode after some minutes
Phone Mi A2 lite latest Stock ROM
Computer windows 11 pro
Code:
C:\Users\Username>fastboot boot "D:\Username\Downloads\twrp-3.5.2_9-2-daisy-unofficial.img"
downloading 'boot.img'...
OKAY [ 0.643s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.665s
Have you enabled bootloader unlocking in developer options?
Tech0308 said:
Have you enabled bootloader unlocking in developer options?
Click to expand...
Click to collapse
OEM Unlock
(Allow bootloader unlock)
yes, i did
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Tech0308 said:
And then run fastboot flashing unlock?
It'll erase your data unless you keep volume down button held while running this command
Click to expand...
Click to collapse
this command doesn't work, i'll get the output of all aviable commands, that's all
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Tech0308 said:
Ahh sorry I meant fastboot oem unlock here's the link to a guide, use the first half for what you want, the instructions are valid and still work
Thread '[GUIDE] How to enable Camera2 API persistently and keep bootloader locked' https://forum.xda-developers.com/t/guide-how-to-enable-camera2-api-persistently-and-keep-bootloader-locked.3851414/
Click to expand...
Click to collapse
thank you, that's it
I would like to know how to enter fastbootd! mode???
Enable the USB debug mode in the Developer options, install adb (it's the part of Android Studio, or as a separate tool for Linux available in the official repos) and execute "adb reboot bootloader".
This is FastBootd! mode ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
uluruman said:
Yes it is. In this mode the phone responds only to the commands of the fastboot CLI tool.
Click to expand...
Click to collapse
so I can install GSI by the dynamic partitions
PaulinoBaslio said:
so I can install GSI by the dynamic partitions
Click to expand...
Click to collapse
Probably. May be. From my experience it simply doesn't work. It sorta flashes something but may be it just takes forever to complete or it's really just stuck but there's no response whatsoever. Fastboot mode is absolutely minimalistic, it does not report anything, no progress, nothing, and I guess it's intended to be like that, because it boots before anything else and theoretically allows you to flash even the very first bootloader. Anyway, I tried something like fastboot flash system lir-v316-220325-arm64-bvZ.img and the CLI tool reported Sending 'system' and then nothing else happened for the next 15 minutes or so, after which I just hit Ctrl+C, ran fastboot reboot and observed that nothing changed, the old system booted just like it was, so I guess nothing was really flashed, even partially. I don't know really, may be it's unpacked internally only when the image is fully uploaded and I didn't give it enough time, but for that time Odin would already flash the whole set of firmware. What else is to try, besides waiting more time, is converting the image to/from Android sparse format using the img2simg & simg2img tools, and try other partition names, such as "system_root" but I am sure this latter thing is absolutely wrong. The GSI system partition is called system, it just must be called that, system_root is something else (I guess it's the system root of the recovery mode).
[EXPERIMENTAL] Nokia G10 and G20 Bootloader Unlock!
Please install ADB and Fastboot Drivers from here
Please proceed with caution. You are responsible for your own action!
PLEASE NOTE I PERFORMED THIS STEPS ON A NOKIA 3 TA-1032 and it worked.
Steps to unlock Bootlader:
1. Turn on Developer options by tapping build number 7 times.
2. Toggle OEM Unlocking ON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Turn on USB Debugging
4. Open CMD in your computer
5. Type adb devices and connect your device to the computer using USB cable
6. Accept the adb authorisation prompt on your Nokia Device
7. CMD will show your device serial number as shown in the picture below
8. Copy the serial number and paste it here and copy the md5 hash value
and make sure you that there's no space or other things inside
the serial number.
9. In CMD type following command
adb reboot bootloader
[then your device will boot into fastboot mode]
10. Then type following command in CMD
fastboot devices
[this is to make sure that your device still connected to pc and it will show your
device serial number]
11.Then type
fastboot oem key [KEY_OBTAINED_GENERATOR-MD5]
so the command will look like as follows
fastboot oem key 282c41d53c2c5aefaa941bbeda525ca3
12. Type
fastboot flashing unlock
then your phone will ask you about unlocking bootloader
13. then press vol up (means yes)
14. Restart your device and see if it is unlocked!
This is great. Does it also works for the Nokia g21?
baseline2016 said:
This is great. Does it also works for the Nokia g21?
Click to expand...
Click to collapse
Please try and see if it works.
I have tested this on Nokia 3.