[Q] Loki flash?? - G2 Q&A, Help & Troubleshooting

ok here's the lowdown.
Verizon lg g2
rooted = yes
downloaded or a update in December = yes
installed twrp using the freegee app in the app market. not sure if their method implies the Loki boot loader bypass.
my question is is their a way to imply Loki bypass no. twrp does work but I can't successfully flash any roms and I believe it's the lack of Loki being implemented.

Here's loki patched twrp and loki patched boot
extract and flash

datechnerd said:
Here's loki patched twrp and loki patched boot
extract and flash
Click to expand...
Click to collapse
Still kinda new to the whole flash game.. I'm using flashify and it has three flash options
boot image
recovery image
and zip file..
which option do I use to flash.
sorry if the question seems obscene.

joewaz said:
Still kinda new to the whole flash game.. I'm using flashify and it has three flash options
boot image
recovery image
and zip file..
which option do I use to flash.
sorry if the question seems obscene.
Click to expand...
Click to collapse
Those are great questions..
I am having a issue close to yours..
I am going to use the boot as boot and the recovery as recovery.
These phone are quite a bit different than htc

http://forum.xda-developers.com/showthread.php?t=2449670 here's a guide
example for twrp
[email protected]:~$ adb push twrp.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
example for boot
[email protected]:~$ adb push boot.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!

datechnerd said:
http://forum.xda-developers.com/showthread.php?t=2449670 here's a guide
example for twrp
[email protected]:~$ adb push twrp.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
example for boot
[email protected]:~$ adb push boot.lok /data/local/tmp
[email protected]:~$ adb push loki_flash /data/local/tmp
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # /data/local/tmp/loki_flash
Usage: /data/local/tmp/loki_flash [boot|recovery] [in.lok]
[email protected]:/ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
[+] Loki validation passed, flashing image.
2253+1 records in
2253+1 records out
9230848 bytes transferred in 0.656 secs (14071414 bytes/sec)
[+] Loki flashing complete!
Click to expand...
Click to collapse
is this something you have to use adb or can you use flashify

joewaz said:
is this something you have to use adb or can you use flashify
Click to expand...
Click to collapse
Looks like adb to me.

i read a post were someone said you could change .lok to ,img and use flashify, you could give it a shot, they said it the same thing

I am getting errors
C:\max\loki-master>adb devices
List of devices attached
LG-LS980-03a89c4cdf4ce82c device
C:\max\loki-master>adb push loki_flash /data/local/tmp/loki_flash
cannot stat 'loki_flash': No such file or directory
C:\max\loki-master>adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/
openrecovery-twrp-2.6.3.2
cannot stat 'openrecovery-twrp-2.6.3.2-g2vzw.img': No such file or directory
C:\max\loki-master>adb push loki_flash /data/local/tmp
797 KB/s (3271 bytes in 0.004s)
C:\max\loki-master>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /data/local/tmp/loki_flash
/data/local/tmp/loki_flash
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
126|[email protected]:/ $ su
su
# /data/local/tmp/loki_flash
# /data/local/tmp/loki_flash
1|[email protected]:/ $ # /data/local/tmp/loki_flash
1|[email protected]:/ $ /data/local/tmp/loki_flash [boot|recovery] [in.lok]
/data/local/tmp/loki_flash [boot|recovery] [in.lok]
/system/bin/sh: recovery]: not found
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
127|[email protected]:/ $ # /data/local/tmp/loki_flash recovery /data/local/tmp/twrp
.lok
recovery /data/local/tmp/twrp.lok <
127|[email protected]:/ $ adb push boot.lok /data/local/tmp
adb push boot.lok /data/local/tmp
error: device not found
1|[email protected]:/ $ exit
exit
C:\max\loki-master>adb push boot.lok /data/local/tmp
4553 KB/s (9848832 bytes in 2.112s)
C:\max\loki-master>adb push loki_flash /data/local/tmp
1595 KB/s (3271 bytes in 0.002s)
C:\max\loki-master>adb shell
[email protected]:/ $ su
su
# /data/local/tmp/loki_flash
# /data/local/tmp/loki_flash
1|[email protected]:/ $ # /data/local/tmp/loki_flash
1|[email protected]:/ $ /data/local/tmp/loki_flash [boot|recovery] [in.lok]
/data/local/tmp/loki_flash [boot|recovery] [in.lok]
/system/bin/sh: recovery]: not found
/system/bin/sh: /data/local/tmp/loki_flash: can't execute: Permission denied
127|[email protected]:/ $ # /data/local/tmp/loki_flash boot /data/local/tmp/boot.lok
boot /data/local/tmp/boot.lok <
127|[email protected]:/ $

Try renaming boot.lok to boot.img and twrp.lok to twrp.img and using flashify. If you still can't get it to work let me know

12B?
If yes, you're out of luck.
If no, what datechnerd said.

Steamer86 said:
12B?
If yes, you're out of luck.
If no, what datechnerd said.
Click to expand...
Click to collapse
I patched twrp for 12b I also patched cwm for 12b

@datechnerd I just saw that. Nice. I used the flashify method for CWM ( loki version) on 11A, loki errors. Never got around to pushing loki. Is your CWM pre loki and flashable after extraction? Thinking about flashing and doing the OTA dirty flash of 12B.

Steamer86 said:
@datechnerd I just saw that. Nice. I used the flashify method for CWM ( loki version) on 11A, loki errors. Never got around to pushing loki. Is your CWM pre loki and flashable after extraction? Thinking about flashing and doing the OTA dirty flash of 12B.
Click to expand...
Click to collapse
when i updated, i did temp unroot(ended up being permanent), plugged phone into pc and used lg tool to update. then used ioroot to root again
the cwm is lokied and i believe only works with 12b

datechnerd said:
when i updated, i did temp unroot(ended up being permanent), plugged phone into pc and used lg tool to update. then used ioroot to root again
the cwm is lokied and i believe only works with 12b
Click to expand...
Click to collapse
I had so much trouble trying to modd my phone after the update.. I pushed lg stock ROM on here and am leaving it that way lol.. Now I have cyan mod 11 on here and its working beautifully.. I'm leaving it on as my daily os

Related

[Guide] Rooting Fascinate and Installing CWM using a MAC

So I posted a question yesterday to see if anyone could instruct me on how to root my phone using a MAC, no PC AT ALL. And then install CWM w/o having to use ODIN, b/c I do not have a PC. Well after some researching on my own I found out how and here is how I did it.
To root: Follow this thread (it requires using adb commands)
http://forum.androidcentral.com/ver...s/34188-rooting-using-mac-video-tutorial.html
To install CWM reference this thread, but here are the steps. You must download and install ROM Manager from market and also download zimage file. This also requires adb commands.
http://forum.xda-developers.com/showthread.php?t=804248
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redbend_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
I know this is vague, but if you know what you are doing and reference the threads you should have no problem. Let me know if you have any questions.

Tattoo recovery downgrade problem

Hi there!
I upgraded my wife's tattoo's recovery to 3.0.0.6 using ROM Manager, unaware that I will not be able to flash ROMs anymore (amend / edify scripting differences)
Now I cannot find a way to revert to original/older recovery, did try a lot of stuff around here and still no luck
Cannot flash using RUU as i receive a "Wrong bootloader error"
Any help would be appreciated.
Thanx in advance.
Adrian
________________________________________________
LE: After trying for some weeks now, I decided to post this message - few minutes after, I solved the problem - like this:
Code:
C:\>adb push c:\flash_image /sdcard/
365 KB/s (26172 bytes in 0.070s)
C:\>adb push c:\rtattoo\recovery.img /sdcard/
905 KB/s (3731456 bytes in 4.025s)
C:\>adb shell
# su
su
# mount -o remount, rw /system
mount -o remount, rw /system
# cp /sdcard/flash_image /system/bin
cp /sdcard/flash_image /system/bin
# cd /system/bin
cd /system/bin
# chmod 777 flash_image
chmod 777 flash_image
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
Thanx - OP please close.
why so much on typing CMD adb
use android commmander It is Great
You can try to use this script http://forum.xda-developers.com/showthread.php?t=644279 but replace the recovery file with the original recovery file . don't forget to rename it to the same name.

Hungover Root [Roots latest version without flashing anything]

Well, I know it's not particularly important since Zergrush still works but I've found an exploit of file permissions on the latest update.
This root causes things to break until you undo it due to it drops you into emulator mode on your phone. This isn't doing anything bad but a lot of things crash and only a few things really work...like ADB. So this is when you install su / superuser.apk and then you just undo it and reboot. Then you'll have superuser installed on your device. This should theoretically work for all samsung Galaxy S devices (Captivate, Vibrant, Epic 4G, etc) so feel free to try and link to this in those forums.
Story behind the root: I was drunk and bored, a friend had the Captivate, and I decided to look and find this.
Instructions! (The fun part!)
Download the .zip file and run the following commands:
Code:
adb push Hungover.sh /data/local/tmp/Hungover.sh
adb shell chmod 755 /data/local/tmp/Hungover.sh
adb shell ./data/local/tmp/Hungover.sh --recovery
After it reboots into recovery hold vol down+vol up + power and it should reboot. After its back up and running do this:
Code:
adb shell ./data/local/tmp/Hungover.sh --setup
after it reboots again, press Volume+, Volume- and Power at the same time, and reboot the system.
One more time with feeling:
Code:
adb shell ./data/local/tmp/Hungover.sh --root
****
After it reboots, run:
adb remount
adb push SuperUser.apk /system/app/
adb push su /system/xbin/su
adb shell "chmod 04755 /system/xbin/su ; chmod 755 /system/app/SuperUser.apk ; ./data/local/tmp/Hungover.sh --undo"
Then you will have root! Do whatever the hell you want at this point! :)
Download:
https://dl.dropboxusercontent.com/u/15069134/Hungover.zip
Changelog:
[code] Initial release 1.0
Credits:
Me for finding the exploit.
mechapanda for letting me potentially break his phone.
This post is mine for ****s and giggles.
It was fun watching my fun go through qemu, although i can't say i'd feel the same if i wasn't doing this on purpose.
Fails on Karbonn A37
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
dockers said:
Fails on Karbonn A37 with the following error.
C:\android-sdk\platform-tools>adb push Hungover.sh /data/local/tmp/Hungover.sh
486 KB/s (1993 bytes in 0.004s)
C:\android-sdk\platform-tools>adb shell chmod 755 /data/local/tmp/Hungover.sh
C:\android-sdk\platform-tools>adb shell ./data/local/tmp/Hungover.sh --recovery
/system/bin/sh: ./data/local/tmp/Hungover.sh: No such file or directory
Click to expand...
Click to collapse
're read the OP mate... It's for Galaxy S phones ! So it won't work for your phone
Sent from my SGH-I897 using Tapatalk 2

[Q] twrp d80010o....SOLVED.....

Have anyone figured out how to put twrp on version ATT D80010o
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
how do i do this
ralphie1267 said:
how do i do this
Click to expand...
Click to collapse
enable usb debugging, plug phone into pc, and you'll need adb in attachments
open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post
datechnerd said:
enable usb debugging, plug phone into pc, and you'll need adb in attachments
open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post
Click to expand...
Click to collapse
i have minumal adb and fastboot can i use this
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
sorry for the late response I was at work....
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]roid:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
for some reason I cant run command I downloaded it to the desktop
antawnm26 said:
for some reason I cant run command I downloaded it to the desktop
Click to expand...
Click to collapse
put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window
datechnerd said:
put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window
Click to expand...
Click to collapse
sweet it came up...Im not that great at it so Im going to need you to walk me through it
[email protected]:~$ adb shell- this should be my user name?
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
antawnm26 said:
sweet it came up...Im not that great at it so Im going to need you to walk me through it
[email protected]:~$ adb shell- this should be my user name?
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
the username is just from an example
datechnerd said:
the username is just from an example
Click to expand...
Click to collapse
ok im getting errors when I copy ~$ adb shell
C:\Users\Bull\Desktop\adb>~$ adb shell
'~$' is not recognized as an internal or external command,
operable program or batch file.
antawnm26 said:
ok im getting errors when I copy ~$ adb shell
C:\Users\Bull\Desktop\adb>~$ adb shell
'~$' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
just type
Code:
adb shell
don't type $ or #
C:\Users\Bull\Desktop\adb>:/ $ su
C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
C:\Users\Bull\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc
al/tmp/aboot.img
dcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.100 secs (10485760 bytes/sec)
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img
'pull' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img
'~$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>
d80010o
Any success guys?
datechnerd said:
just type
Code:
adb shell
don't type $ or #
Click to expand...
Click to collapse
i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks
ralphie1267 said:
i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks
Click to expand...
Click to collapse
think i got it i had to use esfile explorer to get it from the data/local because i suck at adb, but i got all the way with but started getting errors..hold on let me put it in drive
Code:
[CODE]
[/CODE]
antawnm26 said:
C:\Users\Bull\Desktop\adb>:/ $ su
C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
C:\Users\Bull\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc
al/tmp/aboot.img
dcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.100 secs (10485760 bytes/sec)
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img
'pull' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img
'~$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>
Click to expand...
Click to collapse
Code:
adb pull /data/local/tmp/aboot.img
datechnerd said:
Code:
[CODE]
[/CODE]
Code:
adb pull /data/local/tmp/aboot.img
Click to expand...
Click to collapse
https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9
antawnm26 said:
https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9
Click to expand...
Click to collapse
NON-flashablezips
flash with loki
if you don't know how rename the .lok to .img and put it on your phone and flash it with flashify instead
datechnerd said:
flash with loki
if you don't know how take the .img put it on your phone and flash it with flashify instead
Click to expand...
Click to collapse
I know its asking a lot but is there a guide on flashing with loki? also, do i just copy the image without the other files to my sdcard and flash with flashify?

[Q] Installing CWM (Philz) on G2 D803. "Failed to open aboot for reading"

Hi everyone,
I'm trying to install Philz Touch recovery on my LG G2 D803. My phone is rooted, and I followed the guide here, but I'm having a few problems.
The first problem is that if I just run the 1-click installer batch, it does this:
Code:
List of devices attached
0162667808d26b13 device
1556 KB/s (6376 bytes in 0.004s)
4421 KB/s (9558016 bytes in 2.111s)
[email protected]:/ $
So, I thought I'd open up the batch and try to run the commands myself. The batch looks like so...
Code:
@echo off
COLOR 07
Title CANADIAN LG G2 D803 CWM Recovery Installer
echo -----------------------------------------------------------
echo -----------------------------------------------------------
echo One Click PHILZ Recovery Installer for Canadian LG G2
echo by phil3759 -- thank him for this!
echo -----------------------------------------------------------
echo -----------------------------------------------------------
echo One Click Installer made by www.theAndroidSoul.com
echo -----------------------------------------------------------
echo -----------------------------------------------------------
pause
cls
adb devices
adb push loki_flash /data/local/tmp/loki_flash
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/recovery.img
exit
exit
adb reboot recovery
echo -----------------------------------------------------------
echo -----------------------------------------------------------
echo Installation successful!
echo Your device will now reboot automatically.
echo -----------------------------------------------------------
echo -----------------------------------------------------------
fastboot reboot
echo to close this window press any key..
pause
exit
After trying to run the next few commands, this is what I get...
Code:
List of devices attached
0162667808d26b13 device
1556 KB/s (6376 bytes in 0.004s)
4421 KB/s (9558016 bytes in 2.111s)
[email protected]:/ $ su
su
1|[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
10|[email protected]:/data/local/tmp $ chmod 777 loki_flash
chmod 777 loki_flash
[email protected]:/data/local/tmp $ ./loki_flash recovery /data/local/tmp/recovery.img
data/local/tmp/recovery.img <
[+] loki_flash v2.0
[-] Failed to open aboot for reading.
1|[email protected]:/data/local/tmp $
I'm assuming this is because the su command didn't work and I don't have root permission, but I'm not sure what I'm doing wrong.
[Edit]
After a bit more digging, I figured that part out. The problem was that I needed to run the SuperSU app on my phone as I typed su in the shell to get the popup to grant root permission. However, now I have another problem...
Code:
[email protected]:/ # cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 777 loki_flash
chmod 777 loki_flash
[email protected]:/data/local/tmp # ./loki_flash recovery /data/local/tmp/recovery.img
ata/local/tmp/recovery.img <
[+] loki_flash v2.0
[-] Input file is not a Loki image.
Any ideas?
Im having exactly the same problem on LG G2 D802
i've done this on so many devices, samsung s2, s3, and s4, nexus, lg optimus one and so on.... but i've never had as much problems with it as now...

Categories

Resources