Will I then be able to update the device using Kies/OTA? The logic behind the question is that I know the updates need the stock recovery, thus flashing stock with Mobile Odin will give that to my device.
If so, what are the risks in doing the updates with the root? Can it brick? Will it simply fail? What happens when Jelly Bean goes to roll out, will that pose a different set of risks for the device because parts of the core OS have changed?
Just trying to learn more, and figure out what my options are for my device.
PS my device is the P3113.
Just do whatever you want to do right now. When the officially released version of JB is available via Kies or over the air you can flash a stock rom and proceed to update that then. Secondly, I am sure someone will release a version of the stock officially released JB rom with some nice things added and root included once Samsung releases official JB.
You can always flash stock rom and use triangle awat to go back to the day that you purchased your tab with download screen (ODIN/Hiemdall) reset to normal.
bark777 said:
Just do whatever you want to do right now. When the officially released version of JB is available via Kies or over the air you can flash a stock rom and proceed to update that then. Secondly, I am sure someone will release a version of the stock officially released JB rom with some nice things added and root included once Samsung releases official JB.
You can always flash stock rom and use triangle awat to go back to the day that you purchased your tab with download screen (ODIN/Hiemdall) reset to normal.
Click to expand...
Click to collapse
I was trying to avoid having to flash over and over again, which is why I thought using Mobile Odin to flash stock, with root, would then give me the ability to OTA/Kies an update.
I guess I was wrong?
I mean if I have to do things the way you described above then I will lol but I was hoping for a simpler way to get the updates, and keep my root. I like the stock, just need to have my root, and don't want to deal with flashing every few months when they release an update/patch/fix/tweak.
I have flashed my devices over 100 times and with nightlies of cm10 for example, i may flash them daily, do not worry
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
I have flashed my devices over 100 times and with nightlies of cm10 for example, i may flash them daily, do not worry
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I am not really sure what to say to be honest, I always thought that there was a risk in doing these mods, and therefore, the more you do it, the greater the risk becomes.
It's also a convience factor for me, if I can just get the OTAs (while keeping my root) that would make me happy, but I also know there will be a UI patch coming out for it (or I assume there will be) and I will need that, and etc.
I was just trying to KISS (for anyone who doesn't know, Keep It Simple Stupid) since I like ease of use and simple .
So my plan is not possible and that sucks Oh well, live and learn! Thanks!
Flashed to stock with mobile odin now no wifi
i used the method on this thread http://forum.xda-developers.com/showthread.php?t=1856532 and i used everroot and now my tab keeps saying my wifi is too weak to connect when it shows full bars on the scan screen, idk if this is my individual problem or a problem with this method but i havent found a solution yet
Related
..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.
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
Updated my phone to the latest ROM over OTA. Since then, my gps takes forever to get a lock and even then, loses GPS connection frequently. Anyways, I'd like to downgrade my phone to that version. In the meantime I'll root this phone and try out the new jelly bean ROM.
So the question is, does anyone know where I can get a download of that specific ROM?
neurosis737 said:
Updated my phone to the latest ROM over OTA. Since then, my gps takes forever to get a lock and even then, loses GPS connection frequently. Anyways, I'd like to downgrade my phone to that version. In the meantime I'll root this phone and try out the new jelly bean ROM.
So the question is, does anyone know where I can get a download of that specific ROM?
Click to expand...
Click to collapse
Are you talking about the odin package for G7?
BraddahBoi808 said:
Are you talking about the odin package for G7?
Click to expand...
Click to collapse
Preferably cloclwork but odin will do. So far, I can only find the radio packages only. I'd like the entire ROM since this is affecting GPS.
neurosis737 said:
Preferably cloclwork but odin will do. So far, I can only find the radio packages only. I'd like the entire ROM since this is affecting GPS.
Click to expand...
Click to collapse
there are no full packages of stock roms for clockwork. The closest you can get would CleanRom by scrosler which runs amazingly smooth. If not, then you would have to go to invisiblek's goo.im account. he has the full odin flashable packages
1 - if you are rooted, you should not take any ota updates. Potentially this can brick your phone.
2 - for different modem builds, just download whichever version youd like (rootzwiki) and flash.
3 - for return to stock roms (unrooted), well, just follow one of the how-to sticky threads in the forum. Once youre back to stock then can receive ota without problems
download gps fix from playstore.
epagib said:
1 - if you are rooted, you should not take any ota updates. Potentially this can brick your phone.
2 - for different modem builds, just download whichever version youd like (rootzwiki) and flash.
3 - for return to stock roms (unrooted), well, just follow one of the how-to sticky threads in the forum. Once youre back to stock then can receive ota without problems
Click to expand...
Click to collapse
Taking a OTA when rooted will not brick the phone at all, you will just lose your root and will have to redo it. If you wanna go back to pure stock you can follow droidsytles post in section 6 and odin back to G1 then ota upto G7. Its really simple the way droidstyle explains it and only takes about 8 mins give or take.
Sent from my SCH-I535 using xda app-developers app
x714x said:
Taking a OTA when rooted will not brick the phone at all, you will just lose your root and will have to redo it. If you wanna go back to pure stock you can follow droidsytles post in section 6 and odin back to G1 then ota upto G7. Its really simple the way droidstyle explains it and only takes about 8 mins give or take.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Worked a charm.
Over the past month or so I have tried several times to update my S3 with the Jelly Bean update from Verizon. Each time I try it I get a message that the software failed to install.
O I need to unroot the phone and lock the bootloader in order to update? Anyone else had this problem? Right now I am on Android version 4.0.4 and I think the update is 4.1.2.
I believe for the official update you have to be unrooted and have a locked bootloader unless you do it from kies where it can revert it complete to stock and unroot it.
Sent from my SCH-I535 using xda app-developers app
djteotancolis said:
I believe for the official update you have to be unrooted and have a locked bootloader unless you do it from kies where it can revert it complete to stock and unroot it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You are 100% correct. Update will fail due to custom recovery. OP, why not download one of the many JB ROMS from the development section and flash it? Not only will it update your phone, it will be much better than stock as well as easier to install.
HHF2 said:
You are 100% correct. Update will fail due to custom recovery. OP, why not download one of the many JB ROMS from the development section and flash it? Not only will it update your phone, it will be much better than stock as well as easier to install.
Click to expand...
Click to collapse
I have not yet ventured into flashing other ROMS but am certainly willing to give it a try. I know there are many available but can you suggest one or two that i can try.
Really tough to suggest a ROM, there are a lot of different options depending on what you are looking for. Clean ROM is pretty much stock that has been optimized, I would probably start there since you have only done stock. You can then make a nandroid and flash other ROMS and see which one you like the best.
Just remember, read all of the stickies so that you have everything backed up in case something goes wrong. It takes less time to read and learn it before you have a problem and then don't have what you need to fix it nor the know-how.
Okay, so I download a ROM zip file. I copy it to me microSD card. I have TWRP on my phone. I assume I just go into recovery mode, wipe the cache and Dalvik cache and then just install the zip via TWRP. Is that all I need to do?
Never mind. I just flashed the Jelly_Beans10 ROM and it works fine.
I need to send my Blaze in for warranty work. This is what I've done so far.
Reset the flash counter http://forum.xda-developers.com/showthread.php?t=1955273
Used Odin to return to stock http://forum.xda-developers.com/showthread.php?t=1591601
Reset to delete data
Right now my Blaze is back to running 2.3.6. I have already told the warranty department that I updated to 4.0 using KIES. Samsung is obviously expecting me to do a reset before sending it in, but I assume that if I was running 4.0 and did a reset it would still be on 4.0.
Should I update to 4.0 before sending the phone to Samsung or should I leave it at 2.3.6? If so, how? Right now I'm getting a message from KIES which says Your device's current firmware version is not supported to update firmware via KIES
Should I use Odin to update to a different version that I can download from Sammobile.com? If so, does anyone know which version I should use?
Any help that anyone can offer would be great. I don't want to raise any red flags when I sent it in to Samsung. Thanks.
d73805 said:
I need to send my Blaze in for warranty work. This is what I've done so far.
Reset the flash counter http://forum.xda-developers.com/showthread.php?t=1955273
Used Odin to return to stock http://forum.xda-developers.com/showthread.php?t=1591601
Reset to delete data
Right now my Blaze is back to running 2.3.6. I have already told the warranty department that I updated to 4.0 using KIES. Samsung is obviously expecting me to do a reset before sending it in, but I assume that if I was running 4.0 and did a reset it would still be on 4.0.
Should I update to 4.0 before sending the phone to Samsung or should I leave it at 2.3.6? If so, how? Right now I'm getting a message from KIES which says Your device's current firmware version is not supported to update firmware via KIES
Should I use Odin to update to a different version that I can download from Sammobile.com? If so, does anyone know which version I should use?
Any help that anyone can offer would be great. I don't want to raise any red flags when I sent it in to Samsung. Thanks.
Click to expand...
Click to collapse
Do whatever you want... All they do is a root check and boot it once. If even that. They are looking for cracks and other things you may have left out.
I've sent back 4 phones now, all were rooted and customized. Only 1 did I do what you did. The rest I said F it. They didn't care because nothing was wrong with it hardware wise. ||
they just Re-flash their stock on it and go from there. Keep in mind they can always check. Just is super rare. You are good. They don't care what version it is as long as it's stock.
(also that count reseter doesn't reset the custom binary, they still will know you installed a custom recovery)
That's good to hear. I ended up using the August 2012 from sammobile.com then used KIES to update to 4.0. Hopefully everything works out.
chjema said:
Do whatever you want... All they do is a root check and boot it once. If even that. They are looking for cracks and other things you may have left out.
I've sent back 4 phones now, all were rooted and customized. Only 1 did I do what you did. The rest I said F it. They didn't care because nothing was wrong with it hardware wise. ||
they just Re-flash their stock on it and go from there. Keep in mind they can always check. Just is super rare. You are good. They don't care what version it is as long as it's stock.
(also that count reseter doesn't reset the custom binary, they still will know you installed a custom recovery)
Click to expand...
Click to collapse
chjema said:
(also that count reseter doesn't reset the custom binary, they still will know you installed a custom recovery)
Click to expand...
Click to collapse
Reset counter doesn't reset the custom binary, but Odin flashing a stock firmware will.
Also this belongs in General.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Questions go in Q&A
Or General section when no Q&A exists
Thread moved
I have reset flash counter and I have gotten it to say IM running Samsung official but I still have a custom recovery...will they care?
Sent from my SGH-T769 using xda app-developers app
Jserrano56 said:
I have reset flash counter and I have gotten it to say IM running Samsung official but I still have a custom recovery...will they care?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
from what I've heard (and take that with a grain of salt, because I have no personal experience, dont hit me if I'm wrong), they dont care if you have a customer recovery, as long as you have Samsung Official binary with 0 flash count (and often times the flash count is ignored).
Well IM also running a stock ROM... You can't tell the difference only way I could get it to ICS to use triangle away since kies wouldn't recognize my device
Sent from my SGH-T769 using xda app-developers app