N5 dead after logicboard "swapout" - Nexus 5 Q&A, Help & Troubleshooting

Hello,
so here's what happened: I got a fully working N5 with 16GB and a 32GB version which has a broken screen.
Today I tried to replace the logicboard of the 16GB version with the one built into the 32GB one.
The phone didn't start up, neither it reacted to getting plugged into a charger (usb pc & wallcharger both didn't do anything).
I came to the conclusion that the logicboard of my 32GB N5 must be broken aswell, so I put the original 16GB logicboard back in.
The phone booted up normally when all of the sudden it just turned itself off after 5 minutes.
Since then it doesn't start up anymore. Having it plugged in into the charger doesn't do anything either.
I've already tried to get it into bootloader etc but nothing works.
The phone simply doesn't turn on anymore.
When I had it plugged in on my pc I once got a NON-flashing red light, but it seems like I can't reproduce this.
Any ideas?
It would be nice if there is anybody who could help me with my problem.

Swapping the logic board shouldn't prevent the v phone from booting unless something happened during the swap process.
When connect to a windows computer, do you see anything about qhusb load in device manager?

audit13 said:
Swapping the logic board shouldn't prevent the v phone from booting unless something happened during the swap process.
When connect to a windows computer, do you see anything about qhusb load in device manager?
Click to expand...
Click to collapse
After holding the powerbutton + vol up + vol down "QHSUSB_BULK" popped up

That type of "device" is an indication of a hard brick. Disconnect and reconnect without touching anything on the phone. If you see something similar with 9008 in the device name, it could be a soft brick.

After installing a driver it showed up as Qualcomm HS-USB QDLoader 9008. Followed a tutorial using "BoardDiag" to unbrick the device. unfortunately the device remains "dead", no sign of life
:crying:

After having it appear as a "...9008" in your computer, disconnect it from the computer and leave it alone for about 30 minutes. After 30 minutes, try and boot to the bootloader.

Related

[Q] Phone won't charge, no LED, USB makes on/off sounds but won't recognize device

Hello! Last night, my phone died while I was out. When I got home, I plugged it into the wall charger and I noticed the LED didn't come on. I left it charging overnight for about 6 hours and tried to turn it on - no luck. I read on another topic that you needed to charge it to ~2% through USB for it to begin charging on the wall if it's "too" dead, so I left it on my laptop for an hour but again with no luck. I did notice that my laptop couldn't recognize a device though, and since my phone was the only thing plugged in, it means my phone was 'on'. I held the power button and the device disconnected, held the power button again, the unknown device reconnected. So my phone is turning on and off, so I wondered it was my screen. I turned it on, but no sounds worked when I messed with the volume button, so I'm going to rule the screen out. Despite being able to turn 'on', I can't get into recovery and it won't truly turn on.
I'm rooted and unlocked, running a version of PA, though I haven't updated it in some months and haven't downloaded anything other than a picture or two to my phone recently, so I don't think I've bricked it or anything.
I've never used ADB or fastboot or anything like that, so if there's a solution through that I'd be happy to try it out. If there's anything I forgot to mention, please tell me!
Thanks in advance for any help I can get.
This has happened to some people. It seems like going completely dead can somehow corrupt something in the firmware in rare cases.
Open Device Manager and plug in your phone, then see what pops up. If you see QHUSB_DLOAD, your phone has bricked, but it may be fixable. Check into the Unbricking Evita thread and see if the guys there can help.
Failing that, get a warranty exchange.
Try different button combinations (hold power, or hboot combination) while the phone is plugged into the wall charger. At least one person I was trying to help, got his phone to power on this way, when nothing else seemed to work.
Sounds like you're phone is in qdl mode. i second trying the unbricking thread.

[Q] Verizon S3 not working

I used Odin to unlock the bootloaders on my S3. Odin said it completed successfully and the phone shut off but never came back on. I've tried pulling the battery for a few hours but that didn't do anything. I can't get into download or recovery mode. The phone doesn't do anything; no lights or sounds. The only time anything happens is if I plug it into my computer with the battery out; the red LED will go on for a few minutes but nothing else happens. My computer (Macbook with partitions for Lion & Windows 7, have tried with both operating systems) recognizes a device is plugged in but nothing actually happens. What do?
UPDATE: sent it off to have it JTAG'd and it's not bricked. JTAG guy says the eMMC is probably corrupted. So much for giving Android another shot.

[Q] Photon Q won't boot up

Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?
amateurhack said:
Sorry if this is something that has been covered before. I searched, and searched and didn't find my exact problem. Any guidance you may have, including links to the appropriate threads is greatly appreciated.
My Q shutdown today while it was sitting in my pocket during a meeting. It was way too soon for my battery to be dead, but I tried charging it, both by USB on a computer and on a stock charger just in case. The backlight on the screen comes on for a few seconds every minute or so, regardless of whether its on hte charger or not. The screen is black otherwise. The battery is HOT, even after being off the charger for a long time. I tried soft-reset and booting into recovery with no luck. Plugging into USB on a computer that has Moto Device manager installed results in the computer alternating between recognizing and not recognizing the device every few seconds (seemingly in concert with the backlight turning on and off) but it does not recognize it long enough to load directories, etc. RSD lite will not recognize the device.
I wasn't doing anything with the phone at the time. It is rooted but not unlocked.
Any ideas? Will I run into a warranty issue since it was rooted even though it's not unlocked?
Click to expand...
Click to collapse
Have you tried to force reboot (Vol down + Power button for about 7-10 secs)?
Yes. Thanks for the reply. That's what I meant by soft reset. What the issue, I figured out, was that my battery had decided to self-destruct. It didn't have enough charge to even boot the phone successfully, so it was not possible to put it into recovery mode or anything else. I took it to Sprint and they replaced it under warranty.
Sent from my XT897 using XDA Premium 4 mobile app

No response or any indication from my Z5 after a black screen

Here is what happened. I was playing Crashlands when I noticed that my battery is at 3%. So ran to get my Quick charger to get some power fast. After connecting it, I tried to unlock the screen and it went black after a second. So I was thinking that it just shutdown because of low battery. I pressed the power button and noting happens, just the red light showing it was charging. Then I tried soft restart (power + volume up) and it vibrated 3 time and probably shutdown. From that point noting I did started the phone. Even using the off button next to the Sim tray. When I connected it to my PC is ether recognized as Unknown USB device or SOMC Flash Device. I should probably mention that the phone was hot from the game before connected it the charger.
I had the phone for one year and a bit. It is not rooted and i just recently installed the lattes update from Sony. Currently I have it put to charge, at least it looks like it is charging (gets little hot).
Is my phone bricked or something else? What should I do?
I have same problem like this.
Hope someone can help us.
QHSUSB_DLOAD device will show when Connected PC.You can use Flashtool to install the driver.
Unknown divices : because you should complete shut down the power (Disconnect the buttery ).
flash tool will find the phone ,but can't flash.
seems Z1 have a way that find the test point to recovery boot file.hope z5 have the same way.
Sorry for my Poooor English ,hope you can understand what i say and have someone Help US.

Bricked Harrrrd

Metro variant on latest OTA
OEM unlocked
flashed twrp.img
installed magisk 21.4.zip
dog got in confrontation with phone in my hand and in twrp I hit a bunch of crap.
now i have brick -- no power on, no usb trigger, no vol dn+power....nothing
adb and fastboot dont see it.
possibilities....may have restored the SELinux
May have selected the slot b
anything else in twrp advanced tab......
android and linux knowledge at beginner to intermediate levels if im honest
what are my options?
2clacaze said:
Metro variant on latest OTA
OEM unlocked
flashed twrp.img
installed magisk 21.4.zip
dog got in confrontation with phone in my hand and in twrp I hit a bunch of crap.
now i have brick -- no power on, no usb trigger, no vol dn+power....nothing
adb and fastboot dont see it.
possibilities....may have restored the SELinux
May have selected the slot b
anything else in twrp advanced tab......
android and linux knowledge at beginner to intermediate levels if im honest
what are my options?
Click to expand...
Click to collapse
On the computer Under device manager does anything pop up when phone is plugged in?
JimmyJurner said:
On the computer Under device manager does anything pop up when phone is plugged in?
Click to expand...
Click to collapse
nothimg
2clacaze said:
nothimg
Click to expand...
Click to collapse
Not even showing this : Qualcomm HS-USB QDLoader 9008????
JimmyJurner said:
Not even showing this : Qualcomm HS-USB QDLoader 9008????
Click to expand...
Click to collapse
Not a thing under devices, removable our otherwise
You said that it won't power on? Correct? "No power on".. I'm assuming that's what you meant.
If that's the case, it's obvious why nothing shows up when you connect to the computer. I mean, it sounds like you have a fried unit.
I'm not even sure how you could do that in twrp. Lol.
The only phone I've ever had that wouldn't power on, was due to water damage (sweat damage actually). Which I'm still fired up about. I had a pixel 3a. Just 6 months old. Had a case on it.. was walking and talking to my niece, and pouring sweat as I walked/hiked. We hung up, and I noticed I had phantom touches all over the screen. I wiped the phone down, powered it down, sat it in rice for 12 hours. Turned it back on, and it was worse than before. So many phantom touches that I couldnt even power it down. Then volume down and power wouldn't take me to recovery so I could power it off.
I literally just had to sit there for 2 hours as it fried itself alive from water damage. Next morning, I noticed no warming on quick charge. No screen paper. No vibe on startup. Plugged into laptop, nothing registered.
It wasn't bricked. It was gone.
I know it's not a waterproofed phone. But sweat? Destroying a $400 phone? Give me an effin break.
Luckily, I pay my verizon bill with mastercard.. and all mastercard users (even debit cards) have phone insurance built into it. I called them, submitted the paperwork. (Copy of phone bill, copy of bank statement showing I used the mastercard, and a copy of the estimate showing it was a total loss. $349). The deductible was $50.. so 4 business days later, they deposited $299.99 in my account. And I bought the g stylus with it. And when I went to Walmart to buy it, it wouldn't ring up. It was supposed to be $299.99. I found a price match of $249.99. and when he was trying to ring it u, it wouldn't show up on their system. They did a search for it on their website, and he didn't know the difference between a g stylus and a g fast. I got it for $129.99. unlocked. (Was $179.99 on the website, and I had found a 50 off price match for the 299 priced phone earlier, so they gave me the 50 off 179.99. so needless to say -- I got a heckuva deal.
The g stylus is basically a pixel 3a. Except a bigger screen, better battery, and a stylus. The 665 actually performs better on multi ore than the 670 does. Because the 665 has 4 cores at 2ghz, rather than just 2 like the pixel. And the gpu is over closed to almost 1ghz on this phone. So no complaints other than picture quality. The pixel 3a is among the best camera phones ever made to this day. But with the g stylus, running a heavily tweaked and microtuned gcam mod.. its not a huge huge difference unless you are zoomed in. Then it's obvious.
It's possible you tried to boot into a different slot. Hold power and volume down until the phone boots into recovery. Unless you deleted the recovery image, it should still boot into recovery. From recovery you can flash a fresh install of Android or attempt to boot into twrp. I.e. "fastboot boot c:/'location-of-twrp.img'" as to attempt to boot into slot a. I had the same problem and just installed Android one from lollinets site. The variant of Android 11 that works for our metro moto g pro is "11 rprs31.q4u-20-28".
Volume up and power should take you to fastbootd. If hard ware keys aren't working it's either a dead battery or hard bricked. In which case, be careful with the next one.
ok heres the deal .... i came into this thread late but i have made every mistake possiable with this device and have dang near any file to fix the mistakes most of which were on purpose ... i pulled a couple noob reinforced actions tho like flashing sofiar instead of sofiap .... if you still need help brotha hit me up we will team viewer and ill teach you how to correct your issues no prob
sings ..... one of these things is not like the others .......
Vampire Lord said:
ok heres the deal .... i came into this thread late but i have made every mistake possiable with this device and have dang near any file to fix the mistakes most of which were on purpose ... i pulled a couple noob reinforced actions tho like flashing sofiar instead of sofiap .... if you still need help brotha hit me up we will team viewer and ill teach you how to correct your issues no prob
Click to expand...
Click to collapse
I have similar issue. When i connect to charger the white led flashes for exactly one minute then stops. Plug to computer i get nothing. Installed qualcomm drivers still nothing. Tried edl cord no change.
Im not sure what caused this. I was going to root so i unlocked bootloader. Flashed cwm. After flashing cwm its had errors mounting a couple partions. I powerd off and started digging here and on google, found couple options to try. When i tried to power up it was dead. No responce, no conection to computer... just one min of flashing led when i plug into wall charger. Any help would be greatly appreciated
Can you hard reset into recovery
If not does adb recognize your device
If it does you can always force boot twrp from debug
Shane8705 said:
I have similar issue. When i connect to charger the white led flashes for exactly one minute then stops. Plug to computer i get nothing. Installed qualcomm drivers still nothing. Tried edl cord no change.
Im not sure what caused this. I was going to root so i unlocked bootloader. Flashed cwm. After flashing cwm its had errors mounting a couple partions. I powerd off and started digging here and on google, found couple options to try. When i tried to power up it was dead. No responce, no conection to computer... just one min of flashing led when i plug into wall charger. Any help would be greatly appreciated
Click to expand...
Click to collapse
I did exactly this. But I get no flashing LED when I plug into wall charger.
I've tried holding vol down + power for 20+ seconds, nothing.
I've tried holding vol up + power for 20+ seconds, nothing.
When I connect to my computer I no longer see the 9008 in device manager.
abense said:
I did exactly this. But I get no flashing LED when I plug into wall charger.
I've tried holding vol down + power for 20+ seconds, nothing.
I've tried holding vol up + power for 20+ seconds, nothing.
When I connect to my computer I no longer see the 9008 in device manager.
Click to expand...
Click to collapse
Hardbricked mine - I have the metro G Stylus 2021. |
Switched to slot B and now I have nothing.
acrinym said:
Hardbricked mine - I have the metro G Stylus 2021. |
Switched to slot B and now I have nothing.
Click to expand...
Click to collapse
This section is for the 2020 G Stylus.

Categories

Resources