I'm using VS980, on 12B (sorry if I shouldn't have taken the OTA for what I want to do but I didn't know it'd be a problem). I just got this phone a few days ago and I've spent a fair amount of time trying to flash CWM touch to it, using the "loki" method (which I have no idea what loki is or what it's for), and consistently failed.
Each time I try pushing a CWM img with adb using loki_flash it results in an error at the end saying [-] loki aboot version does not match device.
I'm assuming this means the version of loki_flash file I'm using isn't compatible with 12B, but the OP in this thread states that in his walkthrough he's referencing the VZW img file, so I'm confused as to why it isn't working.
Moving on from that, I tried pushing the img without loki just using adb (method #2 in the above thread), and it appeared successful judging by the command prompt, however upon reboot I'm left with a black screen and have to hard restart my phone. I'm left without a working recovery.
With both of these methods failing, I tried installing CWM using an app called freegee, which I found to work, and CWM was fully functional. However, I thereafter tried flashing an AOKP ROM and a CM ROM and both failed. Both failure prompts were different, but the first one mentioned something about loki (again, what does this mean?) I tried rebooting from there and found my phone soft bricked (bootlooping) and I had to restore my nandroid backup.
So in summary, clearly I'm doing something wrong throughout all of the flashing processes that's resulting in recoveries that don't correctly flash ROMs for this phone. Right now I'm left running rooted stock with absolutely no recovery, unless I use freegee to flash TWRP or CWM but I'm left with recoveries that won't flash ROMs.
If anybody could help me sort out this mess I'd appreciate it.
Krogey said:
I'm using VS980, on 12B (sorry if I shouldn't have taken the OTA for what I want to do but I didn't know it'd be a problem). I just got this phone a few days ago and I've spent a fair amount of time trying to flash CWM touch to it, using the "loki" method (which I have no idea what loki is or what it's for), and consistently failed.
Each time I try pushing a CWM img with adb using loki_flash it results in an error at the end saying [-] loki aboot version does not match device.
I'm assuming this means the version of loki_flash file I'm using isn't compatible with 12B, but the OP in this thread states that in his walkthrough he's referencing the VZW img file, so I'm confused as to why it isn't working.
Moving on from that, I tried pushing the img without loki just using adb (method #2 in the above thread), and it appeared successful judging by the command prompt, however upon reboot I'm left with a black screen and have to hard restart my phone. I'm left without a working recovery.
With both of these methods failing, I tried installing CWM using an app called freegee, which I found to work, and CWM was fully functional. However, I thereafter tried flashing an AOKP ROM and a CM ROM and both failed. Both failure prompts were different, but the first one mentioned something about loki (again, what does this mean?) I tried rebooting from there and found my phone soft bricked (bootlooping) and I had to restore my nandroid backup.
So in summary, clearly I'm doing something wrong throughout all of the flashing processes that's resulting in recoveries that don't correctly flash ROMs for this phone. Right now I'm left running rooted stock with absolutely no recovery, unless I use freegee to flash TWRP or CWM but I'm left with recoveries that won't flash ROMs.
If anybody could help me sort out this mess I'd appreciate it.
Click to expand...
Click to collapse
The files from the thread you linked to aren't Loki patched (to my knowledge) look in the Verizon development thread and search for CWM/TWRP for 12B. Those should work. I've been using TWRP and can flash ROMS fine. Also its a matter of those ROMS being patched to flash while on 12B. CM11/gummy/carbon/cyanfox are patched and flash fine.
Here's the link
http://forum.xda-developers.com/showthread.php?p=48879826
Sent from chdhsheh fhhdud
Thank you, that did the trick as far as adb pushing a recovery with loki. It worked and I'm looking at my CWM screen right now. I'll try flashing CM and let you know how it goes although I don't anticipate any problems from here on out.
Thank you again.
Related
I'm trying to install jelly bean on my kindle fire but using KFU I've only managed firefirefire and clockworkrecovery.
I tried rooting using KFU to root but that doesn't work. Always gets stuck with the twrp.img error saying it's the wrong image (seems to be a common problem)
I've tried getting twrp installed using adb shell but when I get to the command to load the recovery image I get error; couldn't load recovery image. I thought maybe there was a problem so I tried loading the fff bootloader even though I already had it on my kf but it also returned with error: couldn't load image.
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
soupmagnet said:
Theoretically, if you have clockwork recovery, there is no need for TWRP. But if you must have TWRP instead, use clockwork to flash a rom (and FFF1.4 while you're at it). Boot into the rom and use the Smirkit to install TWRP. It will save you a lot of hassle.
Click to expand...
Click to collapse
The problem is getting root access. Most of the guides I've tried to follow require twrp installed to get into recovery. Without root I can't flash another rom.
I also already have FFF 1.4.
So I reverted back to stock and went through the manual process again and I was able to get it to work. When I was initially trying to flash twrp with the command line I copied pasted the name of the file without adding the file extension. Fixed that by adding .img and everything went through. Got Jellybean on here now and it's running great.
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
soupmagnet said:
If you are installing a custom rom (including MoDaCo), there is no need to go through the "rooting" process, hence saving you "a lot of hassle". Recoveries, like CWM and TWRP provide temporary root access.
Click to expand...
Click to collapse
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
hxu976 said:
This is odd because I tried installing the JB rom after I got CWM on there. It booted up to a black screen and left it there for 5 minutes and still black screen. I reverted back with the update bin from amazon website after that.
Click to expand...
Click to collapse
That has nothing to do with "rooting". Most of the time it's caused by a bad download (always check MD5s) or not "wiping" correctly before installation.
ALCON,
I have tried repeatedly to install a custom recovery after rooting my phone and have been highly unsuccessful thus far.
I originally rooted my phone after the 12B OTA. I tried flashing the 2.6.3.2 version of TWRP using the Loki Flash tool via command prompt on my PC. However, it gave me an error at the end that stated the input file was not a Loki image. I was unable to reboot into any recovery at this time.
I used the LG flash tool to unroot and reinstall 10B, after this i was able to root again using IOroot and access the stock recovery.
This time i decided to download an already Loki patched 2.6.3.2 TWRP from their website and push it from my sdcard using the dd command in a terminal emulator window. It pushes fine and looks like it installed but i end up with a black screen when i reboot into recovery.
Whwt gives? Thank you for taking any time to help, ots greatly appreciated.
Respectfully,
Crunch
are you following this guide?
http://forum.xda-developers.com/showthread.php?t=2449670
Yes, that was one of many guides i was utilizing. I ended up getting it to work. It appears i was trying to flash 2.6.3.3, not 2.6.3.2, which from what I've read is intended for 4.4 -- long story short i was able to install 2.6.3.2 from my sdcard using terminal emulator.
Thanks for chiming in, mate!
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.
Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.
So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud
vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports
It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.
free gee very fast
Use Flashify u n00b.
Ok so currently running a rooted VS980 on 12B with CWM 6.0.x.x non touch. I have attempted to flash both CM10.2 and a 4.4 kitkat absed rom (pa_g2-4.0-ALPHA-20131205-vs980). In both cases I get the same error,
asset failed: run_program("/system/bin/loki.sh") == 0
E: Error in /data/media/o/ (filename of rom in zip format)
(status 7)
installation aborted
My current steps are a backup of rooted 12B,
wipe/factory reset
wipe cache partition
wipe dalvik
format system.
I also attempted to install a GAPPS .zip to see if it was happening with all zip files, the GAPPS installed with no issues.
phone also will take a restore from CWM so at least im not bricked in the meantime
Now that that is all out of the way can anyone tell me what is happening here? Only my second rooted phone first being a droid 4 and by the time I rooted it there was a lot out in the form of auto runs and apps to take care of all the steps to root/flash roms. So my knowledge level is pretty novice on this.
UPDATE: so after my reading im coming across random issues with CWM on the LG G2. going to attempt to push ASOPA 4.4 with GAPPS after I switch to TWRP.
Get same thing on trwp
Sent from my VS980 4G using XDA Premium 4 mobile app
Make sure you are on the latest versions. Darker ones will not install kitkat. Roms
Sent from my LG-D800 using Tapatalk
UPDATE 2:
Ok, so after following the guide below and face palming myself about a thousand times through the process, I've come to another snag..... I get all the way to the end in both options 1 and 2, then get the error below. Option 3 (GooManager) states that there is no recovery for my phone.
http://forum.xda-developers.com/showthread.php?t=2449670
[+] loki_flash 2.1
[-] loki aboot version does not match device
looked around through the thread and cannot find a definitive answer on what im doing wrong or what I may have done wrong in rooting or with already running CWM.
I want to attempt to go back to stock. Completely unrooted and start from scratch but not sure the path to take on this. I've factory reset via CWM but the phone is still rooted and the apps i removed via titanium backup are missing as well.
Is there a way to pull a stock firmware and somehow push it to the phone so that everything i have done thus far is erased? ( excuse the terminology here) like erasing and reformatting a computer's hdd and re installing windows.
update:
http://forum.xda-developers.com/showthread.php?t=2432476
Hopefully this stock firmware guide works...
Goo doesn't work either lol. Use freegee to install recovery. Will take you about 2 minutes to complete and you will be rooted and have a custom recovery installed
Sent from my LG-D800 using Tapatalk
Thats how I got CWM onto the phone after I rooted. After all my reading though, I want to go back to stock and start all over again. I still haven't got a chance to start the proccess yet, been pouring through the thread about reverting back to stock firmware to see what issues have come up. From mwhat I can tell the issues were all related to people not fully reading the directions provided by the OP. Will update once I have attempted. FreeGee worked like a charm for getting CWM on though
Ok, so using the thread listed above i was able to revert back to 11a!!!!!!! now, onto IORoot and see if i can loki twrp 2.6.3.2 and then flash 2.6.3.3.
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
corrsea said:
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks for clarifying that!!!!!
So as of now I have re flash stock 11A per the guide (showed unrooted once done), Rerooted via IORoot 22 and then adb flashed twrp 2.6.3.2, Now I am going to flash the 2.6.3.3 .zip via TWRP and then try to flash A ROM and Kernel.
Back up and running!!!!
IORoot22
TWRP 2.6.3.3
ASOPA 4.4 BETA (updating as daily releases come out)
Slim GAPPS (might switch to regular due to the speech to text function being missing from keyboard but need to do some reading to figure out if running the full GAPPS will fix that or if it is something with the ROM ) EDIT: as i typed this i got a text and as i replied I noticed the icon is there now on the keyboard.... FACEPALM....
Thanks for all the information that was provided guys. Probably could have cleared this all up without the thread and just reading, Thanks for not flaming me and turning me away with a statement to use the search function.
To anyone reading this to find a fix for an issue they are having here are the links in order of what I did to get back up and functioning.
1. Went back to stock
http://forum.xda-developers.com/showthread.php?t=2448960 ( how to go back to stock )
http://forum.xda-developers.com/showthread.php?t=2141817 ( how to set up SDK )
2. ReRooted
http://forum.xda-developers.com/showthread.php?t=2448887 ( IOROOT how to )
3. TWRP
http://forum.xda-developers.com/showthread.php?t=2449670 ( TWRP how to )
All these guides worked the first time through for me, make sure you take the time and read all the directions in them.
Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
AnitaMedic said:
Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
Click to expand...
Click to collapse
Stock recovery files won't update bootloader, just make sure to use the correct one for your bootloader. It should only be a matter of loki, just make sure you follow specific install instructions.
Sent from my SGH-I337