Hello. I searched the forum but didn't really find an answer.
I was until 5 minutes ago with the MIUI rom. I know the last kernel I flashed was the cyanogenmod kernel (which I used with another rom...can't remember which one because I flashed 5 roms in 1 day).
I wanted today to abandon MIUI because I was having problems with the display timeout...and some other things, compatibility with applications and details were not really good for me.
So I flashed now the rcmixhd, downloaded from rom manager. What kernel should I use?
And....is a kernel independent from the rom? Will a rom not work with the proper kernel?
*deep breath*
By going through the kernel threads, reading about them, seeing what others say then choosing a few to try, add them, try them, make a decision, keep one.
Just like your radio question and your ROM question it comes down to two things:
1. Your particular hardware capabilities - Some devices like some kernels better than others.
2. What YOU want from the kernel and how much YOU think it's the best one for YOUR situation / wants / needs etc.
Only YOU can decide what one YOU like the most subject to them working ok with your particular handset (this is particularly true for overclocking).
As a rule of thumb, if you're not fussed about over-clocking or BFS vs CFS etc. then what ever kernel the ROM creator advises.
Now please, pretty please, use the link in my sig to find more in depth answers as this question has been asked too many times already.
You don't pick the kernel, the kernel picks you.
Ok people a slight helpful guide here, may have already been created but its here regardless
This will also be posted in Q&A under answers just to help people out
So in the Q&A forum i have seen a lot of the same question, my X10 is stuck at boot, which yeah happens but it seems to be for the same reason due to kernel or mod damage so what can you do?
i will also answer from experience on other questions
No1. READ the requirements...
These are the requirements for the ROM i use (DiXperia7 Avenger from DikeJ), (They generally follow same lines but dont suspect they do.)
OS - Android 2.3 or 2.1 (from upgrade from 2.1 to 2.3 wipe will be needed)
Permissions - Root Access, Busy Box, Xrecovery (Kernels for Stock roms not CM series)
Optional - Unlocked bootloader running DoomKernel v6 or above. Seeing as this seems to be final edition from the great doomlord we shal settle there.
So as you can see some simple requirements laid out nicely, bootloops and boot freezes can normally relate to Kernels installed, if theres a problem it wont install or freeze anyways but normally a ROM freeze is picked up before its released.
On locked bootloaders you wont have this problem as long as the ROM supports this. The dev will normally tell you what you need if not ask.
No2. ASK!
of course i am trying to help less skilled people, like me, avoid bootloops and crashes. so always as on the dev forum and wait for a reply, chances are its been tested but if your unsure dont do it until you know 100% and a dev or someone with experience has tested personally.
No3. Make sure your using the correct recovery.
It works like this.
Stock ROM - Xrecovery (DoomKernel ThKernel)
Cyanogenmod series - Clockwork Recovery mod (In FXP Kernels)
MIUI Series - Can be both but seems mainly Clockwork
championswimmer has done a custom version of both CWM and Stock - http://forum.xda-developers.com/showthread.php?t=1564056 credits go to champ.
So enough about Kernels and blah blah xD lets move onto Wifi Troubles
Wifi runs using the Kernel, Unlocked bootloaders need a patch to run Wifi unless its FXP based.
These files are generally found with the kernel on the forums. Known as wifi modules.
You can flash these patches before 1st boot but its not recommended. needs to be reinstalled every time you flash a rom as there wiped out..
(Please make sure the wifi patch is correct to the kernel as a wrong one will not fix wifi errors)
Random Reboots while phone is on.
Ok i dont know highly on this subject but i do remember reading a little about them..
Random reboots can be caused due to hardware failure, normally motherboard crashes, just restart the phone by removing battery normally works.
Another factor of this is a mod that has been installed. If the mod is not designed for your phone it will normally cause a bootloop at kernel but if it gets pasted this could be a cause of your problems.
SuperUser detection not working :S?
I had this problem, SU was stopping my root programs getting there access, but sometimes the app isnt at fault, its your actual root, simply rerooting fixes this .
Ok people i hope this helps just to help new users out on problems, although as always i wont be held responsible for any damages.
Thanks to..
DoomLord - DoomKernel Series
Champ - Kcernal series
ThJap - ThKernel Series
FXP - for the CMW recovery and there kernels
The Devs who fix, create and keep the X10 going
The Q&A forum for asking and answering questions all day long
XDroidie626 said:
Ok people a slight helpful guide here, may have already been created but its here regardless
This will also be posted in Q&A under answers just to help people out
So in the Q&A forum i have seen a lot of the same question, my X10 is stuck at boot, which yeah happens but it seems to be for the same reason due to kernel or mod damage so what can you do?
i will also answer from experience on other questions
No1. READ the requirements...
These are the requirements for the ROM i use (DiXperia7 Avenger from DikeJ), (They generally follow same lines but dont suspect they do.)
OS - Android 2.3 or 2.1 (from upgrade from 2.1 to 2.3 wipe will be needed)
Permissions - Root Access, Busy Box, Xrecovery (Kernels for Stock roms not CM series)
Optional - Unlocked bootloader running DoomKernel v6 or above. Seeing as this seems to be final edition from the great doomlord we shal settle there.
So as you can see some simple requirements laid out nicely, bootloops and boot freezes can normally relate to Kernels installed, if theres a problem it wont install or freeze anyways but normally a ROM freeze is picked up before its released.
On locked bootloaders you wont have this problem as long as the ROM supports this. The dev will normally tell you what you need if not ask.
No2. ASK!
of course i am trying to help less skilled people, like me, avoid bootloops and crashes. so always as on the dev forum and wait for a reply, chances are its been tested but if your unsure dont do it until you know 100% and a dev or someone with experience has tested personally.
No3. Make sure your using the correct recovery.
It works like this.
Stock ROM - Xrecovery (DoomKernel ThKernel)
Cyanogenmod series - Clockwork Recovery mod (In FXP Kernels)
MIUI Series - Can be both but seems mainly Clockwork
championswimmer has done a custom version of both CWM and Stock - http://forum.xda-developers.com/showthread.php?t=1564056 credits go to champ.
So enough about Kernels and blah blah xD lets move onto Wifi Troubles
Wifi runs using the Kernel, Unlocked bootloaders need a patch to run Wifi unless its FXP based.
These files are generally found with the kernel on the forums. Known as wifi modules.
You can flash these patches before 1st boot but its not recommended. needs to be reinstalled every time you flash a rom as there wiped out..
(Please make sure the wifi patch is correct to the kernel as a wrong one will not fix wifi errors)
Random Reboots while phone is on.
Ok i dont know highly on this subject but i do remember reading a little about them..
Random reboots can be caused due to hardware failure, normally motherboard crashes, just restart the phone by removing battery normally works.
Another factor of this is a mod that has been installed. If the mod is not designed for your phone it will normally cause a bootloop at kernel but if it gets pasted this could be a cause of your problems.
SuperUser detection not working :S?
I had this problem, SU was stopping my root programs getting there access, but sometimes the app isnt at fault, its your actual root, simply rerooting fixes this .
Ok people i hope this helps just to help new users out on problems, although as always i wont be held responsible for any damages.
Thanks to..
DoomLord - DoomKernel Series
Champ - Kcernal series
ThJap - ThKernel Series
FXP - for the CMW recovery and there kernels
The Devs who fix, create and keep the X10 going
The Q&A forum for asking and answering questions all day long
Click to expand...
Click to collapse
Nice post!
Hello,
I recently rooted my Galaxy Y and installed CyanogenMod 7.2. After spending time trying to get Google Play to function (I have tried different things and searched on here) but being unable to I decided to try another ROM.
It seems very hard however to get straightforward and comprehensive details on here for anything i.e. whether a different kernel is required, what the installation procedure is in terms of wiping and mounting things. There seems to be a lot of assumed knowledge when things are posted.
So, can someone please recommend a ROM or ROMS with links to precise instructions on installation. I'm looking for something stable, quick, clean and customisable. Things that sound like they might suit are AOSP, EVO and Oxygen.
Thanks in advance.
Hello! This will be a quick post about how it was good earlier and how it can be better today, so please, stay with me.
I've been using Sony's for a while now, starting with small and cute Sony Ericsson k510i, then k550i, then wt19i (LWW), and then Xperia SP. My "flashing career" started after I've lost warranty on my k510. At that time there wasn't a lot you can do to your phone - there were several official firmwares, various customization options, and a lot of custom patches. No competition, one latest official firmware, a big library of patches that you could port to your device, if someone didn't do it already. The only competing area were a lot of graphical patches, but you could compile them together on your phone. Like today, if you were doing something wrong with your phone - you'll get a brick and it's your fault. But for every device there was an instruction, a beautifully crafted instruction on what to do and how to do everything, step by step. Almost every thread included a complete set of links to get you started. If you needed to flash a customisation after installing something, there would be a link on how to flash custom right there.
Today I have my XSP and try to do something to it. So I open one link (non-sticky, needed to bookmark it), see a lot of ROMs, part of which are no longer maintained. Finally open one of them based on performance rating, and see that it needs some kernel. So I go to kernel list, and see that it can't be flashed without recovery. What recovery? One specific recovery, because another one can't flash it. Now how do I flash recovery in the first place? I need a manual for that. Now I go to kernel and ROM page and see that no manual is available for them, too. So I open main device page and don't see any manual, so I open a sticky thread. And guess what? I don't see manual there. And that's when I start a new thread, type my problem in, and see a non-sticky thread with last post made 2nd of May 2015, and no pages link to that thread at all.
Is that how it goes this days? A newbie comes in, spends whole evening, opens 10 tabs, and still can't find anything relevant? I think we need to do something with this, revisit old threads, compile a new one-for-all guide, or at least a list of guides. And stick it, so people can actually see it. Otherwise there will be small closed community of those who already can develop and flash, and all the others who either got brick or is afraid to get a brick. Thanks.
---
UPD: And then I see that the kernel which I almost decided to flash is closed and all developers migrated to another one. I'm talking about tangerine and helium. Again, no info in the first post. And main developer openly says to users of his work - if it didn't work for you, don't use it. What's wrong with you people...
I'm deeply sorry if I offended somebody with my previous post. I'm happy that you guys do such amazing things with this 3 year phone. But damn, FULL INSTALLATION took about 10 minutes, counting PC reboot into linuxes to get fastboot working. In case someone struggles like me, use CyanogenMod instruction to get to Cyanogen Recovery; download TWRP Recovery, ROM of choice and GApps of choice; place all three ZIPs onto your sdcard; go to recovery, flash TWRP, reboot into TWRP (by pressing volume rockers while loading), do Wipe - Factory Wipe, flash ROM, flash GApps, reboot to normal. Wait for about 5 minutes (black screen is normal, there will be dots flying after a minute or so to keep you entertained).
Yes, It's that simple nowadays, so why bothering typing so much? I was in that situation with my SP, too, but if the are so many answers to these questions and so many threads... "You have to read" is the answer! A lot! It's for your own good, trust me. Now I can do anything I want with my phone with nohow! So a little reading and searching here and there is just positive experience for you. Don't complain, the people here ( well a part of them) are hardcore coders or themers or whatever. You can't just ask them to tell you all the stuff. If want help I'm always available.
Thank you for linking to my very dusty and lonely Flash ROM guide hahaha
No you didn't offend anyone at all. The guides are actually there, like how to use Flashtool, how to unlock bootloader, how to flash recovery and everything, it is just that they are buried deep with time as the development goes. The thread are there, in the General section and are awaiting to be searched. Though some are outdated, some are not and you can benefit from there.
Some searching will normally do, but if it didn't, just ask in the threads, someone will probably answer to you!
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
About recovery, PhilZ and CWM is way outdated, and its time for everyone to make TWRP as a standard as it is a still updated recovery. Cyanogen Recovery in my opinion is crap as there are far too less feature plus, it enforce on signed flashable zips.
About the thread on Tangerine, the developer said dont use if it doesn't work is because of the norm of the Kernel. The kernel is made by using an AnyKernel template, hence render support for almost all Lollipop ROMs. Since ROMs can be updated and all ROMs have different sources, a simple change in the system part can render Tangerine unsupported, and the developer cannot do anything (definitely his choice, please respect that) to only fix the problem on one ROM which could possibly break support for the majority of the ROMs! This also appplies to Helium. Therefore, his words of "dont user it if it doesn't work" has a meaning, and it is not something to degrade new users and so.
kojata said:
If want help I'm always available.
Click to expand...
Click to collapse
TechnoSparks said:
I always have my eyes on the General and Q&A subforums of the Xperia SP, and I will usually respond to a help-able problems. So if you have any problems, feel free to post in the Q&A subforum, and if not me, someone will help you. If there are nobody, don't feel offended. Maybe people don't know what to help or suggest (but lets just hope that is not what it will be )
Click to expand...
Click to collapse
Thanks for the answers and offering help, happily I was able to install my ROM of choice and it still works flawlessly, I was even able to squeeze 20 battery days from my old XSP.
Thinking about it, I start to understand why that dev answered like that. I was a python dev in the past and know how one feature can kill two others. Just in my head there is one current linux kernel, and all things that are developed should work with that particular kernel. Kernel comes before OS, if you will. Isn't it the case with ROMs and droid kernels?
About TWRP and reading: I honestly did read a lot of info before doing something, because it's my only phone these days. But it's so hard to find information on whether something is deprecated or not. As a new user, you wouldn't just google "is this deprecated and no longer used?", because that search will not provide any info. That is why during that evening and following morning I lost count of how many times I just shaked my head asking which recovery/kernel should I use and how do I install it? Latest being the easy one, because I already found TechnoSparks thread by that time.
In case anybody is interested, I installed Candy 5 on default kernel. But I still don't know if installing android 5 on a kernel used with android 4.2 was a good idea. It went well, however.
//
One see multiple identical questions .
Two their is no best rom nor best battery rom.
You posted 3 roms you read the instructions and threads .
Decide which one you are capable of installing .
Custom roms are not 100% perfect you decide after reading .
<which is stable for everyday use, no big bugs, battery friendly, well optimized, and easy to install.>
Thats called Samsung stock rom .
//
No rom better its user choice .
Repeat install the rom where you understand the instructions first.
Magma is the most current.
But read the OP and FAQS first.