Another one bites the dust...?

[Guest kapasaki]

Hello,

sorry if this is a known or recurrent topic. I tried to search, but didn't quite find cases like this one. If such exist, though, I'd greatly appreciate if someone could give me link(s) to them.

Right, here's the gist of my predicament... :)

I have a Huawei Ascend G300 phone, that I successfully upgraded with a CyanogenMod 4.4.4 nightly build. Or, so I thought for 10 hours, or so.

In other words, after the upgrade it worked for the rest of the day just fine, but at some point during the following night the phone died. In the morning it was off, and did not start anymore, nor start recharging the battery.

Yes, the phone has the infamous Hynix memory, and yes, I knew the risks.

Now the phone doesn't react in any way to pressing the power button, or the combinations power + volume down, or power + volume up.

I also tried to start the forced upgrade process with an official dload/update.app from Huawei, but the phone just doesn't do anything with the vol up + vol down + power key combination.

If I plug it in a Linux PC, and try the "sudo ./fastboot-linux devices" command, I get nothing, so that route is blocked (I suppose).

However, some life still exists in the beast. I get the following output with dmesg:

[  509.170083] usb 2-3: new high-speed USB device number 3 using ehci-pci
[  509.295870] usb 2-3: string descriptor 0 malformed (err = -61), defaulting to 0x0409
[  509.399973] usbcore: registered new interface driver usbserial
[  509.400130] usbcore: registered new interface driver usbserial_generic
[  509.400183] usbserial: USB Serial support registered for generic
[  509.433656] usbcore: registered new interface driver qcserial
[  509.433866] usbserial: USB Serial support registered for Qualcomm USB modem
[  509.433901] qcserial 2-3:1.0: Qualcomm USB modem converter detected
[  509.434072] usb 2-3: Qualcomm USB modem converter now attached to ttyUSB0
[  509.455962] usbcore: registered new interface driver zte_ev
[  509.456114] usbserial: USB Serial support registered for zte_ev

And the device node "/dev/ttyUSB0" appears.

But I don't suppose that would help me much, or could it?

I would appreciate, if someone with a Linux box could show me his/her corresponding dmesg output.

The battery is probably OK, because it hasn't showed any signs of dying or getting old so far, and I measured a healthy looking 3,7 volts on the terminals. However, just to eliminate the battery failure option, could someone tell me if the phone should start up without the battery, with a recharger only, or if connected to a PC. (If it should, and mine doesn't, then I'd know for sure it's the phone that's broken.)

I'm guessing the phone just happened to die of natural causes, not because of the upgrading I did, since it died at least 10 hours after the upgrade. Or what do you guys think?

Any hints, tips, guidance, help, pity, gloating, recommendations? ;)

Thanks, and sorry for the long post.
 

[Guest Netphilos]

Hello,

sorry if this is a known or recurrent topic. I tried to search, but didn't quite find cases like this one. If such exist, though, I'd greatly appreciate if someone could give me link(s) to them.

Right, here's the gist of my predicament... :)

I have a Huawei Ascend G300 phone, that I successfully upgraded with a CyanogenMod 4.4.4 nightly build. Or, so I thought for 10 hours, or so.

In other words, after the upgrade it worked for the rest of the day just fine, but at some point during the following night the phone died. In the morning it was off, and did not start anymore, nor start recharging the battery.

Yes, the phone has the infamous Hynix memory, and yes, I knew the risks.

Now the phone doesn't react in any way to pressing the power button, or the combinations power + volume down, or power + volume up.

I also tried to start the forced upgrade process with an official dload/update.app from Huawei, but the phone just doesn't do anything with the vol up + vol down + power key combination.

If I plug it in a Linux PC, and try the "sudo ./fastboot-linux devices" command, I get nothing, so that route is blocked (I suppose).

However, some life still exists in the beast. I get the following output with dmesg:

[  509.170083] usb 2-3: new high-speed USB device number 3 using ehci-pci

[  509.295870] usb 2-3: string descriptor 0 malformed (err = -61), defaulting to 0x0409

[  509.399973] usbcore: registered new interface driver usbserial

[  509.400130] usbcore: registered new interface driver usbserial_generic

[  509.400183] usbserial: USB Serial support registered for generic

[  509.433656] usbcore: registered new interface driver qcserial

[  509.433866] usbserial: USB Serial support registered for Qualcomm USB modem

[  509.433901] qcserial 2-3:1.0: Qualcomm USB modem converter detected

[  509.434072] usb 2-3: Qualcomm USB modem converter now attached to ttyUSB0

[  509.455962] usbcore: registered new interface driver zte_ev

[  509.456114] usbserial: USB Serial support registered for zte_ev

And the device node "/dev/ttyUSB0" appears.

But I don't suppose that would help me much, or could it?

I would appreciate, if someone with a Linux box could show me his/her corresponding dmesg output.

The battery is probably OK, because it hasn't showed any signs of dying or getting old so far, and I measured a healthy looking 3,7 volts on the terminals. However, just to eliminate the battery failure option, could someone tell me if the phone should start up without the battery, with a recharger only, or if connected to a PC. (If it should, and mine doesn't, then I'd know for sure it's the phone that's broken.)

I'm guessing the phone just happened to die of natural causes, not because of the upgrading I did, since it died at least 10 hours after the upgrade. Or what do you guys think?

Any hints, tips, guidance, help, pity, gloating, recommendations? ;)

Thanks, and sorry for the long post.

 

Hello, kapasaki:

 

As for your first petition, this is the output of my dmesg, connecting my turn off huawei G300:

 

[  147.186179] usb 1-1.5: new high-speed USB device number 4 using ehci-pci

[  147.273305] usb 1-1.5: New USB device found, idVendor=12d1, idProduct=1038

[  147.273311] usb 1-1.5: New USB device strings: Mfr=2, Product=3, SerialNumber=4

[  147.273315] usb 1-1.5: Product: Ascend G300

[  147.273318] usb 1-1.5: Manufacturer: HUAWEI

[  147.273322] usb 1-1.5: SerialNumber: 5C7D5E02EE31

[  147.275105] usb-storage 1-1.5:1.0: USB Mass Storage device detected

[  147.275256] scsi7 : usb-storage 1-1.5:1.0

[  148.279378] scsi 7:0:0:0: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

[  148.279734] sd 7:0:0:0: Attached scsi generic sg6 type 0

[  148.280941] scsi 7:0:0:1: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

[  148.281279] sd 7:0:0:1: Attached scsi generic sg7 type 0

[  148.285535] sd 7:0:0:0: [sdf] Attached SCSI removable disk

[  148.286889] sd 7:0:0:1: [sdg] Attached SCSI removable disk

 

I quick looks shows that my opensuse 13.1x86 has detected the phone and is treating it as a storage. Yours, seems to show there is no access whatsoever to any kind of storage.

 

This is the output of dmesg command when the phone is turned on:

[ 1172.323981] usb 1-1.5: new high-speed USB device number 5 using ehci-pci

[ 1172.409781] usb 1-1.5: New USB device found, idVendor=12d1, idProduct=1038

[ 1172.409787] usb 1-1.5: New USB device strings: Mfr=2, Product=3, SerialNumber=4

[ 1172.409791] usb 1-1.5: Product: Android

[ 1172.409794] usb 1-1.5: Manufacturer: Android

[ 1172.409797] usb 1-1.5: SerialNumber: 5C7D5E02EE31

[ 1172.410476] usb-storage 1-1.5:1.0: USB Mass Storage device detected

[ 1172.410640] scsi8 : usb-storage 1-1.5:1.0

[ 1173.414944] scsi 8:0:0:0: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

[ 1173.415263] sd 8:0:0:0: Attached scsi generic sg6 type 0

[ 1173.417946] scsi 8:0:0:1: Direct-Access     Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

[ 1173.418331] sd 8:0:0:1: Attached scsi generic sg7 type 0

[ 1173.419936] scsi 8:0:0:2: CD-ROM            Linux    File-CD Gadget   0000 PQ: 0 ANSI: 2

[ 1173.425637] sr1: scsi3-mmc drive: 0x/0x caddy

[ 1173.425827] sr 8:0:0:2: Attached scsi CD-ROM sr1

[ 1173.425906] sr 8:0:0:2: Attached scsi generic sg8 type 5

[ 1173.426417] sd 8:0:0:0: [sdf] Attached SCSI removable disk

[ 1173.429566] sd 8:0:0:1: [sdg] Attached SCSI removable disk

 

 

 

 

Hope to have help you.

Edited September 25, 2014 by Netphilos

[Guest kapasaki]

Hello Netphilos,

 

thanks for your reply. It looks like my phone is more or less a goner... oh well, these things happen.

[Guest kapasaki]

Actually, if someone could still do a little favour for me... if you have a functional G300 battery (HB5N1H), and a multimeter, could you please measure and let me know the resistance between the minus (-) terminal and the middle terminal.

 

Thanks!