I know this is 100% my fault but I was hoping that maybe the genius of XDA could help me out here.
1. Was using phone fine earlier.
2. Flashed Cyanogen 5.0.2
3. Flashed the newest radio version that Cyanogen linked in that thread
4. Didn't test
5. Started playing with 'fastboot oem' commands
6. Gave up tried to send a text message
7. No keybaord
8. Long press -> Input type -> nothing listed
9. Settings -> Keyboard and locale -> nothing about the keyboard.
10. Reflashed latest Cyanogen image
11. Still not working
I think during my fun of fastboot commands I screwed something up. The phone works perfect except I don't have a keyboard, the keypad in the dialer still works. Apparently somewhere along the line I lost my nandroid backup (yes, I know fail on me) I am currently looking for a keyboard app on the web that has a QR code so that I can install a 3rd party one from market. Will let you know how that goes.
Code:
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot flash radio
Radio_20100203_2_Signed_PASSION.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem -?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem secu
rity
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem s=of
f
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
... INFOtask: Parameter error
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
help
... INFOtask -1911570672 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
50
... INFOtask 80 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rtas
k 32
... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
... INFOstart keypad testing ...
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>a
'a' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot oem ?
... ^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rebo
ot
... FAILED (command write failed (Unknown error))
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
???????????? fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFOtask 8 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p passi
on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 1
getvar:1 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 2
getvar:2 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 3
2
getvar:32 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe
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
-b <base_addr> specify a custom kernel base address
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurity
security: on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurit
getvar:securit FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe flash hb
oot hboot-0.33.2012.img
sending 'hboot' (768 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>
Here are all of the commands that I have run since I last closed the CMD window.
Update: I have found the HTC Touch input APK and installed that on my phone. I can now long press input type and select touch input but whenever the keyboard should be coming up I get a force close. I know that on my G1 the HTC Touch input was iffy at best so I am still looking for another solution.
Another update: Got 'Better Keyboard' it works! (yay!) but when I goto click on the voice input it does not. I checked my search widget and the microphone icon is missing from there as well.
Someone posted their nandroid backup of a completely (rooted) stock n1 rom, search around for it and try installing it. I ran accross it while looking for tutorials on how to flash the stock N1 rom if that helps
Update: NOOOO!!!!!!! I did a full wipe from the bootloader (factory restore, dalvik-cache, rotate settings, and what ever that 4th one was and reinstalled cyanogen mod 5.0.2) bad news: all of my settings and applications are gone, as well as my customer ringtones. Very very sad day.
Oh yea, fixed the keyboard issue and the voice input issue. So I guess we can count this as win
Should have backed up your apps with astro or titanium
Oh I had a titanium backup, I just had to reinstall them all, and reset their locations on the home screens, and reset all of my ringtones and notification tones a process that takes a whole 5 - 10 min.
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
just found out my legend keeps creating files on my SD card called: qxdm_20101213_163620_1.dm
mertins said:
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
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
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
Click to expand...
Click to collapse
Happens sometimes when u try to flash a rom on your device.
Your phone has bricked, u now need to learn how to unbrick it.
Search the forums for how to unbrick, im sure u gonna be able to find a solution.
peace
ps don't worry its solvable
Thanks, now at least i know what is wrong
tried to follow the howto USB Unbrink-thread (mentioned it in first post) and as i said i cant even get past "step one"
I'll keep searching
mertins said:
C:\androidSDK\tools>fastboot eom enableqxdm 0
Click to expand...
Click to collapse
Right command: fastboot oem enableqxdm 0
posted at another forum and found that out
feel kinda dumb now, been trying to execute that command for three days :/
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
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.
default: 0x10000000
-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
any suggestions??
You have to be using the latest version of fastboot, so you should update your sdk
GCbard said:
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
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.
default: 0x10000000
-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
any suggestions??
Click to expand...
Click to collapse
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.
chichu_9 said:
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.
Click to expand...
Click to collapse
got it. works! Thanks!!
When I flash my 2017u back to stock 6.0 then update to 7.1.1 this screen on bootup is still present. I also cannot seem to get fastboot to work to lock the bootloader either.
Any help appreciated
Excuse the pic quality it's taken with my backup i9505 s4
Try to go into fastboot using "adb reboot bootloader" or using the volume keys to go into fastboot. After that you should be able to use "adb oem lock" to lock the bootloader and you will no longer see that message when you boot.
Thanks. Will give a try again on the weekend when I Qualcomm firehose it back to stock again. Cheers
vanish0104 said:
Try to go into fastboot using "adb reboot bootloader" or using the volume keys to go into fastboot. After that you should be able to use "adb oem lock" to lock the bootloader and you will no longer see that message when you boot.
Click to expand...
Click to collapse
Hi, I managed to have a play with the phone using the edl tool, the axon7 toolkit and even adb 15 second installer. No command i have tried on B29 MM will lock the bootloader.
The 5 second screen is still there on boot and shows unlocked. I went upto N B15 and the OEM is greyed out but still a 5 second screen. So reverted back to MM B29 for now and hope someone can help me.
Edit - I've tried flashing stock images with axon 7 edl tool and some success in flashing stock but it still leaves me with the 5second screen I've tried now to inject twrp in a stock image to then hopefully flash the remove 5 second screen g and u zip but I get stuck with an encrypted drive and needing to enter a password thus unable to put the zip on the phone to flash with twrp 3.2.3.0
Everything i do i just end up with Failed Command
be1a5d19 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\adb>fastboot devices
C:\adb>adb devices
List of devices attached
be1a5d19 device
C:\adb>adb reboot bootloader
C:\adb>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\adb>fastboot flash lock_critical
unknown partition 'lock_critical'
error: cannot determine image filename for 'lock_critical'
C:\adb>fastboot flashing lock critical
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
C:\adb>adb reboot bootloader
C:\adb>adb oem lock
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fail
s
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from dev
ice
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsdg] <file>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-g: grant all runtime permissions)
adb install-multiple [-lrtsdpg] <file...>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
(-g: grant all runtime permissions)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb disable-verity - disable dm-verity checking on USERDEBUG builds
adb enable-verity - re-enable dm-verity checking on USERDEBUG build
s
adb keygen <file> - generate adb public/private key. The private ke
y is stored in <file>,
and the public key is stored in <file>.pub. Any
existing files
are overwritten.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb remount - remounts the /system, /vendor (if present) and
/oem (if present) partitions on the device read-write
adb reboot [bootloader|recovery]
- reboots the device, optionally into the bootloa
der or recovery program.
adb reboot sideload - reboots the device into the sideload mode in re
covery program (adb root required).
adb reboot sideload-auto-reboot
- reboots into the sideload mode, then reboots au
tomatically after the sideload regardless of the result.
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb unroot - restarts the adbd daemon without root permissio
ns
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, /system, /vendor (if present), /oem (if pre
sent) and /data partitions will be updated.
- If it is "system", "vendor", "oem" or "data", only the corresponding partiti
on
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\adb>
As you can see i tried several commands to lock.
cheers
Jcth1 said:
Hi, I managed to have a play with the phone using the edl tool, the axon7 toolkit and even adb 15 second installer. No command i have tried on B29 MM will lock the bootloader.
The 5 second screen is still there on boot and shows unlocked. I went upto N B15 and the OEM is greyed out but still a 5 second screen. So reverted back to MM B29 for now and hope someone can help me.
Edit - I've tried flashing stock images with axon 7 edl tool and some success in flashing stock but it still leaves me with the 5second screen I've tried now to inject twrp in a stock image to then hopefully flash the remove 5 second screen g and u zip but I get stuck with an encrypted drive and needing to enter a password thus unable to put the zip on the phone to flash with twrp 3.2.3.0
Everything i do i just end up with Failed Command
be1a5d19 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\adb>fastboot devices
C:\adb>adb devices
List of devices attached
be1a5d19 device
C:\adb>adb reboot bootloader
C:\adb>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\adb>fastboot flash lock_critical
unknown partition 'lock_critical'
error: cannot determine image filename for 'lock_critical'
C:\adb>fastboot flashing lock critical
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
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 bootlo
ader
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
C:\adb>adb reboot bootloader
C:\adb>adb oem lock
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
-a - directs adb to listen on all interfaces for a c
onnection
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fail
s
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from dev
ice
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsdg] <file>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-g: grant all runtime permissions)
adb install-multiple [-lrtsdpg] <file...>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
(-g: grant all runtime permissions)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
[-system|-nosystem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb disable-verity - disable dm-verity checking on USERDEBUG builds
adb enable-verity - re-enable dm-verity checking on USERDEBUG build
s
adb keygen <file> - generate adb public/private key. The private ke
y is stored in <file>,
and the public key is stored in <file>.pub. Any
existing files
are overwritten.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb get-devpath - prints: <device-path>
adb remount - remounts the /system, /vendor (if present) and
/oem (if present) partitions on the device read-write
adb reboot [bootloader|recovery]
- reboots the device, optionally into the bootloa
der or recovery program.
adb reboot sideload - reboots the device into the sideload mode in re
covery program (adb root required).
adb reboot sideload-auto-reboot
- reboots into the sideload mode, then reboots au
tomatically after the sideload regardless of the result.
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb unroot - restarts the adbd daemon without root permissio
ns
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, /system, /vendor (if present), /oem (if pre
sent) and /data partitions will be updated.
- If it is "system", "vendor", "oem" or "data", only the corresponding partiti
on
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\adb>
As you can see i tried several commands to lock.
cheers
Click to expand...
Click to collapse
because you didn't allow oem unlocking?
OEM unlocking allowed. I'm now back on Los 16 for the time being. OEM unlocking before greyer out saying my bootloader is already unlocked. It just will not lock and edl will not lock it either
There is a method by @raystef66 where u can "hide" this notification.
Spillunke said:
There is a method by @raystef66 where u can "hide" this notification.
Click to expand...
Click to collapse
Yea I'm not that desperate to hide it no more. I flashed stock android 8 and couldn't get it to stop encrypting the data partition with twrp so I gave up. I'm back on Los 16 with a new battery and that will do.
I'm not going to buy a razer phone 2 this year so this axon will have to do. Just got to order a new speaker as my bottom loud speaker just doesn't work. The plastic cover and the springs arms are intact just nothing coming from it.
Cheers for the replies guys. Was thinking of trading the phone in at CEX here in the UK and then move to my dual Sim Samsung s7. But since the Axon defeated me I'll keep it for now and maybe get shot of the Samsung instead.
Jcth1 said:
When I flash my 2017u back to stock 6.0 then update to 7.1.1 this screen on bootup is still present. I also cannot seem to get fastboot to work to lock the bootloader either.
Any help appreciated
Excuse the pic quality it's taken with my backup i9505 s4
Click to expand...
Click to collapse
you need to flash original stock rom for your device trough edl. (rom your device came from factory,marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Predatorhaze said:
you need to flash original stock rom for your device trough edl. (rom your device came from factory,marshmallow)
then boot into system,unlock developer options.Allow oem unlock and turn on usb debugging.Now connect phone to laptop and check the dialogue on your phone that ask for usb debug.Unplug phone.
When you did this you want to flash TWRP trough EDL.
Now boot in TWRP and flash UnlockbootloaderPackage from DrakenFX.
Reboot system.
Now turn off your device and boot into fastboot,connect your phone with laptop and open ADB terminal on your laptop or use Axon7toolkit.
In terminal enter fastboot oem lock,or in axon7toolkit choose lock bootloader.
Your bootloader is now locked.
PS: you dont need locked bootloader to recieve ota's,and make sure you are on the firmware your device came shipped with!!
You need a locked bootloader to get rid of the warning message ( dont flash any mod package that claims it delete the warning page)
Click to expand...
Click to collapse
Cheers. I however am not the phones original owner. So should I just go with the edl image for b29 marshmallow?
Jcth1 said:
Cheers. I however am not the phones original owner. So should I just go with the edl image for b29 marshmallow?
Click to expand...
Click to collapse
yes,take a early marshmallow build ( not the latest marshmallow build ).
I think u should take B25,follow my guide for lock bootloader and then update the rom trough OTA
Predatorhaze said:
yes,take a early marshmallow build ( not the latest marshmallow build ).
I think u should take B25,follow my guide for lock bootloader and then update the rom trough OTA
Click to expand...
Click to collapse
Any links to an earlier one would be appreciated. I downloaded djkuz b29 but that's his earliest it seems
Jcth1 said:
Any links to an earlier one would be appreciated. I downloaded djkuz b29 but that's his earliest it seems
Click to expand...
Click to collapse
i looked for you but cant find any b25....Then you can go ahead and use B29 marshmallow full edl
New problem...I have managed to flash b29 mm and lock the bootloader finally however 1, I have no SIM or WiFi working on setup screen so cannot set in motion otas. 2, I edl flash b15 N or B32 N or B20 O and none of them stuck. I just end up back at B29 MM Setup screen with a 02 Mac and no detected wifi
Jcth1 said:
New problem...I have managed to flash b29 mm and lock the bootloader finally however 1, I have no SIM or WiFi working on setup screen so cannot set in motion otas. 2, I edl flash b15 N or B32 N or B20 O and none of them stuck. I just end up back at B29 MM Setup screen with a 02 Mac and no detected wifi
Click to expand...
Click to collapse
Did you try factory reset?
Predatorhaze said:
Did you try factory reset?
Click to expand...
Click to collapse
Yes I did
Jcth1 said:
Yes I did
Click to expand...
Click to collapse
You can edl flash nougat stock ROM,or try edl flash b29mm ROM again,then boot in stock recovery( do not boot system) and do factory reset,turn off phone,boot phone.
I don't had these problems
Predatorhaze said:
You can edl flash nougat stock ROM,or try edl flash b29mm ROM again,then boot in stock recovery( do not boot system) and do factory reset,turn off phone,boot phone.
I don't had these problems
Click to expand...
Click to collapse
Ok the recovery says that it's on 6.0.1 and nothing changes ever. Tried flashing b15 N and nope still recovery says 6.0.1.
I tried updating via ADB and sdcard. Neither works. Two different updates also that I downloaded.
I did the factory reset, still same problem. No service on SIM and WiFi Mac is still 02:00:00 etc.
Just spent an hour on my driving break in my truck and nothing had worked.
Jcth1 said:
Ok the recovery says that it's on 6.0.1 and nothing changes ever. Tried flashing b15 N and nope still recovery says 6.0.1.
I tried updating via ADB and sdcard. Neither works. Two different updates also that I downloaded.
I did the factory reset, still same problem. No service on SIM and WiFi Mac is still 02:00:00 etc.
Just spent an hour on my driving break in my truck and nothing had worked.
Click to expand...
Click to collapse
Do you use Miflash for flash EDL firmware?
Predatorhaze said:
Do you use Miflash for flash EDL firmware?
Click to expand...
Click to collapse
No I used axon 7 edl tool.
So today I tried and tried and gave up flashing b15 N. I had a go with b32 N instead. However after flashing I didn't select yes on the edl tool to reboot instead going for a cable unplug and forced reboot holding the power button. I tried to boot into recovery which yielded a double flash of the red led and then nothing else. Blank screen and no led. I tried rebooting again to recovery and voila. 7.1.1 recovery loaded.
Not taking a chance I factory resetted and now have a fully stock axon 7 with a locked bootloader.
Many thanks to those who helped me but I'm going to part with this phone and return to a Nexus 6p that needs a new battery and a dual SIM exynos s7 for my axon 7 lineage os replacement.