Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar
Related
Hello!
How do i mount my HTC hero on ubuntu?
I have tried everything i know about.
Here's some info about it!
It's connected to the machine now.
Code:
[email protected]:~# dmesg|tail
[167350.745833] VFS: Can't find a valid FAT filesystem on dev sda2.
[167350.746019] qnx4: wrong fsid in superblock.
[167392.539945] FAT: bogus number of reserved sectors
[167392.539952] VFS: Can't find a valid FAT filesystem on dev loop0.
[167392.540057] qnx4: wrong fsid in superblock.
[167429.744606] attempt to access beyond end of device
[167429.744614] loop0: rw=0, want=4, limit=2
[167429.744619] EXT3-fs: unable to read superblock
[167584.269145] FAT: bogus number of reserved sectors
[167584.269154] VFS: Can't find a valid FAT filesystem on dev loop0.
[email protected]:~# sfdisk -l
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0 - 0 0 0 Empty
/dev/sda2 * 0+ 18768- 18769- 150759362 f W95 Ext'd (LBA)
/dev/sda3 18768+ 19457- 689- 5529600 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 3916+ 18768- 14853- 119300096 7 HPFS/NTFS
/dev/sda6 0+ 3915 3916- 31455207 83 Linux
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 30G 3.3G 25G 12% /
udev 438M 276K 438M 1% /dev
none 438M 0 438M 0% /dev/shm
none 438M 200K 438M 1% /var/run
none 438M 0 438M 0% /var/lock
none 438M 0 438M 0% /lib/init/rw
/dev/sda5 114G 30G 85G 26% /mnt/sda5
/dev/sda6 30G 3.3G 25G 12% /mnt/sda6
[email protected]:~#
First, you should have your data partition of your SD card formatted as FAT32.
Then connect your Hero to your PC using original USB table (you can use non-original, but not everyone of them works).
You should see notification on hero about connected USB, click on this notification and Hero will ask you if you want to connect it as storage device.
Linux should now recognize your Hero as standard USB flash drive.
This works for me.
hELLO!
How can i format my data-partition on my SD-card to FAT32?
And when i connect the hero to the machine, there is no notification on the notification bar!
sorry for bad english.
Broken USB
Hmm, it seems you have some trouble with USB since Hero does not recognize it. My dmesg looks like this, when I connect my Hero (but before I enable it as storage device):
Code:
[47693.001261] usb 6-2: new full speed USB device using uhci_hcd and address 2
[47693.130013] usb 6-2: device descriptor read/64, error -71
[47693.370011] usb 6-2: device descriptor read/64, error -71
[47693.600011] usb 6-2: new full speed USB device using uhci_hcd and address 3
[47693.730011] usb 6-2: device descriptor read/64, error -71
[47693.971260] usb 6-2: device descriptor read/64, error -71
[47694.201263] usb 6-2: new full speed USB device using uhci_hcd and address 4
[47694.621263] usb 6-2: device not accepting address 4, error -71
[47694.680042] hub 6-0:1.0: unable to enumerate USB device on port 2
[47694.961263] usb 2-4: new high speed USB device using ehci_hcd and address 3
[47695.123330] usb 2-4: configuration #1 chosen from 1 choice
[47695.526904] Initializing USB Mass Storage driver...
[47695.527144] scsi6 : SCSI emulation for USB Mass Storage devices
[47695.527234] usb-storage: device found at 3
[47695.527236] usb-storage: waiting for device to settle before scanning
[47695.527250] usbcore: registered new interface driver usb-storage
[47695.527253] USB Mass Storage support registered.
[47700.521271] usb-storage: device scan complete
[47700.523257] scsi 6:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
[47700.523603] sd 6:0:0:0: Attached scsi generic sg3 type 0
[47700.533243] sd 6:0:0:0: [sdc] Attached SCSI removable disk
i'd try repartitioning the card, looks like a corrupted filesystem.
I don't think repartitioning will help here. /dev/sda is the disk in his computer, because /dev/sda6 is mounted as /. The dmesg output doesn't say anything about /dev/sdb, and there is not even anything about trying to connect a USB device.
My guess is either the cable is bad, or the USB socket on the computer is not connected.
Hi,
I get the same - in Windows it comes up as an unregognised device, and in linux i get
[ 1724.760062] usb 7-1: new full speed USB device using uhci_hcd and address 18
[ 1724.890058] usb 7-1: device descriptor read/64, error -71
[ 1725.130036] usb 7-1: device descriptor read/64, error -71
[ 1725.360077] usb 7-1: new full speed USB device using uhci_hcd and address 19
[ 1725.492549] usb 7-1: device descriptor read/64, error -71
[ 1725.730242] usb 7-1: device descriptor read/64, error -71
[ 1725.960394] usb 7-1: new full speed USB device using uhci_hcd and address 20
[ 1726.380063] usb 7-1: device not accepting address 20, error -71
[ 1726.500053] usb 7-1: new full speed USB device using uhci_hcd and address 21
[ 1726.920281] usb 7-1: device not accepting address 21, error -71
[ 1726.920302] hub 7-0:1.0: unable to enumerate USB device on port 1
and no option on the Hero to mount the partition. I'm open to suggestions
Try another cable and/or another USB port. E.g. the USB ports at the back of your PC are directly soldered to the mainboard, without a shoddy connector and cable in between.
I was trying to restore IMEI and stuffs using QPST.
1. *#7284# and selected USB-> Modem
2. Connected to Windows XP, Device Manager shows 7CDCs as the device with yellow mark showing cannot install device.
3. Tried almost every drivers on the earth.
Connecting this to a linux pc i found the following logs:
103722.210314] usb 1-8: default language 0x0409
[103722.212814] usb 1-8: udev 15, busnum 1, minor = 14
[103722.212817] usb 1-8: New USB device found, idVendor=1519, idProduct=0020
[103722.212821] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[103722.212824] usb 1-8: Product: 7 CDCs
[103722.212827] usb 1-8: Manufacturer: Comneon
[103722.212829] usb 1-8: SerialNumber: 004999010640000
[103722.212964] usb 1-8: usb_probe_device
[103722.212969] usb 1-8: configuration #1 chosen from 1 choice
Doing some dirty digging I found the following in Samsung open source code:
/drivers/usb/core/quirks.c
/* IMC_MAIN - XMM6260, XMM6262 */
{ USB_DEVICE(0x1519, 0x0020), .driver_info = USB_QUIRK_HSIC_TUNE },
I dont see many people reporting this problem.
I saw the same behaviour with Galaxy R too that in diag mode, it is sending idVendor=1519, idProduct=0020.
Anyone faced this before? Any help would be great.
Hey mate, did you ever find a solution to this problem? Im also having trouble connective my phone to QPST.
Hello friends,
I am facing same problem with SGS2.
Please help.
Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!
i'm solved the problem by replacing the nucleus
Hello,
I tested with three different REDMI 3 devices and three different rom versions and have the following problem:
initially everything with connecting an external usb camera was ok. My usb camera app received events asking for permissions for using usb camera. But after 3 or 4 full charges the app stopped receiving permissions. I checked with couple other apps but again no permission. If my battery drops under 60% suddenly everything is ok again and the app detects the camera. It is stranger, that before full detect of the camera the app starts some kind of permission loop. I click allow and after 2 seconds the permission dialog shows again and so on... I checked the source code and appears my USBManager returns empty device list. For me it looks like some kind of battery optimizer or usb state optimizer doing it. I will be more than happy if someone can help me with this issue. Additionally I checked with all other stock rom version. It is all the same.
Here is some log from dmsg.
Code:
<6>[12449.627983] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12449.647323] psy->name:usb
<6>[12449.652992] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12449.653558] healthd: battery l=94 v=4240 t=22.3 h=2 st=4 c=382 chg=
<6>[12449.744320] msm_hsusb_host msm_hsusb_host: EHCI Host Controller
<6>[12449.744844] msm_hsusb_host msm_hsusb_host: new USB bus registered, assigned bus number 1
<6>[12449.751356] msm_hsusb_host msm_hsusb_host: irq 166, io mem 0x078d9000
<6>[12449.769480] msm_hsusb_host msm_hsusb_host: USB 2.0 started, EHCI 1.00
<6>[12449.769624] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[12449.769636] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[12449.769646] usb usb1: Product: EHCI Host Controller
<6>[12449.769656] usb usb1: Manufacturer: Linux 3.10.49-perf-g48b885e ehci_hcd
<6>[12449.769665] usb usb1: SerialNumber: msm_hsusb_host
<6>[12449.772688] hub 1-0:1.0: USB hub found
<6>[12449.772729] hub 1-0:1.0: 1 port detected
<6>[12449.876761] msm_otg 78d9000.usb: USB in low power mode
<6>[12450.296922] msm_otg 78d9000.usb: USB exited from low power mode
<6>[12450.519306] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
<6>[12450.949089] usb 1-1: new high-speed USB device number 3 using msm_hsusb_host
<6>[12451.619450] usb 1-1: new high-speed USB device number 5 using msm_hsusb_host
<11>[12452.316729] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<11>[12453.339456] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12453.759449] usb 1-1: new high-speed USB device number 13 using msm_hsusb_host
<6>[12455.879543] usb 1-1: new high-speed USB device number 21 using msm_hsusb_host
<6>[12456.212015] XXX::smb358_get_prop_batt_status:reg=0x0
<6>[12456.216663] psy->name:rk-bat
<6>[12456.216678] status=3, percent=94
<6>[12456.216684] status=3, percent=94
<6>[12456.222182] XXX::smb358_get_prop_batt_status:reg=0x0
<12>[12456.222723] healthd: battery l=94 v=4248 t=22.4 h=2 st=4 c=401 chg=
<6>[12456.319281] usb 1-1: new high-speed USB device number 22 using msm_hsusb_host
<11>[12457.382047] init: Warning! Service eyecare needs a SELinux domain defined; please fix!
<6>[12457.499222] usb 1-1: new high-speed USB device number 26 using msm_hsusb_host
<11>[12458.407239] init: Warning! Service coloradjust needs a SELinux domain defined; please fix!
<6>[12458.899381] usb 1-1: new high-speed USB device number 31 using msm_hsusb_host
<6>[12459.339269] usb 1-1: new high-speed USB device number 32 using msm_hsusb_host
Im now at tampered rom (the rom says miui global 7.1 | 7.1.1.0.0 stable) it not real global rom! gold colour. but i dont have any problem with otg or battery drops. All working fine. Except a few settings turns back to default if i reset the device. But its doesnt bothered me much.
I am trying to resurrect my old Samsung Galaxy i5500. A couple of years ago I tried installing some custom rom but failed and bricked the phone. The boot process halts at the Samsung logo (the very first logo to appear.)
Putting the phone into recovery mode (using the volume down button + center button + power button) works, at least i presume that it works - the logo with the android shoveling dirt and the word "Downloading..." beneath it appears - but neither adb nor fastboot can see the device.
My troubleshooting so far:
Code:
[email protected]:~# dmesg
...
[823736.755555] usb 2-1.1: new high-speed USB device number 6 using ehci-pci
[823736.851772] usb 2-1.1: unable to get BOS descriptor
[823736.857819] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=6601
[823736.857829] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[823736.857835] usb 2-1.1: Product: MSM7x27
[823736.857839] usb 2-1.1: Manufacturer: Sasmsung
[823739.903177] cdc_acm 2-1.1:2.0: ttyACM0: USB ACM device
[823739.903553] usbcore: registered new interface driver cdc_acm
[823739.903557] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[823761.102222] cdc_acm 2-1.1:2.0: failed to set dtr/rts
[email protected]:~# lsusb
...
Bus 002 Device 011: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
...
[email protected]:~# adb devices
List of devices attached
[email protected]:~# fastboot devices
[email protected]:~#
I am running Lubuntu 12.04 on my laptop.
What do I need to do to be able to connect to the phone using adb and fastboot?
Thanks!
The "recovery mode" that you mentioned, is actually download mode and it's used to flash packages with Odin.
Use it to flash a custom recovery and then use that to flash a custom ROM. Format /system and /data as ext4 before flashing the ROM.
Sent from my LG G2 Mini using XDA Labs