Develop Bugs

D855 Stuck at Boot Screen

So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.

First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...

bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.

In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)

bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.

it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor

bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?

check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)

bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.

Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.

HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)

bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.

HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it

Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.

Tied everything to root swift, cant get past initial fastboot stage

hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!

yodjone1 said:
hi all, sorry if this has beeen posted before but its bugging me as i spent literally 4-5 hours lastnight trying to sort it, i havee rooted 4-5 android phones in the past but im just having no luck with this one
i installed adb / fastboot minimal, enabled what needed to be enabled in developer options on the swift, booted the swift into fastboot mode, then when i run adb on my computer, the first command works 'fastboot oem unlock' but after that its constantly saying 'waiting for devices' whenever i try the next phase of commands ie. fastboot -i 0x2970 oem unlock-go etc it just wont detect the device at all in windows on adb, is there any suggestions anyone could throw out there before i end up sending it back and getting an alternative android phone thats easier to root? the only thing i can think off is its a usb driver issue? but i installed the gloogle usb drivers and it picks up the phone for file transfer etc so im not sure if this is the issue. many thanks!
Click to expand...
Click to collapse
Hi,
I had the same issue. When that happens, do commands without the -i 0x2970 bit. So for example:
fastboot -i 0x2970 erase recovery
becomes:
fastboot erase recovery
Hope this helps
-Jev

I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'

yodjone1 said:
I tried this but it still says 'waiting for any device' My initial command worked for fastboot oem unlock, but then I just couldnt do the following commands, and as a result whenever i tried to install a custom recovery / rom it gave me the error along the lines of 'unable to verify....'
edit: when i missed out the -i part, then said its already unlocked. however i still am not able to install supersu or the recovery as it still gives me the error 'signature verification failed'
Click to expand...
Click to collapse
Hi,
OK, what recovery are you trying to install? I would recommend TWRP 3.0.2 by Beroid (in the development section) because it's easy to use and it works. Get the image and put it in your adb folder is. Make sure you are in fastboot. Then run commands
- fastboot erase recovery
- fastboot flash recovery (name of file).img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation.
You should now be in the recovery. You can flash custom roms and supersu within this new recovery.
Hope this helps
-Jev

Trouble installing Magisk

Any help would be appreciated. This is my first time dealing with Magisk, I've always used SuperSU in the past. I finally used my unlock code and the bootloader says unlocked, that was easy. I installed the Magisk Manager apk but am having trouble with Magisk itself. I'm used to flashing in TWRP, which I apparently can't install until Magisk is installed. I have two options, install - download zip only, and patch boot image file...
So I was trying to use the boot image file from this thread https://forum.xda-developers.com/mate-20-x/development/guide-mate-20-x-root-t3883269 and either patch it or used the patched one, but when my phone goes into the bootloader screen, adb is not recognizing the phone or finding the file which I set inside the adb folder itself. Sorry, I am not a noob to flashing. Done many many phones rooting, unlocking, roms, modems, etc. I am just new to adb and Magisk. Any help would be great as I've been at this all day reading and downloading things I needed. Thank you.
EDIT: I'm not sure if I'm putting the .img file in the wrong folder??? I am stuck on step 5 in that thread.

So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory

DavidMT909 said:
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
Click to expand...
Click to collapse
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'

lightning413 said:
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
Click to expand...
Click to collapse
Thank you, but I may have messed up my phone now. I was trying this from the thread above, and even his example shows Magisk in it.
Step 5:
-Once the device is in bootloader and connected to the PC, run the command "fastboot flash recovery_ramdisk recovery_ramdiskMagiskVARIANT" with VARIANT being whatever ramdisk you downloaded. For example with AL00 you would input "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00.img"
As soon as I tried your way it seemed to work... except when I booted it still did not have root. And now I cannot get into fastboot or recovery. It just keeps rebooting to the phone if I try recovery or fastboot. I used to be able to do this stuff following directions. It just doesn't seem to be working out. Thanks for trying.
My devices still lists in adb, but not fastboot. I'm still working on this. I do make an effort to do things myself.
Okay, I don't know what happened. My Magisk had an update, I installed it and rebooted and for the first time two green checks in Magisk, ran root checker and I have root. So hopefully I can install TWRP now and on to the ROM. Slow progress...
I have TWRP. Time to make a backup, and I'll install a ROM next.

Fastboot loop after installing TWRP and doing "format data"

Hello everyone!
So I got my new Mi9SE, and ready to install crDroid custom rom I followed this steps:
Unlocked the bootloader, flashed TWRP via fastboot mode, boot into TWRP, and then wiped cache, system, data. After data I did a factory reset. When I try to reboot to TWRP again I've got this "no OS installed are you sure you wish to reboot..:" message. I press yes and then it didn't reboot to TWRP, but to fastboot mode...and I can't get out from here. The only thing I can do is flashing Stock Rom from Miflash and start again.
I've read to get out of this loop I have to to disable dm-verity through"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" comand, but when I do this "fastboot: unknown option -- disable-verity" error message appears, eventhough I have the last ADB and Fastboot installed (1.4.3).
What am I doing wrong?

In my case, rom was actually installed, despite the no OS message.
Try with another TWRP and wait a few minutes after reboot.

@Musclepanx: use Red's TWRP only. The unknown option of fastboot command is caused by a wrong blank after --

rp158 said:
@Musclepanx: use Red's TWRP only. The unknown option of fastboot command is caused by a wrong blank after --
Click to expand...
Click to collapse
What's that recovery??I can't find it on the forum. I'm using this one https://forum.xda-developers.com/mi-9-se/development/twrp-3-3-1-3-mi9se-t3949328
I checked and there's no blank space after any of the -- but still getting the "unknown option" message.

@Musclepanx: your linked recovery is Red's. If fastboot command is typed correctly, you may need an updated adb-package.

rp158 said:
@Musclepanx: your linked recovery is Red's. If fastboot command is typed correctly, you may need an updated adb-package.
Click to expand...
Click to collapse
I have the 1.4.3. version, downloaded from https://androidmtk.com/download-minimal-adb-and-fastboot-tool. Is there any other updated package?

Question FAILED (remote: 'Unrecognized command boot')

Hello all together,
I recently have the problem that the fastboot boot "img" command gives me the error: FAILED (remote: 'Unrecognized command boot').
I had updated to Magisk 26.0 last week and later to 26.1. Unfortunately, Comdirect with Magisk 26 recognizes the root and refuses the service. So I wanted to downgrade again to Magisk 25.2.
I downloaded the patched 25.2boot.img from here https://forum.xda-developers.com/t/...oos-13-f21-f75.4252373/page-109#post-88329359.
The 9Pro is recognized in Windows 11. ADB devices command recognizes it as well. Also the command fastboot devices is executed and shows the 9Pro as detected.
If I now try to boot the boot.img it is successfully copied but aborted with the error "FAILED (remote: 'Unrecognized command boot')".
The same happens via Live LinuxMint and via rootTerminal.
Boot.img is successfully copied but aborted with the same error.
This is really strange because 3 weeks ago I switched to A13 and successfully patched the Boot.img.
Also I had not installed/uninstalled or changed any programs, drivers or anything else on my pc in that time.
I have also tried all USB ports and different cables, all without success.

Use the cmd not the power shell and open the cmd from adb platfrom tools folder
Dan3ll1 said:
Hello all together,
I recently have the problem that the fastboot boot "img" command gives me the error: FAILED (remote: 'Unrecognized command boot').
I had updated to Magisk 26.0 last week and later to 26.1. Unfortunately, Comdirect with Magisk 26 recognizes the root and refuses the service. So I wanted to downgrade again to Magisk 25.2.
I downloaded the patched 25.2boot.img from here https://forum.xda-developers.com/t/...oos-13-f21-f75.4252373/page-109#post-88329359.
The 9Pro is recognized in Windows 11. ADB devices command recognizes it as well. Also the command fastboot devices is executed and shows the 9Pro as detected.
If I now try to boot the boot.img it is successfully copied but aborted with the error "FAILED (remote: 'Unrecognized command boot')".
The same happens via Live LinuxMint and via rootTerminal.
Boot.img is successfully copied but aborted with the same error.
This is really strange because 3 weeks ago I switched to A13 and successfully patched the Boot.img.
Also I had not installed/uninstalled or changed any programs, drivers or anything else on my pc in that time.
I have also tried all USB ports and different cables, all without success.
Click to expand...
Click to collapse

ChrisFeiveel84 said:
Use the cmd not the power shell and open the cmd from adb platfrom tools folder
Click to expand...
Click to collapse
Same result.

Dan3ll1 said:
Same result.
Click to expand...
Click to collapse
You use the last platfrom tools.v34?

Yes, everything is up to date. I just cant figure out why all of a sudden it stopped working...

What for fastboot driver Have you installed ?

I use the minimal adb and fastboot drivers from here (XDA).

Dan3ll1 said:
I use the minimal adb and fastboot drivers from here (XDA).
Click to expand...
Click to collapse
Minimal adb is to old

Then what is the way to go?

Dan3ll1 said:
Then what is the way to go?
Click to expand...
Click to collapse
Update the android platfrom tools

Like i said. They are the newest i use.
From here https://developer.android.com/tools/releases/platform-tools

Using the latest OnePlus USB drivers with " disable signed drivers" for windows? And I would change the 25.2boot.img to just boot.img. the extra period may be causing an issue...just my thoughts.

If you want change kernel you have to flash it via "fastboot flash boot magisk.img". You cannot directly boot other kernel with "fastboot boot magisk.img". This command is used for booting recovery without flashing it.

I dont want to flash a kernel. I want to boot temp root with the patched magisk image and then flash it via magisk.

Bugscze said:
If you want change kernel you have to flash it via "fastboot flash boot magisk.img". You cannot directly boot other kernel with "fastboot boot magisk.img". This command is used for booting recovery without flashing it.
Click to expand...
Click to collapse
And you can boot other kernel with fastboot boot (when the Other kernel is a full img)

When this is your boot.img than you can it flash direct no need boot this image
Dan3ll1 said:
I dont want to flash a kernel. I want to boot temp root with the patched magisk image and then flash it via magisk.
Click to expand...
Click to collapse

I mean i could. But like all the tutorials and how to guides say that booting temp root and flashing it with magisk is the safest way.
And it did it this way like a million times before. And now i get this strange error that i dont understand why it is happening.
Edit:
The fastboot flash command works just perfectly fine. But not the fastboot boot command?