Database Users

Error loki-fying the boot image

Hello,
I rooted my G2 D802, and installed CWM recovery (after trying to install TWRP, but failing).
Everything seemed to work, until I tried to flash some zip files through CWM.
I get an error, with every zip I tried to flash : "checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image."
Little precision : when trying to install TWRP, I had problems with the loki file in a "tmp" folder...
Shoud I try to find a boot image from the D802 on the web and restore it ?
Thanks.

Philz recovery.
Try out philz recovery. It has an auto-lokifying feature.
I'm using it on my d802 since i rooted an have'nt had any issues flashing.

Help needed - i9505g soft-brick/recovery boot-loop

This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!

Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.

[Q] D803 Help!

Hello XDA Developers,
I had a device that was rooted on stock rom and recovery. What happened was that an OTA was installed and it went to the "boot verify certification" screen. I had to install Ubuntu to get TWRP running again.
I'm able to boot into TWRP, and I tried installing different ROMs, using adb sideload, from Stock ROM, ParanoidAndroid, and Madri-ROM.
The first one was able to install, but when I reboot the phone, I get stuck on the LG logo. I wait for an hour and it still does not do anything.
So now I try the other two custom ROMs, and I get an error saying "E:Error executing updater binary in zip "... .zip".
Then it reads "Error flashing zip '... zip'.
My question is: What else can I do to get this phone working again? I would like stock ROM, and preferably stock recovery back (Recovery is secondary).
Thanks in advance,
DaAznMan
Note: When I use adb sideload, the .zip file that gets transferred becomes a file called 'sideload.zip'. Is that correct? If not, what do I need to do to fix it?

TWRP Recovery error when flashing zips fix

Hi guys, so I recently tried to install a ROM (Bliss) and well TWRP gave me an error saying 'error executing updater binary in zip'. I could not install any other ROM via recovery neither. Google was telling me that other people (on different phones) and they had reflashed their primary ROM and then flashed their new ROM straight after but I have no way to flash something via TWRP at all, so I thought there are two fixes: first, try and install stock ROM via Odin, or change my recovery. Luckily, I found CWM Recovery and my life was saved. Yep!

Unable to flash roms

When I try to flash CM13, twrp says ''Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160603-UNOFFICIAL-oneplus2.zip'''
Before that I had my phone encrypted and was unable to mount any partition in recovery, so I installing stock OOS over the fastboot. The install failed(bootloop), but I was able to flash TWRP the same way and recovered OOS. Now it gives the error above. Any thoughts?

Make sure you're using the right firmware with the different roms.
http://forum.xda-developers.com/oneplus-2/general/switch-firmware-twrp-t3371583

Update firmware and recovery
Sent from my ONE A2005 using Tapatalk