SP Flash tool crashed after the first step (red bar, 100%).
Now when I connect it, it appears in Device manager as DA USB VCOM Port (COM5), but SP Flash never detects it (I am on 64-bit Win7), and I can't upgrade or upload firmware.
So how can I get this device alive again ? Screen keeps staying black. Before it showed battery status.
I tried to connect in while running VMWare, connecting all USB to Linux, and all I see is like below. It goes directly to the DA USB Port (Product 2001). So no preloader. So how can I salvage it ?
[ 52.150514] [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 460.866849] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 461.214431] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2001
[ 461.214435] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 461.282544] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
[ 461.285440] usbcore: registered new interface driver cdc_acm
[ 461.285441] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
I recovered my bricked G708
I had the same issue after trying to flash the 1.04 firmware. After a few seconds my SP-flashtool became unresponsive and left me with a bricked (black screen all the way) G708. Tried al kinds of tricks, drivers and tools but neither the flash-tool not the MTK droid tools recognized the thing upon connecting. Ultimately:
1. I pried the thing open (remove the 3 tiny screws near the SIM and TF card slot).
2. Disconnected the battery (on my device it is not soldered on the logic board).
3. Reconnected the battery.
4. Coonected the USB cable with SP-flash running in download mode......success!
I am a happy camper again, hope it will solve your problem.
Beste regards,
EP
I have one that shows colorfly logo and 100% battery when connected to the pc (win7 x86).
What to do now?
Related
Anyone using fastboot with linux?
I only get adb running using debian squeeze and this udev rule:
Code:
#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
So I have to boot windows to flash boot images
Greetz,
scheich
no one???
*push*
Should be in latest sdk?
Compile can be a ***** so grab this
http://www.multiupload.com/91QOOXZHPY
Wow, seems, that my fastboot binary was too old.
Thank You a lot!
dmesg
Code:
[ 843.649189] usb 3-4: new high speed USB device using ehci_hcd and address 7
[ 843.795440] usb 3-4: New USB device found, idVendor=0fce, idProduct=adde
[ 843.795449] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 843.795456] usb 3-4: Product: S1Boot Download
[ 843.795461] usb 3-4: Manufacturer: Sony Ericsson Mobile Communications AB
[ 843.795680] usb 3-4: configuration #1 chosen from 1 choice
[ 884.106276] usb 3-4: USB disconnect, address 7
[ 922.884299] usb 3-4: new high speed USB device using ehci_hcd and address 8
[ 923.029670] usb 3-4: New USB device found, idVendor=0fce, idProduct=0dde
[ 923.029679] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 923.029686] usb 3-4: Product: S1Boot Fastboot
[ 923.029691] usb 3-4: Manufacturer: Sony Ericsson Mobile Communications AB
[ 923.029697] usb 3-4: SerialNumber: BX852J5PT5&ZLI
[ 923.029925] usb 3-4: configuration #1 chosen from 1 choice
fastboot-linux devices
Code:
BX852J5PT5&ZLI fastboot
Edit: Oh well now I feel stupid. I guess driver signature enforcement isn't permanent - you have to do it when you want to install a driver.
Hi there,
I was following this guide: androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
but I'm stuck at the APX part, I can't install the driver. why do you hate me windows??
This is on windows 8 64bit, using Universal_Naked_Driver_0.72. Are there any other drivers?
Error message: "The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering."
Screenshot: see attached file
I have disabled driver signature enforcement..
Tried on linux as well but can't even get it properly connected. Here's what i see in dmesg:
[ 659.822881] usb 2-1.7: new high-speed USB device number 15 using ehci_hcd
[ 664.897952] usb 2-1.7: device descriptor read/64, error -71
[ 670.077009] usb 2-1.7: device descriptor read/64, error -71
[ 670.252839] usb 2-1.7: new high-speed USB device number 16 using ehci_hcd
[ 675.327879] usb 2-1.7: device descriptor read/64, error -71
[ 680.506820] usb 2-1.7: device descriptor read/64, error -71
[ 680.682645] usb 2-1.7: new high-speed USB device number 17 using ehci_hcd
[ 686.085269] usb 2-1.7: device not accepting address 17, error -71
[ 686.157292] usb 2-1.7: new high-speed USB device number 18 using ehci_hcd
[ 691.564009] usb 2-1.7: device not accepting address 18, error -71
[ 691.564147] hub 2-1:1.0: unable to enumerate USB device on port 7
Not sure what to try now, any suggestions are appreciated!
You have to disable signature something.... Driver signature... Windows thing... Im still stuck...
I had same problem on windows 8.1 64bit ....would not load drivers even with the signature thingy you say ...forgot what its called now lol .
In the end i used my laptop running vista and worked first time ....if you can try a different pc with a different os .
Karl
P.s dont forget to hold volume up key when powering up to get into APX mode
Hi,
the display of my galaxy s2 is dead and now I'm trying to recover all my data. If I connect the phone via usb to my pc Windows recognizes it as an usb media but I gain no access. Under Linux it gives me the following error
Code:
Unable to mount Android
Unable to open MTP device '[usb:002,003]'
Dmesg shows the following output
Code:
[ 135.856487] usb 2-1.2: Product: Android
[ 135.856492] usb 2-1.2: Manufacturer: Android
[ 135.856497] usb 2-1.2: SerialNumber: 0019adcd587f8e
[ 136.660306] usb 2-1.2: usbfs: process 2538 (pool) did not claim interface 0 before use
[ 136.730533] usb 2-1.2: reset high-speed USB device number 10 using ehci-pci
[ 136.823484] usb 2-1.2: usbfs: process 2538 (pool) did not claim interface 0 before use
[ 136.839730] usb 2-1.2: USB disconnect, device number 10
[ 137.038544] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
[ 137.139993] usb 2-1.2: New USB device found, idVendor=04e8, idProduct=6860
[ 137.140004] usb 2-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 137.140010] usb 2-1.2: Product: Android
[ 137.140015] usb 2-1.2: Manufacturer: Android
[ 137.140020] usb 2-1.2: SerialNumber: 0019adcd587f8e
lsusb also shows the galaxy s2:
Code:
Bus 002 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
but the problem is that adb devices -l says it's still offline, so I can't connect..
Code:
List of devices attached
0019adcd587f8e offline usb:2-1.2
Maybe the problem is that my device boots until the PIN screen and I can't unlock it .. but I think it could be even a hardware issue.. Also I have a custom rom + custom kernel installed (it's called ressurection remix)
So is there a chance to connect my device?
EDIT: now, after a few times of trying sometimes the devices connects correctly (Windows says it's an GT9100 and also Kies tries to connect) but I can't access it 'cause I cannot type in my PIN. Also adb now says I have an unauthorized device connected. So if I can change the last point with adb I think I'll gain access to my data.
EDIT2: I've figured out that I can boot into CWM and now adb says the device is connected as recovery. So I can use pull/push commands but the problem is that i cannot see all files.. trying to find a solution now for this one..
EDIT 3 : I'm recovering my data via the help I got here: techglen.
com/2014/01/29/
how-to-recover-data-using-adb-recovery-on-android/
(I'm not allowed to send links..)
SO I think the thread can be closed
Hi,
Yesterday my Nexus 9 was run-over by a car while it was in my backpack.
It still looks perfectly fine and was just slightly bent on the top where the mainboard sits.
The only problem is that it does not turn on
When I connect it to my laptop I get the following message:
Code:
[ 1951.490340] usb 1-4: new high-speed USB device number 19 using xhci_hcd
[ 1951.674845] usb 1-4: New USB device found, idVendor=0955, idProduct=7f13
[ 1951.674848] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1951.674850] usb 1-4: Product: APX
[ 1951.674852] usb 1-4: Manufacturer: NVIDIA Corp.
I searched a bit and it seems that it is currently not known how to enter the APX mode.
Does anybody have experience with nvflash and would like to help me to diagnose the tablet?
(I suspect a broken solder joint on the EMMC chip)
@donothingloop,
If you are feeling adventuresome, follow this guide to disassemble it and look for the issue > https://www.ifixit.com/Teardown/Nexus+9+Teardown/31425
Hi,
Have already disassembled it.
Found no defect which is visible to the eye.
I can connect to the phone no problem in fastboot mode, but in fastbootd mode I can see it constantly connecting and disconnecting in dmesg.
I've added spaces in the output below so it's easier to read. What the heck is going on? I can't move to flashing DE2117 if I can't get it to stay connected.
Code:
[38977.628840] usb 1-1: new high-speed USB device number 10 using xhci_hcd
[38977.782068] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38977.782085] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38977.782094] usb 1-1: Product: DE2118
[38977.782100] usb 1-1: Manufacturer: OnePlus
[38977.782106] usb 1-1: SerialNumber: 5cbbcabc
[38978.804973] usb 1-1: USB disconnect, device number 10
[38982.540853] usb 1-1: new high-speed USB device number 11 using xhci_hcd
[38982.690310] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38982.690324] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38982.690331] usb 1-1: Product: DE2118
[38982.690336] usb 1-1: Manufacturer: OnePlus
[38982.690341] usb 1-1: SerialNumber: 5cbbcabc
[38983.712907] usb 1-1: USB disconnect, device number 11
[38987.444919] usb 1-1: new high-speed USB device number 12 using xhci_hcd
[38987.594218] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38987.594232] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38987.594239] usb 1-1: Product: DE2118
[38987.594245] usb 1-1: Manufacturer: OnePlus
[38987.594249] usb 1-1: SerialNumber: 5cbbcabc
[38988.617117] usb 1-1: USB disconnect, device number 12
[38992.361028] usb 1-1: new high-speed USB device number 13 using xhci_hcd
[38992.510442] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38992.510456] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38992.510463] usb 1-1: Product: DE2118
[38992.510469] usb 1-1: Manufacturer: OnePlus
[38992.510473] usb 1-1: SerialNumber: 5cbbcabc
[38993.529038] usb 1-1: USB disconnect, device number 13
lurkio said:
I can connect to the phone no problem in fastboot mode, but in fastbootd mode I can see it constantly connecting and disconnecting in dmesg.
I've added spaces in the output below so it's easier to read. What the heck is going on? I can't move to flashing DE2117 if I can't get it to stay connected.
Code:
[38977.628840] usb 1-1: new high-speed USB device number 10 using xhci_hcd
[38977.782068] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38977.782085] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38977.782094] usb 1-1: Product: DE2118
[38977.782100] usb 1-1: Manufacturer: OnePlus
[38977.782106] usb 1-1: SerialNumber: 5cbbcabc
[38978.804973] usb 1-1: USB disconnect, device number 10
[38982.540853] usb 1-1: new high-speed USB device number 11 using xhci_hcd
[38982.690310] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38982.690324] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38982.690331] usb 1-1: Product: DE2118
[38982.690336] usb 1-1: Manufacturer: OnePlus
[38982.690341] usb 1-1: SerialNumber: 5cbbcabc
[38983.712907] usb 1-1: USB disconnect, device number 11
[38987.444919] usb 1-1: new high-speed USB device number 12 using xhci_hcd
[38987.594218] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38987.594232] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38987.594239] usb 1-1: Product: DE2118
[38987.594245] usb 1-1: Manufacturer: OnePlus
[38987.594249] usb 1-1: SerialNumber: 5cbbcabc
[38988.617117] usb 1-1: USB disconnect, device number 12
[38992.361028] usb 1-1: new high-speed USB device number 13 using xhci_hcd
[38992.510442] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 5.04
[38992.510456] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38992.510463] usb 1-1: Product: DE2118
[38992.510469] usb 1-1: Manufacturer: OnePlus
[38992.510473] usb 1-1: SerialNumber: 5cbbcabc
[38993.529038] usb 1-1: USB disconnect, device number 13
Click to expand...
Click to collapse
Try a different USB cable or port.
ethical_haquer said:
Try a different USB cable or port.
Click to expand...
Click to collapse
Fair suggestion. Just tried, 3 different cables in 3 different ports; one front port, 2 back ports (one from each 'stack').
Going to try my mint laptop, see if cycles the connection there too...
The bahvior is the same on the mint laptop. It's an HP 11th gen intel, my main is a 7th gen. Totally different chipsets, that's why I mention it. Probably a similar driver, but I cant think why that would matter. Mint isnt doing anything special with USB, so I assume the OS really isnt to blame. :/
lurkio said:
The bahvior is the same on the mint laptop. It's an HP 11th gen intel, my main is a 7th gen. Totally different chipsets, that's why I mention it. Probably a similar driver, but I cant think why that would matter. Mint isnt doing anything special with USB, so I assume the OS really isnt to blame. :/
Click to expand...
Click to collapse
Oh well, I guess you'll have to just search for a solution. Sorry I couldn't find a solution.