[Q] problem on charging - Galaxy S II Q&A, Help & Troubleshooting

[Q] problem on charging - Galaxy S II Q&A, Help & Troubleshooting

my sgs2 got an unusual charging problem usually from battery 0 to full it doesn't need 3 hours , but today its acting weird cause from 26 % to 74 % its needed 3 hours I checked dmesg.
there is nothing wrong yet at my device
<7>[ 397.116599] buf:7F 0E 00 00 0B 00 FF B6 07 01 03 FF 02 00 05 7E
<7>[ 397.117467] modemctl modemctl: svn <HOST_WUP:1
<7>[ 397.117839] modemctl modemctl: svn >SLAV_WUP:0,0
<6>[ 397.324027] ++s5pv310_enter_core0_aftr
<6>[ 397.324711] --s5pv310_enter_core0_aftr
<6>[ 397.324879] ++s5pv310_enter_core0_aftr
<6>[ 397.325641] --s5pv310_enter_core0_aftr
<7>[ 397.767855] IPC:RX size=69
<7>[ 397.768274] buf:7F 15 00 00 12 00 FF FF 08 05 03 01 02 02 01 A7
<7>[ 397.768996] buf:7F 15 00 00 12 00 FF FF 08 05 03 02 03 02 01 A7
<7>[ 397.769405] buf:7F 15 00 00 12 00 FF 00 08 03 03 02 02 02 35 31
<7>[ 397.781676] IPC:RX size=13
<7>[ 397.782084] buf:7F 0B 00 00 08 00 FF B7 08 02 02 02 7E 02 01 A7
<7>[ 397.786290] IPC:RX size=23
<7>[ 397.786697] buf:7F 15 00 00 12 00 FF B8 08 03 02 02 02 02 35 31
<7>[ 397.789535] IPC:RX size=23
<7>[ 397.790224] buf:7F 15 00 00 12 00 FF B9 08 05 02 02 03 02 01 A7
<7>[ 397.792914] IPC:RX size=23
<7>[ 397.793314] buf:7F 15 00 00 12 00 FF BA 08 05 02 01 02 02 01 A7
<7>[ 397.799541] IPC:RX size=13
<7>[ 397.799952] buf:7F 0B 00 00 08 00 FF BB 08 02 02 02 7E 02 01 A7
<7>[ 397.804287] IPC:RX size=23
<7>[ 397.804685] buf:7F 15 00 00 12 00 FF BC 08 03 02 02 02 02 35 31
<7>[ 397.809785] IPC:RX size=23
<7>[ 397.810182] buf:7F 15 00 00 12 00 FF BD 08 05 02 02 03 02 01 A7
<7>[ 397.814830] IPC:RX size=23
<7>[ 397.815536] buf:7F 15 00 00 12 00 FF BE 08 05 02 01 02 02 01 A7
<7>[ 398.000125] IPC:RX size=16
<7>[ 398.000239] buf:7F 0E 00 00 0B 00 FF BE 07 01 03 FF 01 00 05 7E
<7>[ 399.003839] usb 1-2: svn L2 p.s=1
<7>[ 399.005280] ehci_hub_control:send Port suspend
<7>[ 399.025246] modemctl modemctl: svn <HOST_WUP:0
<7>[ 399.025646] usbsvn_request_resume:run time resume
<7>[ 399.073780] usb_port_resume = 1283, 4
<7>[ 399.075139] usb 1-2: svn L0 p.s=1
<7>[ 399.075777] IPC:RX size=16
<7>[ 399.076176] buf:7F 0E 00 00 0B 00 FF BE 07 01 03 FF 02 00 05 7E
<7>[ 399.077016] modemctl modemctl: svn <HOST_WUP:1
<7>[ 399.077381] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[ 399.442575] IPC:RX size=69
<7>[ 399.442998] buf:7F 15 00 00 12 00 FF FF 08 05 03 01 02 02 01 A7
<7>[ 399.443432] buf:7F 15 00 00 12 00 FF FF 08 05 03 02 03 02 01 A7
<7>[ 399.444120] buf:7F 15 00 00 12 00 FF 00 08 03 03 02 02 02 35 31
<7>[ 399.455421] IPC:RX size=13
<7>[ 399.456121] buf:7F 0B 00 00 08 00 FF BF 08 02 02 02 7E 02 01 A7
<7>[ 399.458161] IPC:RX size=23
<7>[ 399.458567] buf:7F 15 00 00 12 00 FF C0 08 03 02 02 02 02 35 31
<7>[ 399.463724] IPC:RX size=23
<7>[ 399.464129] buf:7F 15 00 00 12 00 FF C1 08 05 02 02 03 02 01 A7
<7>[ 399.468417] IPC:RX size=23
<7>[ 399.468819] buf:7F 15 00 00 12 00 FF C2 08 05 02 01 02 02 01 A7
<7>[ 399.475792] IPC:RX size=13
<7>[ 399.476202] buf:7F 0B 00 00 08 00 FF C3 08 02 02 02 7E 02 01 A7
<7>[ 399.480537] IPC:RX size=23
<7>[ 399.481231] buf:7F 15 00 00 12 00 FF C4 08 03 02 02 02 02 35 31
<7>[ 399.485670] IPC:RX size=23
<7>[ 399.486080] buf:7F 15 00 00 12 00 FF C5 08 05 02 02 03 02 01 A7
<7>[ 399.491031] IPC:RX size=23
<7>[ 399.491431] buf:7F 15 00 00 12 00 FF C6 08 05 02 01 02 02 01 A7
<7>[ 399.820493] IPC:RX size=30
<7>[ 399.820921] buf:7F 1C 00 00 19 00 FF C6 0A 05 03 02 01 0C 01 06
<6>[ 399.918959] ++s5pv310_enter_core0_aftr
<7>[ 399.999905] IPC:RX size=16
<7>[ 400.000307] buf:7F 0E 00 00 0B 00 FF C6 07 01 03 FF 03 00 05 7E
<6>[ 400.001192] --s5pv310_enter_core0_aftr
<7>[ 401.004532] usb 1-2: svn L2 p.s=1
<7>[ 401.007570] ehci_hub_control:send Port suspend
<7>[ 401.019081] modemctl modemctl: svn <HOST_WUP:0
<7>[ 401.019448] usbsvn_request_resume:run time resume
<7>[ 401.068778] usb_port_resume = 1283, 4
<7>[ 401.070135] usb 1-2: svn L0 p.s=1
<7>[ 401.070648] IPC:RX size=16
<7>[ 401.071044] buf:7F 0E 00 00 0B 00 FF C6 07 01 03 FF 04 00 05 7E
<7>[ 401.071995] modemctl modemctl: svn <HOST_WUP:1
<7>[ 401.072360] modemctl modemctl: svn >SLAV_WUP:0,0
<7>[ 401.202361] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 401.232948] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<7>[ 401.971718] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 402.003653] usb 1-2: svn L2 p.s=1
<7>[ 402.003776] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<7>[ 402.004401] ehci_hub_control:send Port suspend
<7>[ 402.541409] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 402.572613] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 403.397918] max17042 9-0036: max17042_get_soc : soc(571e)
<6>[ 403.398277] max17042_need_soc_recal: HW(0xe)
<6>[ 403.399137] max17042 9-0036: max17042_get_soc : use raw (87), soc (89)
<6>[ 403.567545] ++s5pv310_enter_core0_aftr
<6>[ 403.653355] --s5pv310_enter_core0_aftr
<6>[ 403.739102] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<6>[ 403.763209] ++s5pv310_enter_core0_aftr
<6>[ 403.854521] --s5pv310_enter_core0_aftr
<6>[ 403.891290] ++s5pv310_enter_core0_aftr
<6>[ 403.964087] --s5pv310_enter_core0_aftr
<6>[ 404.091302] ++s5pv310_enter_core0_aftr
<6>[ 404.165489] --s5pv310_enter_core0_aftr
<6>[ 404.366730] ++s5pv310_enter_core0_aftr
<6>[ 404.456092] --s5pv310_enter_core0_aftr
<6>[ 407.255224] sec-battery sec-battery: sec_bat_check_temper: recovery count0
<6>[ 407.256365] sec-battery sec-battery: sec_bat_check_temper: temp=370, adc=2
<6>[ 407.256697] sec-battery sec-battery: sec_bat_charging_time_management: chg
<6>[ 407.257187] max8922-charger max8922-charger: max8922_is_charging: chargin3
<6>[ 407.257376] sec-battery sec-battery: soc(89), vfocv(4053), vcell(4001), t)
<7>[ 408.314285] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 408.347389] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 413.007159] ld9040 spi3.0: (id=2) brightness=189, bl=17
<7>[ 413.039806] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 413.103703] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<4>[ 413.161328] P[email protected] Total=16384bytes PrdSz=2048 #Prds=8, dmaE0
<6>[ 413.549319] max17042 9-0036: max17042_get_soc : soc(571e)
<6>[ 413.549649] max17042_need_soc_recal: HW(0xe)
<6>[ 413.549828] max17042 9-0036: max17042_get_soc : use raw (87), soc (89)
<6>[ 413.764143] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<7>[ 414.102198] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 414.144000] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<7>[ 414.869985] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 414.918696] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 415.747233] ++s5pv310_enter_core0_aftr
<6>[ 415.748859] --s5pv310_enter_core0_aftr
<6>[ 415.750217] ++s5pv310_enter_core0_aftr
<6>[ 415.751819] --s5pv310_enter_core0_aftr
<7>[ 417.025322] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 417.066182] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<4>[ 417.085535] P[email protected] Total=16384bytes PrdSz=2048 #Prds=8, dmaE0
<6>[ 417.274313] ++s5pv310_enter_core0_aftr
<6>[ 417.274691] --s5pv310_enter_core0_aftr
<7>[ 418.723426] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 418.765326] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 418.803682] ++s5pv310_enter_core0_aftr
<6>[ 418.805942] --s5pv310_enter_core0_aftr
<7>[ 419.067897] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 419.113494] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 419.780783] ++s5pv310_enter_core0_aftr
<6>[ 419.792531] --s5pv310_enter_core0_aftr
<6>[ 420.291296] ++s5pv310_enter_core0_aftr
<6>[ 420.292980] --s5pv310_enter_core0_aftr
<7>[ 420.768206] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 420.802306] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<7>[ 421.175353] tspdrv: ImmVibeSPI_ForceOut_AmpEnable (1)
<7>[ 421.207610] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<6>[ 421.494843] logger_release: took 0 msec
<6>[ 421.494921] logger_release: took 0 msec
<6>[ 421.595294] ld9040 spi3.0: (id=2) brightness=132, bl=11
<6>[ 422.892336] ++s5pv310_enter_core0_aftr
<6>[ 422.894319] --s5pv310_enter_core0_aftr
<6>[ 423.092527] ++s5pv310_enter_core0_aftr
<6>[ 423.094159] --s5pv310_enter_core0_aftr
<6>[ 423.094559] ++s5pv310_enter_core0_aftr
<6>[ 423.096415] --s5pv310_enter_core0_aftr
<6>[ 423.096810] ++s5pv310_enter_core0_aftr
<6>[ 423.098370] --s5pv310_enter_core0_aftr
<6>[ 423.179216] ++s5pv310_enter_core0_aftr
<6>[ 423.278324] --s5pv310_enter_core0_aftr
<6>[ 423.292693] ++s5pv310_enter_core0_aftr
<6>[ 423.294574] --s5pv310_enter_core0_aftr
<6>[ 423.294989] ++s5pv310_enter_core0_aftr
<6>[ 423.296564] --s5pv310_enter_core0_aftr
<6>[ 423.567244] max17042 9-0036: max17042_get_soc : soc(571e)
<6>[ 423.567401] max17042_need_soc_recal: HW(0xe)
<6>[ 423.567657] max17042 9-0036: max17042_get_soc : use raw (87), soc (89)
<6>[ 423.796036] sec-battery sec-battery: sec_bat_check_vf: Battery Health (1)
<7>[ 424.477886] tspdrv: ImmVibeSPI
[_ForceOut_AmpEnable (1)
<7>[ 424.524913] tspdrv: ImmVibeSPI_ForceOut_AmpDisable (0)
<4>[ 424.586180] P[email protected] Total=16384bytes PrdSz=2048 #Prds=8, dmaE0
<6>[ 424.902490] ++s5pv310_enter_core0_aftr
<6>[ 424.912083] --
Click to expand...
Click to collapse
p. s : if u see there is conected charger and disconected charger cause i tested on my charger

Standard SGS 2 charging time is around three hours .
jje

Related

Unable to activate wifi

Hi,
I seem to have lost the ability to activate wifi. Neither the "Comm Manager" nor the 'Wireless LAN" applications are able to turn wifi on. Also, the wifi details are not shown under the "Wireless" Today panel.
The device has been flashed quite a lot recently. I have tried reflashing the original phones roms, the v3 unlock radio rom, and the 2.05 & 2.11 HTC roms; none of these seem to have solved the problem.
Also, possibly the cause, I ran an 'erase 80000000 d80000' & 'erase 0x80100000 0x20000' (radio(?) & radio bootloader(?) from wiki.
Would reflashing the data that was deleted by the above two erases help? (in case a normal re-flash doesn't touch these areas).
I have searched through the forums and the wiki but I'm unable to find a similar problem, so if anyone has any ideas that would be appreciated.
thanks
rob-ix
WHOOPS just saw http://forum.xda-developers.com/showthread.php?t=295211 so this post my not have been required. But, I gotta read it first, so put this on hold for a few mins

Booting using Platform Builder gives the following possible answer for the problem:
20161 PID:239ceb52 TID:23862ede CertVerify: TIACXWLN.dll trust = 2
20179 PID:2375059e TID:23862ede no EEPROM no WLAN!!
I've tried, changing via HTweakC, to allow non-trusted apps to be used but this hasn't changed things.
If anyone can answer these questions or point me in the right direction to answer/fix them it would be appreciated:
1, Is the 'no EEPROM no WLAN' error being caused by 'trust = 2' on the above dll or is in fact caused by having no wlan EEPROM?
2, Is this EEPROM a real one or one simulated via the flash/NAND?
3, Can this data be re-written/flashed?
thanks
Rob-ix

rob-ix said:
1, Is the 'no EEPROM no WLAN' are being caused by 'trust = 2' on the above dll or is in fact caused by having no wlan eeprom?
Click to expand...
Click to collapse
By having EEPROM erased or corrupted.
2, Is this EEPROM a real one or one simulated via the flash/NAND?
Click to expand...
Click to collapse
I think it is inside the MSM6275 chip.
3, Can this data be re-written/flashed?
Click to expand...
Click to collapse
No that i know of.

pof said:
By having EEPROM erased or corrupted.
Click to expand...
Click to collapse
I ran these commands via the BL at one point to try to clear the radio, could these have been responsibile?
erase 80000000 d80000
erase 80100000 20000
thanks
rob-ix

not sure, let me check if i can get a dump of that...
did you actually use 'erase' from bootloader, or 'rerase' from radio bootloader?
where you successfully authenticated to the bootloader/radio bootloader when you did that?

Pof,
pof said:
not sure, let me check if i can get a dump of that...
Click to expand...
Click to collapse
Great. Then I should be able to compare the two dumps.
did you actually use 'erase' from bootloader, or 'rerase' from radio bootloader? where you successfully authenticated to the bootloader/radio bootloader when you did that?
Click to expand...
Click to collapse
I used 'erase' from the bootloader, and I believe I was authenticated at the time.
thanks
Rob

rob-ix said:
Then I should be able to compare the two dumps.
Click to expand...
Click to collapse
bootloader command 'rbmc' dumps nothing on that addreses

go into bootloader, type these commands:
Code:
task 32
task 37 ff
tell me the output of the second

task 37 ff - output
pof said:
go into bootloader, type these commands:
Code:
task 32
task 37 ff
tell me the output of the second
Click to expand...
Click to collapse
Please see attached.
thanks
Rob

Seems that you have erased the EEPROM:
Code:
03/24/2007 23:53:25 [K :: KERNEL] HTC Nand Read!
03/24/2007 23:53:25 [K :: KERNEL] Kernel: EEPROM signature=FF FF FF FF FF
03/24/2007 23:53:25 [K :: KERNEL] HTC Nand Read!
03/24/2007 23:53:25 [K :: KERNEL] Kernel: EEPROM signature Old=FF FF FF FF FF
[...]
CertVerify: TIACXWLN.dll trust = 2
no EEPROM no WLAN!!
On a normal hermes this looks like this:
Code:
05/01/2006 00:00:00 [K :: KERNEL] HTC Nand Read!
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM signature=50 12 EE 0 2
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM1 Checksum=0xbd4ccc54
05/01/2006 00:00:00 [K :: KERNEL] HTC Nand Read!
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM signature Old=50 12 EE 0 2
05/01/2006 00:00:00 [K :: KERNEL] Kernel: EEPROM2 Checksum=0xbd4ccc54
If I find anything for you to try I'll let you know.

Pof,
pof said:
Seems that you have erased the EEPROM:
Click to expand...
Click to collapse
That makes sense. Do you know if it's a real EEPROM or just some flash pretending to be EEPROM? Would GNU Haret be able to dump/reload the information?
thanks
Rob

would HTC have to replace the entire mainboard for this to be fixed, or do they have a tool that could reflash the EEPROM with a new mac adress and such

In theory, should be possible to reflash via bootloader EMAPI commands, but we don't know how to use them, sure HTC knows... but in service centre they most probably will replace the mainboard for that.

pof said:
In theory, should be possible to reflash via bootloader EMAPI commands, but we don't know how to use them, sure HTC knows... but in service centre they most probably will replace the mainboard for that.
Click to expand...
Click to collapse
... thats not good, how much do you think that would cost? over $300?

is there anyway to emulate the EEPROM or put the MAC address in the registry?

task 37 ff output
Output of task 37 ff scrolls way too much overflowing the screen buffer. I don't see a log option in the mtty I downloaded from wiki pages. What's the method to capture large output like that?
TIA

@cjchriscj: no
@aarman: type "task 37 ff" and pull out the USB cable before the buffer grows too big.

Is it possible that people having this problem have flashed _too big_ a OS.nb file using MFG bootloader before having the problem?
I have the feeling that WLAN EEPROM is read from NAND flash, if we manage to find the right offset we can probably rbmc to read it and reflash it with lnb.

I have the same problem
05/23/2006 23:57:46 [K :: KERNEL] HTC Nand Read!
05/23/2006 23:57:46 [K :: KERNEL] Kernel: EEPROM signature=FF FF FF FF FF
05/23/2006 23:57:46 [K :: KERNEL] HTC Nand Read!
05/23/2006 23:57:46 [K :: KERNEL] Kernel: EEPROM signature Old=FF FF FF FF FF
05/23/2006 23:57:46 [K :: KERNEL]
If i understand that pof say for resolve my probleme i need the lnb wifi ?
The offset is not 0xb6d00000 0x20000000 ?

working on it
ok, good news for those who have ****ed up wlan EEPROM...
I was able to rbmc the right place where the WLAN eeprom is stored, as a proof of concept:
This is my MAC address: 00:09:2d:f1:f2:d3
This is the EEPROM signature reported by "task 32 ff": 50 12 EE 0 2
Code:
[B][COLOR="DarkGreen"]50 12 EE 00 02[/COLOR][/B] 00 00 00 06 00 00 00 A1 01 00 00 P.î.........¡...
43 50 AA 80 00 00 00 00 00 00 00 00 00 00 00 00 CPª?............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
02 11 56 05 1B 06 00 11 31 01 00 01 09 56 12 00 ..V.....1....V..
00 00 01 0D 56 71 00 00 00 02 6D 54 [B][COLOR="DarkRed"]D3 F2 F1 2D[/COLOR][/B] ....Vq..........
[B][COLOR="DarkRed"]09 00[/COLOR][/B] 00 00 01 05 5A 64 00 00 00 01 09 5A 00 00 ......Zd.....Z..
00 00 01 0D 5A 00 00 00 00 01 01 0C 03 00 00 00 ....Z...........
01 01 5A 00 00 00 00 01 55 09 01 00 00 00 01 E5 ..Z.....U......å
58 02 00 00 00 01 F1 58 08 00 00 00 01 D5 58 10 X.....ñX.....ÕX.
00 00 00 01 B1 58 04 00 00 00 00 00 00 00 00 00 ....±X..........
00 0C 00 8B 00 C6 00 D0 00 DC 00 EE 00 0C 01 15 ...?.Æ.Ð.Ü.î....
01 17 01 2D 01 67 01 77 01 7F 01 01 39 00 00 11 ...-.g.w...9...
00 04 01 01 01 00 05 01 06 00 02 01 02 01 02 1E ................
00 0A 00 02 05 02 04 11 22 44 03 06 41 20 30 31 ........"D..A 01
32 40 04 09 54 49 20 41 43 58 31 30 30 05 07 54 [email protected] ACX100..T
49 20 54 65 73 74 01 08 00 00 00 00 00 00 00 00 I Test..........
05 02 00 00 3B 00 81 00 C5 00 1F 01 04 04 44 10 ....;..Å.....D.
00 00 45 10 00 00 18 5A 40 00 14 5A 20 00 02 0E [email protected] ...
A0 01 F7 00 08 01 7E 02 78 00 B2 01 8A 09 80 00 .÷...~.x.².?.?.
F7 00 08 01 79 02 78 00 A4 01 8A 09 01 07 00 01 ÷...y.x.¤.?.....
40 00 00 00 01 00 00 05 04 00 01 01 00 00 00 00 @...............
FF FF FF FF FD FD FD FD FB FB FB FB FB 0E 04 09 ÿÿÿÿýýýýûûûûû...
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 ................
09 09 09 09 09 09 09 0E 01 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 03 02 D4 08 D4 08 07 00 01 .........Ô.Ô....
This is on NAND, around offset 0x500CD800 (after SPL and before MainSplash).
Probably this can be overwriten with 'lnb' command on MFG bootloader, i'm investigating this with Olipro right now.
If anyone wants to serve as a guinea pig, let us know

[DEV] Driver for analogue video grabber USB sticks

beside my DVB-T stick, which is working very well with chulri's DVB-T drivers I have also an analogue frame grabber USB stick like the "Terratec Grabby" flying around.
I think it would be a nice feature, when the A101IT could also handle analogue video sources additional to DVB-sticks.
Those devices, along with some DVB-T sticks like are controlled with the em28xx kernel module.
The common chipset of those sticks includes USB-Bridge Empia EM2860, Philips SAA7113 (video decoder), EMP202 (AC'97 audio processor).
More information:
http://www.linuxtv.org/wiki/index.php/Em28xx_devices
Maybe later, this driver could be backmerged into chulri's DVB-T package.
Actual status:
I was able to compile the 2.6.29 based em28xx (along with dependent modules e.g. saa7115, em28xx-alsa, etc...) and load the kernel module on A101IT.
I did also a few minor modifactions, so that the Magix frame grabber stick with usbid 1b80:e34b is recognized correctly. (source files attached in em28xx_src.zip)
dmesg:
Code:
em28xx 2-1:1.0: usb_probe_interface
em28xx 2-1:1.0: usb_probe_interface - got id
em28xx: New device USB 2863 Device @ 480 Mbps (1b80:e34b, interface 0, class 0)
em28xx #0: Identified as Magix Videograbber (card=77)
em28xx #0: chip ID is em2860
saa7115' 4-0025: saa7113 found (1f7113d0e100000) @ 0x4a (em28xx #0)
em28xx #0: i2c eeprom 00: 1a eb 67 95 80 1b 4b e3 50 00 20 03 6a 20 00 00
em28xx #0: i2c eeprom 10: 00 00 04 57 06 02 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 20: 02 00 01 00 f0 00 01 00 00 00 00 00 5b 00 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 02 01 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 20 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 36 00 33 00 20 00 44 00
em28xx #0: i2c eeprom 80: 65 00 76 00 69 00 63 00 65 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x979a2140
em28xx #0: EEPROM info:
em28xx #0: AC97 audio (5 sample rates)
em28xx #0: 500mA max power
em28xx #0: Table at 0x04, strings=0x206a, 0x0000, 0x0000
em28xx #0: Registering snapshot button...
input: em28xx snapshot button as /devices/platform/musb_hdrc/usb2/2-1/input/input16
em28xx #0: Config register raw data: 0x50
em28xx #0: AC97 vendor ID = 0x83847650
em28xx #0: AC97 features = 0x6a90
em28xx #0: Empia 202 AC97 audio processor detected
em28xx #0: v4l2 driver version 0.1.1
em28xx #0: V4L2 device registered as /dev/video3 and /dev/vbi0
em28xx-audio.c: probing for em28x1 non standard usbaudio
em28xx-audio.c: Copyright (C) :eek:2006 Markus Rechberger
When I try now to do cat /dev/video3 > test.ts, then a memory allocation error occured:
Code:
cat: page allocation failure. order:5, mode:0x0
[<c03518f0>] (dump_stack+0x0/0x14) from [<c00bbb5c>] (__alloc_pages_internal+0x3c0/0x3e8)
[<c00bb79c>] (__alloc_pages_internal+0x0/0x3e8) from [<c00471a4>] (__dma_alloc+0x154/0x408)
[<c0047050>] (__dma_alloc+0x0/0x408) from [<c00474e4>] (dma_alloc_coherent+0x58/0x64)
[<c004748c>] (dma_alloc_coherent+0x0/0x64) from [<c0248db8>] (hcd_buffer_alloc+0x8c/0x94)
r7:00000004 r6:c1dd1f00 r5:c9bf4000 r4:00000800
[<c0248d2c>] (hcd_buffer_alloc+0x0/0x94) from [<c023b8b4>] (usb_buffer_alloc+0x24/0x30)
r5:c9bf4000 r4:c81aa800
[<c023b890>] (usb_buffer_alloc+0x0/0x30) from [<bf348768>] (em28xx_init_isoc+0x124/0x2dc [em28xx])
[<bf348644>] (em28xx_init_isoc+0x0/0x2dc [em28xx]) from [<bf344834>] (buffer_prepare+0xe8/0xf8 [em28xx])
[<bf34474c>] (buffer_prepare+0x0/0xf8 [em28xx]) from [<c0221dd0>] (__videobuf_read_start+0xbc/0x174)
r7:00000001 r6:ca248c8c r5:ca248c90 r4:ca248c8c
[<c0221d14>] (__videobuf_read_start+0x0/0x174) from [<c0222028>] (videobuf_read_stream+0x90/0x248)
r8:00000000 r7:00001000 r6:00001000 r5:ca601d40 r4:ca248c8c
[<c0221f98>] (videobuf_read_stream+0x0/0x248) from [<bf3453ac>] (em28xx_v4l2_read+0xc0/0xd0 [em28xx])
[<bf3452ec>] (em28xx_v4l2_read+0x0/0xd0 [em28xx]) from [<c0216a94>] (v4l2_read+0x50/0x58)
[<c0216a44>] (v4l2_read+0x0/0x58) from [<c00df654>] (vfs_read+0xb4/0x144)
r5:ca601d40 r4:00001000
[<c00df5a0>] (vfs_read+0x0/0x144) from [<c00df7a8>] (sys_read+0x44/0x70)
r7:00000000 r6:00000000 r5:becc6ae8 r4:ca601d40
[<c00df764>] (sys_read+0x0/0x70) from [<c0040e80>] (ret_fast_syscall+0x0/0x2c)
r8:c0041028 r7:00000003 r6:becc6ae8 r5:00001000 r4:40092450
Mem-info:
Normal per-cpu:
CPU 0: hi: 90, btch: 15 usd: 85
Active_anon:9544 active_file:3850 inactive_anon:9574
inactive_file:11687 unevictable:0 dirty:6 writeback:0 unstable:0
free:7421 slab:2380 mapped:12278 pagetables:1318 bounce:0
Normal free:29684kB min:2036kB low:2544kB high:3052kB active_anon:38176kB inactive_anon:38296kB active_file:15400kB inactive_file:46748kB unevictable:0kB present:260096kB pages_scanned:33 all_unreclaimable? no
lowmem_reserve[]: 0 0
Normal: 7185*4kB 44*8kB 23*16kB 7*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 29684kB
15757 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
655[CODE]
36 pages of RAM
7910 free pages
10335 reserved pages
2380 slab pages
59244 pages shared
0 pages swap cached
unable to allocate 115680 bytes for transfer buffer 4[/CODE]
Instructions to load the driver:
1. Install chulri's DVB-T package:
http://code.google.com/p/archos-gen8-dvb/downloads/list?q=label:Featured
2. Read the Howto:
http://code.google.com/p/archos-gen8-dvb/wiki/HowToTest
3. Copy the content of the attached em28xx_mod.zip into the mod/ directory
4. sh loadmod mod/em28xx.ko
5. cat /dev/video3 > test.ts
Does someone have an idea, what could be be the cause for this memory allocation problem ? (maybe RAM shortage on the A101?)
Suggestions, comments and general support, to get this driver working are very welcome !
Best regards,
Onliner09

Thank you very much for this thread
I have an analogue frame grabber USB stick and need to use it with my Archos 101 too.
dmesg result:
...
usb 2-1: New USB device found, idVendor=07ca, idProduct=1827
usb 2-1: Product: AVerTV
usb 2-1: Manufacture: AVerMedia
usb 2-1: SerialNumber: 301306400071
...
usbid = 07ca:1827
Click to expand...
Click to collapse
I wish you can find the solutions to fix this problem and then I will join to test with you.

usb ethernet driver truncate data?

I am trying to connect my phone to a device with the phone acting as the host (using the OTG USB cable).
Once connected, I have new entry "usb0" when I do ifconfig.
I assigned 192.168.3.100 to the phone and 192.168.3.99 to the device.
When I do a tcpdump, I saw that the arp request from the phone got to the device correctly, the device answered corrected but by the time it gets to the phone, it is no longer correct. I suspect that this is the problem within the u_ether driver/gadget.
When the device reply to the ARP request, tcpdump on the device gives:
2 0.000091 5a:65:6b:1b:de:37 62:18:d4:57:77:6c ARP 42 192.168.3.99 is at 5a:65:6b:1b:de:37
Frame 2: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: 5a:65:6b:1b:de:37 (5a:65:6b:1b:de:37), Dst: 62:18:d4:57:77:6c (62:18:d4:57:77:6c)
0000 62 18 d4 57 77 6c 5a 65 6b 1b de 37 08 06 00 01 b..WwlZe k..7....
0010 08 00 06 04 00 02 5a 65 6b 1b de 37 c0 a8 03 63 ......Ze k..7...c
0020 62 18 d4 57 77 6c c0 a8 03 64 b..Wwl.. .d
Which is correct. However, tcpdump on the phone gives:
2 0.000030 CatenaNe_65:6b:1b AvlabTec_00:06:04 0xde37 28 Ethernet II
Frame 2: 28 bytes on wire (224 bits), 28 bytes captured (224 bits)
Ethernet II, Src: CatenaNe_65:6b:1b (00:02:5a:65:6b:1b), Dst: AvlabTec_00:06:04 (00:01:08:00:06:04)
0000 00 01 08 00 06 04 00 02 5a 65 6b 1b de 37 c0 a8 ........ Zek..7..
0010 03 63 62 18 d4 57 77 6c c0 a8 03 64 .cb..Wwl ...d
From the look of it, the section "62 18 d4 57 77 6c 5a 65 6b 1b de 37 08 06" is missing from the frame.
I suspected that I have to make changes to "drivers/usb/gadget/u_ether.c" and/or "drivers/net/usb/cdc_ether.c" but I am not so sure. Do you know where is the good place to start tackling this problem? I tried to put printk statements everywhere in those files but it proved fruitless.
I have tried to do "ethernet over usb" with a Windows machine (RNDIS) and that worked properly.
Thank you.

bug in usbnet driver
The problem I found out was that there were two consecutive calls to "remove header" in the driver.

[ROM][Hybrid][8.24.12]Paranoid-Android v1.0 ~TeamNightmare~

{
"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"
}
This is an ongoing developer project to make way for a modification that will entirely transform your device, but retain the aesthetics and the experience of your phone. I know you've seen tablet mode roms before, they change two lines in your build.prop file which you could easily edit yourself in seconds and maybe throw a keyboard in there to make it work better. It's a start, but this ain't enough. This thing has potential, but it is wasted the moment you try to stuff a full blown tablet into your poor phone. Yet we all know our high res phones can very well handle more than silly 1-column layouts. So the magic must be in between somewhere, a place that Google must have overlooked and left blank. Yes, this rom strives to drop your device into tablet mode, but it won't stop there, it will reshape and redefine ICS to make it all a useful addition and not just a cute novelty. we're calling it: Hybrid Mode, best of both worlds.
Click to expand...
Click to collapse
-Download (in changelog)
- Wipe /system, /cache, and ,data
- Flash
- Reboot
- Enjoy! $$$
Click to expand...
Click to collapse
- Set the font size to 'Large'
- Go into the navigation bar settings, hold your phone in landscape, change the button quantity to 5, then back to 3. (Buttons shouldn't be crammed together anymore).
- Check "Auto Hide" in Settings, System, Statusbar, to finally get Fullscreen (or Hold power button, and press "Toggle StatusBar")
- Launcher Settings: margins: SMALL (If youre using Apex / Nova), show permanent searchbar: YES, Grid: 5x4, resize all widgets: YES, Wallpaper scrolling: OFF
Click to expand...
Click to collapse
- Same as cm9...
- "About Phone" force closes
Click to expand...
Click to collapse
Code:
v1.0- [URL="http://d-h.st/YsI"]Download[/URL]
[LIST]
[*]First Build!
[/LIST]
- CM9 Team, for their code.
- ParanoidAndroid team for the tweaks and Hybrid mode.
- The TeamNightmare team
- Anyone who I've missed, please pm me.
Click to expand...
Click to collapse

oh boy, another task set for me this weekend! thanks!

Screenshots plz!

S1D3winder016 said:
Screenshots plz!
Click to expand...
Click to collapse
getting there lol

ziggy46 said:
getting there lol
Click to expand...
Click to collapse
K thanks! Is this Sense, AOSP, etc.?
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Wow, this looks like a tablet!

lol my friend just showed me this rom on his s3. decided to check our(amaze) dev section. boom here it is XD

S1D3winder016 said:
K thanks! Is this Sense, AOSP, etc.?
Click to expand...
Click to collapse
this is an aosp rom, but different. its similar to cm9 but with tablet mode and hybrid mode.

xilande said:
lol my friend just showed me this rom on his s3. decided to check our(amaze) dev section. boom here it is XD
Click to expand...
Click to collapse
how convenient lol

Check it out in a bit, gotta make a backup of my current ROM! I've notice there has been a lot of new stuff recently! I like it! Keep up the great work!

Link is up!

EDIT: nvm, i found my answer

theinitial21 said:
I'm assuming everything works such as, data and gps? because you dont have a known issue section.
Click to expand...
Click to collapse
data should work. (just like speedrom cm9)

Oh boy! The thought of not changing my build prop DPI has me drooling. I may give this a shot over the weekend, thanks!

Ziggy your AWESOME! I'm excited for this one!

ziggy46 said:
data should work. (just like speedrom cm9)
Click to expand...
Click to collapse
data is still broken, it comes off and on even if i conttect directly to my carriers proxy

crazysohc said:
data is still broken, it comes off and on even if i conttect directly to my carriers proxy
Click to expand...
Click to collapse
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.

ziggy46 said:
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.
Click to expand...
Click to collapse
yea bro just give me a few minutes as i just started restoring my backup, so ill flash it again and get you the log cat as soon as i can
---------- Post added at 05:46 PM ---------- Previous post was at 05:23 PM ----------
D/QC-QMI ( 166): 01 11 00 00 03 01 00 FC 00 20 00 05 00 10 02 00
D/QC-QMI ( 166): 3F 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 47 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [47]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_GET_SIGNAL_STRENGTH(0x20)]; MSG TX ID: [252]; CTL: [Response]
D/QC-QMI ( 166): 01 2E 00 80 03 01 02 FC 00 20 00 22 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00 01 02 00 9C 05 11 04 00 01 00 64 05
D/QC-QMI ( 166): 12 04 00 01 00 15 05 15 05 00 01 00 FF 00 05
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=81
D/QC-QMI ( 156): qmi_client 9c: Received 81 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 32
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_fetch_signal_strength_observati
ons: qcril_qmi_nas_request_signal_strength entered IF UTIL_RES = SUCCESS 127
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 47 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 47 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 13 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [13]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
<unknow NAS message id>(0x4f)]; MSG TX ID: [253]; CTL: [Request]
D/QC-QMI ( 166): 01 0C 00 00 03 01 00 FD 00 4F 00 00 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 26 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [26]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
<unknow NAS message id>(0x4f)]; MSG TX ID: [253]; CTL: [Response]
D/QC-QMI ( 166): 01 19 00 80 03 01 02 FD 00 4F 00 0D 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00 13 03 00 64 15 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=60
D/QC-QMI ( 156): qmi_client 9c: Received 60 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 79
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_fetch_signal_strength_observati
ons: qcril_qmi_nas_fetch_signal_strength_observations completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: .. subfetch sig strength info 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: qcri
l_qmi_nas_dump_sign_strength_report entered
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..GW
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. s
ignalStrength 7, bitErrorRate 255
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..CD
MA
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm -1, ecio -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..EV
DO
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm -1, ecio -1, signalNoiseRatio -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..AT
T
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. d
bm 100, ecno 21
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: ..LT
E
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: .. s
ignalStrength 99, rsrp -1, rsrq -1, snr: -1
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_dump_sign_strength_report: qcri
l_qmi_nas_dump_sign_strength_report completed
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: .. conf res 0
D/RILC ( 156): qmi_ril(0/156): qcril_send_unsol_response: UI <--- RIL_UNSOL_
SIGNAL_STRENGTH (1009) --- RIL [RID 0, Len 56, (null)]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_propagate_known_signal_strength
_ind: qcril_qmi_nas_propagate_known_signal_strength_ind completed 0
I/RILC ( 156): qmi_ril(0/156): qcril_process_event: Exit qcril_process_event
() : <Unknown event> ?, err_no 0
D/RILC ( 156): qmi_ril(0/156): qcril_event_main: qcril_event_main(): Waiting
...
D/RILJ ( 775): [0245]> SCREEN_STATE: false
D/RILC ( 156): qmi_ril(0/156): onRequest: UI --- RIL_REQUEST_SCREEN_STATE (6
1) ---> RIL [RID 0, token id 245, data len 4]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: qcril_qmi
_nas_request_screen_state entered
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: q
cril_qmi_extend_print_power_statistics_9k entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 47 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 47 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 13 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [13]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x9)]; MSG TX ID: [55]; CTL: [Request]
D/QC-QMI ( 166): 01 0C 00 00 E4 01 00 37 00 09 00 00 00
D/GSM ( 775): [GsmDCT] onReceive: action=android.intent.action.SCREEN_OFF
D/GSM ( 775): [GsmDCT] stopNetStatPoll
D/GSM ( 775): [GsmDCT] overall state is CONNECTING
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 316 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [316]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x9)]; MSG TX ID: [55]; CTL: [Response]
D/QC-QMI ( 166): 01 3B 01 80 E4 01 02 37 00 09 00 2F 01 02 04 00
D/QC-QMI ( 166): 00 00 00 00 20 04 00 38 00 00 00 1F 04 00 C5 01
D/QC-QMI ( 166): 00 00 1E 04 00 62 04 00 00 1D 04 00 DC 82 0A 00
D/QC-QMI ( 166): 1C 04 00 56 02 00 00 1B 04 00 DB 22 00 00 1A 18
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 00 26 1A 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 19 70 00 1E 01 00 00
D/QC-QMI ( 166): 00 00 00 00 12 27 00 00 00 00 00 00 00 00 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 4E 44 01 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 03 23 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 5B 7A 01 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 F5 30 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 2E 09 00 00
D/QC-QMI ( 166): 00 00 00 00 00 00 00 00 00 00 00 00 18 08 00 6A
D/QC-QMI ( 166): 23 02 00 00 00 00 00 17 04 00 B7 41 00 00 16 04
D/QC-QMI ( 166): 00 20 00 00 00 15 04 00 62 0F 00 00 14 04 00 40
D/QC-QMI ( 166): 9A 0A 00 13 04 00 5F 02 00 00 12 04 00 8D 07 02
D/QC-QMI ( 166): 00 11 38 00 F3 00 00 00 91 05 00 00 00 00 00 00
D/QC-QMI ( 166): 00 00 00 00 A2 95 01 00 00 00 00 00 54 33 00 00
D/QC-QMI ( 166): 00 00 00 00 07 AF 01 00 00 00 00 00 71 2C 00 00
D/QC-QMI ( 166): 00 00 00 00 AC 08 00 00 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=350
D/QC-QMI ( 156): qmi_client 9c: Received 350 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 9
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_clients=243,1425,0,0,103842,0,13140,0,110343,0,11377,0,2220,0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_try_PC=133005
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]Q6_PC_cnt=607,694848
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_clients=0,0,0,6694,0,0
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_try_XO=8923
D/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: [
PM]ARM9_XO_cnt=598,688860
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_extend_print_power_statistics_9k: q
cril_qmi_extend_print_power_statistics_9k complete, result=0, error=0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_display_status:
qcril_qmi_ssdsrv_request_set_display_status entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x0)]; MSG TX ID: [56]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 38 00 00 00 04 00 01 01 00
D/QC-QMI ( 166): 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x0)]; MSG TX ID: [56]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 38 00 00 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_display_status:
qcril_qmi_ssdsrv_request_set_display_status completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications, param 0
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 91 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 91 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 57 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [57]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_SET_EVENT_REPORT(0x2)]; MSG TX ID: [254]; CTL: [Request]
D/QC-QMI ( 166): 01 38 00 00 03 01 00 FE 00 02 00 2C 00 10 04 00
D/QC-QMI ( 166): 00 02 FF 00 11 01 00 00 12 01 00 00 13 02 00 00
D/QC-QMI ( 166): 05 14 02 00 00 04 15 02 00 00 01 16 02 00 00 03
D/QC-QMI ( 166): 17 01 00 00 18 02 00 00 02
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_SET_EVENT_REPORT(0x2)]; MSG TX ID: [254]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 03 01 02 FE 00 02 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 2
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications requested nas event report 0, 0
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 67 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 67 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 33 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [33]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_INDICATION_REGISTER(0x3)]; MSG TX ID: [255]; CTL: [Request]
D/QC-QMI ( 166): 01 20 00 00 03 01 00 FF 00 03 00 14 00 10 01 00
D/QC-QMI ( 166): 00 13 01 00 00 14 01 00 00 17 01 00 01 18 01 00
D/QC-QMI ( 166): 00
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_NAS_SERVICE(0x3)]; MSG QMI MSG TYPE: [
QMI_NAS_INDICATION_REGISTER(0x3)]; MSG TX ID: [255]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 03 01 02 FF 00 03 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 3
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications requested nas indication reports 0
, 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_enable_networking_indications:
qcril_qmi_util_enable_networking_indications completed with 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: Enable Ga
rbage Filter
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_gf_timer: qcril_
qmi_ssdsrv_request_set_gf_timer entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x5)]; MSG TX ID: [57]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 39 00 05 00 04 00 01 01 00
D/QC-QMI ( 166): 02
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x5)]; MSG TX ID: [57]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 39 00 05 00 07 00 02 04 00
D/QC-QMI ( 166): 01 00 1A 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 5
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_gf_timer: qcril_
qmi_ssdsrv_request_set_gf_timer completed 0, 0
I/RILC ( 156): qmi_ril(0/156): fd_ballots: AP 0 votes to enable fast dormanc
y!
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_fast_dormancy_en
able: qcril_qmi_ssdsrv_request_set_fast_dormancy_enable entered
D/QC-QMI ( 156): Setting the api flag to : 1
D/QC-QMI ( 156): qmi_client 9c: sending 51 bytes on fd = 21
D/QC-QMI ( 166): qmuxd: RX 51 bytes on fd=20 from qmux_client_id=9c
D/QC-QMI ( 166): qmi_qmux: TX/RX - TX 17 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [17]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x2)]; MSG TX ID: [58]; CTL: [Request]
D/QC-QMI ( 166): 01 10 00 00 E4 01 00 3A 00 02 00 04 00 01 01 00
D/QC-QMI ( 166): 01
D/QC-QMI ( 166): qmi_qmux: TX/RX - RX 20 bytes on conn_id=8
D/QC-QMI ( 166): MSG Length: [20]
D/QC-QMI ( 166): MSG Service Type: [QMI_SSDSRV_SERVICE(0xe4)]; MSG QMI MSG TYP
E: [<unknow message id>(0x2)]; MSG TX ID: [58]; CTL: [Response]
D/QC-QMI ( 166): 01 13 00 80 E4 01 02 3A 00 02 00 07 00 02 04 00
D/QC-QMI ( 166): 00 00 00 00
D/QC-QMI ( 166): qmuxd: TX message on fd=20, to clientID = 9c, len=54
D/QC-QMI ( 156): qmi_client 9c: Received 54 bytes on fd = 21
D/QC-QMI ( 156): API Flag .............. 1
D/QC-QMI ( 156): Message ID ............... 2
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_util_convert_qmi_response_codes_to_
ril_result_ex: qcril_qmi_util_convert_qmi_response_codes_to_ril_result_ex ctx ch
eck 0
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_ssdsrv_request_set_fast_dormancy_en
able: qcril_qmi_ssdsrv_request_set_fast_dormancy_enable completed 0, 0
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: >>>>>
> LOCK QCRIL_DATA MUTEX 403308ac
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: LOCK
QCRIL_DATA MUTEX 403308ac result=0
D/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: Switc
h ON/OFF dormancy indications on all active interfaces
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: <<<<<
< UNLOCK QCRIL_DATA MUTEX 403308ac
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: UNLOC
K QCRIL_DATA MUTEX 403308ac result=0
I/RILC ( 156): qmi_ril(0/156): qcril_data_toggle_dormancy_indications: qcril
_data_toggle_dormancy_indications: EXIT with SUCCESS
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: .. data d
ormancy req 1, 0
I/RILC ( 156): qmi_ril(0/156): qcril_reqlist_find: [RID 0] Not found ReqList
entry : token id 245
D/RILC ( 156): qmi_ril(0/156): qcril_send_request_response: UI <--- RIL_REQU
EST_SCREEN_STATE (61) Complete --- RIL [RID 0, Token 245, Success, Len 0 ]
I/RILC ( 156): qmi_ril(0/156): qcril_qmi_nas_request_screen_state: qcril_qmi
_nas_request_screen_state complete with 0
D/RILJ ( 775): [0245]< SCREEN_STATE
sorry for it being so long
---------- Post added at 06:15 PM ---------- Previous post was at 05:46 PM ----------
ziggy46 said:
can you get me a logcat of the radio?
adb logcat -b radio > log.txt
or
adb logcat -b radio
also, this is a KANG from the sensation. therefore data may not work until someone here can build it from source. but we'll try to get it working.
Click to expand...
Click to collapse
let me know if you need another log

here is the rest i think

crazysohc said:
here is the rest i think
Click to expand...
Click to collapse
did you try going into the settings and manually selecting the apn like people had to do on speedrom? i honestly dont see anything wrong in that logcat

ziggy46 said:
did you try going into the settings and manually selecting the apn like people had to do on speedrom? i honestly dont see anything wrong in that logcat
Click to expand...
Click to collapse
yes i did all that i even added proxy port direct to t-mobile and still no data for me :/
---------- Post added at 07:23 PM ---------- Previous post was at 07:08 PM ----------
all i see in the log text is edge:2 css not supported
and with hsdpa

[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?

Better Mobile App

welcome