Develop Bugs

[Q] Wanna up 4.0.4 for my nexus

i am a green hand in here and also abt all rooting,
just wanna up my nexus to 4.0.4 as i read that it optimized the nexus in a best way,
however know little abt that,
just find the latest post from Mike http://forum.xda-developers.com/showthread.php?t=1392310
i have some Qs b4 moving on-;
1. is it okay if i only follow Mike's youtube for upto 4.0.4?
2. rooting means no more maintenance from samsung?
3. the kernel provided by Mike can run at 1.35Ghz?
Hope i can reach some replies from you guys, many thx
bk

I never use anything but stock kernels (its the best for me) so i cant tell you about overclocking..you really dont need to on this beast of a phone....
NOTE: if you ever root your phone and it gets dropped or something just flash the stock files and you can send it into service and it will be fine.
Here is a simple tutorial. (you can find more detail by googleing it)
1. (sorry i forgot) set up ADB - google it...its long
1. Unlock bootloader (this will wipe everything) - "fastboot oem unlock"
2. put the 4.0.4 update.zip on the sd card.
3. flash cwm recovery (using the toolkit or fastboot - "fastboot flash recovery PUT_NAME_HERE.img when you are in fastboot (all keys together till vibrates)
4. reboot into recovery (after flashing it it will stay at the menu...use volume keys to get "recovery mode" to show up at the top then power to select it.
5. flash the zip.
6. reboot (you will lose cwm recovery)
7. lock the bootloader - "fastboot oem lock" in fastboot
8. your done..stock 4.0.4..not rooted...still get support.

ezcats said:
I never use anything but stock kernels (its the best for me) so i cant tell you about overclocking..you really dont need to on this beast of a phone....
NOTE: if you ever root your phone and it gets dropped or something just flash the stock files and you can send it into service and it will be fine.
Here is a simple tutorial. (you can find more detail by googleing it)
1. (sorry i forgot) set up ADB - google it...its long
1. Unlock bootloader (this will wipe everything) - "fastboot oem unlock"
2. put the 4.0.4 update.zip on the sd card.
3. flash cwm recovery (using the toolkit or fastboot - "fastboot flash recovery PUT_NAME_HERE.img when you are in fastboot (all keys together till vibrates)
4. reboot into recovery (after flashing it it will stay at the menu...use volume keys to get "recovery mode" to show up at the top then power to select it.
5. flash the zip.
6. reboot (you will lose cwm recovery)
7. lock the bootloader - "fastboot oem lock" in fastboot
8. your done..stock 4.0.4..not rooted...still get support.
Click to expand...
Click to collapse
many thx for ur reply.
But i still have some Qs abt that
1. root = wipe? i always confuse abt these 2 terms
2. set up ADB? adb is a prog/file?
3. fastboot oem unlock is a prog again?
4. haha nexus is the best? but... from the score prog nexus is not the best lol

billkkc said:
many thx for ur reply.
But i still have some Qs abt that
1. root = wipe? i always confuse abt these 2 terms
2. set up ADB? adb is a prog/file?
3. fastboot oem unlock is a prog again?
4. haha nexus is the best? but... from the score prog nexus is not the best lol
Click to expand...
Click to collapse
1- no. root = administrator/superuser acess in nix-based systems, like it was supposed to be, in our point of view. there are several kinds of wipe (cache, dalvik, userdata).
2- http://source.android.com/source/building-devices.html - check "Building fastboot and adb"
3- http://source.android.com/source/building-devices.html - check "Booting into fastboot mode" and "Unlocking the bootloader"
4- benchmarks aren't everything..

bk201doesntexist said:
1- no. root = administrator/superuser acess in nix-based systems, like it was supposed to be, in our point of view. there are several kinds of wipe (cache, dalvik, userdata).
2- - check "Building fastboot and adb"
3- - check "Booting into fastboot mode" and "Unlocking the bootloader"
4- benchmarks aren't everything..
Click to expand...
Click to collapse
thx for ur reply
i really need to do more search on net b4 moving into next steps
seems the up to 4.0.4 is a complex procedure
btw i c some posts talking abt baseband and kernel, is it 2 diff stuff?
i am puzzling with those terms

billkkc said:
thx for ur reply
i really need to do more search on net b4 moving into next steps
seems the up to 4.0.4 is a complex procedure
btw i c some posts talking abt baseband and kernel, is it 2 diff stuff?
i am puzzling with those terms
Click to expand...
Click to collapse
its not complex at all (even for you)
you don't need baseband and kernel (yes they are different) but you don't need to worry about that (when you flash the file it will do that for you)
just follow the instructions here: (or my post) and you should be fine...(credit to kangxi)
Change to update.zip and flash through stock recovery or CWM *STOCK CDMA NEXUS ONLY*
*02/05 update*
For those having issues, try flashing it with CWM using the toolkit in the dev section.
http://www.mediafire.com/?l1wxw3exb9195w7
Root not required but bootloader must be unlocked
1. Download the toolkit
2. Put your phone into fastboot mode
3. Open the toolkit
4. Choose the option to "Boot into Clockwork Mod without permanently flashing it"
5. Once in CWM, choose install from SD card
6. Choose install "update.zip" if you renamed it to that. Otherwise, choose the option to choose the file.
7. Viola!
JUST TO BE CLEAR YOU NEED THE VERIZON VERSION!!!!

ezcats said:
its not complex at all (even for you)
you don't need baseband and kernel (yes they are different) but you don't need to worry about that (when you flash the file it will do that for you)
just follow the instructions here: (or my post) and you should be fine...(credit to kangxi)
Change to update.zip and flash through stock recovery or CWM *STOCK CDMA NEXUS ONLY*
*02/05 update*
For those having issues, try flashing it with CWM using the toolkit in the dev section.
Root not required but bootloader must be unlocked
1. Download the toolkit
2. Put your phone into fastboot mode
3. Open the toolkit
4. Choose the option to "Boot into Clockwork Mod without permanently flashing it"
5. Once in CWM, choose install from SD card
6. Choose install "update.zip" if you renamed it to that. Otherwise, choose the option to choose the file.
7. Viola!
JUST TO BE CLEAR YOU NEED THE VERIZON VERSION!!!!
Click to expand...
Click to collapse
thx for ur reply,
i plan to up 4.0.4 in this coming sat,
btw i read something on g+
"4.0.4 ROM + franco kernel"
what means "franco kernel"?
is it a meaning of rooting or just wipe a latest room?

billkkc said:
thx for ur reply,
i plan to up 4.0.4 in this coming sat,
btw i read something on g+
"4.0.4 ROM + franco kernel"
what means "franco kernel"?
is it a meaning of rooting or just wipe a latest room?
Click to expand...
Click to collapse
Its just a kernel made by a guy called Franco...if you don't know what it is NY recommendation is to just leave it.alone...you don't need that for the 4.0.4 from tow rock..
so just leave it alone...hope this helps and isnt too pate..

Flashing a Recovery,Kernel and Rom[FAQ'S][NOOB FRIENDLY]

Easiest guide to flash a custom ROM and custom kernel
Lets accept it,we all have been here,confused what should do after i root/boot unlock
we think i know enough so lets get this going but then, we get stuck in the splash/welcome screen and we think **** this was such a bad idea
SO i created this thread for anyone who ever is confused,lost,seeking help.
IF YOU FIND THIS THREAD HELPFUL, BE SURE TO RECOMMEND IT TO OTHERS AND PRESS THE THANKS BUTTON :d
Thread Contents
1.Common terms/Android Slangs
2.Basic Requirements
3.Download links for Recovery Images for PRIMO U/ PRIMO C]
4.How To flash recovery
5.FAST BOOT FILES(download links) : HTC ONE V DRIVER (DOWLOAD LINKS)
6.How To Back Up Your Current Rom
7.Installing Your ROM
8.Choose Your Kernel(download links)
9.Flashing The Kernel[windows]
*Flashing The Kernel[MAC]
10.people who have already flashed a ROM and are confused how to upgrade it
11.Upgrading KERNEL
12.Stuck in Bootloops, Cant Pass the HTC welcome Screen
13.Some tips from me
Click to expand...
Click to collapse
Hope u have successfully rooted and boot unlocked
Common Terms/Android Slangs
a small guide on some of the android terms my Diablo67
Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading.
Fastboot:A diagnostic protocol used primarily to modify the flash filesystem in Android smartphones from another computer over a USB connection. It is part of the Android Debug Bridge library.
Utilizing the Fastboot protocol requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept any command sent to it over USB via a command line. Some of most commonly used fastboot commands include:
•flash - Overwrites a partition in flash with a binary image stored on the host computer.
•erase - Erases a partition in flash.
•reboot - Reboots the device into the either the main operating system or the system recovery partition.
•devices - Displays a list of all devices (with Serial #) connected to the host computer.
Flashing:The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Kernel:A kernel is a layer of code that allows the OS and applications to interface with your phone's hardware. The degree in which you can access your phone's hardware features depends on the quality of code in the kernel. The homebrew (rooting) community for HTC has made several kernel code improvements that give us additional features from our hardware that the stock kernel does not. When you flash a custom ROM, you automatically get a kernel. But you can also flash a standalone kernel ROM on top of the existing one, effectively overwriting it. These days, the difference in custom kernels is less about new features and more about alternate configurations. Choosing a custom kernel is basically choosing one that works best with your ROM.
Nandroid:To backup the current running rom.
Recovery Mode:A small separate operating mode you can boot your device into, used for device administration. Two popular custom recovery modes are Amon Ra and Clockwork.
Basic Requirements
1.A Boot-unlocked and Rooted HTC One V
2.Charge it till above 75% battery
2.A PC(this guide is for now only for windows)
3.usb cable
4.HTC driver download here or HTC SYNC
5.FastBoot Files[ click here>>> download them and put in a folder in c drive ]
> example c:\fastboot or c:\android
6.A recovery image(for image scroll down)
7.A Rom(thats ur choice)
8.boot image(scroll down)
9.put the rom(.zip file) in sd card
Here Are The Recovery Images
Recovery Images[PRIMO U/GSM]
1. CWM 6 by Lloir
2. TWRP 2.6.0 <<Ill Recommend [very user friendly]
3. CWM v5 Touch Recovery
Recovery Images[PRIMO C/CDMA
1. [VM/PRIMOC][RECOVERY] CWM Recovery
2. [VM/PRIMOC][RECOVERY] TWRP2 Recovery
3. [RECOVERY] [PRIMOC/CDMA] CWM 6.0.1.5
How To flash recovery
HOPE U HAVE THE FAST BOOT FILES
[IF NOT]
click here download them and put in a folder in c drive
example c:\fastboot)
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
u might have arrived at Hboot boot mode>>> now move up down by pressing the volume buttons and select fastbootwith the power button
Flash it via cmd(command prompt)
Enter these commands
Code:
[B][COLOR="Red"]fastboot flash recovery recovery.img
[/COLOR][/B]
How To Back Up Your Current Rom
(must for first time flashers)(nand=backup of current ROM)
1. Once the CWM/TWRP recovery installed:
Now enter Fast boot(power button +volume DOWN(for 15 + sec))
now move up down by pressing the volume buttons and select fastbootwith the power button
2. Once you are in the RECOVERY menu:
click backup and restore
click backup
the backup process is running. It will be a max 20 minutes to complete.
(optional step just to be sure)
3. once complete, check whether the backup is successful
click backup and restore
click restore
you will see your backup files, for example 2012-11-27 11-7
it should complete with in a span of time
4.Now if that is over go back to the previous menu
use the back button
click reboot system now to boot your device
Installing Your ROM
5.just do a factory reset and wipe cache, then click on install from sd card
6.flash it(the ROM in ur sd card shud be in a .zip format)
7.NOW.DON'T REBOOT UR PHONE GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot into bootloader)
Choose Your Kernel
9.download whichever kernel u want
[CDMA/PRIMO C]
SuperSick kernel Click ME
SICK kernel PRIMO C/CDMA click here
[GSM/PRIMO U]
SuperSick kernel Click ME
SICK kernel CLICK here
TITANIUM KISS kernel SENSE users CLICK here
HELLBOY kernel FOR AOSP based ROMS(cm9/cm10/AOKP/PA)USE THE LATEST ONE FOR 4.2.2 >click<
Flashing The Kernel[windows]
8.HOPE U HAVE THE FAST BOOT FILES (if not click here download them and put in a folder in c drive)
rename it boot.img and put it in the folder as the fastboot files
GO TO FAST BOOT MODE (VOLUME DOWN+ POWER BUTTON)(or there will be a option to reboot in recovery)
10.flash it via CMD
Enter these commands
Code:
11.[B][COLOR="Red"]Fastboot flash boot boot.img [/COLOR][/B]
12.[B][COLOR="Red"]fastboot reboot[/COLOR][/B]
Flashing The Kernel[MAC] by kalaker
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
13.enjoy
First boot takes some time have patience......be sure to ask questions or doubts
Ok For people who have already flashed a ROM and are confused how to upgrade it
Upgrading ROM
1.download your needed ROM
2.put in SD card
3.boot into recovery
4.no need to wipe everything,wipe caches(and if the dev says to full wipe do it)
5. (Unless u come from a different ROM eg.From Amazing Sense To CM10, in this case a factory reset i needed
6.flash the ROM
7.reboot
8.flash GAPPS
9. enjoy
Upgrading KERNEL
1.boot in bootloader
2.do the required steps(as mentioned above)
3.wipe caches
5.enjoy
Stuck in Bootloops, Cant Pass the HTC welcome Screen
ok, calm down, everyone has this problem while flashing, i get it so many times, they can cause by the following reasons
bad flash
wrong rom
you forgot to flash the kernel
wrong kernel
messed up the order in flashing
ok,
1.Bad flash-this occurs if the .zip file is corrupted
solution:= re flash the ROM, if still no, download the file again and try
2.wrong ROM- u may have downloaded a ROM that is not for ur device or a ROM which is of not ur description
for example u might me a PRIMO C device/CDMA and u downloaded a PRIMO U/GSM ROM
3.Wrong Kernel-Kernel is the link between ur software and hardware, if u flash the wrong one like the case mentioned above , download the correct one and re flash
4.[ FLASHING YOUR KERNEL SHOULD BE THE LAST STEP][UNLESS U HAVE A S-OFF DEVICE]
Ok Some Tips Which May Help You
1.Battery Draining fast?
-----get an app called BetterBatteryStats,run it over night.then next morning open it and check whats waking your device
Click to expand...
Click to collapse
2.Can i use scripts?
-----Your wish, the rom works perfect,running a script can ruin it in some cases(chill,even i run some)
Click to expand...
Click to collapse
3.Good/best/recommended ROMS?
-----all roms are good in their own way, but i can give u a list of recently updated roms
-----1.sphongle(4.2.2) 2.Slimbean 3.Cm10
Click to expand...
Click to collapse
will add more cheers
Hope this helps u

another get thanks quick scheme thread?
Sent from my One V

paarthdesai said:
another get thanks quick scheme thread?
Sent from my One V
Click to expand...
Click to collapse
LOL :silly:

no i plan to help!

My works
You call that work ??
Those are just tips

Y do u have a problem with that
Sent from my One V

No but that work word is pissing me off ..... For using it in a inappropriate place

donhashem.dh said:
No but that work word is pissing me off ..... For using it in a inappropriate place
Click to expand...
Click to collapse
Don't read it
Sent from my One V

to clarify, step 6: "flash" should be edited to say " install ROM from zip" to avoid the "flash" misconception associate with flashing kernels:good:

more detailed work should be there.. like you said install cwm or twrp.... give a link to where they are embedded in the words will be good...
and the above goes for the flashing rom part also...embed the link to the dev section
make it easy and tidy instead of all those ugly looking clutters you did
Sent from my One V

will work into that!

did it!

cybervibin said:
flash it via cmd
Enter these commands
Fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You forgot to mention to boot into fastboot. No offence, but it has to be much better written. Its not noob friendly at all.

m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!

cybervibin said:
m sorry abt that! guess missed it! wrote the thread throygh my phone!
any other problems i corrected the one u said!
Click to expand...
Click to collapse
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
>>Now enter Fast boot(power button +volume DOWN(for 15 + sec))<<<
and
1.Flash CWM 6 by lloir
or TWRP 2.3.1.0 ill recommend TWRP
>>PRIMO C /CDMA click here<<
To flash recovery HOPE U HAVE THE FAST BOOT FILES(IF NOT click here download them and put in a folder in c drive
example c:\fastboot
Click to expand...
Click to collapse
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!

now ill consider that! hard being a noob!

thetuxracer said:
If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Click to expand...
Click to collapse
Nice, I liked this!
Sent from my One V using xda app-developers app

soham_sss said:
Nice, I liked this!
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
thetuxracer said:
Yeah, you could try creatign sub sections, like thinigs to have before swap, then steps after that. Eg in step 1 you say
First you mention the ROM, then out of the blue you mention recovery. ROM should be introduced after a nand backup. You should also explain in short what a nand backup is. A sentence with an analogy is sufficient. I am a software developer and I would like to share a rule that I follow: If you need to add a comment in your code, that means the code is not readable. In the same way, when you mention something in bracket, it itself means that the sentence is no clear, and need rephrasing and rewording.
Dont get me wrong, I am not trying to insult or berate or anything, but I got it read by a friend who wants to flash his One V, and he got back to me with more questions than the guide answered. There a some step holes in the guide, and you have to write is as if you are a noob
Lastly, thanks a lot, this particular guide and your answers have been really helpful to me and the community.
Cheers!
Click to expand...
Click to collapse
how about now, noob friendly enough?

Yup, pretty cool! If there was a way to thank again..

ty!! please keep the recomendations coming!

[Q] Any 1 here experienced with kernels? Need your help for my Kitchen.

Ok firstly this may seem a bit confusing, I am copying this from a PM i sent to @wedgess
Hi, I am wondering if you would be able to make a bootable recovery image with TWRP as i have no idea how to do it and i can only find CWM ones which requires signature for "--update_package="
I don't want a kernel and i don't want a cwm image but i want just simple a TWRP recovery.img which is bootable like http://forum.xda-developers.com/showthread.php?t=1493996 but TWRP instead
Your kernel's work fine but i need it to boot a recovery.img then flash the new rom via "--update_package=" and then reboot device.
For more information check http://forum.xda-developers.com/showthread.php?t=2391169
I hope you can help, Thanks.
-------------------------------
TWRP works great with both the last 2 options so i need to some how create a bootable recovery img based on TWRP but i don't have a clue about kernel development... Could i maybe replace ramdisk with existing bootable recovery or something?
-------------------------------
So to put it simply, I need to switch out CWM on this recovery.img and put TWRP on it (The reasons for this are complicated to explain but i would be extremely thankful if any one could help and credit will be giviven)
So please can any one help me Thanks.

Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.

wedgess said:
Sorry I didn't reply to your final PM as I said due to real life and limited time I cannot do it for you, But happy to help assisting you if needed. Championswimmer has a tutuorial on what to change in the device tree for TWRP. Search function is down ATM so I can't link you to the thread.
Click to expand...
Click to collapse
Yeah no worries, Decided to ask any one else, As i really don't have the time to do this aswell as all the other stuff im doing. And it will take some one with experience a lot less time.
I tried switching out the /sbin folder but it didn't work and i didn't expect it to
I am hoping to find some 1 with a linux enviroment all sorted as i don't have a clue when it comes to kernels. surely there is a simple way to switch out a prebuiilt CWM Recovery with a TWRP recovery? Do you know what files TWRP and CWM use?
Thanks.
Altenatively any ideas on what needs to be changed to boot it to recovery always? if so i could modify a existing TWRP kernel (yours for example) and then force it to recovery.
EDIT
I assume you meant this guide?
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it

@wedgess ok so i got it working it now auto boots to TWRP but ADB isn't working, Any ideas?
Thanks so much i got it all working that guide helped

I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?

Bakisha said:
I am curious of what you are trying to do...
As i understand you want:
-flash (only) twrp recovery in fastboot mode
-reboot to recovery and flash rom from pc (adb sideload maybe?)
-reboot to fastboot again to flash kernel
-reboot
If i understand correctly you want to flash ROM (and kernel) from PC side, not dong it from phone?
Click to expand...
Click to collapse
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684

fma965 said:
ok this is what happens
1. Download rom and kernel from my kitchen via helper application on windows
2. verifiy md5's
3. fastboot fllash new kernel
4. fastboot boot "recovery.img"
5. once in the new bootable recovery i created/edited, send adb command "adb shell" > recovery --update_package=ROM
6. wait for rom to install, reboot
7. DONE! new rom and kernel flashed
All done automagically and without any user interaction other than picking the rom.
Check post 1 and 2 for more info - http://forum.xda-developers.com/showthread.php?p=46111684
Click to expand...
Click to collapse
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP

Bakisha said:
One word: WOW :good:
Not just you have ideas what you can do, but knowledge to do it. You have my respect man :highfive:
i'll check that app ASAP
Click to expand...
Click to collapse
Thanks current released version is quite buggy but new version coming soon
Any way since this problem is now solved, I will close the thread. if you want to discuss this then post on my kitchen thread or pm me

Cyanogen 12 (Lollipop) to Cyanogen 11 (Kitkat)

IT IS POSSSSIIIIIBBBBLLLLLE!​
I am rewriting this tutorial from RDS www.yuplaygod.com member's post
This is only meant for users who had rooted their device, in lollipop, have cwm or twrp recovery installed. IF not rooted find guides for it. (Hint: Google it)
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
So here is what we are going to do!
STEPS (VERY SIMPLE)
1) Download Back_to_cm11-signed by Abhiram.zip https://drive.google.com/file/d/0B4etFrzyEA01UklKR3N5T2JYeGc/view?usp=sharing
2)Download recovery-yu.img https://drive.google.com/file/d/0B4etFrzyEA01d2VGRXNuY2I1MGs/view?usp=sharing
3)Copy Back_to_cm11-signed by Abhiram.zip to SDCARD
4)Open recovery and flash it
5)Open fastboot mode.
6)Connect to your computer and flash recovery-yu.img
7)Open recovery by pressing "vol+"+"vol-"+"pwr"
8)Flash stock rom zip. Go to this guide to get it http://forum.xda-developers.com/yureka/orig-development/rom-t3042384
9) Rock with it!.
********FOR THOSE WHO ARE NOT GOOD WITH FASTBOOT**********
So yureka is something different. So you have to specify the device id for the fastboot to find it.
Install adb-setup.1****.exe https://drive.google.com/file/d/0B4etFrzyEA01SE9NTVNRWTl4Y0E/view?usp=sharing
Open CMD
Type fastboot -i 0x1ebf devices
If any device is detected you r good to go
Close CMD
Open the place where you have downloaded recovery-yu.img
By pressing shift, right click the folder (in which you have downloaded recovery-yu.img) click open command window here
and type fastboot -i 0x1ebf boot recovery-yu.img
That's it

Have you tried that and didn't face any hardbricks?

Yes
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..

Abhiram Shibu said:
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Click to expand...
Click to collapse
tank you

The OP suggest not to use fastboot mode as it may hard brick device & the steps tht follow are based on fastboot option... I'm confused, Is it safe to use fastboot mode thn?

ujilraj their is nothing to be confused. You can use fastboot mode. But if you flash system.img and data.img via fastboot, which has different partition styles, then you will end up with hard bricked phone... That's why!
Flashing recovery is very safe! GO for it!
I have tested it

For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???

A bit confuse
Abhiram Shibu said:
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
That's it
Click to expand...
Click to collapse
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin

ujilraj said:
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
Click to expand...
Click to collapse
Ujilraj That is absolutely correct ! You got it man.:good:

tirta.agung said:
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Click to expand...
Click to collapse
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!

Abhiram Shibu said:
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
Rather than flashing your zip via recovery, can I not use fastboot to flash the following in the order mentioned:
modem, sbl1, aboot, rpm, tz, hyp, recovery. The files that would be used are a part of cm11 fastboot package. After flashing all of these, boot to recovery and then flash the cm11 zip. I'll be essentially doing the same like you did. But I'll be using fastboot to flash firmware specific stuff. I strongly believe that these would not cause the infamous brick.
Thanks,
Sanjay

Abhiram Shibu said:
That is good question, I appreciate that.​
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....

coolboyforeva said:
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
Click to expand...
Click to collapse
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:

Abhiram Shibu said:
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Click to expand...
Click to collapse
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?

coolboyforeva said:
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
Click to expand...
Click to collapse
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/clockworkmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!

Abhiram Shibu said:
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/cyanogenmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Click to expand...
Click to collapse
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest

coolboyforeva said:
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
Click to expand...
Click to collapse
Tips to avoid hardbrick.
Don't flash ROM via fastboot
Don't Format partition using fast boot
You can flash boot and recovery via fastboot.
You can do anything in recovery.
Advice backup ROM before you install kernel, or any zip files. That will help you if you soft brick your phone.
Hit thanks if I help you in anyway till now.

On reading the OP's comments another doubt occurred, Do i need to unlock bootloader all the time when switching between KK & LP? (Will the internal SD memory gets wiped all the time... Do i need to backup every data on the internal SD memory onto PC before switching from KK to LP & vice-versa?)

Yes, but in case of upgrading and unlocking boot loader
Nice Question
When you downgrade from CM12 to CM11 your data will be safe. Unlocking boot loader will not do anything with your data:angel:
But When you are upgrading from CM11 to CM12 your data will be also safe, but the problem occurs when you try to unlock boot loader It will wipe all of your data.:crying:
When we unlock boot loader in kitkat CM11 by using command fastboot -i 0x1ebf oem unlock
It doesn't ask for any confirmations.
But in case of CM12 when you unlock boot loader by using the same command, before wiping data, it asks for confirmation. ie It tells to push vol+ to confirm or push vol - to stop.
If you see like this. Fastboot is going to erase your sdcard.
Its a good practice to backup your data when you r playing with your phones firmware, It will help you get back your memorable moments, favorite music etc.
If you have an otg cable. Keep a pendrive for backup
So concluding in unlocking CM11 no data loss unlocking in CM12 there is data loss.
Good luck:good:​

One more doubt, suppose i'm on KK & want to upgrade to some custom CM12.x rom, do i need to go through the process of installing stock cm12 all the time, or do u suggest any other simple way to directly do the same?

Progress?

I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work

and 4G, and sdcard1...

vmlc said:
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
Click to expand...
Click to collapse
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users

fastbooking said:
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
Click to expand...
Click to collapse
so, you confirm no 4g and camera working?

vmlc said:
so, you confirm no 4g and camera working?
Click to expand...
Click to collapse
yes no camera and 3G/4G

fastbooking said:
yes no camera and 3G/4G
Click to expand...
Click to collapse
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....

vmlc said:
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
Click to expand...
Click to collapse
I will try tomorow there's a french tutorial about that here's the link for the one's who speak french
phonandroid.com/forum/post1800321.html (www . before its just because i can't now)

Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
ok, the part I dont get is: "once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot"
how do you do this?

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
I don't install cyanogen like that,
First I update my phone with EMMA with the Open devices TA
-After I open the zip of the rom and i extract it somewhere you can find it
-take the zip AND THE GAPPS and connect your phone on usb for sending the zip on THE ROOT of your sdcard
-Enter in fastboot, and open flashtool (not emma the other)
-Flash the kernel called : boot.img
-Once Flashed reboot your phone in recovery (up button when the led is purple or violet)
-The led became gold color
- You now are (normaly) in cyanogen recovery
-Wipe data/Factory reset
-Wipe Cache for avoid bugs
-Now the fun part
-Apply update select the ROM and after the GAPPS
-Reboot and enjoy !
If the screen is black for a while after boot it's normal it's the system update
I also recommand you to take the
FXP-cm-12-20150412-UNOFFICIAL-seagull.zip
file because the other in cm12.1 are bootlooping
Now you can enjoy properly without camera and 3G/4G cyanogen
Sorry for my english I'm just a 14 french kid

btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?

vmlc said:
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
Click to expand...
Click to collapse
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:

fastbooking said:
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
Click to expand...
Click to collapse
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...

vmlc said:
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
Click to expand...
Click to collapse
Ok let's start off zero
you installed the zip via the philz recovery and after you wanted to flash the kernel ?

dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
thats what it says...

vmlc said:
thats what it says...
Click to expand...
Click to collapse
follow my tutorial it's the steps i followed and it works for me :good:

fastbooking said:
follow my tutorial it's the steps i followed and it works for me :good:
Click to expand...
Click to collapse
I got bricked meanwhile. Battery problem I think, not the first time...

ok, i think there is a missunderstanding.
in order to flash the kernel, you need to be in fastboot mode (with the blue light). so, once you have installed the zip file, shut down the phone (in recovery mode, select "power options/power off" , disconnect the phone and reconnect it in fastboot (maintain the vol up before and during the USB connection ).
you can now use "flashtool" (the Androxyde's one. to avoid confusion, the Sony's one is called EMMA or if it is more easy for you fastboot.exe
to use fastboot, you open a command line (Windows+R + type "cmd") , you go to the folder where the boot.img is and you enter the comand "fastboot flash boot boot.img". after ~2s the kernel is flashed, you can disconnect the phone and restart.
the first time, the boot time is about 5 min with a black screen after the animated screen, so wait a moment.
it's for that it's very important to have a well charged phone (min 40%) because the first start use a lot of battery, and you can't see anything.

I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...

vmlc said:
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
Click to expand...
Click to collapse
go on emma and select the android 4.4.4 update KK in the services line under open devices TA
It will restore the like the 1 st day but you will loose your data, but after you can install the philz recovery and restore the backup