I reverted back to stock yesterday to receive Jelly Bean update but it says my phone is up to date.
I flashed recovery, locked the bootloader and used RUU 1.29
I'm TMobile UK CID005
When the phone rebooted update 4.0.4 came though, I downloaded and updated the phone to 2.17
No more updates are coming through however. I'm not sure if I flashed stock recovery or not (If I didn't would have update above come through?). Anyway can I reflash the stock recovery just to be sure? And how would I go about this? Also I have a custom Kernal if that makes any difference? Cheers
if you run the ruu then you're on stock already. maybe there's still no JB update for your CID.
robchongke said:
if you run the ruu then you're on stock already. maybe there's still no JB update for your CID.
Click to expand...
Click to collapse
I just unlocked my phone and the 1.25mb update came throught followed by JB. Strange
cassas00 said:
I just unlocked my phone and the 1.25mb update came throught followed by JB. Strange
Click to expand...
Click to collapse
maybe because you're still on stock rom.
Sometimes the updates won't show automatically, if you return to stock in ways like this. its recommended to check manually in the settings menu for updates .... consider this as a small "bug"
Related
hi guys ihave an strange issue iwas using stock yakju 4.0.2 getting the update via ota
but after root and flash another rom idecide to come back to stock so via odin icame back to 4.0.1 thinking that iwill recieve the update directly ! but ididnt !! is there any problem or ?google stopped the ota update !!
From what I know, you have to have the bootloader locked. With it unlocked you won't receive the OTA. I maybe wrong though...
yes you are right but if you came back to 4.0.1 via odin the bootloader will automaticlly locked ! as i know and the unlock image which is below google type when i open the device dissapear so iguess that already locked
You can get the OTA with an unlocked boot loader but make sure you have the stock boot loader and radio as well as the ROM.
Sent from my Galaxy Nexus using xda premium
the problem is im not getting it dunno why so do you guys recmmend to unlock root the device and just flash any thing i want due to recovery !? and which is faster flash update due to recovery or getting ota updates ? from your experience
Did you flash a YAKJU image? Not everyone with the YAKJU** image have gotten the update, so be sure to check which one you have (should say in build.prop i believe or any system info app).
Also, why'd you use ODIN? Just use fastboot to flash the stock images Google provide
I think not everyone receive the OTA update from Google
Maybe 10 minutes after getting my Nexus i got the notification to update to 4.0.2. Mine was yakju out the box. Booted device up for the first time and my Nexus was in Japanese.
I always get the 4.0.2 OTA when i restore the phone to stock ITL41F.
I restored my phone today again and i dont recibe OTA update, seems to be disabled the OTA updates.
Maybe Google is changing something? who knows XD But i´m pretty sure that something happens with the OTA updates for yakju since yesterday.
PD; sorry about my english... XD
I'm still stuck on 4.0.1 on mine, and it came with yakju...so maybe the update still hasn't finished rolling out? Anyone have any other thoughts?
VVV850 said:
From what I know, you have to have the bootloader locked. With it unlocked you won't receive the OTA. I maybe wrong though...
Click to expand...
Click to collapse
You are indeed wrong.
Shieze said:
You can get the OTA with an unlocked boot loader but make sure you have the stock boot loader and radio as well as the ROM.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Stock bootloader? There is no other kind at the moment. And besides, it does not affect anything. Stock radio? Again, all radios available at the moment are stock. I think what you meant to say was the yakju radio. Although it is needed to install the OTA update, it will not affect you getting notification of an OTA update if you are using a radio that comes from a different stock build other than yakju.
Huntlaar said:
the problem is im not getting it dunno why so do you guys recmmend to unlock root the device and just flash any thing i want due to recovery !? and which is faster flash update due to recovery or getting ota updates ? from your experience
Click to expand...
Click to collapse
Yes, I would recommend flashing the latest yakju image (if you don't mind wiping, as unlocking the bootloader will wipe your device). See link in my signature for how to flash to the latest yakju version.
fryhole said:
I'm still stuck on 4.0.1 on mine, and it came with yakju...so maybe the update still hasn't finished rolling out? Anyone have any other thoughts?
Click to expand...
Click to collapse
No one knows the logic behind how updates are pushed out. Just flash the latest build, or update your current build (if your bootloader is unlocked). See link in my signature for how to update your build.
thank you guys especially efrant for your advise ijust rooted and unlocked my gnexus and flashed the last google image using tooklit so easy
I recibe the OTA update one hour ago, the problem with OTA updates is solved.
Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?
benzso63 said:
Today I received the new update message, last time it tried to install it itself after 3 times postponed. But for for reason it failed. Is it because the phone is rooted ?
What if AT&T release the Jelly bean update in the future and I want to install it. How do I fix the update error message? Do I need to un-root the phone first ?
Click to expand...
Click to collapse
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?
AlwaysNoob said:
+1. I also have stock LEM firmware and I am rooted(everything is stock though). When I try to update to LG1 via OTA, it downloads the update and reboots in CWM and fails to update. When I plugin via Kies to update, it times out.
Is there any way to update to LG1 when you are rooted?
Click to expand...
Click to collapse
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?
saj222 said:
Correct me if I'm wrong but it should work if you have the stock recovery - which in your case you don't but not necessarily in the OP's case. Unless the OP wasn't perfectly clear.
Maybe you need to go back to stock first?
Click to expand...
Click to collapse
Is there any way I can remove CWM and go back to stock recovery? I rooted my phone using this easy guide http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am not worry about the minor update from AT&T, we all expect to get Jell Bean soon. Just want to make sure we can download the update and install it properly without any errors. So should we go stock? What will be the steps? Download the stock firmware and use Odin flash it back?
I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.
Did you mean we can just download the custom jelly bean firmware and install it as custom rom instead of the official one from AT&T? I think that make sense.
mrhaley30705 said:
I wouldn't worry about the official update. Usually in a day or two of official release, there will be an official firmware in package in the development section.
Click to expand...
Click to collapse
When its released, yes. That's one reason there are threads just for stock firmware.
hi i just received an OTA notice that i can update my phone to JB. i hv 1 question now, my one x is bootloader unlocked now, but i m using stock rom with root, i wonder if i could update to JB without relocked bootloader, and is it possible root on stock JB now?
All I can tell you is that I never encountered problems with the OTA updated on an unlocked bootloader so I do not think you will encounter them now. Even if something goes wrong you are rooted anyways. If it fails and hboot is not changed just recover. if it fails and hboot is updated just install a 4.1 rom.
SharkDog2 said:
All I can tell you is that I never encountered problems with the OTA updated on an unlocked bootloader so I do not think you will encounter them now. Even if something goes wrong you are rooted anyways. If it fails and hboot is not changed just recover. if it fails and hboot is updated just install a 4.1 rom.
Click to expand...
Click to collapse
can i use this method to update my one x?
http://forum.xda-developers.com/showthread.php?p=26967480
Yes, that's exactly what you have to do.
Personally I forgot to use the RootKeeper even tough I had used it to go from firmware 1.xx to 2.xx, so I had to reflash clockwork recovery and SuperSU to re-root after update, but thats it.
wewewi999 said:
Yes, that's exactly what you have to do.
Personally I forgot to use the RootKeeper even tough I had used it to go from firmware 1.xx to 2.xx, so I had to reflash clockwork recovery and SuperSU to re-root after update, but thats it.
Click to expand...
Click to collapse
thanks for your reply, i will try it later and put my result.
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
I unlocked my bootloader a few months ago to try some custom roms. I didn't like any of them so I went back to the stock rom/firmware. I still receive notifications about new updates but I also still have the bootloader unlocked, so I don't know if that can cause an issue when updating.
Any help?
Sorry man but ota update note working when bootloader unlocked. And you can't go back to official state.
Stock firmware
hansaka said:
Sorry man but ota update note working when bootloader unlocked. And you can't go back to official state.
Click to expand...
Click to collapse
You should be able to go back to Official state by flashing stock firmware with Odin .
peter couniaz said:
You should be able to go back to Official state by flashing stock firmware with Odin .
Click to expand...
Click to collapse
I have the Official state enabled, that's why I receive notifications about new updates. I guess If it was marked as 'Custom' instead of 'Official' it wouldn't even search for updates but that's not the case
A new update just popped up in Settings but I don't know if I should install it via OTA or via Odin
MartinCXV said:
I have the Official state enabled, that's why I receive notifications about new updates. I guess If it was marked as 'Custom' instead of 'Official' it wouldn't even search for updates but that's not the case
A new update just popped up in Settings but I don't know if I should install it via OTA or via Odin
Click to expand...
Click to collapse
I installed an ota update while my bootloader was unlocked and it updated normally