Database Develop

Problem with ROM UPGRADE under VMWARE /no connection after the Boot Loader menu/

I have a trouble flashing my Diamond ROM with HardSPL or anything else, including the original shipped ROMs. First of all I'm running the WinXP as a guest OS under VMWare and my host is linux. Once the Diamond restart and enter the boot loader (the colorful screen) the XP can't recognize it with the standart message "USB Device Not Recognized"...
The info I receive in dmesg is as follows:
usb 3-2: new full speed USB device using uhci_hcd and address 10
usb 3-2: new full speed USB device using uhci_hcd and address 11
usb 3-2: new device found, idVendor=0bb4, idProduct=0a15
usb 3-2: new device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: Qualcomm CDMA Technologies MSM
usb 3-2: Manufacturer: HTC
usb 3-2: configuration #1 chosen from 1 choice
Also, of course I have allowed and redirected the "High Qualcomm CDMA Technologies MSM" into VMWare.
Any ideas??
Cheers!!

i have the same prolem..did u manage to sole this problem?

Problem with connection of Usb-Eth-adapter

I am sorry for possible grammatical and stylistic mistakes - I use the translator of google.
Please help.
Samsung Galaxy Note on the Android ICS 4.0.3 (stock firmware (N7000XXLQ2_N7000OXELP6_N7000XXLPT_HOME), kernel CF-Root-SGN_XX_SEB_LQ3-v5.6-CWM5).
Code:
# uname -a
Linux localhost 3.0.15-N7000XXLQ3-CL646962 #3 SMP PREEMPT Wed May 30 21:05:57 KST 2012 armv7l GNU/Linux
It is necessary to connect the adapter USB-Eth adapter (chip ASIX AX88772B). Connected via USB-OTG.
Driver's sources: AX88772B_772A_760_772_178_LINUX_Driver_v4.4.0_Source.zip
Kernel's sources: GT-N7000_ICS_Opensource_Update3.zip
Linked arm-2010q1.
Plug the adapter:
Code:
[ 90.311645] usb_otg_accessory_power: otg power = 1
[ 90.316215] host_notify: ndev name=usb_otg: from state=0 -> to state=1
[ 90.645890] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 90.646018] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 90.646145] usb usb2: Product: S3C OTGHCD
[ 90.646225] usb usb2: Manufacturer: Linux 3.0.15-N7000XXLQ3-CL646962 EMSP_OTGHCD
[ 90.646348] usb usb2: SerialNumber: s3cotg
[ 90.688297] usb usb2: otg host do not enter suspend.
[ 90.688354] OTG s5pc110_start_otg(214): OTG HCD Initialized HCD, bus=C110 OTG Controller, usbbus=2
[ 91.025575] usb 2-1: new high speed USB device number 2 using s3c_otghcd
[ 91.070410] usb 2-1: New USB device found, idVendor=0b95, idProduct=772b
[ 91.070520] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 91.070621] usb 2-1: SerialNumber: 000977
Inserting modules (mii and asix):
Code:
# insmod /system/lib/modules/mii.ko
# insmod /system/lib/modules/asix.ko
# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 1519:0020
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 002: ID 0b95:772b
# lsmod
asix 45984 0 - Live 0xbf080000
mii 4249 1 asix, Live 0xbf007000
dhd 390627 0 - Live 0xbf01f000
j4fs 69431 1 - Live 0xbf00a000 (P)
Si4709_driver 24207 0 - Live 0xbf000000
# dmesg | grep asix
[ 208.068599] eth0: register 'asix' at usb-s3cotg-1, ASIX AX88772B USB 2.0 Ethernet, 1e:c0:f7:bf:6d:77
[ 208.072102] usbcore: registered new interface driver asix
#
There is eth0 and his mac.
But
Code:
# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
and then when I try to unload the module asix, or pull out the USB connector have a kernel panic:
Code:
<6>[15424.006991] usb 2-1: USB disconnect, device number 2
<6>[15424.007787] eth0: unregister 'asix' usb-s3cotg-1, ASIX AX88772B USB 2.0 Ethernet
<1>[15424.027392] Unable to handle kernel paging request at virtual address bff7c022
<1>[15424.027503] pgd = c0004000
<1>[15424.027560] [bff7c022] *pgd=6b0b2811, *pte=00000000, *ppte=00000000
<0>[15424.027696] Internal error: Oops: 807 [#1] PREEMPT SMP
<4>[15424.027783] Modules linked in: asix mii dhd j4fs(P) Si4709_driver [last unloaded: dhd]
<4>[15424.027977] CPU: 0 Tainted: P (3.0.15-N7000XXLQ3-CL646962 #3)
<4>[15424.028125] PC is at __hw_addr_flush+0x38/0x68
<4>[15424.028217] LR is at dev_addr_flush+0x18/0x24
<4>[15424.028308] pc : [<c060eb5c>] lr : [<c060ec04>] psr: 20000013
<4>[15424.028394] sp : e5307d78 ip : d64e776d fp : e5307d94
<4>[15424.028487] r10: e563d400 r9 : 0000001f r8 : 00000000
<4>[15424.028581] r7 : d64e6800 r6 : 00200200 r5 : d64e6978 r4 : bff7c01e
<4>[15424.028689] r3 : c742d940 r2 : bff7c01e r1 : 00000030 r0 : c742d970
<4>[15424.028803] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
<4>[15424.028923] Control: 10c5387d Table: 62d9404a DAC: 00000015
<4>[15424.047751] Backtrace:
<4>[15424.047848] [<c060eb24>] (__hw_addr_flush+0x0/0x68) from [<c060ec04>] (dev_addr_flush+0x18/0x24)
<4>[15424.047980] r7:d64e6800 r6:d64e6800 r5:d64e6800 r4:d64e6800
<4>[15424.048162] [<c060ebec>] (dev_addr_flush+0x0/0x24) from [<c0605078>] (free_netdev+0x34/0xc4)
<4>[15424.048289] r5:d64e6800 r4:d64e6c20
<4>[15424.048464] [<c0605044>] (free_netdev+0x0/0xc4) from [<bf033ff0>] (axusbnet_disconnect+0xa8/0xec [asix])
<4>[15424.048605] r7:d64e6800 r6:d6356000 r5:d3a63e00 r4:d64e6c20
<4>[15424.048806] [<bf033f48>] (axusbnet_disconnect+0x0/0xec [asix]) from [<c049c0fc>] (usb_unbind_interface+0x58/0x1d8)
<4>[15424.048956] r7:bf038280 r6:d6356000 r5:d3a63e20 r4:d3a63e00
<4>[15424.049127] [<c049c0a4>] (usb_unbind_interface+0x0/0x1d8) from [<c04508bc>] (__device_release_driver+0x78/0xc8)
<4>[15424.049304] [<c0450844>] (__device_release_driver+0x0/0xc8) from [<c04509e8>] (device_release_driver+0x24/0x30)
<4>[15424.049451] r5:d3a63e20 r4:d3a63e54
<4>[15424.049563] [<c04509c4>] (device_release_driver+0x0/0x30) from [<c044fe20>] (bus_remove_device+0xc4/0xd4)
<4>[15424.049703] r5:d3a63e20 r4:d3a63e20
<4>[15424.049813] [<c044fd5c>] (bus_remove_device+0x0/0xd4) from [<c044e69c>] (device_del+0x100/0x174)
<4>[15424.049943] r7:00000001 r6:e563d400 r5:d6356068 r4:d3a63e20
<4>[15424.050115] [<c044e59c>] (device_del+0x0/0x174) from [<c04990c4>] (usb_disable_device+0xa8/0x1b0)
<4>[15424.050247] r7:00000001 r6:e563d400 r5:00000000 r4:d6356000
<4>[15424.050411] [<c049901c>] (usb_disable_device+0x0/0x1b0) from [<c0493c3c>] (usb_disconnect+0x90/0x12c)
<4>[15424.050577] [<c0493bac>] (usb_disconnect+0x0/0x12c) from [<c04949b4>] (hub_thread+0x350/0x11ac)
<4>[15424.050755] [<c0494664>] (hub_thread+0x0/0x11ac) from [<c029c4c0>] (kthread+0x90/0x98)
<4>[15424.050918] [<c029c430>] (kthread+0x0/0x98) from [<c0283d38>] (do_exit+0x0/0x6e0)
<4>[15424.051033] r7:00000013 r6:c0283d38 r5:c029c430 r4:e5043ef0
<0>[15424.051184] Code: e3406020 e593c004 e2830030 e3a01030 (e582c004)
<4>[15424.051403] ---[ end trace 8b33e0e0e42b3c17 ]---
<0>[15424.051743] Kernel panic - not syncing: Fatal exception
The situation is similar to the adapter D-Link DU-E100 and the module pegasus - kernel panic when unloading the module or disconnect the adapter.
Code:
<6>[ 86.855070] usb 2-1: new full speed USB device number 2 using s3c_otghcd
<6>[ 86.855264] OTG compare_ed(384): update ed 8 (0x8)
<6>[ 86.877747] usb 2-1: New USB device found, idVendor=07b8, idProduct=4102
<6>[ 86.877788] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 86.877827] usb 2-1: Product: USB 10/100 Fast Ethernet
<6>[ 86.877854] usb 2-1: Manufacturer: USBs
<6>[ 86.877876] usb 2-1: SerialNumber: 8f0c6e
<6>[ 386.511487] pegasus 2-1:1.0: eth0, USB 10/100 Fast Ethernet, 4e:01:05:8f:0c:6e
<6>[ 386.512386] usbcore: registered new interface driver pegasus
<6>[ 714.011428] usbcore: deregistering interface driver pegasus
<1>[ 714.030230] Unable to handle kernel paging request at virtual address 8f050152
<1>[ 714.030302] pgd = d6654000
<1>[ 714.030331] [8f050152] *pgd=00000000
<0>[ 714.030373] Internal error: Oops: 805 [#1] PREEMPT SMP
<4>[ 714.030421] Modules linked in: pegasus(-) usbnet mii dhd j4fs(P) Si4709_driver
<4>[ 714.030507] CPU: 0 Tainted: P (3.0.15-N7000XXLQ3-CL646962 #3)
<4>[ 714.030592] PC is at __hw_addr_flush+0x38/0x68
<4>[ 714.030636] LR is at dev_addr_flush+0x18/0x24
<4>[ 714.030680] pc : [<c060eb5c>] lr : [<c060ec04>] psr: 200e0013
<4>[ 714.030734] sp : d5b7fde0 ip : e3a06e0c fp : d5b7fdfc
<4>[ 714.030782] r10: 00000000 r9 : d5b7e000 r8 : 00000000
<4>[ 714.030831] r7 : bf08d1ec r6 : 00200200 r5 : e3a01178 r4 : 8f05014e
<4>[ 714.030890] r3 : d77b06c0 r2 : 8f05014e r1 : 00000030 r0 : d77b06f0
<4>[ 714.030952] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
<4>[ 714.031016] Control: 10c5387d Table: 5665404a DAC: 00000015
<4>[ 714.038601] Backtrace:
<4>[ 714.038636] [<c060eb24>] (__hw_addr_flush+0x0/0x68) from [<c060ec04>] (dev_addr_flush+0x18/0x24)
<4>[ 714.038713] r7:bf08d1ec r6:e3a01000 r5:e3a01000 r4:e3a01000
<4>[ 714.038787] [<c060ebec>] (dev_addr_flush+0x0/0x24) from [<c0605078>] (free_netdev+0x34/0xc4)
<4>[ 714.038861] r5:e3a01000 r4:e3a01420
<4>[ 714.038918] [<c0605044>] (free_netdev+0x0/0xc4) from [<bf08a690>] (pegasus_disconnect+0xa4/0xd8 [pegasus])
<4>[ 714.039002] r7:bf08d1ec r6:cee0f020 r5:bf08dd14 r4:e3a01420
<4>[ 714.039070] [<bf08a5ec>] (pegasus_disconnect+0x0/0xd8 [pegasus]) from [<c049c0fc>] (usb_unbind_interface+0x58/0x1d8)
<4>[ 714.039160] r6:d0e76c00 r5:cee0f020 r4:cee0f000 r3:00000003
<4>[ 714.039229] [<c049c0a4>] (usb_unbind_interface+0x0/0x1d8) from [<c04508bc>] (__device_release_driver+0x78/0xc8)
<4>[ 714.039322] [<c0450844>] (__device_release_driver+0x0/0xc8) from [<c04509c0>] (driver_detach+0xb4/0xb8)
<4>[ 714.039403] r5:bf08d224 r4:cee0f020
<4>[ 714.039445] [<c045090c>] (driver_detach+0x0/0xb8) from [<c044fa84>] (bus_remove_driver+0x84/0xc8)
<4>[ 714.039522] r7:d5b7ff34 r6:c09adbcc r5:bf08d224 r4:00000000
<4>[ 714.039585] [<c044fa00>] (bus_remove_driver+0x0/0xc8) from [<c0451318>] (driver_unregister+0x58/0x78)
<4>[ 714.039665] r7:d5b7ff34 r6:bf08d21c r5:bf08d224 r4:00000000
<4>[ 714.039726] [<c04512c0>] (driver_unregister+0x0/0x78) from [<c049be70>] (usb_deregister+0xc4/0xdc)
<4>[ 714.039803] r5:bf08d224 r4:bf08d214
<4>[ 714.039848] [<c049bdac>] (usb_deregister+0x0/0xdc) from [<bf08c6f8>] (pegasus_exit+0x18/0x1c [pegasus])
<4>[ 714.039943] [<bf08c6e0>] (pegasus_exit+0x0/0x1c [pegasus]) from [<c02b6de8>] (sys_delete_module+0x168/0x238)
<4>[ 714.040039] [<c02b6c80>] (sys_delete_module+0x0/0x238) from [<c0244c80>] (ret_fast_syscall+0x0/0x30)
<4>[ 714.040119] r8:c0244e28 r7:00000081 r6:00000001 r5:00000000 r4:be8ec92e
<0>[ 714.040192] Code: e3406020 e593c004 e2830030 e3a01030 (e582c004)
<4>[ 714.041333] ---[ end trace b11a3de5703310e8 ]---
<0>[ 714.041419] Kernel panic - not syncing: Fatal exception
In both cases it is clear that a problem in impossibility of removal of the mac-address (its value = 00:00:00:00:00:00 or uncertain - if I
understood correctly)
Tell me what and where to fix.
Or at least the direction in which to search.

Were you able to solve this? I've run into a very similar issue with a GT-I9100.

[Q] i8190N UMS mode / linux USB problems

Hi,
I use Arch Linux on my laptop (hp dv6 6030ew), and it's not recognizing my phone through usb port. I mean, there is nothing in output of lsusb, and dmesg gives me this :
Code:
[ 665.895871] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[ 665.910145] usb 2-1: no configurations
[ 665.910159] usb 2-1: can't read configurations, error -22
[ 666.069117] usb 2-1: new high-speed USB device number 7 using xhci_hcd
[ 666.083323] usb 2-1: no configurations
[ 666.083338] usb 2-1: can't read configurations, error -22
[ 666.242357] usb 2-1: new high-speed USB device number 8 using xhci_hcd
[ 666.256622] usb 2-1: no configurations
[ 666.256636] usb 2-1: can't read configurations, error -22
[ 666.415590] usb 2-1: new high-speed USB device number 9 using xhci_hcd
[ 666.429800] usb 2-1: no configurations
[ 666.429814] usb 2-1: can't read configurations, error -22
[ 666.429860] hub 2-0:1.0: unable to enumerate USB device on port 1
I think it's hardware problem, but I'm not really sure, so my real question is :
Can you enable UMS on i8190N?
This is my first post, so forgive my newbieshness. Cheers

Hi, fellow Archer...
The stock firmware on the Samsung Galaxy S III mini does not come with an USB Mass Storage Mode.
The nearest thing would be to use MTP (e.g. libmtp, which is in Arch's 'Extra' Repo.
I myself was unable to get this to work, so i'm transferring files either via FTP (have a Server App on the Phone, ADB push command or Airdroid.
If you somehow get Mass Storage Mode or get MTP to work, let me know!
Kind regards
newbienoobz said:
Hi,
I use Arch Linux on my laptop (hp dv6 6030ew), and it's not recognizing my phone through usb port. I mean, there is nothing in output of lsusb, and dmesg gives me this :
Code:
[ 665.895871] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[ 665.910145] usb 2-1: no configurations
[ 665.910159] usb 2-1: can't read configurations, error -22
[ 666.069117] usb 2-1: new high-speed USB device number 7 using xhci_hcd
[ 666.083323] usb 2-1: no configurations
[ 666.083338] usb 2-1: can't read configurations, error -22
[ 666.242357] usb 2-1: new high-speed USB device number 8 using xhci_hcd
[ 666.256622] usb 2-1: no configurations
[ 666.256636] usb 2-1: can't read configurations, error -22
[ 666.415590] usb 2-1: new high-speed USB device number 9 using xhci_hcd
[ 666.429800] usb 2-1: no configurations
[ 666.429814] usb 2-1: can't read configurations, error -22
[ 666.429860] hub 2-0:1.0: unable to enumerate USB device on port 1
I think it's hardware problem, but I'm not really sure, so my real question is :
Can you enable UMS on i8190N?
This is my first post, so forgive my newbieshness. Cheers
Click to expand...
Click to collapse

USB 3.X xHCI module woes

Hi,
I wanted to try to play around with roms for the P1010 (most are for the P1000, so It's really just me trying to see if I can't do a really bad port), so I downloaded Heimdall, put my P1010 into download mode, and checked to see if Heimdall could find my device. It couldnt, but no wonder it couldn't:
Code:
[ 144.398094] usb 3-3: new high-speed USB device number 7 using xhci_hcd
[ 144.411594] usb 3-3: device descriptor read/8, error -75
[ 144.528102] usb 3-3: device descriptor read/8, error -75
[ 144.790846] usb 3-3: new high-speed USB device number 8 using xhci_hcd
[ 144.804350] usb 3-3: device descriptor read/8, error -75
[ 144.920834] usb 3-3: device descriptor read/8, error -75
[ 145.183559] usb 3-3: new high-speed USB device number 9 using xhci_hcd
[ 145.197101] usb 3-3: device descriptor read/8, error -75
[ 145.313586] usb 3-3: device descriptor read/8, error -75
[ 145.576343] usb 3-3: new high-speed USB device number 10 using xhci_hcd
[ 145.589845] usb 3-3: device descriptor read/8, error -75
[ 145.706346] usb 3-3: device descriptor read/8, error -75
[ 145.809327] hub 3-0:1.0: unable to enumerate USB device on port 3
Well, that makes sense. Heimdall can't detect the device if the kernel has trouble recognising the device. So it looks like the xhci_hcd kernel module is having trouble recognising the device. Doing a little research. I've concluded that all of my USB ports are USBv3 ports because all of my USB ports use the xHCI module. If they were v2, they would use eHCI. Further research suggests that download mode with USBv3.x on linux appears to be buggy at the moment. I found reports of people using Heimdall with USB 3 devices, not working, getting the same error, then plugging it into a USBv2 port and it working.
So I'm sort of stuck at this point. My computer came with all USBv3 ports. Does anyone have experience with USBv3 ports and linux? Have you managed to get it to work with the xHCD module? Is there an alternate module that I can use that works better? Does anyone have any more info on this issue?
Thanks,
Dragos

heimdall problem with xhci-hcd module
i have exactly the same problem (and dmesg-logging) with my GT-P5110 tablet on my asus laptop R704A, with ubuntu 12.10 installed.
heimdall does not detect this tablet.
the xhci-hcd module is in kernel embedded, so i can't blacklist that module.
instead i tried to unbind :
conform: ref: ubuntuforums.org/showthread.php?p=9180298#post9180298
echo -n "XXXX:XX:XX.X" | tee /sys/bus/pci/drivers/xhci_hcd/unbind
but without success.
the mentioned problem does not occur with heimdall on the same laptop with my I9300-smartphone connected.
with ADB i don't have any detect problem with the GT-P5110 and I9300-phone.
--
my GT-5110 and I9300 are working perfectly with heimdall on a laptop with the same ubuntu release, but without a usb3.0 interface.

Just found this thread after searching for exactly the same problem. I'm trying to connect a GT-P5110 to Ubuntu (12.10 as well as 13.04) just like you seem to try. Does anyone know if it works on other systems?

I am having this issue too..
[ 37.151513] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[ 37.167861] usb 1-2: device descriptor read/8, error -75
[ 37.287940] usb 1-2: device descriptor read/8, error -75
[ 37.503921] usb 1-2: new high-speed USB device number 3 using xhci_hcd
[ 37.520265] usb 1-2: device descriptor read/8, error -75
[ 37.640343] usb 1-2: device descriptor read/8, error -75
[ 37.856292] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[ 37.872608] usb 1-2: device descriptor read/8, error -75
[ 37.992803] usb 1-2: device descriptor read/8, error -75
[ 38.208755] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 38.225032] usb 1-2: device descriptor read/8, error -75
[ 38.345139] usb 1-2: device descriptor read/8, error -75
[ 38.449017] hub 1-0:1.0: unable to enumerate USB device on port 2
Click to expand...
Click to collapse

I am having the exact same issue trying to root a Galaxy Tab 2 7.0, I too have only v3 USB ports, were you able to figure out a way around this?

Redmi note 9 deleted all partitions - phone dead, no turning on

Unfortunately, I deleted all partitions with 'bkerler/mtkclient' for trying to remove MI Account Verification.
Now the phone looks dead, no turning on, no fastboot mode, linux and windows don't see the phone at all.
Question : is now the TRASH the only remaining way or there is still a chance to rescue it ????
Greets

Oh.
Were you doing this on a Linux or Windows box?
Can you see in USB 0e8d/0003 or 0e8d/2000?

Hi, thanks for your help !
I operated in ubuntu 22.04 - software mtkclient 2.0 (github bkerler/mtkclient)
under ubuntu 22.04 now with command 'adb devices' none devices comes displayed,
under windows 10 os if I attach the phone via usb, the sysytem it ring in and out in loop for a plugged devices but no memory comes out to be used for storing files,
It seems really tuff this time, I am not optimistic !
Yes, I see many, probably for each partitions I deleted ?
Result with command lsusb :
Code:
lsusb
Bus 003 Device 081: ID 0e8d:0003 MediaTek Inc. MT6227 phone
Then with command dmesg | grep usb :
Code:
sudo dmesg | grep usb
...........
[ 1197.853581] usb 3-2: USB disconnect, device number 12
[ 1198.700237] usb 3-2: new high-speed USB device number 13 using xhci_hcd
[ 1198.848490] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1198.848497] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1203.368234] usb 3-2: USB disconnect, device number 13
[ 1204.932401] usb 3-2: new high-speed USB device number 14 using xhci_hcd
[ 1205.080695] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1205.080700] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1209.603143] usb 3-2: USB disconnect, device number 14
[ 1211.172537] usb 3-2: new high-speed USB device number 15 using xhci_hcd
[ 1211.320794] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1211.320800] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1215.837599] usb 3-2: USB disconnect, device number 15
[ 1217.400686] usb 3-2: new high-speed USB device number 16 using xhci_hcd
[ 1217.548976] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1217.548983] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1222.071995] usb 3-2: USB disconnect, device number 16
[ 1223.636870] usb 3-2: new high-speed USB device number 17 using xhci_hcd
[ 1223.785130] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1223.785136] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1228.306519] usb 3-2: USB disconnect, device number 17
[ 1229.869015] usb 3-2: new high-speed USB device number 18 using xhci_hcd
[ 1230.017275] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1230.017281] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1234.540893] usb 3-2: USB disconnect, device number 18
[ 1236.993149] usb 3-2: new high-speed USB device number 20 using xhci_hcd
[ 1237.141447] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1237.141453] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1240.775464] usb 3-2: USB disconnect, device number 20
[ 1242.337280] usb 3-2: new high-speed USB device number 21 using xhci_hcd
[ 1242.485596] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1242.485603] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1247.009965] usb 3-2: USB disconnect, device number 21
[ 1283.686113] usb 3-2: new high-speed USB device number 22 using xhci_hcd
[ 1283.834401] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1283.834407] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1284.416216] usb 3-2: USB disconnect, device number 22
[ 1285.978136] usb 3-2: new high-speed USB device number 24 using xhci_hcd
[ 1286.130454] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1286.130461] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1290.650196] usb 3-2: USB disconnect, device number 24
[ 1292.214284] usb 3-2: new high-speed USB device number 25 using xhci_hcd
[ 1292.362624] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1292.362629] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1296.884820] usb 3-2: USB disconnect, device number 25
[ 1298.450407] usb 3-2: new high-speed USB device number 26 using xhci_hcd
[ 1298.598753] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1298.598759] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1303.119685] usb 3-2: USB disconnect, device number 26
[ 1304.682518] usb 3-2: new high-speed USB device number 27 using xhci_hcd
[ 1304.830755] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1304.830762] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1309.354308] usb 3-2: USB disconnect, device number 27
[ 1310.918632] usb 3-2: new high-speed USB device number 28 using xhci_hcd
[ 1311.066960] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1311.066966] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1315.588837] usb 3-2: USB disconnect, device number 28
[ 1317.150735] usb 3-2: new high-speed USB device number 29 using xhci_hcd
[ 1317.299028] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1317.299034] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1321.822984] usb 3-2: USB disconnect, device number 29
[ 1344.423165] usb 3-2: new high-speed USB device number 30 using xhci_hcd
[ 1344.571498] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1344.571504] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1346.759523] usb 3-2: USB disconnect, device number 30
[ 1348.323227] usb 3-2: new high-speed USB device number 31 using xhci_hcd
[ 1348.471517] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1348.471524] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1352.993785] usb 3-2: USB disconnect, device number 31
[ 1354.555334] usb 3-2: new high-speed USB device number 32 using xhci_hcd
[ 1354.703604] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1354.703610] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1359.227829] usb 3-2: USB disconnect, device number 32
[ 1360.791422] usb 3-2: new high-speed USB device number 33 using xhci_hcd
[ 1360.939739] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1360.939745] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1365.462473] usb 3-2: USB disconnect, device number 33
[ 1367.031486] usb 3-2: new high-speed USB device number 34 using xhci_hcd
[ 1367.179797] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1367.179803] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1371.696458] usb 3-2: USB disconnect, device number 34
[ 1373.263582] usb 3-2: new high-speed USB device number 35 using xhci_hcd
[ 1373.411750] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1373.411752] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1377.930929] usb 3-2: USB disconnect, device number 35
[ 1379.511623] usb 3-2: new high-speed USB device number 36 using xhci_hcd
[ 1379.663980] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1379.663987] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1384.165640] usb 3-2: USB disconnect, device number 36
[ 1385.727770] usb 3-2: new high-speed USB device number 37 using xhci_hcd
[ 1385.880075] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1385.880080] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1390.400420] usb 3-2: USB disconnect, device number 37
[ 1391.967823] usb 3-2: new high-speed USB device number 38 using xhci_hcd
[ 1392.116001] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1392.116009] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1396.634523] usb 3-2: USB disconnect, device number 38
[ 1398.203924] usb 3-2: new high-speed USB device number 39 using xhci_hcd
[ 1398.356032] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1398.356035] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1402.868909] usb 3-2: USB disconnect, device number 39
[ 1404.432001] usb 3-2: new high-speed USB device number 40 using xhci_hcd
[ 1404.580140] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1404.580146] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1409.103339] usb 3-2: USB disconnect, device number 40
[ 1410.668091] usb 3-2: new high-speed USB device number 41 using xhci_hcd
[ 1410.816364] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1410.816369] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1415.337144] usb 3-2: USB disconnect, device number 41
[ 1416.900174] usb 3-2: new high-speed USB device number 42 using xhci_hcd
[ 1417.052290] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1417.052293] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1421.571611] usb 3-2: USB disconnect, device number 42
[ 1423.144205] usb 3-2: new high-speed USB device number 43 using xhci_hcd
[ 1423.296392] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1423.296399] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1427.805727] usb 3-2: USB disconnect, device number 43
[ 1429.372281] usb 3-2: new high-speed USB device number 44 using xhci_hcd
[ 1429.524540] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1429.524543] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1434.039545] usb 3-2: USB disconnect, device number 44
[ 1435.612359] usb 3-2: new high-speed USB device number 45 using xhci_hcd
[ 1435.761558] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1435.761562] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1440.273671] usb 3-2: USB disconnect, device number 45
[ 1441.848416] usb 3-2: new high-speed USB device number 46 using xhci_hcd
[ 1442.000604] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1442.000610] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1446.507555] usb 3-2: USB disconnect, device number 46
[ 1448.076511] usb 3-2: new high-speed USB device number 47 using xhci_hcd
[ 1448.224754] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1448.224757] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1452.742524] usb 3-2: USB disconnect, device number 47
[ 1454.304590] usb 3-2: new high-speed USB device number 48 using xhci_hcd
[ 1454.456747] usb 3-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 1454.456751] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

No, you're seeing one device thrashing.
If you're lucky you can catch it with MTK and write something.
(Sorry, I'm better with EDL than MTK. But I did just pull a boot with MTK.)

wich software can I use for this last try ?
magisk ?
mtkclient it seems to doesn't see the phone because adb see nothing.
Your software suggestion for this last try ?
thanks anyway
It can be that, actually the system recognize my device as MT6227 (before the trouble was appearing as MT6768/MT6769), and in this case, mtkclient don't recognize my device just because in its folder there is no such mt6227_payload.bin ???
Is there exist a mt6227_payload.bin ??? Is this a possible way ?

No, you're mixing up everything.
This is all MediaTek, nothing to do with ADB, fastboot or Magisk.
MediaTek has two bootloader modes, you're in one of them,
Your SoC is Mediatek MT6769Z. There is no specifice payload for MT6769.
If it's close enough to the MT6768, there is mt6768_payload.bin
Sorry, I don't know a lot.

I moved to windows 10, and there I had a fantastic discover, mtkclient there it's working.
Replaced Firmware and Vendor files downloaded from Original site : https://xiaomifirmwareupdater.com/archive/miui/merlin/
I did simply by 'write partition' command and then selecting then the VENDOR and FIRMWARE folders and let the app doing automatic replacement, it has completed !
Now I don't know how to move forward because the phone still doesn't turn on and in linux 'adb devices' not still recognize the device
I use to flash ROM with XIAOMI-TOOL MIFLASH for-Linux-by-IceMan, a great and easy program, but linux still doesn't give me access to the phone.
So the only way is in windows 10, wich App do you suggest me to use here ?
Is there a way to flash the ROM via mtkclient or the only way is SP Flash Tool ?
Thanks for your support

It will always have an option for rescue.
You need to flash the rom again using sp flash tool.
Just it.

in SP Flash Tool seems to be very tricky :
> I connect to MTKClient and let the device be recognized and connected
> then move to SP Flash tool, choice the UART COM Port I see recognized under MediaTek Port_V1633 (COM3 or 4)
But when I press download, I wait and get ERROR CODE :
ERROR : STATUS_ERR (0xC0010001)
or
ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
where am i wrong ?
For what I see, I guess is a driver issue :
Considering to flash ROM via SPFlash Toll with support of MTKClient for auth bypass, wich USB Driver is required ? :
USBdk (required for MTKClient)
MediaTek SP Driver, LibUSB-Win32 are these required ???
Starting without auth-bypass trough MTKClient, with the only SP Flash Tool, I see the usb DEVICE (COM) switch on and off all the time...
need help

Is it possible ... , after installing a rom_engeneered, fixing NVram with modem-meta, replace original IMEI, and at least flashing an original_rom, ... to see android-desktop working back and skipping from that disgusting boot-loop-recovery ??
This question comes because I was able to fix this, but don't know how I did.
And now after so many test I did, some mistakes came, and I got back to 'zero-point', zero-zero-point (zio-cann!!!), and don't find the way back !!
want to see android's icons again ... boot-loop is bad !
heelllllllllll (ppppp)