Related
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
brownmonkey said:
Hi,
I had a few questions about kernels...hope someone can help me in answering these...
I am thinking of trying out the Netarchy kernel on my Nexus S, but i was just wondering is there anywhere I can download the stock kernel (so that if anything does go wrong i dont have to do a full nandroid restore?)
Also, when installing a new kernel does that wipe data (of course I will make a backup etc before installing it, but should all my settings and apps etc remain intact normally?)
what impact does an OTA update have if i am running a non stock kernel? so say i am using Netarchy's kernel, and google releases a new OTA update...will i still be able to install the update? If i do, will it revert to stock kernel?
Thanks in advance,
Click to expand...
Click to collapse
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
kenvan19 said:
I'm not aware of anywhere that the stock kernel is available for download so doing a NANDroid backup is really your best option. If you have anything that deviates from stock (kernel, rom, theme, even just deleted stock apps) it will prevent you from being able to successfully update from an OTA.
You can find a lot of information about all the available kernels here just scroll down to the third post and you'll find the info.
Finally, just as a note of personal opinion, getting OTA updates is a little overrated. If you run a custom ROM, the OTAs will be included in those ROMs eventually so you won't have to worry about restoring a stock ROM just to get the updates.
Click to expand...
Click to collapse
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
brownmonkey said:
Thanks for the quick answer. I had read that post before (it was actually how i came to discover kernels ). The reason why I was asking about the OTA is because I actually use the stock ROM but was just thinking about trying out the Netarchy kernel just to see what its all about. Hence if there is an OTA update, and i am running a different kernel to the stock, is the only way for me to incorporate the update by flashing the new stock rom and then reinstall the netarchy kernel?
Also, if i install it, do you know if it wipes data/apps?
Thanks
Click to expand...
Click to collapse
I apologize as I forgot to mention that part of your question, I'm sick with the flu and a little out of it on some cold medications lol. You only lose data and apps when flashing if you wipe the /data partition in mounts and storage and this is not required nor is it recommended when flashing a kernel. Sorry for answering out of order, but I thought I should clear that up first. As to the other question, you have it correct; you would need to flash the new update ROM and then flashing a new kernel.
I should also note that whenever you install a new ROM, you will need to reflash a custom kernel. This is because the vast majority of ROMs released include a kernel and when you flash them it will overwrite whatever kernel you currently have.
Finally, if you have any other questions you can always feel free to post them on that thread. I'm the one who wrote it and I check it often to try and answer questions as best and as quickly as I can. Happy flashing!
Are you using a custom ROM? Flashing CM7 has the stock kernel. There are probably other ones out there that includes stock kernel with them such as OTA.
Ok, here is what I've done and where I am.
I'm using a Nexus S I9020T (original T-Mobile version). In the past I've used cwm custom recovery, flashed custom roms and obviously was rooted. The last flash I did, I upgraded to 4.0.3 stock and all went smooth, but as of right now I'm just not a fan of it.
So now, I've downgraded back to 2.3.6 stock rom. I'm also now sporting stock recovery and am rooted. I know this is a little weird, but I'm wanting the ability to do OTA updates using stock recovery, but also want root access, which is all working well at the moment.
But, I don't want to go back to 4.0.3 as of right now. So, is there an easy way for me to disable the system update notifications and stay on 2.3.6 right now and later on just re-enable them to do the update later.
From what I've read online, my best bet is to probably edit the build.prop file, but I'm not sure what content would need to go in there. I've also seen about freezing files, but I'm already getting 4.0.3 update notifications, so I'm not sure that will work.
Any help is appreciated
I have two questions...
1. I had rooted my A2 when it was 2.3.5 and deleted a few apps. When the OTA update to 2.3.6 rolled around, I couldn't update because ATT is a grouch. Anyway, to solve that problem, I had to flash stock 2.3.5 back onto the phone removing root access and everything. I then proceeded to update to 2.3.6 which is fine. that's running stock as I type this. My question is, if I root it again on 2.3.6 (I know it's there...) and I freeze apps, when another OTA update rolls around, will I be able to update again? I don't want to have to flash it back to 2.3.6...(can I even do that yet?) so any help here would be appreciated.
2. I was out and about, and was looking at one of my friend's phones. She has this HTC HD2 running Android 2.3.3 AOSP. She uses ADWLauncher, etc etc. This is a Windows Phone, originally. That got me thinking...is there a AOSP version of Gingerbread for my A2? Without Blur? I'm kinda scared to do anything to it, because I want to be able to get ICS come July. Any tips here would help.
Sorry for not using the searchbar, I was just having trouble finding this info. Thanks guys!
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
SeekerLoki said:
1. Yes. Freezing apps / removing bloat as root will almost definitely keep you from the any OTA. Its the nature of the beast. You can always return to stock and apply the updates later. Also, any major update like ICS will produce a lot of posts here about how to update from an altered rom.
2. There is development work on getting CM7 to work on our phone. Currently the only released ROM that I am aware of is lfaber06's ROM
Click to expand...
Click to collapse
When a major update such as ICS is released, there will be alternate ways to install such as through bootstrap. Hopefully we'll find a leaked version of ICS before that, and pull the radio get CM9 working
Okay. So I'm planning on rooting it...now...but when I flashed 2.3.5 from the fxz someone provided, it said that once you updated to 2.3.6 you could never go back...but...
I'll try it.
What's bootstrap? I've heard about it and no one has been able to dumb it down for me...could anyone do that?
You can flash the FXZ after the update. It just requires a bit of modification and care. You might want to read the noob thread. It has lots of useful info.
Bootstrap is a way to backup, restore, and flash zips before android boots.
I just rooted the 2.3.6 it's running wonderfully.
Should I install the ibfaber deoxed rom? I mean I know I can do it per instructions but is it worth it?
It depends on what you want to do. If you want to apply any themes you will need to be running the deoxed rom. He also has a supercharged rom that has a lot more customization.
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
dunderball said:
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
Click to expand...
Click to collapse
I still use LF2 and have seen zero good reasons to switch. I have a custom kernel and several customizations to things such as framework.res and such so I'm not exactly stock rooted.
dunderball said:
Since I got the phone, I've been stock rooted/unlocked the entire time, and managed to disable OTA updates in fear of losing root and etc. Is anyone still on the original firmware and is there any good reason for me to upgrade?
I think the next OTA I'd probably take is if Jelly Bean comes out, and even then I'd most likely simply Odin-flash a stock rooted image whenever the time comes. Any advice on how to go about a possible Jelly Bean OTA from Verizon?
Thanks
Click to expand...
Click to collapse
Why not take the OTA then reroot/unlock? There are some minor changes in the menus and such and also the radio is a good reason to update. Much faster switching between 3g/4g and such, better signal strength. Or if you are running custom recovery you can just flash a updated radio. Also there is a thread floating around here with a customized updater that will keep root and your bootloader unlocked. As for the OTA to jelly bean you can just flash a jelly bean rom ontop of your F2 baseband.
crabapples said:
I still use LF2 and have seen zero good reasons to switch. I have a custom kernel and several customizations to things such as framework.res and such so I'm not exactly stock rooted.
Click to expand...
Click to collapse
Same, stock rooted since day one to change kernal, add wif tether and to use things like titanium back up. I use apex and SwiftKey. Everything works. No reason to break something...
Sent from my SCH-I535 using xda app-developers app
I've been using the Jellybro kang of CyanogenMod (10-20121120-SKANK-d2vzw). I had NFC working as recently as the 11/3 build, but when I flashed the 11/5 build NFC broke.
I tried flashing a stock JB (deodexed and rooted) rom, enabling NFC and restoring back to my nandroid, but the NFC still wasn't fixed. I've tried the NFCfix.zip and that didn't work either.
Do I need to flash stock.vzw_root66.tar in Odin and turn on NFC? Or is there a specific stock rom I should be using?
What am I doing wrong, or what else should I try? I've done my best to search the forums and figure out a solution, so figure me if there has been clearly hashed out elsewhere.
Thanks!
[edit] Solution: flash this NFC fix http://www.mediafire.com/?y6vx27cpaasqhxs
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
ddurandSGS3 said:
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
Click to expand...
Click to collapse
Let me give it a shot. Are you suggesting any TW ICS rom or specifically a stock ICS? Can you link me to the rom you use, please?
Thanks!
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
i use a stock rooted from scottt that i have saved on my laptop to fix my NFC.
ive seen people ahve success wth the zips floating around, try that first its quickest easiest
Polymira said:
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
Click to expand...
Click to collapse
Perfect! That fixed it. Thank you very much.
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
majixx11 said:
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
Click to expand...
Click to collapse
I'm having the exact same problem and seems like no one can help with this
On my S4 I9505 I can turn on S4 but then nothing happens whenever I try to scan any tag... Any ideas? I flashed different stock roms and tested 3 different batteries with visible loop antennas on them. Nothing works.