Redmi note 9 deleted all partitions - phone dead, no turning on - Redmi Note 9 Questions & Answers

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)

Related

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?

USB serial port not appearing in usb host api

I've installed the latest CyanogenMod build on my Galaxy Tab 8.9. When I connect my pl2303 usb serial port adapter to the device and open the "USB Device Info" app I can only see the device under the "Linux" tab, but not under the "Android" tab. Dmesg says:
Code:
<6>[ 241.823933] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 241.824139] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 1
<6>[ 241.832350] [ CONNECTOR_DRIVER (acc_notified,427) ] ACCESSORY=OTG : STATE=online
<6>[ 241.851514] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 241.871488] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 241.871702] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 241.871728] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 241.871749] usb usb1: Product: Tegra EHCI Host Controller
<6>[ 241.871767] usb usb1: Manufacturer: Linux 2.6.36.4-cyanogenmod+ ehci_hcd
<6>[ 241.871786] usb usb1: SerialNumber: tegra-ehci.0
<6>[ 241.876842] hub 1-0:1.0: USB hub found
<6>[ 241.876888] hub 1-0:1.0: 1 port detected
<6>[ 241.878664] tegra-otg tegra-otg: tegra_start_host-
<6>[ 241.878687] host_notify: ndev name=usb_otg: from state=2 -> to state=1
<6>[ 242.091586] usb 1-1: new full speed USB device using tegra-ehci and address 2
<6>[ 242.321825] usb 1-1: New USB device found, idVendor=067b, idProduct=2303
<6>[ 242.321881] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
<6>[ 242.321926] usb 1-1: Product: USB-Serial Controller D
<6>[ 242.321962] usb 1-1: Manufacturer: Prolific Technology Inc.
Why isn't the Android API recognizing the usb device?
I think you need insmod pl2303.ko. ask for it from your kernel developer
Sent from my GT-P1000 using xda premium

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

My H30-U10 doesn't turn on, just vibrates while screen is off

Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1
[email protected]/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1467879144.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,127))
and this is my dmesg log:
Code:
[ 3440.213018] usb 1-1.2: new high-speed USB device number 55 using ehci-pci
[ 3440.307101] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3440.307104] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3440.307105] usb 1-1.2: Product: MT65xx Preloader
[ 3440.307106] usb 1-1.2: Manufacturer: MediaTek
[ 3440.369300] cdc_acm 1-1.2:1.1: ttyACM1: USB ACM device
[ 3443.146921] usb 1-1.2: USB disconnect, device number 55
[ 3560.113932] usb 1-1.2: new high-speed USB device number 56 using ehci-pci
[ 3560.209002] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3560.209005] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3560.209007] usb 1-1.2: Product: MT65xx Preloader
[ 3560.209008] usb 1-1.2: Manufacturer: MediaTek
[ 3560.271453] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3563.563312] usb 1-1.2: USB disconnect, device number 56.
.
.
.
[ 3589.764652] usb 1-1.2: new high-speed USB device number 62 using ehci-pci
[ 3589.859355] usb 1-1.2: New USB device found, idVendor=0e8d, idProduct=2000
[ 3589.859359] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3589.859361] usb 1-1.2: Product: MT65xx Preloader
[ 3589.859363] usb 1-1.2: Manufacturer: MediaTek
[ 3589.921646] cdc_acm 1-1.2:1.1: ttyACM0: USB ACM device
[ 3590.138898] usb 1-1.2: USB disconnect, device number 62
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
So… Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
danialbehzadi said:
Hi
I was trying to unlock bootloader of my honor 3c (H30-U10) via SP Flash Tools. When I was connecting my phone without battery to PC via USB after clicking "Download" Button, the device kept vibrating and the connection got disconnected and connected every 3 seconds. The Screen was off during all of this process.
Here is my SP Flash Tool log:
and this is my dmesg log:
I also tried this with windows with all drivers installed, but I got the exact same result.
After a bunch of tries, now my phone doesn't even turns on. When I press power button with battery inserted, It vibrates every 20 seconds and the screen is always off, too. Connecting it to computer makes the same behavior described above.
Soâ?¦ Is there any way to make it fix? Since I can not access to fastboot mode and SP Flash Tools is not working either?
Click to expand...
Click to collapse
Do adb recognize your phone?!
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
danialbehzadi said:
Not at all. I took my device to Huawei center and they told me it's dead. So, I bought a new phone.
DON'T BY FROM HUAWEI!
Click to expand...
Click to collapse
Ahhh too bad :/
The same thing happened to my Samsung , i overcharged it via an unstable source, and the power IC was damaged, if i slid the battery in it would just keep vibrating and flash light turned on, it costed me PKR Rs.1200(USD.12$) to repair it......
Try SP Flashtool again, but with your battery in. Flashing recovery might be your best bet
Fixed your device?
hassanjavaid8181 said:
Fixed your device?
Click to expand...
Click to collapse
No. Threw it away!
danialbehzadi said:
No. Threw it away!
Click to expand...
Click to collapse
thats another way to fix issue

Categories

Resources