..that is the question
I just bought a brand new Nexus S (cheaply compared to other phones of this caliber), and I'm really loving the the speed, stock Gingerbread and basically everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what's stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- warranty (any way to save to stock ROM and return it if I need to send the phone?
- bricking?
So I'm asking you guys who are using your Nexus S' for awhile:
- are there any special options in the CM7 for the Nexus S?
- what specific features are in CM7 that are missing from stock Gingerbread?
- which kernels do you guys suggest (with what major features)?
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS OTA update is available
- possibility of bricking? How high is it? I'm never had to do some ADB stuff so far, so as I see this won't be exactly just a walk in the park...
I know I bombed this post with questions but basically all I want to know from you guys: is it worth rooting, what are the advantages of rooting (beside the obvious one - having a root access for some apps that needs it) and most importantly what is "fixed" and tweaked in various kernels for the Nexus S?
Thanks in advance,
Atila
atirage said:
..that is the question
I just bought a new Nexus S (cheaply compared to other phones of that caliber), and I'm really loving the the speed, stock Gingerbread and basicly everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- Warranty (any way to save to stock ROM and return it if I need to send the phone?
Click to expand...
Click to collapse
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
atirage said:
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS ota update is due
- possibility of bricking? How high it is? I'm never had to do some ADB stuff so far, so as I see this wont be exactly a walk in the park..
Click to expand...
Click to collapse
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).
krohnjw said:
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).
Click to expand...
Click to collapse
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help
anishs said:
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help
Click to expand...
Click to collapse
You were told incorrectly. I've flashed plenty of OTA's over CWM on both the Nexus One and the Nexus S. There is no assert done on the recovery in the OTA update script, it merely erases it and flashes a full recovery image over it.
Receiving the OTA has NOTHING to do with the status of your system (rooted, not rooted, custom recovery, locked/unlocked). Your device periodically checks to see if there are updates, if your IMEI / ESN is flagged for an update and you are running a previous build (based on build fingerprint) you'll get the notification to download the OTA.
oh wow alright thanks a lot!
@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Thanks in advance,
Atila
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?
I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".
rentaric said:
I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".
Click to expand...
Click to collapse
Honestly, I wouldn't worry about it. I sent in an unlocked Nexus One that was damaged in a car accident - repaired under warranty for no charge. If it's a clear hardware defect you're fine, if you burn our your LED or toast your speaker then they may give you grief.
atirage said:
@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
Click to expand...
Click to collapse
Correct
atirage said:
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
Click to expand...
Click to collapse
It's really difficult to "brick" in the traditional sense.
atirage said:
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
Click to expand...
Click to collapse
I don't use CM7 or any non standard kernel any longer - too many stability issues early on and stock AOSP runs fine. Someone else will need to chime in here.
atirage said:
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Click to expand...
Click to collapse
Yes - this will modify the boot partition though, so OTAs that assert boot to patch it will fail.
atirage said:
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?
Click to expand...
Click to collapse
The OTA didn't come out until last Feb if memory serves correctly. AOSP Gingerbread roms were being built for the Nexus One in December though.
Thank you again for all your answers
Can somebody explain to me what are the improvements in CM7 and a stable kernel over the stock ones?
Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?
atirage said:
Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?
Click to expand...
Click to collapse
A lot..just read at nexus S development..
If you want to safe..
flash CM 7.1/brainmaster MIUI/Formel MIUI/Pete Alfonso/Oxygen 2.3
kernel matrix V8, TEUV,TUV stable
I am personally holding out till ICS is released.
My conclusion...
borrowedchief said:
I am personally holding out till ICS is released.
Click to expand...
Click to collapse
After several days of research, that's the conclusion I got too.
It's all nice what I can do with a rooted device and an unlocked bootloader, but on the other hand the unrooted device is also very customizable and powerful.
The stock rom/kernel works fast and stable, so why risk it?
And the faster ICS official update (earlier then on any other device) is the main reason I bought this phone...
PS. Although I think we won't see an official ICS OTA update before 2-3 months after it's premier (which is next week). Most probably the XDA developers will make an ICS rom much, much sooner and we gonna end up unlocking/rooting our devices anyways.
Related
As the title says, here's the Rom.zip extracted from RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe for those that don't use Windows, or prefer to have their RUU in zip format.
This will flash your phone to 2.31.651.7 STOCK.
http://www.mediafire.com/?m6x4sr682ruk027
Simply rename this to HERCIMG.zip and place on the root of your SDCard.
Power your phone completely off.
Press and Hold VOL DOWN and POWER until your phone boots into HBoot mode.
Wait for it to verify the zip, then click <ACTION> (Trackball) to update, or <SEND> (Green Call) to cancel.
Enjoy!
Here's my guide to rooting .7:
http://forum.xda-developers.com/showthread.php?t=804296
Personally..I want to say THANK YOU, THANK YOU, THANK YOU.
I have spent the last four hours searching for this. This needs to be stickied. I'm bookmarking it for sure. This got my phone unbricked..I thought all hope was lost and I would have to call in for warranty support (I got mine refurbed through Sprint last October..so I don't even know if I would still have any warranty support), and see if I could try my luck and getting it replaced, since that is what others have said to do as apparently this file from OP, did not exist.
And so for future reference, so that others don't go mindlessly searching through the forums.
If you
a.) Managed to overwrite your Recovery some how or completely delete it. (I did..and from searching this and many other forums over the past couple hours..I can see I wasn't the only one), and also have no boot (or a corrupted boot loop)
b.) Still have S-ON (You can find this out by powering off your phone and then pressing and holding the power button and the lower volume button), I recommend you turn S-Off for future reference if you're going to be dealing with customer ROMs a lot (so you don't have to go through the hell I just did..). See here..
http://forum.xda-developers.com/showthread.php?t=759955
c.) Have an updated Hboot (1.47) (you can also find this info. in part b.)
....then you KNOW that you are stuck. Because you
a.) Cannot flash a ROM in Recovery because you cannot access it.
b.) You cannot access ADB because your phone won't go that far and will only go into fastboot..
c.) But even though you have access to fastboot you can't do ANYTHING like flash a recovery image or a ROM..or anything for that matter..because S is still ON. (this is the "not allow" messages you will see pop up.)
d.) You have bootloader 1.47 so if you for example, were like me couldn't use this file here.. (http://forum.xda-developers.com/showthread.php?t=657086), because it would say there was a newer version and wouldn't install it.
So this file right here..was the only thing getting my phone back to a usable state. And considering that my searches have shown to pretty much give up all hope and have it sent it for warranty repair, then I think this thread deserves a bump for all those that have screwed up.
Yeah..I have to start ALL OVER now from a stock ROM (thank god for nandroid), but at least my phone isn't a dead brick.
Just thought this needed a well deserved bump.
I wonder if there is a RUU for the latest .2?
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
Wanted to say BIG THANKS. This worked like a charm to update prl/profile. Keeping two copies of this one on the sd and on the laptop. Thanks again.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
Forgive me for seeming NOOBish... but I can use this to do the same, then restore Nandroid back and it will keep the PRL/Profile update?
Just wondering... lolz, thanks!
Yup But you will have to reroot. This takes root from you. You will have to reroot with the Hero rooter from Reg or Z4 or one click root. But read read read. And as far as the prl/profile yup it will stick. When your phone boots up after running this just go into settings and updates and choose update profile and update prl don't update firmware. I repeat don't update firmware. After that just reboot and check your prl should be 60675. After that reroot, then flash a recovery and then nand restore. Hope this helps good luck
Remember this returns you to stock you will loose root and recovery..
Yea it's me Again. With the
Modified .HERO.
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
laie1472 said:
I tried flashing almost ever sense rom on here pmgrands port, ninfintes stock odex and deodex and his apps 2 sd builds he has like 4 or 6 different builds. Tried flashing liquids builds beta and stable. All gave me a error. So I had to use this. I couldn't flash any sense rom
and it was easier to use this than try to figure out y. If he can flash a sense rom then yea that's the easier way but if not this is a for sure way to get back to stock.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
jckeyser said:
I still have my original nandroid from before I flashed any ROMs and it takes me back to stock Sprint, where I do my updating. Is this faster than that?
Click to expand...
Click to collapse
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Thanks for the reply's all... I like Sense and have NFX rom on my Hero, loaded a few ROMS but they won't update, so no worries, when I have some free time I'll sit and do it then. I don't like the one click rooters nor the clockwork recovery, I guess I'm old school and do it the hard way, lol, but thanks for letting me know it'll work (prl update) and stay on the handset!
Regards!
Without opening a huge can of worms I would like to know whats the best newest rom out there with sense I just searched for like 3 hours and lot of threads are old and I want what ever is new with sense also would like to upgrade to 2.2 im on Honeybun v.-2 lite firmware 2.1 update1
Gelladuga69 said:
Why don't you guys just flash NFX's or LS's already rooted and way faster stock sense ROM to update PRL, etc?
Running stock ROM has to be one of the worst things ever after being on custom ROMs for so long.
Click to expand...
Click to collapse
you got a link ? Im searching now
laie1472 said:
Yup. That's way better and faster. Just go into settings / updates. Then just update prl and profile. Don't update firmware. After you confirm that your updated just nand restore and you should be good.
Edit not sure if you would have to reroot.
Yea it's me Again. With the
Modified .HERO.
Click to expand...
Click to collapse
No need to reroot because it was a nandroid. Can't make a nandroid if you're not rooted.
Sent from my HTC Hero CDMA running Android 2.3
Does anybody have the original MD5 checksum for this file? I wanna make sure this file downloaded properly. Thanks in advance!
EDIT: efa439da700b5fad7ea49915ef7d2866
Sent from my HTC Hero CDMA running Android 2.3
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
mrtimo said:
does this work with any version of HBOOT? The phone I am dealing with has stock 1.5
Click to expand...
Click to collapse
What? Is your phone even rooted? Sprint upgraded to 2.1 a LONG time ago, the update is available at www.htc.com
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
systemshock869 said:
It worked for me a while ago, but my dad just got a new hero so I tried using this, and it wouldn't recognize the image file.. any thoughts?
Click to expand...
Click to collapse
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
il Duce said:
yeah, this only works if he has an S-off bootloader, which he doesn't have if it's a new hero.
Click to expand...
Click to collapse
According to the OP this one was extracted from the RUU, so it *should* work S-ON.
I've seen many different rooting methods for the nexus s but unfortunately they don't allow rooting without unlocking the bootloader like the samsung vibrant allows is there anyway I can root my phone without unlocking the bootloader?
why I don't want to unloack the boot loader because I'm fine with the stock ROM on my nexus s. I was really into installing ROMs and things with my Vibrant but the Nexus S feels really complete so I feel like I don't need to unlock my boot loader
Also for the first time I have decent signal in my house after switiching from my blackberry to android so I don't wanna change my baseband and my battery life is good too so I don't want to mess with the kernel
Really? You posted in the same incorrect forum twice with the same question cut and pasted. Nice work!
Sent from my PC36100 using XDA Premium App
You know you can re-lock the bootloader with a fastboot command, right? And the little open lock goes away.
i'm sorry i accidentally reposted i pmed the moderator right away because i didn't know how to delete the post and this is the right section its a question...
i just have one question i can relock right but if i do unlock the bootloader will it change my kernel or baseband settings? i really couldn't care about the warranty and such
it's like opening the door....if you do nothing inside, nothing will happen
yes i get that but i can't flash back to the original recovery as of now and so no changes to the kernel and baseband alright thanks!!
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
anishs said:
also is there some sort of a "ODIN" availabale for nexus s because thats what I used to always flash my samsung vibrant back to stock. will OTA updates be affected if I root and unlock the bootloader?
Click to expand...
Click to collapse
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
suksit said:
Yes you can use Odin with Nexus S, but consider it the last resort because normally you can do everything via adb and fastboot -- that's the advantage of having a Google phone.
For OTA updates, I'm pretty sure it will not work because OTA update requires stock recovery but rooting requires you to flash a custom recovery.
Click to expand...
Click to collapse
thanks for that reply it explained everything can you just tell me if flashing a custom recovery change my baseband or kernel that's all i need to know now
@anishs no
Sent from my Nexus S using XDA App
thanks to everyone for helping a noob with a nexus s
I'm going to root this weekend, but I have a question...
If my phone starts to fail hardware-wise (for example the touchscreen stops working), is there a way I can unroot and flash back the stock ROM (even with the phone not working) so that I can send it to the warranty?
KaiZ51 said:
I'm going to root this weekend, but I have a question...
If my phone starts to fail hardware-wise (for example the touchscreen stops working), is there a way I can unroot and flash back the stock ROM (even with the phone not working) so that I can send it to the warranty?
Click to expand...
Click to collapse
Depends on the hardware that fails. With working volume, power keys and usb , a computer can be used. No touch screen needed.
Sent from my Skanky Nexus S in the Matrix using XDA App
Thanks, seems good enough to me, I'm going to root.
There's one more question I forgot to ask... I'm currently on official OTA update 4.0.3, how am I supposed to root with ICS currently installed?
Also, what software will I need to flash ROMs and for recovery?
KaiZ51 said:
Thanks, seems good enough to me, I'm going to root.
There's one more question I forgot to ask... I'm currently on official OTA update 4.0.3, how am I supposed to root with ICS currently installed?
Also, what software will I need to flash ROMs and for recovery?
Click to expand...
Click to collapse
Read the pinned guides in the General section of the Nexus S.
My first question is: is it possible to get the OTA update on a rooted phone?
The 2nd question is there something I can do to get the Software Update check work?
I realise that my first question may answer this one as well, it's only just that all of the other ROM's I've tried did at least seem to contact a checking service and come back with a response that No Updates have been found. This one just keeps waiting for a response and never gets one.
Want to at least try the official OTA ICS update from Vodafone UK if possible, without having to load a stock ROM and locking my phone again.
Thanks
Sent from my HTC Sensation Z710e running Extreme Sensation Dream 2 using xda premium
It has always been traditionally said not to apply an OTA on a rooted phone as, historically, it's caused nothing but problems. Whether the same is true now I can't say BUT I would not recommend it personally
do i need to uninstall only SU, or su and clockwork to install ota?
sorry for my bad english
thanks
CWM needs to go as well - you need the stock recovery
Thanks for the advice. I'll have to go stock if CM9 is a long way off. Or try 7.x again, although I'll really miss ICS.
Sent from my HTC Sensation Z710e using xda premium
I think as long as you have stock recovery but are S-OFF; it shouldn't be an issue. I looked at some previous posts , albeit from the Evo forum and it seems to be fine. I could be wrong, though.
I keep seeing people post about being rooted and flashing the OTA update. Now someone please, please, please correct me if I am wrong, but when you flash as new ROM, unless you just flash a new system via ADB fastboot commands, you flash a new kernel and all every time you flash a new ROM. So therefor it does not matter if you are rooted cause the rooted kernel will be replaced with a new ROM. For those out there that do not know the kernel is contained in the boot.img of a ROM. Now in a s tock ROM it is. Of always named boot.img but it is still pretty much the same thing with maybe a little more than a custom TOM's would be. So please people stop wording about being rooted, it does not matter. If you are on the correct stock ROM and have the stock recovery you are good to go to flash and run the OTA. It does not matter if you are S-off or S-on either.
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
EddyOS said:
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
Click to expand...
Click to collapse
So as long as you're stock recovery, and stock ROM, but s-off, it shouldn't have any bearing whether or not you upgrade ota... Right?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
EddyOS said:
It does 100% matter as otherwise the SU app/binary will still be present and potentially cause issue to the 'stock' ROM. Go look at the Desire forums all over the net for examples as to why you shouldn't flash an OTA onto a rooted handset
Click to expand...
Click to collapse
Ok I well look into this further when I get home from work. I have not looked at the Desire forums yet, bit I will later today. My question is though are the Desire users having to use the stock recovery, or has someone made a flashable .zip file for them of the OTA? If so this could have something to do with the troubles. Like I said I will check into this further this evening. I still say it should not as the kernel is replaced when you flash the OTA update, bit I could very well be wrong.
It's not that you can't do it, you can, it's just not recommended. By all means try it but should it go wrong flashing an RUU is all that would work
Sent from my Galaxy Nexus using xda premium
EddyOS said:
It's not that you can't do it, you can, it's just not recommended. By all means try it but should it go wrong flashing an RUU is all that would work
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I totally understand what you are saying, but flashing stock is not the only way to fix it, it is just the easiest and most user friendly way to fix it. It is pretty much a one click fix, and that is because of the RUU it self. When you flash via a RUU the utility runs a Task 28 on the NAND memory first meaning the NAND is totally wipped, meaning all partitions, before the ROM is flashed. Now you can also use ADB to remove and reflash all partitions,Splash 1(mtdblock0), recovery(mtdblock1), boot(mtdblock2), system(mtdblock3). cache(mtdblock4), userdata(mtdblock5).
Now back to the question about being rooted, I still have not got home yet to get on my computer to look at the desire forums. Now from what I know root is acheived on the kernel level cause that is what root is. It allows for direct communication with the kernel, again correct me if I am wrong. Now I understand that Superuser app binaries would still be present if you flashed just the system. But if you flash a whole new ROM wich is what the OTA update does, then the kernel is replaced with the kerneel in the OTA update, which by is either a completely new kernel or a modified kernel that HTC has made to work with ICS. I have not had time to look into wich one it is, but from my experience of trying to help port the SDK of ICS to the Sensation it is probably a completely new kernel.
Anyway I will have to do some research on the differences between stock recoveries and custom recoveries. Specifically the processes the recoveries run when flashing a ROM from SD card, and just what all is in the OTA update files. Once I get to do this I will be more able to give a hard core answer to this question. Oh and thinks to the EddyOS for helping to get me back into digging around in ROM files and learning more about how Android works.
Edit: I totally forgot to mention JTAG, this is another way that you could fix the problem, all be it sort of a major over kill for the problem, but still a fix.
Hello Everyone,
I'm fairly new to rooting phones and ROMs so if this question dosn't make sense please destroy my inner child I have a rooted sgs3 using odin and factory verizon build but the problem I am having is with ClockwordMod I think. The samsung update restarts the phone but ClockworkMod starts up right away and won't let the update go through. Is there a setting I need to change to allow all updates to bypass ClockworkMod or is there another way for me to get the update?
Any help is much appreciated.
Justin
Sounds to me like cwm just saved you from an auto ota update.
I use twrp so i dont know the answer to your question but if you're rooted, why would you want an ota?
Update
maniac2k said:
Sounds to me like cwm just saved you from an auto ota update.
I use twrp so i dont know the answer to your question but if you're rooted, why would you want an ota?
Click to expand...
Click to collapse
Hello and thank you for the reply. I'm not sure that I need/want it though it continues to ask me to update so it's either keep saying defer or just let it update.
Of you download and flash one of the latest and greatest roms, you wont get asked to update. There is a way you can stop the ota but i dont remember off the top of my head. Im sure google knows. I would just flash a newer rom that includes the update.
hmmmm
maniac2k said:
Of you download and flash one of the latest and greatest roms, you wont get asked to update. There is a way you can stop the ota but i dont remember off the top of my head. Im sure google knows. I would just flash a newer rom that includes the update.
Click to expand...
Click to collapse
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
ndjustin20 said:
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
Click to expand...
Click to collapse
Well I have beans 12 and woke up and my phone also was booted into recovery and stopped the update.
Sent from my SCH-I535 using Tapatalk 2
ndjustin20 said:
What would you say is the latest and greatest ROM and can I use odin to flash it? Also, if I flash a new ROM I lose everything that is on my phone right??
Click to expand...
Click to collapse
It is going to keep rebooting into CWM if you don't tell it to until you tell it to stop rebooting to recovery, which is an option in the menu system after flashing. If the OTA update installation is being intercepted by CWM's presence on your phone, then I'm not sure if there is a way around it other than flashing a ROM. Someone with more experience will have to chime in.
With that said, should you choose to install a new ROM, there are a plethora of ROM options on XDA, at least some of which have OTA updates disabled. See the following link for a guide (I'm assuming you are on Verizon):
http://forum.xda-developers.com/showthread.php?p=32079760#post32079760
You can flash the stock, rooted ROM back on with ODIN, and then download EZ-Recovery (which has CWM) and load a custom ROM that way.
I use aokp but jellywiz is a nice stock like rom. Just download a rom and flash in cwm.
ndjustin20 said:
Hello Everyone,
I'm fairly new to rooting phones and ROMs so if this question dosn't make sense please destroy my inner child I have a rooted sgs3 using odin and factory verizon build but the problem I am having is with ClockwordMod I think. The samsung update restarts the phone but ClockworkMod starts up right away and won't let the update go through. Is there a setting I need to change to allow all updates to bypass ClockworkMod or is there another way for me to get the update?
Any help is much appreciated.
Justin
Click to expand...
Click to collapse
If you want the update you should flash back to stock and restore the stock recovery. You can reroot and unlock the boot loader after you update.
Im having same issue. Verizion trying to force my phone to have less features. I was able to ignore it 2 weeks ago but now it keeps trying to force the update and I can keep delaying it. Any good tools you all know of to just block ota updates all together? Pretty happy with stock rom as is no need to fix it minus the copy and paste bug.
You can use Titanium Backup to freeze SDM 1.0 and the update will quit downloading. I'm not sure if freezing apps is supported in the free version but the paid version is well worth it of you plan on switching ROMs.
You could also flash Scotts stock rooted Rom with the latest update, then your phone status will say up to date. I flashed the zip right on my phone through cwm but I'm sure you can use Odin too
Sent from my SCH-I535 using xda app-developers app
I was in the exact same situation as you. The phone will not update with Clockwork Recovery installed. I simply flashed back to the stock ROM via ODIN (stock.vzw_root66 which a quick search should locate), accepted the OTA update, and then used the beginner's guide in the Android Development forum to get back root.
I use Titanium Backup to freeze SDM 1.0. Like JBO1018 wrote, the PRO version is well worth the price, if only to freeze bloatware. Everything else it offers is gravy.
Questions go in Q&A
Thread moved
Thanks