Develop Bugs

Guys WhAt Is Difference in FLasHInG A rom By Cwm REcoVerY OR StoCK

while trying many cusOMS RomS ANd FLAshable ZiPS ,Came aCRoss TWo TERMS Flash BY cwm RecOVeRy or sTOck cwM Wats THE Difference betwen THE two Sorry FOR a A NOOB quESTion but WAS very Anxious to KNow tHE DiFereNCE......THANKS IN ADVANCE

custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!

hell_lock said:
custom roms are modified versions of your current stock rom to make it beautiful and faster.
flashable zips are of 2 types:
1. They are made for updating/adding something in your current rom.
2. Its a file format which lets you to install things using cwm. It can be a rom itself too!
Click to expand...
Click to collapse
i want to ask wat is difference if we flash a rom using cwm or using stock recovery

talwarrokzz said:
i want to ask wat is difference if we flash a rom using cwm or using stock recovery
Click to expand...
Click to collapse
cwm has more options than the stock one so using cwm is preferable

hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone

hell_lock said:
cwm has more options than the stock one so using cwm is preferable
Click to expand...
Click to collapse
CWM has more options and very simple to understand and use!
STOCK=less option.... hard to use... some times its cause a boot loop!

talwarrokzz said:
your answers are good but still cant fullfill my requirements (sorry if rude)
wanted to ask why some roms only prefer cwm recovery not stock and why only cwm is used to replace boot image of our phone
Click to expand...
Click to collapse
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!

hell_lock said:
u can flash a rom from stock recovery too but as I said above, it is recommended to use so that u can restore ur phone if something goes wrong. Wen i tried to flash boot.img frm stock recovery it gave an error but wen u flash it from cwm it is successful . Any more doubts or are you still unsatisfied? ASK MORE!
Click to expand...
Click to collapse
are you mad?

PwN.CraZyTagZ said:
are you mad?
Click to expand...
Click to collapse
Yes I am!!

its depends on scripting... stock recovery runs only amend scripting but cwm 3.0 or later edify scrpiting... and it has so many options then stock... one notable option and frequently using option is dalvik cache wipe... this is y most of em prefer cwm...
I GUESS THIS IS THE ANSWER... BUT IM NOT SURE ABOUT... GOOGLE IT FOR MORE INFO... I READ IT SOMEWHERE ONCE UPON A TIME... SO I FORGET SOME OF THE THINGS...

stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.

irfanbagus said:
stock recovery require your zip to be signed for security reason. cmw is not. signing itself is simple process that only need few second, but once you signing your zip you can't change it's content. you must resign your zip if you do. that's why some people prefer cmw, because you can easily change zip content with regular archive manager without resign.
Click to expand...
Click to collapse
Yes friend u r right............
Sent from my GT-S6102 using xda premium

Let's get to your qeury . . . Flashing via stock or CWM
With CWM Recovery you can:
Flash boot.img (kernel)
Flash Custom ROMS
Flash .zips without resinging packages
Choose what partition to be mounted during flash
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
Flash .zips but requires zips to be signed and resigned if there are modifications on the package

CarlDeanCatabay said:
...
With stock:
Flash boot.img (kernel) -but most kernel are ment to be flashed via CWM as it has a higher chance of success and less likely to cause bootloops
Flash Custom ROMS - but some ROMS use scripts that are NOT SUPPORTED by stock recovery
...
Click to expand...
Click to collapse
that's not stock recovery problem, but custom rom problem. a lot of custom rom have poorly written (or generated) updater-script. rom dev put a lot of work on making his/her rom looks good, but give very small attention to installation process. some rom event try to mount /dev/stl19 to /system in instalation process. that partition not exist in sgy. and updater-script not depend to which recovery that you use. it's depend to updater-binary inside your zip file.

Need help unrooting htc one x

I bought a htc one x rooted not knowing that at the time. I know its got charmeleon 1.29.401.11 software and the kernel version says 2.6.39.4-gc993261 [email protected] #1
Also i have the app supersu but when i open it up it says ''There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Dont have a clue what this is but i want my phone back to stock because ever since i bought the phone i have had problems esspecialy with PkMn Tweaks which never works properly. It is very good to have it rooted so i would either like to get it all fixed or just unroot it fully
Any help would be much grateful Thanks !

To go back to stock you need to relock the bootloader and flash a ruu here's a list of ruu http://forum.xda-developers.com/showthread.php?t=1543604
And to fix the problem you need to flash supersu.zip in cwm recovery or flash a custom rom
Sent from my HTC One X using xda premium

Since the phone is already unlocked, you might as well go ahead and install a Sense custom ROM to get the maximum out of it. A sense custom ROM like Viper X or ARHD will keep the stock look and feel and all the sense goodies while allowing you to tweak it as you like. My personal favorite is Viper X, it has lots of tweak options already built in with an easy to use app, and supports OTA updates.

PhoenixFx said:
Since the phone is already unlocked, you might as well go ahead and install a Sense custom ROM to get the maximum out of it. A sense custom ROM like Viper X or ARHD will keep the stock look and feel and all the sense goodies while allowing you to tweak it as you like. My personal favorite is Viper X, it has lots of tweak options already built in with an easy to use app, and supports OTA updates.
Click to expand...
Click to collapse
I am new to all of this so how would i do that then ?
thanks !

just typed in viperx and it looks very simular to the charmeleon i have but alot better i just dont have a clue how to do any of the things like flashing the rom or what a bootloader is i want to learn what it all is but just need someone to teach me haha

To install a custom ROM you need to have a custom recovery like Clockwork Mod Recovery (CWM). Since you already have a custom ROM you should already have CWM. You can check by rebooting into HBOOT (Boot loader) by holding down the Vol down and power button at the same time, and then select “Recovery” from HBOOT menu options.
If you can successfully boot into CWM then all you have to do is download the appropriate ROM file, flash the correct boot.img then flash the ROM from CWM.
Have a look at this video : http://www.youtube.com/watch?v=ix1XKErVikY
The steps are same for any ROM.
Just to summarize the main points:
Make sure your bootloader is unlocked and CWM is installed and working properly
Download the ROM zip (check the MD5 to verify integrity of the file) then copy it onto the phone
Reboot into HBOOT (Vol down + Power)
Select Fastboot
Flash boot.img (using flashboot.exe from command prompt)
Once done select HBOOT again then Recovery to boot into CWM
Install Zip from SD card and choose the ROM zip
Do a full Wipe within the installer (This is important!)
Follow the wizard to complete the installation (if you want to keep the stock look select stock theme), the installation wizard for Viper X is little different from what is shown on that video, but the steps are clear and easy to follow.

liiaaammmm94 said:
just typed in viperx and it looks very simular to the charmeleon i have but alot better i just dont have a clue how to do any of the things like flashing the rom or what a bootloader is i want to learn what it all is but just need someone to teach me haha
Click to expand...
Click to collapse
Watch these they should help the best way to learn is to read the instructions on the Rom you want or YouTube it
Unroot back to stock
https://www.youtube.com/watch?v=SZuAjz4PIjU&feature=youtube_gdata_player
How to flash custom roms
https://www.youtube.com/watch?v=gxJf8xIVVC0&feature=youtube_gdata_player
Sent from my HTC One X using xda premium

[ROM][d802] Recovery Flashable PURE STOCK EUR OPEN 80220f (+ root)

Made this from the new 80220f open EUR kdz.
This is the complete LG KK 20f ROM - nothing missing or messed with.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB, Rooted KK or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://drive.google.com/file/d/0B_ESvfVtZzEwaWRaTjRNUEdDOEE/edit?usp=sharing
Credit to Chainfire for the rooting method.

good job. but you don't put the download ?

paglop said:
good job. but you don't put the download ?
Click to expand...
Click to collapse
Link is there....!

why use AutoRec ? the recovery is lost ?

how do i acquire custom recovery once i flash 20f? flashify app?

zekurosu said:
how do i acquire custom recovery once i flash 20f? flashify app?
Click to expand...
Click to collapse
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.

paglop said:
why use AutoRec ? the recovery is lost ?
Click to expand...
Click to collapse
Yes,you will lose your custom recovery if you install this stock rom. But don't care about it.You may use AutoRec and your recovery will be back :good:
Edit : Hmm i think knock code will unusable if we flash TWRP with AutoRec.
Edit 2 : Aarghh i misunderstood. After using AutoRec and we will install any kernel with knock code support.

Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.

Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this. If you want to have a pure stock ROM, kernel and all, its easiest to use the alternative method to keep your recovery (at the bottom of the op)
Click to expand...
Click to collapse
If i'm not wrong,the alternative method is not addicted to keep custom recovery. The custom recovery (whatever you have) won't be there after flashing this rom all the way mate.:good:

Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Click to expand...
Click to collapse
Precisely!
If someone already has Custom Recovery, and isn't overly bothered about preserving it, then this is potentially quicker and easier that then kdz method. And with easy root. Big plus point.
If you want a completely Stock experience of course.
What we don't know is how much development LG have done with the kernel. So, if one uses Autorec, any benefits of a later LG stock kernel will be lost.
Enjoy!

I am on v20d stock kit kat rooted with ioroot. D802 model. Does this flashabel rom include bootloader? Cause to have a custom recovery, I will have to use autorec app, which will dowgrade my bootloader. So will this rom work if the recovery has been flashed with autorec?
And also flashing this rom means that stock recovery will be flashed too?

I installed this 20f. it corrects problems ratio with slimport on small screen.

Just updated to D80220F. I can confirm that there is a Google Folder pre created. Havent noticed much else yet. will keep you updated.
Whole system feels super fast. Is it just me or is this faster than 802D/802B?
Knock on seems more reliable. Senses it way better and ignores ghost touches better.. Auto brightness seems to be managing brightness better too.

i have twrp 2.7.0.0 custom recovery, and i'm on d802b firmware (kk stock) with dorimanx kernel...
just 1 question to be sure (because i didn't quite get the OP):
- will i lose twrp if i flash this zip? (if yes, how do i get custom recovery back and safely?)
thanks in advance

Not option for ART
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
60nine yes you lose twrp. It is for return to official.

ok, thanks... and how do i get twrp back? is it even possible?
on that matter - can "recovery.bin" from this zip be replaced by custom recovery .bin file?

shriom_manerker said:
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
Click to expand...
Click to collapse
Can you make a tutorial or write it down how you did it??? Because I wan't stock rom but don't want to lose recovery....

First root, and autorec for instal recovery. But you need a custom kernel .
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
read a little before

ok, so autorec works for 20f... all i wanted to know... (i don't care for knock code, i just want knock on to work)
the OP was a bit confusing - maybe it needs to be updated with a basic FAQ...
if anyone tried to flash this, then used autorec for custom recovery and flashed latest dorimanx 5.7 kernel - please confirm if knock on works (not knock code)
thanks in advance

Not kernel just autorec

[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.

SM-T700 Bootloop after flash of customrom, again and again

Hallo everybody, greetings from germany.
I would need some support from you guys on a bootloop case for the sm-t700. I searched my ass off in google and xda but could not find a solution.
So now after hours of trying it myself I like to ask for help.
In the following I will describe what I have done to come to this point including everything I installed etc.
The stock rom was lollipop 5.0.2 and already installed.
- usb debug mode on
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- forgot to install busybox and rootchecker for verifying root.
- backup of IMEI/EMFS (data is now on pc)
- in recovery backup of Boot.img
- wipe data/cache/dalwik/system in one go
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls from 5 to 10 minutes.
Next I wanted to do it better by installing busybox and cheking for root, because
I thought first that this could be the main cause for the bootloop.
- downloadmode
- flashed succesfully "T700XXU1BOE5_T700DBT1BOD1_HOME.tar.md5" via odin v.3.10.7 to get to stockrom again
- usb debug mode on
- downloadmode
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- verifyied it with rootvalidator
- installed busybox
- deleted all knox stuff
- installed twrp app to get to v.2.8.7.0
- recoverymode
- backup of everything
- wipe data/cache/dalwik/system
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls again from 5 to 10 minutes.
Next I went into recovery and restored everything as before the flash of the customrom.
This happens in the same way with blisspop and liquidsmooth roms.
Hope anyone knows something.

Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
You need to flash the kernel provided in that thread or flash the whole rom again.
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.

ashyx said:
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
Click to expand...
Click to collapse
By "multi flash" do you mean the install procedure in twrp that automates the installation procedure? (add zip)
And how am I able to flash after each successful boot if there is nothing to boot left after wipe?
ashyx said:
You need to flash the kernel provided in that thread or flash the whole rom again.
Click to expand...
Click to collapse
I thought this Kernel would be great. So you do not recommend me to use it?
I will look up the roms now and the kernel they use.
ashyx said:
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
Click to expand...
Click to collapse
How do I do this or if already up to date where do I can look it up?

According to your post you flashed rom, gapps and kernel in one go.
Any one of those could have caused a bootloop or hang.
As for SkyHigh kernel, it is a great kernel but probably not suitable for an aosp rom as it's built from stock sources intended for stock roms.
Use the kernel provided.
To update the bootloader flash the latest firmware or pull it out and flash it separately.

Okay I will do the following now.
First find the appropiate Kernel if Skyhigh is a nogo. sadly.
Then flash in recovery at first the kernel of the rom. boot. recovery, flash the customrom + gapps. Right?
And before all that flash a new bootloader.
Further, is there a Kernel beside the one of the roms that you would recommend me?

Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.

ashyx said:
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
Click to expand...
Click to collapse
Okay worked well.
Left out the kernel because I could not find any custom ones.
Now I have euphoria on it and want to change between blisspop and liquidsmooth until I have the one I like most.
It is kinda hard to get the difference. I just know that euphoria and liquid are faster, smoother?
Thanks a lot without your input I would still be searching for an answer.
Happy day to you.

skyhigh and iron kernel are mean for touchwiz. Its not mean for cyanogen/aosp/aokp.
currently there is no one cook a custom kernel for cyanogen/aosp/aokp rom. so we stuck with the kernel that come with the rom.

Kernels :
https://www.androidfilehost.com/?w=files&flid=37193

Okay, did not know about this kernel.could you give me some info about the "deathly signed"?
My browser here is not loading the xda thread where I found people talking about it.