i am confused whether i should reset my phone before downloading the ota update of ics? I know u dont have to and ota updates do not generally wipe any apps or data but i was wondering if resetiing ur phone will make a big difference?if so in what is it different to just downloading the ota without resetting the phone?
And finally...IS RESETTING WORTH IT? if it doesnt make tht much of a difference i would rather not reset.
Thanks guys.
How about waiting until the OTA is actually out? At this point, nobody knows.
Personally, I'm going to install from scratch. It's a major jump in versions, and I've messed a lot with my NS since I got it in January.
shrivelfig said:
How about waiting until the OTA is actually out? At this point, nobody knows.
Personally, I'm going to install from scratch. It's a major jump in versions, and I've messed a lot with my NS since I got it in January.
Click to expand...
Click to collapse
yea good point, anyway ive decided im just gona download from scratch as well but backing up all my apps and data properly first so i can restore later without havinng to mess my phone out with the huge change in version.
I'll be installing from scratch to guess thats the safe way
here i am already flashed to stock and waiting for the update..
Is it safe to accept the ota (when it actually comes...) with an unlocked bootloader?
Related
So I waste half of my data plan (which isn't supposed to be charged for OTAU anyway) and when it reboots it gets to 25% and says failed. And then I don't get the update, and my phone is still a half-working piece of ****.
Why does it do this? Is it because of root?
Do you know which update it is?
I don't know, but it's about 19.2MB and it eats my data (of course it does, you NEVER trust anything ATT says) and I can't use mobile data at all after trying it without rediculous overage fees.
I'm just worried I won't be able to get the GB update when it does come out...
Naphthoylindole said:
I don't know, but it's about 19.2MB and it eats my data (of course it does, you NEVER trust anything ATT says) and I can't use mobile data at all after trying it without rediculous overage fees.
I'm just worried I won't be able to get the GB update when it does come out...
Click to expand...
Click to collapse
When GB comes out, if it really does, it won't be such a small update.
Check with AT&T 'cos OTA updates are not supposed to be charged, and you can talk to them and have them rolled back if you are sure they are from OTA update.
had the same problem use gtg unbrick it restores with out root and update will install you cant just unroot because it will do the same the udate is the h1 modem
So just wait for the GB update since it's the only thing that matters and then backup, unbrick, and update?
Also, you're saying that this is caused by root, correct?
And if it is caused by root, I'm pretty sure just doing a factory reset would fix it, and take a lot less time.
I had the same issue when I used the ucke3 firmware in Odin to return to stock because it was already rooted. You can unroot it using superoneclick then but it will probably still fail. Or you could flash, in Odin, uckd5 which is not already rooted that's what I did. Once I returned to stock I also did a factory reset and the update went thru perfectly.
yes it is caused by root and no a factory reset will wipe data but i think it doesnt effect root not sure about that though
jerrycoffman45 said:
yes it is caused by root and no a factory reset will wipe data but i think it doesnt effect root not sure about that though
Click to expand...
Click to collapse
I'm 100% sure it does...
Alright thanks everyone.
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
Hi all,
I used Titanium Backup to remove bloatware apps from my rooted 6210. Will this modification affect the ICS update? will it give me an error message or will it just install these bloatware apps back? Thanks in advance!
PS I heard the update is coming in September...LOL
To be safe I would recommend that you reinstall all the apps you uninstalled. I mean, it should be ok, but I always like to be safe rather then sorry..
And September 2013 got it
vamp6x6x6x said:
To be safe I would recommend that you reinstall all the apps you uninstalled. I mean, it should be ok, but I always like to be safe rather then sorry..
And September 2013 got it
Click to expand...
Click to collapse
Not this. When ICS comes along you'll want to do a complete wipe and start from scratch. The process of rooting should prevent OTA updates, so if you want the stock ICS you'll have to unroot first. I'll wait it out for someone to build rooted ICS builds.
Dunno if that will hold for the SGT+. Previous devices I've gotten on rooted devices just broke root. (TF101 comes to mind) Could be different for Sammy. But then we all did full backups before rooting....right?
I think that it will not matter what you have installed or uninstalled. M major updates like those will wipe everything and probably could not be done on OTA.
I would advice to do backup of your personal data only. If you restore a full backup of hc on ics you will got a bootloop.
Root should not prevent updates at all, but we will lose it. But probably we can use the same steps to take it back an the same update file.
Sent from my MB525 using Tapatalk 2
You'll have no problems updating through Kies but it will wipe everything. Not sure if an OTA will even be put out for those who bought it through a carrier or if everyone will have to update through Kies. I believe AT&T is forcing everyone to update their GSII to ICS through Kies. We will also most likely lose the ability to root until someone fixes it in ICS which shouldn't take too long.
jesusdiedforyourroms said:
Hi all,
I used Titanium Backup to remove bloatware apps from my rooted 6210. Will this modification affect the ICS update? will it give me an error message or will it just install these bloatware apps back? Thanks in advance!
PS I heard the update is coming in September...LOL
Click to expand...
Click to collapse
based on my experience, it doesn't matter what bloatware you delete, it'll all be back with a vengeance in the update. Things related to your apps and data shouldn't be wiped, but you will lose root and have to wait for the talented folks here to figure out how to re-root.
So, I got a factory reset after the latest update on my Tmo One S. It has been previously rooted and I dinked around with a few custom roms before reverting to stock and relocked.
Anyone else have this happen? I was a little pissed to say the least after loosing all my apps and text messages. Thankfully none of my pictures was lost.
What the hell happened to the JB update? Europe and Asia gets it but not the US?
Strange
Mooncalled said:
So, I got a factory reset after the latest update on my Tmo One S. It has been previously rooted and I dinked around with a few custom roms before reverting to stock and relocked.
Anyone else have this happen? I was a little pissed to say the least after loosing all my apps and text messages. Thankfully none of my pictures was lost.
What the hell happened to the JB update? Europe and Asia gets it but not the US?
Click to expand...
Click to collapse
I can understand your pissed but this is strange.. and im confused? you did a factory reset or did it happen by itself? And yeah bro im with you on the JB ****.. I had this Phone For Like 8 or 9 Months.. And the Guy at tmobile told me we have jelly bean coming out.. ****ing liars.. Still No jellybean..but rather they release this wack update with only updates the raidoo.... Comon Tmobile... Ya Slackin...
Factory reset
ParamjotSingh1989 said:
I can understand your pissed but this is strange.. and im confused? you did a factory reset or did it happen by itself? And yeah bro im with you on the JB ****.. I had this Phone For Like 8 or 9 Months.. And the Guy at tmobile told me we have jelly bean coming out.. ****ing liars.. Still No jellybean..but rather they release this wack update with only updates the raidoo.... Comon Tmobile... Ya Slackin...
Click to expand...
Click to collapse
It does a factory reset on its own. I had relocked mine and pushed the 2.35 ruu and saw that even after all updates the final ota 2.35.12 does an auto factory reset . Now i am in process of rerooting.
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
simms22 said:
the camera deamon itself is not a bug, itll show up if you use the camera. what was a bug is that it continued to drain battery after the camera was used.
Click to expand...
Click to collapse
But this is showing up after rebooting, and I haven't used the camera for a few days. I also don't have any apps like skype that may be accesing it. Maybe I'm just being paranoid though.
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
rootSU said:
I always recommend wiping when updating Android versions. The Same principles as custom ROMs actually apply to stock too. Of you have bugs, rule out your data and legacy settings first by wiping data
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
iJimaniac said:
Yeah, I know it's a good idea, but I'm always hesitant to do so since my internet speed is around .25 mbps. Redownloading apps takes a looong time. I suppose there's always backup solutions though.
Click to expand...
Click to collapse
Yeah you can use helium.
Sent from my Nexus 5 using Tapatalk
No issues here
iJimaniac said:
Hello, am I the only one experiencing bugs that I didn't have before since upgrading to 4.4.3?
To be specific: I never had the mm-camera-daemeon bug before updating, now I see it in the battery statistics! I thought 4.4.3 was supposed to fix this, not introduce it for people who previously didn't have it.
Also, this might just be me, but the speaker and headphone volume seem quieter than before, which again, I thought this bug was supposed to be fixed.
I installed the factory image from google with fastboot, but didn't wipe the data.
Any thoughts?
Click to expand...
Click to collapse
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
movielover76 said:
I have no issues, but I waited for the OTA and sideloaded it because I didn't want to wipe my data.
Dirty flashing is almost always a bad idea, if you have problems your just going to have to reset your device.
Yet everyone insists on doing it because they can't wait a day for the OTA to drop
Happens every time there's a new Google version put out, tons of people with issues because they dirty flashed the factory image.
Lesson
Wait for the OTA to sideload or install the factory image and let it reset your device as it's designed to do.
Click to expand...
Click to collapse
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Modified system
iJimaniac said:
Actually, I flashed it because I had modified the /system partition and my limited understanding of how Nexus devices update told me the ota wouldn't work with a modified system. Is this correct, or does the modified system only keep your device from receiving the ota, not sideloading it? This is the first device I've had that actually receives official updates, so I'm new to this.
Click to expand...
Click to collapse
If your not stock your right, the OTA will likely fail. You can get away with being rooted, you'll just lose root.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
It's part of the price that comes with tinkering with your device.
movielover76 said:
If your not stock your right, the OTA will likely fail.
Unfortunately everyone wants to get away without clearing and reseting their device and it leads to problems when people dirty flash the factory image.
If your not stock and want the latest update, your best bet is to bite the bullet and install the full factory image the way it was intended.
Clearing the device at the same time with the factory image, or installing one of the pre-rooted roms that comes out shortly after the new version drops. (Again clearing user data)
Click to expand...
Click to collapse
Alright, good deal! Now I know for next time, thanks