Hello, and thank you for taking the time to read this thread!
There were a lot of things that I did to my phone that could be the cause of this problem, so I'll lay it all out chronologically:
I was running CM12 and discovered that the crDroid team developed a 6.0 ROM for the G2. I installed the CAF bootloader, ROM, and GApps zips. Everything went smoothly, but when I rebooted to recovery to install the zip for Xposed, I got a "secure boot error" at the LG screen. Granted, I could boot to system just fine, but not having recovery was kind of a dealbreaker; I love tweaking my phone so I use Xposed frequently. I didn't know what could have broken my recovery, so I just kind of gave up. I scrapped Marshmallow and decided I would go back to using CM12.
I then used the .tot method with LGFlashTool to get everything back to stock, and from there I rooted the phone and installed TWRP using loki. After that, I used TWRP to flash the LP bootloader, CM12, and GApps. But for some reason, when I tried installing GApps it gave me an error: "error executing updater binary in script". I didn't really know what to do so I downloaded AOSPA with the respective GApps and flashed both files successfully.
This is where I am now. After I rebooted to system, the message "Unfortunately, [everything] has stopped." flooded the screen and now I can't really do anything. Any help would be greatly appreciated.
XDA Visitor said:
Hello, and thank you for taking the time to read this thread!
There were a lot of things that I did to my phone that could be the cause of this problem, so I'll lay it all out chronologically:
I was running CM12 and discovered that the crDroid team developed a 6.0 ROM for the G2. I installed the CAF bootloader, ROM, and GApps zips. Everything went smoothly, but when I rebooted to recovery to install the zip for Xposed, I got a "secure boot error" at the LG screen. Granted, I could boot to system just fine, but not having recovery was kind of a dealbreaker; I love tweaking my phone so I use Xposed frequently. I didn't know what could have broken my recovery, so I just kind of gave up. I scrapped Marshmallow and decided I would go back to using CM12.
I then used the .tot method with LGFlashTool to get everything back to stock, and from there I rooted the phone and installed TWRP using loki. After that, I used TWRP to flash the LP bootloader, CM12, and GApps. But for some reason, when I tried installing GApps it gave me an error: "error executing updater binary in script". I didn't really know what to do so I downloaded AOSPA with the respective GApps and flashed both files successfully.
This is where I am now. After I rebooted to system, the message "Unfortunately, [everything] has stopped." flooded the screen and now I can't really do anything. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello,
it seems more like an incompatible gapps issue.
Further, you could make XDA account so we could assist you in moving this thread to LG G2 Q & A whereall the LG g2 experts could help you in fixing the issue.
-Vatsal
Related
Ok so thanks ahead of time for any help given, here is my story. I have a E980 with the latest AT&T 4.4.2 on it and should have done a little more reading before I installed a custom recovery. I used a one click rooting app for pc which worked great and root was achieved with no problems. Then not knowing about needing a lokified recovery for this I used FREEGEE and CM Rom Manager to attempt to install a custom recovery which both said they were successful and according to CM Rom manager i am running CM recovery 6.0.3.8. My phone still works fine but I can't factory restore or boot into recovery without getting the secure booting error Cause: boot certification verify. I have looked for the last two days on this form and others trying to find a way to get back into recovery. Everything I have read on this error ends up leading back to me using the recovery to flash another rom or another recovery which I can't do. From what I have read the people with this error normally can't do anything on there phones. I do have Android studio installed (although don't really know how to use it) on my PC in hopes that there is some way I can fix this. Please if anyone can lead me in the right direction so I can get back into a recovery and load the lokified one it would be greatly appreciated.
Thanks again for any help given!
Bump
I had stock 5.0 and installed MultiROM via fastboot. And after that I tested out xTraSmooth 3.1 on the secondary ROM so I pretty much liked it so I said **** it, why not make it the primary. So I formatted the device completely secondary and primary and all. And I copied the zip files and flashed them as primary. I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. Anyway, I wanted to test some more ROMs now, I ended up with a bootloop or updater binary error.
So, I said I'll test it on the same ROM I had tested before, which is now my primary one. So I flashed another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop. What should be done? Or is this some new problem with MultiROM?
Bump
SA3DX said:
... I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. ...
Click to expand...
Click to collapse
That sounds very strange to me! I'd try a fresh install using the MultiROM Manager Android App. Make sure that the status displayed in the app does NOT say Kernel: doesn't have kexec-hardboot patch! (see Installation section in the first post of the MultiROM thread).
... another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop.
Click to expand...
Click to collapse
Did you try the newest version of xTraSmooth (3.3)? I had a quite similar situation with AICP for Nexus 7. In fact, at first it never got past the boot animation and then "suddenly", with a newer version, things were fine.
You may also want to try installing another ROM as secondary, just to make sure your current MultiROM installation works as it should.
First, I have to apologize for being more or less a noob. I have been away from Android for a few years and just returned with a Galaxy S5. I used to flash ROMs all the time but it has been awhile and I have not had a Samsung before.
I was running stock Lollipop, then I rooted and installed phillZ CWM recovery. I then downloaded MOAR 6.2 and attempted to flash it from recovery, but keep getting errors, it says something about the signature and then it fails and reboots. I tried downloading it several times from both the main source and the mirror, and I did check the MD5. It is on the root of my SD card. So what am I doing wrong? Hopefully someone can help me get back into my Android ROM flashing!
Thank you in advance for your help.
I figured it out - I had flashed the CWM recovery but for some reason I still had the stock android recovery. It's all good now!
While I was attempting to flash CM 13.1 to the phone, it got stuck in a bootloop. Would not get past the white startup/splash screen. So, I booted it into TWRP and attempted to install the recovery I had made using TWRP. It ended up throwing me an error (I don't remember the code.) Anyways, I got the bright idea to completely wipe my phone and retry it. Now TWRP deleted my recovery, and my OS is gone. It was rooted and had SuperSU installed before it got bricked. Any help at all?
Regards,
Cheer
Hi Cheerfulfilms
Next time when you brick your phone, read this thread. I hope you'll be good now.
Cheers
bemolx said:
Hi Cheerfulfilms
Next time when you brick your phone, read this thread. I hope you'll be good now.
Cheers
Click to expand...
Click to collapse
The Xtreme System ZIP is no longer available.
*update*
I decided to try my own way and it worked very well. Using TWRP I was able to transfer a ROM onto a MicroSD, and then install that ROM from TWRP. It's a lot less complicated than the thread given. The Xtreme stock ROM is running very well though.
Hi all, I'm trying to get my TF101 up to speed so to speak. I had previously ( a year or 2 ago) installed TWRP and a Jelly Bean ROM, and decided to update to KatKiss. After some tribulation, I got TWRP updated so I could install the ROM, and I got KatKiss installed. However, I'm having issues flashing SuperSU. Whenever I install the ZIP via TWRP recovery, I get the following message:
Code:
- Placing files
********************
-Finding boot image
--- Boot image: not found, aborting
Then a warning telling me not to let TWRP install SuperSU if it asks (it doesn't) and TWRP tells me the install was Successful. But no SuperSU is installed when I boot into KatKiss. Any idea why this is happening?
Also, I flashed the Pico version of OpenGApps, and am constantly getting a message saying GooglePlay Services has stopped working. Any help on this would be appreciated to.
Thanks!
EDIT: In my frustrations, I thought maybe it would be best to go back to stock and start at square one. I used EasyFlasher to go back to the stock Asus ROM and unroot everything. I'll give installing KatKiss another go tomorrow. I guess mods can delete this thread.
mods, this thread can be locked/deleted.