[G3 Q&A, Help & Troubleshooting] EdFor:
Hi everyone,

Being the more adventurous kind of person I am, and also rather sick of LG's android overlay, I decided to finally try rooting and installing a custom ROM, as my previous device was the Nexus 5, and I longed to return to the stock android world. It is a first for me to try this, so I read a few forum posts about it, and finally I rooted my G3 (D855 model), which went flawlessly. I then installed cyanogenmod 12 (I cannot remember which version, it was the most recent at the time) and I was finally satisfied by the software, which was as smooth as butter, unlike LGs skin. After a few months, I made the terrible mistake of installing one of the updates that where suggested, and then the problems began. While the phone was performing the update, it froze on the "optimizing apps" screen, and stayed so for several hours, until I decided to pull the plug on it, and it slowly died of a flat battery. I then tried to reboot the device, which stayed on the LG logo screen for a long time, until I again had to leave it to die. I then rebooted into TWRP recovery, which was the recovery I had installed and used to install CM12, and I tried to recover from the last backup I had performed a week prior about, and it failed with "error executing binary in script". After some googling, I found a forum where someone recommended to wipe the cache, data, system, and dalvik partitions. Having done this , the backup was successful and the phone was up again. A few days later I saw that CM13 with android M was released for the G3, and I decided to try it. I downloaded the rom, backed up my old version again and flashed it with TWRP. It worked, and the device booted into CM13, but I was greeted with a "process has crashed" message. I dismissed it, and the OS seemed to work, but then I realised it failed to recognize my SD card, and the phone internal memory (I own the 32GB model) was listed at a mighty 2gb. I decided to return to CM12 for the moment, so I rebooted into recovery, flashed the backup and got the same "error executing binary in script". I then wiped the cache, data, system, and dalvik partitions, and flashed my backup with no error. The phone reeboted, showed the LG screen, and then went black, then the LG screen, then black, etc... I quickly discovered this to be a boot loop. After some attempts to fix this, the phone booted to the LG screen, then the Cm logo pulsing, and then the "optimising apps". At the end of the process, the lock screen appeared, and after unlocking the device, I discovered it was back in CM13. This was suprising, and the errors I previously had were still here, so I returned to TWRP and tried to flash the original CM12 file I had, and this showed no error. After booting the device, CM13 greeted me again. I decided the device was seemingly possessed, and made the decision to unroot and reinstall into factory settings. But the first step of this process was out of reach, as the phone goes no further then the "download mode" screen with the small blue dots in the middle when I hold the volume down and plug it into the PC. After an hour on said screen, I pulled the plug and tried to reboot again. CM13 appeared once again, as if it was haunting my dreams, and I also found out that TWRP is no longer accessible, as the device stays on the blue loading screen of TWRP.

I have searched and not found anything saying how to get any further then this. I know that as I am not very experienced with this, it was rather foolish to act as I did, so spare me the lectures about that. But I didn't learn to ride a bike without falling off it, so it's kind of the same isn't it? Anyhow, is there someone out there who may assist me?

Many thanks to anyone who has any advice, I'm sick of my backup samsung S3 D:

Ed