Develop Bugs

[Brick phone] help needed

I have flashed many phones before my G4 and this is the first time I'm having to ask for help.
The firmware installed was AICP CM13, then the screen went green with a DemiGod message. I held the vol down button to reboot and it came back up. After a few restarts and green screens i figured I needed to reflash the firmware. I booted into Recovery and while wiping the device to flash a new firmware, TWRP crashed. After leaving it for half hour or so, I took the battery out to enter into TWRP so I can flash the new firmware. TWRP is no there to be seen. I hold down the vol down and power button, releasing power for second or two and choose to go into recovery. Every time the phone just gets stuck on the LG screen displaying "Bootloader state :Bootlader unlocked!".
In short, I have no firmware, the device has been wiped and TWRP doesn't seem to be working.
I have tried to flash a KDZ file (H81520A_00.kdz) using the flash guide here. This comes back as unsuccessful saying "connection to server failed". As shown below.
View attachment 3605673
The method to flash an .img file using cmd on the pc includes moving the 4gb .img file to the parent folder of the phone storage. I can't get to move any files whatsoever to my device so figured this method would not work.
Seems if I can somehow flash TWRP, then I should be able to install a new firmware.
Any help much appreciated.

Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!

rav101 said:
Hi, Can you get an ADB connection to your phone, or get your phone into bootloader somehow. From there you could try 'fastboot boot recovery.img'?
If so, then from within TWRP you can flash twrp recovery so the recovery is then sorted. Then you could flash click here (the full version). This will then allow LG UP to find a connection. From there if you really wanted to can flash any KDZ as a proper reset. Hope it works buddy!!
Click to expand...
Click to collapse
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?

AndHD2 said:
I can get into recovery but I am unsure as to how I could try 'fastboot boot recovery.img'. Would that be the same as flashing an img when the root method first came out?
Click to expand...
Click to collapse
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi

It is late here and with me being tired I said recovery instead of download. I can boot into download mode but when I try to boot into recovery then it just goes straight to the LG splash screen and it will either remain in that screen or the green Demigod screen would come up.
I'm off to sleep and away from my laptop as I have to be up in 5 hours. Luckily I still have my Note 4 so at least I'm not without a phone in the morning. I will try the steps what you have suggested just as soon as I get back from work.
Many thanks

rav101 said:
Just to make sure you know. TWRP is your recovery. Your last message said you did not have TWRP?
When I first rooted my phone (and subsequently when I install a .kdz), I have to go into the bootloader and install TWRP. I personally do this by using the above command "fastboot boot recovery.img" with the recovery.img being placed on my computer in the same location as my adb installation. This command only boots up TWRP but does not flash it. I then flash twrp by having a copy of it on my external sd card. Within twrp you can select to flash zip, or there is an option to flash an image. I use this to flash twrp (from twrp... its a little inception like but it works). Once you have twrp up and running, you can install a rom. If you want to do flash a .kdz, I have found you need to be on a stock based rom in the first place hence why i referenced the v20a full system zip.
Hope that made sense.
Regards,
Ravi
Click to expand...
Click to collapse
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.

AndHD2 said:
I have finally got chance to sit down and have a go at performing the procedure listed above. I downloaded the adb and fastboot installation as outline here. It is the minimum to what this thread says I will need for my device. I moved the recovery.img to the installation location which were in Windows/programs files (x86)/Minimal adb and fastboot. I launched the program and typed in 'fastboot boot recovery.img'. I tried this in download mode, charging mode (phone off) and while on the LG flash screen where TWRP didnt load but in all cases I have had no response at all.
If someone can help the much appreciated.
Click to expand...
Click to collapse
Hi @AndHD2, I'm sorry but I can't think of anything else

rav101 said:
Hi @AndHD2, I'm sorry but I can't think of anything else
Click to expand...
Click to collapse
I had another demigod type screen but this was grey and not green with less detail. However it did say it were a kernel error.
Is the handset still under warrenty with the bootloader unlocked. I have a feeling its not

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.

Nexus 5X Bootloop even after stock flash

I was just surfing in the internet when my Nexus froze and rebooted but it did not boot again because during the boot animation it froze and reboots.
I have no problem with this because i flashed it lots of time and everything has always worked, so i downloaded the latest factory image rom google (7.1.1) and tried to flash it WITHOUT WIPING dalvik-cache via TWRP.
The flashing process has reported no errors but when I try to boot my phone it freezes during the boot animation and reboots.
I cannot even get into the recovery because the stock recovery says no-command and the if i flash twrp with fastboot it does not even start.
I tried fastboot erase cache, system, boot, etc and flashed again but the result is the same.
I can get into fastboot mode and download mode and the bootloader is unlocked.
What can I do to revive it?
If I flash stock rom and lock bootloader can i send it to assistance (warranty is two years in Italy so I am still covered)?.
Thank you very much
Sorry for the bad english
UPDATE: Go to my last post.

Edoardo396 said:
I was just surfing in the internet when my Nexus froze and rebooted but it did not boot again because during the boot animation it froze and reboots.
I have no problem with this because i flashed it lots of time and everything has always worked, so i downloaded the latest factory image rom google (7.1.1) and tried to flash it WITHOUT WIPING dalvik-cache via TWRP.
The flashing process has reported no errors but when I try to boot my phone it freezes during the boot animation and reboots.
I cannot even get into the recovery because the stock recovery says no-command and the if i flash twrp with fastboot it does not even start.
I tried fastboot erase cache, system, boot, etc and flashed again but the result is the same.
I can get into fastboot mode and download mode and the bootloader is unlocked.
What can I do to revive it?
If I flash stock rom and lock bootloader can i send it to assistance (warranty is two years in Italy so I am still covered).
Thank you very much
Sorry for the bad english
Click to expand...
Click to collapse
So you followed these instructions?
fastboot flash bootloader C:/image-bullhead-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-bullhead-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-bullhead-XXXXXX/system.img
fastboot flash vendor C:/image-bullhead-XXXXXX/vendor.img
fastboot flash userdata C:/image-bullhead-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-bullhead-XXXXXX/boot.img
fastboot flash recovery C:/image-bullhead-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-bullhead-XXXXXX/cache.img
- After everything finished, select "Recovery" using the volume buttons.
- When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
- Reboot. Your phone should be stock.

Most likely you need a new motherboard. Search the forum for the topics about this hardware bootlooping fault. LG is has admitted the n5x has this problem and will exchange/repair/refund.
Don't waste time solving it yourself.

Tulsadiver said:
So you followed these instructions?
fastboot flash bootloader C:/image-bullhead-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-bullhead-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-bullhead-XXXXXX/system.img
fastboot flash vendor C:/image-bullhead-XXXXXX/vendor.img
fastboot flash userdata C:/image-bullhead-XXXXXX/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-bullhead-XXXXXX/boot.img
fastboot flash recovery C:/image-bullhead-XXXXXX/recovery.img
fastboot erase cache
fastboot flash cache C:/image-bullhead-XXXXXX/cache.img
- After everything finished, select "Recovery" using the volume buttons.
- When a small Android appears, press Power Button + Volume UP.
- Select "Wipe data/factory data reset"
- Reboot. Your phone should be stock.
Click to expand...
Click to collapse
Yes, i followed these procedure. I have also tried to erase system/boot/cache etc... before flashing. Result is the same.
peltus said:
Most likely you need a new motherboard. Search the forum for the topics about this hardware bootlooping fault. LG is has admitted the n5x has this problem and will exchange/repair/refund.
Don't waste time solving it yourself.
Click to expand...
Click to collapse
Ok, thank you, now I re-flash original android 7.1.1 and re-lock bootloader and trying to send it to warranty, I will let you know.
Sorry for the bad english

Edoardo396 said:
I was just surfing in the internet when my Nexus froze and rebooted but it did not boot again because during the boot animation it froze and reboots.
I have no problem with this because i flashed it lots of time and everything has always worked, so i downloaded the latest factory image rom google (7.1.1) and tried to flash it WITHOUT WIPING dalvik-cache via TWRP.
The flashing process has reported no errors but when I try to boot my phone it freezes during the boot animation and reboots.
I cannot even get into the recovery because the stock recovery says no-command and the if i flash twrp with fastboot it does not even start.
I tried fastboot erase cache, system, boot, etc and flashed again but the result is the same.
I can get into fastboot mode and download mode and the bootloader is unlocked.
What can I do to revive it?
If I flash stock rom and lock bootloader can i send it to assistance (warranty is two years in Italy so I am still covered).
Thank you very much
Sorry for the bad english
Click to expand...
Click to collapse
I have the same issues I flash the stock rom and locked my bootloader and I sent it to lg they want to me to pay 130 (the real price is 180euros)anyway just sent it to lg witout locking your bootlader they can fix it for less money
they say me there no official words for lg ....sorry for my bad English I am Cypriot

dimitrispas22 said:
I have the same issues I flash the stock rom and locked my bootloader and I sent it to lg they want to me to pay 130 (the real price is 180euros)anyway just sent it to lg witout locking your bootlader they can fix it for less money
they say me there no official words for lg ....sorry for my bad English I am Cypriot
Click to expand...
Click to collapse
I hope they will fix it for free since i haven't done anything wrong and the problem is their if the motherboard doesn't work. I still have warranty (in italy it is 2 years by law).
Anyway the assistance in Italy sucks and I went to 3 different repair centers and they said they cannot accept any device because of in 12 days it's Christmas and I should return in January. Are you kidding me? I think I will send it to the shop where I bought.
Isn't there any method to repair it myself?
Thank You and sorry for my English

UPDATE: I sent the phone to LG and they changed the motherboard, when I have gotten it back (today) I noticed that it was running the android version 7.0 Nougat and I tried to update it to 7.1.1 via OTA but the update failed and the phone rebooted.
The phone works fine with Android 7.0 but I bought a Nexus to have the latest release of android so I decided to flash to 7.1.1 and I have seen that in fastboot mode it says: "SECURE BOOT: ....(no rpmb)" but at the firt time I ignored it. I used the command fastboot flashing unlock to unlock the bootloader but then when I tried to reboot I noticed that the bootloader was still locked. I tried this 3 times with no result.
I searched on the internet and found that LG does not want me to unlock the bootloader. I am very mad and I will NEVER buy another LG phone again. They sold me a broken device, replaced MOBO and sent back a phone which I will never be able to unlock even if the warrant would be over. At least they have replaced the mobo for free.
Conclusion: If you are thinking of buying a Nexus or an LG Phone in general DON'T DO THAT.
Thank you very much and sorry for the english

I can't boot into TWRP, any way to save the phone?

The bootloader is unlocked and TWRP is installed on the phone. First boot into it went fine. There I made backups and wiped some /system, /data, internal storage and cache..
Now I get "The System has been destroyed. Press power button to shotdown."
I can get into fastboot, but not into TWRP. Tried power button up, tried "fastboot reboot recovery", tired "fastboot boot twrp.img". Nothing is working.
I have a full backup, but that won't do me much good if I can't get TWRP to run.
Is there any way to get into TWRP? Any help would be very much appreaciated.
Edit: Got it fixed. Basically just follow this if you ever have the same problem: http://c.mi.com/oc/miuidownload/detail?guide=2
Still don't get why TWRP wouldn't boot. Is recovery dependent on system? Who designs a phone like this? Oh well, only important thing is that it works again.

I would like to try this - I'm in the exact same position as you and having twrp back would be a lifesaver. However mine is the Chinese version and I'm not sure if flashing the global version is smart...
Edit: I'm seeing success, but it flashed in 1 second, which did nothing..

Just flash the stock firmware back by bronging your phone to fastboot mode and using Xiaomi's Flash Tool using a fastboot image for your phone.
Once unbricked you can set it up, reinstall twrp, then rinse and repeat if in cases it happens again when trying a custom ROM.
Check this linkfor a thorough unbricking guide.

Lyves said:
Just flash the stock firmware back by bronging your phone to fastboot mode and using Xiaomi's Flash Tool using a fastboot image for your phone.
Once unbricked you can set it up, reinstall twrp, then rinse and repeat if in cases it happens again when trying a custom ROM.
Check this linkfor a thorough unbricking guide.
Click to expand...
Click to collapse
Yes, have seen that guide but I'm getting flash xbl error on latest versions of the Xiaomi Flash Tool. So right now I'm actually stuck on Fastboot with no way to revive it.

nyvled said:
Yes, have seen that guide but I'm getting flash xbl error on latest versions of the Xiaomi Flash Tool. So right now I'm actually stuck on Fastboot with no way to revive it.
Click to expand...
Click to collapse
Use an older version. That worked for most.

Lyves said:
Use an older version. That worked for most.
Click to expand...
Click to collapse
I've tried a few at random. Most threw xbl error, one just flashed in a second and then nothing happened on the phone.
I'll give it another shot. Thanks for suggesting. :/

hy my friend if you have mi account you have to sighnout and then flash recovery and then go to recovery with vol up and power when you stil in the fastboot

Slowking said:
"The System has been destroyed. Press power button to shotdown."
Edit: Got it fixed....
Click to expand...
Click to collapse
no need to follow that tutorial
just flash vbmeta in fastboot using
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
and u r good to go

Have you tried orange fox recovery