Updates while on custom kernel? - ONE Q&A, Help & Troubleshooting

Ok, so I'm no stranger to modding and XDA but every phone I've always had I always flashed custom Roms immediately so I'm not sure how it works on stocks. I'm rooted with unlocked bootloader on the stock ROM with Franco's kernel. Can I install system updates or is it best to do that on stock kernel and does being rooted with unlocked boot loader affect it? Thanks for any help.
Sent from my One using xda premium

The OTA should contain the stock kernel, so you would just need to flash the custom one afterwards. I'm not 100% sure, but I don't see why it should be different from what I said...

bradipovsky said:
The OTA should contain the stock kernel, so you would just need to flash the custom one afterwards. I'm not 100% sure, but I don't see why it should be different from what I said...
Click to expand...
Click to collapse
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium

C-4Nati said:
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium
Click to expand...
Click to collapse
Sorry, I wasn't clear: most likely the OTA itself contains the stock kernel, therefore it installs it instead of whatever you already have. After the OTA you should just have to (re-)flash your custom one back and be good to go.

C-4Nati said:
I'm on a custom kernel now, wasn't sure if I can do an ota on a custom kernel or not.
Sent from my One using xda premium
Click to expand...
Click to collapse
worse case scenario you can flash an update zip but like previously mentioned the kernel is not what generally causes the issue but the recovery. I do not think you will have an issue but hey there are some nice custom roms out there with options give one a shot. Just nandroid you current setup
Remember custom roms are running 4.4.4

playya said:
worse case scenario you can flash an update zip but like previously mentioned the kernel is not what generally causes the issue but the recovery. I do not think you will have an issue but hey there are some nice custom roms out there with options give one a shot. Just nandroid you current setup
Remember custom roms are running 4.4.4
Click to expand...
Click to collapse
Yeah I know, I always use custom Roms cause I generally have phones that have some OEM ui plastered on so since this is already close to stock I'm going to ride it out and see how CM does updating for a bit. Especially since they promised L within 3 months after it's release.
Sent from my One using xda premium

C-4Nati said:
Yeah I know, I always use custom Roms cause I generally have phones that have some OEM ui plastered on so since this is already close to stock I'm going to ride it out and see how CM does updating for a bit. Especially since they promised L within 3 months after it's release.
Sent from my One using xda premium
Click to expand...
Click to collapse
I hear ya but they working on a Android L rom in development now just so you know... I ran the version for my N4 and it is a lovely OS :good:

Related

[CMW] Rom may flash stock recovery on boot. Fix?

Im using CMW Recovery 6.0.1.0, when I install a rom and reboot I get this message, "Rom may flash stock recovery on boot. Fix?" I said yes... Does saying yes or no make a difference?
OCD madness.
I was assuming that I don't want the stock kernel with my cm10 so I said no.
Sent from my SCH-I535 using xda premium
Can someone give me an in dept answer?
ForeverSupra said:
Can someone give me an in dept answer?
Click to expand...
Click to collapse
I would like to know also. I still have the stock rom, just rooted and was going to get ready for a new rom when I saw this.
dTardis said:
I would like to know also. I still have the stock rom, just rooted and was going to get ready for a new rom when I saw this.
Click to expand...
Click to collapse
This is an outdated thread from before the bootloader was unlocked. Basically, disregard what they are implying because the way flashing roms used to work is "different" than how it is now. Our bootloader was unlocked on August 15th, since that date, when you flash a rom the kernel is flashed as well. It's my understanding that this was not the case when our bootloader was locked prior to August 15th, only a rom was flashed not a kernel. The kernel remained the same throughout all the roms, it was the touchwiz stock kernel. As I said already, this is no longer the case.
Ignore this thread and read DroidStyle's guide in the Development Section if you have any questions regarding the flashing roms process. Also, backup your IMEI.
Sent from my SCH-I535 using xda app-developers app
^what he said!
and to the op, Forever LS1
loveubuntu said:
I was assuming that I don't want the stock kernel with my cm10 so I said no.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
the recovery is not the kernel
say yes
The question has no relevance when running a custom rom. It's there for reverting back to stock on a stock rom/returning original recovery.
Saying yes or no has zero impact unless your on stock rom.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises

Unlocked bootloader

So if i unlock my bootloader will i be able to take the JB OTA when it arrives? If not how do i restore the locked bootloader? Also what if my phone has issues.. Would vzw notice i have this?
Sorry if these r dumb questions. I am not 100% on unlocking it.
Sent from my SCH-I535 using Tapatalk 2
Adam outler specifically stated to not do any ota's after unlocking the bootloader...besides the devs will bring us updates faster than ota anyways. Im not 100% but Adam has a stock bootloader.tar posted in the op of his thread. I believe you would flash that in the bootloader function of odin and that will relock your bootloader...now I am not 100% on this, hopefully others will confirm!
The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.
So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
manaox2 said:
The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.
Click to expand...
Click to collapse
llama555 said:
So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I love you
Sent from my SCH-I535 using xda app-developers app
Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?
llama555 said:
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?
Click to expand...
Click to collapse
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand. I tried finding the original thread i read that on but came up short so if I'm wrong someone please correct me as I don't want to spread false information).
And honestly I'm sure almost every rom will be updated within 24 hours to reflect this if not sooner and development will be full steam ahead! Just beware of an OTA cause you know Verizon is not gonna be happy we broke out of their sphere of influence. You can prolly guarantee this "issue" will be towards the top of their to-do list.
Sent from my SCH-I535 using xda app-developers app
Otas cannot be forced though right?
We always have to accept it on our end correct?
asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
That's not always the case anymore. I've noticed Rezound users have been forced OTA's (update installs without your explicit approval) which means we very well could see the same as well.
Sent from my SCH-I535 using xda app-developers app
asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
Phew good, I'm on Synergy, I think they've blocked OTAs
Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
even if you unlock the bootloader and are worried about OTA's just install clockwork mod or team win. the custom recovery will stop the installation of the files. last line of defense as some phones will download and OTA and install it regardless of what you do (rezound, thunderbolt, etc)
droidstyle said:
besides the devs will bring us updates faster than ota anyways.
Click to expand...
Click to collapse
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
llama555 said:
Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
drbobmd said:
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand.
Click to expand...
Click to collapse
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.
SFniner415 said:
I love you
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Off topic, sorry, but GO NINERS!!!
Sent from my SCH-I535 using Tapatalk 2
lazarus2405 said:
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.
Click to expand...
Click to collapse
Good to know thank you
Sent from my SCH-I535 using xda app-developers app
so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium
Hulk0069 said:
so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My best guess would be to find out what files are responsible for it and see if they are safe to remove via root explorer or something.
Sent from my SCH-I535 using xda premium
Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
The OTA's also fail once they boot into recovery if the stock recovery isn't there. So it's not likely you'll get a forced OTA that works.

Brand New Warranty replacement S3 4.3 - Am I screwed?

So my last s3 stopped working and I got a new one sent via my extended warranty. Previously I had an unlocked bootloader and root running gummy 4.4 which was awesome! My new phone came stock with 4.3 touchwiz which I am reading might be bad news. So here are my questions:
1) Is there really no way to unlock the bootloader on 4.3?
2) What are my alternatives to installing custom roms?
3) Is safestrap a stable/safe option even though its in beta?
4) Can safestrap be reversed if a method for unlocking the bootloader is revealed?
5) Where can I find a rooting tutorial for 4.3? Can I lose root easily/ corrupt my phone if a Samsung update is applied?
6) Should I wait for a downgrade option? Slash is it supposedly possible (twitter update)?
jl2222 said:
So my last s3 stopped working and I got a new one sent via my extended warranty. Previously I had an unlocked bootloader and root running gummy 4.4 which was awesome! My new phone came stock with 4.3 touchwiz which I am reading might be bad news. So here are my questions:
1) Is there really no way to unlock the bootloader on 4.3?
Click to expand...
Click to collapse
Nope.
2) What are my alternatives to installing custom roms?
Click to expand...
Click to collapse
As of this minute, one option: Saferoot then Safestrap.
3) Is safestrap a stable/safe option even though its in beta?
Click to expand...
Click to collapse
Yup. Read the replies in Safestrap if you need reassurance.
4) Can safestrap be reversed if a method for unlocking the bootloader is revealed?
Click to expand...
Click to collapse
Yup, you could even Odin flash VRUCML1 4.3 tar and be back to "normal" again. However, don't count on the 4.3 bootloader being unlocked. There's no guarantee anyone is even utilizing their time to find an exploit and its entirely possible no one is.
5) Where can I find a rooting tutorial for 4.3? Can I lose root easily/ corrupt my phone if a Samsung update is applied?
Click to expand...
Click to collapse
Read me. Use Saferoot, then SafeStrap. Yes, much worse could happen in a future update as well.
6) Should I wait for a downgrade option? Slash is it supposedly possible (twitter update)?
Click to expand...
Click to collapse
That's your call. It's possible, but whether it comes to fruition is entirely different.
Will xposed module work using safestrap safe ROM? Gotta get my greenify experimental features back! And keep chat!
Sent from my SCH-I535 using xda app-developers app
jl2222 said:
Will xposed module work using safestrap safe ROM? Gotta get my greenify experimental features back! And keep chat!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
They should
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They should
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
omair2005 said:
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think flashing a custom kernel isn't suggested with SafeStrap. I don't know the specifics, maybe @BadUsername or someone else can expand on that? I thought I read that you are still running the stock kernel even if you flash a custom kernel when using SafeStrap. Someone was discussing this before but it was not explicitly proven they were in fact running the custom kernel.
omair2005 said:
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Good deal! Glad xposed works. How you liking alliance by the way? I'm torn between that and clean rom. I'm actually not the most familiar with TW roms currently. Before this replacement phone I was all ASOP.
Sent from my SCH-I535 using xda app-developers app
jl2222 said:
Good deal! Glad xposed works. How you liking alliance by the way? I'm torn between that and clean rom. I'm actually not the most familiar with TW roms currently. Before this replacement phone I was all ASOP.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've come to the conclusion I want to use my partitions to the full capacity so I'm sticking with stock rom + xposed for any modifications I need..
Yeah same here, I was AOSP for awhile soon as I discovered Quantum Kernels..
omair2005 said:
I've come to the conclusion I want to use my partitions to the full capacity so I'm sticking with stock rom + xposed for any modifications I need..
Yeah same here, I was AOSP for awhile soon as I discovered Quantum Kernels..
Click to expand...
Click to collapse
Quantum Kernels huh. Not familiar with those kernels. Ill have to check them out. I would use the stock rom as well Im just worried about a random automatic update that would kill root and make my replacement phone even more useless than it already is without an unlocked bootloader. Do you know if there a way to disable the Samsung update center on the stock rom using root?
jl2222 said:
Quantum Kernels huh. Not familiar with those kernels. Ill have to check them out. I would use the stock rom as well Im just worried about a random automatic update that would kill root and make my replacement phone even more useless than it already is without an unlocked bootloader. Do you know if there a way to disable the Samsung update center on the stock rom using root?
Click to expand...
Click to collapse
Use TiBu and freeze SDM, FWupgrade

Custom Recovery for Kitkat

I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800
sropedia said:
I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800
Click to expand...
Click to collapse
AutoRec the only ting to keep in mind is that if you are going to flash an aosp/4.2 rom you also got to flash a kk baseband ported for aosp or the jb baseband
Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800
sropedia said:
Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800
Click to expand...
Click to collapse
No the patches for some roms are because they support multiple devices and the patches are usually modified kernels to boot the different devices the baseband is for touch/gps/radio/rotation/etc there is a the w ad which has most of the jellybean basebands and cloudy has the stock kk basebands in most of his roms thread
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Benefits of flashing stock 4.4.4 rom

Hello,
I am currently running SlimKat stable build 7 with elemental x. My nexus 5 has been unlocked, rooted and been running custom roms since 4.4.1. I have flashed the 4.4.4. Radio recently and it's been working good.
Will i benefit from flashing a stock Rom apart from the Radio?? Will flashing stock fix any bugs I might have even though I'v e been running SlimKat with no problems at all.
Thanks.
Sent from my LG-D800 using XDA Free mobile app
Mojar7070 said:
Hello,
I am currently running SlimKat stable build 7 with elemental x. My nexus 5 has been unlocked, rooted and been running custom roms since 4.4.1. I have flashed the 4.4.4. Radio recently and it's been working good.
Will i benefit from flashing a stock Rom apart from the Radio?? Will flashing stock fix any bugs I might have even though I'v e been running SlimKat with no problems at all.
Thanks.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
If slimkat is running without problems why flash stock?
The old saying don't fix what isn't broken:good:
Mojar7070 said:
Hello,
I am currently running SlimKat stable build 7 with elemental x. My nexus 5 has been unlocked, rooted and been running custom roms since 4.4.1. I have flashed the 4.4.4. Radio recently and it's been working good.
Will i benefit from flashing a stock Rom apart from the Radio?? Will flashing stock fix any bugs I might have even though I'v e been running SlimKat with no problems at all.
Thanks.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I must admit I simply don't understand what you're getting at here. You say Slimkat is running good, why change it? If you go to stock you'll lose features. Most ROMs are about as stable as stock by now anyways.
and radios and roms are completely unrelated. you can flash whatever custom rom, none of them include radios. radios are a separate flash.
Very true. SlimKat at has been really stable for me. Its more of planning for the next Android OS release. Maybe something I'm not seeing or experiencing but might cause problems later on.
Thanks.
Sent from my LG-D800 using XDA Free mobile app
simms22 said:
and radios and roms are completely unrelated. you can flash whatever custom rom, none of them include radios. radios are a separate flash.
Click to expand...
Click to collapse
This is my point exactly, even though I flashed the radio, it doesn't apply to the Rom and it's features.
Sent from my LG-D800 using XDA Free mobile app
TheLastSidekick said:
I must admit I simply don't understand what you're getting at here. You say Slimkat is running good, why change it? If you go to stock you'll lose features. Most ROMs are about as stable as stock by now anyways.
Click to expand...
Click to collapse
I understand I'll lose the features, but maybe there are certain "codes" that the stock Rom has and custom does not.
You are right though, most custom roms are very stable already.
Sent from my LG-D800 using XDA Free mobile app
Mojar7070 said:
I understand I'll lose the features, but maybe there are certain "codes" that the stock Rom has and custom does not.
You are right though, most custom roms are very stable already.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know, there's no good reason to return to stock. People still on stock generally have had problems in the past with other ROMs and prefer the guaranteed stability of stock. I know Franco one of our kernel developers uses stock with his kernels and his reason given was because it's the only ROM that can support everyone the way he intended and guarantees it works properly.
Mojar7070 said:
I understand I'll lose the features, but maybe there are certain "codes" that the stock Rom has and custom does not.
Click to expand...
Click to collapse
If you don't know what these "codes" are or how they affect your experience then they should be irrelevant to you.
Wakamatsu said:
If you don't know what these "codes" are or how they affect your experience then they should be irrelevant to you.
Click to expand...
Click to collapse
Sounds like a plan. Thanks.
Sent from my LG-D800 using XDA Free mobile app
TheLastSidekick said:
As far as I know, there's no good reason to return to stock. People still on stock generally have had problems in the past with other ROMs and prefer the guaranteed stability of stock.
Click to expand...
Click to collapse
This is why I am on stock. Seems like everytime I go with a custom ROM I eventually end up getting annoying system UI FCs. Very rarely ever get it on stock. Would love to ask what ROMs are the most stable so I can experiment, but alas that's not allowed so I'll stick with stock, but rooted.
scottharris4 said:
This is why I am on stock. Seems like everytime I go with a custom ROM I eventually end up getting annoying system UI FCs. Very rarely ever get it on stock.
Click to expand...
Click to collapse
I too experienced this. Until I discovered Rastakat and for some reason, never had any weird problems after that.
TheLastSidekick said:
I too experienced this. Until I discovered Rastakat and for some reason, never had any weird problems after that.
Click to expand...
Click to collapse
What is Rastakat?
scottharris4 said:
What is Rastakat?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541185
[ROM] RASTAKAT [Android 4.4.4_r1 KTU84P] [PRODUCT_DEVICE := hammerhead] + Vanilla
sent from my "Purified" Hammerhead
scottharris4 said:
What is Rastakat?
Click to expand...
Click to collapse
A custom ROM in Original Development.
TheLastSidekick said:
I too experienced this. Until I discovered Rastakat and for some reason, never had any weird problems after that.
Click to expand...
Click to collapse
Never had one that wasn't my own doing.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Never had one that wasn't my own doing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I mean it very well could be my own doing, but the same things I generally did on other ROMs that produced some errors didn't on Rastakat. I guess everyone finds their true ROM in the end, lol.
TheLastSidekick said:
I mean it very well could be my own doing, but the same things I generally did on other ROMs that produced some errors didn't on Rastakat. I guess everyone finds their true ROM in the end, lol.
Click to expand...
Click to collapse
I'm not familiar with Rastakat, so how is their history with ROM development? I ask because I don't want to flash it and then before long they just stop official development (like what happened with CyanogenMod on my Moto G).
scottharris4 said:
I'm not familiar with Rastakat, so how is their history with ROM development? I ask because I don't want to flash it and then before long they just stop official development (like what happened with CyanogenMod on my Moto G).
Click to expand...
Click to collapse
I guess the only way to describe is to see for yourself. Go check out the thread. All of the users there constantly help each other.
TheLastSidekick said:
I guess the only way to describe is to see for yourself. Go check out the thread. All of the users there constantly help each other.
Click to expand...
Click to collapse
hi i am new to nexus 5 , just wanted to know what is the build date on the offical stock kernel 4.4.4.,mine is mon-mar- 17/ 15.16.36 PDT 2014, could you please tell me if i am on the right version build date , regards joe,

Categories

Resources