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...
Related
Using Fastboot, is there a way to apply the custom ROM zip files?
My goal: Apply a new ROM to the phone, without having to use the phone itself. IE: boot it into recovery, and drop to a shell, then use ADB to wipe/format the proper partitions, and flash the new ROM. If I can't flash the ROM (IE: Intension-v1.3.zip) that way, perhaps via Fastboot...I am not sure if there is a way, but if there is, could someone point me in the right direction?
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
For more fastboot Commands go - Here
I am quite capable of reading the output of the fastboot command. But that talks about update.zip files and such (including in the link you posted)...but, for a file such as Intension-v1.3.zip only contains a boot.img...no data.img, or system.img as the link you posted discusses.
You could rename the Intension-v1.3.zip into update.zip and try 'fastboot flash update update.zip' But I'm not sure though...
BoomBoomPOW said:
You could rename the Intension-v1.3.zip into update.zip and try 'fastboot flash update update.zip' But I'm not sure though...
Click to expand...
Click to collapse
I Have thought of trying that, but afraid that if that is not the correct way to do it, that I might end up bricking my phone.
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
ADB Devices lists no devices in fastboot (XT1072)
Hello, apologies if this has been debated elsewhere, I couldn't see a thread for it.
When I run ADB Devices with my Moto G 2nd Gen (XT1072) phone in normal mode it happily lists the device as being connected. However, when I reboot into bootloader mode, ADB can't see the device any more:
Code:
C:\platform-tools>adb devices
List of devices attached
XXXXXXXXXX device
C:\platform-tools>adb reboot-bootloader
C:\platform-tools>adb devices
List of devices attached
C:\platform-tools>
The phone has USB Debugging enabled and the same thing happens in either MTP or PTP modes. The latest Motorola USB driver is installed, so you can see ADB connects OK when the phone's not in bootloader mode.
Any ideas what I'm doing wrong?
Adb doesn't work in bootloader. Bootloader mode is fastboot mode. So in bootloader mode only fastboot commands work.
notiflux said:
Adb doesn't work in bootloader. Bootloader mode is fastboot mode. So in bootloader mode only fastboot commands work.
Click to expand...
Click to collapse
OK, thanks. However, "fastboot devices" also returns no connected devices when in bootloader mode. I'm running cmd.exe as administrator too by the way, as I've seen that suggested as a potential solution elsewhere.
Probably you only have adb drivers installed, not fastboot drivers
Fastboot is installed, I can list the fastboot helpfile and I've used it before on an old phone from this PC:
Code:
C:\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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 notice that the device is listed in Device Manager on.my PC as "Motorola ADB". Does the standard driver only deal with ADB connections and not Fastboot?
sharkyblunt said:
Fastboot is installed, I can list the fastboot helpfile and I've used it before on an old phone from this PC:
Code:
C:\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
Click to expand...
Click to collapse
download the motorola device manager 2.5.4 exe from motorola website and install , choose repair if already installed. this has ALL the required usb/adb/fastboot drivers or from my link below (it contains MDM2.5.4.exe and adb/fastboot v1.31 in the zip
moto drivers usb /adb /fastboot
Yep, I'm using the Motorola Device Manager driver pack. Unless I'm using the wrong instance of the toolset, as I already had ADB and Fastboot installed by Android SDK from before I owned a Motorola device. Where does the Motorola instance install to by default?
sharkyblunt said:
Yep, I'm using the Motorola Device Manager driver pack. Unless I'm using the wrong instance of the toolset, as I already had ADB and Fastboot installed by Android SDK from before I owned a Motorola device. Where does the Motorola instance install to by default?
Click to expand...
Click to collapse
I own a xt1068 and missus xt1072 I can type mfastboot reboot and phone reboots on both versions guessing you dont have correct fastboot or mfastboot (motorolas version) so find attached a zip to unzip to pc - then put phone in ap fastboot mode and run the test -reset . bat file --- IT WILL NOT RESET YOUR PHONE UNLESS YOU CHOOSE TO -- run it and choose option 4 (reboot) the zip folder includes mfastboot and fastboot and required files to run. please open the test- reset file with notepad++ if you want to see the commands that run
the command to list your device in the bootloader is < fastboot devices > or what ever you fastboot exe is called.
Thanks reefuge, I was unaware that Motorola had their own mfastboot tool. That has solved my issue.
I've installed magisk and gapps on Slot B then i went to Slot A just bootloops?
Go to fastboot and type fastboot set_active b
Reiyn_ said:
Go to fastboot and type fastboot set_active b
Click to expand...
Click to collapse
There's no command?
Reiyn_ said:
Go to fastboot and type fastboot set_active b
Click to expand...
Click to collapse
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
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
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> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
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
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