Database Info

[Q] Update always fails at 25%

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.

New 3.2 update bootlooping?

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..

[Q] resetting before ics ota?

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?

[Q] Unrooted stock bootloop - need help

Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?

iglu said:
Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?
Click to expand...
Click to collapse
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.

And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
You think it might be a result of ICS upgrade ?

iglu said:
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
You think it might be a result of ICS upgrade ?
Click to expand...
Click to collapse
Yes factory data reset only deletes all data on your phone not the SD card.
Sent from my Galaxy Nexus using xda premium

simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
Okay, so i did factory reset and i'm still stuck on the bootloop. Need to remove the battery and turn back on until it doesn't bootloop.
Actually what happens is the google logo appear, then for a moment it turned off and comes back again.
simms22, why do you think it's internal sd damage ?
TheMatrix246, what's ODIN ?

Guys, you think if i root and switch ROM it could be fixed ?
I would appreciate some help here a bit lost.

One last thing before you contact Samsung:
Download Nexus S [i9020T/i9023] 4.0.3 Full ROM and copy to sdcard as update.zip
Go into bootloader
Recovery
Data/factory reset
Install update.zip (reflash all files of ICS)
Reboot and hope it works out fine
If this doesn't work for you i highly doubt rooting and changing ROMs will. This will reinstall the entire OS (format and install /system), bootloader, radio, kernel and recovery.

Do i need to be root user in order to do that ?
And just to make sure, this Full ROM is for i9020T ? correct ?
(mine says only GT-i9020 on the back, bought in Carphone Warehouse in England).

Yes, i9020T. If you get 3G with Orange, and you have the SAMOLED screen, you have the i9020T (and to my knowledge, 9020 on the back signifies i9020T).
Also, i don't believe you need to be root to do that. I'm pretty sure you can flash the same version ROM from stock recovery as long as it is signed, just not older versions.

First, thanks guys for the help.
After first doing the factory reset, it seemed the bootloop happens less often. At first i tought it was solved but then it rarely (1 to 5 reboots) yet happened.
Today i installed the Full ROM Harbb suggested and so far i have no reboot issues.
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?

iglu said:
First, thanks guys for the help.
...
...
...
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?
Click to expand...
Click to collapse
You're welcome. Also, all that file does is replace everything in the /system partition (OS). All apps besides the defaults that come from the factory are not in that partition so are not affected. Hopefully your problem is fixed permanently

But it's generally recommended to do a full wipe when switching ROMs. It could be that you encounter other problems because of the ROM change without wipe. But you could also be lucky to have no problems. Just to remind you, when you encounter something wierd.

Problem is still there ....
Hi guys,
First thanks for all the help, but the problem still there.
I did the upgrade using the Full ROM as Harbb suggested. For the first 10-12 times i rebooted (i rebooted again and again) it was alright, booting successfully ... but then it stated occasionally to bootloop and now it does it almost everytime. usually takes up to 10 times i remove the battery and start the phone so it will start up and not bootloop.
Also, I'm sorry the taking so long to respond, the nature of the problem compelling me to test it for a few days so i will know if it works or not.
Should i root the device ?
If so , how do i replace / rewrite the boot program ?
I would much appreciate any suggestion.

I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.

BlatDinger said:
I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.
Click to expand...
Click to collapse
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?

iglu said:
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?
Click to expand...
Click to collapse
Most likely its a refurbished one, as is the way of sending devices for warranty
Sent from my ice cream powered Nexus S

Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium

BlatDinger said:
Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hey, thanks for the replay.
What does is mean to flash it ?
How do i do that ?
You noted it was returned unrooted, was it rooted before ?
Again thank you all for the help.

To be honest I'm a novice to these terms but know that they unlocked it(it was not unlocked when sent off) and reinstalled os 2.3.3 after a complete wipe. Details of how to unlock and flash (install a different os) are on the forums. If you follow the forum advice precisely the instructions work. I am now running a CyberGR rom of ics 4.0.3 that runs smoother than stock ics . Again found on these forums. Hope this helps.
Sent from my Nexus S using xda premium

T-Mobile Nougat Update Slow

Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis

I didn't. What I did have was bootlooping that started about 48 hours after installation. Stock, not rooted and very minimal apps. I ran a factory reset and it has been much better.

My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.

anbowlynn said:
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
Click to expand...
Click to collapse
( it was the same problem with my S5 from 5.0.1 to MM will never do same error save all yr data and do clean flash )
1- do just cache clean
2- you can flash the old MM tmb but dont flash csc flash HOME_csc
but wait for more suggestion but for me is that the only solution

hapakun said:
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
Click to expand...
Click to collapse
same. s7 slow and laggy as hell crappy battery life. they did this with the s5 too. slowed it down with updates until youre forced for a new phone.

This last update definitely negatively impacted my battery life. Stock, no root, and I wiped cache. I'm not in the mood to do a factory reset. Weasles.