Database Users

[Guide] Most Problems and Info's that you must Know about ADB and Fastboot

Tips & Guides About Moto G 2014 ADB and FastBoot
The most of people have problems with fastboot and ADB. Here will explain some tips and guides.
- Do u know can use ADB in recovery mode?
Yeah if u have bricked your phone or deleted system or can't put the Debug Mode have a alternative. This happens the Device ADB have two modes. The USB mode and Debugging Mode, using two different drivers. When you download Motorola Device Manager he installs the Debugging Drivers. In Motorola is really hard obtain the correct drivers.
- Can I flash zips with fastboot?
Yeah but isn't recommended the people try that:
- fastboot flash zip myzip.zip
This is incorrect he will try to flash a .IMG in a partition called zip.
- fastboot -I flash system myzip.zip
This is incorrect. When you download a ROM backup to flash in Recovery he have some partitions making that will create a partition into a partition. Bricking your device.
The correct way to flash ROM is in recovery.
- I can't transfer file on my device.. Can I flash?
Yes using two methods
- ADB push
You push to your device a .zip with the Rom eg.:
- adb push my file.zip /sdcard or /sdcard1
This will push your file to the device and you can after that flash in recovery.
Is normal after digit the command nothing happens. Differently fastboot the ADB doesn't shows progress of transfer.
- ADB side load
You can flash sideload the zip
Using adb sideload myzip.zip
Must enable sideload mode on your recovery.
- my device doesn't appear on the list.
When you are on boot loader mode the ADB doesn't runs. Only in recovery mode or system mode.
Most times you have incorrect drivers. But if u are on recovery mode try that on cmd:
adb kill-server
adb usb
This will enter the daemon service in USB mode.
- can I reboot my device in recovery? Yes, adb reboot recovery
- can I wipe my firmware with fastboot? Yes, using these cmds.
fastboot erase userdata
fastboot erase cache
- can I get my device info?
Yes with ADB.
adb get-imei
adb get-serialno
adb get-deviceno
If u have more questions write here. I will add on OP.
Downloads:
- Moto G drivers: https://mega.co.nz/#!IY0mUBDL!tukY40l9_GlYpJVuSxahYBXhDjXDBfhG-bfG0oIvEa8
- Minimal (really minimal) ADB & fastboot: https://mega.co.nz/#!NJUVlIwI!uiRi4UAdU-8ZKEeQ1gquGDYbSSG9rWIWeMElUcMD4e0

Impressive, n tnks for sharing
sent From My XT1068{LP} using TapatalK

plez help me
OEM unlock failure! :crying:

adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Dont type UNIQUE_KEY in the command. Its just the syntax.

KrishnaSagar said:
Dont type UNIQUE_KEY in the command. Its just the syntax.
Click to expand...
Click to collapse
I totally did that before lol

adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Hello tipe
fastboot oem unlock TheKey
But u can check if is unlocked in the boot loader is is status code 3
Ah.. If the unlock doesn't work:
fastboot oem get-unlock-data
Pick the code without the word (fastboot)
And put all the code in one line.
THE MOTOROLA PAGE DOESNT VALIDATE YOUR ENTERED CODE ONLY GENERATE A CODE WITH YOUR INPUT.
If u put a wrong code. He will generate a wrong code.
Cheers

how to install recovery in redmi note 4

what is the requirement to install TWRP recovery in Redmi Note 4
1. Universal ADB driver
2. ADB files
3. TWRP Recovery
These 3 files you can download by clicking here after download these files first insatall universal adb driver after that unzip the adb.zip and twrp.zip after unzip both file open twrp unzip folder and copy twrp.img and past it on adb unzip folder.
Your device bootloder must be unlock if your device bootloder is not unlock than unlock it. visit here to unlock your device bootloder.
After unlock bootloder in your device just follow the step given below
Enable USB Debugging
==> Enable Developer option- Goto Settings > About phone > tap on MIUI version 5 to10 times.
==> Enable USB Debugging- Goto Settings > Additional settings > Developer options > USB Debugging and enable it.
Enable OEM Unlock
==> Enable OEM Unlock – Goto Settings > Additional settings > Developer options > Enable OEM Unlock.
Installation Process For TWRP Recovery in Redmi Note 4
1. Now connect your phone Redmi Note 4 to PC via USB cable.
2. Open the ADB unzip Folder.
3. Inside the folder, press and hold “Shift” Key then right click and select and selecte the option “Open command Windows here”. like this
4. The Command prompt will open.
5. Now write the this command.
adb devices
7. If your Redmi Note 4 properly connected to your PC it will show your device with some alphanumeric character.
8. Now write the this command. This will reboot your device into fastboot mode
adb reboot bootloader
9. Now its time to flash TWRP, so run this command.
(NOTE:- you must check in adb folder twrp.img file present or not if not present than past it first from twrp folder)
fastboot flash recovery twrp.img
once flashing process done than turn on your device

Actually you may use command 'dd' in adb shell or a terminal emulator to flash recovery easily.

yadav. said:
fastboot flash boot twrp.img
once flashing process done than turn on your device
Click to expand...
Click to collapse
I seems that the right command is "fastboot flash recovery twrp.img"
Unless you wanna install the recovery onto the kernel partition.

@OP: The correct command to flash the recovery is
fastboot flash recovery twrp.img
Please correct it in your post.

it does't work
after i downloaded the ADB file and the TWRP img together into my phone , which i saw with the CMD . and i open back my phone to recovery mode agian. it does not appear as TWRP . HOW?

Aaronyap said:
after i downloaded the ADB file and the TWRP img together into my phone , which i saw with the CMD . and i open back my phone to recovery mode agian. it does not appear as TWRP . HOW?
Click to expand...
Click to collapse
Because the instruction in first post is incorrect, after you flashed recovery you also need to use this command: "fastboot boot recovery_image_name.img"
This is needed only to boot into TWRP for first time, if you intend on flashing custom ROM's then Format DATA,reboot to recovery again and you can use it normal.

Downgrade Orea beta to Nougat

Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.

are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help

Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse

I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.

swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.

tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied

swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm

tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.

Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.

trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.

[Solved] Huawei P9 Lite Bricked

Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160

Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275

4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess

wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.

4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader

wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.

4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.

OnePlus 8 TMO Magisk boot image IN2017_11_C.43

It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!

what attached boot img?

zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download

If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!

Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?