Database Users

[Q] fastboot - no boot or img file

hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.

you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.

when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875

kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.

unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery

Fastboot mode - no boot or recovery img **help**

Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?

Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy

since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.

*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)

Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.

I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option

I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).

Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!

No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S

saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?

I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?

it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium

Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"

It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++

saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!

My LG LS980 device is now bricked

I need big help, my LG LS980 device is now bricked currently works only in recovery mode with ADB commands, any firmware I tried to upload I did not succeed
adb devices
List of devices attached
03xxxxxxxxxxxx07 sideload
adb sideload aokp_ls980_kitkat_unofficial_2014-01-16. zip
sending 100%
on my screen devices
finding update package
Opening update package
Verifying update package
Installing update
assert failed: run_program ("/system/bin/loki.sh") == 0
Installation aborted.
I've tried other firmware that is supposed to my device with similar result
You may need to restore to stock firmware but I can't figure out the process.
Is there anyone who can help me to restore the device

follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .

bachera said:
follow steps to reroot and push loki to device, reinstall recovery. try install again.
before redownload different rom and try to install that, aokp is buggy rom anyway, latest 16th build doesnt boot .
Click to expand...
Click to collapse
Thanks for your reply, my problem is that I don't understand how do reroot the device.
The device does not have many options, pressing the buttons (power and Vol +) the device enters in a State Factory Hard Reset.
Pressing (power and Vol-) goes into recovery mode and loads the black screen with anticipation for the adb commands
reboot system now
update from external apply sdcard
apply update from cache
apply update from ADB
wipe data/factory reset
wipe cache partition
With closed then press the device (Vol +) and connect the USB cable enters into Download Mode, here you also don't know what to do.
When I hit the power button just opens the device showing the logo of LG and the led flashing in green/blue and after a while makes itself restarted
I searched the forum for reroot and saw that need to do some settings on the device to do root, did I forget something and so I do not understand?
Sorry, I don't understand and become tedious but it's my first time playing with the object

so, you dont have recovery now?
"adb reboot recovery" not working ?

Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.

I'm happy because I just unbrick my device by selecting Download Mode Firmware Update and with the LGFlashTools loaded LS980ZV8_ software 13.51097. tot.
Now I lie in my original problem, I want to unlock to accept SIM card from another provider and another country.
Some help to be able to start from somewhere the unlock process?

id3210 said:
so, you dont have recovery now?
"adb reboot recovery" not working ?
Click to expand...
Click to collapse
Who not any command except devices-sideload-kill server-start server-reboot
any other command, I was giving "error close"
votinh said:
Based on what you said, you are able to get in recovery and adb is working, then push the ROM zip file over and reflash it in recovery.
Click to expand...
Click to collapse
to command push, I was giving "error close"
But all ok, unbrick my devices with LGFlashTools

Great!
Good to hear that.

I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?

antbox12 said:
I need help as well. My phone ls980 is bricked only works in recovery TWRP. Can someone please help me?
Click to expand...
Click to collapse
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk

natefuhr said:
Did you accidentally accept that update too?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
No but I fixed it. I had to put it in download mode and flash the stock rom back to it.

[Q] Hardbricked LG g2

Hi guys.
I did something really stupid with my brand new lg g2. Wanted a custom rom, so flashed twrp recovery.
Then i wanted to flash the downloaded custom rom, but i somehow deleted everything on the phone.
Then i connected my device to the pc, and tried to sideload the rom. That didn't go well, so now i can't enter recovery or anything.
The phone only shows the LG logo or bootlooping.
Is there any hope?
(I tried to send in my phone during warranty, but they said i needed a new mainboard - which is very costly)

You don't sideload a ROM, you instead push it to internal storage via ADB so it can be installed via recovery (TWRP, PhilZ CWM, etc.). So this would be the command from a command prompt, run from the AndroidSDK\Tools directory or from the directory containing the ADB executable...
adb push ROM.zip /sdcard/ROM.zip
... replacing ROM with the EXACT name of the ROM file. If besides not being able to access recovery using this method...
alone-together said:
Hold the power button until the phone turns completely off, then turn on the phone while holding the power and volume down buttons. When the LG logo pops up, let go and re-press those buttons. When prompted for a factory reset, press the power button
Click to expand...
Click to collapse
... you can't access download mode to restore using either the *.tot or *.kdz method, then this may be your only alternative:
http://forum.xda-developers.com/showthread.php?t=2582142

redduc900 said:
You don't sideload a ROM, you instead push it to internal storage via ADB so it can be installed via recovery (TWRP, PhilZ CWM, etc.). So this would be the command from a command prompt, run from the AndroidSDK\Tools directory or from the directory containing the ADB executable...
adb push ROM.zip /sdcard/ROM.zip
... replacing ROM with the EXACT name of the ROM file. If besides not being able to access recovery using this method...
... you can't access download mode to restore using either the *.tot or *.kdz method, then this may be your only alternative:
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Thank you very much. I was able to reach twrp again, pretty easy. I pushed a custom rom to my device, but even though the rom is installed OK, i wasn't supposed to make my device boot into the rom. The device only boots to twrp. I Installed several roms to see, if this was because of a bad flash, but that wasnt the answer. I wiped everything, and reached the aroma installer for cloudyfas rom. Installed without problems, but when rebooting, it still only boots up TWRP. Can't do anything to reach the rom (s). Any suggestions?

You may need to flash the KitKat baseband. The link is in the OP of the CloudyG3 thread.

redduc900 said:
You may need to flash the KitKat baseband. The link is in the OP of the CloudyG3 thread.
Click to expand...
Click to collapse
Thanks for answer. I did flash the baseband first.
And Tried several roms. Now Im back to stock and Wonder If i really should try again. On my first lgg2, screen Damage appeared When i was flashing a custom rom. I just don't understand Why i Couldnt load the rom after i flashed in twrp.

[GUIDE] How to root, install TWRP, ROMs and mods on a G3s/G3 beat d722 in 2020?

*After I wrote this whole thing as a DM i figured it might be helpful for a couple of people that are struggeling to root and install a custom recovery on their d722.*
Before we start you will need a PC with internet connection and a USB cable.
If you get stuck or need something about the device you can find it here. It's an XDA thread about the d722, it's mods, roms... : https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
First you will need to flash your phone back to 4.4 kitkat firmware to ensure maximum compatibility (this is the only way my device would root) ( find it here: https://lg-firmwares.com/ (type in your model and download a 4.4 firmware closet to your region, language...)). We will do that with the lg flash tool (find it here: https://lgflash.com/download/) + also install lg drivers if you don't have them already (https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560).
1. First enable developer options in phone settings by tapping the build number 7 times. Go to the developer options and there tick usb debugging. Than you want to turn you device off. Hold volume up and plug it into you computer. You will get into download mode. On your PC extract and open the lg flash tool. There you will chose your kdz firmware file you downloaded previously and click normal fash. Choose other instead of korean and your preferred language. When you flash it the tool might report an error but just ignore it and wait for the phone to reach 100% download. It will reboot itself when finished. After that you can close the flash tool and continue to the next step.
2. Now you will root your phone. You will do that with lg one click root (found here: https://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951). Download the latest GUI version, install it onto your PC and open it. When your redy plug your phone into the computer (turned on no apps open) and click start. Wait for it to be done. It's normal for it to restart a few times.
3. Now we will instal the custom recovery to be able to flash ROMs. To do that you will need to dowbload this zip file from here and extract it with 7zip (https://forum.xda-developers.com/showpost.php?p=61220755&postcount=100) and install ADB (remeber install folder) (from here: https://forum.xda-developers.com/showthread.php?t=2588979). Paste aboot file into /sdcard folder (or folder of choice with adjusted path in command) ob your phone uding file manager. Than open CMD and type in
cd *path of your folder*
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you get an error that says there is no aboot file or something similar than you nees to change this command : dd if= *your phones path*/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot For me it was : dd if=/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4. This should have installed a basic version of TWRP on your phone ane booted into twrp recovery but we will be updating it.
To get into recovery from off state hold volume down + power button until you see the LG logo. Relese both for a split second and hold both down again (volume down + power) until you see an option to factory reset (wont actualy reset anything if you did all steps correctly). Click yes and yes again by using volume and power buttons and you will be booted to TWRP.
Alternative is to go to playstore and download root app that boots you to recovery if you do it often.
This version is quite old and not capable of flashing newer ROMs so we will be flashing an updated version (download it here: https://vasy.ru/TWRP/jagnm/ and rename it to .img if it isnt named like that alredy). Easiest way is to download it to your PC and transfer it via USB if your PC detects the phone while in TWRP. If not boot it up transfer the files and boot back to recovery. Now just flash the .img file and reboot.
5. At this point you have root privilages (super SU) and a custom recovery. Now all theres left to do is to flash ROMs and mods.
You boot to TWRP recovery, connect your phone to the PC and transfer the .zip files you want to flash. Tha you click flash in twrp chose your ROM files and click add more, your GAPPS click add more and the mod (if you want to try it of course). Than you flash them, wair for it to finish and click reboot.
If it takes longer than 15 min+ than you probaboy have a bootloop. To fix it take out the battery put it back in and boot into recovery (volume down + power until LG logo pops up, release for half a second hold again, yes and yes). Try factory reseting (type yes). And than just flash the ROM and boot. If it boots go back to recovery and flash GAPPS and mod and it should normaly boot into android.
If nothing fixes your issue you can alway use the firmware and lgflashtool to go back to default unrooted kitkat or lolipop.
My recomendations:
I personaly use this liniage (14.1) 7.1 ROM as it's still getting updates (I also tried 8.1 but it's buggy, laggy and gapps don't work):
https://forum.xda-developers.com/lg-g3/development/cyanogenmod-14-1-lg-g3s-t3508224
And of course you want google apps to go along with it:
https://opengapps.org/ (pick ARM, android version of ROM (7.1 in this case) and how many preinstalled apps (I use nano))
I also have this mod installed which makes colours of your display a bit better:
http://www.mediafire.com/download/6z9yg1d3gooyz37/Sony_Bravia_3.zip
From here you can also get Exposed framework, root apps like LSpeed to speed up your phone even more, greenfy and amplify to improve battery life. Again every mod for this phone along with overclocking and other mods is or was discussed here at one point so dont be afraid to join the conversation in this thread:
https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
And ofcourse google is your friend if you get into any issues. Hope this helps, typed it on my G3s .

Thanks
---------- Post added at 12:28 PM ---------- Previous post was at 11:44 AM ----------
It would be better for our phone to release an android 9 custom, it would be great. Here is the same phone as our processor and video accelerator. Android 9 would work great on our phone https://4pda.ru/forum/index.php?showtopic=633150&view=findpost&p=36961339

Thanks for the guide!
I bought a G3s D722 cheap off ebay to experiment with. I tried to flash four different kitkat roms many times on 2 computers and each time the phone went into boot loop (start tune and logo over and over) so I flashed the first UK Lollipop on the list and all went fine, there are not UK kitkat roms in the link.
The UK kitkat roms must be different is all I can determine anyone know where I can get one?
The preflash OS was V20e-EUR-XX and now its V20d
Any thoughts or suggestions anyone?
Thanks!

I couldn't get this to work so tried the very easy no PC method in the link and it works great!
LG G3/G3s/G3 Beat telekom,orange or any other operator
Hi everyone, I want to show u how to upgade your LG G3s/beat to adroid 7.1.1 lineage OS. It has taken me some time to find and to gather all needed files but i was succesfull :D So I had my lg running on android 5.1 Lollipop but I had problem...
forum.xda-developers.com