I think tsens_interrupt is for thermals. Maybe someone knows the correct one. I'm trying to increase touch sensitivity by modifying CPU affinity.
Code:
[email protected]:/ # cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
1: 78 5 0 0 0 0 wcd9xxx SLIMBUS Slave
3: 0 0 0 0 0 0 wcd9xxx HPH_L OCP detect
4: 0 0 0 0 0 0 wcd9xxx HPH_R OCP detect
6: 0 0 0 0 0 0 qpnp-int wdog-timeout
10: 0 0 0 0 0 0 qpnp-int dcin-uv
15: 22 14 14 9 0 0 qpnp-int usbin-src-det
20: 459950702 52016823 98592578 96452819 7181524 5207383 GIC arch_timer
23: 0 0 0 0 0 0 GIC ARM64 Single-Bit Error PMU IRQ
35: 0 0 0 0 0 0 GIC apps_wdog_bark
39: 120443316 21473301 40468945 40344746 3978543 2659359 GIC arch_mem_timer
47: 2474 7236 7201 7344 0 0 GIC cpr
51: 14740 89 801 0 0 0 GIC cpr
56: 0 0 0 0 0 0 GIC modem
57: 76833 274290 129569 116190 0 0 GIC qcom,smd-modem
58: 6 0 0 0 0 0 GIC qcom,smsm-modem
59: 5 0 8 0 0 0 GIC smp2p
61: 33146 994 875 10798 0 0 GIC
65: 2968112 173213 187968 109072 0 0 GIC kgsl-3d0
73: 0 0 0 0 0 0 GIC msm_iommu_global_cfg_irq
75: 0 0 0 0 0 0 GIC msm_iommu_global_cfg_irq
76: 414931 0 346 101591 0 0 GIC msm_vidc
81: 6841 1609 1125 0 0 0 GIC
82: 2264 463 190 0 0 0 GIC cci
83: 23 0 0 2 0 0 GIC csid
84: 5 0 0 0 0 0 GIC csid
85: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
86: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
87: 7079 1544 1008 0 0 0 GIC
89: 4 0 0 0 0 0 GIC
90: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
92: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
93: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
104: 2599468 171363 66068 84312 0 0 GIC MDSS
108: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
109: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
110: 0 0 1 0 0 0 GIC csiphy
111: 0 0 0 0 0 0 GIC csiphy
112: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
126: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
128: 0 0 0 0 0 0 GIC i2c-msm-v2-irq
130: 405 10 0 52 0 0 GIC i2c-msm-v2-irq
133: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
134: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
137: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
138: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
140: 1 0 0 0 0 0 GIC
141: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
142: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
143: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
144: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
145: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
146: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
147: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
148: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
149: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
150: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
151: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
152: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
155: 1290537 643414 357878 521582 0 0 GIC mmc0
157: 186472 0 0 0 0 0 GIC mmc1
166: 2361 70 0 117 0 0 GIC msm_otg, msm_hsusb
167: 0 0 0 0 0 0 GIC sps
170: 28219 8260 6380 2428 0 0 GIC 7824900.sdhci
172: 0 0 0 0 0 0 GIC msm_otg
174: 1473 701 70 140 0 0 GIC qcom,smd-wcnss
175: 0 0 0 5 0 0 GIC smp2p
176: 0 0 0 0 0 0 GIC qcom,smsm-wcnss
178: 0 0 0 0 0 0 GIC wcnss_wlan
181: 0 0 0 0 0 0 GIC wcnss
185: 0 0 0 0 0 0 GIC csid
195: 19865 0 0 568 0 0 GIC ngd_slim_irq
200: 7928199 478788 271455 61370 1355 707 GIC qcom,smd-rpm
203: 977386 35805 15878 10199 81 53 GIC 601d0.qcom,mpm
212: 5105 209 0 0 0 0 GIC sps
216: 3273 0 0 0 0 0 GIC tsens_interrupt
222: 35786 153403 72764 64622 0 0 GIC 200f000.qcom,spmi
224: 16928 12 1479 23 0 0 GIC spdm_bw_hyp
240: 1066143 85917 31754 16613 0 0 GIC 1000000.pinctrl
253: 28688 0 0 0 0 0 GIC 7864900.sdhci
260: 24592 10794 9771 13617 6894 76 GIC ipa
262: 540316 1278583 4741987 5174023 0 0 GIC sps
270: 1059981 91150 12440 25896 0 0 GIC sps
272: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
273: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
274: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
286: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
287: 0 0 0 0 0 0 GIC msm_iommu_secure_irq
305: 0 0 0 0 0 0 GIC ARM64 primary ext IRQ
306: 0 0 0 0 0 0 GIC ARM64 secondary ext IRQ
307: 0 0 0 0 0 0 GIC ARM64 primary DBE IRQ
308: 0 0 0 0 0 0 GIC ARM64 secondary DBE IRQ
321: 10170534 9990 71563 229378 0 0 GIC qcom,smd-adsp
322: 0 0 0 0 0 0 GIC qcom,smsm-adsp
323: 6 0 0 0 0 0 GIC smp2p
325: 0 0 0 0 0 0 GIC adsp
332: 1074 0 45 0 0 0 GIC i2c-msm-v2-irq
334: 0 0 0 0 0 0 GIC i2c-msm-v2-irq
344: 0 0 0 0 0 0 GIC 7803000.sdcc1ice
346: 91 0 0 30 0 0 GIC cpr
352: 0 0 0 0 0 0 msm_tlmm_irq 7864900.sdhci cd
353: 0 0 0 0 0 0 qpnp-int pm8950_tz
354: 185 34 25 38 8 0 qpnp-int qpnp_kpdpwr_status
355: 44 62 12 10 0 0 qpnp-int qpnp_resin_status
360: 0 0 0 0 0 0 qpnp-int qpnp_adc_tm_high_interrupt
361: 0 0 0 0 0 0 qpnp-int qpnp_adc_tm_low_interrupt
362: 0 0 0 0 0 0 qpnp-int qpnp_rtc_alarm
364: 0 0 0 0 0 0 qpnp-int chg-error
368: 25 17 115 10 0 0 qpnp-int chg-p2f-thr
369: 3 8 53 3 0 0 qpnp-int chg-rechg-thr
370: 0 0 0 0 0 0 qpnp-int chg-taper-thr
371: 5 11 55 4 0 0 qpnp-int chg-tcc-thr
372: 0 0 0 0 0 0 qpnp-int otg-fail
373: 0 0 0 0 0 0 qpnp-int otg-oc
374: 0 0 0 0 0 0 qpnp-int usbid-change
375: 0 0 0 0 0 0 qpnp-int batt-hot
376: 32 0 20 12 0 0 qpnp-int batt-warm
377: 0 0 0 0 0 0 qpnp-int batt-cold
378: 0 0 0 0 0 0 qpnp-int batt-cool
380: 0 0 0 0 0 0 qpnp-int batt-low
381: 0 0 0 0 0 0 qpnp-int batt-missing
383: 24 16 18 11 0 0 qpnp-int usbin-uv
384: 0 0 0 0 0 0 qpnp-int usbin-ov
385: 0 0 0 0 0 0 qpnp-int aicl-done
386: 22 14 15 9 0 0 qpnp-int power-ok
387: 0 0 0 0 0 0 qpnp-int temp-shutdown
390: 4 6 6 7 0 0 qpnp-int full-soc
391: 0 0 0 0 0 0 qpnp-int empty-soc
392: 422 468 468 451 0 0 qpnp-int delta-soc
393: 0 0 0 0 0 0 qpnp-int first-est-done
397: 33 9 4 6 0 0 qpnp-int vbatt-low
401: 0 0 0 0 0 0 qpnp-int batt-missing
403: 34988 152768 72069 64056 0 0 qpnp-int mem-avail
405: 0 0 0 0 0 0 qpnp-int bcl_ibat_interrupt
406: 0 0 0 0 0 0 qpnp-int bcl_vbat_interrupt
407: 0 0 0 0 0 0 qpnp-int qpnp_wled_sc_irq
408: 0 0 0 0 0 0 qpnp-int qpnp_sc_irq
410: 0 0 0 0 0 0 qpnp-int pm8004_tz
411: 99 4 10 5 0 0 msm_tlmm_irq wcd9xxx
412: 0 0 0 0 0 0 msm_tlmm_irq hall_sensor
413: 1055360 85877 31728 16183 0 0 msm_tlmm_irq ft5x06_ts
542: 10321 32 16 427 0 0 msm_tlmm_irq fpc_fpc1020.109
543: 0 0 0 0 0 0 smp2p_gpio adsp
544: 1 0 0 0 0 0 smp2p_gpio error_ready_interrupt
545: 1 0 0 0 0 0 smp2p_gpio adsp
546: 0 0 0 0 0 0 smp2p_gpio adsp
575: 0 0 0 0 0 0 smp2p_gpio wcnss
576: 0 0 0 1 0 0 smp2p_gpio error_ready_interrupt
577: 0 0 0 1 0 0 smp2p_gpio wcnss
578: 0 0 0 0 0 0 smp2p_gpio wcnss
607: 0 0 2 0 0 0 smp2p_gpio modem
608: 1 0 2 0 0 0 smp2p_gpio error_ready_interrupt
609: 1 0 2 0 0 0 smp2p_gpio modem
610: 0 0 0 0 0 0 smp2p_gpio modem
703: 0 0 0 0 0 0 msm_tlmm_irq camera_focus
704: 0 0 0 0 0 0 msm_tlmm_irq camera_snapshot
705: 324 4 0 0 0 0 msm_tlmm_irq volume_up
706: 20 2 0 0 0 0 wcd9xxx mbhc sw intr
707: 0 0 0 0 0 0 wcd9xxx Elect Remove
708: 8 0 0 0 0 0 wcd9xxx Button Press detect
709: 4 1 0 0 0 0 wcd9xxx Button Release detect
710: 0 0 0 0 0 0 wcd9xxx Elect Insert
IPI0: 44210297 54722749 33361414 20216691 6813301 4354336 Rescheduling interrupts
IPI1: 1147947 2488334 3017214 3176499 925095 933268 Function call interrupts
IPI2: 6290564 179639 164178 136534 882320 126468 Single function call interrupts
IPI3: 0 0 0 0 0 0 CPU stop interrupts
IPI4: 4633737 1508042 1717479 1538825 135943 105164 Timer broadcast interrupts
IPI5: 78 2 3 1 0 0 IRQ work interrupts
IPI6: 0 0 0 0 0 0 CPU wakeup interrupts
IPI7: 0 0 0 0 0 0 CPU backtrace
Err: 0
Related
Hi! Long story short, I was messing up some things with android stock apps than force closes appeared. I then needed bring back a backup so I flashed package_us2.3.5.tar.md5 which work but I had clock app problems. So not really knowing what I was doing I flashed with the .pit file provided here with repartition checked and I started getting E: cant mount errors...
This is where it went ugly: I mistook 4.0 and 5.0 .tar and .pit file... So basically I am the owner of a brick. I mean it, black screen brick. But with the unbrickable resurector I could get it back to download mode and heimdall could pull the pit file + odin would detect the device so I guess I am not that unlucky... or so I thought.
Odin always fails after full NAND write, doesn't matter with what I try.
Heimdall (run in linux):
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
.glassechidna
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:
glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
Serial No: "?"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:6601
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...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Uploading PIT
PIT upload successful
Uploading KERNEL
0%
File Part #0... Response: 0 0 0 0 0 0 0 0
1%
File Part #1... Response: 0 0 0 0 1 0 0 0
3%
File Part #2... Response: 0 0 0 0 2 0 0 0
5%
File Part #3... Response: 0 0 0 0 3 0 0 0
6%
File Part #4... Response: 0 0 0 0 4 0 0 0
8%
File Part #5... Response: 0 0 0 0 5 0 0 0
10%
File Part #6... Response: 0 0 0 0 6 0 0 0
11%
File Part #7... Response: 0 0 0 0 7 0 0 0
13%
File Part #8... Response: 0 0 0 0 8 0 0 0
15%
File Part #9... Response: 0 0 0 0 9 0 0 0
16%
File Part #10... Response: 0 0 0 0 A 0 0 0
18%
File Part #11... Response: 0 0 0 0 B 0 0 0
20%
File Part #12... Response: 0 0 0 0 C 0 0 0
21%
File Part #13... Response: 0 0 0 0 D 0 0 0
23%
File Part #14... Response: 0 0 0 0 E 0 0 0
25%
File Part #15... Response: 0 0 0 0 F 0 0 0
26%
File Part #16... Response: 0 0 0 0 10 0 0 0
28%
File Part #17... Response: 0 0 0 0 11 0 0 0
30%
File Part #18... Response: 0 0 0 0 12 0 0 0
31%
File Part #19... Response: 0 0 0 0 13 0 0 0
33%
File Part #20... Response: 0 0 0 0 14 0 0 0
35%
File Part #21... Response: 0 0 0 0 15 0 0 0
36%
File Part #22... Response: 0 0 0 0 16 0 0 0
38%
File Part #23... Response: 0 0 0 0 17 0 0 0
40%
File Part #24... Response: 0 0 0 0 18 0 0 0
41%
File Part #25... Response: 0 0 0 0 19 0 0 0
43%
File Part #26... Response: 0 0 0 0 1A 0 0 0
45%
File Part #27... Response: 0 0 0 0 1B 0 0 0
46%
File Part #28... Response: 0 0 0 0 1C 0 0 0
48%
File Part #29... Response: 0 0 0 0 1D 0 0 0
50%
File Part #30... Response: 0 0 0 0 1E 0 0 0
51%
File Part #31... Response: 0 0 0 0 1F 0 0 0
53%
File Part #32... Response: 0 0 0 0 20 0 0 0
55%
File Part #33... Response: 0 0 0 0 21 0 0 0
56%
File Part #34... Response: 0 0 0 0 22 0 0 0
58%
File Part #35... Response: 0 0 0 0 23 0 0 0
60%
File Part #36... Response: 0 0 0 0 24 0 0 0
61%
File Part #37... Response: 0 0 0 0 25 0 0 0
63%
File Part #38... Response: 0 0 0 0 26 0 0 0
65%
File Part #39... Response: 0 0 0 0 27 0 0 0
66%
File Part #40... Response: 0 0 0 0 28 0 0 0
68%
File Part #41... Response: 0 0 0 0 29 0 0 0
70%
File Part #42... Response: 0 0 0 0 2A 0 0 0
71%
File Part #43... Response: 0 0 0 0 2B 0 0 0
73%
File Part #44... Response: 0 0 0 0 2C 0 0 0
75%
File Part #45... Response: 0 0 0 0 2D 0 0 0
76%
File Part #46... Response: 0 0 0 0 2E 0 0 0
78%
File Part #47... Response: 0 0 0 0 2F 0 0 0
80%
File Part #48... Response: 0 0 0 0 30 0 0 0
81%
File Part #49... Response: 0 0 0 0 31 0 0 0
83%
File Part #50... Response: 0 0 0 0 32 0 0 0
85%
File Part #51... Response: 0 0 0 0 33 0 0 0
86%
File Part #52... Response: 0 0 0 0 34 0 0 0
88%
File Part #53... Response: 0 0 0 0 35 0 0 0
90%
File Part #54... Response: 0 0 0 0 36 0 0 0
91%
File Part #55... Response: 0 0 0 0 37 0 0 0
93%
File Part #56... Response: 0 0 0 0 38 0 0 0
95%
File Part #57... Response: 0 0 0 0 39 0 0 0
96%
File Part #58... Response: 0 0 0 0 3A 0 0 0
98%
File Part #59... Response: 0 0 0 0 3B 0 0 0
100%
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Re-attaching kernel driver...
On a side note, I thought perharps the battery was uncharged since I have read somewhere it doesn't charge when the "not phone" is in this state. True, it doesn't charge when to connected to a computer, a wall charger is fine. Why is that?
AND usb jig doesn't do anything on this case. But I haven't tested it on another phone which I will do soon.
Any ideas? I don't want to send back it to samsung as I might happen to me again (or to some of you)
Thanks!
Sounds like your partition table is messed up, if heimdall can output pit info then you might want to post it here and try and get someone else to do the same, to see if they match up
Ok, here is the info from heimdall:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
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:
glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 12
Unknown 1: 2086912
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 29
Unknown 7: 63480
Unknown 8: 61
--- Entry #0 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 6684783
Unknown 3: 2097268
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename:
--- Entry #2 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 20
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.rfs
--- Entry #3 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 4
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename: sbl.bin
--- Entry #5 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 21
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #6 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 22
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 23
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 0
Unknown 3: 0
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Partition Type: 0 (RFS)
Partition Identifier: 24
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 176
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: MOVINAND
Filename: movinand.mst
Ending session...
Rebooting device...
Re-attaching kernel driver...
I can not be sure because I do not own a 4.0, but I noticed that the last partition is EXT4 while all of the rest are RFS. On the 5.0, the stock kernel can not mount ext4. Only a custom kernel that has ext4 enabled would be able to mount it. The block size and block count are also 0? Maybe that's the way it's supposed to look... I don't know, hopefully someone with a U.S. 4.0 will post their heimdall output.
If you've just used the resurrector then the bootloaders that you have flashed are only temporary. Every time you boot the device you will most likely get the download mode screen. I don't think the file "package_us2.3.5.tar.md5" has bootloaders in it, but you can check by opening it with winrar and see if it has "boot.bin" and "Sbl.bin".
If it does have bootloaders in it. You might try flashing it and then flashing SeveS kernel, then see if it boots. SteveS kernel may be able to at least mount that EXT4 partition...
Let us know how it goes...
I have an idea but I don't know if it will work.
1. Go to samfirmware.com and download 1 of the rom*(froyo 2.2) for the YP-G1.
2. Then extract the files (rename the .tar.md5 to just .tar)
3. Then download package_us2.3.5.tar.md5 and rename it like the froyo package.
4. Then try to flash the files with heimdall but replace the factoryfs.rfs and the zimage (take SteVeS one) with the one from package_us2.3.5.tar.md5
5.Enjoy!!! (DON'T FORGET TO CHECK REPARTITION.)
It is supposed to work because it contains the bootloader for the galaxy s wifi (Which is galaxy player internationnal version.)
Also try this on windows. Don't forget to install drivers from heimdall.
Hope this helps
---------- Post added at 06:42 PM ---------- Previous post was at 06:39 PM ----------
Meticulus said:
I can not be sure because I do not own a 4.0, but I noticed that the last partition is EXT4 while all of the rest are RFS. On the 5.0, the stock kernel can not mount ext4. Only a custom kernel that has ext4 enabled would be able to mount it. The block size and block count are also 0? Maybe that's the way it's supposed to look... I don't know, hopefully someone with a U.S. 4.0 will post their heimdall output.
If you've just used the resurrector then the bootloaders that you have flashed are only temporary. Every time you boot the device you will most likely get the download mode screen. I don't think the file "package_us2.3.5.tar.md5" has bootloaders in it, but you can check by opening it with winrar and see if it has "boot.bin" and "Sbl.bin".
If it does have bootloaders in it. You might try flashing it and then flashing SeveS kernel, then see if it boots. SteveS kernel may be able to at least mount that EXT4 partition...
Let us know how it goes...
Click to expand...
Click to collapse
Steve's don't have ext4 support so it can't mount it. (I think)
zaclimon said:
Steve's don't have ext4 support so it can't mount it. (I think)
Click to expand...
Click to collapse
I looked at SteveS source code and it looks like ext4 is enabled in the kernel, however the init.rc is not is not scripted to mount ext4 partitions. I believe that I could make this change and I have asked SteveS for his permission to do so...
Meticulus said:
I looked at SteveS source code and it looks like ext4 is enabled in the kernel, however the init.rc is not is not scripted to mount ext4 partitions. I believe that I could make this change and I have asked SteveS for his permission to do so...
Click to expand...
Click to collapse
That would be so awesome if you could do that. Thanks!
Sent from my Galaxy Player 4.0 (YP-G1)
Meticulus said:
I looked at SteveS source code and it looks like ext4 is enabled in the kernel, however the init.rc is not is not scripted to mount ext4 partitions. I believe that I could make this change and I have asked SteveS for his permission to do so...
Click to expand...
Click to collapse
I saw his kernel I did add the scripts but I don't know how to convert it lol. -__- Well I didin't flash it yet. I'll try this during the weekend.
zaclimon said:
I saw his kernel I did add the scripts but I don't know how to convert it lol. -__- Well I didin't flash it yet. I'll try this during the weekend.
Click to expand...
Click to collapse
This has gotten a little off topic but, Ghetto Lagfix to convert
Meticulus said:
I looked at SteveS source code and it looks like ext4 is enabled in the kernel, however the init.rc is not is not scripted to mount ext4 partitions. I believe that I could make this change and I have asked SteveS for his permission to do so...
Click to expand...
Click to collapse
In his source code there is the possibility of ext4 support but you have to configure the kernel to compile with it (make menuconfig) or something similar if I remember correctly. I'll give it a try when I get my device back from the dead.
But yeah, it might be off topic
Oh well, seems like my problem got away by itself I am indeed confused. I tried booting (not in vmware) in windows to flash with odin (which didn't work), got back into linux to resurect my player and then it flashed like it used to. I got no clue why, the only thing I did different was reboot and keep vmware closed.
So then I flashed the 4's internationnal version complete rom (with sbl, boot, param, cache ...) except for the zimage (I used steve's) and factoryfs (I took the "package_us2.3.5.tar.md5") + I used the US's pit file.
So far everything works fine except the clock app!
(Btw how do I change the title of the thread to mark [solved]?)
Congrats on your restored device! I know it's off topic but I managed to change the script. The problem is it cant mount cache I got error
Code:
E:can't mount /cache/recovery/command
for exemple.
Ok, after a little more testing, there are 2 things that do not work if you flash the mentioned international's file to the US: entering download mode or recovery with the button combo!
usb jig works fine and in a terminal emulator reboot recovery does the trick.
In the DFT SPL package, the file name of nbh is ETERIMG.nbh. But it did not work for AT&T Titan. In that case, you can try to rename the file to be ETERDIAG.nbh and put it the golden card. Usually, it works better.
Anyone success to flash HSPL?
I used ETERDIAG.nbh to flash SPL 2.05, it shows it completed successfully. But after it reboot, nothing change. The SPL is still 2.5.
BTW The phone already has EURO rom.
If anyone can flash SPL 2.05, plz share how to do it. Thanks.
will the ETERDIAG.nbh do the job for any ROM file or just SPL file, can anyone try flashing diferent roms and spl's with the ETERDIAG.nbh and report
ppgame said:
In the DFT SPL package, the file name of nbh is ETERIMG.nbh. But it did not work for AT&T Titan. In that case, you can try to rename the file to be ETERDIAG.nbh and put it the golden card. Usually, it works better.
Click to expand...
Click to collapse
What's the difference between ETERIMG & ETERDIAG?
jenrique15 said:
What's the difference between ETERIMG & ETERDIAG?
Click to expand...
Click to collapse
Actually, almost all the spl of HTC phone will support ***IMG.nbh and ****DIAG.nbh. IMG is for the reflashing and DIAG diagnostic image. For example, HTC Excalibur http://forum.xda-developers.com/showthread.php?t=330099. DIAG is very useful when your phone is in trouble. For Titan, I found the DIAG image http://www.52sjwx.com/read.php?tid=74083 ( chinese website), but you have to pay money to download it.
Wonder if renaming the .nbh to ETERDIAG would assist with the HSPL flashing problem on AT&T branded titans.
Sent from my PI39100 using Board Express
dhack21 said:
Wonder if renaming the .nbh to ETERDIAG would assist with the HSPL flashing problem on AT&T branded titans.
Sent from my PI39100 using Board Express
Click to expand...
Click to collapse
In my ATT phone, I can not flash other stock rom with ETERIMG or RUU but no problem with ETERDIAG. However, no luck for the spl and radio even it shows the update is finished.
ppgame said:
Actually, almost all the spl of HTC phone will support ***IMG.nbh and ****DIAG.nbh. IMG is for the reflashing and DIAG diagnostic image. For example, HTC Excalibur http://forum.xda-developers.com/showthread.php?t=330099. DIAG is very useful when your phone is in trouble. For Titan, I found the DIAG image http://www.52sjwx.com/read.php?tid=74083 ( chinese website), but you have to pay money to download it.
Click to expand...
Click to collapse
I will try to register later or ask some chinesse friends to register for me if anyone can do it before pls try it it would be great solution
My gold card only allows me to flash ETERIMG.nbh
i cant dig out eterdiag.nbh for htc at&t titan..
jenrique15 said:
What's the difference between ETERIMG & ETERDIAG?
Click to expand...
Click to collapse
Here is the information I dumped from the phone after used the goldcard to upgrade spl by ETERIMG
Code:
[SPL] +SDFATChkIfNeedUpdate...
[SPL] SDFATChkImg: FileName=ETERDIAG.nbh
[SPL] dwBytesPerSector = 512
[SPL] dwSectorsPerCluster = 8
[SPL] dwTotalSectors = 1060227
[SPL] dwFirstDataSector = 8192
[SPL] dwRootStartSector = 8192
[SPL] dwFatStartSector = 6136
[SPL] GetNextClusterNum: bad block or EOF
[SPL] SDFATChkImg: Failed to open config.dat.
[SPL] GetNextClusterNum: bad block or EOF
[SPL] SDFATCheckTargetImage: RhOpenFile() failed ETERDIAG.nbh
[SPL] SDFATChkImg: FileName=ETERIMG.nbh
[SPL] SDFATChkImg: Target File Size = 19A237EE
[SPL] SDFATChkImg: Read File Length = 200000
[SPL] +RhReadFile: dwSize 0x200000 (5186)
[SPL] -RhReadFile: dwTotalRead 0x200000 (7094)
[SPL] +00000000 52 30 30 30 46 46 A 0 0 0 0 0 0 0 0 0
[SPL] +00000010 0 0 0 0 0 0 0 0 0 1 0 FFFFFF80 0 0 0 1
[SPL] +00000020 48 0 0 0 54 0 0 0 43 0 0 0 49 0 0 0
[SPL] +00000030 4D 0 0 0 41 0 0 0 47 0 0 0 45 0 0 0
[SPL] +00000040 50 49 33 39 31 31 30 30 30 0 0 0 0 0 0 0
[SPL] +00000050 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000060 0 3 0 0 0 2 0 0 30 9 0 0 FFFFFF80 3 0 0
[SPL] +00000070 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000080 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000090 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000000A0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000000B0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000000C0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000000D0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000000E0 0 22 0 0 0 22 72 1 50 72 7E 1 44 FFFFFFCC 7E 1
[SPL] +000000F0 FFFFFF91 FFFFFFCC 7E 1 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000100 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000110 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000120 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000130 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000140 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000150 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000160 0 0 72 1 50 50 C 0 FFFFFFF4 59 0 0 4D 0 0 0
[SPL] +00000170 0 FFFFFFBA 15 18 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000180 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +00000190 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001A0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001B0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001C0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001D0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001E0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] +000001F0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[SPL] Image0 Type=0x300, Offset=0x2200, Length=0x1720000
[SPL] Image1 Type=0x200, Offset=0x1722200, Length=0xC5050
[SPL] Image2 Type=0x930, Offset=0x17E7250, Length=0x59F4
[SPL] Image3 Type=0x380, Offset=0x17ECC44, Length=0x4D
[SPL] Image4 Type=0x400, Offset=0x17ECC91, Length=0x1815BA00
[SPL] -SDFATChkImg...0
[SPL] +CheckNbhModelID
[SPL] Model ID error(5) 31 != 30
[SPL] Signature : 0xEE4329
[SPL] UpdateStatus : 0x2
[SPL] UpdateCount : 0x3
[SPL] BodyLength : 0x23A
[SPL] BodyCRC : 0xCC8B744E
This log shows the USB HOST MODEL will check three files in sequence: ETERDIAG.nbh, config.dat, ETERIMG.nbh.
For ETERIMG, it will load the file but it also checks the Model ID at the end. But it will not check the model ID if upgrade by ETERDIAG.
And more, the nbh file will have some "FFFFFF". I think this is an error during loading. If I try different card or flash drive, "FFFFFF" will be at different position. It might be lucky to get everything done if you dont have any "FFFFFF" in the loading process. I suggest you can try different sd cards or usb drives as many as you can.
wow that is great discovery, so the flash drive plays big role after all, thta means that correct flash drive can struck u out i will get 100 flash drives DD
i tried to flash stock img.zip file from sdcard. i got nfc error.
i wanted to try fastboot flash nfc nfc.img then i got this error
Code:
writing 'nfc'...
(bootloader) nfc_dl_write: Error res pattern
(bootloader) cmd=
(bootloader) [0|4]: B 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) exp=
(bootloader) [0|4]: 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) res=
(bootloader) nfc_dl_write: Error res pattern
(bootloader) cmd=
(bootloader) [0|4]: B 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) exp=
(bootloader) [0|4]: 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) res=
(bootloader) nfc_dl_write: Error res pattern
(bootloader) cmd=
(bootloader) [0|4]: B 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) exp=
(bootloader) [0|4]: 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0
(bootloader) res=
(bootloader) nfc_fwupdate fail [Settings memory area 1]
Any ideas ???
Maybe permissions issue writing to memory space? Is your log more verbose?
HTC RUBY - Energized ICS Faux123 kernel - XDA Premium
it is s-off and engineering hboot flashed.
Hello,
on my Wintec Filemate Clear T720 I flashed a bad CWM recovery (CWM-based Recovery v6.0.1.0 for A10C (LY-F1/TREQ) by flowish) was is not designed for my device. First I had think, that A10 means the processor. But it isn't. It's a another product!
Now the tablet boots only in recovery or bootloader mode.
I can't install anything, because I get the following errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Even, the original T720BK07-update_20121214.zip isn't installable. It's Android 4.0.3
In recovery mode, I can put adb commands, but after reboot, the tablet goes allways in CWM recovery.
I can boot into the bootloader too.
Livesuit or PhoenixUSBPro shows allways Error 0x120 or 0x162, based on the image I like to flash.
Livesuit shows "Image file invalid" or "No device that need to update !" based on the images i tryed.
Here are some infos I get from adb in recovery mode:
adb devices
List of devices attached
2008044236 recovery
-
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 59.63
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : sun4i
Revision : 0000
Serial : 0000000000000000
-
cat /proc/partitions
major minor #blocks name
179 0 7977472 mmcblk0
179 1 7446096 mmcblk0p1
179 2 500162 mmcblk0p2
179 3 31182 mmcblk0
-
cat diskstats
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
179 0 mmcblk0 180 15379 15566 740 15 30 45 790 0 790 1530
179 1 mmcblk0p1 179 15379 15558 740 15 30 45 790 0 790 1530
-
adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 416864 52 416812 0% /dev
tmpfs 416864 4 416860 0% /tmp
-
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
-
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 52.0K 407.0M 0% /dev
tmpfs 407.1M 4.0K 407.1M 0% /tmp
-
adb shell ls
boot emmc sd-ext
bootloader etc sdcard
busybox init sys
cache init.rc system
data proc tmp
datadata res ueventd.goldfish.rc
default.prop root ueventd.rc
dev sbin ueventd.sun4i.rc
-
Has someone an idea to repair my tablet?
Best regards
Walter
I upload the correct firmware on 4Shared filemate clear T720Cc08 work perfectly i also use
That was orignally russion tab prology evolution tab 750
After flashing tablet speed very strong and fast
Sent from my XT1058 using Tapatalk
On linux, we can use something like `netstat -s` and get something like the following:
netstat -s | grep retrans
8411 segments retransmitted
1 timeouts after reno fast retransmit
874 fast retransmits
113 retransmits in slow start
The netstat version on Android doesn't have this functionality. How can we determine retransmission statistics on the Android platform?
drizzle123 said:
On linux, we can use something like `netstat -s` and get something like the following:
netstat -s | grep retrans
8411 segments retransmitted
1 timeouts after reno fast retransmit
874 fast retransmits
113 retransmits in slow start
The netstat version on Android doesn't have this functionality. How can we determine retransmission statistics on the Android platform?
Click to expand...
Click to collapse
I don't think your able to do that mate
([emoji3590]09-09-18[emoji3590])
We can do the following:
TB-8504F:/ $ cat /proc/net/netstat
TcpExt: SyncookiesSent SyncookiesRecv SyncookiesFailed EmbryonicRsts PruneCalled RcvPruned OfoPruned OutOfWindowIcmps LockDroppedIcmps ArpFilter TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab DelayedACKs DelayedACKLocked DelayedACKLost ListenOverflows ListenDrops TCPPrequeued TCPDirectCopyFromBacklog TCPDirectCopyFromPrequeue TCPPrequeueDropped TCPHPHits TCPHPHitsToUser TCPPureAcks TCPHPAcks TCPRenoRecovery TCPSackRecovery TCPSACKReneging TCPFACKReorder TCPSACKReorder TCPRenoReorder TCPTSReorder TCPFullUndo TCPPartialUndo TCPDSACKUndo TCPLossUndo TCPLostRetransmit TCPRenoFailures TCPSackFailures TCPLossFailures TCPFastRetrans TCPForwardRetrans TCPSlowStartRetrans TCPTimeouts TCPLossProbes TCPLossProbeRecovery TCPRenoRecoveryFail TCPSackRecoveryFail TCPSchedulerFailed TCPRcvCollapsed TCPDSACKOldSent TCPDSACKOfoSent TCPDSACKRecv TCPDSACKOfoRecv TCPAbortOnData TCPAbortOnClose TCPAbortOnMemory TCPAbortOnTimeout TCPAbortOnLinger TCPAbortFailed TCPMemoryPressures TCPSACKDiscard TCPDSACKIgnoredOld TCPDSACKIgnoredNoUndo TCPSpuriousRTOs TCPMD5NotFound TCPMD5Unexpected TCPSackShifted TCPSackMerged TCPSackShiftFallback TCPBacklogDrop TCPMinTTLDrop TCPDeferAcceptDrop IPReversePathFilter TCPTimeWaitOverflow TCPReqQFullDoCookies TCPReqQFullDrop TCPRetransFail TCPRcvCoalesce TCPOFOQueue TCPOFODrop TCPOFOMerge TCPChallengeACK TCPSYNChallenge TCPFastOpenActive TCPFastOpenActiveFail TCPFastOpenPassive TCPFastOpenPassiveFail TCPFastOpenListenOverflow TCPFastOpenCookieReqd TCPSpuriousRtxHostQueues BusyPollRxPackets TCPAutoCorking TCPFromZeroWindowAdv TCPToZeroWindowAdv TCPWantZeroWindowAdv TCPSynRetrans TCPOrigDataSent
TcpExt: 0 0 0 0 0 0 0 0 0 0 37 0 0 0 0 0 151 0 82 0 0 22 0 2320 0 8335 5 278 74 0 1 0 0 0 0 0 0 0 0 9 0 0 0 0 1 0 0 65 43 1 0 1 0 0 81 0 0 0 48 44 0 53 0 4 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 2 1600 132 0 0 2 2 0 0 0 0 0 0 0 0 14 0 0 0 64 751
IpExt: InNoRoutes InTruncatedPkts InMcastPkts OutMcastPkts InBcastPkts OutBcastPkts InOctets OutOctets InMcastOctets OutMcastOctets InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts InCEPkts
IpExt: 0 0 385 248 683 0 3790846 363856 14808 11056 68971 0 0 6861 0 0 0
drizzle123 said:
We can do the following:
TB-8504F:/ $ cat /proc/net/netstat
TcpExt: SyncookiesSent SyncookiesRecv SyncookiesFailed EmbryonicRsts PruneCalled RcvPruned OfoPruned OutOfWindowIcmps LockDroppedIcmps ArpFilter TW TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab DelayedACKs DelayedACKLocked DelayedACKLost ListenOverflows ListenDrops TCPPrequeued TCPDirectCopyFromBacklog TCPDirectCopyFromPrequeue TCPPrequeueDropped TCPHPHits TCPHPHitsToUser TCPPureAcks TCPHPAcks TCPRenoRecovery TCPSackRecovery TCPSACKReneging TCPFACKReorder TCPSACKReorder TCPRenoReorder TCPTSReorder TCPFullUndo TCPPartialUndo TCPDSACKUndo TCPLossUndo TCPLostRetransmit TCPRenoFailures TCPSackFailures TCPLossFailures TCPFastRetrans TCPForwardRetrans TCPSlowStartRetrans TCPTimeouts TCPLossProbes TCPLossProbeRecovery TCPRenoRecoveryFail TCPSackRecoveryFail TCPSchedulerFailed TCPRcvCollapsed TCPDSACKOldSent TCPDSACKOfoSent TCPDSACKRecv TCPDSACKOfoRecv TCPAbortOnData TCPAbortOnClose TCPAbortOnMemory TCPAbortOnTimeout TCPAbortOnLinger TCPAbortFailed TCPMemoryPressures TCPSACKDiscard TCPDSACKIgnoredOld TCPDSACKIgnoredNoUndo TCPSpuriousRTOs TCPMD5NotFound TCPMD5Unexpected TCPSackShifted TCPSackMerged TCPSackShiftFallback TCPBacklogDrop TCPMinTTLDrop TCPDeferAcceptDrop IPReversePathFilter TCPTimeWaitOverflow TCPReqQFullDoCookies TCPReqQFullDrop TCPRetransFail TCPRcvCoalesce TCPOFOQueue TCPOFODrop TCPOFOMerge TCPChallengeACK TCPSYNChallenge TCPFastOpenActive TCPFastOpenActiveFail TCPFastOpenPassive TCPFastOpenPassiveFail TCPFastOpenListenOverflow TCPFastOpenCookieReqd TCPSpuriousRtxHostQueues BusyPollRxPackets TCPAutoCorking TCPFromZeroWindowAdv TCPToZeroWindowAdv TCPWantZeroWindowAdv TCPSynRetrans TCPOrigDataSent
TcpExt: 0 0 0 0 0 0 0 0 0 0 37 0 0 0 0 0 151 0 82 0 0 22 0 2320 0 8335 5 278 74 0 1 0 0 0 0 0 0 0 0 9 0 0 0 0 1 0 0 65 43 1 0 1 0 0 81 0 0 0 48 44 0 53 0 4 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 2 1600 132 0 0 2 2 0 0 0 0 0 0 0 0 14 0 0 0 64 751
IpExt: InNoRoutes InTruncatedPkts InMcastPkts OutMcastPkts InBcastPkts OutBcastPkts InOctets OutOctets InMcastOctets OutMcastOctets InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts InECT0Pkts InCEPkts
IpExt: 0 0 385 248 683 0 3790846 363856 14808 11056 68971 0 0 6861 0 0 0
Click to expand...
Click to collapse
Damn that's alot of code
([emoji3590]09-09-18[emoji3590])