Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors:
https://imgur.com/a/bBdbnvH
It was previously unlocked until I tried flashing the recent December update.
Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Ofuroski said:
Can't load into recovery or system, only fastboot mode. In fastboot, I get these errors: https://imgur.com/a/bBdbnvH It was previously unlocked until I tried flashing the recent December update. Any ideas on how to get it back up an running? I haven't seen Secure boot: NONE and NOS Production: Error posted on here before or a state where it can't determine if it's locked or unlocked. I'll try ubreakifix otherwise. Thanks!
Click to expand...
Click to collapse
Don't start a duplicate thread dude! Starting to sound like a Google FRP workaround to me. What does Google support say??
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
starcleff said:
Same here (with Pixel 3 non-xl).
I don't know what to do. Recovery doesn't work, only fastboot mode with "device state: error!" .
Bootloader is locked, and I have no way of unlocking it, because fastboot times out.
It happened shortly after I took it in the shower (it's never a problem). Maybe it's not that waterproof.
Google support says the phone is probably done, but they can't help with the warranty because apparently I got scammed buying it second-hand, the invoice doesn't match the IMEI.
Click to expand...
Click to collapse
I might be a bit late, but I had exactly the same issue, lost hope and all. I have tried multiple chargers and cables but nothing helped.
How I fixed it is:
1) Left the phone on in fastboot mode, until the battery died (unplugged obviously).
2) Left the phone unplugged for about 8h.
3) In the morning, keep pressed power button and plugged in the charger.
4) After few seconds it started up.
Hope this is helping you guys.
This just happened to me. Has the problem returned on you? Assuming I can get it to boot again, I'm wondering if I should do a factory reset to give myself a fresh start and clear out whatever software issue may be causing it, if it is a software issue.
Thanks fixed it
Thanks NathanTan...
It fixed my issue. I left it overnight with fastmode displayed. After it ran out of battery powered on and boom phone was back to normal. I never thought it will sort without replacing handset. Thank you
Hey guys. Please help. I am facing this issue in Pixel 5a now.
Only the end user can set the user-settable root of trust. It cannot be set at the factory or any other point before the device is delivered to the end user.
geometry dash is a game that is loved by many people.
Related
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
Hi,after i wiped all data in twrp my nexus 5x stucked in bootloader mode(when you have to choice between recovery,power off,reboot etc.) and my bootloader is locked,before i had an android 7.0 rom, what can i do?
Please help me ,i've got any idea.
Can you still boot to twrp? You can sideload a custom Rom zip from you pc if you can.
Sent from my Nexus 9 using XDA-Developers mobile app
Any chance OEM Unlock was already enabled to run bootloader unlock command? Long shot I guess.
Otherwise use TWRP if you can get it.
If you ever Unlock you bootloader. Never lock it.
Sent from my Nexus 5X using Tapatalk
I can't go to twrp and i've got no chances to unlock oem bootloader.
I think i will try to flash the .tot file from pc.
Any idea?
I have the same problem now. Bootloader Locked, OEM and USB debugging not enabled in developers mode.
A few hours after android 7 update, phone booted itself and getting stuck at google dot animation.
I have tried adb sideloading stock image, it would finish successful but will get stuck at same google dot animation on reboot.
Please help. I'm out of ideas.
Have you found any solution?
vmchakka said:
Have you found any solution?
Click to expand...
Click to collapse
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
Yes, for some reason, a number of N5X devices are having an issue after recent updates where they subsequently will not boot and it is not possible to boot to Recovery Mode - in effect when they try the system continues trying to complete the system reboot that occurs at the end of the update. It would appear this happens because the update reboot didn't finish properly and did not clear a well defined in memory post box. I have raised this issue with the Community Manager for escalation to the development team as something is wrong (hardware or software still to be determined). In the meantime, if this occurs all that can be done is return the device for warranty replacement.
Click to expand...
Click to collapse
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Huskehn said:
It appears to be a common issue, but I don't see any resolution other than having the phone replaced:
I just got this phone, too...
Things I have tried, so you don't have to try them too:
Flashing LGH790AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing LGH791AT-00-V10f-NXS-XXX-OCT-03-2015-32G-MDA89E-US.tot
Flashing bullhead-mda89e-factory-29247942.tgz
Flashing bullhead-nrd90m-factory-d215f148.tgz
Sideloading bullhead-ota-mhc19q-8fe67a2b.zip
Sideloading bullhead-ota-mtc19t-4ea6522b.zip
Sideloading bullhead-ota-mtc20f-6303e5cd.zip
Sideloading bullhead-ota-nrd90m-fdb8250a.zip
And I tried them in all kinds of different orders, too, as well as changing USB drivers, cables, computers. I have been doing nothing but this since I got home from work yesterday. I didn't sleep. I have to go to work in a bit but I fear that there may not be a fix other than having the phone replaced.
Click to expand...
Click to collapse
I have exactly same problem like you Huskehn.
So far I tried with all OTA's with a successful installation, yet wouldn't stop it get stuck at dot animation.
I also mailed back my seller for warranty replacement. Turn's out the seller disappeared from ebay and the office contact is unreachable. Talked to ebay helpline and the passed it on to paypal 180 days money back guarantee. Paypal asked me to chargeback from bank as the seller is out of reach. I have managed to talk to bank and get chargeback.
I am not sure if I want to risk buying same 5x now also it is constantly bugging me that I wasn't able to get a success fixing this device. Waiting for a Solution, If you can get yours to work, let me know. cheers
I know that this issue has been discussed several times here on the forum, but I couldn't find a solution for my situation. So, kindly bear with me.
I was talking on the phone when it slipped and fell down to the ground. When I lift the device, the screen was fine but the touch was not working. I couldn't draw the lock pattern or type the password or anything. I restarted the device several times but without success.
I found a youtube video on how to open the device to check the screen flat cable. I opened the device and checked the cable. It was a little bit loose, I secured it and put everything back. I turned on the device and the screen worked, but it gave the message "Your device is corrupt ..." (Red warning).
The google support forum said that this warning is due "tampering" with the OS. This is not my case because simply, I don't know how.
I tried "Factory Reset" several times, but wasn't successful. The device keeps showing this warning and when I continue, it works for half an hour or so before it restarts again, and so on.
My problem now is that I don't know if this is a hardware or software problem.
I really appreciate all your help and support.
Best Regards,
mwahid
mwahid said:
My problem now is that I don't know if this is a hardware or software problem.
I really appreciate all your help and support.
Best Regards,
mwahid
Click to expand...
Click to collapse
That is what shows up on every boot after you unlock the bootloader. There may have been a short circuit of some kind and was viewed as tampering. It affects nothing in the way your phone operates but affects warranty.
If it is really bothering you, you can try to flash the factory image and relock the bootloader. Then re-unlock the bootloader to see if that gets rid of the problem. However, as stated above it does not affect how your phone operates; so personally I would just leave it.
Thanks for your reply.
The problem is that the device is not working properly. It keeps restarting every half an hour or so and sometimes it hangs even when I am not using it.
I checked the bootloader from the fastboot menu and it is locked. I didn't try to unlock the bootloader or reflash the device. This message appeared only after I opened the device to fix the screen.
I will try reflashing the factory image and see what will happen.
Thanks again for your help.
I followed this guide to the letter, but the problem is still the same. The phone works for a few minutes then suddenly restarts and displays the message "Your device is corrupt ..." (Red warning)
I really appreciate any ideas.
Thanks
Hello again,
Could a hardware malfunction be the cause of this problem?
I just want to know so I can evaluate my option whether to fix it or buy a new one.
Thanks,
mwahid
Im haveing the same problem but i never drop it or open it its did not boot half the time now its having none of it its will not even turn on so gg LG.
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app
1. This phone's been babied no damage.
2. Never rooted or any kind of tweaking, only basic usage.
Now it gets stuck on boot and even if I try to hard reset once I tap the button to get into recovery it just flashes the Google start up logo. I can never get to the "no command" part. Besides that it does nothing but turn on stay stuck on boot (Google logo).
same here :/ any updates?
its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...
---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------
it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.
godkingofcanada said:
its not a brick. if this issue is affecting several people, someone at xda will figure it out, or google themselves will notice and fix it. I contacted google about it and let them know that ive seen several users reporting the same issue. i'm also trying different things on my end, but without being able to sideload zips or get into twrp its difficult. I cant even tell if the memory is encrypted or not. and fastboot has no diagnostic tool for me to run a hardware test, however I cant see all of our devices working fine one day and randomly breaking the next...
---------- Post added at 05:10 AM ---------- Previous post was at 05:09 AM ----------
it seems the last update or two did something and flashing different boots and stock images is not overwriting whatever is wrong, almost as if it was an update to something that can't be rolled back. if thats the case we will need another update that corrects the issue, since we can't manually reverse it.
Click to expand...
Click to collapse
so... Google knows about the issue, ok. But how will that help, to a whaetver person like me, that has NO google shops to RMA, or bring them to fix it to?
Are you saying that they will patch an OTA, so that we can sideload it? i can enter recovery mode, after letting the phone stay in Power Off mode a few hours. Tried resetting multiple times.
I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please
I'm on the phone with google software development
No luck. Toasted or repair. They said the mobo
Sorry to hear that. Just curious - how old the device was, maybe you have a manufacturing date? Have you used the genuine USB C PD charger, or used third party chargers? Just don't understand how motherboard dies so frequently for first gen.
Mine died this morning when I went to check the weather. An update had apparently installed overnight, nothing else was out of the ordinary. It froze and I hard powered it off. I haven't had any signs of life since. It is listed as "Qualcomm-HS-USB QDLoader 9008" when I try to plug it into my computer (no access, just listed as a connected device.) Mine was a 128gb variant, carrier unlocked, never rooted/etc., only used with official charger & usb cable. I don't have the mfg date unfortunately.
I hope any of that info can prove useful, even if just to help establish a scope of the affected devices.
C4rb0nf00tpr1nts said:
I have a similar situation.
Pixel XL on charge, went out for 10 minutes, came back, pick up phone, power button unresponsive...
I did have all the preps for rooting (OEM unlock turned on, developer mode enabled, USB debug etc...) because I was going to try some custom ROMs.
"fastboot oem unlock" returns "FAILED (remote: 'oem unlock is not allowed')"
My whole life is in that damn expensive paperweight... I am in serious trouble (medical reasons, daily notes stored on phone) if i can't even simply recover user data.
Any ideas? anyone? help... please
Click to expand...
Click to collapse
Did you try the more current "fastboot flashing unlock" command? That is the correct one.
The problem is that will erase your user data partition.
Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.
jaytv said:
Did you try the more current "fastboot flashing unlock" command? That is the correct one.
The problem is that will erase your user data partition.
Hopefully your notes were taken in Google Keep? If so, you can read them on any computer you can sign into with your Goodle account.
Click to expand...
Click to collapse
Sure did. Tried everything. Nothing will connect to the phone - only things that return a successful response are some of the fastboot commands (getvar all, device).
And due to having friends and colleagues that kept telling me to turn off all the "big brother" type of backup options I have nothing.
I can categorically state that I have nothing to hide from all the officious types that would be watching my every key stroke or phone entry and I will be turning on every backup or recovery option in future, whether or not I go back to the fragile device of a Google phone is to be decided if I myself decide to push on from this point at all...