Problem while building ipset binary to android - Android Q&A, Help & Troubleshooting

Hello,
I am losing my mind while building ipset binary to android, i am worked on it at least two hours, i have successfully builded kernel module for ipset, it is working fine but i cannot run ipset binary on my device. (nexus 5)
Code:
PKG_CONFIG_PATH=/storage/android/lib/pkgconfig CC=/storage/arm-linux-gnueabi-linaro_4.9.1-2014.06/bin/arm-eabi-cc ./configure --with-kmod=no --enable-shared=no --host=arm-linux-gnueabi --prefix=/storage/android
With this configuration command, ipset builds fine, but when i push it to /system/bin/ipset, i can not execute it from here.
Code:
/system/bin # ./ipset
/sbin/sh: ./ipset: not found
readelf -hd ipset output
Code:
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: ARM
Version: 0x1
Entry point address: 0x92a1
Start of program headers: 52 (bytes into file)
Start of section headers: 365580 (bytes into file)
Flags: 0x5000202, has entry point, Version5 EABI, soft-float ABI
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 8
Size of section headers: 40 (bytes)
Number of section headers: 38
Section header string table index: 35
Dynamic section at offset 0x171e0 contains 25 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libdl.so.2]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000000c (INIT) 0x8b98
0x0000000d (FINI) 0x1038c
0x00000019 (INIT_ARRAY) 0x271d4
0x0000001b (INIT_ARRAYSZ) 4 (bytes)
0x0000001a (FINI_ARRAY) 0x271d8
0x0000001c (FINI_ARRAYSZ) 4 (bytes)
0x00000004 (HASH) 0x818c
0x00000005 (STRTAB) 0x86ec
0x00000006 (SYMTAB) 0x831c
0x0000000a (STRSZ) 576 (bytes)
0x0000000b (SYMENT) 16 (bytes)
0x00000015 (DEBUG) 0x0
0x00000003 (PLTGOT) 0x272d0
0x00000002 (PLTRELSZ) 440 (bytes)
0x00000014 (PLTREL) REL
0x00000017 (JMPREL) 0x89e0
0x00000011 (REL) 0x89c8
0x00000012 (RELSZ) 24 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x6ffffffe (VERNEED) 0x89a8
0x6fffffff (VERNEEDNUM) 1
0x6ffffff0 (VERSYM) 0x892c
0x00000000 (NULL) 0x0
readelf -hd iptables output (the one that comes with android, works fine)
Code:
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: ARM
Version: 0x1
Entry point address: 0x5348
Start of program headers: 52 (bytes into file)
Start of section headers: 223636 (bytes into file)
Flags: 0x5000000, Version5 EABI
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 8
Size of section headers: 40 (bytes)
Number of section headers: 27
Section header string table index: 26
Dynamic section at offset 0x32cec contains 26 entries:
Tag Type Name/Value
0x00000003 (PLTGOT) 0x33e44
0x00000002 (PLTRELSZ) 864 (bytes)
0x00000017 (JMPREL) 0x4a00
0x00000014 (PLTREL) REL
0x00000011 (REL) 0x1080
0x00000012 (RELSZ) 14720 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x6ffffffa (RELCOUNT) 1835
0x00000015 (DEBUG) 0x0
0x00000006 (SYMTAB) 0x148
0x0000000b (SYMENT) 16 (bytes)
0x00000005 (STRTAB) 0x8c8
0x0000000a (STRSZ) 1098 (bytes)
0x00000004 (HASH) 0xd14
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000020 (PREINIT_ARRAY) 0x33c6c
0x00000021 (PREINIT_ARRAYSZ) 0x8
0x00000019 (INIT_ARRAY) 0x33c74
0x0000001b (INIT_ARRAYSZ) 8 (bytes)
0x0000001a (FINI_ARRAY) 0x33c7c
0x0000001c (FINI_ARRAYSZ) 8 (bytes)
0x0000001e (FLAGS) BIND_NOW
0x6ffffffb (FLAGS_1) Flags: NOW
0x00000000 (NULL) 0x0
I think the problem is libraries, i also pushed the libc.so.6 and libdl to /system/lib with no success.
Could someone point out where i am doing the mistake?
Thanks.

Related

[A] Shared Libs elf text for stock shooter (Evo 3D)

Ok so this was something that I needed for Porting MIUI to the EVO 3D
the command in Linux is readelf -d liba2dp.so
Example of output
File: liba2dp.so
Dynamic section at offset 0xe048 contains 27 entries:
Tag Type Name/Value
0x00000003 (PLTGOT) 0xe12c
0x00000002 (PLTRELSZ) 320 (bytes)
0x00000017 (JMPREL) 0xcf4
0x00000014 (PLTREL) REL
0x00000011 (REL) 0xe34
0x00000012 (RELSZ) 16 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x6ffffffa (RELCOUNT) 16
0x00000006 (SYMTAB) 0x34c
0x0000000b (SYMENT) 16 (bytes)
0x00000005 (STRTAB) 0x85c
0x0000000a (STRSZ) 1175 (bytes)
0x00000004 (HASH) 0xf4
0x00000001 (NEEDED) Shared library: [liblog.so]
0x00000001 (NEEDED) Shared library: [libcutils.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x0000000e (SONAME) Library soname: [liba2dp.so]
0x00000019 (INIT_ARRAY) 0xe000
0x0000001b (INIT_ARRAYSZ) 8 (bytes)
0x0000001a (FINI_ARRAY) 0xe008
0x0000001c (FINI_ARRAYSZ) 12 (bytes)
0x00000016 (TEXTREL) 0x0
0x00000010 (SYMBOLIC) 0x0
0x0000001e (FLAGS) SYMBOLIC TEXTREL
0x00000000 (NULL) 0x0
I have included all of the readelf in a text below
Hope this helps some of you!
Ok thats great! thank

[Q] help with ndk build

hello guys,
I need to use a native library in my app but with all the ways I've tryed to build it, I get the following warning:
Code:
10-11 10:33:51.095: WARN/dalvikvm(337): No implementation found for native L[I](path to my activity)[/I];.Init (Ljava/lang/String;IIIII)I
and then the error
Code:
10-11 10:33:51.115: ERROR/AndroidRuntime(337): java.lang.UnsatisfiedLinkError: Init
I have downloaded the library and I'm not familiar with c++ to modify or debug it if that is the case but I believe that my error comes from the Android.mk file which was like this when downloaded:
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_MODULE := gifflen
LOCAL_SRC_FILES := gifflen.cpp
LOCAL_LDLIBS := -L/cygdrive/c/android-ndk-1.5_r1-windows/android-ndk-1.5_r1/build/platforms/android-1.5/arch-arm/usr/lib -llog
include $(BUILD_SHARED_LIBRARY)
but because i use linux and ndk-r6b, i've modyfied it like:
Code:
LOCAL_LDLIBS += -L/home/me/android-ndk-r6b/platforms/android-3/arch-arm/usr/include/android/ -llog
This may be useful too:
Code:
$ readelf -d libgifflen.so
Dynamic section at offset 0x53ac contains 26 entries:
Tag Type Name/Value
[B]0x00000001 (NEEDED) Shared library: [liblog.so][/B]
0x00000001 (NEEDED) Shared library: [libstdc++.so]
0x00000001 (NEEDED) Shared library: [libm.so]
0x00000001 (NEEDED) Shared library: [libc.so]
0x00000001 (NEEDED) Shared library: [libdl.so]
0x0000000e (SONAME) Library soname: [libgifflen.so]
0x00000010 (SYMBOLIC) 0x0
0x00000019 (INIT_ARRAY) 0x6394
0x0000001b (INIT_ARRAYSZ) 12 (bytes)
0x0000001a (FINI_ARRAY) 0x63a0
0x0000001c (FINI_ARRAYSZ) 12 (bytes)
0x00000004 (HASH) 0xd4
0x00000005 (STRTAB) 0xf54
0x00000006 (SYMTAB) 0x564
0x0000000a (STRSZ) 2464 (bytes)
0x0000000b (SYMENT) 16 (bytes)
0x00000003 (PLTGOT) 0x649c
0x00000002 (PLTRELSZ) 176 (bytes)
0x00000014 (PLTREL) REL
0x00000017 (JMPREL) 0x19e4
0x00000011 (REL) 0x18f4
0x00000012 (RELSZ) 240 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x00000016 (TEXTREL) 0x0
0x6ffffffa (RELCOUNT) 28
0x00000000 (NULL) 0x0
Any help would be greatly appreciated and I thank you for your time in advance,
cheers!
Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Need help in changing FS type for int. and ext. SD on MTK6589

Hello, all!
Trying to customize my new device (Runbo X6: MTK6589T, 2GB RAM, 32GB ROM, Android 4.2.1) I discovered some problems and hope for some help her.
1) Repartitioning
Actually, I successfully edited the partition table in EBR1 and EBR2 and the start addresses in the Scatter file and proofed it multipple times by recalculating, but after flashing, although I get a correct output in system settings and by dumping /proc/emmc, /proc/partitions and /proc/dumchar_info, when I try to push some apps, for ex., above the initial 680MB to /system/app or something similar I get a "disk is full" message. As I was able to find out only the /data and /fat partitions get physically updated by the new sizes, meanwhile the /system and /cache partitions remain physically on the initial state and get updated by the new sizes logical only. Although if after flashing I dump the system image by "cat /dev/block/mmcblk0p5 > /sdcard/system.img" I get an image with a size corresponding to the updated size of the partition.
Initial values:
EBR1
begin /system = 00 18 02 00 (real 00 02 18 00)= 137216 blocks (* 512 bytes + 1024 blocks of 512 bytes) = 70778880 bytes
size /system = 00 50 14 00 (real 00 14 50 00) = 1331200 blocks (* 512 bytes) = 681574400 bytes
begin /cache = 00 68 16 00 = 1468416 blocks = 752353280 bytes
size /cache = 00 F0 03 00 = 258048 blocks = 132120576 bytes
begin /data = 00 58 1A 00 = 1726464 blocks = 884473856 bytes
size /data = 00 00 40 00 = 4194304 blocks = 2147483648 bytes
EBR2
begin /fat = 00 94 58 00 = 5805056 blocks = 2972712960 bytes
size /fat = FF A7 A5 FF = 4289046527 blocks = 2195991821824 bytes
Scatter
ANDROID = 0x4980000 = 77070336 bytes (- 12 * 1024 blocks of 512 bytes; I don't know why even 12, perhaps you can explain...) = 70778880 bytes
CACHE = 0x2d380000 = 758644736 bytes = 752353280 bytes
USRDATA = 0x35180000 = 890765312 bytes = 884473856 bytes
__NODL_FAT = 0xb5180000 = 3038248960 bytes = 3031957504 bytes
My values:
EBR1
begin /system = 00 18 02 00 (real 00 02 18 00)= 137216 blocks = 70778880 bytes
size /system = 00 40 51 00 (real 00 40 51 00) = 5324800 blocks = 2726297600 bytes
begin /cache = 00 58 53 00 = 5462016 blocks = 2797076480 bytes
size /cache = 00 D0 0B 00 = 774144 blocks = 396361728 bytes
begin /data = 00 28 5F 00 = 6236160 blocks = 3193438208 bytes
size /data = 00 00 A0 00 = 10485760 blocks = 5368709120 bytes
EBR2
begin /fat = 00 64 FD 00 = 16606208 blocks = 8502902784 bytes
size /fat = FF 00 D7 FF = 4278245375 blocks = 2190461632000 bytes
Scatter
ANDROID = 0x4980000 = 77070336 bytes = 70778880 bytes
CACHE = 0xa7180000 = 2803367936 bytes = 2797076480 bytes
USRDATA = 0xbeb80000 = 3199729664 bytes = 3193438208 bytes
__NODL_FAT = 0x1feb80000 = 8568438784 bytes = 8502902784 bytes
cat /proc/emmc output
android start = 00 02 00 1c , android size = 00 51 40 00
cache start = 00 53 5c 00 , cache size = 00 00 0b d0
data start = 00 00 5f 2c , data size = 00 a0 00 00
fat start = 00 00 ff 2c , fat size 02 00 a4 2c
cat /proc/partitions output
android start = 2662400 blocks
cache start = 387072 blocks
data start = 5242880 blocks
fat start = 22156800 blocks
cat /proc/dumchar_info output
android start = 04 38 00 00 , android size = a2 80 00 00
cache start = a6 b8 00 00 , cache size = 17 a0 00 00
data start = be 58 00 00 , data size = 01 40 00 00 00
fat start = 01 58 00 00 fe , fat size = 05 48 58 00 00
I also read somewhere that it is also necessary to edit PMT: in that case I tried to flash with original PMT, edited PMT and without PMT, but cuoldn't notice any difference.
2) Mounting the internal memory and external SDcard on system start natively as EXT4 instead of FAT32
Using my old device (Runbo X5: MTK6577) I had success on mounting the internal storage as EXT4 by disassembling recovery.img and editing /etc/recovery.fstab to change the "vfat" value to "ext4" and reformatting the storage after a successful boot with ne recovery, but on Runbo X6 I get no change to the filesystem after reformatting. By the external SDcard I never had success.
Thouthand thanks for any help and advices what I'm doing wrong.
Nobody having a suggestion???
Maybe this one...
Hello, I just got my X6, and didn't have much time to play with it - plus I don't have your block/partition knowledge :s
So far I found this page http://4pda.ru/forum/index.php?showtopic=520192
there's a rooted rom on it (installed it trough the default recovery) - it works well.
There's also a custom recovery and some tools to install it, but running linux, I was blocked for that part.
Unfortunately, I havn't been able to boot the phone on fastboot to push it (it seems like there's no fastboot on the phone).
have you been able to get the NFC working?
Hi!
Thank you for the reply!
According to the manufacturer the NFC feature is still not working.
I tried VVL's custom on my old Runbo X5 and it had a lot of bugs... Also I don't think that he has realized the feature with different FS on SD mounting...
Besides that I have now my own custom based on the stock firmware I got with the device and its working perfect. By the way if you need a fully working CWM its provided by latest "MTK Droid and Tools".

Get bootlogo not found

Hello guys,
i have an allview viva C701 tablet and tried to change the bootlogo image but i didn't manage to extract it.
Using adb and the following command dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1 i get the following error "no such file or directory". examining forward i saw that if i try "#cat /proc/mtd" is returning the same error, after some researching i managed to get the partition table with "cat /proc/partitions" and the result is like this :
major minor #blocks name
253 0 131072 zram0
93 0 32768 nanda
93 8 16384 nandb
93 16 16384 nandc
93 24 2097152 nandd
93 32 16384 nande
93 40 32768 nandf
93 48 786432 nandg
93 56 16384 nandh
93 64 16384 nandi
93 72 81920 nandj
93 80 4358144 nandk
Now i am stuck. can someone help me find the boot logo image? or an original rom ?
any ideas ?
Best regards.
nobody ?

[UNLOCK bootloader]Using USB sniffing tool

Hi all,
I have a Redmi Note 3 Special Edition (KATE) using MIUI 8 global 7.1.19 | Beta (6.0.1 MMB29M)
and I'm trying to unlock it using the official metod but, as I see it on a loot of cases, it is stuck at 50%.
I tried to follow a lot of threads (including unofficial method), but nothing works.
Now I'm using a USB sniffer (h**p://freeusbanalyzer.com/) (this is a free one, but any usb sniffing tool could be enough) and I watch what happen between MiUnlock tool (MiFlashUnlock_1.1.0317.1_en) and my phone.
this is the log:
Code:
000000: PnP Event: Device Connected (UP), 2017-02-05 09:50:43,9853586 (1. Device: Android Bootloader Interface)
The USB device has just been connected to the system.
000001: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,4340120 +10,4486485 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000002: Control Transfer (UP), 2017-02-05 09:50:54,4352269 +0,0012149. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000003: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,4353628 +0,0001359 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xe bytes to the device
67 65 74 76 61 72 3A 70 72 6F 64 75 63 74 getvar:product
000006: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,4362125 +0,0006771. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x8 bytes from the device
4F 4B 41 59 6B 61 74 65 OKAYkate
000007: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,5170053 +0,0807928 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000008: Control Transfer (UP), 2017-02-05 09:50:54,5182476 +0,0012423. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000009: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,5183864 +0,0001388 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xd bytes to the device
67 65 74 76 61 72 3A 73 6F 63 2D 69 64 getvar:soc-id
000012: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,5192327 +0,0005505. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000013: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,5861826 +0,0669499 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000014: Control Transfer (UP), 2017-02-05 09:50:54,5873706 +0,0011880. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000015: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,5875075 +0,0001369 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xd bytes to the device
67 65 74 76 61 72 3A 73 6F 63 5F 69 64 getvar:soc_id
000018: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,5883543 +0,0006893. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000019: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,6663795 +0,0780252 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000020: Control Transfer (UP), 2017-02-05 09:50:54,6676384 +0,0012589. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000021: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,6677675 +0,0001291 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0x14 bytes to the device
67 65 74 76 61 72 3A 62 6F 61 72 64 5F 76 65 72 getvar:board_ver
73 69 6F 6E sion
000024: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,6686480 +0,0007040. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000025: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,3349831 +59,6663351 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000026: Control Transfer (UP), 2017-02-05 09:51:54,3362591 +0,0012760. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000027: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,3366136 +0,0003545 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0x7 bytes to the device
6F 65 6D 20 6C 6B 73 oem lks
000030: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,3374902 +0,0001624. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x13 bytes from the device
46 41 49 4C 75 6E 6B 6E 6F 77 6E 20 63 6F 6D 6D FAILunknown comm
61 6E 64 and
000031: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,4131364 +0,0756462 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000032: Control Transfer (UP), 2017-02-05 09:51:54,4143474 +0,0012110. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000033: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,4144867 +0,0001393 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xf bytes to the device
6F 65 6D 20 64 65 76 69 63 65 2D 69 6E 66 6F oem device-info
000036: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4153437 +0,0006957. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1b bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 74 61 6D 70 INFO.Device tamp
65 72 65 64 3A 20 66 61 6C 73 65 ered: false
000038: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4163381 +0,0009279. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1b bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 75 6E 6C 6F INFO.Device unlo
63 6B 65 64 3A 20 66 61 6C 73 65 cked: false
000040: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4173369 +0,0009572. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x24 bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 63 72 69 74 INFO.Device crit
69 63 61 6C 20 75 6E 6C 6F 63 6B 65 64 3A 20 66 ical unlocked: f
61 6C 73 65 alse
000042: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4183362 +0,0009577. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x21 bytes from the device
49 4E 46 4F 09 43 68 61 72 67 65 72 20 73 63 72 INFO.Charger scr
65 65 6E 20 65 6E 61 62 6C 65 64 3A 20 74 72 75 een enabled: tru
65 e
000044: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4193375 +0,0009602. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x14 bytes from the device
49 4E 46 4F 09 44 69 73 70 6C 61 79 20 70 61 6E INFO.Display pan
65 6C 3A 20 el:
000046: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4203363 +0,0009568. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000047: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,4849557 +0,0646194 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000048: Control Transfer (UP), 2017-02-05 09:51:54,4861066 +0,0011509. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000049: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,4862122 +0,0001056 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xc bytes to the device
67 65 74 76 61 72 3A 74 6F 6B 65 6E getvar:token
000052: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4870975 +0,0006893. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1c bytes from the device
4F 4B 41 59 45 44 71 49 31 37 50 42 51 6F 7A 4B OKAYEDqI17PBQozK
74 50 61 6B 77 7A 36 38 42 41 59 6F tPakwz68BAYo
Now I see that the oem lks command is failing with unknown command
6F 65 6D 20 6C 6B 73 oem lks
000030: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,3374902 +0,0001624. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x13 bytes from the device
46 41 49 4C 75 6E 6B 6E 6F 77 6E 20 63 6F 6D 6D FAILunknown comm
Is somebody else who tried to sniff the USB communication between Mi Unlock tool and the phone?
If your OFFICIAL unlock process is working, can you please post a log of your sniff? Maybe we can find the true commands that can unlock the phone without any permissions/ rights.
Do you know what the oem lks command is doing?

Categories

Resources