Database Develop

[Q] Help: Unable to flash TWRP on unlocked bootloader after 4.4 update

I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?

danherbert said:
I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
Click to expand...
Click to collapse
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Sent on my Moto X

flashallthetime said:
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Click to expand...
Click to collapse
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.

danherbert said:
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
Click to expand...
Click to collapse
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Sent on my Moto X

flashallthetime said:
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Click to expand...
Click to collapse
Your suggestion worked. I didn't have easy access to a Windows machine so I couldn't use rsdlite. I had to manually reset to stock. For anyone who stumbles upon this thread, these are the steps I used which worked for me:
Make sure adb and fastboot from the Android SDK are already part of your PATH.
Download moto-fastboot for Mac OS X
Download the Kitkat 4.4 update for Sprint (Make sure to download the version that matches the build number from "Settings -> About Phone" in your device)
Download the Kitkat 4.4 version of TWRP
Extract the factory image .zip to a folder
Copy the moto-fastboot binary to the folder you extracted the factory image to and rename it to "mfastboot"
Copy the TWRP .img file to the folder with the factory image files
Create a file named "factoryreset.sh" and paste the following as its contents
Code:
#!/bin/sh
FASTBOOT=./mfastboot
$FASTBOOT getvar max-download-size
$FASTBOOT oem fb_mode_set
$FASTBOOT flash partition gpt.bin
$FASTBOOT flash motoboot motoboot.img
$FASTBOOT flash logo logo.bin
$FASTBOOT flash boot boot.img
$FASTBOOT flash recovery recovery.img
$FASTBOOT flash system system.img
$FASTBOOT flash modem NON-HLOS.bin
$FASTBOOT erase modemst1
$FASTBOOT erase modemst2
$FASTBOOT flash fsg fsg.mbn
$FASTBOOT erase cache
$FASTBOOT erase userdata
$FASTBOOT erase customize
$FASTBOOT erase clogo
$FASTBOOT oem config carrier sprint
$FASTBOOT oem fb_mode_clear
Open a terminal and navigate to the directory you created
On your device, navigate to "Settings -> About Phone" and tap on the build number 7 times to enable developer mode
Go back to the main "Settings" screen, open "Developer Options", and enable USB Debugging
Connect your device to your computer. Go back to your device, make sure you choose to trust your computer to use ADB in the dialog that pops up, then run the following command from your terminal
Code:
adb reboot-bootloader
Once your device is in fastboot mode, run the command
Code:
sh factoryreset.sh
From the device choose to boot normally and wait for it to finish booting completely.
Run the command
Code:
adb reboot-bootloader
Once the device is in fastboot mode again, run the command
Code:
fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
From your device, power up normally then reboot into the recovery. If everything went smoothly you'll boot into TWRP recovery.
Code:
adb reboot recovery

Unable to Root MRA58N

I have been going at it for a week straight and unable to find help. I am using Nexus Root Tool Kit 2.1.0. My Device is unlocked and OEM unlocked. However when i try to root the phone restarts into AP Fastboot Mode and nothing happens but the program seems like its trying but just unable to finish.
Log File:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3099
- AndroidDeviceListFull.ini 3099
- AndroidDeviceListFlash.ini 3099
SHAMU-SHAMU: Android 6.0.0 - Build: MRA58N
Live log initiated [2015-11-28]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Flashing Root Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_shamu_mra58n.img"
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Rebooting your device...
Waiting for your device...
I have also tried to flash a custom boot.img but NRT stops at rebooting device.
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Flashing boot.img to BOOT partition...
fastboot flash boot "C:\Users\Dave\Desktop\volantis-mra58n-boot-system\boot.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
my screen just never does anything i remember last time i rooted on Android L it went with no problems.
just stays at
AP Fast boot Flash Mode (Secure)
BL: moto-apq8084-71.15 (sha-96f7faf, 2015-08-04 11:36:17)
Base Band : D4.01-9625-05.27+fsg-9625-02.104
just installed ADB and tried from command prompt to flash TWRP and i got failed (data transfer failure (unknown error) )

well, you are doing it wrong for a nexus owner, you dont need a root toolkit. to root m you need to flash any custom kernel for m as well as the latest supersu(as well as the latest twrp recovery so you can flash a custom kernel and supersu).

Don't use Root kits and follow these steps. Start from step 1 if you already have your bootloader unlocked and if you have SDK tools installed (adb and fastboot). And you should be fine...

yes wont let me install recovery TWRP
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
C:\Program Files (x86)\Android\android-sdk\platform-tools>

thats because you dont use adb for this. you have to use fastboot while you are in your recovery. read that again, FASTBOOT instead of ADB. you always use fastboot to flash the factory image or any part of it, or twrp recovery.

simms, the command he posted that failed WAS fastboot.
HOWEVER, if adb is reporting devices, you are likely either booted to android or recovery... reboot to the bootloader
(turn off device, then hold volume down and while holding vol down press and hold power until the device boots to the bootloader mode.
Make sure that you have twrp in the same folder, and that you have renamed it to recovery.img (not .img.img as a lot of people accidently do) That last part isn't completely necessary, as its really just "fastboot flash recovery <file name>", and you can replace <file name> with the name of the recovery image it doesn't HAVE to be recovey.img, and it doesn't have to be in the same folder if you include path... but people find it easier to just rename it to recovery.img, copy it to their platform tools folder and use the command you ran.

ahh.. yea @scryan i didnt see that fastboot was used(later in the post). now i see hes uding adb devices instead of fastboot devices.

As far as I can see, you are trying to flash recovery using fastboot flash recovery recovery.img while not in bootloader (or you didn't copy everything you did).
You should:
1. adb reboot bootloader (your phone will reboot into bootloader)
2. now you can write "fastboot devices" to see if your phone is recognized
2. then if it's there: "fastboot flash recovery recovery.img"
EDIT: If you still did everything correctly, quick google search said it could be problem with computer's USB port. Try another port...

I have tried every port on my pc some give unrecognized USB error while others work. If I am able to charge and transfer files along with send adb commands (restart phone,adb sees my phone) does that rule out the USB cable? I bought a pack of four on ebayhttp://m.ebay.com/itm/4x-6Ft-Micro-USB-Charger-Sync-Data-Cable-Nylon-Braided-for-Samsung-Galaxy-HTC-/221891441910?txnId=1650092351012
I no longer have the cable I used to flash marshmallow but I did use this to unlock the device.

Problem installing not incremental ROM

Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.

I am on mac so cannot use Mi Flash

EMJI79 said:
Well I have tried to install MIUI ROM 6.5.26 after not processing updates for months (since november).
So I downloaded latest ROM and put it to the top of the partitions and then I wiped everything and that's where i might have done a mistake: I wiped internal storage (inside TWRP 2.8.7 i found there http://forum.xda-developers.com/mi-...timizing-leo-miui-advanced-tweaks-to-t3286972) then I might have might done a second mistake: I have done the command fastboot 'flash boot boot.img' as I read on an old HTC forum.
Then I pushed the latest ROM to the phone (as it was not there after the wipes) and when I tried installing it, it gave E: unable to mount 'cache' .
Now it seems i cannot enter TWRP, only Fastboot or I am stuck with MI logo.
I just want to install latest ROM, as I have done Titanium Backup before all the mess.
I don't know where i should start.
Click to expand...
Click to collapse
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader

helderfp said:
you wiped internal sd so you have nothing the only way to solve is
Download the fastboot ROM https://www.dropbox.com/s/dg198q49dctzfgr/leo_images_5.11.26_20151104.0000.4_5.1_cn.tar.gz?dl=0 (recomend this others from this year locked bootloader)
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
10. Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash tz tz.mbn
C:\Fastboot>fastboot flash dbi sdi.mbn
C:\Fastboot>fastboot flash sbl1 sbl1.mbn
C:\Fastboot>fastboot flash rpm rpm.mbn
C:\Fastboot>fastboot flash aboot emmc_appsboot.mbn
C:\Fastboot>fastboot erase boot
C:\Fastboot>fastboot flash misc misc.img
C:\Fastboot>fastboot flash modem NON-HLOS.bin
C:\Fastboot>fastboot flash system system.img
C:\Fastboot>fastboot flash cache cache.img
C:\Fastboot>fastboot flash userdata userdata.img
C:\Fastboot>fastboot flash recovery recovery.img
C:\Fastboot>fastboot flash boot boot.img
C:\Fastboot>fastboot reboot
Now you're all set and should be able to boot normally.
after you can install recovery
to install recoverytwrp https://www.dropbox.com/s/hkuwc6d881im2hy/TWRP_leo.zip?dl=0
Extract it to the same directory you extracted ADB/Fastboot
Press "Windows key + X" -> "Command Prompt (administrator)
In command prompt, go to your folder where your ADB/Fastboot are, assuming they are in C:\Fastboot, you type
> cd C:\Fastboot
> C:
Once in the "C:\Fastboot" folder, you will need to issue a chain of commands to flash critical images, so type:
C:\Fastboot>fastboot devices
C:\Fastboot>fastboot flash recovery TWRP.img
C:\Fastboot>fastboot reboot
done now you can install latest rom from xiaomi.eu Does not locked bootloader
Click to expand...
Click to collapse
OK thanks a lot. :good:
I will try that tonight or tomorrow (already downloading from your dropbox, thanks again).
I'll let you know.

Only i dont understand: (recomend this others from this year locked boot loader) ?

EMJI79 said:
Only i dont understand: (recomend this others from this year locked boot loader) ?
Click to expand...
Click to collapse
It broke halfway, so I am trying again. Thank you for your patience.

Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:

EMJI79 said:
Well, I downloaded it entirely and tried "fastboot the tz", then I get -> "device is locked. Cannot flash images"...
So I guess I locked my bootloader already, somehow... :crying:
Click to expand...
Click to collapse
ok
so you have to do this
Download Xiaomi MiFlash Tool and install it to your PC https://www.dropbox.com/s/1qntzckybxg3rr4/MiSetup3.2.1.3111_2717.zip?dl=0
Download Qualcomm Driver 32-bit https://www.dropbox.com/s/klnn6h9z7038u80/QDLoader HS-USB Driver_32bit_Setup.zip?dl=0 OR Qualcomm Driver 64-bit https://www.dropbox.com/s/gvizx1ja1vmihox/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0 install it to your PC
Enter your phone in fastboot mode
in command promt wrtite:
cmd
cd C:\fastboot
fastboot devices
fastboot oem edl
After the last command Your Note pro detected as a new device
Launch MiFlash and flash Note pro not locked ROM if you get one error at the midle (not at the beginnig) of flashing dont worry, you have unlocked bootloader, and you can folow the previous steps you already tried
The latest roms from xiaomi (since January 2016) lockes bootloader that is why i recomend that on the link.

Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...

EMJI79 said:
Thanks
But I am on Mac, no MiFlash, only ADB, fastboot...
Click to expand...
Click to collapse
to work on mac
Download the fastboot ROM for your Mi phone and place it on your desktop. Double-click on it and Archive Utility will extract the file on the desktop, so you'll get a folder,
now go to terminal an type
cd C:\fastboot
fastboot devices
fastboot oem edl
In order to use the fastboot scripts, you should go to the folder. For that purpose, execute the following command (the folder name may be different in your case, the example below is for cancro):
cd ~/Desktop/cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global
Copy the Code
Quick tip: you don't need to write the whole folder name, just type cd ~/Desktop/cancro, then press the Tab key and Terminal will append the folder name automatically.
Once inside, you need to make the scripts (all the files with .sh extension) executable. Execute the following command:
chmod +x ./*.sh
Now, the scripts are ready to use. In order to start the process, issue one of the following commands:
./flash_all.sh
or
./flash_all_except_storage.sh
or
./flash_all_except_data_storage.sh
When you start any of the scripts, you'll see the fastboot messages, flowing through the Terminal window. Once the script has done its work, the phone will restart itself automatically.

When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.

EMJI79 said:
When I change directory for the fastboot ROM directory, the fastboot screen on my phone disappears. I have done the steps after that but i see no message on the terminal or the phone screen. My phone screen is black.
Edit: In fact the fastboot screen on my phone disappears when I type fastboot oem edl in my terminal although i get the message OKAY in my terminal.
Click to expand...
Click to collapse
so don't change the directory put the rom in the fastboot folder and do the next step
if you are not able to flash in your mac try in another pc (windows)

Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?

EMJI79 said:
Don't you think I just locked my bootloader and I need to do the apply stuff for getting my phone unlocked?
Click to expand...
Click to collapse
you dont need
just try
put rom in fastboot folder and
cd C:\fastboot
fastboot devices
fastboot oem edl
chmod +x ./*.sh
./flash_all.sh
to unlock bootloader the previous steps (not this) work fine on windows
http://en.miui.com/thread-237832-1-1.html
https://xiaomi.eu/community/threads/mi-note-pro-complete-beginners-guide.30817/

every time I type:
fastboot oem edl
the screen of the smartphone goes off

Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?

EMJI79 said:
Maybe I will buy Windows to make it work in VM...
Only can you interpretate why fastboot oem edl makes the screen go off?
Click to expand...
Click to collapse
do you have qualcom drivers instaled?

No
Will try tomorrow.
Thanks again.
The link to your dropbox for Qualcomm drivers is for Windows, i found that:https://developer.qualcomm.com/download/software
and Snapdragon SDK but I have to register.

Is Snapdragon SDK actually Qualcomm drivers?

helderfp said:
do you have qualcom drivers instaled?
Click to expand...
Click to collapse
Hello,
OK, no Qualcomm drivers for Mac it seems... I have searched thoroughly and haven't found. I have asked a en.miui dev and waiting for the response.. Don't have them?

BQ Aquaris M10 FHD failed image upload

Hi friends,
The app recommended by BQ "MTK Tool Flash" (SP_Flash_Tool_exe_Linux_v5.1612.00.100.zip) just didn't work for me on my Debian PC. There were always some excuses. So I tried some black command-line magic with fastboot and now I'm with a bricked device.
See ubuntu-android-installation-process-for-bq-aquaris-e4-5-and-e5 link I cannot post...
The good news is, I have installed the TWRP (twrp-3.1.1-0-freezerfhd.img) before I shot myself in the toe. So power + volume up gives me the comforting bluish screen of TWRP.
Question is, how can I bring the lovely device back to life? I wanted to flash official Android on it (which failed - 2.3.0_20170405-1553_bq_aquaris_m10_FHD_-FW.zip) and I'd like to complete that, but if it's a no go, I can go back to Ubuntu.
I have tried installing the image zip from twrp, but it said the image has invalid zip file format!
Thanks a lot for your help
Rob

failures
I've been struggling with this one. So I can switch to the bootloader mode and run fastboot commands. However, when I try to flash the system image I get some funny error:
Code:
sudo fastboot flash system ./system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: 0.002s
With the flash tool (after fixing all it's complaints) I'm stuck with a timeout on detecting the USB port (while fastboot works just fine)
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
And with TWRP as mentioned earlier:
Code:
Invalid zip file format
I read the stock rom can be adjusted somehow to allow TWRP to flash it but I'm quite like what...? Android kitchen doesn't list my device as supported.

progress
Aha! This got us further:
Code:
sudo fastboot flash system -u -S 1G ./system.img
Which means do not erase the partition upfront, and sparse the file at max 1 GB.
Code:
sudo fastboot flash userdata -u -S 1G ./userdata.img
sudo fastboot flash boot -u -S 1G ./boot.img
sudo fastboot reboot
Now device is "powered by ubuntu" and stuck there... not sure what's happening

S now I tried flashing some more exotic partitions and the device is completely dead. I hope BQ can help...

undead
Wow, so BQ contacted me right away with a hard reset procedure. The key bit of information I must have overlooked somewhere is that for the flash tool to detect the device, the device must be plugged in while it's off and while the tool is waiting. We're now "powered by android" and system is ready to use. Oh my... thanks BQ

Question OnePlus 10 Pro Bootloader Unable to unlock [NE2215]

Hi,
I am trying to unlock the bootloader as it show status as "Device Lock"
When I try to use the command "fastboot oem unlock", it showed
"
...
FAILED (remote: unknown command)
finished. total time: 0.001s
I then tried "fastboot flashing unlock" but it showed this
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
Any solution to this?

fastboot flashing unlock
Make sure your platform tools are up to date as well - https://developer.android.com/studio/releases/platform-tools

Still the same. This is what I kept getting

When you type in fastboot press tab and it'll populate the actual filename.
I get this with certain setups. Same with ADB, just press tab after typing fastboot or ADB then continue with the same commands as you have..
Could just be your fastboot/ADB files.
. I've got the ones I use in my root guide in this forum, grab it and pop it in the root of C then give it another shot.
Hope you get it sorted

Jcddenton said:
Still the same. This is what I kept getting
Click to expand...
Click to collapse
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.

You go into developer options and tick oem_unlock on?

EtherealRemnant said:
Don't use PowerShell. Use command prompt. People using PS report nothing but problems.
Click to expand...
Click to collapse
The above is what I have experienced myself.. Only ever happens with PS never CMD, not the end of the world though

Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.

Update your platform-tools. I had the same issue trying to unlock my pixel 7.

az_r2d1 said:
Did this issue get resolved ? I am having the same issue. I am using CMD in admin mode.
Click to expand...
Click to collapse
Everything you need is linked in my sig

Unlock oem from setting

ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !

az_r2d1 said:
ok, I figured out my issue. The root cause was the usb cable I was using. I used the oem cable that came with the 6t. IT refused to recognize the phone in bootloader mode ! As soon as I used an aftermarket stock usb-c cable, my pc recognized the phone in bootloader mode !
Click to expand...
Click to collapse
In his case he is actually getting connect currently and it's visible..
As it's an unknown command then it's probably due to PowerShell,, when you type in the command, eg:
fastboot reboot
It won't see the word fastboot itself as the correct command. To fix this just click tab once and it'll populate it's actual name from the list of files in the active folder, so in actual fact the command would be
.\fastboot.exe reboot
Same thing with ADB as a command.
.\adb.exe devices
Just pressing the tab key would do the job.
Or just use CMD and navigate to the folder you'd like to be active

I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!

BeachNYC said:
I'm afraid I don't understand. Brand new 10 Pro, have tried multiple cables, OEM unlocked, boot into fastboot and type "fastboot oem unlock" and it returns "FAILED (remote: 'unknown command')
I can't figure out from this thread whether anyone has a solution. I'm not using powershell, cables changed, so I'm clueless....and don't want to set up the 10 Pro knowing that (hopefully) it will be wiped when the bootloader is unlocked.
Many thanks for any help!
Click to expand...
Click to collapse
Install platform tools, go into the directory that platform tools was installed, and run adb and fastboot thru that, i was getting same error and then went from directory platform tools was unzipped at and it worked fine...fastboot flashing unlock though

fastboot flashing unlock don't work for me!
adb is ok
fastboot reboot and fasboot devices is ok all commands
but not fastboot flashing unlock! on power shell or cmd always the same!
no error just the list
i test different cable or usb plug
i go crazy...

Damned fastboot flashing unlock passed. Don't ask me when. verified all 10 time and voilà !?
First time I like erase all my data
Just CMD like the undred before, but why this time?
I don't know really.
Though lock.