Database Users

ADB PULL

Is there anyway to pull the files from the devices while the device could not boot into the OS, and only able to access to recovery mode (apply update from adb).

adb device unauthorized

Hey, I'm on A2017U stock B19 bootloader unlocked,
I want to backup my stock recovery and boot using axon7tool (I want to flash twrp after that),
When I type: "adb devices" I get my device number and next to it: "unauthorized",
And when I type "adb reboot edl" I get: "error: device unauthorized."
USB debugging enabled.
What am I missing?
(also when I try to go to edl mode (vol up + vol down + power) nothing happens...)
Thanks

I think u need to be root in order to backup those files using adb and you have to have the bootloader unlocked in order to root even tho theres a thread showing how to root without bootloader unlocked

Thanks,
My bootloader is unlocked...
Is there any other way to backup stock recovery and boot before flashing twrp?

Hello, do you have the proper drivers installed for the phone usb wise and in edl mode it won't do anything, that's normal.

Hi, Thanks,
I think so, as I say, it does recognize my phone number on "adb devices" , and I successfully unlocked my bootloader using fastboot

P9 Lite VNS-L21 won't boot into TWRP

Hello
As menitoned, my phone won't boot into TWRP, it does boot into Android 7.0 EMUI 5.0, can boot into revolutionary recovery, but no, not TWRP... Bootloader is unlocked! Please help

Are you certain it's not booting into TWRP? The reason I ask is I thought I couldn't boot into the custom recovery programme either: it kept loading EMUI, using the phone's buttons. In my case, ver.4.1.1
Have you tried booting via ADB commands? I had reloaded a stock update, then unlocked the bootloader for a second time, only find the same scenario. It wasn't until I tried rebooting with ADB that it actually loaded TWRP.
In case you aren't familiar with the commands. Install ADB Tools, then open a command window from the correct folder location, where ADB tools are installed. To check the PC recognises the device, use:
adb Devices
it should show the device's serial number {I think}. Then:
adb reboot recovery
it should reboot into recovery mode. If TWRP has been installed correctly, it should load into it. Otherwise...I don't have a clue what the issue is. All the best.

[Moto G6 Play][JETER] Rooting progress thread for JETER

UPDATE: Root achieved see thread here
I've managed to extract the boot.img from my device using the following steps, but patching it with MAGISK ends up with boot loop.
Here are the steps I've done.
I've unlocked the bootloader using the standard methods. All ADB commands are run from a computer with ADB and fastboot setup.
Connect phone to computer, enabled ADB usb debugging.
Code:
adb reboot bootloader
Once the device reboots to the bootloader.
https://drive.google.com/file/d/1Q7CIF2-byTW7ERUXFU0XlWFYZQM5hysd/ DO NOT FLASH THIS TO YOUR DEVICE only boot from it. This is a patched Moto E5 TWRP image. It takes a while to boot.
Don't mess with anything inside TWRP.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Once TWRP boots from your computer type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb reboot
Once the device reboots and you're back in android run
Code:
adb push stockboot.img /sdcard/
This will push the stockboot.img to your sdcard folder
Intall Magisk Manager - https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Patch stockboot.img located on your sdcard using magisk manager.
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
This will pull the patched_boot.img to your computer
Code:
adb reboot bootloader
Once the device reboots into the bootloader you can run
Code:
fastboot flash boot patched_boot.img
fastboot reboot
From here it boots to "N/A" and you get nothing. It just hangs there forever.
From here you can just flash the stockboot.img using the steps below
Hold power + volup + voldown which will boot back to the bootloader
Code:
fastboot flash boot stockboot.img
fastboot reboot
Now you're back on the stock bootloader and the device will boot up like normal.
Anyone have any advice on how to get MAGISK to patch correctly? The stock boot.img is ~16.8MB and the patched one from magisk is 12.1MB. I'm guessing that's the issue, but I'm not sure what else to do.

Hi!
I did the exact same thing with ALI, the Moto G6 non-plus. Glad to see that I'm not the only one struggling.
Hope we will find an answer...

My phone is not recognized in ADB console while running fastboot mode

I wanted to install a custom rom for my moto g4 and I just have problems with installing twrp. I downloaded twrp img and adb tools, then connected my phone to the pc in debug mode. In the adb console, the phone is displayed, but when I put the phone in the fastboot mode, it is not recognized.

that's cos there's separate program (e.g. fastboot) for interfacing with bootloader (c.f. Android Debug Bridge for interacting with recovery or Android).