Develop Bugs

[Q] Nexus 7 stuck in Fastboot

I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?

Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk

ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.

So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk

Check if your Android SDK is up to date

ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>

What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.

ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.

djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.

End of knowledge - Need help with bricked Z1C

Hello Everyone,
i wanted to flash a newer CM Rom (12.1). But since WiFi didn't work i wanted to go back. Now it seems i "overflashed" my phone... Long story short, the following is what i can do atm:
-get into Fastboot mode
-get into Flash mode
What i tried:
Using flashtool and flashing different ftf's to no success. Flashtool aborts the flash process at this line: x10flash.java:770 error (beforehand it says "parsing boot delivery" followed by "ending flash session")
Using fastboot to get into a recovery. Fastboot either gives "command not allowed" or "too many links"
At one point i was able to boot into a recovery, but that stopped working as well now.
I've never experienced a brick that crazy. Besides entering the two modes, i can do exactly nothing with it.
I have somewhat experience with flashing (owned a galaxy s3 before, flashed many times) and have flashed to the z1c many times.
No backup ofc, doh. But it doesn't matter since i backuped all my personal stuff anyway.
My question: is there any way i could do a FULL clean installation? Stock ROM or whatever. Just so i can get into a recovery at least again!
Edit/ the phone shows up under devices in fastboot "CB5A1YERET". Flashtool on the other hand says, "unknown" if i look at the debug log.
Edit2/ I don't even get to see the Sony logo. So it seems, the phone is stuck somewhere in the beginning of the boot up. When i plug it into the pc, the plug/unplug usb sound comes every 1-2 minutes.

goop.Q said:
Hello Everyone,
i wanted to flash a newer CM Rom (12.1). But since WiFi didn't work i wanted to go back. Now it seems i "overflashed" my phone... Long story short, the following is what i can do atm:
-get into Fastboot mode
-get into Flash mode
What i tried:
Using flashtool and flashing different ftf's to no success. Flashtool aborts the flash process at this line: x10flash.java:770 error (beforehand it says "parsing boot delivery" followed by "ending flash session")
Using fastboot to get into a recovery. Fastboot either gives "command not allowed" or "too many links"
At one point i was able to boot into a recovery, but that stopped working as well now.
I've never experienced a brick that crazy. Besides entering the two modes, i can do exactly nothing with it.
I have somewhat experience with flashing (owned a galaxy s3 before, flashed many times) and have flashed to the z1c many times.
No backup ofc, doh. But it doesn't matter since i backuped all my personal stuff anyway.
My question: is there any way i could do a FULL clean installation? Stock ROM or whatever. Just so i can get into a recovery at least again!
Edit/ the phone shows up under devices in fastboot "CB5A1YERET". Flashtool on the other hand says, "unknown" if i look at the debug log.
Edit2/ I don't even get to see the Sony logo. So it seems, the phone is stuck somewhere in the beginning of the boot up. When i plug it into the pc, the plug/unplug usb sound comes every 1-2 minutes.
Click to expand...
Click to collapse
What commands are you typing in fastboot that are getting you those responses? When you're connected in fastboot, what do you get when you type 'fastboot', or 'fastboot devices'?

levone1 said:
What commands are you typing in fastboot that are getting you those responses? When you're connected in fastboot, what do you get when you type 'fastboot', or 'fastboot devices'?
Click to expand...
Click to collapse
Hi,
following commands:
fastboot boot boot.img
fastboot flash recovery recovery.img
fastboot -w
fastboot shows me the commandlist
fastboot devices shows the phone, see my first post.
Edit/ Somehow i was able to boot a boot.img (i believe its the boot.img from the last known cm version i flashed), but the phone got stuck at the Sony logo. Now its not working again.
I still have the TA backup, but how the hell can i restore it? nearly every tool out there needs me to enable usb debugging and/or adb. which i can't, cause i'm not able to enter the phone in any way.
I fear, that i hard-bricked my phone to a point were it can not be repaired...

goop.Q said:
Hi,
following commands:
fastboot boot boot.img
fastboot flash recovery recovery.img
fastboot -w
fastboot shows me the commandlist
fastboot devices shows the phone, see my first post.
Edit/ Somehow i was able to boot a boot.img (i believe its the boot.img from the last known cm version i flashed), but the phone got stuck at the Sony logo. Now its not working again.
I still have the TA backup, but how the hell can i restore it? nearly every tool out there needs me to enable usb debugging and/or adb. which i can't, cause i'm not able to enter the phone in any way.
I fear, that i hard-bricked my phone to a point were it can not be repaired...
Click to expand...
Click to collapse
Try these files - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM

levone1 said:
Try these files - https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM
Click to expand...
Click to collapse
Already tried them. To no success.

goop.Q said:
Already tried them. To no success.
Click to expand...
Click to collapse
Strange - I guess you could try Emma or PC Companion repair.

levone1 said:
Strange - I guess you could try Emma or PC Companion repair.
Click to expand...
Click to collapse
Emma registration did not work. Never received an email.
PC Companion can't get a connection to the phone, when i'm being prompted to plug it in.
It seems the phone is in flashmode all the time. Whenever i plug it into the pc, the led flashes red and then green for a short moment.
I can unplug it and get into fastboot mode (re-plugging and pressing Vol+). The led stays blue, till i try a fastboot command. Then it turns off, like it's trying to boot up.

goop.Q said:
Emma registration did not work. Never received an email.
PC Companion can't get a connection to the phone, when i'm being prompted to plug it in.
It seems the phone is in flashmode all the time. Whenever i plug it into the pc, the led flashes red and then green for a short moment.
I can unplug it and get into fastboot mode (re-plugging and pressing Vol+). The led stays blue, till i try a fastboot command. Then it turns off, like it's trying to boot up.
Click to expand...
Click to collapse
No need to wait for registration for Emma. Look for info, (I can't remember exact), you just have to modify some file in the DL package. I'll see if I can find it. What happened originally, did it disconnect during flash or something?
---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------
goop.Q said:
Emma registration did not work. Never received an email.
PC Companion can't get a connection to the phone, when i'm being prompted to plug it in.
It seems the phone is in flashmode all the time. Whenever i plug it into the pc, the led flashes red and then green for a short moment.
I can unplug it and get into fastboot mode (re-plugging and pressing Vol+). The led stays blue, till i try a fastboot command. Then it turns off, like it's trying to boot up.
Click to expand...
Click to collapse
Here - https://talk.sonymobile.com/t5/Andr...ony-Flash-tool-for-Xperia-devices/td-p/307318
I would start with ta update, ( http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/ ), and try to get recovery from there. Make sure to flash recovery after update - the ta update only enables recovery, but doesn't include it.

goop.Q said:
fastboot boot boot.img
Click to expand...
Click to collapse
That command will only hotboot a kernel, the right one for it to stick is fastboot flash boot boot.img.

Using fastboot Flash a stock kernel with recovery>get into recovery>wipe data/factory reset>install any rom>your good to go
also the command to flash a boot.img is
HTML:
fastboot flash boot boot.img
All the best

Htc 10 EU version. *Unlocked* *S-ON* bricked?

Hi guys,
So i run into this problem this morning that my phone wont charge at all. Did a reboot and got stuck there somehow.
Some time ago i flashed TWRP recovery and Unlock the bootloader. Everything went ok, but had the red text under HTC logo every time i was booting up.
Now i can access the bootloader by pressing VolUp + VolDn + Power buttons but that's it.
If i try to Boot into Download Mode to use fastboot (as far as i know this way it can be used) it goes back to the boot-loop. Same happens with Boot to Recovery. Also ADB and Fastboot won't show it at all.
Even when i select Power Down it goes into boot-loop.
So far i've tried on a Linux machine without any luck. I'll try on a Windows but i suspect the same result.
Linux can't see it at all on the USB interface (only for a really short period of time when is looping, like half a second. not enough to adb or fastboot)
It got bricked? Just like that? Any way to flash anything on it? Like a recovery or the stock ROM.
Hope you can help me guys. Thanks

Update:
I've just installed on Windows the HTC 10 Drivers and ADB, Fastboot tools.
The device is shown in Device Manager as "My HTC 10" and its listed in "fastboot devices".
The Recovery is still unreachable and if I try to reflash the recovery i get this error message.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (53680 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.392s
I have to say that first time i did this it went smooth without errors and i was S-ON the entire time. Do you have any ideas? Please.

I believe you need to use htc_fastboot.exe rather than the stock fastboot.exe. Google is your friend for finding it, then do the exact same command but with htc_fastboot rather than fastboot.
so: htc_fastboot flash recovery twrp....

Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.

iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
You need to be in download mode

iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
Try fastboot oem reboot-download when in bootloader to see if it'll boot to download using fastboot commands.
Sent from my HTC U11 using XDA Labs

That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.

iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Hi, do you finded any solutions?

iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Try to search for the HTC Decrypt Tool here. You'll find the thread which will help to decrypt the RUU and receive the images needed to flash.
On thebother hand you got to be in download mode to flash them. If you're not able to reach it, I guess it's a case for a professional repair.
Sent from my HTC U11 using XDA Labs

LG G7 - Fastboot bootloop [SOLVED]

After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?

Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Try to get into lgup to flash a kdz, if you cant do that you might be SOL

LGUP does not detect phone, download mode is not working

hi
Prosjak said:
LGUP does not detect phone, download mode is not working
Click to expand...
Click to collapse
Please contact me, I can help you recover the device

PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
How to contact you and how you can help me.
If you want to help write this here to help this benefit to anyone who has this or similar problem
Thank you

Prosjak said:
After trying to flash Pie my G7 stuck in fastboot mode. Download mode is unavailable so I not can reset the stock ROM.
After it reboots it boots into only to fastboot mode and is stuck in a loop now.
An even bigger problem is that now the bootloader is locked and the unlock.bin file can not unlock the bootloader.
ADB mode is not working!
DOWNLOAD mode is not working!
SYSTEM mod does not work!
There is only FASTBOOT mode that is in the loop
Does anyone have any suggestions?
Click to expand...
Click to collapse
Fastboot --set-active=a

LameMonster82 said:
Fastboot --set-active=a
Click to expand...
Click to collapse
Thank you for your reply
The problem is that the bootloader is locked
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s

Problem solved
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day

What version of G7 use?
Sent from my LM-G710 using Tapatalk

PjLyTam said:
Please contact me, I can help you recover the device
Click to expand...
Click to collapse
i got this problem too.. please help with that

Prosjak said:
Octoplus/Octopus LG 2.9.3
Reset FRP Lock
1. Attach testpoint, and connect phone with Micro USB cable (don´t use USB hubs!).
2. Check PC Device Manager, a new device should appear "Qualcomm HS-USB QDLoader 9008" or "Unknown Device" if you hadn´t installed a driver.
3. Release testpoint and press "Reset FRP Lock" button.
Emergency mode
To enter emergency mode, disconnect cable, disconnect battery, press and hold "Vol+" button and connect USB cable.
My lucky day
Click to expand...
Click to collapse
how i can do this?

My G710EM has a problem with my lockback BL. I can't boot the system and it will prompt "Your device has failed a routine safety check and will not boot. This may be a temporary problem. If this message occurs repeatedly, visit this link on Another device and refer to the red case:g.co/ABH Your device will power off automatically after a while.” With LGup brush kdz brush does not go in, fastboot “fastboot flash unlock unlock.bin” prompt is invalid
* Target reported max download size of 536870912 bytes
Sending 'unlock' (1 KB)...
OKAY [ 0.004s]
Writing 'unlock'...
FAILED (remote: Flashing Unlock is not allowed
)
Finished. total time: 0.011s
I don't know what to do.

I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
At first, you'll need a working fastboot environment, you'll find out how to set it up on your own. Then you'll need the laf.img, I can upload mine if you want or I could help you extracting one out of a kdz file. Put the laf.img in the same folder like your fastboot.exe, then hold shift and right click, then click on "open command panel here" or however it's called in English. Type "fastboot flash laf laf.img" (Edit: It would probably better to use "fastboot boot laf.img" instead because of the bootloader lock). If that works, you at least have a working download mode.
Click to expand...
Click to collapse
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again

Garlikus said:
I had the very same problem as OP. I tried to install pie with LGUP (G710EM20b_00_OPEN_EU_OP_0508.kdz) but ended in fastboot loop.
After whole night of trying different things (being a noob means less sleep) I managed to run the phone in download mode. Starting from there I was able to install my previous rom. Both failed update and rescue operations were done on Win 10.
What I tried and didn't work:
- Fastboot --set-active=a
Code:
C:\ADB>Fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote: Slot Change is not allowed in Lock State)
finished. total time: 0.003s
- Unlocking with unlock.bin. Didn't save the msg but saw it somewhere in another thread. I needed to install/point drivers first because the device was not recognized in Win.
- Solutions for G6 for going into download mode. The download mode icon was displayed for a second and then going to fastboot again.
- LG Flash Tool 2014 - I just followed a guide for older phones but it didn't work. Didn't try again.
What did work:
1. I found this post on reddit (remove spaces or PM me, I'm not allowed to post links):
Code:
https:// www .reddit. com/r/LGG3/comments/2qe5sr/in_need_of_serious_help_stuck_in_fastbootno/cn5f2qr/?utm_source=share&utm_medium=web2x
Quoting the post
2. I used LG_Firmware_Extract_v1.2.6.1 and extracted dz file from aforementioned pie file. The I extracted two laf files for the kz file. In my case they were: laf.img_180534 and laf.img_81990.
3. I took one of these files (sry, don't remember which one, but they have the same size - didn't check if they're the same) renamed it to laf.img and put a folder where fastboot.exe is.
4. I did
Code:
fastboot boot laf.img
and voila: the phone was in download mode!
5. After that LGUP the previous rom and the phone is working again. Here I needed few tries. At first the were some problems, then I tried different combinations (1.14, 1.15, w/ and w/o uppercut). I think LGUP 1.15 (1.14 with patch) did the work. I was able to "refurbish" the phone.
Hope it's useful for others. If anyone could prepare a guide from this description or/and tell why it worked - please feel free to do so.
I think I will wait some time before trying pie again
Click to expand...
Click to collapse
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."

davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I recall I also had some error msg, it could've been the same. Now I don't remember what I exactly did next as most my actions were more or less random. Either I tried the same command but with other laf.img file (from the rom I used before), or I tried to restart the phone into download mode (vol- and power together and then vol+ after screen goes black) or tried the same file again.
Hope it helps.

davinik84 said:
Thanks for you guide.. I follow it but unfortunatly after "fastboot boot laf.img" I get this message from my LG:
"Your device has failed a routine safety check.... it will reboot after a while.."
Click to expand...
Click to collapse
I have the same problem as well. I follow the guide but I received the same error message

domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
Check if the phone is recognized in LG Bridge. If so, then choose update error recovery from software update tab. Again, I don't remember if it worked immediately or did I need to reinstall drivers and/or choose a proper driver in device manager (generic ADB vs LG...) and/or restart the phone.

domenico.dalpiaz said:
I have the same problem as well. I follow the guide but I received the same error message
Click to expand...
Click to collapse
I have same error too ...

DenisVelev said:
I have same error too ...
Click to expand...
Click to collapse
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
install the LG Bridge updater software on a computer, go to updates, click the "correct update errors" button. Then plug in your turned-off phone while holding down the volume up button. It should switch to download mode and reinstall all software from the PC. Yes, this will erase all data but it should unbrick your phone (unless the hardware's broken I guess)
Click to expand...
Click to collapse

Garlikus said:
Based on other threads, e.g. https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903 and https://www.reddit.com/r/lgg6/comments/axd17d/lg_g6_eu_glh870_bricked_after_update_your_device/
try:
Click to expand...
Click to collapse
Cannot put in download mode. Only Fastboot. For a secound show download mode after that show fastboot mode.

Bricked device, can't get into EDL mode

Good night.
I have been using for a few days the YAAP custom rom for android 11 on my 7T, and it's been great. But I wanted to root it for some customizations and tried to flash magisk through mauronofrio's unnoficial TWRP. After trying to flash through it, my phone bricked. I can't get into fastbootd mode and the
HTML:
fastboot getvar is-userspace
command outputs "no", so I couldn't re-flash YAAP normally. I tried using the MSM tool for the 7T but I was also not able to boot into EDL mode. When I try to boot into it through the vol up/down mode, it reboots into bootloader again, and the
HTML:
fastboot oem edl
command returns FAILED (remote: unknown command).
I can flash twrp, but when I try to flash the YAAP zip, it shows me an error.
It shows signs of life, as it gets caught into the OOS boot animation loop, so I know there is a way around it, but I am having trouble figuring out how.
Would anyone here know how to circulate this issue? Or has been through something like this?

Shiro744760 said:
Good night.
I have been using for a few days the YAAP custom rom for android 11 on my 7T, and it's been great. But I wanted to root it for some customizations and tried to flash magisk through mauronofrio's unnoficial TWRP. After trying to flash through it, my phone bricked. I can't get into fastbootd mode and the
HTML:
fastboot getvar is-userspace
command outputs "no", so I couldn't re-flash YAAP normally. I tried using the MSM tool for the 7T but I was also not able to boot into EDL mode. When I try to boot into it through the vol up/down mode, it reboots into bootloader again, and the
HTML:
fastboot oem edl
command returns FAILED (remote: unknown command).
I can flash twrp, but when I try to flash the YAAP zip, it shows me an error.
It shows signs of life, as it gets caught into the OOS boot animation loop, so I know there is a way around it, but I am having trouble figuring out how.
Would anyone here know how to circulate this issue? Or has been through something like this?
Click to expand...
Click to collapse
If you are getting as far as the boot logo then you might be able to format data and try it
can't you reboot to EDL from fastboot?
fastboot reboot EDL ?
You said you can't use the MSM tool. Have you tried the regular all-in-one tool here on the forum?
Try fastboot boot twrp.img, format data and reflash the custom rom?
I'm just throwing ideas out here they may not be the best lol

redemptionx11 said:
If you are getting as far as the boot logo then you might be able to format data and try it
can't you reboot to EDL from fastboot?
fastboot reboot EDL ?
Click to expand...
Click to collapse
Can't. I have tried it before. fastboot reboot edl says the command is unknown, and the existing command (fastboot reboot emergency) throws me back to the bootloader.
The logo got weird. It shows up for a second after turning on and then the bootloader shows up.
redemptionx11 said:
You said you can't use the MSM tool. Have you tried the regular all-in-one tool here on the forum?
Try fastboot boot twrp.img, format data and reflash the custom rom?
I'm just throwing ideas out here they may not be the best lol
Click to expand...
Click to collapse
I haven't tried the all-in-one tool yet, but I don't know which one is it yet lol.
As for twrp this is the log I get:
HTML:
PS D:\Documentos\ADB> fastboot boot .\recovery-oneplus7t-3.4.2-10.0-b26.img
downloading 'boot.img'...
OKAY [ 2.318s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.337s

I'm going to assume you did fastboot reboot fastboot before you tried yes?
I'd go try the all in one. There's a thread for it named "all in one" or something.
The tool might have an option to reboot to EDL I can't remember but I've fixed several soft bricks using it.

redemptionx11 said:
I'm going to assume you did fastboot reboot fastboot before you tried yes?
Click to expand...
Click to collapse
Yes I did. Powershell says it does not exist and list all other commands
redemptionx11 said:
I'd go try the all in one. There's a thread for it named "all in one" or something.
The tool might have an option to reboot to EDL I can't remember but I've fixed several soft bricks using it.
Click to expand...
Click to collapse
I will look into it

The all in one worked for getting into the EDL mode. And for the rest of the process, @SkippRunning really helped a lot. Kudos for him for helping out lost souls and bricked devices!

Shiro744760 said:
The all in one worked for getting into the EDL mode. And for the rest of the process, @SkippRunning really helped a lot. Kudos for him for helping out lost souls and bricked devices!
Click to expand...
Click to collapse
ayyy well done man. Good to see you got it going

maybe you can try changing the slot from a to b or opposite