Database Info

TWRP Recovery Testers Needed

Hi, before I release the exynos version of TWRP Recovery for note 3, I need some testers. Please reply if you're interested.
For those who just want to test, an alpha version can be found here: http://goo.im/devs/bigbiff/ha3g-recovery.img.tar

just downloaded it. will flash and report back.
Sent from my SM-N900 using Tapatalk

bigbiff said:
Hi, before I release the exynos version of TWRP Recovery for note 3, I need some testers. Please reply if you're interested.
For those who just want to test, an alpha version can be found here: http://goo.im/devs/bigbiff/ha3g-recovery.img.tar
Click to expand...
Click to collapse
will you make one for the Verizon Note 3??? thanks for the work.

chefb said:
will you make one for the Verizon Note 3??? thanks for the work.
Click to expand...
Click to collapse
Has the bootloader been unlocked?

No

flashed it. booted to recovery successfully.
first screen asked for a password. (never seen this before while using twrp on note2).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hit the cancel button and got the main page with options to install, backup, etc.
tried to backup my current rom but got an error.
tried to reboot to recovery and worked perfectly. (though got the password page again)
tried reboot (system) and it showed a message that there's no os installed. but reboot system option workrd perfectly.
Sent from my SM-N900 using Tapatalk

numerouknow said:
flashed it. booted to recovery successfully.
first screen asked for a password. (never seen this before while using twrp on note2).
I hit the cancel button and got the main page with options to install, backup, etc.
tried to backup my current rom but got an error.
tried to reboot to recovery and worked perfectly. (though got the password page again)
tried reboot (system) and it showed a message that there's no os installed. but reboot system option workrd perfectly.
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for testing. Is adb working? Can you pull /tmp/recovery.log?

bigbiff said:
Thanks so much for testing. Is adb working? Can you pull /tmp/recovery.log?
Click to expand...
Click to collapse
PFA...

numerouknow said:
PFA...
Click to expand...
Click to collapse
PFA == Please find attached?

numerouknow said:
PFA...
Click to expand...
Click to collapse
sry forgot to attach the log file
https://db.tt/BYIKLpqP
Sent from my SM-N900 using Tapatalk

numerouknow said:
sry forgot to attach the log file
https://db.tt/BYIKLpqP
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Can you post the results of:
Code:
find / -name by-name

bigbiff said:
Can you post the results of:
Code:
find / -name by-name
Click to expand...
Click to collapse
note sure if this is what you wanted. hope i am helping and not complicating things.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ram>cd..
C:\Users>cd..
C:\>adb find / -name by-name
Android Debug Bridge version 1.0.31
-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 <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
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 jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 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 status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
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, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
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:\>

You need to execute adb shell first then execute the find command on the device.

bigbiff said:
You need to execute adb shell first then execute the find command on the device.
Click to expand...
Click to collapse
pls check if i am doing it right this time.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ram>cd..
C:\Users>cd..
C:\>adb shell
~ # ←[6nfind / -name by-name
find / -name by-name
/dev/block/platform/dw_mmc.0/by-name
~ # ←[6n
edit:
in recovery tried advanced -> adb sideload ->swipe to start sideload - and it failed.

numerouknow said:
pls check if i am doing it right this time.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ram>cd..
C:\Users>cd..
C:\>adb shell
~ # ←[6nfind / -name by-name
find / -name by-name
/dev/block/platform/dw_mmc.0/by-name
~ # ←[6n
edit:
in recovery tried advanced -> adb sideload ->swipe to start sideload - and it failed.
Click to expand...
Click to collapse
Thanks, I updated the recovery.img with the path so twrp can find the partitions. I uploaded under the same file name. Let me know if it works.

bigbiff said:
Thanks, I updated the recovery.img with the path so twrp can find the partitions. I uploaded under the same file name. Let me know if it works.
Click to expand...
Click to collapse
downloaded from the op link and flashed it.
rebooted to recovery successfully.
got the password page again.
backup didn't work. got the same error/backup failed message.
tried reboot (system) and again got the same message that no os is installed. but reboot system worked perfectly.
pls download recovery.log here: https://db.tt/BYIKLpqP
Sent from my SM-N900 using Tapatalk

numerouknow said:
downloaded from the op link and flashed it.
rebooted to recovery successfully.
got the password page again.
backup didn't work. got the same error/backup failed message.
tried reboot (system) and again got the same message that no os is installed. but reboot system worked perfectly.
pls download recovery.log here: https://db.tt/BYIKLpqP
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Can you give be the output of ls -l /dev/block/platform/dw_mmc.0/by-name/

bigbiff said:
Can you give be the output of ls -l /dev/block/platform/dw_mmc.0/by-name/
Click to expand...
Click to collapse
sry...i couldnt reply sooner.
output:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ram>cd..
C:\Users>cd..
C:\>adb shell
~ # ←[6nls -l /dev/block/platform/dw_mmc.0/by-name/
ls -l /dev/block/platform/dw_mmc.0/by-name/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2013-10-28 16:18 BOOT -> /dev/block/mmcblk
0p9
lrwxrwxrwx root root 2013-10-28 16:18 BOTA0 -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 2013-10-28 16:18 BOTA1 -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2013-10-28 16:18 CACHE -> /dev/block/mmcbl
k0p19
lrwxrwxrwx root root 2013-10-28 16:18 CARRIER -> /dev/block/mmc
blk0p7
lrwxrwxrwx root root 2013-10-28 16:18 CDMA -> /dev/block/mmcblk
0p12
lrwxrwxrwx root root 2013-10-28 16:18 EFS -> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 2013-10-28 16:18 HIDDEN -> /dev/block/mmcb
lk0p16
lrwxrwxrwx root root 2013-10-28 16:18 OTA -> /dev/block/mmcblk0
p11
lrwxrwxrwx root root 2013-10-28 16:18 PARAM -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 2013-10-28 16:18 PERSDATA -> /dev/block/mm
cblk0p17
lrwxrwxrwx root root 2013-10-28 16:18 RADIO -> /dev/block/mmcbl
k0p13
lrwxrwxrwx root root 2013-10-28 16:18 RECOVERY -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 2013-10-28 16:18 RESERVED2 -> /dev/block/m
mcblk0p18
lrwxrwxrwx root root 2013-10-28 16:18 SYSTEM -> /dev/block/mmcb
lk0p20
lrwxrwxrwx root root 2013-10-28 16:18 TDATA -> /dev/block/mmcbl
k0p15
lrwxrwxrwx root root 2013-10-28 16:18 TOMBSTONES -> /dev/block/
mmcblk0p14
lrwxrwxrwx root root 2013-10-28 16:18 USERDATA -> /dev/block/mm
cblk0p21
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs1 -> /dev/block/mmc
blk0p4
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs2 -> /dev/block/mmc
blk0p5
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs3 -> /dev/block/mmc
blk0p6
~ # ←[6n

numerouknow said:
sry...i couldnt reply sooner.
output:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ram>cd..
C:\Users>cd..
C:\>adb shell
~ # ←[6nls -l /dev/block/platform/dw_mmc.0/by-name/
ls -l /dev/block/platform/dw_mmc.0/by-name/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2013-10-28 16:18 BOOT -> /dev/block/mmcblk
0p9
lrwxrwxrwx root root 2013-10-28 16:18 BOTA0 -> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 2013-10-28 16:18 BOTA1 -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2013-10-28 16:18 CACHE -> /dev/block/mmcbl
k0p19
lrwxrwxrwx root root 2013-10-28 16:18 CARRIER -> /dev/block/mmc
blk0p7
lrwxrwxrwx root root 2013-10-28 16:18 CDMA -> /dev/block/mmcblk
0p12
lrwxrwxrwx root root 2013-10-28 16:18 EFS -> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 2013-10-28 16:18 HIDDEN -> /dev/block/mmcb
lk0p16
lrwxrwxrwx root root 2013-10-28 16:18 OTA -> /dev/block/mmcblk0
p11
lrwxrwxrwx root root 2013-10-28 16:18 PARAM -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 2013-10-28 16:18 PERSDATA -> /dev/block/mm
cblk0p17
lrwxrwxrwx root root 2013-10-28 16:18 RADIO -> /dev/block/mmcbl
k0p13
lrwxrwxrwx root root 2013-10-28 16:18 RECOVERY -> /dev/block/mm
cblk0p10
lrwxrwxrwx root root 2013-10-28 16:18 RESERVED2 -> /dev/block/m
mcblk0p18
lrwxrwxrwx root root 2013-10-28 16:18 SYSTEM -> /dev/block/mmcb
lk0p20
lrwxrwxrwx root root 2013-10-28 16:18 TDATA -> /dev/block/mmcbl
k0p15
lrwxrwxrwx root root 2013-10-28 16:18 TOMBSTONES -> /dev/block/
mmcblk0p14
lrwxrwxrwx root root 2013-10-28 16:18 USERDATA -> /dev/block/mm
cblk0p21
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs1 -> /dev/block/mmc
blk0p4
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs2 -> /dev/block/mmc
blk0p5
lrwxrwxrwx root root 2013-10-28 16:18 m9kefs3 -> /dev/block/mmc
blk0p6
~ # ←[6n
Click to expand...
Click to collapse
That's from TWRP right? This path is what I am using in TWRP.

bigbiff said:
That's from TWRP right? This path is what I am using in TWRP.
Click to expand...
Click to collapse
well what i did was this:
i rebooted my phone into twrp recovery - connected phone to my laptop with usb cable - from laptop's command prompt executed those commands.
ps: i tried adb sideload option thru advanced menu in twrp recovery but it failed.
---------- Post added at 12:24 AM ---------- Previous post was at 12:19 AM ----------
Sent from my SM-N900 using Tapatalk

Marquis MP977 MarquisPad serial disabled

Hi,
Because I could not find a reliable rooting mechanism I soldered a serial FTDI UB232, and I gain shell access.
The serial works ok as long I am in u-boot prompt.
Texas Instruments X-Loader 1.41 (Apr 12 2012 - 12:06:17)
OMAP4460: 1.2 GHz capable SOM
**** DDR SDRAM PATTERN TEST ****
DDR SDRAM DATA BUS TEST..... [PASSED]
DDR SDRAM ADDRESS BUS TEST..... [PASSED]
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4 (Nov 9 2012 - 20:33:58)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
printenv
bootargs=console=ttyO2,115200n8 [email protected] [email protected] init=/init vram=48M omapfb.vram=0:32M androidboot.console=ttyO2
bootcmd=booti mmc1
bootdelay=1
baudrate=115200
ipaddr=128.247.77.90
serverip=128.247.77.158
netmask=255.255.254.0
bootfile="uImage"
ethact=KS8851SNL
Environment size: 285/131068 bytes
As soon android boots when everything is settled down, the tty input is totally ignored, though the shell
prints all the os messages. There is no prompt. ?!?
[ 33.844390] wlan0: moving STA 00:90:a9:a5:51:a1 to state 3
[ 58.387908] omap_cpu_thermal_manager:sensor 66200 avg sensor 59795 pcb 0, delta 18897 hot spot 85097
[ 58.397766] omap_monitor_zone:hot spot temp 85097
[ 58.887908] omap_cpu_thermal_manager:sensor 63800 avg sensor 59795 pcb 0, delta 17742 hot spot 81542
[ 58.897827] omap_safe_zone:hot spot temp 81542
no prompt
Any idea how to outcome and enable the shell tty input.
Here are the pictures of the serial soldering and the serial to usb adapter.
(The pictures are mine, from the stack-over-flow post)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The ftdi

I found and android for OMAP blaze (GB and a kernel from https://e2e.ti.com/support/omap/f/849/t/310839),
After having all cowboys engineering from Texas headaches I finally end up with:
boot.img cache.img fastboot mkbootimg MLO_es2.1_gp MLO_es2.2_emu ramdisk.img ramdisk-recovery.img recovery.img system.img u-boot.bin userdata.img zImage files.
I tried first a non destructive flash, trying to flash the system, (then boot, kernel, recovery / all of them encountering same error)
Linux console:
sudo fastboot flash system system.img
[sudo] password for mpang:
< waiting for device >
sending 'system' (110304 KB)...
OKAY [ 42.127s]
writing 'system'...
FAILED (remote failure)
finished. total time: 42.137s
marquis tablet serial output, as shown in previous post
OMAP44XX TAB # fastboot
I2C read: I/O error
I2C read: I/O error
Device Serial Number: 5C28000200000001
Fastboot entered...
Starting download of 112951340 bytes
................................................................................... many dots
downloading of 112951340 bytes finished
writing to partition 'system'
Wrong Image... Failed to program
How did we get here fastboot.c 993 ?
Anyone ?, Thank you

understanding if fastboot is enabled on mi a3 with broken screen

Hi *,
I hava a xiaomi mi a3 with broken screen, i already rooted and enable debugging previous of the broken.
Now i would use scrcpy but adb listing my device as unhautorized.
I see in other post that i need to copy the key on /android/data/..., but i unable because adb shell does not work, so i read that entering in fastboot mode i able to copy the files without key.
So i powered off the phone and restart with volume up+power and i see this on my syslog
Oct 22 15:32:22 debian-z230 kernel: [ 5541.994136] usb 2-7: new high-speed USB device number 19 using xhci_hcd
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144023] usb 2-7: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice= 4.14
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144038] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144044] usb 2-7: Product: Mi A3
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144048] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:32:23 debian-z230 kernel: [ 5542.144051] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:32:23 debian-z230 gvfsd[14218]: LIBMTP PANIC: Unable to find interface & endpoints of device
Oct 22 15:32:23 debian-z230 gnome-shell[2659]: Unable to mount volume Mi A3: Gio.IOErrorEnum: Unable to open MTP device “002,019”
Oct 22 15:32:24 debian-z230 gvfsd[14218]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
I tryed to run adb but it seems always recognized it as unhautorized, fastboot devices command instead does not report any output:
[email protected]:~$ fastboot devices
[email protected]:~$ fastboot reboot
< waiting for any device >
[email protected]:~$ adb devices
List of devices attached
7044fce4312c unauthorized
if the phone starts in normal mode instead on the syslog i see this
Oct 22 15:44:24 debian-z230 kernel: [ 6263.802797] usb 2-7: new high-speed USB device number 24 using xhci_hcd
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953115] usb 2-7: New USB device found, idVendor=2717, idProduct=ff08, bcdDevice= 4.14
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953121] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953123] usb 2-7: Product: Mi A3
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953125] usb 2-7: Manufacturer: Xiaomi
Oct 22 15:44:24 debian-z230 kernel: [ 6263.953126] usb 2-7: SerialNumber: 7044fce4312c
Oct 22 15:44:24 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:24 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:25 debian-z230 mtp-probe: checking bus 2, device 24: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-7"
Oct 22 15:44:25 debian-z230 mtp-probe: bus: 2, device: 24 was not an MTP device
Oct 22 15:44:55 debian-z230 /usr/libexec/gdm-x-session[2473]: (EE) event2 - Primax HP USB Keyboard: client bug: event processing lagging behind by 13ms, your system is too slow
Oct 22 15:45:01 debian-z230 CRON[14796]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
so seems that product, vendor and device id is different.
Could someone confirm that the first id, of product vendor and device is fastboot device?
There is a method to solve this impasse?
Thanks a lot to all
so the vendor product and device is different

Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.

jwoegerbauer said:
Fastboot gets enabled by default when an Android device boots up, unless manufacturer ( e.g. Samsung ) decided not to support Fastboot. But Xiamomi devices support Fastboot, AFAIK.
FYI: Fastboot isn't a device you can find in /dev/block, it's a software that allows to operate on Android device's bootloader.
Click to expand...
Click to collapse
Hi and thanks for the answers, but I think that Linux discover fastboot device with different product vendor and device id respect normal boot. I would know why fastboot command does not discover my device, I suspect, because my screen on device is broken, that device not start in fastboot mode and I ask to group what kind of product device and vendor I'd you seen for your xiaomi mi a3 device under syslog or lsusb in fastboot mode.

Yes
Code:
sudo ./fastboot devices
returns
Code:
<SERIAL_ID> fastboot
but that's NOT AN ANDROID DEVICE, IT'S THE DEVICE'S BOOTLOADER connected to, and nothing else.
If the output is shown as above listed, then Fastboot-mode is enabled/activated and working.

[DEV] "Empty" userdata-Partition of AVD/Genymotion Emulator

Hey,
i want to analyse the partitions of my Android Emulator using Autopsy for a prototype i am developing. I started with the userdata partition. However, it seems like that the partition does not contain any data, even though i produced some data (installed apps, phone calls, messages, browsing, etc). It is basically "empty" besides the default stuff that was already there before producing data (see the picture at the bottom). I dont really understand why this is the case. I also tried to reboot the emulator as i thought that the data i produced might be cached somewhere and is written to the userdata partition during shutdown (i checked if the generated data is still there after the reboot). Still, the size of the partition did not change. Other images (not created by me), which i analysed using autopsy during my digital forensic class, contained way more data in der userdata partition and were also produced using an emulator. Besides the AVD Emulator i tried the Genymotion Emulator. Nothing changed except the mapping.
This is what i did to extract the userdata:
1. Launched the emulator (latest API Level) and generated some data
2. Checked the connection via ADB (adb devices)
3. Become and verify root (adb root; whoami; id)
4. List the partition mapping (adb shell; ls -l /dev/block/mapper/)
emulator64_x86_64_arm64:/ # ls -l /dev/block/mapper/
total 0
drwxr-xr-x 2 root root 160 2022-03-26 11:09 by-uuid
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 product -> /dev/block/dm-2
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system -> /dev/block/dm-0
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system-verity -> /dev/block/dm-4
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 system_ext -> /dev/block/dm-1
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 userdata -> /dev/block/dm-5
lrwxrwxrwx 1 root root 15 2022-03-26 11:09 vendor -> /dev/block/dm-3
5. Extracted the partition (adb pull /dev/block/dm-5 /DESTINATION_PATH)
6. Renamed the file to .img and created a new autopsy case
I expected the image to atleast contain data within the /app and /data folder.
Also: I would like to know if there is a possibility to extract the whole file system using the ADB only.
Thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[adb] What is the adb syntax to connect wirelessly to Android by unique serial number (instead of by Wi-Fi LAN IP address & random port assignment)?

[adb] What is the adb syntax to connect wirelessly to an Android phone by its unique serial number
(instead of by its static Wi-Fi LAN IP address & random port assignment)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background: (USB is no longer needed)
1. Android 11 (and up) allows adb to connect wirelessly (no USB)
2. Android 12 (and up) adds a TILE to make it very easy to set up
3. The latest ADB adds "adb pair" to the "adb connect" commands
The syntax for those wireless adb commands is easy when you know the IP address & random port assignment:
SYNTAX: adb pair [STATIC-IP]:[RANDOM-PORT] [RANDOM-PIN]
EXAMPLE: C:\> adb pair 192.168.0.2:40089 572791
RESULT:
Successfully paired to 192.168.0.2:40089 [guid=adb-YFVR80V7YFY-yF7kj8]
SYNTAX: adb connect [STATIC-IP]:[RANDOM-PORT]
EXAMPLE: C:\> adb connect 192.168.0.2:34967
RESULT:
connected to 192.168.0.2:34967
A. After you connect the PC to Android via adb you can query it
B. That query often shows TWO connections
C. One is via the IP : PORT and the other is via a SERIAL NUMBER
SYNTAX: adb devices
EXAMPLE: C:\> adb devices
RESULT:
List of devices attached
192.168.0.2:34967 device
adb-YFVR80V7YFY-yF7kj8._adb-tls-connect._tcp. device
The help for adb says to use the "-s" option to specify the serial number.
C:\> adb --help | findstr "serial"
RESULT:
-s SERIAL use device with given serial (overrides $ANDROID_SERIAL)
get-serialno print <serial-number>
$ANDROID_SERIAL serial number to connect to (see -s)
The problem I'm having is I can't figure out the syntax to connect via that serial!
Assuming the outputs above, this does not work for me.
C:\> adb shell "ifconfig|grep -A 1 wlan0|tail -n 1|cut -f2 -d:|cut -f1 -d' '"
RESULT:
adb.exe: more than one device/emulator
C:\> adb -s 192.168.0.2:34967 shell "ifconfig|grep -A 1 wlan0|tail -n 1|cut -f2 -d:|cut -f1 -d' '"
RESULT:
192.168.0.2
That works fine if you already know the IP address (and port, which is more important but not for this trivial example); but what if you don't know the IP address or random port?
What if you only know the unique Android device serial number?
C:\> adb -s adb-YFVR80V7YFY-yF7kj8 shell "ifconfig|grep -A 1 wlan0|tail -n 1|cut -f2 -d:|cut -f1 -d' '"
RESULT:
adb.exe: device 'adb-YFVR80V7YFY-yF7kj8' not found
What am I doing wrong (syntactically speaking) to query any given Android device (over Wi-Fi) by its unique serial number?

By accident, while I was testing out the ladb app open source app (aka "local adb"), I realized in the PC command-line queries that sometimes adb says the Android device serial number is of (what I'll call the "long form") and sometimes the serial number output is of (what I'll call the "short form")...
Long form serial number:
"adb-YFVR80V7YFY-yF7kj8._adb_tls-connect._tcp."
Short form serial number:
"YFVR80V7YFY"
That syntactical difference may play a role in the syntax required of adb '-s' commands.
For example, does anyone know what all that other "stuff" is that's prepended and mostly what is appended to (what I'll call the) "short form" serial number?