Develop Bugs

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs

Nexus 7 (2013) self-bricked??

Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.

jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed

I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk

jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.

All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk

If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.

LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.

mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel

Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.

Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img

If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk

jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.

I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.

TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk

jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi

I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk

My 5x bootloops and I can't even get into recovery..

My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?

It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.

k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.

sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.

redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.

sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.

Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.

redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?

okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.

Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app

The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.

sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.

Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.

redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.

I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.

I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)

Phone won't boot into Android or Recovery Mode. Help?

32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?

Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone

Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium

I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.

I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium

dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk

Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk

Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.

maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.

Stock, Locked BL, Cannot Boot OS - Save User Files

My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?

I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?

annoyingduck said:
My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?
Click to expand...
Click to collapse
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.

Vulkaistos said:
I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?
Click to expand...
Click to collapse
If it can't be done manually, NRT won't be able to do it either. Plus I feel that toolkits will someday become the foundation for the demise of humanity as a whole.
sfhub said:
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.
Click to expand...
Click to collapse
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!

annoyingduck said:
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!
Click to expand...
Click to collapse
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.

sfhub said:
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.
Click to expand...
Click to collapse
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Sent from my XT1575 using Tapatalk

annoyingduck said:
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Click to expand...
Click to collapse
The FULL OTA *is* a full image flash.
Did you factory reset?

The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Sent from my XT1575 using Tapatalk

annoyingduck said:
The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Click to expand...
Click to collapse
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.

sfhub said:
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.
Click to expand...
Click to collapse
Neither do I, it's a first.
Sent from my XT1575 using Tapatalk

annoyingduck said:
Neither do I, it's a first.
Click to expand...
Click to collapse
Sorry, I should be more clear, could you list what it says.
It sounds like the flash script is not checking for errors at the end so there is some error flashing within one of the partitions, but the overall script is saying everything good.