Related
Hello people,
Are there any tools for viewing and editing the amss.bin?
HEX Editor...
IDA...
Brain.
Best Regards
adfree said:
HEX Editor...
IDA...
Brain.
Best Regards
Click to expand...
Click to collapse
with revskill i got this with amss.bin
#define UNLOADED_FILE 1
#include <idc.idc>
static main() {
MakeName(0x00079B70, "Memcmp");
MakeName(0x00062160, "Memcpy");
MakeName(0x0022E924, "Memcpy");
MakeName(0x0006216B, "Memcpy_Generic");
MakeName(0x0022E92F, "Memcpy_Generic");
MakeName(0x000621D0, "__rt_udiv");
MakeName(0x00079F8C, "__rt_udiv");
MakeName(0x00062334, "strlen");
MakeName(0x0007A2C4, "strlen");
MakeName(0x00070DB2, "diag_sp");
MakeName(0x00062298, "strcmp");
MakeName(0x0007A1D8, "strcmp");
MakeName(0x0007A360, "strncpy");
MakeName(0x00072502, "diag_pkt");
MakeName(0x00062F00, "__rt_div0");
MakeName(0x0007D324, "__rt_div0");
MakeName(0x00062F10, "__32__rt_raise");
MakeName(0x0007F1F8, "__32__rt_raise");
MakeName(0x00ACC3A8, "rex_int_lock_32");
MakeName(0x00072330, "subsys_getid");
MakeName(0x0007A548, "vsprintf");
MakeName(0x00062004, "MemClr");
MakeName(0x0022E7C8, "MemClr");
MakeName(0x000725CC, "diag_subsystem");
MakeName(0x0006EC72, "diag_hdlr");
MakeName(0x000726D2, "diag_hdlr");
MakeName(0x00083D86, "diag_hdlr");
MakeName(0x00085432, "diag_hdlr");
}
What about it ?
@Tigrouzen, no segment found at 0x00079B70 etc
amss it's regular elf with a bunch of segments
Code:
Name : LOAD
Start : 0x001E7000
End : 0x001EE000
Length: 0x00007000
----------------------
Name : LOAD
Start : 0x001F0000
End : 0x001F1000
Length: 0x00001000
----------------------
Name : LOAD
Start : 0x001F2000
End : 0x005D8000
Length: 0x003E6000
----------------------
Name : LOAD
Start : 0x005D8000
End : 0x00CDB000
Length: 0x00703000
----------------------
Name : LOAD
Start : 0x00CDB000
End : 0x00D11000
Length: 0x00036000
----------------------
Name : LOAD
Start : 0x00D11000
End : 0x00DAF000
Length: 0x0009E000
----------------------
Name : LOAD
Start : 0x00DAF000
End : 0x00DB9000
Length: 0x0000A000
----------------------
Name : LOAD
Start : 0x00DB9000
End : 0x00E9B000
Length: 0x000E2000
----------------------
Name : LOAD
Start : 0x00E9C000
End : 0x01BF9000
Length: 0x00D5D000
----------------------
Name : LOAD
Start : 0x01BF9000
End : 0x01D05000
Length: 0x0010C000
----------------------
Name : LOAD
Start : 0x01FF0000
End : 0x01FF006C
Length: 0x0000006C
----------------------
Name : LOAD
Start : 0xB0000000
End : 0xB0010CE7
Length: 0x00010CE7
----------------------
Name : LOAD
Start : 0xB0040000
End : 0xB0057000
Length: 0x00017000
----------------------
Name : LOAD
Start : 0xB0100000
End : 0xB0107207
Length: 0x00007207
----------------------
Name : LOAD
Start : 0xB0140000
End : 0xB01401B8
Length: 0x000001B8
----------------------
Name : LOAD
Start : 0xB0200000
End : 0xB0208CF3
Length: 0x00008CF3
----------------------
Name : LOAD
Start : 0xB0240000
End : 0xB024028C
Length: 0x0000028C
----------------------
Name : LOAD
Start : 0xB0400000
End : 0xB040DBE8
Length: 0x0000DBE8
----------------------
Name : LOAD
Start : 0xB0600000
End : 0xB0602000
Length: 0x00002000
----------------------
Name : LOAD
Start : 0xB0602000
End : 0xB0604000
Length: 0x00002000
----------------------
Name : LOAD
Start : 0xF0000000
End : 0xF001F878
Length: 0x0001F878
----------------------
Name : LOAD
Start : 0xF0020000
End : 0xF0026000
Length: 0x00006000
load amss.bin with TriX, dump decoded stage (elf format) and analyze with disassembler (e.g. IDA)
Ok guys i extract certificate from Amss S8530 XEJL2, bootloader segments full info fsbl sbl...
Also i can dump complete NAND and find segment and algorith for RC1 too
This is appscompressed.bin algorythme
0x01ca7750 RIPEMD128+160+MD4
0x01ca7750 SEAL+MD4 key
appcomp hash :
SHA1 : EB55C6690ACAF40BB2F845313F58BFE9C3BC529D
SHA224 : AAC3E2B65CC9F33BB7EDDA3DEB541CA9E8919422CC179B4D2B49F39BAE008F00
SHA256 : 580D3DB21E41A9FE588AE544266040FABA8AF044E739971E77F2B1272323D0B6
SHA256-HTC : A44BC029D7F952750003D9695ED7B464E446D34EEF5BD9665487E4C2BF81F669
MD4 : B3BD8310FF2C4C05E2044FD491814792
MD5 : 7220779D1094C5F7789094DC75BA4E9E
CRC16 (0x1189) : F4EA
CRC30 (Block: 0x1000, Page: 0x200) : 0BD214AA
CRC30 (Block: 0x2000, Page: 0x400) : 0A28A17A
CRC32 (0xEDB88320) : 313F4EF2
CRC32 (0x04C11DB7) : 90B01704
CRC32 HTC (0xEDB88320) : B55B60A7
ECC Reed Solomon (parity 10) : 43702DA1FDAC4DB2023B
ECC BCH Micron 3 byte : 818144
ECC Hamming Toshiba (8 bit - 0x200 bytes) : C00FC3
ECC Hamming (8 bit - 0x200 bytes) : FF3CF3
ECC Hamming (16 bit - 0x200 bytes) : 3FCFFC
Amss algo :
0x0007fce0 CRC-16 norm
0x0007fee0 CRC-16 inv
0x0007f8e0 CRC-30
0x0007eb50 CRC30 Function
0x00b66194 CRC-32
0x00b66394 CRC32 Function
0x000800e0 CRC-32 Xilinx
0x0007eb58 CRC32 Xilinx Function
0x000800e4 CRC32 Xilinx Function
0x00c3c490 DES RAW Spbox
0x00c39381 RSA PKCS SHA1/RIPEND Digest
0x00c39390 MD2 S
0x00463548 SHA2 table
0x008fcc88 SHA2 table
0x00b6eb14 ZDeflate
0x0041a28c SHA1+MD4+MD5 init
0x008fcb08 SHA1+MD4+MD5 init
0x00c3d7f8 SHA1+MD4+MD5 init
0x0041a29c SHA1+MD4+MD5 key1
0x008fcb18 SHA1+MD4+MD5 key1
0x00c3d808 SHA1+MD4+MD5 key1
0x001a9844 SHA1+MD4+MD5 key2
0x0041ac1c SHA1+MD4+MD5 key2
0x008fcb1c SHA1+MD4+MD5 key2
0x001a9848 SHA1+MD4+MD5 key3
0x0041ac20 SHA1+MD4+MD5 key3
0x008fcb20 SHA1+MD4+MD5 key3
0x00463648 SHA2 init table
0x008fcd88 SHA2 init table
0x00c3d80c SHA2 init table
0x0046364c SHA2 init table
0x008fcd8c SHA2 init table
0x00c3d810 SHA2 init table
0x00419980 RIPEMD128+160+MD4
0x008fcaf8 RIPEMD128+160+MD4
0x00bdcca0 RIPEMD128+160+MD4
0x001a9844 MD5
0x0041ac1c MD5
0x008fcb1c MD5
0x00419980 SEAL+MD4 key
0x008fcaf8 SEAL+MD4 key
0x00bdcca0 SEAL+MD4 key
0x004fc7af HTC PUBLIC KEY
E9079DBB2452104990982132470BA20B7C795D1B4690B718B62FCD38D71D4E458FAF320374B89D5236C79BD57D2BA2D3508A4A605B0D48CB8CA5478BFE4D7D32AB0AE072BC367A9615F002D5023A617B422FEC1EF8DAD772D75E9C4F06EF624B864699A3F080D1B8E192B921D159852B2DC798F752B4F1FA529FF123D9963F73
0x00708134 Sober 128
0x00c3cd90 Sober 128 SBox
Possible algos little endian: 45
0x00315f6c AES te
Possible algos big endian: 1
Amss hash :
SHA1 : C59C5785E823E5E1CA9BE05DB6F55F8C8AC1BBA3
SHA224 : 5F50CED13C1204068E443919706B53D866271DAB1CFB5A9CB07A953CAE008F00
SHA256 : D86C7634FE07806D3B87701EC7F72F25DAAFAC7C40CA1D370C1ABA5840C091C0
SHA256-HTC : 120F70AECE78B8DCF69DCD79F020AB00AE17572123BA21274D6F6EE280774A09
MD4 : 7703DF5B1074392D4B91ECA23BAC9D92
MD5 : 22197F8AAD6A2CB4394E1B4E63EB843C
CRC16 (0x1189) : FAC5
CRC30 (Block: 0x1000, Page: 0x200) : 311AE4C7
CRC30 (Block: 0x2000, Page: 0x400) : 295DFC29
CRC32 (0xEDB88320) : 8DB21A34
CRC32 (0x04C11DB7) : 7B94B6A4
CRC32 HTC (0xEDB88320) : 08450BBC
ECC Reed Solomon (parity 10) : A04D69B134A126F3FD15
ECC BCH Micron 3 byte : 000000
ECC Hamming Toshiba (8 bit - 0x200 bytes) : FFFFFF
ECC Hamming (8 bit - 0x200 bytes) : FFFFFF
ECC Hamming (16 bit - 0x200 bytes) : FFFFFF
Amms certificat :
https://rapidshare.com/files/3061245812/1.cer
Well, the main idea was ..., to get some tools with which the amss.bin for bada v1.2 and v2 can be modified to work for the American/Australian version of the wave. Looks like there are some hardware differences and this file is containing information needed for the RF module.
Looks like there are some hardware differences and this file is containing information needed for the RF module
Click to expand...
Click to collapse
No idea if Hardware differences, but I'm pretty sure there are different Config/Calibration data...
Check out NV items... AMSS + NV items = Qualcomm related part...
http://www.samsunguniverse.com/forum/s8500-can-work-with-qualcomm-tools-t199.html
You could take an look on FCC documents for maybe Hardware check...
Best Regards
I think gambal refers to UMTS bands, Europe is different than in America.
UMTS bands in America are 850 - 1900
UMTS bands in Europe are 2100
bada 1.2 and above only works with Euro bands (these updates hasn't oficially released in America), so as we know the file "amss.bin" contains the parameters that define which bands to work, would be good to try to edit the information to compile a new "amss.bin" to work with American bands ..
Many Americans would be happy!
...would be good to try to edit the information to compile a new "amss.bin" to work with American bands ...
Click to expand...
Click to collapse
But you are really sure that not NV items differ?
Maybe easier to compare NV items...
Best Regards
You mean to compare amss NV items from a 1.0 American firmware and another 1.2 European firmware?
I was import to a .Qcn file a list of NV items of my mobile (bada 1.0 american), i will compare with another one of 1.2.
It's posible to create more NV items if is necesary?
sorry for double post.
i've compared NV items of my phone, first with a 1.0 american firmware then with a 1.2 European firmware..
EDIT: thought that there were no differences because the file size was identical, but looking more attentively i find some, i will continue researching,
You tried QPST or which Tool?
And are sure there are no differences?
I have 2x S8500... with QPST difference 10 NV items + one S8500 has 10 more
Content not checked... too lazy at this time.
Best Regards
Edit 1.
File Summary:
Phone Model: 19 [QSC6270/QSC6240], Configuration Name: default, Total NV Item Count: 305
Click to expand...
Click to collapse
File Summary:
Phone Model: 19 [QSC6270/QSC6240], Configuration Name: default, Total NV Item Count: 319
Click to expand...
Click to collapse
And these are only the "official" NV items... and not the hidden one...
Example...
Code:
NV item: [B]2608[/B] [NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I], index 0
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 0: 12 3d fc ff 9c 3c fc ff 26 3c fc ff b0 3b fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 1: 34 3b fc ff af 3a fc ff 2a 3a fc ff a6 39 fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 2: 22 39 fc ff 9f 38 fc ff 0c 38 fc ff 65 37 fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 3: be 36 fc ff 18 36 fc ff 73 35 fc ff ce 34 fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 4: 2a 34 fc ff 87 33 fc ff e5 32 fc ff 43 32 fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 5: a2 31 fc ff 01 31 fc ff 61 30 fc ff c2 2f fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 6: 23 2f fc ff 85 2e fc ff 85 2e fc ff 85 2e fc ff
NV_GSM_850_AMPM_MASTER_TBL_SEG8_F1_I 7: 85 2e fc ff 85 2e fc ff 85 2e fc ff 85 2e fc ff
sorry for my english, I mean to say that i find some differences..
between 2 firmwares, I find 40 differents NV items using "RF NV items Manager" program.
Example:
European 1.2 Firm:
Code:
NV item: 5059 [NV_WCDMA_2100_TX_LIN_MASTER_0_ENH_I], index 0
NV item: 5061 [NV_WCDMA_900_TX_PDM_LIN_0_ENH_I], index 0
American 1.0 Firm:
Code:
NV item: 5064 [NV_WCDMA_1900_TX_PDM_LIN_0_ENH_I], index 0
NV item: 5060 [NV_WCDMA_800_TX_PDM_LIN_0_ENH_I], index 0
(it's look like these items manage the umts network)
This are 2 items of 40 that I find.. So, I imported all 40 1.0 American Firmware Nv Items to the 1.2 Euro Firmwared Phone, (using previous modified .QCN file) then, i restart the device, but nothing happen, still no find UMTS network... But i want believe that we are close to find the solution
If I use PSAS to Display the new added NV items, these appear as "inactive item" and those already on the phone appears lile "bad parameter"
not know what else I can try...
Even if NV items count is different. Dump of NV area will be always the same in size. Area in oneNAND reserved for NV data is constant, and in most it's just empty space, filled with zeros.
Is it possible to dump whole NV items list using QPST? Can you guys do that and send dumps to me?
If not please search for following NV items and send me values you get (if you get any)
Int id 556
Int id 5
Int id 7
Int id 1403
String id 254
String id 387
String id 388
String id 256
String id 197
I want to prove some theory just taken from Bada kernel and need few different values to compare. These should contain Timezone, Locale and SimBlock settings. (If these NV items are even available)
Please send me PMs with dumps if you get any. Thanks in advance.
Tell me when you are ready "amms.bin" to "bada 2.0" so I can put it on my phone. I'm from Argentina. Thank you very much!
Rebellos said:
Int id 556
Int id 5
Int id 7
Int id 1403
Click to expand...
Click to collapse
With "PSAS" display "Inactive Item", and with "RV NV item manager" i don't these id's..
@adfree
Hey, if I wrote in phone (with "RV NV item manager") some NV items, is not take any effect... does exist another step to "activate" these items or some? maybe in Stune have to add any parameter? or maybe the "QPST Service program" tool..
I have fear of breaking the handset really... I just wan't to calibrate the UMTS bands, need these:
WCDMA_II_PCS_1900
WCDMA_V_850
http://forum.xda-developers.com/showpost.php?p=12436452&postcount=1
Other way to access NV items.
Now you can backup with sTune for instance... folders:
Code:
[B]NV
nvm[/B]
EXTREME Caution!
Some IDs are protected... so you can maybe write/activate, but not easily remove change = brick...
Best Regards
a little question..
there is a firmware of S8530 which has bada 1.2 and 850/900/2100Mhz 3g bands capable... there are firmwares prepared for Brazil and Australia.
it's posible to flash that amss.bin in a S8500 with bada 1.2?
I tried this, but the bootloader says "error erase amms"
amss.bin in a S8500 with bada 1.2?
Click to expand...
Click to collapse
If I remember correct, then yes...
Maybe not all combinations...
BUT check Multiloader ... adresses are different...
So you have to edit...
Later more.
Maybe give Link to this S8530 Firmware, so I can take an look or try for you...
Best Regards
Hi Everyone,
If you're looking for something to do with your GN's NFC radio, check out FareBot.
https://market.android.com/details?id=com.codebutler.farebot
I just released an updated version designed for Android 4.0 with support for Japanese cards.
http://codebutler.com/farebot-visits-japan
Hope you find it useful!
Any chance we could get Melbourne Myki implemented? More than happy to feed through details.
insty said:
Any chance we could get Melbourne Myki implemented? More than happy to feed through details.
Click to expand...
Click to collapse
I +1 this! Happy to help with some info if you need it!
ditto with Brisbane''s go card - happy to send you any data you need to include..
Hi,
Can't read a Singapore ezLink card, and it didn't work with a different tool (mobSenz), too. Could it be that different card standards are used?
Sent from my Galaxy Nexus using xda premium
Would be awesome if this worked with Londons Oyster Cards
azazin said:
Would be awesome if this worked with Londons Oyster Cards
Click to expand...
Click to collapse
+1
Sent from Mobile..
jrjunior said:
Hi,
Can't read a Singapore ezLink card, and it didn't work with a different tool (mobSenz), too. Could it be that different card standards are used?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
There seems to be something funny with ezlink cards. Try placing the card on a flat surface, launching FareBot, setting the phone down on top of the card, and waiting 30 seconds.
Really nice application! Very handy to see travel history / balance straight of the card
It would nice if I could use it here in The Netherlands using the "OV-chipkaart"
Here is some technical information (if usefull):
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE Classic (MF1ICS70)
# Application information:
OV-chipkaart
* Personal card
* Valid until 26-04-2016
# Memory size:
4 kB
* 32 sectors of 4 blocks and 8 sectors of 16 blocks
* 256 blocks, with 16 bytes per block
# Technologies supported:
MIFARE Classic compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Detailed protocol information:
ID: 2D:87:99:XX
ATQA: 0x0200
SAK: 0x18
Click to expand...
Click to collapse
Does this mean I can use my Phone as a clipper card?
Can WMATA cards be supported (Washington, DC)? Shows as unsupported
Technologies:
MifareClassic
NfcA
.... edit
actually this was a Rio De Janeiro Metrorio card.... I get no response from the WMATA Smartcard
Would love to have support for the norwegian flexus system aswell!
Does this do RFID card emulation?
codebutler said:
There seems to be something funny with ezlink cards. Try placing the card on a flat surface, launching FareBot, setting the phone down on top of the card, and waiting 30 seconds.
Click to expand...
Click to collapse
This works with EZ-Link! I opened Farebot and kept the phone on the card for about 10 seconds. The phone beeped 3 or 4 times before Farebot read the card.
I used to be able to just tap the card without launching the Farebot app on my Nexus S though. Maybe it's something to do with ICS?
MiKA7 said:
Would love to have support for the norwegian flexus system aswell!
Click to expand...
Click to collapse
+1 to this, but I fear that Ruter has encrypted everything and you need access/master keys to access the data.
Code:
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE DESFire (MF3ICD40)
# DESFire Applications:
NORTIC transport application
NORTIC card issuer application
# Application information:
Norway public transport card
* Card no: ******
* Valid till: Sunday May 31 2015
-----------------------------------------------
# NFC data set storage not present:
-----------------------------------------------
# Memory size:
4 kB
# IC detailed information:
Capacitance: 17 pF
# DESFire version information:
Vendor ID: NXP
Hardware info:
* type/subtype: 0x01/0x01
* version: 0.2
* storage size: 4096 bytes
* protocol: ISO/IEC 14443-2 and -3
Software info:
* type/subtype: 0x01/0x01
* version: 0.6
* storage size: 4096 bytes
* protocol: ISO/IEC 14443-3 and -4
Batch no: 0x8E45515660
Production date: week 45, 2004
-----------------------------------------------
# Technologies supported:
ISO/IEC 7816-4 compatible
Native DESFire APDU framing
ISO/IEC 14443-4 (Type A) compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Android technology classes supported:
android.nfc.tech.IsoDep
android.nfc.tech.NfcA
Tag.toString() result:
* TAG: Tech [android.nfc.tech.IsoDep, android.nfc.tech.NfcA]
# Detailed protocol information:
ID: 04:2F:39:71:45:1D:80
ATQA: 0x4403
SAK: 0x20
ATS Historical bytes: 0x80 |.|
# Memory content:
PICC level (Application ID 0x000000)
* PICC key configuration: (0x0B 01)
- PICC key required for:
~ directory list access: no
~ create/delete applications: yes
- Configuration changeable
* Master key version: 0
Application ID 0x578001 (NORTIC transport application)
* Master key configuration: (0x12 08)
- Master key required for:
~ directory list access: no
~ create/delete files: yes
- Configuration frozen
- Max. 8 (3)DES keys
* Master key version: 131
* 8 file(s) present
- File ID 0x0A: Standard data, 32 bytes
~ Communication: plain
~ Read key: key #7
~ Write key: blocked
~ Read/Write key: key #2
~ Change key: key #1
- File ID 0x0C: Standard data, 32 bytes
~ Communication: plain
~ Read key: key #7
~ Write key: blocked
~ Read/Write key: key #3
~ Change key: key #1
- File ID 0x01: Backup data, 384 bytes
~ Communication: with MAC
~ Read key: key #7
~ Write key: blocked
~ Read/Write key: key #4
~ Change key: key #1
- File ID 0x02: Backup data, 128 bytes
~ Communication: with MAC
~ Read key: key #7
~ Write key: key #6
~ Read/Write key: key #4
~ Change key: key #1
- File ID 0x03: Backup data, 288 bytes
~ Communication: with MAC
~ Read key: key #7
~ Write key: key #6
~ Read/Write key: key #4
~ Change key: key #1
- File ID 0x04: Value data
~ Lower limit: 0
~ Upper limit: 2147483647
~ Limited credit not allowed
~ Communication: with MAC
~ Read key: key #7
~ Write key: blocked
~ Read/Write key: key #5
~ Change key: key #1
- File ID 0x05: Cyclic record file, 8 records
~ Record size: 36 bytes
~ Max. no. of records: 9
~ Communication: plain
~ Read key: key #7
~ Write key: key #6
~ Read/Write key: blocked
~ Change key: key #1
- File ID 0x06: Cyclic record file, 2 records
~ Record size: 32 bytes
~ Max. no. of records: 3
~ Communication: plain
~ Read key: key #7
~ Write key: key #5
~ Read/Write key: blocked
~ Change key: key #1
Application ID 0x578000 (NORTIC card issuer application)
* Master key configuration: (0x12 04)
- Master key required for:
~ directory list access: no
~ create/delete files: yes
- Configuration frozen
- Max. 4 (3)DES keys
* Master key version: 197
* 1 file(s) present
- File ID 0x0C: Standard data, 16 bytes
~ Communication: plain
~ Read key: free access
~ Write key: blocked
~ Read/Write key: blocked
~ Change key: key #1
~ Contents:
[0000] 90 80 00 02 00 08 9E 39 |.......9|
[0008] 69 14 00 00 40 00 0C 40 |[email protected]@|
-----------------------------------------------
azazin said:
Would be awesome if this worked with Londons Oyster Cards
Click to expand...
Click to collapse
+2
10char
edit: sorry wrong thread
I have one I'd like to add to the list, if the dev is taking suggestions:
Konami eAmusement pass - it's a card used for arcade games that stores your information on their network
Unsupported tag
Identifier: 84696808000104e0
Technologies: NfcV, NdefFormatable
edit: while I think about it, here we all sit and ask for things, but I'd like to say thanks for putting work into this app that reads outside-the-box NFC tags
Farebot
Hi Mr Eric,
Does Farebot supports writing? Is overwriting possible without losing its current data? I want to try adding extra command to be written in my ezlink card also.
Thanks
+1 for Oyster card support
Hi,
I am trying to clone or modify this card that I have. I do not have the keys. Is it possible? What can I do with it?
I am basically trying to clone it so it works with my phone case as it is too thick.. I'm open to melting the card and taking the internals out just to get it to work too, any suggestions?
See below for the dump:
** TagInfo scan (version 4.11.59 [β4011059]) 2016-01-04 11:09:14 **
-- INFO ------------------------------
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE DESFire EV1 (MF3ICD41)
# DESFire Applications:
1 unknown application
-- NDEF ------------------------------
# NFC data set storage not present:
Maximum NDEF storage size after format: 4094 bytes
-- EXTRA ------------------------------
# Memory information:
Size: 4 kB
Available: 4.0 kB
# IC detailed information:
Capacitance: 17 pF
# Version information:
Vendor ID: NXP
Hardware info:
* Type/subtype: 0x01/0x01
* Version: 1.0
* Storage size: 4096 bytes
* Protocol: ISO/IEC 14443-2 and -3
Software info:
* Type/subtype: 0x01/0x01
* Version: 1.4
* Storage size: 4096 bytes
* Protocol: ISO/IEC 14443-3 and -4
Batch no: 0xBA4450B120
Production date: week 10, 2013
-- TECH ------------------------------
# Technologies supported:
ISO/IEC 7816-4 compatible
Native DESFire APDU framing
ISO/IEC 14443-4 (Type A) compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.IsoDep, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable]
android.nfc.tech.NdefFormatable
android.nfc.tech.IsoDep
* Maximum transceive length: 261 bytes
* Default maximum transceive time-out: 618 ms
* Extended length APDUs not supported
android.nfc.tech.NfcA
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms
# Detailed protocol information:
ID: 04:43:8B:5A:56:2C:80
ATQA: 0x4403
SAK: 0x20
ATS: 0x06757781028000
* Max. accepted frame size: 64 bytes (FSCI: 5)
* Supported receive rates:
- 106, 212, 424, 848 kbit/s (DR: 1, 2, 4, 8)
* Supported send rates:
- 106, 212, 424, 848 kbit/s (DS: 1, 2, 4, 8)
* Different send and receive rates supported
* SFGT: 604.1 us (SFGI: 1)
* FWT: 77.33 ms (FWI: 8)
* NAD not supported
* CID supported
* Historical bytes: 0x80 |.|
# Memory content:
PICC level (Application ID 0x000000)
* PICC key configuration:
- AES key
- PICC key changeable
- PICC key required for:
~ directory list access: no
~ create/delete applications: yes
- Configuration changeable
- PICC key version: 129
Application ID 0x000001
* Key configuration:
- 14 (3)DES keys
- Master key changeable
- Master key required for:
~ directory list access: no
~ create/delete files: yes
- Configuration changeable
- Key itself required for changing a key
* 1 file present
- File ID 0x00: Standard data, 384 bytes
~ Communication: with MAC
~ Read key: key #1
~ Write key: key #2
~ Read/Write key: key #2
~ Change key: master key
~ (No access)
--------------------------------------
As application 0x000001 is using 3DES keys, it may be possible (I'm curious too) to crack the read/write key because its using 3DES and not something stronger like AES
lawonga said:
Hi,
I am trying to clone or modify this card that I have. I do not have the keys. Is it possible? What can I do with it?
I am basically trying to clone it so it works with my phone case as it is too thick.. I'm open to melting the card and taking the internals out just to get it to work too, any suggestions?
See below for the dump:
** TagInfo scan (version 4.11.59 [β4011059]) 2016-01-04 11:09:14 **
-- INFO ------------------------------
# IC manufacturer:
NXP Semiconductors
# IC type:
MIFARE DESFire EV1 (MF3ICD41)
# DESFire Applications:
1 unknown application
-- NDEF ------------------------------
# NFC data set storage not present:
Maximum NDEF storage size after format: 4094 bytes
-- EXTRA ------------------------------
# Memory information:
Size: 4 kB
Available: 4.0 kB
# IC detailed information:
Capacitance: 17 pF
# Version information:
Vendor ID: NXP
Hardware info:
* Type/subtype: 0x01/0x01
* Version: 1.0
* Storage size: 4096 bytes
* Protocol: ISO/IEC 14443-2 and -3
Software info:
* Type/subtype: 0x01/0x01
* Version: 1.4
* Storage size: 4096 bytes
* Protocol: ISO/IEC 14443-3 and -4
Batch no: 0xBA4450B120
Production date: week 10, 2013
-- TECH ------------------------------
# Technologies supported:
ISO/IEC 7816-4 compatible
Native DESFire APDU framing
ISO/IEC 14443-4 (Type A) compatible
ISO/IEC 14443-3 (Type A) compatible
ISO/IEC 14443-2 (Type A) compatible
# Android technology information:
Tag description:
* TAG: Tech [android.nfc.tech.IsoDep, android.nfc.tech.NfcA, android.nfc.tech.NdefFormatable]
android.nfc.tech.NdefFormatable
android.nfc.tech.IsoDep
* Maximum transceive length: 261 bytes
* Default maximum transceive time-out: 618 ms
* Extended length APDUs not supported
android.nfc.tech.NfcA
* Maximum transceive length: 253 bytes
* Default maximum transceive time-out: 618 ms
# Detailed protocol information:
ID: 04:43:8B:5A:56:2C:80
ATQA: 0x4403
SAK: 0x20
ATS: 0x06757781028000
* Max. accepted frame size: 64 bytes (FSCI: 5)
* Supported receive rates:
- 106, 212, 424, 848 kbit/s (DR: 1, 2, 4, 8)
* Supported send rates:
- 106, 212, 424, 848 kbit/s (DS: 1, 2, 4, 8)
* Different send and receive rates supported
* SFGT: 604.1 us (SFGI: 1)
* FWT: 77.33 ms (FWI: 8)
* NAD not supported
* CID supported
* Historical bytes: 0x80 |.|
# Memory content:
PICC level (Application ID 0x000000)
* PICC key configuration:
- AES key
- PICC key changeable
- PICC key required for:
~ directory list access: no
~ create/delete applications: yes
- Configuration changeable
- PICC key version: 129
Application ID 0x000001
* Key configuration:
- 14 (3)DES keys
- Master key changeable
- Master key required for:
~ directory list access: no
~ create/delete files: yes
- Configuration changeable
- Key itself required for changing a key
* 1 file present
- File ID 0x00: Standard data, 384 bytes
~ Communication: with MAC
~ Read key: key #1
~ Write key: key #2
~ Read/Write key: key #2
~ Change key: master key
~ (No access)
--------------------------------------
Click to expand...
Click to collapse
If you get it, please tell us.
I guess no one manage to do this and my EV3 would be even harder to do so ...so no luck I suppose
My application ID is 0x000000 (PICC)
Hi
I've tried to flash twrp on my Samsung Galaxy Tab S 10.5 but under Windows I don't get a connection in Download Mode (three different PC with Win10 and Win7) and under Linux Heimdall also refuses to connect to the device
Here is the verbose output
Code:
[email protected]:~/Downloads$ sudo heimdall print-pit --verbose
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
when trying the dd methode then I only get a access restriction that I'm not allowed to write in the Recovery partition.
Is there a way to get TWRP, LineageOS and root access on a T800 with MM (Android 6.0.1 / MMB29K.T800XXU1CPK2)?
All the How-to are for older Versions and need options that there aren't anymore
br
Daniel
i have a teclast M20 4G M3K4 and I would like to root it found a link on the internet that explains how to do this would like your opinions
canot post link because i have no rights
AIDA64 for Android v1.66 Repo
<<< System >>>
Device Model: Teclast M20 4G
Device Type: Tablet
Manufacturer: techain
Model: M20_4G
Brand: Teclast
Board: mt6797
Device: M20_4G
Hardware: mt6797
Platform: mt6797
Product: M20_4G
Installed RAM: 4 GB LPDDR3
Total Memory: 3682 MB
Available Memory: 1887 MB
Internal Storage Total Space: 53.43 GB
Internal Storage Free Space: 49.40 GB
External Storage Total Space: 29.80 GB
External Storage Free Space: 21.95 GB
Bluetooth Version: 4.0
Device Features: android.hardware.audio.low_latency
android.hardware.audio.output
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.autofocus
android.hardware.camera.front
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.opengles.aep
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.telephony
android.hardware.telephony.cdma
android.hardware.telephony.gsm
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.vulkan.level
android.hardware.vulkan.version
android.hardware.wifi
android.hardware.wifi.direct
android.software.activities_on_secondary_displays
android.software.app_widgets
android.software.autofill
android.software.backup
android.software.companion_device_setup
android.software.connectionservice
android.software.cts
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.managed_users
android.software.midi
android.software.picture_in_picture
android.software.print
android.software.voice_recognizers
android.software.webview
<<< CPU >>>
SoC Model: MediaTek Helio X20 (MT6797)
Core Architecture: 4x ARM Cortex-A53 @ 1391 MHz
4x ARM Cortex-A53
2x ARM Cortex-A72
Manufacturing Process: 20 nm
Instruction Set: 64-bit ARMv8-A
CPU Revision: r0p1
CPU Cores: 10
CPU Clock Range: 221 - 1391 MHz
Core 1 Clock: 1118 MHz
Core 2 Clock: 1118 MHz
Core 3 Clock: 1118 MHz
Core 4 Clock: (sleeping)
Core 5 Clock: (sleeping)
Core 6 Clock: (sleeping)
Core 7 Clock: (sleeping)
Core 8 Clock: (sleeping)
Core 9 Clock: (sleeping)
Core 10 Clock: (sleeping)
Scaling Governor: interactive
Supported ABIs: arm64-v8a, armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
Supported 64-bit ABIs: arm64-v8a
AES: Supported
NEON: Supported
SHA1: Supported
SHA2: Supported
<<< Display >>>
Screen Resolution: 2560 × 1600
Technology: IPS LCD
Screen Size: 218 mm × 136 mm
Screen Diagonal: 10.1 inches
Pixel Density: 299 dpi (xhdpi)
xdpi / ydpi: 320 / 320 dpi
GPU Vendor: ARM
GPU Renderer: Mali-T880
Refresh Rate: 57 Hz
Default Orientation: Landscape
OpenGL ES Version: 3.2
GPU Version: OpenGL ES 3.2 v1.r20p0-01rel0.d174d1328b67c542941eec67baa38e6a
OpenGL ES Extensions: GL_EXT_debug_marker
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth24
GL_OES_depth_texture
GL_OES_depth_texture_cube_map
GL_OES_packed_depth_stencil
GL_OES_rgb8_rgba8
GL_EXT_read_format_bgra
GL_OES_compressed_paletted_texture
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_EGL_image_external
GL_OES_EGL_image_external_essl3
GL_OES_EGL_sync
GL_OES_texture_npot
GL_OES_vertex_half_float
GL_OES_required_internalformat
GL_OES_vertex_array_object
GL_OES_mapbuffer
GL_EXT_texture_format_BGRA8888
GL_EXT_texture_rg
GL_EXT_texture_type_2_10_10_10_REV
GL_OES_fbo_render_mipmap
GL_OES_element_index_uint
GL_EXT_shadow_samplers
GL_OES_texture_compression_astc
GL_KHR_texture_compression_astc_ldr
GL_KHR_texture_compression_astc_hdr
GL_KHR_texture_compression_astc_sliced_3d
GL_KHR_debug
GL_EXT_occlusion_query_boolean
GL_EXT_disjoint_timer_query
GL_EXT_blend_minmax
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_OES_texture_3D
GL_EXT_texture_storage
GL_EXT_multisampled_render_to_texture
GL_OES_surfaceless_context
GL_OES_texture_stencil8
GL_EXT_shader_pixel_local_storage
GL_ARM_shader_framebuffer_fetch
GL_ARM_shader_framebuffer_fetch_depth_stencil
GL_ARM_mali_program_binary
GL_EXT_sRGB
GL_EXT_sRGB_write_control
GL_EXT_texture_sRGB_decode
GL_EXT_texture_sRGB_R8
GL_EXT_texture_sRGB_RG8
GL_KHR_blend_equation_advanced
GL_KHR_blend_equation_advanced_coherent
GL_OES_texture_storage_multisample_2d_array
GL_OES_shader_image_atomic
GL_EXT_robustness
GL_EXT_draw_buffers_indexed
GL_OES_draw_buffers_indexed
GL_EXT_texture_border_clamp
GL_OES_texture_border_clamp
GL_EXT_texture_cube_map_array
GL_OES_texture_cube_map_array
GL_OES_sample_variables
GL_OES_sample_shading
GL_OES_shader_multisample_interpolation
GL_EXT_shader_io_blocks
GL_OES_shader_io_blocks
GL_EXT_tessellation_shader
GL_OES_tessellation_shader
GL_EXT_primitive_bounding_box
GL_OES_primitive_bounding_box
GL_EXT_geometry_shader
GL_OES_geometry_shader
GL_ANDROID_extension_pack_es31a
GL_EXT_gpu_shader5
GL_OES_gpu_shader5
GL_EXT_texture_buffer
GL_OES_texture_buffer
GL_EXT_copy_image
GL_OES_copy_image
GL_EXT_shader_non_constant_global_initializers
GL_EXT_color_buffer_half_float
GL_EXT_color_buffer_float
GL_EXT_YUV_target
GL_OVR_multiview
GL_OVR_multiview2
GL_OVR_multiview_multisampled_render_to_texture
GL_KHR_robustness
GL_KHR_robust_buffer_access_behavior
GL_EXT_draw_elements_base_vertex
GL_OES_draw_elements_base_vertex
<<< Network >>>
<< Telephony >>
Phone Type: GSM
Network Operator Name: Oi
Network Operator Code: 72431
Network Operator Country: Brazil
SIM Provider Name: Oi
SIM Provider Code: 72431
SIM Provider Country: Brazil
SIM State: Ready
Network Type: EDGE
Data Connection State: Disconnected
Data Activity: None
Device Is Roaming: No
ICC Card: Present
<< Wi-Fi >>
State: Enabled
SSID: "casa1"
BSSID: ec:08:6b:e0:3e:e7
Hidden SSID: No
IPv4 Address: 192.168.1.102
IPv6 Address: fe80::200:3ff:fe22:28f9
Signal Strength: -70 dBm (Good)
Link Speed: 52 Mbps
Frequency: 2457 MHz
Network ID: 0
Gateway: 192.168.1.1
Netmask: 255.255.255.0
DNS1: 8.8.8.8
DNS2: 8.8.4.4
DHCP Lease Duration: 24 hours
5 GHz Band: Supported
Wi-Fi Aware: Not Supported
Wi-Fi Direct: Supported
<<< Battery >>>
Power Source: Battery
Level: 50 %
Status: Not Charging
Health: Good
Technology: Li-ion
Temperature: 25.0°C
Voltage: 3.765 V
Charge Counter: 6400 mAh
Discharge Rate: 533 mA
Capacity: 6600 mAh
<<< Android >>>
Android Version: 8.0.0 (Oreo)
API Level: 26
Android Security Patch Level: 2018-06-05
Rooted Device: No
Android ID: b640aeefa323aa7e
Baseband: MOLY.LR11.W1630.MD.MP.V67.2, 2018/04/02 17:50
Build ID: V1.02_20190223
Codename: REL
Fingerprint: CHUWI/Hi9Air/Hi9Air:8.0.0/O00623/1520042099:user/release-keys
ID: O00623
Incremental: 1520042099
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 384 MB
Kernel Architecture: aarch64
Kernel Version: 3.18.60
Tags: release-keys
Type: user
Google Play Services Version: 19.6.29 (040406-278422107)
Huawei Mobile Services Version: < Not Present >
OpenSSL Version: OpenSSL 1.0.2 (compatible; BoringSSL)
ZLib Version: 1.2.8
ICU CLDR Version: 30.0.3
ICU Library Version: 58.2
ICU Unicode Version: 9.0
Android Language: English (United States)
Configured Time Zone: Brasilia Standard Time (UTC-03:00)
UpTime: 01:08:50
<<< Devices >>>
<< Rear-Facing Camera >>
Resolution: 5.0 MP (2592 × 1944)
Focal Length: 3.50 mm
Focus Modes: auto, macro, infinity, continuous-picture, continuous-video
Video Stabilization: Supported
Zoom: Supported
Auto Exposure Locking: Supported
Auto White Balance Locking: Supported
Flash: Not Supported
<< Front-Facing Camera >>
Resolution: 2.1 MP (1920 × 1088)
Focal Length: 3.50 mm
Focus Modes: fixed, infinity
Video Stabilization: Supported
Zoom: Supported
Auto Exposure Locking: Supported
Auto White Balance Locking: Supported
Flash: Not Supported
<< Vulkan Device - Mali-T880 >>
Device Name: Mali-T880
Device Type: Integrated GPU
Device UUID: C5-18-34-CB-95-43-3E-BE-3B-53-73-BF-A4-4B-EC-E2
Device ID: 000013B5-08801008
Memory Size: 3768076 KB
Max 1D Image Size: 8192
Max 2D Image Size: 8192 x 8192
Max 3D Image Size: 4096 x 4096 x 4096
Max Cube Image Size: 8192 x 8192
Max Image Layers: 256
Max Texel Buffer Elements: 65536
Max Uniform Buffer Range: 65536
Max Storage Buffer Range: 134217728
Max Push Constants Size: 128 bytes
Buffer Image Granularity: 4 KB
Max Bound Descriptor Sets: 4
Max Per-Stage Descriptor Samplers: 128
Max Per-Stage Descriptor Uniform Buffers: 12
Max Per-Stage Descriptor Storage Buffers: 4
Max Per-Stage Descriptor Sampled Images: 16
Max Per-Stage Descriptor Storage Images: 4
Max Per-Stage Descriptor Input Attachments: 4
Max Per-Stage Resources: 44
Max Descriptor Set Samplers: 768
Max Descriptor Set Uniform Buffers: 72
Max Descriptor Set Dynamic Uniform Buffers: 8
Max Descriptor Set Storage Buffers: 24
Max Descriptor Set Dynamic Storage Buffers: 4
Max Descriptor Set Sampled Images: 96
Max Descriptor Set Storage Images: 24
Max Descriptor Set Input Attachments: 4
Max Vertex Input Attributes: 16
Max Vertex Input Bindings: 16
MaxVertex Input Attribute Offset: 2047
Max Vertex Input Binding Stride: 2048
Max Vertex Output Components: 128
Max Tesselation Generation Level: 64
Max Tesselation Patch Size: 32
Max Tesselation Control Per-Vertex Input Components: 64
Max Tesselation Control Per-Vertex Output Components: 64
Max Tesselation Control Per-Patch Output Components: 120
Max Tesselation Control Total Output Components: 2048
Max Tesselation Evaluation Input Components: 64
Max Tesselation Evaluation Output Components: 64
Max Geometry Shader Invocations: 32
Max Geometry Input Components: 64
Max Geometry Output Components: 128
Max Geometry Output Vertices: 256
Max Geometry Total Output Components: 1024
Max Fragment Input Components: 128
Max Fragment Output Attachments: 4
Max Fragment Combined Output Resources: 12
Max Compute Shared Memory Size: 32 KB
Max Compute Work Group Count: X: 65536, Y: 65536, Z: 65536
Max Compute Work Group Invocations: 256
Max Compute Work Group Size: X: 256, Y: 256, Z: 256
Subpixel Precision Bits: 8
Subtexel Precision Bits: 8
Mipmap Precision Bits: 8
Max Draw Indexed Index Value: 4294967295
Max Draw Indirect Count: 1
Max Sampler LOD Bias: 2.000000
Max Sampler Anisotropy: 1.000000
Max Viewports: 1
Max Viewport Size: 8192 x 8192
Viewport Bounds Range: -16384.000000 ... 16383.000000
Min Memory Map Alignment: 64 bytes
Min Texel Buffer Offset Alignment: 256 bytes
Min Uniform Buffer Offset Alignment: 16 bytes
Min Storage Buffer Offset Alignment: 256 bytes
Min / Max Texel Offset: -8 / 7
Min / Max Texel Gather Offset: -8 / 7
Min / Max Interpolation Offset: -0.500000 / 0.500000
Subpixel Interpolation Offset Bits: 4
Max Framebuffer Size: 8192 x 8192
Max Framebuffer Layers: 256
Framebuffer Color Sample Counts: 0x00000005
Framebuffer Depth Sample Counts: 0x00000005
Framebuffer Stencil Sample Counts: 0x00000005
Framebuffer No Attachments Sample Counts: 0x00000005
Max Color Attachments: 4
Sampled Image Color Sample Counts: 0x00000005
Sampled Image Integer Sample Counts: 0x00000001
Sampled Image Depth Sample Counts: 0x00000005
Sampled Image Stencil Sample Counts: 0x00000005
Storage Image Sample Counts: 0x00000001
Max Sample Mask Words: 1
Discrete Queue Priorities: 2
Point Size Range: 1.000000 ... 1024.000000
Line Width Range: 1.000000 ... 1.000000
Point Size Granularity: 0.062500
Optimal Buffer Copy Offset Alignment: 64 bytes
Optimal Buffer Copy Row Pitch Alignment: 64 bytes
Non-Coherent Atom Size: 64 bytes
Driver Version: 313.546.569
API Version: 1.0.52
Vulkan Library: /system/lib64/libvulkan.so
Alpha To One: Not Supported
Anisotropic Filtering: Not Supported
ASTC LDR Texture Compression: Supported
BC Texture Compression: Not Supported
Depth Bias Clamping: Supported
Depth Bounds Tests: Not Supported
Depth Clamping: Not Supported
Draw Indirect First Instance: Supported
Dual Source Blend Operations: Not Supported
ETC2 and EAC Texture Compression: Supported
Fragment Stores and Atomics: Supported
Full Draw Index Uint32: Supported
Geometry Shader: Supported
Image Cube Array: Supported
Independent Blend: Supported
Inherited Queries: Not Supported
Large Points: Supported
Logic Operations: Not Supported
Multi-Draw Indirect: Not Supported
Multi Viewport: Not Supported
Occlusion Query Precise: Supported
Pipeline Statistics Query: Not Supported
Point and Wireframe Fill Modes: Not Supported
Robust Buffer Access: Supported
Sample Rate Shading: Supported
Shader Clip Distance: Not Supported
Shader Cull Distance: Not Supported
Shader Float64: Not Supported
Shader Image Gather Extended: Supported
Shader Int16: Supported
Shader Int64: Not Supported
Shader Resource Min LOD: Not Supported
Shader Resource Residency: Not Supported
Shader Sampled Image Array Dynamic Indexing: Supported
Shader Storage Buffer Array Dynamic Indexing: Supported
Shader Storage Image Array Dynamic Indexing: Supported
Shader Storage Image Extended Formats: Not Supported
Shader Storage Image Multisample: Not Supported
Shader Storage Image Read Without Format: Supported
Shader Storage Image Write Without Format: Supported
Shader Tesselation and Geometry Point Size: Not Supported
Shader Uniform Buffer Array Dynamic Indexing: Supported
Sparse Binding: Not Supported
Sparse Residency 2 Samples: Not Supported
Sparse Residency 4 Samples: Not Supported
Sparse Residency 8 Samples: Not Supported
Sparse Residency 16 Samples: Not Supported
Sparse Residency Aliased: Not Supported
Sparse Residency Aligned Mip Size: No
Sparse Residency Buffer: Not Supported
Sparse Residency Image 2D: Not Supported
Sparse Residency Image 3D: Not Supported
Sparse Residency Non-Resident Strict: No
Sparse Residency Standard 2D Block Shape: No
Sparse Residency Standard 2D Multisample Block Shape: No
Sparse Residency Standard 3D Block Shape: No
Standard Sample Locations: Yes
Strict Line Rasterization: Yes
Tesselation Shader: Supported
Timestamps on All Graphics and Compute Queues: Not Supported
Variable Multisample Rate: Not Supported
Vertex Pipeline Stores and Atomics: Not Supported
Wide Lines: Not Supported
Device Extensions: VK_KHR_incremental_present
VK_GOOGLE_display_timing
VK_KHR_maintenance1
VK_KHR_shader_draw_parameters
VK_KHR_swapchain
Instance Extensions: VK_KHR_surface
VK_KHR_android_surface
VK_EXT_swapchain_colorspace
VK_KHR_get_surface_capabilities2
VK_EXT_debug_report
VK_KHR_get_physical_device_properties2
No USB devices found.
No OpenCL devices found.
No CUDA devices found.
No PCI devices found.
<<< Thermal >>>
Battery: 25.0°C
<<< Sensors >>>
ACCELEROMETER:
<<< Apps >>>
AIDA64: com.finalwire.aida64(v1.66)
AnimeDLR: net.android.adm(v6.0.1)
Dashlane: com.dashlane(v6.1946.2-arm64-v8a)
Firefox Nightly: org.mozilla.fenix.nightly(vNightly 191117 06:00)
Rastreador: app.rmayrink.Rastreador_de_Encomendas(v1.9.9)
TuneIn Radio Pro: radiotime.player(v23.2)
WhatsApp: com.whatsapp(v2.19.333)
<<< Codecs >>>
OMX.MTK.AUDIO.DECODER.MP3: audio/mpeg
OMX.MTK.AUDIO.DECODER.GSM: audio/gsm
OMX.MTK.AUDIO.DECODER.RAW: audio/raw
OMX.MTK.AUDIO.DECODER.G711.ALAW: audio/g711-alaw
OMX.MTK.AUDIO.DECODER.G711.MLAW: audio/g711-mlaw
OMX.MTK.AUDIO.DECODER.ADPCM.MS: audio/x-adpcm-ms
OMX.MTK.AUDIO.DECODER.ADPCM.DVI: audio/x-adpcm-dvi-ima
OMX.MTK.AUDIO.DECODER.APE: audio/ape
OMX.MTK.AUDIO.DECODER.ALAC: audio/alac
OMX.MTK.VIDEO.DECODER.HEVC: video/hevc
OMX.MTK.VIDEO.DECODER.MPEG4: video/mp4v-es
OMX.MTK.VIDEO.DECODER.H263: video/3gpp
OMX.MTK.VIDEO.DECODER.AVC: video/avc
OMX.MTK.VIDEO.DECODER.VPX: video/x-vnd.on2.vp8
OMX.MTK.VIDEO.DECODER.VP9: video/x-vnd.on2.vp9
OMX.MTK.VIDEO.DECODER.DIVX: video/divx
OMX.MTK.VIDEO.DECODER.DIVX3: video/divx3
OMX.MTK.VIDEO.DECODER.XVID: video/xvid
OMX.MTK.VIDEO.DECODER.VC1: video/x-ms-wmv
OMX.MTK.VIDEO.DECODER.MPEG2: video/mpeg2
OMX.MTK.VIDEO.ENCODER.MPEG4: video/mp4v-es
OMX.MTK.VIDEO.ENCODER.H263: video/3gpp
OMX.MTK.VIDEO.ENCODER.AVC: video/avc
OMX.MTK.VIDEO.ENCODER.HEVC: video/hevc
OMX.MTK.VIDEO.ENCODER.VPX: video/x-vnd.on2.vp8
OMX.google.mp3.decoder: audio/mpeg
OMX.google.amrnb.decoder: audio/3gpp
OMX.google.amrwb.decoder: audio/amr-wb
OMX.google.aac.decoder: audio/mp4a-latm
OMX.google.g711.alaw.decoder: audio/g711-alaw
OMX.google.g711.mlaw.decoder: audio/g711-mlaw
OMX.google.vorbis.decoder: audio/vorbis
OMX.google.opus.decoder: audio/opus
OMX.google.raw.decoder: audio/raw
OMX.google.aac.encoder: audio/mp4a-latm
OMX.google.amrnb.encoder: audio/3gpp
OMX.google.amrwb.encoder: audio/amr-wb
OMX.google.flac.encoder: audio/flac
OMX.google.mpeg4.decoder: video/mp4v-es
OMX.google.h263.decoder: video/3gpp
OMX.google.h264.decoder: video/avc
OMX.google.hevc.decoder: video/hevc
OMX.google.vp8.decoder: video/x-vnd.on2.vp8
OMX.google.vp9.decoder: video/x-vnd.on2.vp9
OMX.google.h263.encoder: video/3gpp
OMX.google.h264.encoder: video/avc
OMX.google.mpeg4.encoder: video/mp4v-es
OMX.google.vp8.encoder: video/x-vnd.on2.vp8
<<< Directories >>>
Data: /data
Root: /system
Java Home: /system
Download/Cache Content: /data/cache
<< External Storage >>
Primary External Storage: /storage/emulated/0
External Files #1: /storage/emulated/0/Android/data/com.finalwire.aida64/files
External Files #2: /storage/C2E0-1DEA/Android/data/com.finalwire.aida64/files
Alarms: /storage/emulated/0/Alarms
DCIM: /storage/emulated/0/DCIM
Downloads: /storage/emulated/0/Download
Movies: /storage/emulated/0/Movies
Music: /storage/emulated/0/Music
Notifications: /storage/emulated/0/Notifications
Pictures: /storage/emulated/0/Pictures
Podcasts: /storage/emulated/0/Podcasts
Ringtones: /storage/emulated/0/Ringtones
<< Mount Points >>
/: Device: rootfs
File System: rootfs
Read-Only
/dev: Device: tmpfs
File System: tmpfs
Read-Write
/dev/pts: Device: devpts
File System: devpts
Read-Write
/dev/cpuctl: Device: none
File System: cgroup
Read-Write
/dev/cpuset: Device: none
File System: cgroup
Read-Write
/dev/usb-ffs/adb: Device: adb
File System: functionfs
Read-Write
/proc: Device: proc
File System: proc
Read-Write
/sys: Device: sysfs
File System: sysfs
Read-Write
/sys/fs/selinux: Device: selinuxfs
File System: selinuxfs
Read-Write
/sys/kernel/debug: Device: debugfs
File System: debugfs
Read-Write
/sys/kernel/debug/tracing: Device: tracefs
File System: tracefs
Read-Write
/sys/fs/pstore: Device: pstore
File System: pstore
Read-Write
/system: Device: /dev/block/dm-0
File System: ext4
Read-Only
/vendor: Device: /dev/block/dm-1
File System: ext4
Read-Only
/acct: Device: none
File System: cgroup
Read-Write
/mnt: Device: tmpfs
File System: tmpfs
Read-Write
/mnt/runtime/default/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/read/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/runtime/write/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/mnt/media_rw/C2E0-1DEA: Device: /dev/block/vold/public:179,129
File System: vfat
Read-Write
/mnt/runtime/default/C2E0-1DEA: Device: /mnt/media_rw/C2E0-1DEA
File System: sdcardfs
Read-Write
/mnt/runtime/read/C2E0-1DEA: Device: /mnt/media_rw/C2E0-1DEA
File System: sdcardfs
Read-Write
/mnt/runtime/write/C2E0-1DEA: Device: /mnt/media_rw/C2E0-1DEA
File System: sdcardfs
Read-Write
/config: Device: none
File System: configfs
Read-Write
/cache: Device: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache
File System: ext4
Read-Write
/protect_f: Device: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1
File System: ext4
Read-Write
/protect_s: Device: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2
File System: ext4
Read-Write
/nvdata: Device: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata
File System: ext4
Read-Write
/nvcfg: Device: /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvcfg
File System: ext4
Read-Write
/data: Device: /dev/block/dm-2
File System: ext4
Read-Write
/storage: Device: tmpfs
File System: tmpfs
Read-Write
/storage/emulated: Device: /data/media
File System: sdcardfs
Read-Write
/storage/C2E0-1DEA: Device: /mnt/media_rw/C2E0-1DEA
File System: sdcardfs
Read-Write
/storage/self: Device: tmpfs
File System: tmpfs
Read-Write
<<< System Files >>>
Buddy Info: /proc/buddyinfo
Build Properties: /system/build.prop
Character & Block Devices: /proc/devices
Command Line: /proc/cmdline
CPU Information: /proc/cpuinfo
Default Properties: /default.prop
Execution Domains: /proc/execdomains
File Systems: /proc/filesystems
Frame Buffer Devices: /proc/fb
Hosts: /system/etc/hosts
Interrupts: /proc/interrupts
Input Devices: /proc/bus/input/devices
I/O Ports: /proc/ioports
Kernel Version: /proc/version
Load Average: /proc/loadavg
Locked Files: /proc/locks
Memory Information: /proc/meminfo
Memory Map: /proc/iomem
Misc Drivers: /proc/misc
Partitions: /proc/partitions
Statistics: /proc/stat
Swap Spaces: /proc/swaps
serial number:SN811SN8112H184641652