Related
it keeps telling me there's a tmobile software update, but when i try to update, it restarts the phone and goes into clockworkmod recovery and then i just exit back to the phone and nothing happens.
how do i update it or just turn the notification off?
Download 2.3.6 stock ROM (http://forum.xda-developers.com/showthread.php?t=1391174) and update via odin. I did same thing.
it wont erase my data won't it?
DeathBlimp said:
it keeps telling me there's a tmobile software update, but when i try to update, it restarts the phone and goes into clockworkmod recovery and then i just exit back to the phone and nothing happens.
how do i update it or just turn the notification off?
Click to expand...
Click to collapse
You cannot updatee if you are rooted. If you dont want to update, I believe you can freeze the notification using BloatFreezer or similar. If you do want to update you can either (1) do so via Kies or (2) un-root and then update ota. Either way you will be unrooted and have to re-root
i did update to 2.3.6 when i received the OTA and I click update and realize that i am rooted (root using superoneclick). I let the update goes through and after few minutes, my sgs2 is updated to 2.3.6 with wifi calling and great battery life. I think i will stay stock rooted until Nick (dev for Miui vibrant) made Miui for SGS2
Edit: Like everyone said, every phone is not created equal. Like mine, got updated even its rooted
samdobbs said:
You cannot updatee if you are rooted. If you dont want to update, I believe you can freeze the notification using BloatFreezer or similar. If you do want to update you can either (1) do so via Kies or (2) un-root and then update ota. Either way you will be unrooted and have to re-root
Click to expand...
Click to collapse
I tried an app called voodoo OTA rootkeeper, I got it to temp-unroot my phone but after a restart it went into clockworkmod recovery. i restarted it again and it went back into unrooted mode.
i also cannot find bloatfreezer on android market.
bikrame said:
Download 2.3.6 stock ROM (http://forum.xda-developers.com/showthread.php?t=1391174) and update via odin. I did same thing.
Click to expand...
Click to collapse
thanks, but where do i get the PIT file? or do i need one? would i also need to re-partition? i dont see those information in that thread
DeathBlimp said:
thanks, but where do i get the PIT file? or do i need one? would i also need to re-partition? i dont see those information in that thread
Click to expand...
Click to collapse
You just need one file. I am at work now. i will go home and check and write details tomorrow.
Sorry .
Sent from my SGH-T989 using XDA App
Look at Page 13 of same thread. There is full description.
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Diger36 said:
Are you sure you are not in standard recovery mode? When the droid appears: push Volume up+power and you should have the stock recovery mode...
Click to expand...
Click to collapse
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Chaosblast said:
I'm sure. When the droid appears (I've attached the image) it doesn't respond to any button. I've tried V.up + Power, V.down + Power, and V.up+V.down+Power. Nothing happens.
I have ClockworkMod installed, version 5.5.0.2.
Click to expand...
Click to collapse
Now that IS weird. The screenshot you took is indeed the screen you get in Stock Recovery and pressing Volume up + Power simultaniously should bring you into the recovery menu.
If not: I'm afraid this problem is over my head. Sorry about that... Maybe anyone else?
Chaosblast said:
I have an error updating with the OTA 4.0.2. GSM Galaxy Nexus.
I have only my phone rooted, and no Wallet installed or something. The error it's only that when the device restarts, it starts the installation, and then a "dead" Android appears with an exclamation sign on it. It fully block the device, and I have to put the battery out and restart.
I have tried so many times, each time OTA comes up.
Some help? Thank you.
Click to expand...
Click to collapse
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
jd1001 said:
You can use OTA updates when your phone is rooted. When you try to install the OTA update it looks for the stock bootlader. Because you have rooted the install wont complete when it gets to your modded bootloader.
The only way to update is put a 4.0.2 or 4.0.3 rom on your sd card and flash using CWM.
Click to expand...
Click to collapse
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
Diger36 said:
Is that true? Even if you didn't install CWM, are on Stock recovery and all you did was unlock fastboot and root the phone? I guess then you should be able to install the OTA updates flawlessly or am I wrong?
Click to expand...
Click to collapse
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
jhuynh said:
Unlocked bootloader doesn't prevent OTA updates.
---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------
If all you did was unlock the bootloader and root and didn't install CWM recovery, different modem or anything else like that than you should be able to do the OTA.
Click to expand...
Click to collapse
Oh ok I thought that was the issue! So it's when you install a custom recovery that the OTA updates won't work. Sorry for the incorrect info.
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
danger-rat said:
Having a custom recovery allows you to flash packages that are not signed by the same party as the ROM on your phone. What this means is that if you don't have a custom recovery, you can only install updates from your ROM signer. Pure yakju builds are released from Google. The other yakju derivatives are carrier and OEM releases.
AFAIK, only Google (yakju) has released the 4.0.2 update for GSM, so you can only install the update on yakju if you have a stock recovery. If you have a custom recovery you have the option to bypass the signature verification process...
Click to expand...
Click to collapse
Thanks for that. I got bootloader and recovery mixed up!
Thanks all of you guys. That should be the problem. Then I delete the CWM and then update with the OTA. Then I reinstall the CWM and that should be fine.
It's weird because I my cousin has installed the OTA, and he had also rooted his Galaxy Nexus, and I think he also changed the recovery.
Anyway, it's good to know. Thanks again.
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
danger-rat said:
I don't think you understood me:
Having CWM let's you flash the update, but you may have to turn off signature verification to do so.
The problem is, the update has only been released for the yakju firmware, so if you want the update you probably want to make sure that you have the yakju firmware installed (use Android System Info or similar app).
It's possible that the update can be forced to flash on other non-yakju builds, but I can't say for sure...
Click to expand...
Click to collapse
I don't want to flash any update via CWM for now. I prefer doing that by the official way until I see some ROM that I like.
I understand what you mean of the firmware. But I think I haven't changed the firmware. I mean, I have only unlocked the bootloader, rooted, and then installed CWM. I don't think that changes my firmware.
By the way, I have installed Android System Info, and checked it. But I don't know how to stay sure. I have attached the screenshot.
Thank you.
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
danger-rat said:
Understood.
Looks like you have yakju...
If you want the update to auto install, then yes, you will need the stock recovery.
Personally, I find it easier to flash the update manually than to switch recovery...
Click to expand...
Click to collapse
It's true, but where can I find the exact update (not the full ROM) in a zip package? I don't know how to get it from the OTA, and didn't find it on the forum either.
I want to be sure it's the correct update for my version and only the 4.0.1 to 4.0.2 package.
Bump! Could you answer my last question? It's the last one and all this thread is done.
Thank you.
I have exactly the same problem that Chaos, i tried to do the same as you told him but the problem persist, each time that i try to upgrade 4.04 by OTA it stopped and appair the android with the red exclamation on it.
I have the Nexus rooted and the stock recovery flashed
I'm running the JB 4.1 version that was released with the dev units during Google I/O -- Now it's constantly telling me to update, and when I update, it fails.
Now, I want to "upgrade" to a CM 10 nightly.
Do I have to wipe and install or can I just install?
If you want to go to CM10, you need to 100% wipe that device before installing.
If you want to try and diagnose the issue you're having taking the OTA to 4.1.1, we can work through that too.
Alright. What do you need to know?
iFargle said:
Alright. What do you need to know?
Click to expand...
Click to collapse
To try and accept the OTA?
How did you install this 4.1? Did you flash the proper radio with it? Do you have a custom recovery? Are you rooted? Have you changed or uninstalled any system apps? What error do you get (what happens) when you try to accept the OTA?
We need to know what you flashed... Did you just flash the ROM or flashed radio, bootloader and recovery for that variant? If you didn't flash them, you gotta do it. If not, you can't update.
However, if you did flash everything, just flash them one more time just to make sure. Sometimes, people get confused and flash wrong version of radio and stuff...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
iFargle said:
I am rooted and unlocked, yes. I installed this 4.1 image using clockworkmod recovery. I don't even know what a custom recovery is, so I assume I do not have one of those.
Ah, I did disable one system app -- Google Play Magazines. As soon as the update popup comes back I will try again... Since now when I go and click on the check updates button it tells me I'm up to date, even though it's still 4.1.
Click to expand...
Click to collapse
Disabling any apps wouldn't matter. However, you just said that you have Clockworkmod, right? If it's, there's your problem. Flash stock recovery and you should be good to go
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
I've been a long time lurker, first time post.
I have been running the official AT&T ICS release I927UCLH2, and was notified of an update for my phone from Device Management. I am now updated to I927UCLJ3 baseband. To my surprise, my keyboard backlight is now working. So far, everything looks good. There is no sign of this update on the Samsung ICS page. Maybe AT&T is just going to push it out and forgo Kies altogether? Who knows?
GrepACE said:
I've been a long time lurker, first time post.
I have been running the official AT&T ICS release I927UCLH2, and was notified of an update for my phone from Device Management. I am now updated to I927UCLJ3 baseband. To my surprise, my keyboard backlight is now working. So far, everything looks good. There is no sign of this update on the Samsung ICS page. Maybe AT&T is just going to push it out and forgo Kies altogether? Who knows?
Click to expand...
Click to collapse
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
PacoL250 said:
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
Click to expand...
Click to collapse
Seconded here. Do we have to remove CWMR in order to update from the new OTA update?
I just got a software push from AT&T for my Captivate Glide. After the restart, the keyboard lights now work! About phone says: Android v. 4.0.4. Baseband v. I927ULCLJ3. Build number IMM76D. I'll see if other things have been fixed like, ringtones that stop working and clock being x time slow. Both of which required a system restart
Gizmokid2005 said:
Seconded here. Do we have to remove CWMR in order to update from the new OTA update?
Click to expand...
Click to collapse
I reloaded the stock recovery from my LH2 install and tried the OTA update. It downloads the update but fails to install with an "Update Failed" after the reboot.
I never rooted my phone only installed CWM for the Keyboard fix and to backup with CWM. Wish I had never installed CWM now.
Just got off the phone with AT&T myself, the rep said it should be available on Kies, they want me to try the new firmware before they'll continue warranty procedure on my wife's glide.
Edit: Well it's not, but it should be soon I guess.
Second Edit: On phone with samsung, they say the update is still "on hold" on his system. At&t told me to call them if I needed help with the firmware update.
Thanks for the info. Kies kept crashing on me so could not try it and OTA says I need to way 24hrs to try again.
Will try Kies on a second computer.
Is there any way to reset the 24hour AT&T update time without erasing the data partition?
PacoL250 said:
I get notified too; however because I have CWM installed, it interrupts the installation and I can't install the update.
Any thoughts on what to do to get it installed?
Click to expand...
Click to collapse
Gizmokid2005 said:
Is there any way to reset the 24hour AT&T update time without erasing the data partition?
Click to expand...
Click to collapse
I was able to flash back to the 4.0.4 default ROM from samfirmware and then disable automatic time update and move my day ahead one.
Official update get!
Gizmokid2005 said:
I was able to flash back to the 4.0.4 default ROM from samfirmware and then disable automatic time update and move my day ahead one.
Official update get!
Click to expand...
Click to collapse
I might have to try something similar since Kies nows says that "You device does not support upgrading via Kies". Since I did not root my phone it must either not be happy with the flashes I have done to recovery even though I have flashed back to stock recovery or the Keyboard fix I did.
This blows.
does anyone know if i flash with a stock AT&T from sam firmware on a Rogers i927(r) will I be able to update to the new AT&T version on Kies ?
VideoRoy said:
I might have to try something similar since Kies nows says that "You device does not support upgrading via Kies". Since I did not root my phone it must either not be happy with the flashes I have done to recovery even though I have flashed back to stock recovery or the Keyboard fix I did.
This blows.
Click to expand...
Click to collapse
Success!!
Here are my steps:
1. Restore a backup I made with CWMR before when I first installed it before making any mods.
2. Reinstall stock Recovery before doing anything else.
3. Get OTA update even though less than 24 hours since I restored a previous point in time.
Doing the stock ROM was my second choice but since I had a backup at least most of my apps and settings were recovered.
Good luck!
2.3.6 phone says no OTA update. I'll try Kies later.
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
is there someone who would upload it somehow, so I could flash it via ODIN, or something? I cannot update OTA, cause I live outside the US and at&t doesn't reach this destination. . .
Can somwone post the stock LH2 recovery please?
Sent from my SGH-I927 using xda app-developers app
SamMobile download link
This ROM version is downloadable from SamMobile Firmware Page:
link
Downloading is in progress.
You can flash this with Odin.
Is this the same as before with Samsung Touchwiz for the homescreen ?
yohan4ws said:
Is this the same as before with Samsung Touchwiz for the homescreen ?
Click to expand...
Click to collapse
Yes it is essentially the same, but all the things that were wrong are supposedly fixed
Sent from my SGH-I927 using xda premium
How do I root this ?? I have CWM installed on it but am not sure where to get a CWM zip to install SU...
I found an odin flashable I927UCLH2.md5 and used it, and when into settings, about phone, software update, and it gave me an update and I'm downloading it right now.
The phone is now at I927UCLJ3. So AT&T can OTA push it instead of trying to force the phone to work with kies
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
You're rooted, which means you edited the system, which means the OTA probably won't install. Always better to go back to 100% stock and re-root
ftrack said:
Hi,
I have rooted Stock 4.2.1 Jelly Bean Build number JOP40D, I got software alert 5 days back its successfully download and then after click on restart and install button mobile reboot in TWRP mood and stuck by giving me some error related to partition, image file not found etc etc..
I had tried this 3 to 4 times but same error.
Please help me how to install it on the air.
Just for info i have upgraded my Gnex from 4.1.1 to 4.2.1 using Wug's Nexus Root Toolkit v1.6.2.
Please help me.
Click to expand...
Click to collapse
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
Huh.. I've received JDQ39 ota, I forgot to remove TWRP before hand, but it still went through anyway. It installed fine, surprised the hell out of me actually. TWRP 2.4.1.0. Didn't have any other mods though. Not even rooted.
Sent from my Nexus
Petrovski80 said:
You cannot install an OTA update unless you are 100% stock. You have TWRP recovery, thus not 100% stock. That's why it fails. Either flash back stock recovery and retry, or simply apply the update manually using this guide: http://forum.xda-developers.com/showthread.php?t=1419170
Click to expand...
Click to collapse
you can definitely install the OTA with a custom recovery. it however will not install if you modified any /system files, bootloader or radio do not match.
Oh really? That surprises me honestly. Although I never tried it, I always assumed every partition needed to have unmodified stock files (adding extra files does not matter). Apparently the recovery partition is an exception.
Petrovski80 said:
Oh really? That surprises me honestly. Although I never tried it
Click to expand...
Click to collapse
+1
I was really surprised, in a good way! xD