4.4 update bricked my nexus 7 - Nexus 7 (2013) Q&A

Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys

chylos said:
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
Click to expand...
Click to collapse
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.

DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
Click to expand...
Click to collapse
yepp exactly the same.

In short, don't update
Sent from my Nexus 7 using XDA Premium 4 mobile app

Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Sent from my Nexus 7

datallboy said:
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Click to expand...
Click to collapse
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.

I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
Click to expand...
Click to collapse
Damn that sounds awful, and I was nagging for not getting the update, that's way worse. So you can't access bootloader mode at all? Did you try to use fastboot commands or adb when plugged to the pc?

Worth a shot if not already tried:
http://forum.xda-developers.com/showthread.php?t=2404297

DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
Click to expand...
Click to collapse
I've actually gotten the QHSUSB_DLOAD before when trying to get into bootloader but pressing the wrong buttons.
I was eventually able to get out of it going through various button sequences.
I believe holding down the power for a long time worked in the end, but I forget now.

nope nothing helped me. it's still bricked. i tried every button combination up to 3 minutes. No sign of power.İt was 32 gb. i think google ****ed up this time.

Related

Lg nitro hd upgrade

TO ANDROID 4.0 ICE CREAM SANDWHICH IS NOW AVAILABLE
www.lg.com/us/nitrohd-upgrade
can be done through Mobile TOOL
jjflores87 said:
TO ANDROID 4.0 ICE CREAM SANDWHICH IS NOW AVAILABLE
www.lg.com/us/nitrohd-upgrade
can be done through Mobile TOOL
Click to expand...
Click to collapse
Update: I love it! although i have 4 apps that arent working anymore and i cant remember what they were.
can anyone confirm if you can upgrade.through mobile tool coming from a custom ROM? ...HO!NO! or CM9, etc.
Thanks.
Hopefully this easier to root never did get v10j to root.
chrisrotolo said:
can anyone confirm if you can upgrade.through mobile tool coming from a custom ROM? ...HO!NO! or CM9, etc.
Thanks.
Click to expand...
Click to collapse
Yes, you can, but you will lose root and CWM and be back to a "stock" experience. You won't be able to root or install CWM again without downgrading.
i tried to update from leaked ics using the lg tool and got stuck at "rethink possible" screen. had to go back to leaked ics. anyone know why it didnt work? tried it 3 times and same thing.
1986aw11 said:
i tried to update from leaked ics using the lg tool and got stuck at "rethink possible" screen. had to go back to leaked ics. anyone know why it didnt work? tried it 3 times and same thing.
Click to expand...
Click to collapse
Did you try doing a factory reset (volume down + power) after installing the new ICS update?
How do you get CM9 to go into "PC Software" mode? Right now the update software does not see phone is connected?
Thanks
blaineball said:
How do you get CM9 to go into "PC Software" mode? Right now the update software does not see phone is connected?
Thanks
Click to expand...
Click to collapse
Turn on USB debugging (aka Android debugging) under developer options. I think that will do it.
drumist said:
Did you try doing a factory reset (volume down + power) after installing the new ICS update?
Click to expand...
Click to collapse
tried the factory reset thing. didnt work. ugh. this sucks. leaked version sucks battery way too quickly.
1986aw11 said:
tried the factory reset thing. didnt work. ugh. this sucks. leaked version sucks battery way too quickly.
Click to expand...
Click to collapse
Can you document the steps you have been going through in attempts to update from ICS Leak. Do you have a rooted ICS Leak configuration?
1986aw11 said:
tried the factory reset thing. didnt work. ugh. this sucks. leaked version sucks battery way too quickly.
Click to expand...
Click to collapse
Just to clarify, when you say it "didn't work", do you mean you couldn't get it to perform the factory reset? or that you did get it to do a factory reset but it didn't fix the problem?
I can confirm. I am on he leaked ICS and can't update to this version. I too get stuck at ATT Rethink logo. I went back to Leaked build.
I tried everything from putting the phone to download mode. Trying the "Recovery option". It seems like everything installs correctly but it gets stuck during the reboot process. Nothing I do can fix it.
Help Needed
Hi All,
I have an UNLOCKED LG Nitro HD and want to update to ICS.
Need some inputs reg. update
1. As my mobile is unlocked can i follow the same procedure of ATT LG update ?
2. Can we do it Windows 7 or Winxp ?
Thanks
Yes, you can update normally and you will still be SIM unlocked.
drumist said:
Yes, you can update normally and you will still be SIM unlocked.
Click to expand...
Click to collapse
Thanks for the input. will try the update today :angel:
i couldt get it to go into factory reset mode apparently. finally got it to reset and now have new version. seems a little laggy when exiting settings and app folder. ah well. battery seems a little better now.
Stuck on "Rethink Possible" screen
I had the same problem.
I came from the rooted leaked ICS trying to update to the official version and got stuck on the rethink possible boot screen.
The way I got my phone to work was via hard factory reset
1 Turn the power off.
2 Press and hold the following keys at the same time for 8 seconds: Down Volume Key + Power/Lock Key
3 Release the keys when the FACTORY HARD RESET screen appears. (I had to try twice to get it to work and the phone needed to be unplugged from PC)
4 Read the warning and press the Power/Lock Key to confirm.
5 Press the Power/Lock Key image to confirm once more
6 Wait for your device to perform a hard reset (don't worry if it seems to be stuck on the rethink possible screen. It may take 1-2 minutes and the phone will start up properly).
UNhooked said:
I can confirm. I am on he leaked ICS and can't update to this version. I too get stuck at ATT Rethink logo. I went back to Leaked build.
I tried everything from putting the phone to download mode. Trying the "Recovery option". It seems like everything installs correctly but it gets stuck during the reboot process. Nothing I do can fix it.
Click to expand...
Click to collapse
1986aw11 said:
tried the factory reset thing. didnt work. ugh. this sucks. leaked version sucks battery way too quickly.
Click to expand...
Click to collapse
I couldnt agree with you more, seems like those added features to disable unused programs and save battery actually made it worse.
I might be the only idiot but I could not get it to work till I took sd card and sim out of the phone.
I had to restart after drivers installed and use another port on laptop as the old usb one won't work...weird.
Anyways, after removing sim and sd, all I had to do was use a new fresh port after restart of computer and it all went well till I got stuck on AT&T logo. After 5 minutes, I pulled the battery out and restarted with vol down + power button and did a factory reset and all is working well now.
Thank you very much

[Q] Hardbricked? do not reboot HELP!!!

hi everybody,
I'm usually more active on auto forums but I need your help.
wanting to install a custom rom, I'm a but lost in the manipulations. Last night when I wanted to turn on the tab (only with the power button), I had the google logo that was displayed at the top right and the small rectangle of recovery menu (start, recovery, reboot bootloader and poweroff). With buttons I could choose one of four functions. I had access to the recovery menu, when I choosen restart bootloader, it well reboot and poweroff worked well too. By when I clicked start I had a small line at the top left telling me "boot failed"
I try to flash everything thanks to a tutorial.
So I'm DL the original elements but still the same issue. Having struggled until 3am I give up. This morning when I tried to turn on the tab, I did even more than what I have explained below whatsoever with the power button or volume down + power nothing happens the screen stays black.
Any Ideas?
PS sorry for the language I'm french
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
stanglifemike said:
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
I'm seriously thinking of this solution but I'm afraid before they give me a new one they send it to their after sales service. If they find out I have rooted it and unlock the bootloader they will make nothing for me
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
sfreemanoh said:
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
Click to expand...
Click to collapse
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
swagstr said:
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you .
No it doesn't works. For the time being my first to issue is to succeed to boot it at least as yesterday evening.
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
geckocavemen said:
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
+1 Try plugging it in for awhile too. You want to get to the bootloader - the screen with the Android where you go through the options with the volume buttons. Once there,you can use fastboot to flash TWRP and fix from there. Again, stay away from the OLD Nexus files.
Sent from my Nexus 7 using Tapatalk 4
geckocavemen said:
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
I tried to keep on the power button during 1 min with and without charger and pluged to PC : nothing happens. I tried the same thing with volume down + power and nothing happens either
I'm not sure what might help next. Perhaps someone with more experience will come along with advice. If it were me I would probably return it and tell them the power button stopped working.
stef77972 said:
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Click to expand...
Click to collapse
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
I'm seriously thinking of this solution. I'm just worry if asus find out everything I made
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Hmm.. This is possible. If your device will not turn on, I'm thinking you are SOL my friend. Or in your native tongue: merde pas de chance. Hopefully that conveys it
Sent from my Nexus 7 using Tapatalk 4
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Yes I used this one but I think I have the old version
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
Oh boy... *Grabs popcorn*
Sent from my Nexus 7 using Tapatalk 4
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
the old nexus 7 or the new 2013 model with a camera on the back? is yours wifi only or 3g capable?
The only thing i can think of is to plug into your pc's usb port and hold the power button for 30sec.
Then unplug from PC and press power button for about 15sec and you should see the google logo - if not, i think your bootloader is bricked from flashing the wrong one.
If you do see the google logo, keep holding power and also press vol down as soon as you see the logo - should get you into the bootloader.
Messing up the bootloader is the only way you can brick a nexus, feel sorry for ya man
noob question: so you are using a Nexus 7 (2013) and you flashed an old-nexus-7 ROM on your device? If you're using the new one, here is the ROM for the new one http://forum.xda-developers.com/showthread.php?p=44054613.
I have just had the same problem. Flash the old nexus 7 kernel on the new one, luckily I fixed it
There is a different forum for the 2012 Nexus 7 here. This forum is for the 2013 version.

[Q] Nexus 7 suddenly bricked ?

Hello all, so yesterday I went on my tablet (Nexus 7 2013 WIFI ver.) and browsed the net a bit and went to sleep. I recall having around 30% battery power. This morning I wake up to an apparently flat battery (power button didn't turn on anything) so I just plugged it in and did something else. After a while, I took my tablet and started it with the power button. However, it got stuck on the Google logo and never fired up anything. I've rooted the tablet quite some time ago (months) so the cause is not from there.
Things I haven't recently done:
Installing an app.
Rooting or flashing anything.
Updating an app.
Things I have tried doing to fix the problem:
Booting into FASTBOOT then trying the recovery mode = still stuck on the Google logo.
Booting a custom recovery image using Wug's toolkit = frozen at the team logo (TWRP) / black screen (CWM).
Flash Stock + Unroot (Soft-Bricked/Bootloop) = FAILED (flash write failure).
So now I'm really stuck and desperate to make the device work again. I've been reading all day long and trying all sorts of solutions to no avail. And it seems far-fetched to me for a device like this to just instantly brick itself without any reason at all.
Can anyone help me with this case ? Or does anyone has any idea what just happened to my tablet ? :crying:
EDIT: I'm afraid that warranty might not work as the device was unlocked and rooted so it's the last solution for me.
Bumpity bump
No one has any idea what happened to the tablet and how to fix it ? I've tried doing some more flashing but to no avail. It just refuses to flash and keeps failing to write the files.
I think you need to leave out on the charger for 1/2hr without doing anything with it. You are probably using what little power it has charged by trying to reboot it, etc.
I had to do that once and it did the trick.
Sent from my Nexus 7 using XDA Free mobile app
There is no reason you should not be able to get in to recovery (power and volume down).
You could call Motorola. They have good tech support.
The exact same thing happened to me. I rooted it months ago and haven't changed a thing since then. It just froze up a few days ago. I restarted and it just gets stuck on the google screen. I can get into the bootloader, but when I try to go to recovery, the google screen comes up and won't go away. I've tried every method I can find for flashing the stock image and absolutely nothing is working. I just get stuck on the google screen.
Please update this if you find a solution!
Do u guys have the most up to date version of whatever particular recovery that you're on?
Yep. I've flashed the stock recovery multiple times to no avail. :/
nexusjas said:
Yep. I've flashed the stock recovery multiple times to no avail. :/
Click to expand...
Click to collapse
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Have you tried to see if your computer sees your N7 by typing fastboot devices if you have the sdk installed?
wantabe said:
If you can't get into recovery or flash any images it sounds to me like a hardware failure. Bad memory maybe? If you've tried everything then RMA to Asus before the one year warranty runs out.
Click to expand...
Click to collapse
Not what I wanted to hear, but you're probably right. Thanks :/
nexusjas said:
Not what I wanted to hear, but you're probably right. Thanks :/
Click to expand...
Click to collapse
I was to slow with my update. Does your computer see your N7 with fastboot?
wantabe said:
I was to slow with my update. Does your computer see your N7 with fastboot?
Click to expand...
Click to collapse
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
nexusjas said:
Yes, I can get into the bootloader just fine and I can use fastboot. I go through the flashing process and the command prompt says everything flashed successfully, but when I restart the device, it hangs on the google logo. The same thing happens when I try to boot into recovery.
Click to expand...
Click to collapse
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
wantabe said:
If you fastboot flashed the factory image and can't boot up then it sounds like a hardware problem. Out of ideas, sorry.
Click to expand...
Click to collapse
I'm not sure what happened, but I just ran this little utility again (I've done it many times over the last week or so to no avail) and it actually worked. Hopefully it keeps working!
Thanks for your help!

Bootloop, soft brick?

I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.
Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...
enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.
Mine is @ LG as I haven't bought from Google... Let's see...
talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.
Nexus are impossible to brick, unless you flash stock factory image...
I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus

My Nexus 5X just died - question about warranty

Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Razeer123 said:
Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
Click to expand...
Click to collapse
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
theGekkoST said:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Click to expand...
Click to collapse
nirogu325 said:
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
Click to expand...
Click to collapse
Today the diode started to blink red, I connected Nexus 5X to charger and waited ~30 mins to charge a bit. Then I wanted to flash stock system + recovery and unroot but when booting to recovery device again stopped on Google logo and went black. From this moment no sign of beeing alive. I think I'll wait to this situation to happen again and will try to install stock firmware.
Mine would flash red when the battery was completely drained. I could plug it in and get the battery logo, but if I tried to boot it up; the screen would hit to the Google logo and then just go black. I could wait a day and the red battery light would flash again when I pressed the power button. After a few times of doing this, it wouldn't even charge anymore.
Honestly I seriously doubt they have time to go Sherlock Holmes on your phone and void your warranty. They are most likely going to get your phone see if it boots, if not replace the motherboard and go on.
Not to mention if its not responding to anything at this point what do you have to lose. Send it in and see what happens.
This problem is frequent on the Nexus 5x, V10,V20,G4 and G5, the only issu is to use heat gun on the CPU, these devices will starts normally but the problem will appear again
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Same thing happened to me
Same thing happened to me last night. I tried everything I could think of, I was running the latest stock Nougat version with no root and all of a sudden the device froze. After manually powering it down, I could not get it to boot up again. No LED, battery charging icon on the screen, nothing worked, so as it was still under warranty, I got in touch with someone at Google. They've sent me a replacement device that's set to arrive tomorrow and I am to return the faulty one free of charge. Luckily my Nexus 4 still works otherwise I would've missed several calls today. I suggest you get in touch and see what they say. I know of cases where despite the phone being rooted, if they were running stock the warranty was still applicable. With your device being completely dead, you really have nothing to lose.
Okay, update - I was able to reinstall stock firmware via Nexus Root Toolkit on this device, because I booted it into fastboot and it worked for few minutes. Bootloader is still unlocked - should I wait and lock it (I don't know when will my phone be accessible again, red diode is blessing right now because it boots when it's blinking) or should I send it to repair without worrying?
I would lock it.
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Welcome to the boot kingdom
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Razeer123 said:
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Click to expand...
Click to collapse
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
nirogu325 said:
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
Click to expand...
Click to collapse
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Razeer123 said:
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Click to expand...
Click to collapse
No worries, you are in luck.
I tried it with oreo and nougat, but it did not work, it keeps freezing.

Categories

Resources