hey there everyone I am trying to install slimkat ROM on my Verizon lg g2 and I keep getting ROM zip flash failed at the Loki boot image part. What are the steps to get the Loki flash part bump working in twrp recovery I am new to this device and I have been having issues with it and all I want is slimkat ROM. Can someone tell me the proper steps and the required files I'm already on the kitkat stock ROM and have v3 of twrp installed but I can't get slimkat to flash properly it keeps failing at the Loki part
I also tried flashing another twrp recovery and it failed as well
Please see my screenshot
Thanks in advance
Related
I don't remember if I deleted it or what but I only have TWRP 2.6.1 on my device as a recovery and I would like to reinstall CWM on my device. However, every "flashable" CWM zip I have tried through TWRP has failed and I'm not sure why. Don't nwant to brick my device and don't necessarily want to WebOS doctor it if I can avoid it, as my device has run fairly well (I am on 4.2.2). Any/all help is appreciated. Thanks!
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
bananagranola said:
I'm guessing that TWRP doesn't support flashing another recovery from it. Have you tried flashing recovery image from fastboot?
Click to expand...
Click to collapse
Not yet, although I managed to get a workable CWM running by moving an image to the boot folder and then updating to the latest working version (couldn't get the "touch" version to work via touch, however).
However, I may try flashing via fastboot if something unexpected happens. Thanks for the help
I know last time I tried flashing a 4.4 ROM I would get some error because of some weird compatibility thing with CWM or TWRP or something like that. I don't remember which recovery it was that I needed that would let me flash, I'm trying to flash beanstalk
You should flash the boot.img from the rom zip using fastboot, then boot into recovery and flash the rom.
I would advise doing a lot more research of how to flash custom roms and how to fix potential problems before continuing on any further as it will save you time in the future in case of any problems.
Sent from my C6603 using Tapatalk
extract from the zip file boot.img
flash it through fastboot , reboot your phone and go to recovery and then flash the rom
Hello
I have unlocked BL and rooted.
I've been trying to install CM12 on my Xperia V but everytime I'm in recovery and trying to flash CM12 it just aborts in the middle of it, and if i remember it gives an error a long the lines of "device is mint, rom isn't" I tried this rom http://forum.xda-developers.com/xpe.../rom-cyanogenmod-12-neo-s-homebuilds-t2967819
Since that pretty much bricked the phone Im back on stock JB [4.3] and I actually tried it twice, and no luck. Haven't tried any other roms since re-rooting and installing cwm/twrp is such a pain with xperia V and im not interested in anything else other than CM11/12.
I tried search but no luck
So, the question is, whats the most painless way to get CM11/12 on my phone, and what do I have to keep in mind while doing it. I'm very new to the phone and haven't figured out everything that I need to know I suppose.
Heres some "about phone"
Model : LT25i
Android ver: 4.3
Kernel ver: 3.4.0
Build number: 9.2.A.2.5
Either remove the first line in my rom zip/META-INF/com/google/android/updater-script (this will disable device verification, so do so at your own responsibility), then repack the rom zip and flash - or fastboot flash my rom's boot.img before installing the zip itself.
WhiteNeo said:
Either remove the first line in my rom zip/META-INF/com/google/android/updater-script (this will disable device verification, so do so at your own responsibility), then repack the rom zip and flash - or fastboot flash my rom's boot.img before installing the zip itself.
Click to expand...
Click to collapse
Thanks for the fast answer. So I'll just root and install twrp yet again, then flash your boot.img in with flashtool and THEN wipe/factory reset from twrp and install your ROM, right ?
villur700 said:
Thanks for the fast answer. So I'll just root and install twrp yet again, then flash your boot.img in with flashtool and THEN wipe/factory reset from twrp and install your ROM, right ?
Click to expand...
Click to collapse
Actually, no need for root and twrp. Just go ahead, flash the kernel, then reboot to recovery and follow the installation steps in my CM12 thread
So I decided to install cyanogenmod WhiteNeo ROM on my xperia T
did the entire process alright.
for recovery, CWM din't work so downloaded app from playsore and got TWRP from there.
the followed the steps from here to reach till step 8 from wiki.cyanogen guide.
stuck at step 8. DOn't get how to perform it because it is confusing.
altenrately sentthe zip package to sd card and tried there but says Error executing updater binary in zip.
I am stuck.
5%battery left.
and I dont know what to do.
can't even get out of Recovery mode.
device is unresponsive when connected to USB and is powered off.
can anyone please sort this out and explain in simple words how to get out of this mess?
p.s: if battery expires,then what happens?
tried installing stock firmware using flashtool
but
07/014/2015 19:14:54 - ERROR - Error in processHeader
all the time
googled all the solutions
none works
help please?
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
WhiteNeo said:
You should be able to flash official CM12 and proceed from there.
First, revert to stock FOTAKernel, then flash my ROM's boot.img via Fastboot mode in Flashtool. Then reboot to TWRP and check versions. Should be 2.8.7.0.
Then flash the ROM zip, gapps and supersu. Done.
Click to expand...
Click to collapse
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
aber96crombie said:
Thankyou soo much!
could you just elaborate a bit on how to revert to stock FOTA kernel and check TWRP version. confused about that.
btw... how do I use CM recovery instead of TWRP?
also if you have time.
another issue
before you posted this, I already flashed CM12 official, it works fine. But I am having an issue flashing gapps.
have tried
gapps-L-4-21-15.zip
pa_gapps-stock-5.0.1-20150215-signed (1).zip
gapps-lp-20141212-signed (1).zip
For installing
proceeded to install through sdcard and in recovery mode.
installs fine.
as soon as phone starts, google errors(stopped working) start spamming the screen and pressing ok just causes more to come.
reset all to factory version, reinstalled cyanogenmod with gapps, still no good.
can you point out the correct process for it or where am I going wrong.
Click to expand...
Click to collapse
Reverting to stock FOTA and getting official CM recovery (which won't flash anything but official CM builds and gapps) can be done with flashtool and a suitable ftf or using a Terminal command that you will find on the last pages of my CM12.1 thread for Xperia T.
TWRP version should be visible in settings or what one would call a "status bar".
And the force-closing gapps are just the result of a broken or outdated recovery. I've already been reported the same issue after creating a FOTAKernel TWRP for a friend.
You should be able to flash official CM12 gapps from Cyanogen Recovery.. Just google those.
Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
livgrave said:
Hi everyone, this question was asked already but I just want to make sure that it's safe to flash a 5.1 based ROM over a currently active Marshmallow ROM using TWRP using only the usual wipes? I remember that I had to flash a custom boot image with a PC or something like that in order for the custom recovery to work on my K3 Note, which I received with Marshmallow installed, so I'm not sure if I can hop back to 5.1 if phone never even had it installed. Any advice?
Click to expand...
Click to collapse
Yes, IT IS SAFE but there are some points to note:
Every Rom Zip contains a boot.img file which is also flashed when the zip is flashed.
You do not need to replace boot.img in order to install TWRP, but you need it to flash SuperSU.zip to your device or install xposed
Remember You need to wipe data partition (No need to wipe Internal) in order to continue.
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
livgrave said:
Thanks for the reply. I don't know why, but I remember when I was installing TWRP I couldn't boot into it until I flashed a new boot image or something like that. All I could boot into was the stock recovery or something like that. I needed to use SP flash tools and flash something in order to get it to work. So it's safe for me to try 5.1 ROMs? They seem to be more stable than custom Marshmallow ROMs....
Click to expand...
Click to collapse
You must have flashed the recovery.img ( and also the boot.img) because my root methods mention them.