Database Users

Solved - Thanks anyhow - Factory Reset Gone Wrong - Assistance Required

EDIT: Its amazing how typing everything help when asking for help can give you an idea on how to fix it. I downloaded the recovery image manually, unpacked it once, loaded it up in RapidCRC to figure out its MD5, restarted the factory reset program, and bam all working. Guess I was just being dumb and overlooking the obvious. Thanks anyhow all. Sorry for the trouble.
Hello all, I am in quite the pickle and I hope someone here can help me.
Not long ago I unlocked my Nexus 10's boot loader and installed TWRP recovery and a rooted copy of 4.2.2. I did all of this using the latest Nexus root toolkit, and I had zero issues. However recently I decided to revert back to stock completely. This brings me to the problem I am having.
So this morning these were my exact steps. Again, the current state of my Nexus 10 before I did anything was Unlocked Bootloader, TWRP Recovery, and 4.2.2 rooted installed. Nothing else.
I loaded up the Nexus Root Toolkit and connected my tablet to my computer making sure to use a USB port that worked last time. Made sure USB Debugging was enabled and clicked the "Flash Stock + Unroot" button. I followed all the steps and selected the latest (4.2.2) recovery image. Everything appeared to be going ok. I will now post exactly what I saw on the flashstock.bat window below.
sending 'bootloader' <1280 KB>...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 0.124S]
finished. total time: 0.270s
rebooting into bootloader....
OKAY [ 0.004s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 535248732 bytes
error: update package missing system.img
It then closed and showed the completion message in the console window and said something along the lines of "press any key to close". In the bootloader it said " fastboot status fail signature verification".
At this point I thought "well, maybe it did not send the reboot single" so I selected the reboot option from the bootloader and all it did was hang at the google logo. Nothing happened. Next I tried rebooting into the bootloader and selecting recovery. Here is where I got very worried as nothing happened except a black screen. Nothing at all. Its like it does not have a recovery system at all.
I tried redoing the whole process and the same thing happened. I hope someone can help me as I really have no idea what to do and am quite frightened I broke it. The only thing I can think that leads me to believe me I can salvage this is that I can still get into the bootloader and as a result I assume I can get into fastboot.
Any help would be greatly appreciated.
Thanks very much,
-S

Glad you got it solved.

[Solved] Root with locked bootloader, flash failure XT907

Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.

cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641

aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.

cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse

aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse

Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.

THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.

cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!

Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907

nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff

Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.

nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3

SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767

No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?

[Q] Fastboot bootloop??

My Razr M is in a state where all I can do is boot into fastboot. I was trying to fastboot back to stock Jellybean by using Matts Utility 1.20. I received the following when the utility ran:
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*]
[*] Before continuing, ensure your Razr is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'mbm' (512 KB)... OKAY [ 0.063s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.011s]
writing 'mbmloader'... INFOInvalid partition name mbmloader
FAILED (remote failure)
sending 'mbm' (512 KB)... OKAY [ 0.056s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
erasing 'cache'... OKAY [ 12.865s]
sending 'logo.bin' (854 KB)... OKAY [ 0.102s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
sending 'devtree' (512 KB)... OKAY [ 0.069s]
writing 'devtree'... OKAY [ 0.325s
Everything fails?????? My phone screen says the following.
AP Fastboot Flash Mode (S)
10.9B(#) (sha-1e9f557, 2013-02-22 09:18:22)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code:3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I reboot the phone whether connected usb or not it comes back to the fastboot screen and says Flash Failure! Any Ideas of what I can do? I have a factory cable and have tried it as well as standard USB cable. I tried booting into recovery and once I press volume up, it sticks on my bootlogo and will not go into recovery?
Update: I am a complete retard and was using the wrong Utility. WOW rookie mistake. Sorry. Using the Utility for XT912 not XT907

Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.

RikRong said:
Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.
Click to expand...
Click to collapse
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?

evocop said:
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?
Click to expand...
Click to collapse
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.

RikRong said:
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.
Click to expand...
Click to collapse
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.

evocop said:
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.
Click to expand...
Click to collapse
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.

RikRong said:
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.
Click to expand...
Click to collapse
Well I downloaded Deadcalm rom and flashed. Booted to language screen and screen is unresponsive still. Is it done for?

A dmesg might be useful.
Maybe you could try flashing a non-stock based ROM (CM, Carbon, etc) and see if overwriting the boot.img with something completely non-stock might fix it...
It sounds like a driver (boot.img) issue, but that should be fixed with a simple reflash of a correct RSD XML...
EDIT: I really don't think you're done for, since we are booting the OS. May need some... Advanced fixing though
Sent from my Nexus 7 using Tapatalk 4

Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"

Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?

yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.

productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.

Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!

productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways

[HELP] Bricked LG G6 US997, Need help

Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.

Have you tried flashing anything from fastboot?

If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea

boksquare said:
Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.
Click to expand...
Click to collapse
Did you relock the bootloader ?

cory733 said:
Have you tried flashing anything from fastboot?
Click to expand...
Click to collapse
No I have not. Should I? What should I flash thru fastboot?
jimbomodder said:
If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
Ok I will try that
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea
Click to expand...
Click to collapse
numpea said:
Did you relock the bootloader ?
Click to expand...
Click to collapse
No I did not. Should I? I bricked my HTC One once doing this and I remember locking bootloader would make things harder to fix for me.

Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.

cory733 said:
Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.
Click to expand...
Click to collapse
I don't really have lots of USB cables or computers at my disposal though.. Do I just keep trying until it works, and even if so, how do I know when the phone is detected in download mode?
I also found out that even though I can enter fastboot, my bootloader is somehow locked again, and I can't flash the unlock bin so I can't even get a custom recovery to be flashed on there. Any other ideas or is my phone dead for good?

New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?

boksquare said:
New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?
Click to expand...
Click to collapse
maybe you locked the bootloader at some point with twrp !
maybe your unlock.bin is corrupted you need either unlock bootloader or try to flash kdz via download mode accessing
if you can't do that, LG center is the only way good luck

Why were you originally trying to flash stock firmware?

cory733 said:
Why were you originally trying to flash stock firmware?
Click to expand...
Click to collapse
I realized the visual appeal of custom OSes no longer attract me as much as full usability (Using google pay or fingerprint in some apps) and stability as I used to when I was young. I wanted to flash stock firmware and just keep root and xposed to enhance my stock experience.

Update 2:
I contacted LG and they quoted me a minimum of $300 and up for repairs.. Really hope someone has a fix to my issue or any other suggestions. I'm thinking about taking to a phone repair store but I doubt they will be able to fix this. I live in Houston, TX area if anybody has store suggestions. Thank you

So what rom were you on? And how did you flash it without TWRP? Can you go through from start to finish exactly what you did?