Develop Bugs

[Q][help] bricked badly after failed encrypt - fastboot and ODIN can't write to flash

hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo

Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f

i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.

philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img

i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'

philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery

i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.

So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me

EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this

interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...

It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.

problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...

nice work... let them try to fix that shiz!

Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse

philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna

The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !

Unfixable Google Loop - So frustrated

I bought my Nexus 7 2013 shortly after they were available and it was a good device until the release of KitKat. After the KitKat OTA it's been a piece of junk.
After the KitKat OTA it developed a problem where the tablet was on but the touchscreen was unresponsive. The only way to fix it was to shut it down by holding the power button. Eventually it started being stubborn and I'd have to power cycle it several times before it would clear the Google screen. That gradually progressed to having to do a system reset before it would come back to life.
On December 15th it finally refused to go past the Google splash. Attempting to boot into recovery also left you stuck at the Google logo. At the time I tried the WUGFresh tools to do a stock recovery and while I was successful in unlocking no amount of flashing / formatting / erasing would give you a normal boot or a recovery screen.
I sent it off to ASUS on 12/17 and got it back this past Monday (1/13). It worked fine until Tuesday night when once again the screen was unresponsive and I had to shut it down by holding the power button. It's now stuck at the Google screen and no amount of flashing / formatting / erasing using FreshWug or fastboot directly via command line has brought it back.
Here's what I've done so far:
Spammed flash-all at least 6 times
fastboot format of /boot /system /userdata /cache multiple times
Multiple runs of WUGFresh
Flashed 4.4.2 and 4.3 images
What else is there I can do aside from sending it back to ASUS?

Does it boot to bootloader?
Sent from my Nexus 7 using Tapatalk

As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
This
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Pandae said:
As Micheal said, can you get to the bootloader? Do all of these commands go successfully?
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I don't use Wug's tool, preferring to do things from the command line so I know exactly what's being done and to see error messages.
Click to expand...
Click to collapse
Yes to all of those, I just did them again to verify. FYI WUG opens a command shell as it runs fastboot so you can see what it's up to.
Anywhoo I reflashed kot49h (manually) and got the same result, stuck at Google. If this thing wasn't still under warranty I'd snap it in half and light the two halves on fire.
Any other ideas?

What if you tried a custom recovery and custom ROM?

So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?

buelldozer said:
So I ran through the procedure once more last night and it worked! After about 20 minutes the tablet rebooted on it's own, displayed the working android and then booted up. I guess you just need to reflash 22 times?
Click to expand...
Click to collapse
any updates? is it working fine now? any random reboots? god i hated that on my 1st nex7fhd, im on my 2nd one, its and perfect aside from the 'low speaker volume' stock

Might be an hardware issue, don't get stuck with software too much, send it again until they replace it.

I'd be interested in what ASUS did to it.
Did they include a list of parts replaced, etc?

I'm also curious.
As long as the flashes are done correctly it should boot fine.
However, I had a similar issue flashing stock.
The fix was to flash stock. Boot.
If it boot looped restart and wipe dalivik cache and cache and reboot. It should start then. just an FYI...
Sent from my Galaxy Nexus using xda app-developers app

If u get boot loops = lemon, it will develop those anno ying reboots
Via my NeXus™ 7 FHD on Tapatalk⁴ Pro

So it did it again but following the previous directions I was able to unloop it immediately the big story though is WHY it was looping.
I have a minisuit BT keyboard / case ( http://www.amazon.com/Minisuit-Blue...=UTF8&qid=1390433882&sr=8-3&keywords=minisuit ). The thing is dynamite and I love it and it worked great! The keyboard has a low power battery saver state so after you don't use it for a few minutes it basically goes to sleep until you tap a few buttons and wake it up.
I went a week with no issues but I wasn't using the keyboard. When I did finally use the keyboard I would stop typing and let it go to sleep as I always do. When I tapped a few keys it would wake up and then wake up the N7 and it's screen but the screen would -not- accept touch input. I had to hold the power button down and force the N7 to shut off. When I powered it back up...BAM...LOOPED.
It didn't do this before the Kit Kat upgrade. It's obvious that something is wrong with the BT stack in 4.4.2 and when a HID goes into a low power state it hoses the touch input. Since the touch input is hosed you can't shut it down correctly and the file system corrupts, likely the /system partition.
If I use the N7 without the keyboard it's perfectly fine.
userdelroot I couldn't clear dalvik on mine because I couldn't boot to recovery. All boot options lead to a Google Loop.

I have had exactly the same experience, basically. Just got mine back from ASUS, worked for about a day, and then BAM, back to the same DAMN thing! I think you may be on to something about the BT stack. If there is any common thread to both my breakdowns, its that my Nexus got screwed not long after i paired a BT headset with it. Its late and I'm frustrated as all hell so please forgive my short rant. So what to do? Do I send it back to ASUS and hope they actually replace it this time? (The invoice I got back from them was very strange incidentally. I couldn't tell what they did, except among four parts listed, they seemed to replace a "cracked, broken screen" which was not the way it was when I sent it to them???!) Or should I just keep reflashing and hope it takes, as it seemed to do for you? But then can I risk pairing my BT headset again?! This sux.
Update: Woke up this morning, turned it on, and it booted up! WTF? Not complaining I guess. Taking it easy this time, unlocked bootloader still of course, but holding off rooting, and not going to pair any BT with it for awhile. Although its kinda BS I should have to try it this way...

It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.

buelldozer said:
It's at it again but this time time I wasn't using my keyboard (I quit using it thinking that was the problem).I'm attempting to unloop it again using the same procedure as before. Use of the BT may aggravate the problem (it certainly took longer to glitch out this time) but it's not the whole problem.
I didn't have these problems before the 4.4 update so I'm rolling back to 4.3 for some testing.
Click to expand...
Click to collapse
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?

Demian87 said:
I have the same problem. Described it right here: http://forum.xda-developers.com/showthread.php?t=2653430
Nothing helps me =( Please, write down any solution, you are able to find.
You wrote, you was able to boot it normally. What did you do for that?
Click to expand...
Click to collapse
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.

buelldozer said:
Perform these steps in this order:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash-all.bat
Then wait at least a full hour before deciding it didn't work. Mine takes a very long time to 'recover' and boot up after that procedure. I'm beginning to suspect that the problem is actually in the /cache partition as it's one of the things that isn't addressed in the flash-all script and it appears to retain information between reboots. The next time this happens I'm going to format and erase just cache and see what happens.
I'm serious on waiting a full hour, and it may take two. I just started it on mine and am timing it now to see what it actually takes.
Click to expand...
Click to collapse
Thank you a lot! I'll try to leave it turned on for the whole night. I left it only for 45 minutes before that. Probably, that was not enough.

My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.

buelldozer said:
My tablet is now at 3.5 hours and still hasn't left the "Google" screen. "All Night" might be the correct time frame. I'll give it another 4 hours and see what that does.
Click to expand...
Click to collapse
My tablet is now at 9:15 hours and still at Google logo. I'm guessing that the time is not the only matter for normal boot up.
---
Now after 11 hours I gave up. =(

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance

I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that

Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload

Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

[HELP] Access internal memory from Fastboot

First up:
My 5x was rooted and working for 6 months using the amazing step by step posted at: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
It has TWRP custom recovery which I can no longer access.
The only mode I can access is the bootloader using fastboot.
Google has already sent me a replacement but I would like to get as much of my non-backed-up info from the internal memory as possible before returning it.
The phone functioned perfectly in its rooted state for 6 months until one day on vacation when it kept rebooting at random intervals where the intervals got shorter and shorter to the point where the phone was simply unusable. Now it does not boot at all.
Even a week ago ago I was able to go into TWRP once out of 25 tries but now that does not work anymore either.
If you let it try and boot, it will display the "Your device software can't be checked for corruption.... please lock your bootloader..." message. It will then display "GOOGLE" on a plain black screen with an unlocked padlock in the bottom. It will loop between these two screens over and over without every going into the android startup animation screen.
I have reflashed a new stock image from the google repository as well as a new recovery - all of which completed successfully per the messages at the command prompt screen. However this did nothing to fix the actual issue. Same exact screen and bootloop.
At this point I would be happy just to be able to go in and access the information in the two users (I had multi-users setup). Since the bootloader is the only mode I can enter, is it possible to access the internal memory using fastboot? Thanks in advance.

Did you flash the full factory image? It would have deleted all your user information?
Even if not, you would need to access from something like TWRP as the user partition is encrypted, even if you have no password set up (it is encrypted with random password, which itself is then obfuscated by encrypting with known-text)
You could try booting TWRP over USB using
fastboot boot twrp.img
But if I recall correct, twrp has a bug where it can't decrypt user if booted in this way, but I don't remember if that is for pattern/pin/password or even with default known password.

sfhub said:
Did you flash the full factory image? It would have deleted all your user information? Even if not, you would need to access from something like TWRP as the user partition is encrypted, even if you have no password set up (it is encrypted with random password, which itself is then obfuscated by encrypting with known-text)
You could try booting TWRP over USB using fastboot boot twrp.img
But if I recall correct, twrp has a bug where it can't decrypt user if booted in this way, but I don't remember if that is for pattern/pin/password or even with default known password.
Click to expand...
Click to collapse
Thank you Sfhub. Just tried your recommendation of booting TWRP over USB. Still the same issue. The device restarts but never goes into recovery, just loops over and over. And no I did not flash the full image so as to protect the user data still on the device.

Nothing else I could try? Anyone?

anik321 said:
Nothing else I could try? Anyone?
Click to expand...
Click to collapse
It just sounds like your EMMC is dying or dead and whenever something tries to access it, the kernel panics and reboots.

https://dl.google.com/dl/android/aosp/bullhead-mtc19v-factory-f3a6bee5.tgz
Extract the archive and archive saved in it, then try flashing these images:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
and then check if the phone boots. You will not lose data.

No luck :/ but thanks przemcio510
I left the phone alone for a few days and came back to find a weird message saying the encryption process was interrupted and as a result all data is lost. That I should reset the phone to factory conditions to proceed. I am unable to replicate this screen back.
And the bootloop continues...

sfhub said:
It just sounds like your EMMC is dying or dead and whenever something tries to access it, the kernel panics and reboots.
Click to expand...
Click to collapse
If the EMMC was dead, would adb or fastboot complete flashing successfully?

What is your bootloader version? Try reflashing it from fastboot. If it fails, then I have no idea what's wrong.

You could get the message that it completed successfully. Try locking your bootloader, fastboot oem lock. Then reboot to the bootloader. If it doesn't say locked them the emmc is bad.
Sent from my Nexus 9 using XDA Free mobile app

anik321 said:
If the EMMC was dead, would adb or fastboot complete flashing successfully?
Click to expand...
Click to collapse
I don't know if fastboot does error checking. The OTA should be doing error checking.
One issue is the problem area of EMMC might not be the system/vendor/boot partitions.
It doesn't need to be catastrophic failure where everything is affected. It can be partial failure.

jd1639 said:
You could get the message that it completed successfully. Try locking your bootloader, fastboot oem lock. Then reboot to the bootloader. If it doesn't say locked them the emmc is bad.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
If you re-lock your bootloader, that wipes userdata now as well.

[TRIED FLASHING FACTORY IMAGES] H790 random power-offs, not bootloop

Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help

bilboswaggins22 said:
Hi,
I did try to search this problem but couldn't really find the words I needed to get enough specificity to differentiate it from other problems which weren't mine, so sorry if this post is a duplicate of something else.
My problem is that my 5X 16GB will power off consistently and boot itself up again. It isn't a bootloop because it isn't an instantaneous shut down, but can often stay on for about 2-5 minutes, sometimes staying on for almost an hour. There doesn't really seem to be any pattern or predictable nature to it, as sometimes when the device powers back on the default launcher and 'system' will stop working and the device will just give up, skipping straight to the boot animation and skipping the google logo.
I have tried erasing and formatting all partitions on the device i could get my hands on (namely recovery, cache, system, userdata, and boot), then flashing in the following order:
fastboot flash bootloader bootloader-bullhead-bhz11h.img
fastboot flash radio radio-bullhead-m8994f-2.6.36.2.20.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Sometimes I was able to get the device working for a long time such as two days with the device acting completely normally, and it would only enter its old state when it powered off. I can't really remember what I did to get the device working before, but I'm fairly sure it was something like flashing 6.0.0 (which would behave strangely, with the setup sometimes crashing and the device rebooting) and update the device OTA, which restored it to a state of normality.
Am quite lost right now and very frustrated- this is my second phone, the first being a Oneplus One which is also cocked up :crying:
Thanks for any help
Click to expand...
Click to collapse
Request an exchange from LG or Google.
Sent from my Nexus 5X using Tapatalk

HW bootloop begins with random reboots. So bring back to LG right now.
(Flash stock, Lock the bootloader if unlocked etc)