Database Info

[Q] Can't Flash 5.0 Image

I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?

ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
It means you've not copied the files into your ADB folder as it can't find the fastboot files

ArsenaMarabdeli said:
I can't flash the image file. It fails for some reasons.
I'm getting an error message("fastboot is not recognized as an internal or external command") in cmd when I open flash-all.bat file.
phone is rooted, with open bootloader. I had AOKP custom rom before i tried to flash 5.0.
Any Ideas what to do?
Click to expand...
Click to collapse
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.

gamer.11 said:
open the folder where you extracted the tarbal
hold down shift and right click
open command prompt here
do a "fastboot devices" to check if your device is connected
continue flashing using the commands.
Click to expand...
Click to collapse
This won't work if fastboot binary isn't in env PATH.
EddyOS said:
It means you've not copied the files into your ADB folder as it can't find the fastboot files
Click to expand...
Click to collapse
"Into your FASTBOOT folder". adb's got nothing to do with this.

http://forum.xda-developers.com/showthread.php?t=2513701
Follow method two in this guide.

beekay201 said:
This won't work if fastboot binary isn't in env PATH.
Click to expand...
Click to collapse
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.

Easiest way is to extract the sh1t out of the Google file until you eventually see all the img files. Then extract the fastboot zip into the same folder they're in and open a command prompt there.
Fastboot zip -
https://www.dropbox.com/s/b8wxmwfi2ekdw3a/Adb And Fastboot.zip?dl=0
Sent from my Android 5.0 Nexus 5

gamer.11 said:
worked for me i never had to put anything into my android tools folder, i have system wide access no matter where i open up the command prompt.
Click to expand...
Click to collapse
Because it's in your PATH.

beekay201 said:
This won't work if fastboot binary isn't in env PATH.
"Into your FASTBOOT folder". adb's got nothing to do with this.
Click to expand...
Click to collapse
People refer to the folder with ADB and fastboot in it as the ADB folder (If you had adb/fastboot in the system path this wouldn't even be required)
Do you really think I meant them to use ADB? Come on, now

beekay201 said:
Because it's in your PATH.
Click to expand...
Click to collapse
oh "env" meant environment, sorry did not understand your shot hand.
by the way OP? solved your issue?

EddyOS said:
People refer to the folder with ADB and fastboot in it as the ADB folder
Click to expand...
Click to collapse
I refer to this folder as the platform tools folder

nikon120 said:
I refer to this folder as the platform tools folder
Click to expand...
Click to collapse
Makes more sense I guess, just more to type! This is where being in PATH makes life better

[GUIDE]How to update from 5.0 to 5.x without loosing data if you're not 100% stock

Instead of having instructions all over the place inside various threads I felt a clear guide should be available as it's own thread. Now since Google implemented this great feature (all hail google) where normal OTA's no longer work on Nexus devices with Android 5.0 that isn't 100% stock i.e. rooted with or without custom recovery a lot of people don't know how to update their devices.
IMO opinion the easiest way without losing any data is to use Fastboot and this is an attempt of a how-to-guide. This is made on a windows PC, probably works with other OS's too.
What you need:
1. You need ADB.exe and fastboot.exe inside an easy accessed folder i.e. put in c:\ADB.
The easiest way to get these are with this tool: http://forum.xda-developers.com/showthread.php?t=2317790
You can also get this by installing the whole Android SDK but that is just a waste of bandwidth and time.
2. You also need to download the latest factory image for Nexus 5. Do this here: https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
3. You might need adb drivers but you'll have to find instructions for this by yourself.
The procedure:
1. Extract necessary files. The factory image you'll download is named hammerhead-lrx22c-factory-0f9eda1b.tgz
This is an archive which can be opened with an extractor of your choice e.g. 7-zip
Inside this archive is another file with no file type extension. Extract this file and rename it to whatyouwant.zip since it's a regular zip file. Then extract all files within this file (very meta with zips inside zips inside zips etc).
The files you need for updating with fastboot are:
system.img
boot.img
radio-hammerhead-m8974a-2.0.50.2.22.img (rename this to radio.img for more convenience)
put all these files in the ADB folder (it will make things easier).
2. plug your phone to your PC. You need to have USB debugging activated in developer mode.
3. open a command prompt and orient yourself to the adb folder (c:\ADB)
4. type adb reboot bootloader and wait until your phone is in bootloader mode.
5. type fastboot flash system system.img and wait until it's finished.
6. type fastboot flash radio radio.img
7. type fastboot flash boot boot.img
8. reboot your device (type fastboot reboot).
Hopefully this will work and you will update without loosing any data. Then you can proceed with rooting, flashing custom recovery etc. This is easiest done with WUG nexus root toolkit (http://forum.xda-developers.com/showthread.php?t=2389107)
I couldn't find any other guide's but if there's already one please remove this.

Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.

Thanks for the guide @mertzi. I've just used to upgrade my Nexus 5 to 5.0.1 without any loss of data. I appreciate the help!

rootSU said:
Just a note, you don't need adb.exe at all, and the drivers are actually USB drivers.
Its also worth noting that 95% of us prefer to recommend users not use toolkits.
Also, you could simply say:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash radio radio.img
...then point them to the existing adb and fastboot thread which would have saved you writing all the installation stuff out.
Click to expand...
Click to collapse
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?

optoisolator said:
Do I still use "fastboot flash radio radio.img" even though the radio image from the tgz file is "radio-hammerhead-m8974a-2.0.50.2.22.img"?
Click to expand...
Click to collapse
No. The 4th section is the file path and location.

So this keeps user data? Just updated the system to 5.0.1?
Maintains root and all?
Sent from my Nexus 5 using XDA Free mobile app

Keeps user data but you will have to re-root.

Thank you, thank you, thank you.
I've spent last couple days trying to make heads or tails out of other "tutorials". Some of them linked the OTA update and gave instructions for full image, others gave instructions but lacked the links to the image. I am surprised that none of my searches took me here until today.

Thanks a lot for this guide I was ale to update to 5.0.1 thanks to this guide.

Can I use this method to update from 4.4.4 to 5.0.0 ?

... Not aire if you can jump from 4.4.4 to 5.0 this way...
I actually jumped flashing radio and baseband and THEN flashing CM12.1

[TWRP][FAIL TO FLASH] TWRP.img file don't work

Hello!
I'm stuck trying to flash TWRP into my devices and hoping now to maybe get some help figuring this out.
My devices is
LG Nexus 5, D821, Android 6.0.1
OnePlus 3T, A3003, OxygenOS 5.0, Android 8.0.0
I wanting to flah them both with TWRP Recovery, I've followed the tutorials for each phone from the links below
LG Nexus 5
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
OnePlus 3T
http://www.teamandroid.com/2017/02/24/install-oneplus-3t-twrp-3-0-3-recovery-complete-guide/2/
I have installed the android studio for my PC and downloaded the neccesary tools to make this work as "Android SDK Platform-Tools", "Android SDK Tools", "Google USB Driver". I have unlocked the bootloader on both phones and downloaded the latest TWRP.img file for each phone from
LG Nexus 5
https://eu.dl.twrp.me/hammerhead/
OnePlus 3T
https://eu.dl.twrp.me/oneplus3t/
I've located each file in the same directory as adb and fastboot. The problem for me now is when I'm in command prompt and typing the following command
"cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery recovery.img"
I get the following text
"error: cannot load 'recovery.img': No such file or directory"
I have tried to download older twrp files and also from other pages but the issue remians. And when I'm in windows and trying to open the .img file I get a window that says
"It is not possible to mount the file"
"The Disc Image file is corrupted"
How can I solve this issue? Please Help

I've located each file in the same directory as adb and fastboot.
Click to expand...
Click to collapse
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.

unignostik said:
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.
Click to expand...
Click to collapse
Thank you! It worked now

EmmanouilEk said:
Thank you! It worked now
Click to expand...
Click to collapse
good stuff :good:

Question Need help

Might be wrong forum but needed help with rooting my Google pixel 6a with magisk. Alright I patched the image using magisk and put it on my laptop and pulled up cmd prompt did the adb reboot bootloader then did fastboot flash patched_magisk.img and it keeps giving unknown file location and unknown file. I'm I doing something wrong?

Kerrylee1738$$$ said:
Might be wrong forum but needed help with rooting my Google pixel 6a with magisk. Alright I patched the image using magisk and put it on my laptop and pulled up cmd prompt did the adb reboot bootloader then did fastboot flash patched_magisk.img and it keeps giving unknown file location and unknown file. I'm I doing something wrong?
Click to expand...
Click to collapse
Bootloader is unlocked. I actually did that part correct

Kerrylee1738$$$ said:
Might be wrong forum but needed help with rooting my Google pixel 6a with magisk. Alright I patched the image using magisk and put it on my laptop and pulled up cmd prompt did the adb reboot bootloader then did fastboot flash patched_magisk.img and it keeps giving unknown file location and unknown file. I'm I doing something wrong?
Click to expand...
Click to collapse
Try...
fastboot flash boot <nameofpatchedbootimage>
Also, you can find a rooting guide here. It will work for the 6a as well. There is also a 6a forum.

It gave a unknown file error. Is there a certain file that everything should be in?

Kerrylee1738$$$ said:
It gave a unknown file error. Is there a certain file that everything should be in?
Click to expand...
Click to collapse
The way I do it is put the patched boot image in my Platform Tools folder (latest version of course), open command prompt from the Platform Tools folder and flash it.

Thanks I found a pixel flasher on here that helped with the rooting process.

Kerrylee1738$$$ said:
did fastboot flash patched_magisk.img and it keeps giving unknown file location and unknown file. I'm I doing something wrong?
Click to expand...
Click to collapse
Did you copy the file called "patched_magisk.img" into the folder you launched adb.exe from? You either have to have it in the same folder, or call the file using its path (eg. "c:\users\admin\desktop\patched_magisk.img")

Guide to Rooting the Infinix Hot 30 Play, With Magisk

Preface​Luckily, it looks like Infinix is following the general trend of Android root solutions being more straightforward than in the recent past. Besides the usual spiel about your warranty being voided, and the annoying chirp each time you boot your phone, this hopefully won't present any problems for you if you do end up rooting your phone.
Notices​
Still, I'm not responsible for anything bad that will happen to your phone if you do this, and there's no support guaranteed either from me or your OEM/support centre.
There's quite a few steps to this, and naturally you're gonna need a few more things to setup before you even start.
Your phone's data will be reset, please backup everything you'd like to keep before rooting your phone (now and in general).
You do need to know some things already, mainly what ADB and Fastboot are, and how to keep your working environment clean and straightforward.
Please do review all the tools you're working with, be sure that you personally trust all the software you're running.
And last but not least, you won't be able to update your phone through OTA updates anymore unless you go back to stock firmware.
The process​
Make an environment for easy access:
Setup ADB and Fastboot (either as a local executable or a global environment variable to that executable).
Setup an easy to access directory with the Google Fastboot driver in it.
Grab your firmware's boot.img file, or grab the one attached to this post, or from here (and skip to the preliminary work section):
1. Download your phone's current ROM.
2. Extract it, as it should be a simple .zip file.
3. Look for the file of the same name (boot.img).
4. Copy it to your phone's storage, anywhere works.
Install the Magisk APK (from their Github).
Once it's installed, Magisk's app frontend allows you to patch your stock boot.img with itself, the gist of it is:
Click on Install within the app, in the "Magisk" section of the main menu.
Click "Select and patch a file", a file selection menu will show up, select the stock boot.img, then start the installation.
Magisk should spit out a patched boot.img named in the format of magisk_patched_[random_strings].img, in your phone's /sdcard/Download/ directory.
Copy that back into our working directory, and rename it to magisk_patched.img for easier usage.
Now, let's do some preliminary work, in any order, really:
Have Powershell or CMD open in the directory of all your tools, alongside the patched image.
Click to expand...
Click to collapse
From here on out, if you have to use adb as a command, and it's not a global environment variable, use ./adb while in the working directory instead, the same goes for fastboot.
Click to expand...
Click to collapse
Make sure that the adb daemon (adbd) is properly detecting your phone:
Enable developer options.
Enable ADB debugging.
Run adb devices to start the server daemon for ADB, and see if ADB detects your phone.
Authorize your PC for ADB debugging if it prompts you to.
Click to expand...
Click to collapse
Infinix's implementation of Fastboot will exit back out of itself and into normal boot after 60 seconds of inactivity, which makes this a tad annoying, although you can simply send it any input to reset that timer.
Click to expand...
Click to collapse
Let's start:
Restart the phone into Fastboot, adb reboot bootloader loader, it'll take a second, the phone is slow.
Unlock flashing 3rd party software, fastboot flashing unlock, the phone will prompt you on the screen to confirm doing this. Yes, this will void your warranty.
Flash magisk_patched.img to both A and B virtual partitions, fastboot flash boot_a magisk_patched.img and then fastboot flash boot_b magisk_patched.img.
That should be it! fastboot reboot to boot normally!
Be sure to also run the Magisk app so it finishes setting itself up, with another reboot, naturally.
Technicalities​The Infinix Hot 30 Play does have a dedicated vbmeta partition, it's advised that you also flash it alongside flashing the patched boot.img for Verified Boot, but that's not necessary if you don't want to tinker with your super partition's crypto keys.
Thank yous​- topjohnwu for their work on Magisk.
- ansh_/ and their post/guide on rooting the Infinix Hot 11, that I used originally.

Addendum​
Using fastboot with MediaTek SoCs will be a bit of a pain as their driver availibilty is limited, if it doesn't get installed by Windows automatically, you have a few options:
Grab the Google's Pixel driver, and install it in realtime during fastboot.
Try to install the VCOM driver from a source you trust.
For grabbing the Google one, you'll have to:
Extract the driver somewhere easy to access.
Open Windows' Device Manager.
Plug in your phone during fastboot to your Windows PC.
Replace the "Unknown" entry for your phone with the Google driver in device manager, within the 60 second window it stays open in.
Note that you'll have to do this every time you go into fastboot.