Related
I have some questions regarding the installation of SlimBean ROMs from Stock ROMs:
Upgrading Slim Bean
Unless we specify otherwise in changelog
Reboot to recovery, wipe cache, dalvik cache then just flash your device zip.
From Froyo/GB Rom to SlimBean
Get yourself booted with cm9 or cm10. then follow the steps "From another JB or ICS ROM"
Click to expand...
Click to collapse
1. I'm from GingerBread. Does this refer to the "[NIGHTLY][ROM][4.2.2] CyanogenMod 10.1 for Samsung Captivate" from Android Development?
From another JB or ICS Rom to SlimBean
Download device_x.x.zip, slim_gapps.zip.
Enter CWM, wipe data, format system ( in mounts and storage)
Flash Device_x.x.zip***, then MUST flash slim_gapps.zip (other files optional)
Click to expand...
Click to collapse
2. Assuming I'm from JellyBean Stock ROM, do I have to install cm9 or cm10 as well like the one posted above? Before proceeding to these steps?
From Other Custom ROMs:
Wipe data
Format /system
Flash rom
Reboot
Click to expand...
Click to collapse
3. Do they still require cm9 or cm10 installed as well? Or no need?
GB > CM10 > Slim
Just follow instructions for each step, nothing special or too complicated.
You can use CM10 stable. Get the files + instructions from http://www.cyanogenmod.org/
For Slim files + instructions go to http://www.slimroms.net/
Yes, Slim requires CM10, can't upgrade GB to Slim directly. There is no Jelly Bean stock ROM for Captivate.
If you already have working Jelly Bean custom ROM, then flash Slim directly, no need to go through CM10 again.
Is your GB rooted and with CWM already?
Val D. said:
GB > CM10 > Slim
Just follow instructions for each step, nothing special or too complicated.
You can use CM10 stable. Get the files + instructions from http://www.cyanogenmod.org/
For Slim files + instructions go to http://www.slimroms.net/
Yes, Slim requires CM10, can't upgrade GB to Slim directly. There is no Jelly Bean stock ROM for Captivate.
If you already have working Jelly Bean custom ROM, then flash Slim directly, no need to go through CM10 again.
Is your GB rooted and with CWM already?
Click to expand...
Click to collapse
I suppose you could change out CM10 for a Custom CM10 based rom? That's what I did and it seems to run fine.
x0ne215 said:
I suppose you could change out CM10 for a Custom CM10 based rom? That's what I did and it seems to run fine.
Click to expand...
Click to collapse
Yeah, that works as well. CM10 is just the simpler option as it's more popular/easy to find.
Yes, and CM10 has a stable release, no issues expected with installation.
Val D. said:
GB > CM10 > Slim
Yes, Slim requires CM10, can't upgrade GB to Slim directly. There is no Jelly Bean stock ROM for Captivate.
If you already have working Jelly Bean custom ROM, then flash Slim directly, no need to go through CM10 again.
Click to expand...
Click to collapse
So I can dirty flash Slim 3.0 over cm10 without the factory reset? Just Dalvik and cache? Not the newest Slim for cm10.1...
I never recommend dirty flashing. If you want to move to Slim, then go for the latest 4.2 version. It has many new and improved features.
Thanks for the reply.
Some follow ups:
1. Is it recommended to use CM10 Stable instead of CM10 Nightlies? Does it matter in installing custom roms?
2. Nope. Not yet rooted and without CWM. How to do those for this phone?
3. Is rooting required before installing custom roms from stock? Are all custom roms already rooted?
1. CM10 has stable version (tested), CM10.1 is still in experimental stage (may contain bugs, including installation process). It is my personal preference to use CM10 stable.
2. You may start from here http://forum.xda-developers.com/showthread.php?t=1350266 or here https://docs.google.com/document/d/1YvC_lLbjk06WOttsifG8fD2QUHvC9_rDtZdNrDZKAFc/edit?pli=1, both very good guides.
3. Yes, Root/CWM is required. Yes, custom ROM's are rooted and with CWM. Once you have custom JB ROM installed, switching to another JB based is very easy.
Val D. said:
1. CM10 has stable version (tested), CM10.1 is still in experimental stage (may contain bugs, including installation process). It is my personal preference to use CM10 stable.
2. You may start from here http://forum.xda-developers.com/showthread.php?t=1350266 or here https://docs.google.com/document/d/1YvC_lLbjk06WOttsifG8fD2QUHvC9_rDtZdNrDZKAFc/edit?pli=1, both very good guides.
3. Yes, Root/CWM is required. Yes, custom ROM's are rooted and with CWM. Once you have custom JB ROM installed, switching to another JB based is very easy.
Click to expand...
Click to collapse
Thanks!
x0ne215 said:
I suppose you could change out CM10 for a Custom CM10 based rom? That's what I did and it seems to run fine.
Click to expand...
Click to collapse
BWolf56 said:
Yeah, that works as well. CM10 is just the simpler option as it's more popular/easy to find.
Click to expand...
Click to collapse
Does this mean if I'm from Gingerbread stock and choosing another custom rom besides SlimBean, there's no need of installing CM10 because they are already "Custom CM10 based rom"? So all I have to do from stock GB, is to flash a kernel with CWM to be able to flash the custom rom zip from sd card?
It is always good to flash any rom which is complete in itself
Slim rom is not as its slimmed
Say it can be captivating, hellybean, any cm10
Then flash slim rom
Wiping data is necessary when switching from one rom to another as every rom contains different features
JakeJesper said:
Thanks!
Does this mean if I'm from Gingerbread stock and choosing another custom rom besides SlimBean, there's no need of installing CM10 because they are already "Custom CM10 based rom"? So all I have to do from stock GB, is to flash a kernel with CWM to be able to flash the custom rom zip from sd card?
Click to expand...
Click to collapse
You ALWAYS gotta follow the FULL ROM instructions posted in their OP.
Coming from GB, you'll have to flash the ROM twice. You'll need their respective Gapps.
There are plenty of guides on this, you need to do some reading if you're not sure of what you're doing.
JakeJesper said:
Does this mean if I'm from Gingerbread stock and choosing another custom rom besides SlimBean, there's no need of installing CM10 because they are already "Custom CM10 based rom"? So all I have to do from stock GB, is to flash a kernel with CWM to be able to flash the custom rom zip from sd card?
Click to expand...
Click to collapse
Well, that's what I did. Was on GB 2.3.5, rooted/cwm with tut in my sig, then from that flashed Captivating X5 with no issues (that may have been hellybean based idk I lose track since sepphi switches bases a decent bit). Currently running SlimBean Build 4.2 with no issues (Captivating X5 -> X6 -> SaltyBean Final -> SlimBean 3 - > SlimBean 4 - > SlimBean 4.2 (my cappys life in the past few weeks).
BWolf56 said:
You ALWAYS gotta follow the FULL ROM instructions posted in their OP.
Coming from GB, you'll have to flash the ROM twice. You'll need their respective Gapps.
There are plenty of guides on this, you need to do some reading if you're not sure of what you're doing.
Click to expand...
Click to collapse
What do you mean by flashing the ROM twice? Please explain. I didn't understand that part.
And regarding Gapps, if I'm not wrong, most custom roms have it already included?
If ever it's not installed, will flashing the latest Gapps zip be compatible with this device? No compatibility issues?
JakeJesper said:
What do you mean by flashing the ROM twice? Please explain. I didn't understand that part.
And regarding Gapps, if I'm not wrong, most custom roms have it already included?
If ever it's not installed, will flashing the latest Gapps zip be compatible with this device? No compatibility issues?
Click to expand...
Click to collapse
When coming from something else than JB, you need to repartition, which is what flashing the ROM twice will do; Flash the ROM, get back in recovery and flash it again.
Also, Gapps aren't cooked into JB ROMs. They need to be flashed right after flashing the ROM.
BWolf56 said:
When coming from something else than JB, you need to repartition, which is what flashing the ROM twice will do; Flash the ROM, get back in recovery and flash it again.
Also, Gapps aren't cooked into JB ROMs. They need to be flashed right after flashing the ROM.
Click to expand...
Click to collapse
Thanks for the explanation. I am indeed wrong with Gapps. lol.
Anyways, will flashing the latest Gapps zip be compatible with this device? No compatibility issues?
JakeJesper said:
Thanks for the explanation. I am indeed wrong with Gapps. lol.
Anyways, will flashing the latest Gapps zip be compatible with this device? No compatibility issues?
Click to expand...
Click to collapse
Simply grab the one provided in their OP. If some apps need updating, just do so through the play store.
Correct me if I'm wrong, but aren't the Gapps for Captivating included in the ROM? If not now, were they prior to X5? Don't remember flashing Gapps when I used to run Captivating.
x0ne215 said:
Correct me if I'm wrong, but aren't the Gapps for Captivating included in the ROM? If not now, were they prior to X5? Don't remember flashing Gapps when I used to run Captivating.
Click to expand...
Click to collapse
They could be, I haven't looked at Captivating all too much as I gave my cappy to my little brother before it got released. (I'm actually quite behind on ROM updates for the cappy tbh)
Thanks. I think I could handle it with regards to the Gapps thing.
Lastly, I just wanted to clarify if I'm directly going to a Custom ROM from stock, do I still need to be rooted? Or just CWM installed?
I currently have the JB based SweetRom v7 installed on my Galaxy Note.
Recently it was pointed out to me by a friend that CM based ROMs have a better functionality and are easier to use. Me, never having used a CM based ROM (not even on a friend's phone), am kind of in a dilemma whether or not to switch.
It would be of great help if you could help me out with the Pros and Cons of both JB based and CM based ROMs and if I should give CM a try. Also, a list (If possible) about the features which might not work/are absent from CM based ROMs..
Also, an elaborate guide to switching from JB to CM and a ROM suggestion for a first-time CM user will be very helpful.
Thanks in advance guys.
aurator said:
I currently have the JB based SweetRom v7 installed on my Galaxy Note.
Recently it was pointed out to me by a friend that CM based ROMs have a better functionality and are easier to use. Me, never having used a CM based ROM (not even on a friend's phone), am kind of in a dilemma whether or not to switch.
It would be of great help if you could help me out with the Pros and Cons of both JB based and CM based ROMs and if I should give CM a try. Also, a list (If possible) about the features which might not work/are absent from CM based ROMs..
Also, an elaborate guide to switching from JB to CM and a ROM suggestion for a first-time CM user will be very helpful.
Thanks in advance guys.
Click to expand...
Click to collapse
I'll answer part of your question. If you switch to a CM-based ROM, you won't be able to use S Pen-based apps such as the S Note, as it is tightly integrated into Touchwiz.
4.1.2 JB LT4 Union ROM v7, LT3 Modem, PhilZ LT4 kernel, Carrier: AT&T (US)
Will i not be able to use only the apps or the S-Pen as a whole?
aurator said:
Will i not be able to use only the apps or the S-Pen as a whole?
Click to expand...
Click to collapse
You would not be able to use Samsung applications for S-pen but you can use their alternatives from play store, also FM does not work but you can use Spirit FM, No Wi-Fi Direct but you can use the alternatives from play store.
Edit: Just so that you know, CM based roms are much faster and smother than the TW or stock rom. Also has lot more customisation to it compared to TW. TW also has customization but you will have to apply then or use a customized TW rom.
aurator said:
I currently have the JB based SweetRom v7 installed on my Galaxy Note.
Recently it was pointed out to me by a friend that CM based ROMs have a better functionality and are easier to use. Me, never having used a CM based ROM (not even on a friend's phone), am kind of in a dilemma whether or not to switch.
It would be of great help if you could help me out with the Pros and Cons of both JB based and CM based ROMs and if I should give CM a try. Also, a list (If possible) about the features which might not work/are absent from CM based ROMs..
Also, an elaborate guide to switching from JB to CM and a ROM suggestion for a first-time CM user will be very helpful.
Thanks in advance guys.
Click to expand...
Click to collapse
Yep, as already was said here, the spen apps, and functionality like scrolling, hovering stuff doesn't work.
Not every ROM is the same, so ones can be faster and others slower.
If You would like to have many many options I would recommend You to flash the jellybam ROM. It's slower but greater.
You may also try android 4.3
Okay, So I finally decided to go with JB 4.2.2 SuperNexus ROM.
I'm still confused about how to flash it. I've gone through the procedure and I understand it all but I'm now sure how to Switch from Philz recovery to CWM recovery?
I know this sounds stupid but this is the only thing keeping me from flashing the CM Rom.
Do I flash a CM based kernel to change from Philz recovery to CWM or is there something more?
Help will be greatly appreciated!
As for note the recovery is in the kernel, you will need to flash a cm kernel.
But you could directly flash it using philz recovery. When the rom installs it will install cm kernel and overwrite philz kernel.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
As for note the recovery is in the kernel, you will need to flash a cm kernel.
But you could directly flash it using philz recovery. When the rom installs it will install cm kernel and overwrite philz kernel.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
So I just need to flash the ROM and Gapps through Philz recovery to get it working?
All that head-banging went in vain, I guess -_-
Thanks a ton!
it wont go in vain.. will come handy some day,. there was an issue with Philz recovery not able to install CM/AOSP roms.. (error 7). which was resolved in the latter updates,, if you get the same error ... then flash a CM kernel first and then reboot recovery and flash the rom.
So, right now im on cf-rooted 2.3.6 jvu, I want to install cm11 nightlies and my question is: its possible to install semaphore kernel with it? (this: http://forum.xda-developers.com/showthread.php?t=1786220 ) its intended for kk roms, but are they actually compatible? if affirmative, how I should proceed?
thank in advance
jorgecft said:
So, right now im on cf-rooted 2.3.6 jvu, I want to install cm11 nightlies and my question is: its possible to install semaphore kernel with it? (this: http://forum.xda-developers.com/showthread.php?t=1786220 ) its intended for kk roms, but are they actually compatible? if affirmative, how I should proceed?
thank in advance
Click to expand...
Click to collapse
flashing guide for updating form JVU to KK look here . Like they say climb the ladder one step at time, same goes for updating, so proceed after making backups> ICS> JB> KK
If you look at the link you posted it clearly states, the kernel for KK is version 3.4.0
Semaphore <= 2.6.6 for 4.1.2
Semaphore >= 2.8.0 for 4.2
Semaphore >= 3.1.0 for 4.3
Semaphore >= 3.4.0 for 4.4
Click to expand...
Click to collapse
for flashing kernels you can do it with Odin for .tar files and CWM recovery for .zip files.
Check this out! Links to useful Guides and " Banned " Documentaries
Oh yeah I know how to install cm11, just via CWM and this stuff, but, when I'm already on cm11, i just reboot into recovery and flash the kernel .zip? Or is anything else required (wipes, etc)?
thx
jorgecft said:
Oh yeah I know how to install cm11, just via CWM and this stuff, but, when I'm already on cm11, i just reboot into recovery and flash the kernel .zip? Or is anything else required (wipes, etc)?
thx
Click to expand...
Click to collapse
just flash the kernel without wipes and enjoy!!!
I always flash the kernel on my ROM without wipes
I flash new kernel and after my phone don´t start, don´t start cwm, work only downloading.....PLEASE HELP ME !
What kernel?
Powered by CM11
jurinecko said:
I flash new kernel and after my phone don´t start, don´t start cwm, work only downloading.....PLEASE HELP ME !
Click to expand...
Click to collapse
Flash stock firmware with Odin.
I think that you installed CM kernel, maybe that Aroma installer for CM kernels on JB. CM kernel does not work on JB or GB, JB kernel do not work on CM or GB, GB kernel do not work on CM or JB. Also do not use CM10.1/2 kernel on CM11 or any combination, use kernel on ROM version that kernel is made for.
Hey,
Whenever I try to flash another kernel which is required to flash a new rom to my SP, everything works just fine. Except that when I finish the flashing and boot up to the ROM, the screen seems to flicker a lot...
I tried turning auto brightness off, flashing another compatible kernel, and flashing a couple of scripts that claimed to fix the issue...
I am currently at the stock firmware, rooted and with unlocked bootloader.
What is weird is, when I flash the stock 12.1.A.1.205 firmware back...the screen stops flickering.
Any ideas?
Thanks in advance
LoizosAristides said:
Hey,
Whenever I try to flash another kernel which is required to flash a new rom to my SP, everything works just fine. Except that when I finish the flashing and boot up to the ROM, the screen seems to flicker a lot...
I tried turning auto brightness off, flashing another compatible kernel, and flashing a couple of scripts that claimed to fix the issue...
I am currently at the stock firmware, rooted and with unlocked bootloader.
What is weird is, when I flash the stock 12.1.A.1.205 firmware back...the screen stops flickering.
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
it is bug cm11 kernel. (cm kernel based 12.1.A.0.266 kernel …=> flickeris bug
win32r said:
it is bug cm11 kernel. (cm kernel based 12.1.A.0.266 kernel …=> flickeris bug
Click to expand...
Click to collapse
It's not only the cm11 kernel, other kernels like DooMLoRD kernel, which is based on the stock fw also has this problem..
Are you saying that I use a lower firmware kernel on a newer firmware?
LoizosAristides said:
It's not only the cm11 kernel, other kernels like DooMLoRD kernel, which is based on the stock fw also has this problem..
Are you saying that I use a lower firmware kernel on a newer firmware?
Click to expand...
Click to collapse
DooMLoRD kernel based 12.1.A.0.266.
I advise you use cm11 for LBL + wiliams kernel v7.. => no flickeris bug
win32r said:
DooMLoRD kernel based 12.1.A.0.266.
I advise you use cm11 for LBL + wiliams kernel v7.. => no flickeris bug
Click to expand...
Click to collapse
Oh I didn't know that it's based on the .266
Thanks man, I hope Williams kernel works
win32r said:
DooMLoRD kernel based 12.1.A.0.266.
I advise you use cm11 for LBL + wiliams kernel v7.. => no flickeris bug
Click to expand...
Click to collapse
Ok so I should've mentioned that my bl is unlocked...
Also, williams kernel v7 is for 4.3...
I'm trying to flash cm11, for cm11 there's williams kernel v4...
I tried both the stock cm11 kernel and williams one and they both gave me flickering screen...
Any other ideas?
LoizosAristides said:
Any other ideas?
Click to expand...
Click to collapse
add to build.prop this lines:
Code:
# System property for cabl
ro.qualcomm.cabl=0
win32r said:
add to build.prop this lines:
Code:
# System property for cabl
ro.qualcomm.cabl=0
Click to expand...
Click to collapse
Can you tell me what does it do?
LoizosAristides said:
Can you tell me what does it do?
Click to expand...
Click to collapse
It is fix flikers bug! :laugh:
win32r said:
It is fix flikers bug! :laugh:
Click to expand...
Click to collapse
Hmm I'll try it tomorrow
Thanks for helping me dude...
Forget it)
win32r said:
Forget it)
Click to expand...
Click to collapse
Ok so I tested it out today...and it doesn't work
I am now convinced that it's a kernel problem, since I tried a lot of different versions of cm11, but I also used 4 different kernels, each one at the latest version, NOTHING!
Any other ideas?
LoizosAristides said:
Any other ideas?
Click to expand...
Click to collapse
Hm... I don't know..=( sorry
I tried to write in support of the CM. But the answer is no.
win32r said:
Hm... I don't know..=( sorry
I tried to write in support of the CM. But the answer is no.
Click to expand...
Click to collapse
That's ok...
Thanks for your time anyway
As win32r said, you should try a cm11 based ROM but for locked bootloader (they work for ubl too). With these roms you can use a kernel based on stock ( for example stock kernel or Williams kernel Sony version) which should fix your issue.
All roms that are for LBL will work with the stock kernel or Williams kernel v7. I wrote something about this in the Williams kernel website : http://williams-kernel.tk/help.php and I'll probably write this info on xda too if I have some time.
Wow. Apparently, your kernel is the only one that that doesn't give me a flickering screen
I tried an unofficial cm11 build along with it and it worked like a charm!
I just can't thank you both enough...
Finally I got a fully working cm11 on my SP