Well I was running stock 404(i9020t) rooted with matrix kernel, and trying to prepare for jb ota in a few days I decided to go back to stock thinking having a non stock kernel, I would miss out on jb ota. So I proceeded to flash what I thought was my stock image for my phone (i9020t) but it turns out it was for (i9020a). After I realized that wasn't the correct image I halted my process. I'm currently on stock 404(i9020a),but my bootloader is still unlocked. So my question is 1. Will this affect me getting jb ota 2. If not will the ota correct my phone baseline 3. What steps should I take to achieve the stock 404 for my specific phone? I've read through multiple posts so I'm guessing I need some simple explanation. Thanks in advance.
Mod plz remove. I solved my problem. thx.
Related
_title says it all.
kemsiro said:
_title says it all.
Click to expand...
Click to collapse
Return to stock by flashing an official, signed & of course unrooted Rom through recovery. The link below has everything you need to get back to stock. The other alternative is to wait till someone posted a stock rooted ICS rom which will in all likelihood happen before it gets pushed out to everyones phone anyway...
[REF] Links for ALL Nexus S OTA Updates for ALL Variants, Plus Full ROM Packages
http://forum.xda-developers.com/showthread.php?t=1063664
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 did a search and couldnt find the answer to this.
I have a TMOUS Sensation 4G, i went ahead and did s-off, rooted, and installed an ics rom. I loved the rom, but decided to go back to stock due to radio issues i just couldn't get figured out with multiple attempts. So, i'm back to current stock firmware and am un-rooted. The only thing i haven't done is gone back to s-on. Does anyone no if that will effect me getting the OTA to ICS when released?
Thanks for the help!
No being S-off will not keep you from getting the OTA update when it gets pushed. You just have to be running the 1.50 software and have the stock recovery.
Check out this thread and follow the instructions in order to install the ICS OTA.
I think i'm getting overwhelmed with all the reading I'm doing and need a little help clear out the confusion in my brain
I'm rooted
I have SUPER CID
I have S-OFF
Custom Recovery (TWRP)
On a custom ROM (chameleon OS)
Never updated to JB OTA
Does my phone need to update to JB before I begin to flash any other Custom ROM? I know these roms provide Android 4.1/4.2+ but does my phone need the OFFICIAL JB update for it to work good? I see a lot of people installing the stock RUU and getting the update - I guess my main question is - is it necessary to downgrade back to stock, update, re-root,unlock, install new ROM again with my phone now having JB thru OTA?
If so - what are the PROS of doing this?
If not - is my phone going to be okay installing ROMs with my phone never being updated.
Thanks!
Short answer: no.
Long answer: no, because you're wiping cache and data the phone is a blank slate. You could go back to Cupcake or skip forward to Jelly Bean 4.3... If you managed to break into Google Inc and get the data for that.
Sent from my HTC One S using xda premium
Normaly no.
But I've seen situations with previous devices that a certain min hboot/firmware is required.
Like if your firmware is gb any jb/ics Rom might not work. just an example!!
Just look what base the Rom is made from. Test if it works. If not update you're firmware to min required or same as base of rom. Test it again.
Always check op of rom. Or ask the dev.
Verstuurd van mijn HTC One S met Tapatalk
since you're s off, any ROM will work.
Real187, on some other HTC devices (eg.Flyer), you had to match your hboot to the ROM, but so far for the One S, this hasn't mattered (for the average user).
The only "firmware" partitions you might consider messing with is the radio, but that won't affect if the ROM boots.
to answer your question, the pros of ota are none to negligible. No ones sure if the other partitions it updates are beneficial.
Thx for the replies! I was worried about this as I see a lot of people trying to downgrade and bricking their phones while doing the process.
I have searched high and low for help getting Kitkat to work on my phone. Here is the background to my problem:
I rooted my Bell Note 3 (Canadian) phone running JB. After doing so I then put a CWM recovery and then flashed with a custom JB rom. Everything works great and yes I do know that I have tripped the KNOX counter. So when the new Kitkat was released I wanted to upgrade to it. I downloaded the original Bell stock JB rom and the stock KK rom. I also downloaded Odin. I tried to flash back to the stock JB rom like I should before updating to Kitkat and while doing so and with Odin I keep getting errors not allowing me to revert back to stock. I know when I boot up I get a notification in the top left corner saying on two separate line exactly like you see it below.
KERNEL IS NOT SEADROID ENFORCING
Set Warranty Bit : kernel
My question is to whoever knows the solution to how to return back to stock JB and then flash KK rom. I have a feeling it has something to do with what is in the left corner when I boot like you see above. If there is a fix please let me know and if I am totally wrong and the problem and fix is something else please feel free to help me. I have been flashing custom roms since Android has been around. This problem has me baffled and don't know what to do from here to get me back to JB then to KK.