Error message "no ndef messages found" - NFC Hacking

Hello everyone
I am using an apk from Google Play Store called "NFC Reader Writer" by Manjul Saini on a smarphone Galaxy J7 with android 8.1.0
I am trying to copy the above NFC card. Here is the data have been read:
-Serial number: aa:42:3d:d1
-Tehnologies: NfcA, MifareClassic, NdeFormatable
-SAK (hex): 0x08:00
-ATQA (hex): 0x04:00
-Default tranceive time out: 618ms
-Max Tranceive Length: 253 bytes-
-Mifare Classic type: Classic
-Mifare size: 1024 bytes
-Mifare sectors: 16
-Mifare blocks: 64
But when trying to copy I get an error message "No NDEF messages found". Any ideas about this? Is it possible the card being protected?
Thanks in advance

Related

Error 112 or 113

If you are the 112 error,
with mtty set 14 0 and nothing then task 28 and i have results like
set 14 0
HTCSF kEØ(HTCEUSB>
USB>task 28
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
MountVolume:status=23.
FAT0 Size: 0x0
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x3770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x100000,FAT2_ADDR=0xB00000
USB>
Source : http://buzzdev.net/read.php?40,34924,35161#msg-35161
Error 113,
task 28 55aa
Wait..
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>
After reflash you PPc and it's OK
Source : http://buzzdev.net/read.php?40,34924,35161#msg-35161
I'm having this error and when i try "set 14 0" appears
"flAbsWrite is fail.:i=1FD00,ebstart=90900000
DOC_WriteFAT0 fail: Start=3FA0000,Len=200,status=7C
HTCSF kEØ(HTCEUSB>"
Any solution?
Tks in advance
BonesC said:
I'm having this error and when i try "set 14 0" appears
"flAbsWrite is fail.:i=1FD00,ebstart=90900000
DOC_WriteFAT0 fail: Start=3FA0000,Len=200,status=7C
HTCSF kEØ(HTCEUSB>"
Any solution?
Tks in advance
Click to expand...
Click to collapse
It's possible a hardware problem
teddybear3k said:
task 28 55aa
Wait..
Read data error in tag
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>
After reflash you PPc and it's OK
Source : http://buzzdev.net/read.php?40,34924,35161#msg-35161
Click to expand...
Click to collapse
It worked for UNIVERSAL I rebooted after executing this procedure and reflashed
It worked great!!!
I got a question from you...
Are you an angel???
Man you just saved my ass!
This error 113 was freaking me out!
it took 6 hours of my time and I was getting mad.
you are the best
[REF] Guides | Tutorials | FAQs | Stickies | etc.
Included on compilation thread for future references:
http://forum.xda-developers.com/showthread.php?t=549207
Hi guys pls help in my dopod 900. I flash a wm 6.5 v12.1 by tomal 128mb,i cant open some applications and hang, when i reflash to another version ko wm6.5 v10 64mb,cant always appear erroe 112
Hey,
I got error 112. Then, I tried this methode with my HTC Universal. But when I tried to install win 6.1 on it, I alway get error 112.
Ebi
I get error 112 too
ebi11 said:
Hey,
I got error 112. Then, I tried this methode with my HTC Universal. But when I tried to install win 6.1 on it, I alway get error 112.
Ebi
Click to expand...
Click to collapse
I get error 112 too. Can someone with an HTC Universal help me out please? Maybe we can get on instant messaging and you can assist me in real time?
Searching...
Have a look here on post 2

[Q][Help] Reading and Writing performances...

Hello,
I have an HTC Desire with HTC ROM (originaly my phone is a branded orange one). The ROM works perfectly.
I would like to ask if someone succeed to fix the problem of writing performances into the internal memory.
I used J Bench Mark 1.0 to see these performances and here is the results:
1) With the Orange ROM (before changing it):
SD Card (4 Class):
Data size: 10.0(MB)
Buffer size: 2.0(KB)
Test Results:
Write Perf: 2.17(MB/s)
Read Perf: 2.51(MB/s)
Internal Memory (Internal NAND) :
Data size: 10.0(MB)
Buffer size: 2.0(KB)
Test Results:
Write Perf: 0.1(MB/s)
Read Perf: 2.42(MB/s)
2) With the HTC ROM with FROYO:
SD Card (4 Class):
Data size: 10.0(MB)
Buffer size: 2.0(KB)
Test Results:
Write Perf: 1.27(MB/s)
Read Perf: 2.07(MB/s)
Internal Memory (Internal NAND) :
Data size: 10.0(MB)
Buffer size: 2.0(KB)
Test Results:
Write Perf: 0.34(MB/s)
Read Perf: 2.13(MB/s)
The values for the "Write Perf" are not very good...
Do you have the same results?
Is it possible that this device has the same problem than the Samsung Galaxy S (I9000) one?
Do you know a possible fix of this problem?
Thanks in advance for any help on this issue.
Hello,
Noone can tell me if there is a fix about this issue like on the Samsung?
Thanks in advance.

HTC X7500 Advantage Probleem

plz.. help me.. my smartphon Not started...I tried everything but ROM- No Entry
Cmd>task 32
task 32
Level = 0
Cmd>lnbs mymac.bin 75108000
lnbs mymac.bin 75108000
Format by TrueFFS ver.: 7.1.0
:F=mymac.bin
:A=75108000
:O=00000000
:L=FFFFFFFF
start NB image download
SH
Load ADDR: 75108000 Length: 13
Programming DOC flash blocks by serial port...
Buffer=4M,0x400000
DOCInfoTableinitHW+
Binary0 Size: 0x200000
FAT0 Size: 0x5000000
FAT1 Size: 0xB00000
FAT2 Size: 0x9080000
All Size: 0xED80000
FAT0_ADDR=0x200000,FAT1_ADDR=0x5200000,FAT2_ADDR=0 x5D00000
ERROR: NO header matched
Transfer CERT error
Flash Programing Error
Please help me

FareBot: Read public transit RFID/NFC cards

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

[ROM][7.1.2][OFFICIAL] LineageOS 14.1

{
"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"
}
Official LineageOS 14.1 for Lenovo Vibe Z2 Pro
(kingdom_row/kingdomt)
Update to latest OTA-update (S288 or CN equivalent) before flashing this!​
Lin·e·age /ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Known issues
Exporting contacts from phone to SIM is broken due to the changes in Android 7.1 SIM (batch) operations. Import from SIM works fine.
What is unlikely to be added
VoLTE support (impossible without proper support in modem firmware)
Touchscreen gestures (impossible without proper support in touchscreen firmware)
Overclocking (prohibited in official distributions)
What you need to know
Report device specific bugs to me, for the rest use the LineageOS Bug Tracker.
If you're coming from an older or unofficial CM/Lineage (14.0/13.0/...) do a wipe of ART Cache, Cache & Data.
I'm not responsible for anything that happens to you or your property.
Nobody is forcing you to flash this.
No ETAs.
​
OFFICIAL Builds (weekly):
LineageOS Downloads: https://download.lineageos.org/kingdom
Changelog: https://download.lineageos.org/kingdom/changes/​
UNOFFICIAL Builds (outdated):
dd/mm/yyyy (SU/root included in all builds)
25/01/2017: https://mega.nz/#!UIw3xL5a!zdSJvdKUrYdxsqOVeL-Nu1nG5okeRsWScRgQKJpXHZc
04/01/2017: https://mega.nz/#!pEgVRAZB!2qCGtXgLMSrJ__gp3r7Z7XXfJVIE6unJFNrbfC2qaSw
25/12/2016: https://mega.nz/#!kd4lzJgZ!TPNE_tp22p_G62hlRHnSraqR5PN9xahvAIiENurMZ5s
23/11/2016: https://mega.nz/#!wNwUmRaT!ZNk_aNbWq-dgHYlOym9MkTYhVLWFv_h3eLVPyaSXerU
20/11/2016: https://mega.nz/#!UdwXUCTT!AQ-PPPHp-7lhgIAvyyJ_Tp3W7KQlcLB7nTAim4m-1u0
13/11/2016: https://mega.nz/#!lRhRQAYb!adanU8xZTjZerGbtzBk8jaBNT585zb73Su0mHQdBt-w
12/11/2016: https://mega.nz/#!JQhwRA6R!AE53FeuqFxKSS2ktpmbJ5MjW1dTACicbaY0rBhQgKIU
04/11/2016: https://mega.nz/#!sZp1zQyJ!EM4mn9cgbqoRCChmQj2AVzwBAclljRjZvOoJ3cYUbck (Disable signature verification)
30/10/2016: https://mega.nz/#!8BACFBqD!sBALhCbu2Sg4-VIkGzZEzVMt30wHxhZIC0-O7Wa2sV8
28/10/2016: https://mega.nz/#!BdgkXQrY!2_mjk_n4dDRUyHZCE7NDup3oO40TferTCclCEsUFqEQ
27/10/2016: https://mega.nz/#!tBRF2QLb!DLi_DHsUVfgKofg2-x7-VamEkdpcfcdpIbyciC2ffUQ
Builds by frantisheq: https://basketbuild.com/devs/frantisheq/kingdom_row/cyanogenmod
​
Useful links:
Google Apps: http://opengapps.org/ (use ARM 7.1)
TWRP: http://forum.xda-developers.com/android/development/recovery-team-win-recovery-project-3-0-t3454739
SU (root) addon: https://download.lineageos.org/extras (use ARM)
Official sub-reddit: https://www.reddit.com/r/LineageOS/
​
Special thanks for help and support
lockhrt999
cyprien T
mittar
northmantif
AntoSVK
leecs
iabanji1402
(if I forgot about you or you don't want to be here, send me a PM)
​
XDA:DevDB Information
LineageOS 14.1, ROM for the Lenovo Vibe Z2 Pro
Contributors
Electry, frantisheq
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-10-27
Last Updated 2017-05-09
Electry, thank you and frantisheq for your work! But could you please change the location of a build becase mega does not allow to download it due to the absence of an account?
Torch quick-tile works for me, NFC doesn't.
I noticed fishku.na 7.0 and 7.1 of the flashlight shutter does not work. .... But if the voice of google inc. Then everything works ....
Заметил фишку.на 7.0 и 7.1 фонарик из шторки не работает. ....но если голосовым из гугла вкл. Потом всё работает....
I guess the thing that won´t make me flash it right away is missing the OTA.
GREAT WORK from you guys, thank you!!!
new build up
You're awesome! It looks really great. Thank you
There´s something wrong with Wifi... can see the networks, but can´t connect. On Settings > Wifi I can turn on/off the wifi, on drag-down top bar I can´t, stays always on.
Maybe it´s just me.
time to retire i guess i have to ask everybody who wants to donate to send $ to Electry if it's possible and he agrees, not to me. as i wrote before this is mostly his work and i'm not really helping anymore, this ROM becomes "pixel perfect" thanks to him and he really deserves it
Sent from my K920 using Tapatalk
Hi electry, thank you for develop this rom for our K920! Ive tried to install it and I have the same issue that I had with CM14 a month ago, when I install it everything works except mobile network, when I enable it on the status bar it disable it automatically. I have a CN K920, could be modem compatibility problems?
Thank you
My experiences
- Speed is very good, smooth AF, no lags etc.
- Notificaion light: I can change the color and add aps, but cant set the brigthness
- Double tap to wake dont work. When i go to settings and i can turn it on, but dont work and when i go back to settings the switch is off.
- Torch tile works, NFC too
Question: It is possible that the notification light has higher priority than charging ligth? In stock rom when I was charging the phone and received a notification the ligh was pulse, as when the phone doesnt charge. (Sorry for bad einglish)
Thanks your hard work, have a good day
Do you help me to instal this amazing ROM on my k920 CN? Thanks for your help and your job.
Drug_Store said:
There´s something wrong with Wifi... can see the networks, but can´t connect
Click to expand...
Click to collapse
can confirm, is there a quick fix for wifi?
I have a problem after apply this unlock bootloader on my K920?* CN kitkat.
?*
Now I don't any partition. Specially "Preload" . It's strange all is ok with QFIL but the status bar is very quick to update the partition (roughly 10 seconds...). How can I rebuild all partion on my K920? Thanks!!!!
?*
LOG QFILE :
?*
Process Index:0
Programmer Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
Image Search Path:C:\UnlockBootloader_KK_CN
Please select the XML file
Start Download
Program Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
?*
?*?* ?* QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
?*
?*?* ?* QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Start Download
Program Path:C:\UnlockBootloader_KK_CN\prog_emmc_firehose_8974.mbn
COM Port number:4
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:4
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xA5EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x4ec
PROGRAM: Partition 0, Sector: 264232, Length: 1260 Sectors, Sector Size: 512 Bytes
File: C:\UnlockBootloader_KK_CN\emmc_appsboot.mbn
PROGRAM: Written Bytes 0x9d800 (64)
Program Size: 0.62 MB
Total Size: 0.65 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6479492MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Download Fail:FireHose Fail Fail to find QDLoader port after switch
Finish Download
[ROM][7.1] CyanogenMod 14.1
Wifi dont work
Enviado desde mi iPad con Tapatalk and LTE
flashlite, double tap and wi-fi working fine, without any fixes
Krasimir said:
flashlite, double tap and wi-fi working fine, without any fixes
Click to expand...
Click to collapse
right? It's also working fine for me.
I have no idea why wifi doesn't work for some of you.
I'll try to revert the old wifi driver back, to see if that might be the problem.
Electry said:
right? It's also working fine for me.
I have no idea why wifi doesn't work for some of you.
I'll try to revert the old wifi driver back, to see if that might be the problem.
Click to expand...
Click to collapse
Updated 10. 30. and flashlight doesnt work :S. Wiped cache and dalvik but same. Wifi fine, double tap too. The battery parcentage show in status bar, but cant change the battery icon.
With latest 30/10 build can't connect wifi
NETWORK_SELECTION_DISABLED_ASSOCIATION_REJECTION=4 NETWORK_SELECTION_DISABLED_AUTENTICATION_FAILURE=4
Display goes crazy flashing red.
EDIT: As I assumed, wifi mac address is being read from NV in a reversed order, it should start with AC:38:70 (which is Lenovo's vendor tag). Some routers reject bad mac adresses, and therefore you aren't able to connect to any of them.
This should be fixed in next build.

Categories

Resources