LG G2 F320 with Marshmallow need Custom Recovery!!! - Android Q&A, Help & Troubleshooting

Hello Everyone!
I am correctly using LG G2 F320 that run on Marshmallow 6.0.1 (cm13) and after install this ROM I lost my recovery. Is this a normal thing that happen after install new ROM or what? And now I want to get back my recovery( last Time I use TWRP recovery that I use Autorec KK to install it). But anyway, for now when I try to install it again using Flashify and....another.....I don't know what happen there is no recovery mode or anything. It shows me a black screen. But I know how to return to normal. And now What I want is.....I need you guy to make autorec mm for lg g2 f320. I don't know how to install custom recovery. Please help!!!!!

Doesn't sound like you followed the correct way to update your device as you need to have the correct bootstack installed. You should be able to find info on it here:
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Installation guide for CM13 based roms:
-Flash Bootstacks According to your variants from HERE (click the link above)
- Download the latest build
- Download Gapps
- Take a nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using latest TWRP recovery
- Flash Gapps
- Reboot.
- First boot will take a while...be patient, it will boot
You might have to flash the original LG OS and start over to make sure everything is set up correctly.

Related

HELP!! No system partition... need full rom

So I decided to unlock the bootloader and flash TWRP, i knew that unlocking it would wipe the data but what happened to me was that after trying to reboot into the system and install SuperSU it would always return to recovery and now it says no OS detected. So now i have to flash a completely stock image and i dont have one. Can anyone help???
EDIT: Used the restore tool(cant remember who by) and it worked fine.
Official twrp does not support squashfs which the new system is in, here is an unofficial build from the twrp forum on the lg g watch
http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
follow my guide here for rooting on android wear 6.0: http://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097

Latest Cyanogenmod doesn't work.

Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !

Update SW with TWRP installed

I have a unlocked and rooted LG G5 (H850 EU variant) with TWRP installed. As I already read in other threads, I can not install with OTA anymore.
I want NFC and glance screen to work so I suppose I need to stick with the stock ROM. Also since I use Xposed, I don't want to update to Nougat for now. Is there any flashable ZIP that I can flash from TWRP with latest Marshmallow ROM? Is this the preferred way or should I rather use LGUp? What do I need to choose not to do a factory reset?
I highly recommend you to update to Nougat, as it is very stable and fluid (from my experience).
Here's the flashable zip for Android Marshmallow: (P.S. not sure if this is the latest version)
https://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
Here's the flashable zip for Nougat:
https://forum.xda-developers.com/lg-g5/development/stock-h850-20a-eu-rom-flashable-zips-t3506514
USE THEM ON YOUR OWN RISK.
You shouldn't worry about about not using LG UP,
As the zip files contains everything necessary for the update process including: modem, bootloader, etc. (Except the recovery partition, to keep TWRP in tact)
I've updated yesterday to nougat though TWRP, and all was perfect, I didn't do even a factory reset, and preserved root and data partition unencrypted (flashing an extra .zip), so I too advise you to make the upgrade.
pd.: Not OTA nor LGUP worked for me

If you're stuck/bricked/bootloop while going back from a Custom ROM to Indian Stock

See guys, we do not have an option to install stock C675 if everything is wiped. ( I mean to say something equivalent to EFS partition where imei resides ). Then what best can be done here is get your device working in Lineage and try some apn creation fixes which I'll post below for Volte. If it works, well and good. If it does not, we need to wait and swap sims till we get the official stock system.img and boot as well as recovery ramdisk out from a dev or Honor's side. They do not have it in their database and so its difficult for them too to install it from scratch as they need every rom partition and in the treble devices, its a different way than samsung's odin or Mi's flashtool.
Now follow the exact steps below which I did and got a working device :
Things to download :
Berkley TWRP Official, Lineage OS - [ 1. system.img from Garbage folder. (Latest) , 2. ROM zip to update the ROM to latest from TWRP later.] , Stock Recovery from XDA, Luk's Gapps.
1. Install Berkley Official TWRP latest one from XDA thread (with NO mod) through fastboot.
2. Always use the button combination (power+vol up) to boot to twrp as soon as it gets flashed and you remove the wire.
3. Once it boots, wipe data, system,cache. After that, go to "Format data" option in TWRP and format it. (Its different than wipe)
4. Restart in TWRP.
5. Go to fastboot mode from TWRP and flash stock recovery through fastboot by using ramdisk command.
6. Flash system.img which you downloaded through fastboot and then as soon as it gets installed, do not boot it and instead go to stock recovery from button combination and click on factory data reset. Once done, let your phone boot.
7. Once you boot, setup your phone and flash TWRP Image through fastboot again. (Do not wipe anything on that.)
8. Once flashed just boot to TWRP and flash Lineage 15.1 "zip" as well as gapps through ADB sideload or USB drive. Do it one by one, first OS zip and then reboot to TWRP and do the same process for Gapps zip. Just make sure, you do not wipe anywhere after step - 4.
9. If you follow the exact process, you get a working ROM.
Credits : I would like to thank Luke for Lineage 15.1 . If we are midway, we have no other option to go back to C675 and this is the only option mentioned above to get a Bug free device other than Volte and camera. For camera, there are stock ones available for Magisk.

No access to stock roms

I am still not able to install latest lineage without bootloop see here:
see older xda thread
so this weekend I thought well give it a last try before selling my unlocked H850 on ebay. I want to flash it back on stock rom and do the whole process again - maybe flashing this time a different custom rom(15.1 unofficial).
The problem is it seems stock rom is no longer available.
See here
LG-H85010E-Flashable.COMPLETE.zip -> download speed is very slow and I wasn't able to finish download successfully (always connection errors )
H85010e_00_OPEN_EU_OP_0817.kdz -> get no access to this file (has LG stopped service?)
can be closed solution was first flashing Android 8 stock rom with uppercut (H85030f_00_OPEN_EU_OP_1122.kdz) than flashing custom rom based on Android 9 (lineage-16.0-20200811-X86CPU-h850 - thank you to the author) and than I was able to flash official lineage 17.1 than bootloop was suddenly fixed. Each time after flashing I just did normal wipe (confirming with yes).
official tutorial completly sucks:
https://wiki.lineageos.org/devices/h850/install
-> sideload is not necessary and when you come from older Android Version you have to flash Lineage 16 before (no evidence and no image in download section).

Categories

Resources