Hi all,
I'm really hoping someone can help.
This morning I applied the stock Google 4.2 (JOP40C) update from Google's factory images page using the supplied flash-all.sh script. The tablet applied the update, rebooted - and then I saw an error message saying an app had crashed, I believe it was the launcher but basically ignored it, and after pressing "okay" a few times I just held the power button until the power off dialog came up and I turned the tablet off.
Now it won't turn back on. I've tried the long-press method (I've tried 30 seconds, 1 minute, whilst plugged in to the mains, whilst plugged in to USB, volume up/down buttons held and not held) but so far it's as dead as a can of spam. I gave it a two hour charge on a wall charger, still no difference.
When attempting a stock flash / debrick via fastboot, fastboot just says "waiting for device" and waits forever. That's the same on Windows and on Linux, both systems usually work fine with ADB and fastboot.
When connected via USB to my Ubuntu PC, dmesg says:
Code:
[15660.333585] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[15665.328725] xhci_hcd 0000:03:00.0: Timeout while waiting for address device command
[15670.527680] xhci_hcd 0000:03:00.0: Timeout while waiting for address device command
[15670.731479] usb 3-1: device not accepting address 4, error -62
[15670.731578] xhci_hcd 0000:03:00.0: Bad Slot ID 3
[15670.731579] xhci_hcd 0000:03:00.0: Could not allocate xHCI USB device data structures
[15670.731582] hub 3-0:1.0: couldn't allocate port 1 usb_device
[15746.062340] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[15746.080922] usb 3-1: New USB device found, idVendor=0955, idProduct=7330
[15746.080925] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15746.080926] usb 3-1: Product: APX
[15746.080928] usb 3-1: Manufacturer: NVIDIA Corp.
[15746.080983] usb 3-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[15746.080986] usb 3-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
When attached via USB to my Windows PC, which usually works with Android / fastboot / APX devices just fine, I see an "unknown device" appear, with the status of:
Code:
Windows has stopped this device because it has reported problems. (Code 43)
Now I'm guessing it's dead and time to call Asus, but I wanted to check first. I went to back to the PC World store I bought it from and they say because it's a month old it's not their problem (over 21 days since purchase) so it has to go back to Asus.
Can anyone give any advice? Is there a way of re-flashing the bootloader some how without the need for fastboot? Is there something like nvflash for the N7 (I've seen this mentioned before here but it didn't seem to lead anywhere). Given that I can't get it to respond to fastboot nor ADB and as the screen never comes on I guess it's dead, but I'd welcome any hints before I call Asus - thanks in advance! :good:
Related
Hi,
From the bootloader I am unable to connect via USB or to flash from MicroSD.
I am running SPL-2.08.000 8G XE
I have magldr version 1.11 installed with a cyaogen mod 7 running on top of that.
On the PC, I am running Windows 7 x64.
When I run the bootloader (pwr on + hold vol dn) it says serial at the bottom and when I connect it to the Win7 machine one of three things happens.
1) Nothing.
2) On the Windows Desktop I get a message that "USB Device not Recognized"
3) On the phone, I get a white only bottom (no Serial or USB message)
This happens with both the routine to "disable drivers signature" by pressing F8, and without doing that.
I have also removed Windows Mobile Device Center 6.1 and the drv update. It still will not load. I have tried the AS drivers for Win7x64 and it says "no driver for this device found in this folder".
One possible solution was to flash the rom, via the MicroSD card, by renaming a .nbh to LEOIMG.nbh. However, I have tried several roms (1.66 roms, windows 6.5 roms, magldr 1.12 and magldr 1.13 nbhs) yet, the phone goes grey and says "Loading..." but nothing happens.
I am genuinely stuck.
I've been through a million forums and I can't seem to find a solution to my problem. As you can see I have tried several different solutions that I have found but none have worked.
My aim is to update magldr to ver 1.13 and load a newer rom.
Thank you,
P
"USB Device not Recognized"
This usually happens when cable is faulty or the jack.
It also happens when the phone is unresponsive.
crush said:
"USB Device not Recognized"
This usually happens when cable is faulty or the jack.
It also happens when the phone is unresponsive.
Click to expand...
Click to collapse
It charges... how else can I test the cable? Or the jack on the phone?
//edit: I have a spare cable and have tested it. It is not the cable. I have also cleaned the jack. A wiggle of the jack does not yeild any difference.
I went into Linux on my machine and ran
[email protected]:~$ dmesg | tail
[ 253.644057] usb 3-1: device descriptor read/64, error -62
[ 253.888054] usb 3-1: device descriptor read/64, error -62
[ 254.128061] usb 3-1: new low speed USB device using ohci_hcd and address 11
[ 254.269065] usb 3-1: device descriptor read/64, error -62
[ 254.512059] usb 3-1: device descriptor read/64, error -62
[ 254.752054] usb 3-1: new low speed USB device using ohci_hcd and address 12
[ 255.160725] usb 3-1: device not accepting address 12, error -62
[ 255.296064] usb 3-1: new low speed USB device using ohci_hcd and address 13
[ 255.705054] usb 3-1: device not accepting address 13, error -62
[ 255.705095] hub 3-0:1.0: unable to enumerate USB device on port 1
What I suppose is really unusual is that this has happened AND I'm unable to flash via MicroSD.
P
ok,
Are you using front USB port? if yes then try different port at back.
Because its strange on some motherboards that it stop reading properly from front usb's :-S this happened to me with my panasonic camera which wasn't readable at front but did work on back.
for more info you can goto these link
http://www.linux-usb.org/FAQ.html#ts6
I have an old Canadian Bell based Galaxy s4, with a dead screen. I'd like to try to get files off it, but did not enable usb debugging mode prior to the screen breaking.
Is there any way to access the file system on the phone in this situation? I've done a bit of looking around and can see that I should be able to access it via adb if I have usb debugging turned on, but debugging isn't on in this case.
I have usb connected the phone to my fedora machine and can see via dmesg that it does get detected. I can hear the thing start up, but beyond that I can't see anything else.
Googling around it sounds like I should be able to load a recover kernel, with debugging turned on if I use the right process, but I can't find enough into to get me going.
dmesg output is below just in case it helps...
.....................................................................................
[ 4104.343749] usb 2-2: USB disconnect, device number 6
[ 4180.261104] usb 2-2: new high-speed USB device number 7 using ehci-pci
[ 4180.376385] usb 2-2: New USB device found, idVendor=04e8, idProduct=6860
[ 4180.376390] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4180.376394] usb 2-2: Product: SAMSUNG_Android
[ 4180.376396] usb 2-2: Manufacturer: SAMSUNG
[ 4180.376399] usb 2-2: SerialNumber: ........
Any help is much appreciated!
If you can get a custom recovery on you can use adb without use debugging on. I assume you have an i337m. Try this with twrp http://galaxys4root.com/clockworkmodtwrp-recoveries/
Sent from my Nexus 9 using XDA Free mobile app
If you have a custom recovery plug it up to hdmi thru HML and use the TV for the screen. Hopefully the touchscreen still works. This worked for mine. No lcd but the digitizer was still good.
Hello,
It's been a while since I have been facing the problem described in the title. Only now I've managed to get some time to investigate the issue. I'm using LineageOS 15.1.
I was using Lineage 14.1 before, and I had the following issues:
USB OTG was not working
MTP, PTP (and the rest) ALSO not working
After I flashed Android 8.1, USB OTG started working, but ADB, MTP and PTP still did not work. I realized it could be a hardware problem. So I tried connecting with several different USB Cables: did not work. It is also not a driver issue, since I tested in multiple computers (with Linux and Windows);
Then, I bought a new charging board (the one that also has the phone's mic.) and exchanged the old one. That did not help at all.
I was messing around with ADB over network and I happened to make the phone get recognized - about 3 times - using the setprop command:
setprop sys.usb.config adb,mtp,ptp
The problem, after the OS (Ubuntu 16.04) managed to recognize the phone, was that as soon as I unplugged the cable and then plugged it back in, the phone stopped being recognized again. Running dmesg on my PC returned this:
[15548.910595] usb 1-2: new full-speed USB device number 12 using xhci_hcd
[15549.730614] usb 1-2: device descriptor read/64, error -71
Click to expand...
Click to collapse
I also got a device not accepting address error (on dmesg), which I forgot to copy
When I boot into the bootloader (Fastboot Mode), the dmesg output is:
Bus 001 Device 008: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
Click to expand...
Click to collapse
I appreciate your help. Any extra information needed, please ask.
Thank you.
I have the same problem with the rom lineage-14.1 and 15.1
A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).
marcosource said:
A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).
Click to expand...
Click to collapse
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards
Dadditz said:
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards
Click to expand...
Click to collapse
I've tried a lot of things, including other cables, chargers ++
I guess it is dead.. ah well..
Thanks anyway
Have you tried booting to Fastboot?
The Restless Soul said:
Have you tried booting to Fastboot?
Click to expand...
Click to collapse
Can't get any sign of life from it at all.
In linux, if you connect a usb device you see a message with a command called dmesg that gives info about the connected device, there is no reaction when i connect it.
Example when connecting my p20 lite:
[176821.173652] usb 1-6: new high-speed USB device number 18 using xhci_hcd
[176821.326319] usb 1-6: New USB device found, idVendor=12d1, idProduct=107e, bcdDevice= 2.99
[176821.326321] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[176821.326322] usb 1-6: Product: ANE-LX1
[176821.326323] usb 1-6: Manufacturer: HUAWEI
[176821.326324] usb 1-6: SerialNumber: <REDACTED>
[176821.355138] usb-storage 1-6:1.1: USB Mass Storage device detected
[176821.355224] scsi host6: usb-storage 1-6:1.1
[176821.355301] usbcore: registered new interface driver usb-storage
[176821.356740] usbcore: registered new interface driver uas
[176822.386058] scsi 6:0:0:0: CD-ROM Linux File-CD Gadget 0404 PQ: 0 ANSI: 2
[176822.386549] sr 6:0:0:0: Power-on or device reset occurred
[176822.386980] sr 6:0:0:0: [sr0] scsi-1 drive
[176822.386981] cdrom: Uniform CD-ROM driver Revision: 3.20
[176822.387121] sr 6:0:0:0: Attached scsi CD-ROM sr0
[176822.387181] sr 6:0:0:0: Attached scsi generic sg3 type 5
[176822.869111] ISO 9660 Extensions: Microsoft Joliet Level 1
[176822.872240] ISOFS: changing to secondary root
Click to expand...
Click to collapse
And when connecting the p9 lite, there is no reaction what so ever.
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the factory Google image back to the phone?
burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the Google stock factory image?
I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel
burntpuppy said:
I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel
Click to expand...
Click to collapse
If it's detecting the device your fine. Go here, https://flash.android.com/build/7005429?target=flame-user&signed. and re-flash the firmware and you will be good to go.
I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working
burntpuppy said:
I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working
Click to expand...
Click to collapse
You need to re-flash everything. It should do all the work for you. Maybe you flashed the wrong boot.img? Here is the main page for all devices. https://developers.google.com/android/images Select your device, you can choose flash and it will do it all for you or you can download the image, extract it all to your adb folder, double click flash-all and it should flash everything on its own.