Database Develop

[Q] Sensation XL stuck at HTC screen with warning Triangles in all 4 corners.

Hi can sombody help me my phone will not install ruu and cant do anything now.
It was HBOOT 1.28
S-ON
Software 1.05.401.5
HTC__001
Now i have HBOOT 1.25 by Fardjadb and after that i did something wrong (i think) but dont know wat..
So now it wil turn on and go to htc screen with 4 triangels in all 4 corners with ! in them..
I can not flash or get ruu to work with bootloader 1.25 HELP!!!
try with locked and unlocked still no ruu wil work
plzzz help Android rules it's has too be like 5 day's thats it's not working
really need help on this one

Your CID is europe CID.
Relock bootloader.
PHP:
fastboot oem lock
Download and install:
130

stona175 said:
Your CID is europe CID.
Relock bootloader.
PHP:
fastboot oem lock
Download and install:
130
Click to expand...
Click to collapse
If i do that i get error 132 with ruu
Thanks for your help with this one

Try this or this

stona175 said:
Try this or this
Click to expand...
Click to collapse
Thanks for the info but cant find sigtool.exe
and will try the 2end link now!\
will let you know how it go's
Thanks

Dj-Fantasy said:
Thanks for the info but cant find sigtool.exe
and will try the 2end link now!\
will let you know how it go's
Thanks
Click to expand...
Click to collapse
Sorry don't have recovery but i can flash it but can not eter in to it stuck on htc screen...
Thats y i have ben at this for 5 days now having to use my iPhone pffff

than install recovery.
link on my signature.
or try this or this

stona175 said:
than install recovery.
link on my signature.
or try this or this
Click to expand...
Click to collapse
recovery has ben installed but how do i get in to it see pic at the top this is all i get when phone is on...
Thanks,

Unlock your bootloader.
fastboot reboot-recovery or without -

stona175 said:
Unlock your bootloader.
fastboot reboot-recovery or without -
Click to expand...
Click to collapse
Can't use that comand i get this:
C:\tools>fastboot reboot-recovery
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
-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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\tools>

Dj-Fantasy said:
Can't use that comand i get this:
C:\tools>fastboot reboot-recovery
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
-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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\tools>
Click to expand...
Click to collapse
reboot it normal to htc white screen an try
adb reboot recovery
to fix hboot you need make S-OFF procedure.

stona175 said:
reboot it normal to htc white screen an try
adb reboot recovery
to fix hboot you need make S-OFF procedure.
Click to expand...
Click to collapse
Sorry but my Phone olny starts up with the htc screen in black and when i pull the usb cable out if it is only see white screen see pic this is all i can get..
it only say ruu thats it
Thanks,

try this, maybe this give something. If not than srry but i think you bricked it and only services can do something.
11. Update HBOOT/Radio V3 thx to shingers5​
This operation does not break down your rom. All you have to do after this operation to change the file vold.fstab to 34​
1. Unlock bootloader
2. S-OFF the phone
2. Download the file and put to SDK Android Tool folder.
HBOOT 1.28
3. Get CMD
PHP:
adb reboot-bootloader
Once in bootloader it will say in red fastboot usb.
Click to expand...
Click to collapse
PHP:
fastboot flash hboot_7230ddr2_Runnymede_1.28.0006_20120424.nb0
or type h then tab to auto complete.
4. Reboot the phone to bootloader and check.
PHP:
adb reboot-bootloader
Click to expand...
Click to collapse

stona175 said:
try this, maybe this give something. If not than srry but i think you bricked it and only services can do something.
Click to expand...
Click to collapse
Ok Thanks for your time. ill just use my iPhone now and try to get a new mainboard for my Phone!!

stona175 said:
Unlock your bootloader.
fastboot reboot-recovery or without -
Click to expand...
Click to collapse
AFAIK you can only reboot into recovery from adb not fastboot.
@op. Try pulling your battery, replace it, then connect power lead without switching device on. Usually device should boot into CWM.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2

This only hapend on hboot 1.28 andro
And right only in adb you can boot in to recovery. My misstake.
Sent from my HTC One V using xda premium

My only other thought is, if he can use fastboot commands, he could try flashing a system.img through fastboot.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2

AndroHero said:
AFAIK you can only reboot into recovery from adb not fastboot.
@op. Try pulling your battery, replace it, then connect power lead without switching device on. Usually device should boot into CWM.
Sent from my HTC Sensation XL with Beats Audio X315e using Tapatalk 2
Click to expand...
Click to collapse
Hi adb can not find my phone so its the end of the line for me wil get new mainboard
Thanks for your help..

stona175 said:
This only hapend on hboot 1.28 andro
And right only in adb you can boot in to recovery. My misstake.
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
I have got a new mainboard so my phone is working
Like to thank everyone that has help me..

Download the ruu for your firmware to ur comp and follow instructions, it will sort that out, it will take u to stock rom
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium HD app

[GUIDE][02 Aug 2012]Retired -- Prepare ICS HBOOT 2.02.0002 for S-OFF Downgrade Tool

NOTE: This procedure has been incorporated in nonverbose's Downgrade Script, so it is no longer necessary to run this manually.
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this procedure.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/​
Thanks to attn1, XDA Recognized Developer and author of the Advanced Ace Hack Kit for the HTC Desire HD/HTC Inspire, here is a procedure that you can use if you have upgraded your IncS to the official ICS ROM and you now have HBOOT version 2.02.0002 installed.
As you may have discovered, HBOOT 2.02.0002 can no longer use the tacoroot exploit to gain temproot and thus renders nonverbose's S-OFF Downgrade Tool unusable.
This procedure will require that you use the Unlock Bootloader procedure at HTCDEV.com. Once you unlock the bootloader, you can then flash an unsecured boot image and then you should be able to use nonverbose's S-Off Downgrade Tool.
Here is the procedure:
Unlock the bootloader using the procedure at HTCDEV.com
Unzip vivo_unsecured_boot.zip and verify the MD5 checksum of the boot.img
Copy the boot.img file to the same directory where you have installed fastboot.exe
Enter FASTBOOT USB mode and flash the unsecure boot.img file using the following:
fastboot flash boot boot.img
You can now proceed with running the S-OFF Downgrade Tool
Thanks to attn1 for documenting a work-around that was the basis for this post (http://tau.shadowchild.nl/attn1/?p=88)
Thanks to nonverbose for his S-OFF Downgrade Tool and support to the IncS community.
NOTE: This procedure has been incorporated in nonverbose's Downgrade Script, so it is no longer necessary to run this manually.

Thanks for this, I was actually in the process of creating one myself for testing purposes. More specifically, if it would work on a locked bootloader using the command "fastboot boot boot.img" instead of flashing it, and then continuing on with the script. I don't have much spare time to test but it could be worth looking into.
Edit: my downgrade script in its current state is actually usable with an unlocked bootloader. You just need to flash the superuser binary giving you root and run the script as a rooted user.

Is there any problem if following message appear while relocking?
Code:
<bootloader> lock successfully
FAILED<status read failed <Too many links>>
Finished. total time 0.876s

EvrStngNevDwn said:
Is there any problem if following message appear while relocking?
Code:
<bootloader> lock successfully
FAILED<status read failed <Too many links>>
Finished. total time 0.876s
Click to expand...
Click to collapse
No, there shouldn't be any problem. Go ahead and reboot the phone and then you can start the S-Off Downgrade Tool.

tpbklake said:
No, there shouldn't be any problem. Go ahead and reboot the phone and then you can start the S-Off Downgrade Tool.
Click to expand...
Click to collapse
Thank you for your quick response.
Which thread should i use for S-Off

EvrStngNevDwn said:
Thank you for your quick response.
Which thread should i use for S-Off
Click to expand...
Click to collapse
This thread's purpose was to prepare the phone to use the S-Off Downgrade Tool found here:
http://forum.xda-developers.com/showthread.php?t=1373697

EvrStngNevDwn said:
Thank you for your quick response.
Which thread should i use for S-Off
Click to expand...
Click to collapse
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
continue continue with autoboot
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
is this right and what the Next stip

rambo 11 said:
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
continue continue with autoboot
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
is this right and what the Next stip
Click to expand...
Click to collapse
What steps have you done so far? Did you run step 5 and flash the new boot.img?

tpbklake said:
What steps have you done so far? Did you run step 5 and flash the new boot.img?
Click to expand...
Click to collapse
Looks like incorrect usage of fastboot command, he might have typed fastboot USB?

tpbklake said:
What steps have you done so far? Did you run step 5 and flash the new boot.img?
Click to expand...
Click to collapse
am download vivo_unsecured_boot.zip
and Extract this file into c/android with fastbot and adb and run fastboot c:\Android boot.img
thise is right or not
sory abote my english

rambo 11 said:
am download vivo_unsecured_boot.zip
and Extract this file into c/android with fastbot and adb and run fastboot c:\Android boot.img
thise is right or not
sory abote my english
Click to expand...
Click to collapse
No it's not right. Have another look at the instructions, these commands cannot be "close enough" they must be correct.

Nonverbose said:
Looks like incorrect usage of fastboot command, he might have typed fastboot USB?
Click to expand...
Click to collapse
Spot on as usual! Good call!

Hi.
After done this, I always on the fastboot usb.
Should i see something different or not?
Should i must restart the phone or I can lunch the downgrade toolkit v3.3 runme.cmd ?
Because, if not, i have something wrong, because after lunch the toolkit, i see on the bootloader "RELOCKED"
Thanks

ebouilleur said:
Hi.
After done this, I always on the fastboot usb.
Should i see something different or not?
Should i must restart the phone or I can lunch the downgrade toolkit v3.3 runme.cmd ?
Because, if not, i have something wrong, because after lunch the toolkit, i see on the bootloader "RELOCKED"
Thanks
Click to expand...
Click to collapse
After you run through this procedure, reboot your phone normally and then you can run the Downgrade Toolkit v3.3 runme.cmd. At the end of the downgrade kit, it will relock your bootloader.

And for the toolscript, for the question if i root, must I must say Yes or No?
I'm not but...

ebouilleur said:
And for the toolscript, for the question if i root, must I must say Yes or No?
I'm not but...
Click to expand...
Click to collapse
Answer NO at that prompt.

ebouilleur said:
And for the toolscript, for the question if i root, must I must say Yes or No?
I'm not but...
Click to expand...
Click to collapse
I saw your post on the other thread. Thank you for showing us the results of running the Downgrade Script. From the output the script was successfully able to downgrade your version-main value to 2.00.000.0 and you are now ready to run the RUU mentioned in the Downgrade Script. Once you run that RUU, you will be able to use the Revolutionary tool to get S-OFF.

tpbklake said:
I saw your post on the other thread. Thank you for showing us the results of running the Downgrade Script. From the output the script was successfully able to downgrade your version-main value to 2.00.000.0 and you are now ready to run the RUU mentioned in the Downgrade Script. Once you run that RUU, you will be able to use the Revolutionary tool to get S-OFF.
Click to expand...
Click to collapse
I'm not 100% but I think this user might have originally run the script as rooted after flashing your boot image. Have a look at this thread for a comparison.

Nonverbose said:
I'm not 100% but I think this user might have originally run the script as rooted after flashing your boot image. Have a look at this thread for a comparison.
Click to expand...
Click to collapse
Yeah it is hard to follow his broken English. I answered his question as thought he was asking 'How should I answer the Are You Rooted question'. At any rate when you look at the output of his script, he did answer NO and tacoroot was able to get temproot on the unsecured bootloader, so that was good to see.
I'm beginning to think that your idea of just using the unsecured boot.img as a temp boot (Fastboot boot boot.img) would work on an unlocked bootloader just fine. I just don't think a locked bootloader is going to allow the Fastboot boot boot.img to execute.

tpbklake said:
Yeah it is hard to follow his broken English. I answered his question as thought he was asking 'How should I answer the Are You Rooted question'. At any rate when you look at the output of his script, he did answer NO and tacoroot was able to get temproot on the unsecured bootloader, so that was good to see.
I'm beginning to think that your idea of just using the unsecured boot.img as a temp boot (Fastboot boot boot.img) would work on an unlocked bootloader just fine. I just don't think a locked bootloader is going to allow the Fastboot boot boot.img to execute.
Click to expand...
Click to collapse
Unfortunately you're right about not being able to boot it through fastboot with a locked bootloader. I ran a few tests today and found that simply having the boot.img flashed enables root access, which is obvious now that I think about it.
Code:
E:\fastboot>fastboot flash boot boot_ics.img
sending 'boot' (3822 KB)...
OKAY [ 1.186s]
writing 'boot'...
OKAY [ 1.108s]
finished. total time: 2.293s
E:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.156s
E:\fastboot>adb shell
* daemon not running. starting it now *
* daemon started successfully *
[email protected]droid:/ [b][color=red]$[/color][/b] exit
exit
E:\fastboot>adb reboot bootloader
E:\fastboot>fastboot flash boot boot_unsecured.img
sending 'boot' (3824 KB)...
OKAY [ 1.201s]
writing 'boot'...
OKAY [ 0.920s]
finished. total time: 2.122s
E:\fastboot>fastboot reboot
rebooting...
finished. total time: 0.156s
E:\fastboot>adb shell
[email protected]:/ [b][color=red]#[/color][/b]
So there's no real need to use the temproot script to change the main version or create the goldcard.
I also found that booting through fastboot means theres no ***SECURITY WARNING*** when the bootloader is relocked as it reverts to original kernel upon reboot.
With your permission I would like to use your unsecured boot image to integrate into my script.

[REQ] Tilapia bootloader and radio jb 4.2.2

There is a possibility from someone to have 2 cwm flashable zip file for the new img of bootloader "bootloader-tilapia-4.18.img" and radio "radio-tilapia-1231_0.17.0_1205.img".
I hope yes . Regards

manolohd said:
There is a possibility from someone to have 2 cwm flashable zip file for the new img of bootloader "bootloader-tilapia-4.18.img" and radio "radio-tilapia-1231_0.17.0_1205.img".
I hope yes . Regards
Click to expand...
Click to collapse
radio-tilapia-1231_0.17.0_1205.img
bootloader-tilapia-4.18.img

philos64 said:
radio-tilapia-1231_0.17.0_1205.img
bootloader-tilapia-4.18.img
Click to expand...
Click to collapse
.zip file for a flash with cwm recovery?

manolohd said:
.zip file for a flash with cwm recovery?
Click to expand...
Click to collapse
Not, but you can use my guide for flash to your N7
You don't need ADB, follow the guide and it will be good -
for the bootloader, just rename it bootloader and use this code
Code:
fastboot flash bootloader bootloader.img
and for the radio :
Code:
fastboot flash radio radio.img
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
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
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
-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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

thankyou, another question: now in my nexus i have a custom rom 4.2.2 "unofficial xylon 2.1" if i use fastboot metood to flash new bootlooader and new radio, i can loose my data my recoverymod cwm and my custom rom?
or i must do all with a stock rom and recovery stock?
Ty

manolohd said:
thankyou, another question: now in my nexus i have a custom rom 4.2.2 "unofficial xylon 2.1" if i use fastboot metood to flash new bootlooader and new radio, i can loose my data my recoverymod cwm and my custom rom?
or i must do all with a stock rom and recovery stock?
Ty
Click to expand...
Click to collapse
Go to see and apply my new guide : [GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions

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 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.