Tying to install a rom. keep getting this error on cwm. Im stuck in Cwm recovery loop. LG G2 (D802). Installing from otg as pc will not find phone. using adb to push rom
"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. "
Keep it simple (Noob Friendly)
donation for fix
Thanks hope you can help
FIXED
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
hayjoesam said:
if anyone is stuck here is the ADB command that fixed my phone.
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
hope it helps
Click to expand...
Click to collapse
You know there's a LG G2 section right? And there's also an irc channel for these types of things.
Sent from an Xposed LG-G2/LS-980
Related
after downgrade to .15, root , instnall cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.It lets me backup from recovery but when i reboot again it takes me back to recovery.I am totally inexperienced in these things.If someone can make a small program for me to making my asus prime 201 to work again i donate to him $100.
chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
Uh oh lol, kinda sounds like boynamedstacy's issue. Maybe not though, you could try whatever methods he was unsuccessful with and hopefully you're not bricked.
chasosa said:
after downgrade to .15 root install cwm recovery and now my asus 201 stay on recovery and do not reboot.Please help.
Click to expand...
Click to collapse
first of all install the naked drivers and search for a workimg adb.
then connect your tablet with you pc and make sure your prime is in recovery.
open up your cmd (make sure you are on win7) and typ: adb shell
now: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 hit enter.
now typ: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 enter.
exit cmd and now reboot via cwm.
if it stuck on the eee pad screen, just typ in the adb: adb push romname \sdcard\ romname again.
now flash the rom and your done.
Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Scottymeuk said:
Hello,
Basically my prime was running fine, GooManager then told me to update gApps which i then did. And now my device will only boot into Recovery. It totally skips the bootloader screen, and even holding down just goes into recovery.
I did manage to fix it using the following command:
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
But then i accidentally flashed the gApps again (i know, I'm an idiot)
I could just run the command again and fix it, but adb will not run. Just keeps saying device not found. The drivers are installed, and it shows up in Device Manager fine.
Any ideas on what to do?
Click to expand...
Click to collapse
try to uninstall the drivers and install again
leime68 said:
try to uninstall the drivers and install again
Click to expand...
Click to collapse
Thanks for your reply.
I have done many times Doesnt seem to want to work at all. I dont know what to do
i instaled cwm 5.8.2.0
i dont have rom in memory of device & cant get ADB commands
it says no device found
how can i transfer rom file to the memory ? or get rid of the bootloop
i saw it can by adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
but i cant get ADB
If you accidentally take the OTA and have the bumped twrp installed you'll find yourself in a bootloop.... to fix it do this;
If you have ADB access (once booted into twrp), plug in your phone to your computer and do this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
If you DONT have ADB access for whatever reason or you do not have access to a computer or something you can use TWRP's "terminal command" option to do this:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type the above out with the onscreen keepboard so be very very careful to get all the spaces and /'s.... One wrong letter and you could blow up your phone.
After you can reboot and it should boot as normal.
I was using a guide, https://forum.xda-developers.com/android/help/guide-how-to-lg-d-631-att-fastboot-t3130955, in hopes to use a custom recovery to restore my phone, it didn't take. Which lead to this problem.
During the process, I used ADB and inputed this command:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
(I also ran this command to zero out the actual block partition)
dd if=/dev/zero of=/dev/block/mmcblk0p15
So I found this guide, after finding out that a tot file is the only way to restore.
https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
I did well until the final part of step, which requires the phone to be in download mode. I realize the problem is that the phone is in fast boot instead of download/driver mode, and I have no idea how to switch it back.
Also, The fastboot reboot command does nothing, and it flatout rejects the reboot into bootloader command.