Develop Bugs

plzz help to flash a cm11

i want to flash CM11
i have done many a times in samsung..but sony its hectic.
plzz help me out..i have unlocked my bootloader.
do i have to install superuser? but how?
nd trying different methods but not succesfull..
m on latest stock firmware....
thnkx in advance

Firstly, make sure you are in 15.4.A.0.23 and above.
1. Head over to this site. Download the latest build for Nicki.
2. Extract boot.img from the downloaded zip and flash in fastboot.
3. Wipe /data and /cache through CWM.
4. Put the CM11 zip in any storage then flash it in CWM.
5. (Optional) Download GApps from here. Make sure it's for 4.4.4. Then flash it in CWM.
If you are having root permission problems, download the latest SuperSU flashable zip from here then flash it in CWM. Disable the default Superuser app (it can be found in Developer Options by tapping the Build Number 7 times) in CM11 and untick the box in SuperSU that states "Respect CM root settings."
That's it. Hope I helped.

elmkzgirxp said:
Firstly, make sure you are in 15.4.A.0.23 and above.
1. Head over to this site. Download the latest build for Nicki.
2. Extract boot.img from the downloaded zip and flash in fastboot.
3. Wipe /data and /cache through CWM.
4. Put the CM11 zip in any storage then flash it in CWM.
5. (Optional) Download GApps from here. Make sure it's for 4.4.4. Then flash it in CWM.
If you are having root permission problems, download the latest SuperSU flashable zip from here then flash it in CWM. Disable the default Superuser app (it can be found in Developer Options by tapping the Build Number 7 times) in CM11 and untick the box in SuperSU that states "Respect CM root settings."
That's it. Hope I helped.
Click to expand...
Click to collapse
does 4.4 Gapps have photo sphere or not?

theperson333 said:
does 4.4 Gapps have photo sphere or not?
Click to expand...
Click to collapse
I don't think so. They removed it because it doesn't work for most devices.

elmkzgirxp said:
I don't think so. They removed it because it doesn't work for most devices.
Click to expand...
Click to collapse
for anyone interested, I have found that it is due to our devices lacking gyro.

developing kernel

Hi guys,
First of all I don't know where thi thread should be. so, mods please spare me.
I have been compiling (Developing) kernel for a week now and I compiled 2 kernels from cm11 source and also from cm10.2 source using NDK toolchain4.6 (as 4.8 gives me some errors) .
I got zImage and also modules.I thought I will make a flashable zip but I don't have any other files and also I don't have source for any rom.so i pulled out boot.img from the AICP release 5.0 RC and packed my zImage in to a boot.img (renamed zImage to boot.img-kernel) and tried to put that boot.img and modules in to AICP zip folder and flash but everytime it gets stuck in LG logo.there could be many reasons for this as i am using a very crude method to put boot.img and modules files in to a rom zip and also it could be the kernel itself.I can't flash it in fastboot mode as my device won't stay in fastboot.
SO if anyone wants to try if this kernel works or not,please flash the provided boot.img in your device fastboot and let me know.If it works then i can go on making changes and adding OC ,governors and all.
BTW you know that normal XDA slogan so i won't repeat.
boot.img

Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx

1. Unpacked boot.img (i pulled it from AICP release 5 RC.zip) using the script
2. Unpacked ramdisk.gz in to ramdisk folder
3. deleted boot.img-kernel file and renamed zImage to boot.img-kernel
4. repacked using the script
I used this script

I started looking at some videos to try and make a kernel also can you share a guide

sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.

sukesh1090 said:
sure.this is the best one i found,
[Tutorial] Building Your First Kernel
before this you need to install some things and you can follow this guide for that
How to Compile AOSPA from Source
follow this guide till installing android SDK then download android ndk and then follow the guide I provided above "building your first kernel" .
one more thing i wasn't able to install oracle jdk6 according to that guide so google it,you will find the installation procedure.
Click to expand...
Click to collapse
Thanks we need some attention on this device, its still an invincible device, if it was on more carriers it would have gotten the attention of many

I want to prest my respect and thanks for youres work, both. The g pro still are a great device, I don't understand why aren't some quality and quantity of stock Base room's and kernel's! So, I hope we seen some of that from yours!
I don't have skills to help, only I can say... Good luck and keep on!

bountyman334 said:
Wat steps did u take as in making the image
Am making a kernel for stock KitKat sphinx
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.

sukesh1090 said:
Is it necessary to lokify the boot.img before flashing or will freegee will do it for us??
I don't understand why the stock unmodified CM 10.2 kernel get stuck in LG logo.I don't get any errors while compiling but still it won't boot.
Click to expand...
Click to collapse
What Recovery you use?

I believe the recoveries provided through FreeGee are already lokified.
Sent from my LG-E980 using XDA Free mobile app

I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??

sukesh1090 said:
I am using TWRP provided in freegee OG pro. I remember sometimes seeing the log while flashing it says lokifying.... .I think it does the job for us but then why the hell my kernel is not booting.
Atleast If fastboot was working it would have made my life much easier,I didn't have to flash then if it won't work then flash some other kernel,its pain in ........
guys is fastboot working for you??
Click to expand...
Click to collapse
Try CWM 6.0.4.4 [emoji15]

Mervingio said:
Try CWM 6.0.4.4 [emoji15]
Click to expand...
Click to collapse
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o

^^
does fastboot work in your recovery??

bountyman334 said:
Thought i would share this fount a twrp recovery 2.6.3.0 loki-fied and i made a simple swap and it works for all my flashing (am On Spihnx 1.6) <-- Flash this daily becuz am testing g3 & g flex apps and i dont have to switch over to cwm....
but Note when u wipe data,cache,dalvik u have 2 reboot 2 recovery
https://mega.co.nz/#!hhBHWb4I!NEgT5TIeEgZEvLKMG22sAB3m1i6Uzk3bXB2wElIEO7o
Click to expand...
Click to collapse
Not sure ladt time i tru use TWRP need back to LG Flash tool

this is legit am using it now between cm11 and sphinx...but i fiqured out that u have to be on 4.1.2 to use twrp tried it with the stock kitkat and it dosent wrk ...so beware dont use stock kitkat at all by my understanding its boot need to be loki fied first

I think the development stopped

dante_67 said:
I think the development stopped
Click to expand...
Click to collapse
Yup for now because I am not in home. next week I will get back to my comp and then I will continue the development .I compiled with both NDK toolchain 4.6 and 4.8 both compile without error but kernel gets stuck in LG logo.so I will try with linaro tool chain,let's see how it goes.

My own impression, of samsung s2 days, linaro is far more superior to ndk

[RECOVERY] Flashable ZIP-TWRP 2.8.1.0 - LG G Pro: E980, E988, F240LSK

First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
We are now in the early developmental stages of Android L and the last version of TWRP that I could locate here at XDA for the E980 was v2.6xx. I feel that we have a need for the latest version of this recovery now that we are transitioning over to Lollipop. With that said, the following is copied straight from his post over at that site.
TWRP Recovery SELinux support only for the rom install or extract img style set_metadata.
- Works well on all the GPRO and GK: E988, E980, and F220K F240LSK.
- Full SELinux support: That means you have can flash the rom CM 4.4, 5.0 or higher (set_metadata).
- USB-OTG Support
- Support for MTP - can copy the data directly to your phone when you are in Recovery
- Support screenshot of Recovery [hold Power + volume controls]
- Supports backup IMEI (EFS)
- Support Hard reset using hardware keys: Hold the Volume Down + Home and resources.
- Can operate on both 4.1.2 and 4.4.2 (even 5.0)
Installation: The first download listed is a flashable ZIP file that can be flashed through whatever recovery you have installed now. Not recommended if your are running a stock based ROM as it causes a "boot certification error" after flashing. Only use the flashable .zip file if you are already running a custom ROM based on CM source.
For those of you that are running a stock based ROM, please use Flashify to flash any of the three .IMG files that are listed below. Descriptions are in the download links.
Note: If you are running a custom ROM that is based on CM source, yet want to use one of the themed versions below, it is safe to use Flashify to install any of the recovery .IMG files below to your device.
All devs, please feel free to use this as a building block to obtain a reliable TWRP 2.8.1.0 recovery for our E980 device.
UPDATE 12/24/2014: Attachment downloads have been removed and all links are now directed to my 4Shared storage. The account has a 3GB per day / 30GB per month limit so I am hoping that it will be satisfactory for our download needs. If anyone would like to set up a mirror, please feel free to do so and PM me with links that I can add to this post.
UPDATE 12/24/2014 - Part 2: This version of TWRP for our G Pro devices now supports SD card in recovery mode!
Many thanks to @soralz , @culot and @hoangnova for delving into the code and providing us with this excellent recovery for our G Pro devices!
All of the above is assuming that your device has already been rooted and a custom recovery installed via the FreeGee method first. Do not flash anything posted in this thread before obtaining root and installing a custom recovery first!
Download Links:
TWRP 2.8.1.0 Unofficial - Flashable Zip -> DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Stock TWRP Theme -> DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Play Themed ->DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Altered Splash Screen -> DOWNLOAD
@soralz Google Drive Mirror - All Versions, IMG and ZIP -> DOWNLOAD
Click to expand...
Click to collapse
Happy flashing but flash at your own risk. I assume no responsibility for any damages incurred by doing so. - HTR
Now, some legal mumbo jumbo:
This recovery is provided "AS IS" and without warranty or support of any kind and I expressly disclaim all other warranties, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Under no circumstances shall I be liable for any incidental, special or consequential damages that result from the use of, or inability to use this recovery.
- Unless otherwise stated, the recovery image that is made available in the original post of this thread is distributed as "freeware". You may freely use and modify this recovery without restriction, whether it be for personal use or distribution to others.
Click to expand...
Click to collapse

hitekredneck said:
First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
We are now in the early developmental stages of Android L and the last version of TWRP that I could locate here at XDA for the E980 was v2.6xx. I feel that we have a need for the latest version of this recovery now that we are transitioning over to Lollipop. With that said, the following is copied straight from his post over at that site.
TWRP Recovery SELinux support only for the rom install or extract img style set_metadata.
- Works well on all the GPRO and GK: E988, E980, and F220K F240LSK.
- Full SELinux support: That means you have can flash the rom CM 4.4, 5.0 or higher (set_metadata).
- USB-OTG Support
- Support for MTP - can copy the data directly to your phone when you are in Recovery
- Support screenshot of Recovery [hold Power + volume controls]
- Supports backup IMEI (EFS)
- Support Hard reset using hardware keys: Hold the Volume Down + Home and resources.
- Can operate on both 4.1.2 and 4.4.2 (even 5.0)
Installation: This is a flashable ZIP file that can be flashed through whatever recovery you have installed now.
Happy flashing - HTR
Click to expand...
Click to collapse
Awesome! Thanks!
Just wondering... I was using it for a while and does work great. Then, tried to get cyan delta up and running with it today. It seemed to give an error. I then tried it with philz and worked fine.
Is anyone using the two together and experiencing it, or just me?

@hoangnova - Can you shed some light as to why flashing BlissPop v1.1 with this recovery would fail?
By the way, thank you for a recovery that might possibly be modified to work with our device! It seems that it just needs a few bugs ironed out to be fully functional with the E980 for AT&T.

Thanks
hitekredneck said:
First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
Great find cant wait to get into it and see what is possible.
One thing obviously loki support is set up with this recovery right?
Click to expand...
Click to collapse
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.

Fant0m3 said:
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.
Click to expand...
Click to collapse
@hoangnova may possibly be able to provide source. Not sure how often he checks in here though. I think that the more we could get working on this, the better our chances would be.

Yup agreed
I agree but I'm pretty slow at this developer stuff as I've taught myself everything and you know wife and kids and all that BS kind and limit my ability and availabilityI'll eventually find a solution it just may not be in a timely fashion

Modified TWRP 2.8.1.0 to E980
Hi guys, I am using the TWRP a while ago and realise this TWRP almost can't flash any ROM on it for ex. CM11 Nightlies. So I made some modifications to this recovery using simple Android Kitchen. By editing it's default.prop. This recovery is simply taken from f310lr (which preventing us from flashing other ROM because it's a LG GX!) more info.
Summary of changes can refer attachments below.
Working:
Everything, except can't mount External SD Card, now you can flash like a boss.
Download
Flashable zip, with the modified recovery and another one is simply the *.img file. Flash with Flashify or similar app.
Extra, TWRP Materialised theme.
It has been modded to fit my taste for welcoming Lollipop, if you want the TWRP theme simply place it to /sdcard/TWRP/theme/ui.zip.

Hopefully we can get the latest version of twrp going. From the change log it looks like the latest has fuller 5.0 features.

soralz said:
Hi guys, I am using the TWRP a while ago and realise this TWRP almost can't flash any ROM on it for ex. CM11 Nightlies. So I made some modifications to this recovery using simple Android Kitchen. By editing it's default.prop. This recovery is simply taken from f310lr (which preventing us from flashing other ROM because it's a LG GX!) more info.
Summary of changes can refer attachments below.
Working:
Everything, except can't mount External SD Card, now you can flash like a boss.
Download
Flashable zip, with the modified recovery and another one is simply the *.img file. Flash with Flashify or similar app.
Extra, TWRP Materialised theme.
It has been modded to fit my taste for welcoming Lollipop, if you want the TWRP theme simply place it to /sdcard/TWRP/theme/ui.zip.
Click to expand...
Click to collapse
Does it work on lollipop roms?

eocobby721 said:
Does it work on lollipop roms?
Click to expand...
Click to collapse
I suppose the pic can tell you.

@soralz. Thanks for sharing. My comment on latest version was not meant to follow what you shared it was just a comment in general.
The twrp looks great!

soralz said:
I suppose the pic can tell you.
Click to expand...
Click to collapse
Thanks. I asked because I flashed it once n couldn't flash any lollipop rom except da Chinese cm12 ROM. Once again thanks

Verified by yours truly. I flashed this recovery and used it to flash BlissPop v1.3 with no problems whatsoever. Now if only we can get someone that knows their beans to fix the problem with external SD not mounting.

I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.

arek78 said:
I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.
Click to expand...
Click to collapse
Optimus G, or Optimus G Pro? Which do you have? If it is a G Pro, yes you can flash this one using the twrp 2.6.3.3 that you installed with FreeGee.

arek78 said:
I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.
Click to expand...
Click to collapse
*Only works on custom ROM, if you are on stock you will get boot verification error.

So I can not install on Stock 4.4.2.

hitekredneck said:
Verified by yours truly. I flashed this recovery and used it to flash BlissPop v1.3 with no problems whatsoever. Now if only we can get someone that knows their beans to fix the problem with external SD not mounting.
Click to expand...
Click to collapse
From a lengthy dissection of its innards, it looks like it was cobbled together mainly from parts of Nexus 5 and G2 recovery stuffs, and isn't even trying to load the external_sd. There also seems to be several other discrepancies, where its targeting a Nexus 5 or G2, when it should be targeting the almighty G Pro.
Take a look at the '/etc/twrp.fstab' -- it's missing '/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable', which I think may be a culprit in the lack of SD.
I've taken my undisciplined hand at fixing these issues, but I can never seem to repack the goddamn thing properly. I got sad skillz.
EDIT: I just noticed when you 'unpackbootimg' it provides all the info to repack properly. Friggin' duh, yo. Testing time! *crosses fingers and legs and black cats*
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
hitekredneck said:
UPDATE #3 12/19/2014: I have been notified by soralz that when trying to flash the zip file version of this recovery when running a stock ROM, the flash will not process properly and will hand at "boot certification verification." Therefore I am providing a link to the recovery.img that can be installed using Flashify or similar utility.
Click to expand...
Click to collapse
Is it Lokification error/lack?
hitekredneck said:
Download recovery.img for Flashify here-> [URL="https://doc-0k-2g-docs.googleusercontent.com/docs/securesc @soralz
Click to expand...
Click to collapse
Your link doth stink. Exactly what is this 'recovery.img' you have there, where is it from.

culot said:
Take a look at the '/etc/twrp.fstab' -- it's missing '/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable', which I think may be a culprit in the lack of SD
Click to expand...
Click to collapse
Okay, got it:
- Open ADB shell while in OP's TWRP 2.8:
Code:
mount -t /system /dev/block/mmcblk0p23
mkdir /external_sd
echo "/dev/block/mmcblk1p1 /external_sd vfat rw" >> /etc/fstab
mount -t /dev/block/mmcblk1p1 /external_sd
Now the microSD is mounted at '/external_sd'. It does not show up on your computer when you enable MTP though; and next time recovery loads, those changes will be gone, so you have to do it all over again -- that is until someone bakes a fixed twrp.fstab into a recovery.img and/or flashable zip (my attempts so far go bootloops at the LG logo, every time).
---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------
arek78 said:
So I can not install on Stock 4.4.2.
Click to expand...
Click to collapse
Have you tried using the Sphinx APK to install it? Just worked on my stock Kitkat 20g.

Fant0m3 said:
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.
Click to expand...
Click to collapse
This Omnirom TWRP Recovery and this guide should do fine. You'll have to tinker in the e980 stuff though. You can use the configuration files from OP's version to start with, and then make proper wtih e980 device specifics. This TWRP repo for a Japanese version of the phone holds some solid leads.
It compiled fine for me early this morning, but would not boot. But! After spending many hours since then learning how it really works, I'm certain when I take another crack at it tomorrow that it will be simple to get working. So close, yet so burned out for today.

[Kernel][Recovery][CM12]TWRP and CWM recoveries for Lollipop (CM12) [discontinued]

CM12 now comes with CyanogenMod recovery, which is unusable for now. So here are repacked kernels with TWRP and CWM.
For now, use Recovery-in-FOTA images! This thread probably will not be updated anymore. Also you can use this script.
Download TWRP (for PecanCM's Beta 3, not flashable)
Older versions (CWM included):
for FXP-2015-0115:
1. TWRP
2. CWM
For FXP-2015-0110 build:
1. TWRP (with fixed app2sd)
2. CWM
For PecanCM's 01.03 build:
1. CWM
2. TWRP
3. TWRP 2.8.3.0 (new)
For PecanCM's Beta 2:
1. CWM
2. TWRP
Thanks to:
@osm0sis for Android Image kitchen for Windows (and to @FindYanot and @Bonoboo for discovering it for me).
@JustArchi for compiling TWRP 2.8.3.0 for our device in ArchiDroid 3.0.1.1
Installation:
1. Extract archive to the root of external sdcard and run in terminal emulator su then /ext_card/flash_kernel.sh
or in adb adb shell /ext_card/flash_kernel.sh
2. Flash boot.img drom archive via fastboot (fastboot flash boot boot.img) or fastbootmode in Flashtool
These are obsolete, but will work though
3. Via adb:
- Place boot.img to the root of internal sd (adb push *path*\boot.img /sdcard/ (replace *path* with path to file on your PC))
- adb shell dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
4. Via Terminal emulator (you can download it on Play Store):
- Place boot.img to the root of internal sd
- Enter su and allow superuser access
- Type dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

I want warn, that at least CWM (probably and TWRP) not backup apps moved to sdcard.
Because it "don't know" that they on external sdcard1, not on sdcard0
So manually copy folder .android_secure only on PC via cardreader.
Or using RootExplorer copy all from /mnt/asec/
But restoring will be hard because it must performed before boot.

Hi @cucumber09 , I just wanted to know what are the changes in this kernel and original kernel except the recovery change...
Please tell..!

abhatia1435 said:
Hi @cucumber09 , I just wanted to know what are the changes in this kernel and original kernel except the recovery change...
Please tell..!
Click to expand...
Click to collapse
There are no other changes, I didn't rebuild the kernel, I just repacked it with replacing recovery ramdisk using very simple script.

Bonoboo said:
Or using RootExplorer copy all from /mnt/asec/
But restoring will be hard because it must performed before boot.
Click to expand...
Click to collapse
Is it possible to restore them using AromaFM, or is this folder unmounting when the phone is not booted in system?

A little question
Err @cucumber09 Is this the same overclocked kernel from FindYanot or is this the stock kernel that's not oc? Cuz when i flashed this just now the performance is slower than FindYanot's kernel.

XtremeWave said:
Is this the same overclocked kernel
Click to expand...
Click to collapse
There no any word about overclock in first post.
So it's without overclock = nothing surprising that it's slower than with.

Yeah. You're right. Please don' t think of me as an idiot nor undestimate. I'm 11, but I rooted and unlocked the BL of my C1904 just to get Cm11 in 2012, I was just wondering as he said repacked etc. So i guess i have to TRY other things. Well the kernel's fine. Just that I wanted an oc cwm kernel.
Thanks @ Bonoboo

XtremeWave said:
Yeah. You're right. Please don' t think of me as an idiot nor undestimate. I'm 11, but I rooted and unlocked the BL of my C1904 just to get Cm11 in 2012, I was just wondering as he said repacked etc. So i guess i have to TRY other things. Well the kernel's fine. Just that I wanted an oc cwm kernel.
Thanks @ Bonoboo
Click to expand...
Click to collapse
should i flash both cwm and twrp

You need to flash one. Choose what u want.
Here's one over clocked kernel (Cwm 6.05.1) for Beta 2 of the CM12 ROM by Senior Member PecanCM for the Xperia M:http://www60.zippyshare.com/v/11764560/file.html
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Well TWRP is great. But I prefer CWM

UPDATED!
Recoveries are updated for new build (press thanks to Bonoboo). Dload links are in the OP.

New TWRP version
Kernel with new version of TWRP (2.8.3.0), wich should be more compatible with Lollipop. Compiled by sir @JustArchi. I didn't test it on LP yet. If someone will test it, let me know is it working as it should. Changelog is here (our previous version is 2.8.0.0).
UPD: I already tested it: recovery works, but I don't know, is there any bugs.

Will this recovery work on 5.0.2 as well??

manoj36 said:
Will this recovery work on 5.0.2 as well??
Click to expand...
Click to collapse
One post above:
Recoveries are updated for new build
Click to expand...
Click to collapse

cucumber09 said:
Kernel with new version of TWRP (2.8.3.0), wich should be more compatible with Lollipop. Compiled by sir @JustArchi. I didn't test it on LP yet. If someone will test it, let me know is it working as it should. Changelog is here (our previous version is 2.8.0.0).
UPD: I already tested it: recovery works, but I don't know, is there any bugs.
Click to expand...
Click to collapse
I have test the 2.8.3.0 TWRP, and so far its work as expected
Sent from my C1905

madper said:
I have test the 2.8.3.0 TWRP, and so far its work as expected
Sent from my C1905
Click to expand...
Click to collapse
Okay, if there is no bugs, I will repack kernels for next builds with this version of recovery.

it's working for me as well & very stable so far checked..thank you! :thumbup:

Thanks for update sir

Update TWRP for FXP build
TWRP updated for FXP-20150110
TWRP version: 2.8.3.0

CWM update for FXP
CWM updated for FXP-20150110.
Happy flashing!

[Recovery][FOTA]CWM and TWRP recoveries for custom ROMs

Now we have official TWRP support, so this thread will not be updated anymore. For more info about official TWRP visit this thread.
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.7.0
TWRP 2.8.6.0 (this and next versions are compiled for Xperia M by me)
Older versions and CWM:
TWRP 2.8.5.0 (port from Xperia L)
TWRP 2.8.4.0 (thanks to @Rohan purohit for bringimg it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader this partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.

Download
TWRP 2.8.6.0>>>
TWRP 2.8.5.0>>>
TWRP 2.8.4.0>>>

Restoring original image
- You can restore original FOTAKernel flashing it via Flashtool by flashing any firmware (just uncheck everything in "wipe" section and uncheck everything in "exclude" section excluding "FOTA" like in attached screenshot).
- Or install attached zip via recovery or flash FOTAKernel.img from archive as it is written in OP.

cucumber09 said:
TWRP version is 2.8.0.0, because I could not boot 2.8.3.0 this way (maybe due to ramdisk size limitations), I'll look for this later and will try to fix it
Click to expand...
Click to collapse
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea

kh34d said:
Excuse me sir,
is this recovery work with cm11 which I have now??
Can I flash it now,
so when I decided to flashing cm12 being ready[emoji4]
I hope I explained my idea
Click to expand...
Click to collapse
I don't know for sure. Download both recoveries, try to flash one that differs from yours and reboot recovery. If it changes, that means it works on CM11 kernel. BTW, even if it doesn't work on CM11, it will work when you will flash CM12 kernel. So you can flash it to be prepared.

Some one please uploade original fota kernel, i'm forgot to backup them .. thanks

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Okay, I will upload original FOTAKernel.

itsnie said:
Some one please uploade original fota kernel, i'm forgot to backup them .. thanks
Click to expand...
Click to collapse
Everything about restoring is in 3rd post.

cucumber09 said:
Everything about restoring is in 3rd post.
Click to expand...
Click to collapse
Thangs, now all problem will be fixed ..

@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?

KHM90 said:
@cucumber09 Will it work for stock 4.3, i know you mentioned for custom rom but just curious about it, what do u think?
Click to expand...
Click to collapse
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.

cucumber09 said:
No, it needs custom kernel, that includes extract_elf_ramdisk, stock kernel doesn't. BTW, there are CWM-included kernels for all stock ROMs. And TWRP is not available for stock. I can try repacking stock kernel with TWRP, but I doubt it will work.
Click to expand...
Click to collapse
Ok thx, Not needed just wanna know whether it will work or not
btw, FOTA kernel awesome idea:good:

I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...

ndrancs said:
I try to repack my custom kernel with justarchi twrp version. I can Confirm it doesn't boot to fota recovery. Main boot.img is cm12 first nightly. It always boot to CyanogenMod recovery. Still search for solution...
Click to expand...
Click to collapse
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.

I'm confused, does it work for locked bootloader?

pincheraro said:
I'm confused, does it work for locked bootloader?
Click to expand...
Click to collapse
No way. It even won't work on stock kernel with unlocked BL.

@cucumber09 Which build is the attached FOTA restore zip from? .9?

elmkzgirxp said:
@cucumber09 Which build is the attached FOTA restore zip from? .9?
Click to expand...
Click to collapse
No, it is from earlier build, but also from 4.3. From first 4.3 build, as I remember.

cucumber09 said:
I read sources of extract_elf_ramdisk utility. And found there something about uncompressed ramdisk size, there is limitation to 8 Mb by default. So, I think, we should reduce ramdisk size by removing unnecessary or redundant files and binaries (must be done very carefully) or to commit change in our kernel.
Click to expand...
Click to collapse
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?

ndrancs said:
You mean this source code: Dees-Troy
I inspect the twrp, but no found the file that save to be removed. Btw, what commit needed to apply to kernel?
Click to expand...
Click to collapse
I read these sources. And 49th line defines size of uncompressed ramdisk. But now I am not sure, which one is used in our kernel. I suppose, that newer one.