Trying to repair my phone with DC-Unlocker tool I noticed that the software was able to execute fastboot commands even with "FRP lock"
I tried to discover the used commands and I found this
"fastboot oem backdoor get"
"fastboot oem hwdog certify begin"
-- missing part --
"fastboot flash slock Unlockcode.bin"
Unfortunately don't know how to generate the "Unlockcode.bin" file that generates the software
So my question is: does anyone know how to generate this bin file ?
Many thanks in advance for any help ....
azerty11 said:
Trying to repair my phone with DC-Unlocker tool I noticed that the software was able to execute fastboot commands even with "FRP lock"
I tried to discover the used commands and I found this
"fastboot oem backdoor get"
"fastboot oem hwdog certify begin"
-- missing part --
"fastboot flash slock Unlockcode.bin"
Unfortunately don't know how to generate the "Unlockcode.bin" file that generates the software
So my question is: does anyone know how to generate this bin file ?
Many thanks in advance for any help ....
Click to expand...
Click to collapse
You can capture the USB traffic with USBpcap and monitor the captured data with wireshark.
I'm also trying to find out what data it is which unlocks my phone.
Related
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
**Corrupt zip removed**
syztemlord said:
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
Click to expand...
Click to collapse
Download and install the ADB & fastboot setup file I have attached. Allow admin rights at prompt and enter Y twice when prompted for ADB and fastboot, allow install with system wide support; close command prompt.
Reopen command prompt and re run "fastboot oem device-id" command.
Loggsie
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
syztemlord said:
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
Click to expand...
Click to collapse
I'll remove the corrupt zip.
Try a download from Google, search for "adb-setup-1.3.zip" it should be the top link for Google Drive.
Loggsie
So I'm using that app bugjaeger adb otg, I pretty much doing everything right, oem unlock enabled on target device, USB debugging enabled on both devices, reboot target device into bootloader, on host device I do "fastboot oem unlock" and then it tells me to enter command again and it says it goes to but it doesnt give me the popup window to actually unlock the boot
Did you follow the steps in Motorola website? Did you receive unlock code on email?
Can't you unlock with a computer?
You need to enter that unlock data on their website and if it works they should return an unlock code to your email which then you enter that code with the oem unlock command.
Here's an example of the final command:
"fastboot oem unlock 86yy8uufyuwhvr77836vvvj6e"
mrsiri said:
Did you follow the steps in Motorola website? Did you receive unlock code on email?
Can't you unlock with a computer?
You need to enter that unlock data on their website and if it works they should return an unlock code to your email which then you enter that code with the oem unlock command.
Here's an example of the final command:
"fastboot oem unlock 86yy8uufyuwhvr77836vvvj6e"
Click to expand...
Click to collapse
you know how to close the bootloader
dan12121z said:
you know how to close the bootloader
Click to expand...
Click to collapse
Yeah. you just press volume buttons till the start option appears.
Otherwise just inout this command "fastboot reboot". It should start booting your rom, if not then input this command first: "fastboot oem fb mode clear" and then "fastboot reboot".
I am trying to unlock the bootloader of the Poco F3 in order to root it.
I installed the platform tools present in the apt repositories (OS: Pop!_OS 20.10), this is the version I installed:
Bash:
$ fastboot --version
fastboot version 1:8.1.0+r23-8
Installed as /usr/lib/android-sdk/platform-tools/fastboot
Then I did this:
enabled developer options, USB debugging and OEM unlock in the device's settings
turned it off and then on again in fastboot mode (holding power and volume down buttons)
connected it to my PC through USB and then ran the following commands but when I run fastboot flashing unlock I get an unknown command error
Bash:
$ fastboot devices
████████ fastboot
$ fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Am I missing something here?
I read somewhere that I should install device specific drivers but I couldn't find any for Linux, what do I have to do?
You need to use mitools to unlock the bootloader. Search some videos of how to do it. You will need to wait 168 hours after finish the steps.
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
One Way : Mi Unlock Tool
No other way than Mi unlock tool......yet
Oh alright, Mi unlock tool it is then, thanks for the quick help!
It's purely so Xiaomi can limit people to unlock bootloader so that you don't get companies bulk buying devices falshing custom firmware and selling them as other phones for more
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
that guide is wrong flashing unlock would work if the bootloader didnt need a special img file as part of the unlocking process.
the miunlock tool simply does the downloading of the img file in the background once you have waited the mandatory 168 hour wait period.
I'm attempting to follow this guide here https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/ and I'm finding myself having issues at step #5. ADB picks up my device while it's on no issue but when I reboot into bootloader, it no longer picks up my device to get the unlock code.
Anyone know what the issue could be? Any help is appreciated.
Edit: when I use the command "fastboot oem get_unloock_code" the CMD window says "Waiting for any device"
You don't have fastboot drivers.
craznazn said:
You don't have fastboot drivers.
Click to expand...
Click to collapse
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
MushroomElm said:
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
Click to expand...
Click to collapse
Glad you figured it out
Ive had my LG G7 for about a year now. I managed to unlock the bootloader without any problems and used magisk ok.
I just came to upgrade the firmware without any problems. I enabled dev and usb debug but the 'Enable oem unlock' button is greyed out and displays "bootloader already unlocked" ok so not a problem - that is until I come to access the bootloader again.
Here is the message:
Welcome to Fastboot mode: Please check "Enable OEM unlock" in developer options
adb commands no longer work at this point as connection is lost. Only choice is manually reboot or switch off.
WTF now what. Im unable to root or restore the bootloader. So even though its unlocked and displays the bootloader unlocked message when booting - Fastboot does not see it and it still wants me to 'Enable oem unlock' but its greyed out.
Any suggestions please anyone
You can use QFIL to restore laf_a & laf_b. Then flash full rom (Refurbish) in Download mode.
ps: the reason is you do not flash full rom after unlock bootloader in order to tell to the machine that you are in the illegal mode kakaka.
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall, cant freeze garbage etc.
Being relatively unsure, would you mind going over the QFIL method with me.
Thanks
chadandchew said:
Thanks for your reply nttuan. I just about gave up hope. Im totally paranoid without root. No decent firewall
Click to expand...
Click to collapse
Never used QFIL before. Where do I get the firehose elf file from. I noticed a couple of elf files in the extracted folder, is it one of these.
Do I have to create any xml files and do I have to rename any of the kdz extracted files?
Some posts are a bit old and for other models.
Instead of flash the boot_a from magisk_patched image, you can use command
fastboot boot magisk_patched.img
and use the LGUP to reflash the firmware.
If you look at the photo above I LOSE ALL ADB commands after adb reboot bootloader.
fastboot boot magisk_patched.img or any other command just displays "Waiting For any Device" in CMD window.
This is my problem because the bootloader is already unlocked and oem greyed out - it is asking me to "Enable OEM Unlock"
I am wanting to either root the phone or restore bootloader to locked. Sorry for any confusion
type fastboot devices and show me the result.
maybe you do not have correct fastboot driver
It did say waiting for any device but now its gone from bad to worse. I followed this guide Here and now all I get is fastboot screen, see photo. If I now try fastboot devices then fastboot flash boot_a magisk_patched.img it shows error which does not look good actually , photo 2. Cant get download mode. If I try to get it by holding volume button and inserting usb lead I get this nasty screen, photo 3. I think that some of the partitions may have been overwitten. . Stupid move on my part.
Forgot to mention - EDL is still accessable
Ive managed to sort the above problem
QFIL flashed only the following 6 files :
abl_a and abl_b
laf_a and laf_b
boot_a and boot_b
Phone rebooted perfectly after this.
Thanks for your advice