Database Info

How to prepare nexus s for ice cream sandwich ota

Currently running miui with matrix kernel and I'm looking into flashing a stock gingerbread ROM to receive ics when it is released. I've flashed customs ROMs before but have never gone back to stock. How do I go about doing this? Will I need to reroot my phone? And will I be able to flash a kernel on the stock ROM? Thanks
Sent from my Google Nexus S using Tapatalk

I wouldn't worry about it. Someone kind will post it here in a zip file soon after release i would imagine!
Sent from my obnoxious finger using Swype

mokflurry said:
Currently running miui with matrix kernel and I'm looking into flashing a stock gingerbread ROM to receive ics when it is released.
Click to expand...
Click to collapse
This is not necessary; somebody will almost certainly post a zip of it here you can flash.
mokflurry said:
I've flashed customs ROMs before but have never gone back to stock. How do I go about doing this?
Click to expand...
Click to collapse
Flash it just like any other ROM.
mokflurry said:
Will I need to reroot my phone?
Click to expand...
Click to collapse
No. As long as you have CWM, you're all set.
mokflurry said:
And will I be able to flash a kernel on the stock ROM?
Click to expand...
Click to collapse
If someone makes one, sure.

sorry for abusing you thread, mokflurry, but i also have a question regarding requirements for the upcoming ota-update.
i am running stock rom, rooted, with cwm and custom kernel.
regarding the recovery, i already read, that this shouldn't be a problem. can anybody confirm that?
and what about the kernel? will i have to return to complete stock for ota?
thanks in advance!
yours
n00b ;-)

Petarsson said:
sorry for abusing you thread, mokflurry, but i also have a question regarding requirements for the upcoming ota-update.
i am running stock rom, rooted, with cwm and custom kernel.
regarding the recovery, i already read, that this shouldn't be a problem. can anybody confirm that?
and what about the kernel? will i have to return to complete stock for ota?
thanks in advance!
yours
n00b ;-)
Click to expand...
Click to collapse
You can be rooted with another recovery, But need stock rom and kernel.

Until and unless you believe that you will be the first one to get the OTA, you need not worry about the OTA. It will be up on XDA as soon as OTA is rolled and you be flashing it even before the OTA is actually is pushed to you

[Q] Returning to TMobile

So I called TMo and they're sending me a replacement G2x. I've seen a number of people claim that they never unroot their phones before sending them in. Is this true? I'm inclined to believe that this would cause issues but I'd just like everyone's two cents before I send this in.
Also, there's a thread in the dev section for reverting to stock. However, this uses SuperOneClick, a method for FroYo based G2x only. So, if I cannot send my phone in rooted, is there a method for reverting phones that have been updated to GB?
Thanks. And sorry if this has been posted before.

I believe you can use S.O.C. after already achieving root to help you revert back to stock. You can just go back to gingerbread no need for froyo.
Sent from my LG-P999 using xda premium

http://forum.xda-developers.com/showthread.php?t=1056847
Sent from my LG-P999 using XDA App

You need to go back to a stock 2.3 unrooted rom
http://forum.xda-developers.com/showthread.php?t=1255214
[ROOT] G2X Gingerbread 2.3.3. stock ROM with flashable zip in Clockworkmod Recovery Then use nvflash the recovery to stock to go back to a 100% stock
Sent from my LG-P999 using xda premium

Easy way to fix it is to format the /system in CWM then flash stock recovery with NVflash. Tell T-Mobile that the phone will not boot and your problem is fixed. No need to flash back to stock rom.

Prod1702 said:
Easy way to fix it is to format the /system in CWM then flash stock recovery with NVflash. Tell T-Mobile that the phone will not boot and your problem is fixed. No need to flash back to stock rom.
Click to expand...
Click to collapse
That is pure evil. I like it.

GenghisKhan67 said:
That is pure evil. I like it.
Click to expand...
Click to collapse
I work for T-Mobile if it makes you feel better.

Prod1702 said:
I work for T-Mobile if it makes you feel better.
Click to expand...
Click to collapse
I used to work for T-Mo tier2 pda until they closed our support center January 2010... I never heard of someone having their warranty voided due to root, but it's probably better to be safe than sorry. Things may have changed.

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

Updates while on custom kernel?

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: