[KERNEL][STOCK][T][JB 4.3] 9.2.A.1.199 - flashable - Sony Xperia T, TL, TX, V

Stock kernel for the Xperia T 9.2.A.1.199 4.3 firmware!
This can be flashed via CWM, this means an update is possible without flashtool! This is to go in conjunction with any .199 firmware, it will also work on .295 firmware, since they are both JB 4.3
Confirmed working, thanks @nreuge
This isn't really development but a stock kernel and it's probably best placed here for people to find!
Download: http://d-h.st/i2u

Thanks bro.will this kill root?

josephnero said:
Thanks bro.will this kill root?
Click to expand...
Click to collapse
It doesn't

As it says in the OP, I haven't tested this since my T is under repair, it's had nearly 50 downloads so I'm going to assume this is working...?

matt4321 said:
As it says in the OP, I haven't tested this since my T is under repair, it's had nearly 50 downloads so I'm going to assume this is working...?
Click to expand...
Click to collapse
Working perfectly, thanks!

nreuge said:
Working perfectly, thanks!
Click to expand...
Click to collapse
Thanks mate

does this have cwm integrated? if not, can i install philz touch 1.7 (showthread.php?t=2657190)?
EDIT: yes you can. works without problems so far. i'll have to test rom manager backups, though.

bamdadkhan said:
does this have cwm integrated? if not, can i install philz touch 1.7 (showthread.php?t=2657190)?
EDIT: yes you can. works without problems so far. i'll have to test rom manager backups, though.
Click to expand...
Click to collapse
No this doesn't have integrated CWM, since it's for locked bootloaders so needs to be stock and signed which it is.
If you want PhilZ recovery for locked bootloaders you must root first on 4.1.2, upgrade to 4.3 by flashing a deodexed rooted version, plus kernel, plus the recovery

matt4321 said:
No this doesn't have integrated CWM, since it's for locked bootloaders so needs to be stock and signed which it is.
If you want PhilZ recovery for locked bootloaders you must root first on 4.1.2, upgrade to 4.3 by flashing a deodexed rooted version, plus kernel, plus the recovery
Click to expand...
Click to collapse
well, i was already on the 199 (not deodexed) firmware (of quintas84) (i used the cwm flashable zip) with the dual recovery kernel (by sj8023ld) flashed via flashtool.
i simply flashed your kernel from cwm over the previous one, and then flashed philz touch. rebooted, touch recovery works, the device boots properly, kernel version is okay (3.4.0-perf-ga3976ea), and the bootloader shows blue instead of yellow, so it would probably work even if i relocked the bootloader.
am i missing something? : )

Related

[Q] CWM Recovery on stock KF1(2.3.3)

Is there a method or known workaround that provides the capability to use CWM recovery with the leaked KF1 build?
I have seen talk about it in other posts, but it never seemed to lead anywhere.
Check out Cognition Thread
There is a link in the OP for the Beta 2 kernel. Flash that and you will have CWM 4.0 which is compatible with CWM 3.0 files.
Can it run with stock or is it just for loading CWM files only?
cappysw10 said:
Check out Cognition Thread
There is a link in the OP for the Beta 2 kernel. Flash that and you will have CWM 4.0 which is compatible with CWM 3.0 files.
Click to expand...
Click to collapse
Ok. Now from what I was reading though, there is issues if you try to boot into the phone with this kernel flashed, is that correct? Or does run ok with stock without flashing COG?(I am just waiting till its out of beta).
mastergflash said:
Ok. Now from what I was reading though, there is issues if you try to boot into the phone with this kernel flashed, is that correct? Or does run ok with stock without flashing COG?(I am just waiting till its out of beta).
Click to expand...
Click to collapse
I haven't tried it myself though you can just try and test if for w/e reason it dosent work just use the 1 click here to flash back to stock KF1 with out bootloaders so there's minimal risk (I'm assuming you already have GB bootloaders and all). From what i know Cog's Beta kernal is modded but it should work with stock KF1.
It worked like a charm. I was just leary to do it at first as I have been toning down my phone experimentation lately. But it looks like I am back in business.
Thanks to both of you guys. (And of course, not that he will see this here, but as always, thanks to DG for providing what makes my phone what it should be)

easy question CWM and ROOT

I installed an old firmware [N7000XXKKA], applied ROOT and CWM to it.
now I upgraded my firmware to a new one [N7000XXLA4], by using the CWM manager, and choose KEEP CF-ROOT.
my question is:
did the firmware get completely upgraded? or did the kernel remained the same and I just did nothing
Your kernel will be same old.
You can update it to new LA4 with this
Download , extract n Run I am already Rooted. it will take few seconds
Qvp said:
I installed an old firmware [N7000XXKKA], applied ROOT and CWM to it.
now I upgraded my firmware to a new one [N7000XXLA4], by using the CWM manager, and choose KEEP CF-ROOT.
my question is:
did the firmware get completely upgraded? or did the kernel remained the same and I just did nothing
Click to expand...
Click to collapse
Yes , your device got updated to LA4 and the Kernel remained same. and you have root.
thanks a lot!!!
btw dr.ketan about sanity and bluetooth recording, do you know how to stop echo?
dr.ketan said:
Your kernel will be same old.
You can update it to new LA4 with this
Download , extract n Run I am already Rooted. it will take few seconds
Click to expand...
Click to collapse
What kind of features am I going to miss if I'm on the latest ROM (LA6), but stay on the KK1 kernel?
serpent2005 said:
What kind of features am I going to miss if I'm on the latest ROM (LA6), but stay on the KK1 kernel?
Click to expand...
Click to collapse
If your CWM application is full functional, I dont think any thing you will miss.
dr.ketan said:
If your CWM application is full functional, I dont think any thing you will miss.
Click to expand...
Click to collapse
Ok I was afraid staying with the older kernel meant I was giving up performance enhancements (or other enhancements) in the later kernels.

[Q] More details about flashing

Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
SCC2002 said:
Hi, everyone. I believe these questions are not covered in this forum yet.
Is it possible to just flash kernel from FTF file?
Is it possible to convert or package kernel (IMG / ELF) file to FTF file?
If above 2 are possible, does that mean that kernel can be flashed from flashmode instead of Fastboot mode & thus eliminating the need to unlock bootloader?
Are the firmware & kernel of Xperia T / TX / TL / V interchangeable?
Is there any risk trying to flash other firmware or kernel or anything that is not compatible?
Is there any risk trying to flash kernel (IMG /ELF) file & custom ROM with locked bootloader?
Is flashing stock advanced kernel equivalent to flashing stock kernel?
Click to expand...
Click to collapse
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
SCC2002 said:
I believe these questions are worthwhile to be added into the All In One thread as well.
Appreciate for the knowledgeable input from u all. Thx in advance! =)
Click to expand...
Click to collapse
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
gregbradley said:
These questions have been answered
1) yes, stock only
2) No
3) No, to flash custom kernel you need fastboot, hence you need unlocked bootloader
4) No, but you can try and see
5) There is always a risk when you flash something to your phone.
6) No risk, because without an unlocked bootloader it wont work*
7) No, Stock advanced kernel is a custom kernel based on stock with cmw and a few other things incorpprated, whilst stock kernels are stock kernels.
EDIT
* from number 6) you may soft brick the phone, but just flash a stock based rom back and it will work again. The problem will be with flashing a rom that needs a custom kernel that our phone will not support because you have a locked bootloader.
Click to expand...
Click to collapse
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Why didnt you ask in that thread then? I have spent the time to add them to the FAQ there...
Click to expand...
Click to collapse
Well, I was thinking that these questions are better asked on a separate thread then. Anyway, thx a lot for compiling the All In One thread. It's very useful. More details can be added though. =)
SCC2002 said:
Thank u so much for ur answers. Sorry for didn't manage to find them. =)
1 - 4. My questions arose are bcoz that in order to root firmware later than 7.0.A.3.195 needs to downgrade to 7.0.A.1.303. However, I'm owning a Xperia TX, which having the firmware of 7.0.A.3.197 & the earliest firmware I found for Xperia TX is 7.0.A.1.307. That's why I am not sure whether Xperia T's 7.0.A.1.303 firmware works on Xperia TX.
5. Well, what I mean is additional risk from usual flashing. =)
7. If that's the case, does installing CWM recovery with the phone rooted but locked bootloader resulting in a custom kernel?
Click to expand...
Click to collapse
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
gregbradley said:
1-4) The 303 and 307 firmware are basically the same FW. 303 for the T and 307 for the TX. also 195 is for the T and 197 is for the TX.
5) If you flash something that is not compatable then you can either get various results ranging from no apparent bugs, to slightly buggy formware, to soft bricks or inthe worst case a hard bricked phone.
7) No, installing recovery is seperate to having a custom kernel with recovery incorported within it.
Click to expand...
Click to collapse
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
SCC2002 said:
5. Hard-brick. Does that mean the phone is irrecoverable any more? In what case would result in this condition?
Click to expand...
Click to collapse
Hard brick means your phone is properly FUBAR'd
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
Maybe, try it and see. But i think a whole flash of the firmware is needed.
SCC2002 said:
Oh yea, another question. In this case, downgrading the firmware is required to root the phone. So, does downgrading the kernel only, but not the firmware possible to give the same effect?
Click to expand...
Click to collapse
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
gregbradley said:
Hard brick means your phone is properly FUBAR'd
Maybe, try it and see. But i think a whole flash of the firmware is needed.
Click to expand...
Click to collapse
Spectre51 said:
I had read that for some other devices (I think Xperia P) flashing just the old kernel, then rooting then flashing the new kernel works to keep root without flashing system folder or anything else. Give it a try, worse case you just flash again full ftf and start over.
Click to expand...
Click to collapse
Happy New Year, guys! Thx for the answer. I've tried just flashing the kernel. Doesn't work. Succeeded rooting after flashing the whole firmware. =)
Anyway, now I'm stuck in the process of upgrading the firmware. I can't seem to find a stock ROM for Xperia TX (LT29i) 7.0.A.3.197 firmware. I just gone through all the hard ways to create a stock ROM myself & successfully flashed it. Perhaps bcuz of the improper build, my WiFi can't be turned on & there might be other problems coming up later.
Now I am also worrying that would it cause any prob to my phone. I followed this guide to create the ROM.
http://forum.xda-developers.com/showthread.php?t=1931189
& I took the META-INF folder from this custom ROM.
http://forum.xda-developers.com/showthread.php?t=2040989
Plz kindly help that if there's any resource to the stock ROM or any way to fix this, as well as have a look if there is any side effect from flashing that ROM. Many thanks! ><
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Spectre51 said:
Wifi not working is because you have to copy and rename the /system/lib/modules/prima/prima_wlan.ko file to just /system/lib/modules/wlan.ko
I use this for making my own versions: http://forum.xda-developers.com/showthread.php?t=633246
Click to expand...
Click to collapse
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
SCC2002 said:
Really? That's all? There's no other side effect from the way that I built the ROM? Am I building ROM with a proper way?
Do I've to keep the original file at the original location? Why is it that we need to modify this, just wondering?
Btw, I heard that there's a prob with MAC address with this method from another forumer. Is this true?
Click to expand...
Click to collapse
I kept the other file in the original location. Not sure about any Mac address issue. Worked fine for my device. Not sure about the way you use to build the rom. I just use the android kitchen since its pretty quick and easy.
Sent from my Sony Xperia™ TL

[Q] eXizistenZ ultra 4.0.0 bootloader

I am new to rooting and stuff.
So recently I bought Sony Xperia SP C502 .
The current firmware version is 12.1.A.1.205 .
I want to root my phone and install eXistenZ 4.0.0( rom based on stock rom )
My bootloader is locked.
Bootloader unlock is allowed.I don't want to unlock the bootloader.
Is it possible to root and install the rom without unlocking the bootloader ?
Will rooting and installing the rom automatically unlock it ?
please help I am a noob.
Existenz is for unlocked and locked bootloader
TsunaH said:
Existenz is for unlocked and locked bootloader
Click to expand...
Click to collapse
So installing it won't unlock my bootloader ?
Because i don't want to lose DRM keys and BE2.
See bro
Root it using app called towel root
Install super su not from play store
Install busybox installer from playstore
Install a custom recovery
And flash it
You won't be unlocking your bootloader
You can flash it on locked bootloader too.Flashing this rom won't unlock your bootloader
Existenz Ultra 4.0.0 - Awesome Rom
Existenz Ultra 4.0.0 is really awesome rom with all good features which covered honami as well as sony features.
Battery is good, and most of all AR effect which comes with the rom is the most enjoyable feature ever experienced.
But if this rom will be having good audio mod like Viper4Android.. viz. coz i have observed sound is a little bit less than stock. sorry for my bad english.
ROM Rocks......:good:
Steps for Switching Rom
I am currently using Cm11 on sony xperia sp, I have a unlocked BL and root access.
I would like to switch to a new custom rom now like XperianZe. I tried also, and in the process i bricked and also had a bootloop.
Can anyone please explain the detailed steps to do a fresh install to a new custom rom like XperianZe.
sanusunnyk said:
I am currently using Cm11 on sony xperia sp, I have a unlocked BL and root access.
I would like to switch to a new custom rom now like XperianZe. I tried also, and in the process i bricked and also had a bootloop.
Can anyone please explain the detailed steps to do a fresh install to a new custom rom like XperianZe.
Click to expand...
Click to collapse
Just follow the mentioned instructions in the respective thread. And as for Xperianz as you mentioned, you have to read this post.
Based on the post, it seemed the installation is straight forward. What makes you have a bootloop? Did you flashed the kernel mentioned in the thread via fastboot?
TechnoSparks said:
Just follow the mentioned instructions in the respective thread. And as for Xperianz as you mentioned, you have to read this post.
Based on the post, it seemed the installation is straight forward. What makes you have a bootloop? Did you flashed the kernel mentioned in the thread via fastboot?
Click to expand...
Click to collapse
yes, you guessed correct. i tried flashing the kernel. And the phone didn't start at all.. not even power up.
Later i read a post in XDA, in which it was described that i should do a hard rest by pushing the hole button at back and then try to boot.
Tats when i got boot-loop. I again flashed the custom kernel (DooMLoRD) and did installed CM11 again using CM recovery. Then the phone booted cm 11.
I followed this link and tried doing so. which resulted in phone not powering up and then boot-loop.
So now if i install Xperianz ROM following instruction in this link, it should be working properly correct?
Am sorry if am asking dump questions. Now am a bit scared to try to switch to this cutom ROM as i may end up bricking the phone again. The thing is I really don't want to mess it up again.
I am new to rooting n playing around with custom ROM. CM11 was my first try and was a success in first go.
Thank you for helping me.
sanusunnyk said:
yes, you guessed correct. i tried flashing the kernel. And the phone didn't start at all.. not even power up.
Later i read a post in XDA, in which it was described that i should do a hard rest by pushing the hole button at back and then try to boot.
Tats when i got boot-loop. I again flashed the custom kernel (DooMLoRD) and did installed CM11 again using CM recovery.
But now am a bit scared to try to switch to this cutom ROM as i may end up bricking the phone again. That's why i asked if anyone could give me detailed steps on how to do so.
I am new to rooting n playing around with custom ROM. CM11 was my first try and was a success in first go.
Thank you replying
Click to expand...
Click to collapse
I am concerned about how you flashed the kernel. How did you flash the kernel provided in the thread? Did you use adb or FlashTool?
If you want to try any other you can use Existenz as it require only the stock kernel.
TechnoSparks said:
I am concerned about how you flashed the kernel. How did you flash the kernel provided in the thread? Did you use adb or FlashTool?
If you want to try any other you can use Existenz as it require only the stock kernel.
Click to expand...
Click to collapse
I used FLashtool to flash the kernal.
If my understanding is correct, As of now i am not on stock kernal. When instaling CM11, I flashed the kernal of DoomLord for getting CM 6. recovery.
If this is the case should i flash the stock kernal first and then give a try for Existenz?
sanusunnyk said:
I used FLashtool to flash the kernal.
If my understanding is correct, As of now i am not on stock kernal. When instaling CM11, I flashed the kernal of DoomLord for getting CM 6. recovery.
If this is the case should i flash the stock kernal first and then give a try for Existenz?
Click to expand...
Click to collapse
Well Existenze require most Sony things out of the box, so you'll first need to have Stock ROM in place before flashing it's ZIP. I've dug through the Xperianze thread for you and seemed like your problem is not to be found in the thread. If you really want to try out Xperianze, you might want to flash the kernel via fastboot using adb, rather than Flashtool.
TechnoSparks said:
Well Existenze require most Sony things out of the box, so you'll first need to have Stock ROM in place before flashing it's ZIP. I've dug through the Xperianze thread for you and seemed like your problem is not to be found in the thread. If you really want to try out Xperianze, you might want to flash the kernel via fastboot using adb, rather than Flashtool.
Click to expand...
Click to collapse
Thanks a lot.
I will try it out. and let you.
Again Thanks a lot for your help.

[KERNEL][STOCK] Stock 5.0 LRX21O Flashable Kernel

Hello all,
Couldn't find a stock flashable kernel for in between kernel flashes, so I slapped this one together. I used an old kernel script I had from back in the day (see my thread history) and just put the boot.img inside and changed the UI text. Tested working. Enjoy!
Handy! Thanks for your efforts.
Thank you?
No problem! I made it for myself and realized nobody had one up here so I figured it could help at least one person.
Thanks, always handy when you've tried a kernel that is not good
Thank you very much for this man!
Thanks
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
MidnightDevil said:
First of all, thank you for sharing it with us.
Then, from my understanding since this is Google Stock Kernel that comes with Lollipop, I'm assuming it won't allow root even flashing SuperSU ? (Last time I've read the kernel needed to be somewhat compliant with root so you can use root), am I right?
Cheers!
Click to expand...
Click to collapse
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
jlink38 said:
You're correct. So basically what I do is flash this, then immediately flash the next kernel I want to use in the same TWRP session.
Click to expand...
Click to collapse
Thanks, also, from my understanding, some users reporting broken scripts when switching from one custom kernel to another. The solution so far was to flash Stock kernel before flashing another custom kernel. This happene(d) betweeen Franco Kernel and ElementalX, where sweep2wake functions wouldn't work.
Thanks for clearing this up, a stock kernel is always handy whatever the reason
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
jlink38 said:
Sure, flash away, as long as it is stock 5.0. Not sure how it would fare with AOSP. YMMV.
Click to expand...
Click to collapse
Thanks
Duilio Patiño said:
So, I'm on Franco Rom can I flash this kernel and then xxkernelxx? Thanks in advance
Click to expand...
Click to collapse
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
xdrc45 said:
Not all kernels modify the devices system files.
I believe though that since Franco kernel modifies the system files and Since flashing just the stock recovery wouldn't alter or restore those modified system files back to normal otherwise it may/will cause conflicts and errors while running the new kernel.
You would need to (depending on your current setup)
1. Dirty flash the 5.0 ROM that your running to replace those system files back to normal and then flash the OP's stock recovery.
2. Fastboot flash the 5.0 Google Factory System.img (whick would reaplace the modified system files) and or the google factory boot.img or just flash the OP,s stock recovery and then any other compatible kernel in one setting.
3. Restore a stock nandroid backup that has the stock system.img and then flash any comparable kernel.
@jlink38
Thank you for this... Very Much appreciate and it will definitely come in very handy! :good:
I like to have a copy of evey stock recovery version for the N5 in a flashable.zip
Click to expand...
Click to collapse
No problem!
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
RevoWution said:
Thank you very much for the thoughtful upload, OP!!
Been meaning to try out Franco's latest nightly for LP to see if I get an improvement in battery life
I'm assuming if I don't like Franco's kernel, I just simply flash this zip in recovery (I use Philz CWM) to return back to the stock LP kernel?
Click to expand...
Click to collapse
Pretty much, yeah
Sent from my Nexus 5
amir7777 said:
Pretty much, yeah
Sent from my Nexus 5
Click to expand...
Click to collapse
Cheers buddy
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
danifeb said:
I'm in Elementalx kernel and Rom stock. To receive OTA, flash stock kernel is enough?
Click to expand...
Click to collapse
You should be OK. I don't know what else you have tweaked.

Categories

Resources