Database Info

Fasboot getting unpredictable

I went to flash the new 5.0.1 image today and fastboot has been incredibly flaky. Most commands just stall saying <waiting for device>. Half the time, "fastboot devices" shows nothing. Flashing images when it is "working" typically fails. One of the errors I received was "too many links". It just seems that my bootloader/fastboot is very unstable now. These issues came up out of the blue. Is my device dying?
[edit] this is the kind of thing that happens:
C:\Users\bwilcox\Desktop\hammerhead-lrx22c\hammerhead-lrx22c>fastboot devices
019ddb090911b9a4 fastboot
C:\Users\bwilcox\Desktop\hammerhead-lrx22c\hammerhead-lrx22c>fastboot flash syst
em system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 1.127s]
sending 'system' (981472 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 3.722s

brianwilcox said:
I went to flash the new 5.0.1 image today and fastboot has been incredibly flaky. Most commands just stall saying <waiting for device>. Half the time, "fastboot devices" shows nothing. Flashing images when it is "working" typically fails. One of the errors I received was "too many links". It just seems that my bootloader/fastboot is very unstable now. These issues came up out of the blue. Is my device dying?
[edit] this is the kind of thing that happens:
C:\Users\bwilcox\Desktop\hammerhead-lrx22c\hammerhead-lrx22c>fastboot devices
019ddb090911b9a4 fastboot
C:\Users\bwilcox\Desktop\hammerhead-lrx22c\hammerhead-lrx22c>fastboot flash syst
em system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 1.127s]
sending 'system' (981472 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 3.722s
Click to expand...
Click to collapse
You should try changing the data cable and making sure you aren't trying to use a usb3.0 port. I wasted half an hour doing just that - even though I knew it wouldn't work.

Niflheimer said:
You should try changing the data cable and making sure you aren't trying to use a usb3.0 port. I wasted half an hour doing just that - even though I knew it wouldn't work.
Click to expand...
Click to collapse
Thank you. I did use a different computer with USB 2.0 ports. Worked just fine. It is odd though, I have been using my laptop with USB 3 for these updates for over a year, never had any trouble. Oh well. Thank you!

No sign of life after attempting to go back to stock (CM 12S)

Hi,
I had the latest CM 12 nightly on my OPO and wanted to go back to stock. So I used what at this thread:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
launched flash-all.bat, and it all went smoothly till a certain point, after one of the various fastboot reboots issued by the batch file the device didn't came back in fastboot mode and the batch file kept waiting. I waited for a while, nothing happened afterward.
Here's how far it went:
Code:
D:\cm-12.0-YNG1TAS17L-bacon-signed-fastboot_64GB>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'modem' (57361 KB)...
OKAY [ 1.872s]
writing 'modem'...
OKAY [ 0.760s]
finished. total time: 2.635s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target reported max download size of 1073741824 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.019s]
finished. total time: 0.034s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target reported max download size of 1073741824 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.005s]
writing 'dbi'...
OKAY [ 0.013s]
finished. total time: 0.020s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
target reported max download size of 1073741824 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.024s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.049s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
target reported max download size of 1073741824 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
OKAY [ 0.020s]
finished. total time: 0.032s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.007s
< waiting for device >
I tried to reboot, go back in fastboot (volume + powerup), in recovery (volume + power down), tried to keep the power button pressed for 30 seconds, nothing happens anymore. The phone seems dead.
Anyone has been in the same situation? Suggestiongs on how to revive it?

ok I think I found a possible answer to my own question here:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I'll give this a try as soon as I find a few hours to dedicate to it.
If anyone else has other suggestions that might help as well.

adri72 said:
ok I think I found a possible answer to my own question here:
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I'll give this a try as soon as I find a few hours to dedicate to it.
If anyone else has other suggestions that might help as well.
Click to expand...
Click to collapse
Let me know how it goes
Sent from my SM-G920T

no joy so far... I installed the driver, and my PC can see the device after a power + volume up (see screenshot), but then when I launch the Msm8974DownloadTool.exe and hit "refresh" no device shows up in the list of COM ports.
Tried connecting / disconnecting / changing USB port / rebooting the pc... nothing helped so far. That's too bad cause I feel I got really close but but without the tool to seeing the actual device not much more I can do

Does the phone charge when you plug the charger? Any signs of life?
Sent from my SM-G920T

no sign of life -- charge led doesn't turn on. I believe it's not even powering off so unless I get it out of brick soon, it will run out of power and that's going to be it.

adri72 said:
no sign of life -- charge led doesn't turn on. I believe it's not even powering off so unless I get it out of brick soon, it will run out of power and that's going to be it.
Click to expand...
Click to collapse
As I know, OPO won't fully brick that easily, even flashed wrong kernel from other devices. I have hard-bricked my OPO twice, but both successfully recovered, I am guessing the USB drivers you are using isn't correct. Where did you get the drive? Last time I remember my driver doesn't have the "Forge" keyword infront.

Hi there, had the same Problem some days ago... My OPO was dark as a Stone. No charging led, nothing. But you can test if your connected Computer reacts on USB when reboot OPO.
I tried all those Solutions that helped so many People before. But nothing worked. The only hint that helped me was to unconnect the battery. And yes you will loose your warranty THEN. But a bricked OPO or a OPO with no more Hardware warranty, that was no Long Lasting decision. Just have a look on YouTube for opening OPO. If you have Fingernails you don't even Need a tool.
After resetting the board thru power loss, connecting battery plug again, I could enter Fastboot mode again. I flashed CM11 and voila... OPO alive! after that the normal updates took place and now i'm on CM12. works for me!
Before doing this you should Charge your mobile. And it will Charge, even without LED. Prooven for three days of nervous reading and trying and charging of my bricked OPO
If you don't mind losing your warranty... give it a try.
Hope this will help you as well as me.
Good luck, and tell us if that helped

Press for 10sec the power button? It will restart the phone ... Test this before you removed your Battery..

ItsMeDontPanic said:
Hi there, had the same Problem some days ago... My OPO was dark as a Stone. No charging led, nothing. But you can test if your connected Computer reacts on USB when reboot OPO.
I tried all those Solutions that helped so many People before. But nothing worked. The only hint that helped me was to unconnect the battery. And yes you will loose your warranty THEN. But a bricked OPO or a OPO with no more Hardware warranty, that was no Long Lasting decision. Just have a look on YouTube for opening OPO. If you have Fingernails you don't even Need a tool.
After resetting the board thru power loss, connecting battery plug again, I could enter Fastboot mode again. I flashed CM11 and voila... OPO alive! after that the normal updates took place and now i'm on CM12. works for me!
Before doing this you should Charge your mobile. And it will Charge, even without LED. Prooven for three days of nervous reading and trying and charging of my bricked OPO
If you don't mind losing your warranty... give it a try.
Hope this will help you as well as me.
Good luck, and tell us if that helped
Click to expand...
Click to collapse
What do you mean "resetting the board through power loss"? How do you achieve that? Or just by simply disconnecting the battery?
Sent from my SM-G920T
---------- Post added at 01:47 ---------- Previous post was at 01:45 ----------
soralz said:
As I know, OPO won't fully brick that easily, even flashed wrong kernel from other devices. I have hard-bricked my OPO twice, but both successfully recovered, I am guessing the USB drivers you are using isn't correct. Where did you get the drive? Last time I remember my driver doesn't have the "Forge" keyword infront.
Click to expand...
Click to collapse
How did you unbrick it those 2 times it got hard bricked? Also how do you know if it is hard bricked and not simply a battery issue that can get fixed by disconnecting the battery?
Sent from my SM-G920T

ambervals6 said:
What do you mean "resetting the board through power loss"? How do you achieve that? Or just by simply disconnecting the battery?
Sent from my SM-G920T
---------- Post added at 01:47 ---------- Previous post was at 01:45 ----------
How did you unbrick it those 2 times it got hard bricked? Also how do you know if it is hard bricked and not simply a battery issue that can get fixed by disconnecting the battery?
Sent from my SM-G920T
Click to expand...
Click to collapse
1st time, flashed customized CM12 bootlogo then it bricked (I know was my fault)
2nd time, for unknown reason it hard bricked itself after I updated a Xposed module, stuck at bootlogo followed by that no sign of life anymore.
Perhaps you can try my QHSUSB drivers. Update it from device manager, and remember disable driver signature enforcement else it won't install. This driver revived my phone. (x64 OS Win7, Win8 only)

soralz said:
1st time, flashed customized CM12 bootlogo then it bricked (I know was my fault)
2nd time, for unknown reason it hard bricked itself after I updated a Xposed module, stuck at bootlogo followed by that no sign of life anymore.
Perhaps you can try my QHSUSB drivers. Update it from device manager, and remember disable driver signature enforcement else it won't install. This driver revived my phone. (x64 OS Win7, Win8 only)
Click to expand...
Click to collapse
Thanks
Sent from my SM-G920T

soralz said:
As I know, OPO won't fully brick that easily, even flashed wrong kernel from other devices. I have hard-bricked my OPO twice, but both successfully recovered, I am guessing the USB drivers you are using isn't correct. Where did you get the drive? Last time I remember my driver doesn't have the "Forge" keyword infront.
Click to expand...
Click to collapse
Thank you for your suggestion about the drivers -- that was the issue. I got them from this post here (just a couple of days ago... although now the post 404s), so I went through the unbrick guide again, and downloaded the drivers mentioed there.
Removed the drivers I had installed, had the phone re-detected, installed the new drivers, and this time the flashing tools detected my OPO! So I was able to flash ColorOS and get the phone to boot again. The flashing completed successfully, although now the device will turn itself off soon after the language selection screen after boot.
Anyway, I can now get back to fastboot, so I'll flash the latest CM 12S (stock) and hopefully get it fully working again.

[Solved] Only Fastboost works on my phone. Is there still a solution?

Hi all,
I write this thread after spending almost one entire week trying to fix my phone, that is a Motorala RAZR HD XT925.
It was very slow lately, and finally it was just showing the Motorola logo like it was about to turn on, but it was getting stuck to that....
I tried a lot of stuff: soft reset, hard reset, factory reset: nothing, still the logo until it runs out of battery.
Finally, I saw few stuffs about AP Fastboost and I figured out that it was the only thing remaining that wokrs somehow. Then I found tutorials about flashing roms via Fastboost.
I tried several roms but none was working (failure on boot.img and recovery.img), before I figured out that XT925 is not XT926.... For the latter you find a lot of Fastboot files easily, for the XT925 well is seems more difficult.... then after trying so many things, I got lost, totally lost!
Flashing roms, ClockWorkMod, Recovery, Root, Unblock Bootloader, .... everything is messed up in my head. I want to buy a new phone anyway because I have not that much hope. But I've decided to throw my last card and write a post in here before
In summury: it is an XT925 (bought in France), the phone is not rooted, the bootloader is blocked, it seems I lost all my data (after doing a "fastboot -w" I think but at this stage I don't really mind), I only have access to the AP Fastboot and I am under linux (no DS Lite then...).
Is there any way to turn this phone on again?
Thank you for all.

Mangaf said:
Hi all,
I write this thread after spending almost one entire week trying to fix my phone, that is a Motorala RAZR HD XT925.
It was very slow lately, and finally it was just showing the Motorola logo like it was about to turn on, but it was getting stuck to that....
I tried a lot of stuff: soft reset, hard reset, factory reset: nothing, still the logo until it runs out of battery.
Finally, I saw few stuffs about AP Fastboost and I figured out that it was the only thing remaining that wokrs somehow. Then I found tutorials about flashing roms via Fastboost.
I tried several roms but none was working (failure on boot.img and recovery.img), before I figured out that XT925 is not XT926.... For the latter you find a lot of Fastboot files easily, for the XT925 well is seems more difficult.... then after trying so many things, I got lost, totally lost!
Flashing roms, ClockWorkMod, Recovery, Root, Unblock Bootloader, .... everything is messed up in my head. I want to buy a new phone anyway because I have not that much hope. But I've decided to throw my last card and write a post in here before
In summury: it is an XT925 (bought in France), the phone is not rooted, the bootloader is blocked, it seems I lost all my data (after doing a "fastboot -w" I think but at this stage I don't really mind), I only have access to the AP Fastboot and I am under linux (no DS Lite then...).
Is there any way to turn this phone on again?
Thank you for all.
Click to expand...
Click to collapse
Give me a little bit, i'll post the kk xt925 for you
EDIT - Here's the link
https://drive.google.com/file/d/0B52pkPIFU2dRWFRXOU9UQlhHZ3c/view?usp=sharing
Sent from my ATRIX HD using XDA Free mobile app

Wow... Thanks for your fast reply!
Well just to be sure, if I go through that tuto (type mrbluecoat tutorial restore verizon droid razr on Google) with the files you provided it should be ok?
Or is there another special process? (I see a lot of files that are not mentioned in the tuto...)
Thank you a lot, I will have to go to work now and I am not at office today, so I will probably try this tonight! (Hope is back! :good
Nice day to all

Mangaf said:
Wow... Thanks for your fast reply!
Well just to be sure, if I go through that tuto (type mrbluecoat tutorial restore verizon droid razr on Google) with the files you provided it should be ok?
Or is there another special process? (I see a lot of files that are not mentioned in the tuto...)
Thank you a lot, I will have to go to work now and I am not at office today, so I will probably try this tonight! (Hope is back! :good
Nice day to all
Click to expand...
Click to collapse
I'd go with RSD Lite or House of Moto to flash it
Sent from my ATRIX HD using XDA Free mobile app

Hello
I am coming back to the news.
I used House of Moto as you suggested, and after some time struggling to make it work on linux, see below the output of the flashing process.
Flash GPT partition? [y/n]: y
sending 'partition' (32 KB)...
OKAY [ 0.013s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.364s]
finished. total time: 0.377s
Flash motoboot partition? [y/n]: y
sending 'motoboot' (1347 KB)...
OKAY [ 0.114s]
writing 'motoboot'...
flashing aboot ...
flashing rpm ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
flashing tz ...
OKAY [ 3.927s]
finished. total time: 4.041s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
sending 'modem' (30720 KB)...
OKAY [ 2.346s]
writing 'modem'...
OKAY [ 1.101s]
sending 'modem' (19148 KB)...
OKAY [ 3.475s]
writing 'modem'...
OKAY [ 3.630s]
finished. total time: 10.553s
sending 'fsg' (165 KB)...
OKAY [ 0.023s]
writing 'fsg'...
OKAY [ 0.854s]
finished. total time: 0.877s
erasing 'modemst1'...
OKAY [ 0.713s]
finished. total time: 0.714s
erasing 'modemst2'...
OKAY [ 0.707s]
finished. total time: 0.707s
sending 'logo' (1709 KB)...
OKAY [ 0.140s]
writing 'logo'...
OKAY [ 1.381s]
finished. total time: 1.520s
sending 'boot' (10240 KB)...
OKAY [ 0.793s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.517s
sending 'recovery' (10240 KB)...
OKAY [ 0.809s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.552s
sending 'system' (30720 KB)...
OKAY [ 2.358s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 2.684s
erasing 'cache'...
OKAY [ 1.195s]
finished. total time: 1.195s
rebooting...
Well, it seems boot, recovery and system.img failed...
On the other hand, I have the logo back and the battery charging when I turn it off and plug it to the outlet....
that is still an advance compared to this morning.
What is missing? maybe it was not the proper version of the FXZ?
I had Kitkat on my phone already, after an update from Motorola, and no doubt about it, it is an XT925 (it is written behind).
Thanks for all.

One more detail that can make a difference I think: my bootloader is locked...
I've read somewhere than you cannot downgrade if it is locked... then if there is a way to unlock it from fastboost, maybe I can try the Jelly Bean firmware?

Mangaf said:
One more detail that can make a difference I think: my bootloader is locked...
I've read somewhere than you cannot downgrade if it is locked... then if there is a way to unlock it from fastboost, maybe I can try the Jelly Bean firmware?
Click to expand...
Click to collapse
Yes, a locked bootloader does make a difference. I assumed you already were, but its ok, we can fix this. Use this link to get rooted and unlocked
http://forum.xda-developers.com/showthread.php?t=2797116

Well I tried the tools at the given link, but they don't seem to work...
Since I only have access to the fastboot mode, I think it is a problem to detect the phone with adb.
When I do "adb devices" on a command line, there is nothing detected while with "fastboot devices" the phone is detected.
Yeah it is very boring I know, but I think unless there is a method that can fully work on the fastboot mode, I don't see any way to get through this xD

Wow!! I cannot belive that this phone is finally on!!!! :crying: (tears of happiness!!!)
Here is what I did finally (in detail):
As I told you, when I do "fastboot devices" in the terminal it detects the device, that means in some way I must hive some proper drivers installed I guess...
I tried to find a way to unlock the bootloader from the fastboot. It turns out that the official tuto provided by Motorola itself just require fastboot!!
(motorola-global-portal.custhelp / unlock-your-device).
So I followed the instructions:
$ fastboot oem get_unlock_data
It gave me some numbers, that I returned back to Motorola (need to sign in) who returned me the *My_Unique Number* to unlock my phone.
Then a last step was:
$ fastboot oem unlock *My_Unique Number*
And as magic: that was it!!!
But my pain was far from being over! (Ok not that far...., for not to discourage those who are in the same case )
After that, I had that famous issue of "Battery Low" at the bootloader... xD Perfect moment for the!
I never could have the big battery on the screen charging, no matter what I tried, but just the screen reminding me that I've unlocked my bootloader, then I may be in trouble.... (well at this state, I think no trouble from this phone can really scare me now!).
I even sacrificed one mini USB cable (RIP) trying to get some kind of factory cable, and of course that didn't work....
So I was about to give up, then I just plugged it as if I was charging it at that time it was still working properly... , it popped up the warning screen again about the bootloader, and I just left it there for few minutes (20 min approximately).
When I turned it on again, it turned out that it was charging indeed! So I got the "Battery OK" mode!!
Finally, I took the KitKat FXZ files you provided to me earlier, and I used HouseOfMoto to flash it! Everything went good until it riched "system.img", and it went through a kind of loop.... xD
Well after several sending 'system' and writing 'system', I decided to stop it! Then I took a Brasilian Jelly Bean version FXZ file, restarted the process, and arriving at system, same thing! But this time I left it go, and at some point, it seems it stopped... then the "Battery Low" came again and then all the rest (few actually) failed, and terminated the process.
Then the rebooting moment came, and I have never been so happy to read Portuguese on my screen !
I want to say a big thanks to the team of this website for the really (but really really) amazing work they are doing. But of course, special HUGE thanks to you palmbeach05, because if you didn't answer me that fast, and helped me so much, I would have thrown this phone already!
Thanks man! :good:
Cheers!

Mangaf said:
Wow!! I cannot belive that this phone is finally on!!!! :crying: (tears of happiness!!!)
Here is what I did finally (in detail):
As I told you, when I do "fastboot devices" in the terminal it detects the device, that means in some way I must hive some proper drivers installed I guess...
I tried to find a way to unlock the bootloader from the fastboot. It turns out that the official tuto provided by Motorola itself just require fastboot!!
(motorola-global-portal.custhelp / unlock-your-device).
So I followed the instructions:
$ fastboot oem get_unlock_data
It gave me some numbers, that I returned back to Motorola (need to sign in) who returned me the *My_Unique Number* to unlock my phone.
Then a last step was:
$ fastboot oem unlock *My_Unique Number*
And as magic: that was it!!!
But my pain was far from being over! (Ok not that far...., for not to discourage those who are in the same case )
After that, I had that famous issue of "Battery Low" at the bootloader... xD Perfect moment for the!
I never could have the big battery on the screen charging, no matter what I tried, but just the screen reminding me that I've unlocked my bootloader, then I may be in trouble.... (well at this state, I think no trouble from this phone can really scare me now!).
I even sacrificed one mini USB cable (RIP) trying to get some kind of factory cable, and of course that didn't work....
So I was about to give up, then I just plugged it as if I was charging it at that time it was still working properly... , it popped up the warning screen again about the bootloader, and I just left it there for few minutes (20 min approximately).
When I turned it on again, it turned out that it was charging indeed! So I got the "Battery OK" mode!!
Finally, I took the KitKat FXZ files you provided to me earlier, and I used HouseOfMoto to flash it! Everything went good until it riched "system.img", and it went through a kind of loop.... xD
Well after several sending 'system' and writing 'system', I decided to stop it! Then I took a Brasilian Jelly Bean version FXZ file, restarted the process, and arriving at system, same thing! But this time I left it go, and at some point, it seems it stopped... then the "Battery Low" came again and then all the rest (few actually) failed, and terminated the process.
Then the rebooting moment came, and I have never been so happy to read Portuguese on my screen !
I want to say a big thanks to the team of this website for the really (but really really) amazing work they are doing. But of course, special HUGE thanks to you palmbeach05, because if you didn't answer me that fast, and helped me so much, I would have thrown this phone already!
Thanks man! :good:
Cheers!
Click to expand...
Click to collapse
Now you can either stay with that or upgrade it to KK. For you guys on the RHD, its all a matter of what bl you want to be on. Most of the ROMs (if you choose to move to custom firmware) is kkbl based for RHD since you guys did get that update from Moto.

Help! Bricked my phone?

So I booted my phone into the bootloader this morning intending on using one of the factory images provided by Google to restore my phone to stock. I downloaded the image, plugged the phone in, and ran the flash-all.bat script inside the zip file. The bat file got exactly this far:
target reported max download size of 536870912 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.147s]
writing 'bootloader'...
OKAY [ 0.126s]
finished. total time: 0.276s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.014s
< waiting for any device >
Then the phone immediately shut off and will not turn back on. I can't get into the bootloader or anything, screen won't turn on, the LED light doesn't blink. I've tried every combination of volume up, volume down, and power button i can think of and I've tried several different chargers to no avail. Is the phone bricked? What could possibly have caused that? Any help would be greatly appreciated.

Look in device manager for new device when connecting nexus by usb. It could show up as Qualcomm ..... sonething. Dont remember it

aciupapa said:
Look in device manager for new device when connecting nexus by usb. It could show up as Qualcomm ..... sonething. Dont remember it
Click to expand...
Click to collapse
Ok I see "Qualcomm HS-USB QDLoader 9008", but now what?
*Edit* Found this: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
I'm about to give it a whirl, Ill post back here with results... Fingers crossed.

Check this http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301

aciupapa said:
Check this http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
I appreciate your help but it turns out I'm an idiot- I meant to post this in the Nexus 5X forums. Any chance a mod could move it there?

@bipolarbear58 idk

Random Reboots, Then Phone Bricked Itself! Help Recover My Kid's Disneyland Videos!

This is a standard US Google Pixel 128GB that I picked up in January from Swappa. I have not ever modified it in any way. Never been dropped or abused either.
Since early April, the phone would randomly freeze and reboot itself. Sometimes it would be days between reboots, sometimes it would reboot multiple times even before it finishes booting. It's usually random, but I noticed it would always reboot if I am recording a really long video (5-10 minutes). Audio also failed once (no sound could be heard from speaker or earpiece) even after rebooting multiple times. Three days ago, while recording a long video of my kid at Disneyland, it froze. This time, the reboot failed to. The screen flashes some garbled stuff on the screen. Only difference this time is that I know the internal flash memory was almost full before I even started recording the video.
I can't get the phone to boot at all. If I press the vol-down button (doesn't even need the power button), I can get to the bootloader menu. In the bootloader menu, if I choose "Start," Restart bootloader," or "Recovery mode," the screen will flash again forever (I've waited hours). If I choose "Barcodes," then I will see all the proper IME/SKU/Serial numbers and barcodes. Choosing "Power off" works too, if it's not plugged in -- if it's plugged into power, the screen will flash a "static" screen endlessly. I took a video of this happening at Disneyland.
https://youtu.be/VlQ_PpZQ9SY
https://youtu.be/5m8_u0nQ4hE (the flashing screen)
After I got back from vacation, I plugged it into a Windows PC. No ADB access, but I can get fastboot to see it. Trying to reflash the lastest stock image (https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3) fails with this:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.810s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.919s
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.055s
< waiting for any device >
Click to expand...
Click to collapse
The screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.430s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.542s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
< waiting for any device >
Click to expand...
Click to collapse
Once again the screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: FA6C70300873
checking product...
OKAY [ 0.052s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1703151359'.
finished. total time: 0.367s
Press any key to exit...
Click to expand...
Click to collapse
That's it. The bootloader screen does show BL and Baseband versions as "N/A", but can't these be overwritten? And is it normal for the device to say LOCKED? This is everything on my bootloader screen:
BL: N/A
Baseband: N/A
Product/Variant: sailfish-US-PVT
Serial Number: FAxxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Click to expand...
Click to collapse
If it'll help, I can get better photos/videos of the phone. The screen flashes some random distorted Google/Android logos and some "static"-looking pixels.
Any clue about what I should do? I would like to be able to get my photos/videos from the phone. I would also like to be able to recover the phone. Doing both would be awesome. I'm not sure if there is a hardware issue or software issue, but this phone has been horrible since April.

I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.

Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.

Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard

UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
justinxfan said:
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Click to expand...
Click to collapse
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
danielt021 said:
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
Click to expand...
Click to collapse
adb didn't see the device. Just fastboot.

ken830 said:
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
adb didn't see the device. Just fastboot.
Click to expand...
Click to collapse
Yep sounds like the boot loader is screwed. Phone is a brick. She thing happened to my Nexus 7. I had to replace the motherboard.

did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.

AlphaOrion said:
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
Click to expand...
Click to collapse
Sorry to hear this, but I didn't have any solution except for replacing the entire phone. You should contact Google anyhow.

this is so disappointing...I wonder how many people this has happed to already, I was using the phone and it just randomly shut off and wont turn back on..almost exactly what the OP is experiencing...obviously phone is now out of warranty and apparently motherboard needs to be replaced (which is ridiculous!!)….I've never had a phone brick on me ever, never thought it would actually happen, especially on stock everything.
---------- Post added at 08:02 AM ---------- Previous post was at 07:57 AM ----------
Maybe its me....but it seems like more and more people are having this issue...looks like as the hardware gets older the more prone to partition being corrupted....this is not acceptable for a 2 year old phone

I have had numerous pixel replacements. One of them was a hard brick like yours. Even took it to iFixit and they confirmed it was dead. So it may not be uncommon.

I just don't get if photos and videos were so important if no one ever does a weekly backup? Use Google drive, use Google photos, use your USB cable to PC if you don't trust Google.
Phones break, get over it. You want a fast phone? Expect it to die even faster. 2 years for a phone is normal, if you don't think it is get then budget phones are there, with the long life low hardware aspect

I had TWRP and Magisk flashed. Now I wanted to go back, flashed factory, locked the bootloader and now I can only boot into fastboot. Everything elsa ends in a bootloop with a short flashing Google logo.