thats nothing to worry about
just means loki is working
yes it is the default theme created by Tassadar (the one in their github)
was an oversight on my part that theme was there the whole time, swear I looked for it oh well
[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]
- Thread starter Drgravy
- Start date
just means loki is working
was an oversight on my part that theme was there the whole time, swear I looked for it oh well
In github is the res folder for the 1920x1200 resolution not for the 1200x1920 that is the right one for G pad.thats nothing to worry about
just means loki is working
yes it is the default theme created by Tassadar (the one in their github)
was an oversight on my part that theme was there the whole time, swear I looked for it oh well
Sent using Mixed Theme from omegadroid.co
Sorry to ask something so basic, but I want to understand when to use the appropriate .lok file and when to use the OpenRecovery-twrp-2.6.3.0-awfi.img file. Those posts that I quoted seemed to say it was okay to use that OpenRecovery...img file in flashify. Yet other posts seem to say the appropriate .lok file must be renamed to a .img file, and then flashify will work with that renamed file.Yes, Just open Flashify, select recovery, select the TWRP file, and flash. It will then reboot into recovery.
The OP seemed to say that the OpenRecovery...img file should only be used in the 2nd method of flashing, i.e. in the dd command.
So finally to get to my question! Are the .lok files and the OpenRecovery...img file completely different formats? Or are they the same, the only difference being that the .lok files are for TWRP 2.6.3.1, while the .img file is for TWRP 2.6.3.0? Can flashify use either the .lok (renamed) or the .img file? Similarly, can the loki_flash command flash either the .lok file or the .img file? And finally, could method 2 (with the dd command) use either the .lok file or the .img file? Thanks for bearing with me!
It is my understanding that lok files are built to bypass the bootloader, flashify only works with IMG files. If you have a file that has been customized to bypass the bootloader and just change the name back to IMG it appears to do the trick(both show up on flashify and bypass the bootloader). This is just my reasoning I don't know if it is 100%. All I know is that once you change the .Lok to .IMG flashify will recognize it and it works.
Sent from my LG-V500 using Tapatalk
I've succeed installing TWRP...
however whenever I flash either CMB rom or CM11 I get this message
"assert failed run program ('\system\bin\loki.sh")==0"
when I boot the device, screen says
[Secure Booting Error!!
Cause: Device Unlock, so Boot Success!] message
which means my device is unlocked....
what have I done wrong? or what is wrong with my device?
however whenever I flash either CMB rom or CM11 I get this message
"assert failed run program ('\system\bin\loki.sh")==0"
when I boot the device, screen says
[Secure Booting Error!!
Cause: Device Unlock, so Boot Success!] message
which means my device is unlocked....
what have I done wrong? or what is wrong with my device?
Last edited:
I know mate. I flashed the latest TWRP Recovery so I saw you fixed it. I am telling that in TWRP's github there is now default folder (res folder) for 1200x1920 resolution yet. In github there is only a 1920x1200 resolution folder.
Sent using Mixed Theme from omegadroid.co
Please tell me which version of twrp you have installed ? is it 2.6.3.1?
also since your device software version is V50010e LOKI in the rom source needs to be updated
I am working on something for you to test I will pm you when its ready
adb reboot recoverysorry
or there are some apps that can reboot into recovery
I got this error, anyone can help?
Thanks in advance!
127|[email protected]:/data/local/tmp $ ./loki_flash recovery /data/local/tmp/twrp.lok
[+] loki_flash v2.1
[-] Failed to open aboot for reading.
Thanks in advance!
127|[email protected]:/data/local/tmp $ ./loki_flash recovery /data/local/tmp/twrp.lok
[+] loki_flash v2.1
[-] Failed to open aboot for reading.
Make sure you are rooted
You have the $ icon you need the #
Try:
adb shell
su
Then you should get a # prompt
I still have $ instead of #
I have rooted my device with Kingo Root
---------- Post added at 01:37 PM ---------- Previous post was at 01:32 PM ----------
all done! insert usb cable again and started over with procedure, now I can boot into recovery mode.
thanks!
Use xpose and gravity box and add power menu options. It also adds features without bloating the ROMsorry
Sorry for my post, but is there any other, maybe noober way of installing the recovery. Something like the nexus toolkit that exists for the nexus. This is the first Android device I own not being a nexus. I'm used to use the toolkits available. Not very familiar with adb and Fast-food commands.. Is there any "easier" way than the two ways on the first post? Best regards
You can flash TWRP with an app called flashify. Directions are near the start of this thread. In all fairness it's even easier than Wugs toolkit
Sent from my LG-V500 using XDA Premium 4 mobile app
Sent from my LG-V500 using XDA Premium 4 mobile app
This:
http://forum.xda-developers.com/showthread.php?p=31767716
Learn the basics of adb and fastboot; if i can you can too or you should be nowhere near a nexus device.
Go to the nexus 5 root thread. That's a good place to get the idea how to get around the fastboot.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone