Database Develop

[Q] Unlocked N1 - But Root Fail - ERROR- could not get pipe properties (MAC)

hi there,
been busy all evening on my Mac trying to unlock and root my nexus one retail. Got the phone unlocked after extensive reading on SDK and ADB Hoped that the positive flow would continue when switching over to the rooting process, but unfortunately I seem to get stuck and have failed
I downloaded the correct superboot version for my phone and placed it in my home folder (on same drive as where I successfully did the fastboot procedure for unlocking). And then I entered this in Terminal:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /superboot
suikerchiller-macbook-3:superboot suikerchiller$ chmod +x install-superboot-mac.sh
suikerchiller-macbook-3:superboot suikerchiller$ ./install-superboot-mac.sh
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... OKAY
suikerchiller-macbook-3:superboot suikerchiller$
---
As a result my phone automatically reboots into basic settings. Does anybody know what I'm doing wrong??? I'm a total n00b but am really eager to learn In a bit of trouble now as well, because I don't know what to do anymore and dare to touch my fone either.
Any help would be great. Can't wait to finally be released from Vodafone's retail nexus one terror and want to challenge all those ignorant iphone studs out there and show how cool and superior my Nexus one actually is
P.S. I searched for quite some time on the forum and couldn't find a post/thread that was related to my problem. Please forgive me if this is some sort of double post.

If your phone is unlocked, don't bother with superboot, just flash a custom recovery and use it to install the su zip...
http://forum.xda-developers.com/showthread.php?t=682828
Place the recovery image in your sdk tools folder, place the su zip on your sd card, connect via fastboot and type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Flash the su zip from recovery, and you're done!

many many thanks for the quick reply I placed the recovery image in my sdk tools folder.
However, still have a couple of questions:
I don't know what you exactly mean with a su zip??? Where can I get this file?
what do you mean with: "flash the su zip from recovery"?

I put a link in my original post. The eclair/froyo version works for gingerbread, also...
Once in recovery, you chose the flash zip from sd option, and then the chose zip from sd option, find and select the zip... It will be obvious when you do it...

sorry, it's still too much rocket science for me I guess
I uploaded the su zip file (did not unzip or rename file) to my sd card (activated usb storage and dropped the zip via Mac in the main folder of my phone).
what do you exactly mean with "connect with fastboot"? I shut down my fone first and pressed power button at same time with track ball. Then I did this:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:~ suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ cd ~
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
As you can probably see it didn't really work haha what am I doing wrong? Sorry for my n00biness!

You said you have already unlocked your bootloader. In order to unlock the bootloader I you have to connect with fastboot...
How did you unlock the bootloader?

I unlocked it via the first 7 steps of this procedure (sorry have to copy paste a lot of text because im not allowed to post outside links on forum yet haha):
-----
Connect your Nexus One to your PC/Mac and turn it off.
Hold the trackball and hit the power button (while holding the trackball). You should see the following bootloader screen.
Now from the files you downloaded previously, you will see a folder called ‘fastboot‘ (if you extracted fastboot.zip that is!).
On a Windows machine – launch Command Prompt and CD to fastboot folder. (Type in ‘cd ‘ (without the quotes and drag and drop the fastboot folder to the command prompt). Type in ‘cd fastboot‘ again and now type the following command ‘fastboot-windows oem unlock‘ (without quotes) and hit enter.
On a Mac or Linux machine – launch the Terminal and CD to fastboot folder (type in ‘cd ‘ and drag and drop the folder. Now hit enter.). Now CD to the other fastboot folder and type the following (without quotes): ‘./fastboot-mac oem unlock‘ (for Mac) or ’./fastboot-linux oem unlock’ (for Linux) and hit enter. You will see the following. Ignore the error.
This is the screen that you will see now. Use the volume button (on the side) to select ‘Yes’. (Please read the full message displayed on the screen thoroughly). Now push the Power button to select this option (weird, I know. Trackball would have been a better choice to select!).
Great! You have successfully unlocked the bootloader! You will see the unlock image while your phone boots up.
----
I did this successfully and had the black screen and selected unlock phone. So when I press the power button & trackball at same time now I get a white screen now and it says in pink on top: ***Unlocked***

Ok substitute the term fastboot-mac instead of fastboot, into my previous instructions

damn, still doesn't seem to be working:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
----
it's really weird, it looks like my fastboot is not responding anymore... Any idea what's going wrong here???
thanks so much for taking time and helping with figuring this one out!!!

Just tested something. When my phone is switched on normally and connected via USB, Terminal recognizes it as an adb device. However, when I switch into fastboot, Terminal doesn't recognize it:
---
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
HT07YP804207 device
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???

adb will only work when it can see the adbd on your phone, so the phone had to be booted to either recovery or fully bolted.
fastboot will only connect when your phone is booted in fastboot. If its not connecting, reboot your phone and mac and try again...

suikerchiller said:
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
Click to expand...
Click to collapse
Sorry, just re-read this...
Command not found, NOT device not found.
You should be typing fastboot-mac, not fastboot...
Do you have a file called fastboot-mac in the same folder as your adb and recovery img?

rebooted my mac and phone... Still no difference, this is my latest command:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
---
can this be the reason: my fastboot folder is in a different (other) folder than my 'android sdk' folder... should i drag and drop fastboot into the tools folder of sdk???

YES!
Put the fastboot-mac file in the same folder as the other stuff!! xD

haha ok, so I copied my fastboot-mac file (original file from fastboot folder) into AndroidSDK/tools folder. It's in the same folder now where the .img file is in as well.
But it still doesnt seem to be working. These are the commands that I have been using:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac boot recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$
---
What's going wrong??? I'm going slightly mental now. Also running out of beer at same time. Not a good combination

can you list the contents of that folder, and tell me what result you get?

this is the list of files in my AndroidSDK/tools folder:
--
suikerchiller-macbook-3:tools suikerchiller$ ls
Jet hierarchyviewer
NOTICE.txt hprof-conv
adb-mac layoutopt
adb_has_moved.txt lib
android mksdcard
ant monkeyrunner
apkbuilder proguard
ddms recovery-RA-passion-v2.2.1-CM.img
dmtracedump source.properties
draw9patch sqlite3
emulator traceview
etc1tool zipalign
fastboot-mac
---

and here are the commands for fastboot, in case they can be of any usage
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id

Hmmmmm, well the file is there, so that's really weird because you mac is definately saying that it's the command it can't find...
I'm not much of a mac guy, but I do know that your mac is the one having the problem...
Try:
./fastboot-mac flash recovery name-of-recovery.img

suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
sending 'recovery' (3380 KB)... OKAY
writing 'recovery'... OKAY

fastboot FAILED (command write failed (Bad file descriptor))

Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s

at first glance it sounds like your file is corrupt, have you already tried to redownload it?
as long as fastboot stops immediately and does not actually write stuff in your phone you should be safe anyway

Check the file for any possible download errors.

abr4xas said:
Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Click to expand...
Click to collapse
Try upgrading bootloader / redownloading file and flashing

abr4xas said:
Hi there,
Need help with showthread.php?t=1785010
Code:
$ fastboot flash recovery recovery.img
sending 'recovery' (5002 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Click to expand...
Click to collapse
This happened to me too, it was just that the file was not there, I had SU and path was not correct. So the next person who comes here looking for the solution for this.... yes you! do a "ls" or "dir" and see that the recovery.img or boot.img or whatever you are trying to flash is even there. :victory:

shieraz said:
This happened to me too, it was just that the file was not there, I had SU and path was not correct. So the next person who comes here looking for the solution for this.... yes you! do a "ls" or "dir" and see that the recovery.img or boot.img or whatever you are trying to flash is even there. :victory:
Click to expand...
Click to collapse
Did anybody find a solution to this problem, yet??
BTW: it says "error: cannot load 'xxxxx.img': No such file or directory" if it can't find the file. "FAILED (command write failed (Bad file descriptor))" seem to be a different issue. Maybe inside the phone, when it can't find the partition it should flash. No idea. However, I'm stuck with "FAILED (command write failed (Bad file descriptor))" and appreciate your help!
I'm trying to run it on Debian 8.1 AMD64. Here is some code:
[email protected]# fastboot -i 0x413c flash recovery 407recov.img
sending 'recovery' (3660 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]# file 407recov.img
407recov.img: Android bootimg, kernel (0x20008000), ramdisk (0x21000000), page size: 2048, cmdline (androidboot.hardware=streak)
[email protected]# cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
[email protected]# ls -l /etc/udev/rules.d/51-android.rules
-rw-r--r-- 1 root root 56 Sep 17 15:51 /etc/udev/rules.d/51-android.rules
[email protected]# fastboot -l devices
Default# fastboot usb:1-10
[email protected]# fastboot -i 0x413c reboot
rebooting...
finished. total time: 0.002s
[email protected]#
As you can see, "fastboot reboot" works, but not "fastboot flash". This dies with that pesky message "FAILED (command write failed (Bad file descriptor))".

[email protected]# fastboot -i 0x413c flash recovery 407recov.img
Click to expand...
Click to collapse
I don't use Debian/Linux but... Fastboot command to flash a partition would be
Code:
fastboot flash recovery 407recov.img
as I've never had to type in anything else as -i 0x413c
Sent from my HTC One_M8 using XDA Free mobile app

Antagonist42 said:
I don't use Debian/Linux but... Fastboot command to flash a partition would be
Code:
fastboot flash recovery 407recov.img
as I've never had to type in anything else as -i 0x413c
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
This "-i 0x413c" part makes the device selection specific. It's not needed if there is only one device connected.
However, I found (and fixed) the problem. More detail here:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=800661

bomilkar said:
However, I found (and fixed) the problem. More detail here:
bugs.debian.org/cgi-bin/bugreport.cgi?bug=800661
Click to expand...
Click to collapse
How did you fix it? Corrected the sourcecode and recompiled android-tools-fastboot?!

PeterCxy said:
Check the file for any possible download errors.
Click to expand...
Click to collapse
Sir I want your help
E:\Mobile\adb>fastboot -i 0x2A96 boot twrp.img
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
This is show on my yophoria when I flash custom recovery

My phone is Desire HD, but this worked for me to solve the problem.
Try this:
http://forum.xda-developers.com/showthread.php?t=1474490
Originally Posted by CostaTX
Connect phone via usb and turn on debugging/just charging
Open up cmd (eventually as administrator) and type in "adb shell"
Find out how your system partition is named: "cat /proc/mounts | grep /system"
Mount system partition write/read. replace the X's "mount -o remount,rw -t yaffs2 /dev/block/XXXXX /system"
Use the terminal emulator to install the recovery:
su
flash_image recovery /sdcard/touch.img (or whatever the recovery image is named)
remount the system partition again as read only "mount -o remount,ro -t yaffs2 /dev/block/XXXXX /system
and you're done
Click to expand...
Click to collapse
"cat /proc/mounts |grep system" and command "mount -o remount,rw ..."
You can change by "mount -o remount,rw /system"
"mount -o remount,ro" by "mount -o remount,ro /system"
Code:
adb shell
$ su
# mount -o remount,rw /system
# flash_image recovery /sdcard/recovery.img
# mount -o remount,ro /system
# exit
$ exit

pls help..how to solve this.
writing 'userdata'...
FAILED (remote: flash_cmds error!
it fail when i using fastboot -w command.
my phone bricked, can use fastboot and adb.
but when i apply "update.zip via adb" using "adb sideload update.zip" it cannot read "update.zip" .
so i start using fastboot to flash but it failed.

fastboot FAILED (in various ways for various versions)
I've now tried 3 releases of android platform-tools. I had hoped that one of these included the fix posted on XCSoar forum (for the original reason for this thread) but I'm not convinced that's so. I tried both:
1) platform-tools issued with ubuntu 14.04
2) platform-tools_r25.0.5-linux
3) platform-tools_r26.0.0-rc1-linux.
When trying to upgrade my Dell Streak 5 beyond 2.2, none of these work, but of course they fail in different ways to fastboot released with ubuntu 14.04 (which is my main machine, I don't have a windows machine).
Running platform-tools_r25.0.5 or platform-tools_r26.0.0-rc1, I get:
/bin/platform-tools_r26.0.0-rc1$ sudo ./fastboot -i 0x413c flash recovery ~/recovery.img
target didn't report max-download-size
sending 'recovery' (3668 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Whereas running the (14.04) issued fastboot I get (notice the use of DOT/fastboot and fastboot to select the right one), I get:
sudo fastboot -i 0x413c flash recovery ~/recovery.img
sending 'recovery' (3668 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Interestingly when I run /(25.0.5 or 26.0.0) :
$ ./fastboot -i 0x413c reboot
the DS5 doesn't reboot.
However if I run the 14.04 fastoot, ie:
$ fastboot -i 0x413c reboot
the DS5 reboots.
Has anyone else come across these problems? If so what's the solution?

SK_Raj said:
Sir I want your help
E:\Mobile\adb>fastboot -i 0x2A96 boot twrp.img
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
This is show on my yophoria when I flash custom recovery
Click to expand...
Click to collapse
solved?

Is there a way of getting *Locked* bootloader via CMD?

Hey.
I'm currently working on a method to lock the ONE's bootloader compelitly via cmd.
I dont know if there is any fastboot command , but is it?
And is there any way to transfer revone to the phone and use the terminal on the computer instead of the one is the phone?
Tnx

TunneIVision said:
Hey.
I'm currently working on a method to lock the ONE's bootloader compelitly via cmd.
I dont know if there is any fastboot command , but is it?
And is there any way to transfer revone to the phone and use the terminal on the computer instead of the one is the phone?
Tnx
Click to expand...
Click to collapse
Umh, do you have a custom recovery?
If yes, use the guru zip.
However, you can use the revone from the cmd of pc
And you can also use the command for lock in recovery.

Guich said:
Umh, do you have a custom recovery?
If yes, use the guru zip.
However, you can use the revone from the cmd of pc
And you can also use the command for lock in recovery.
Click to expand...
Click to collapse
I dont have a custon recovery , and I'd like to hear how
" you can use the revone from the cmd of pc
And you can also use the command for lock in recovery "

TunneIVision said:
I dont have a custon recovery , and I'd like to hear how
" you can use the revone from the cmd of pc
And you can also use the command for lock in recovery "
Click to expand...
Click to collapse
Code:
adb push revone /data/local/tmp
Code:
adb shell
Code:
cd /data/local/tmp
Code:
chmod 755 revone
And after you can use the revone commands

Guich said:
Code:
adb push revone /data/local/tmp
Code:
adb shell
Code:
cd /data/local/tmp
Code:
chmod 755 revone
And after you can use the revone commands
Click to expand...
Click to collapse
So I should do the whole proccess in the computer? but how does the computer get into the tmp folder of the phone?
And is there a command in the (computer) CMD for factory reset?
Thanks

TunneIVision said:
So I should do the whole proccess in the computer? but how does the computer get into the tmp folder of the phone?
And is there a command in the (computer) CMD for factory reset?
Thanks
Click to expand...
Click to collapse
Yes, you can do the process with the pc.
When you use the adb shell code you're "into" you phone, so you will see all the folder/file of the phone...
Nope, as i know, there isn't any command for the factory reset from prompt.
Seems i'm using my One...

Guich said:
Yes, you can do the process with the pc.
When you use the adb shell code you're "into" you phone, so you will see all the folder/file of the phone...
Nope, as i know, there isn't any command for the factory reset from prompt.
Seems i'm using my One...
Click to expand...
Click to collapse
I found this in some site , and I lighted what seems to be a wiping command , but I cant really get it.
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] 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
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable

TunneIVision said:
I found this in some site , and I lighted what seems to be a wiping command , but I cant really get it.
fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] 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
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
Click to expand...
Click to collapse
Probably should work, but i never checked because for a factory reset i flashed the stock recovery and permformed it from bootloader
Or do a full wipe, that is the same, from recovery
Seems i'm using my One...

Question [CLOSED] NE2210 Bootloader Unlock Fail!

I am trying to unlock the Bootloader on my OP10P but I keep facing failure even after trying more then one Unlock Command.
Device Model: NE2210
Build: NE2210_11_A.16
Here are my results:
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> adb devices
List of devices attached
b3b5a915 device
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> adb reboot bootloader
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> fastboot devices
b3b5a915 fastboot
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> fastboot flashing unlock
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
than size. 0 to disable
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools>
*Edited Post to focus on the Major issue of Bootloader not unlocking only, will ask other question once this issue is dealt with*

try fastboot oem unlock
also, ensure dev options - unlock bootloader is checked.

miffymiffy said:
try fastboot oem unlock
also, ensure dev options - unlock bootloader is checked.
Click to expand...
Click to collapse
- Dev options Enabled
- Unlock Bootloader Checked
- USB Debugging Checked
Results:
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools>

BL4KMRK8 said:
- Opções de desenvolvimento ativadas
- Desbloquear Bootloader Verificado
- Depuração USB verificada
Resultados:
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools> fastboot oem unlock
...
FAILED (remoto: comando desconhecido)
finalizado. tempo total: 0,000s
PS C:\Users\bl4kp\OneDrive\Desktop\platform-tools>
Click to expand...
Click to collapse
command used is wrong , use command: flashing unlock

TrajanoX3 said:
command used is wrong , use command: flashing unlock
Click to expand...
Click to collapse
He tried that first and got same issue

Also, make sure your ADB/fastboot is up to date

miffymiffy said:
Also, make sure your ADB/fastboot is up to date
Click to expand...
Click to collapse
miffymiffy said:
He tried that first and got same issue
Click to expand...
Click to collapse
Yes i tried this first.

miffymiffy said:
Also, make sure your ADB/fastboot is up to date
Click to expand...
Click to collapse
I am using platform-tools_r33.0.2-windows

type fastboot flashing unlock
Agree to unlock - allow to boot

download and install the tools in my sig

spevil07 said:
type fastboot flashing unlock
Agree to unlock - allow to boot
Click to expand...
Click to collapse
That's the first thing he tried

GbnrVR said:
That's the first thing he tried
Click to expand...
Click to collapse
Oh I see, haven't seen it directly

spevil07 said:
type fastboot flashing unlock
Agree to unlock - allow to boot
Click to expand...
Click to collapse
I have tried this command already with no results (it's the command I used in the first post)

g96818 said:
download and install the tools in my sig
Click to expand...
Click to collapse
I'll give that a shot once I make it back to the computer. Had to take a "woosaa" break due to frustration lol
** Update. Bootloader is now unlocked tyvm!!! **

Can you tell us what you did after all the "unable posts"?? Bootloader unlocked won't help others see what went wrong. Thanks

I used the files in the Signature as suggested and the "fastboot flashing unlock" command worked no problem.
I put together a little guide as best I could to detail my process. Hopefully it helps! (Click link below & it should be post #39)
Chinese Model Running Global Rom Region Change
I was wondering if changing an already converted Chinese model from NE2215 to NE2213 is less risky than the initial conversion? Any models I see are already on the Global ROM and I want it to be on the EU ROM, and was hoping there was an easy...
forum.xda-developers.com

Hi. use my script
AFH

g96818 said:
download and install the tools in my sig
Click to expand...
Click to collapse
Thanks mate.
platform-tools_r33.0.0 from his signature worked for me aswell. I was getting an error on command adb flashing unlock

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.