Database Info

Unlock 6.0 Bootlader

I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows

MrTooPhone said:
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
Click to expand...
Click to collapse
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.

In addition to the above, by not prepending './' to your command, you were calling a(n apparently available) system-wide installation that might have been too old to detect the device. It would also help if you would post an lspci so we could see if the device is at least in the correct mode.

acejavelin said:
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
Click to expand...
Click to collapse
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.

MrTooPhone said:
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
Click to expand...
Click to collapse
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk

acejavelin said:
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Tried again with Linux. SU did the trick. Thanks.

After TWRP Update Nothing Works

Hi all,
I was running LineageOS 14.1 Official Latest Build lineage-14.1-20180119 and I have updated the TWRP from 3.0.2-0 to 3.2.1-0. After flashing to boot from within recovery it does not reboot. Just nothing.
No Screen or LEDs. When pressing the power key it vibrates. No fastboot or Recovery mode.
Red LED flashes when connected to PC. That's it. Nothing else.
Please help!!!!!

I had this too. To recover:
- Download lineage-14.1-20180119.zip, unpack it and locate the file "boot.img".
- Download flashtool (I used v0.9.23.1).
- Boot into fastboot mode:
- Disconnnect the USB cable, Turn off phone and wait a bit.
- Hold volume+ and connect the USB cable.
- The phone should show a blue status light.
- Flash boot.img using FlashTool (press Flash icon, Flash kernel only).
- Reboot phone to system in FlashTool
This should bring your phone back up.
To install TWRP, I always use one of those procedures:
- Connect phone via USB and enable ADB
- Copy .img to some location on phone, eg. /storage/sdcard1
- Start ADB shell
- Run command via ADB:
su
dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
OR:
- Connect phone via USB and enable ADB
- Run on host computer:
adb root
adb wait-for-device
adb push "PATH_TO_TWRP_IMG_FILE" /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
If adb is complaining about "no premissions" for your device, try:
sudo adb kill-server
sudo adb start-server

Awesome!!
OverBim said:
I had this too. To recover:
- Download lineage-14.1-20180119.zip, unpack it and locate the file "boot.img".
- Download flashtool (I used v0.9.23.1).
- Boot into fastboot mode:
- Disconnnect the USB cable, Turn off phone and wait a bit.
- Hold volume+ and connect the USB cable.
- The phone should show a blue status light.
- Flash boot.img using FlashTool (press Flash icon, Flash kernel only).
- Reboot phone to system in FlashTool
This should bring your phone back up.
To install TWRP, I always use one of those procedures:
- Connect phone via USB and enable ADB
- Copy .img to some location on phone, eg. /storage/sdcard1
- Start ADB shell
- Run command via ADB:
su
dd if=/storage/sdcard1/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
OR:
- Connect phone via USB and enable ADB
- Run on host computer:
adb root
adb wait-for-device
adb push "PATH_TO_TWRP_IMG_FILE" /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
If adb is complaining about "no premissions" for your device, try:
sudo adb kill-server
sudo adb start-server
Click to expand...
Click to collapse
You are AWESOME!!! that actually worked!! Thank you very much @OverBim
I was very hopeless about recovering the phone. Thank you again.
And if you can, please tell me what did I do wrong or what happened to cause that.

[ NO ROOT ] Enable Camera2API / EIS

You are not root, you do not want to root then unroot like this guide...
https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
And nothing happen when you follow this guide either...(this is what happen to me)
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-enable-hal3-camera2api-t3747073
-----------------------
Assuming you're already have adb tools and know how to use it
1. Enter fasboot mode (volume down + power)
2. Run CMD command
3. Type lines as follow...
fastboot devices (tap enter)
fastboot oem unlock (tap enter)
4. Then boot to twrp...
fastboot boot twrp.img (tap enter)
5. After device boot to twrp, DONT TOUCH it
6. Now type this...
adb shell (tap enter)
setprop persist.camera.HAL3.enabled 1 (tap enter)
setprop persist.camera.eis.enable 1 (tap enter)
adb exit (tap enter)
7. Then boot to fastboot again...
adb reboot bootloader (tap enter)
fastboot devices (tap enter)
fastboot oem lock (tab enter)
fastboot reboot (tab enter)
8. You're done, now download Manual Camera Compatibility from Playstore to check.
Hope this help

pyronia said:
You are not root, you do not want to root then unroot like this guide...
https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
And nothing happen when you follow this guide either...(this is what happen to me)
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-enable-hal3-camera2api-t3747073
-----------------------
Assuming you're already have adb tools and know how to use it
1. Enter fasboot mode (volume down + power)
2. Run CMD command
3. Type lines as follow...
fastboot devices (tap enter)
fastboot oem unlock (tap enter)
4. Then boot to twrp...
fastboot boot twrp.img (tap enter)
5. After device boot to twrp, DONT TOUCH it
6. Now type this...
adb shell (tap enter)
setprop persist.camera.HAL3.enabled 1 (tap enter)
setprop persist.camera.eis.enable 1 (tap enter)
adb exit (tap enter)
7. Then boot to fastboot again...
adb reboot bootloader (tap enter)
fastboot devices (tap enter)
fastboot oem lock (tab enter)
fastboot reboot (tab enter)
8. You're done, now download Manual Camera Compatibility from Playstore to check.
Hope this help
Click to expand...
Click to collapse
there is already a thread posted about it, so please dont spam the forum with mirror links
i request moderator to close it

<p>some title</p>
just a silly (and probably noob) question: does the unlock / re-lock bootloader procedure wipe your device data ??

pyronia said:
You are not root, you do not want to root then unroot like this guide...
https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
And nothing happen when you follow this guide either...(this is what happen to me)
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-enable-hal3-camera2api-t3747073
-----------------------
Assuming you're already have adb tools and know how to use it
1. Enter fasboot mode (volume down + power)
2. Run CMD command
3. Type lines as follow...
fastboot devices (tap enter)
fastboot oem unlock (tap enter)
4. Then boot to twrp...
fastboot boot twrp.img (tap enter)
5. After device boot to twrp, DONT TOUCH it
6. Now type this...
adb shell (tap enter)
setprop persist.camera.HAL3.enabled 1 (tap enter)
setprop persist.camera.eis.enable 1 (tap enter)
adb exit (tap enter)
7. Then boot to fastboot again...
adb reboot bootloader (tap enter)
fastboot devices (tap enter)
fastboot oem lock (tab enter)
fastboot reboot (tab enter)
8. You're done, now download Manual Camera Compatibility from Playstore to check.
Hope this help
Click to expand...
Click to collapse
Its modify system

pyronia said:
You are not root, you do not want to root then unroot like this guide...
https://forum.xda-developers.com/mi-a1/how-to/tool-google-camera-root-magisk-enable-t3747585
And nothing happen when you follow this guide either...(this is what happen to me)
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-enable-hal3-camera2api-t3747073
-----------------------
Assuming you're already have adb tools and know how to use it
1. Enter fasboot mode (volume down + power)
2. Run CMD command
3. Type lines as follow...
fastboot devices (tap enter)
fastboot oem unlock (tap enter)
4. Then boot to twrp...
fastboot boot twrp.img (tap enter)
5. After device boot to twrp, DONT TOUCH it
6. Now type this...
adb shell (tap enter)
setprop persist.camera.HAL3.enabled 1 (tap enter)
setprop persist.camera.eis.enable 1 (tap enter)
adb exit (tap enter)
7. Then boot to fastboot again...
adb reboot bootloader (tap enter)
fastboot devices (tap enter)
fastboot oem lock (tab enter)
fastboot reboot (tab enter)
8. You're done, now download Manual Camera Compatibility from Playstore to check.
Hope this help
Click to expand...
Click to collapse
Thanks for manual instructions waiting from last 4 days . Now my gcam is working perfectly

nx2592 said:
just a silly (and probably noob) question: does the unlock / re-lock bootloader procedure wipe your device data ??
Click to expand...
Click to collapse
No

Already a thread for this here:
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-enable-hal3-camera2api-t3747073
Thread closed.

Adb fails to recognise device only when in fastboot

Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.

herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.

Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.

How to escape TWRP? Activate ADB w/ broken screen?

So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.

Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload

jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.

AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot

jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB