[Solved] official JB 4.3 for Maguro ? - Samsung Galaxy Nexus

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.

Related

[Q] any difference between factory 4.0.4 or OTA to 4.0.4 from 4.0.2?

hi i just upgrading my phone from 4.0.2 to 4.0.4 imm76i (gsm/hspa+ without google wallet),
i am going to root the phone by cwm recovery, then i have some questions:
when i was on 4.0.2, i rooted the box by cwm, and when i want to do update by OTA, i have to refresh back to the original recovery in the factory 4.0.2 image to apply the package, and that's what i have done...
so here is the question: if i root it by cwm again, and then flash the new recovery.img from factory 4.0.4 image download from "https://developers.google.com/android/nexus/images#yakjuimm76i"
to the phone, will it keep the ability to OTA to next android version? in another way, is there any difference between OTA & factory image OR, is there a identification to know that whether this device flashed a factory image or ota from a previous version?
ok, then if do not mv/rm /system/recovery-from-boot.p after flash cwm(for root), will it restore the stock recovery and keep the ability to do OTA?
erics_lu said:
hi i just upgrading my phone from 4.0.2 to 4.0.4 imm76i (gsm/hspa+ without google wallet),
i am going to root the phone by cwm recovery, then i have some questions:
when i was on 4.0.2, i rooted the box by cwm, and when i want to do update by OTA, i have to refresh back to the original recovery in the factory 4.0.2 image to apply the package, and that's what i have done...
so here is the question: if i root it by cwm again, and then flash the new recovery.img from factory 4.0.4 image download from "https://developers.google.com/android/nexus/images#yakjuimm76i"
to the phone, will it keep the ability to OTA to next android version? in another way, is there any difference between OTA & factory image OR, is there a identification to know that whether this device flashed a factory image or ota from a previous version?
Click to expand...
Click to collapse
The ota is usually just the parts of the rom that have been updated, those image files are the whole rom, if u root u will be able to get the ota but it won't install even with factory recovery,I haven't done it since my N1 but if I remember right u can delete super user from system app folder and delete,--- com.noshufou.android.su and reboot and root should be gone then ota will work and after u update u just root agn .... but your way u did it is always an option ....
biggofer said:
The ota is usually just the parts of the rom that have been updated, those image files are the whole rom, if u root u will be able to get the ota but it won't install even with factory recovery,I haven't done it since my N1 but if I remember right u can delete super user from system app folder and delete,--- com.noshufou.android.su and reboot and root should be gone then ota will work and after u update u just root agn .... but your way u did it is always an option ....
Click to expand...
Click to collapse
thank u for response, i tried to update to 4.0.4 from rooted 4.0.2, and everything is ok.. according to your condition, i think there may be some difference between nexus S and galaxy nexus, so root is not the question(though i met some problem while rooting 4.0.4 caused by the version of su.zip is out of date ).
now i am on 4.0.4 and rooted by cwm, and i didn't delete /system/recovery-from-boot.p, i hope that i will not have to re-flash stock recovery when the next OTA come
When you say that is rooted through CWM, means what exactly? You only used the CWM to root the device? But how?
yep cause i wanna use stock rom on my GN so far, so i use cwm only for root(by flashing a su.zip), and after googled a lot, i think it has went back to stock recovery now, no longer worry about OTA, thank you
erics_lu said:
hi i just upgrading my phone from 4.0.2 to 4.0.4 imm76i (gsm/hspa+ without google wallet),
i am going to root the phone by cwm recovery, then i have some questions:
when i was on 4.0.2, i rooted the box by cwm, and when i want to do update by OTA, i have to refresh back to the original recovery in the factory 4.0.2 image to apply the package, and that's what i have done...
so here is the question: if i root it by cwm again, and then flash the new recovery.img from factory 4.0.4 image download from "https://developers.google.com/android/nexus/images#yakjuimm76i"
to the phone, will it keep the ability to OTA to next android version? in another way, is there any difference between OTA & factory image OR, is there a identification to know that whether this device flashed a factory image or ota from a previous version?
Click to expand...
Click to collapse
No difference. If you did not delete the two files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) then your device will automatically flash the correct stock recovery on every re-boot.
EDIT: Actually there is one difference: the OTA places those two files on your system, while a full stock ROM does not.
erics_lu said:
ok, then if do not mv/rm /system/recovery-from-boot.p after flash cwm(for root), will it restore the stock recovery and keep the ability to do OTA?
Click to expand...
Click to collapse
Yes.
biggofer said:
[snip]
if u root u will be able to get the ota but it won't install even with factory recovery
Click to expand...
Click to collapse
This is wrong. Rooting has no impact whatsoever on being able to install an OTA update.
efrant said:
No difference. If you did not delete the two files (/system/etc/install-recovery.sh and /system/recovery-from-boot.p) then your device will automatically flash the correct stock recovery on every re-boot.
Yes.
This is wrong. Rooting has no impact whatsoever on being able to install an OTA update.
Click to expand...
Click to collapse
thank you so much, explained so detailed

OTA Update

I'm on a JB rom from here and I just got the OTA update message. If I hit restart and install will it brick it or is it safe to do? If its not how do I clear the message?
Mind providing a little more information? Which Jelly Bean ROM are you running? Is it stock? Is it custom?
If your entire phone is stock, then yes, update.
If not, don't update. Flash stock, perhaps 4.0.4 Yakju, then update.
If you have no idea, don't update. Flash stock, perhaps 4.0.4 Yakju, then update.
Don't be afraid of the search feature located on the top left side of your screen.
This Rom and I have CWM installed
joshua.justice said:
This Rom and I have CWM installed
Click to expand...
Click to collapse
what is "this rom"
joshua.justice said:
This Rom and I have CWM installed
Click to expand...
Click to collapse
Can't help you if all you got is "this ROM". Flash stock 4.0.4 yakju using the toolkit by mskip. Then update.
Sent from my Galaxy Nexus using xda premium
will not flash with cwm, but it won't brick either.
joshua.justice said:
I'm on a JB rom from here and I just got the OTA update message. If I hit restart and install will it brick it or is it safe to do? If its not how do I clear the message?
Click to expand...
Click to collapse
Depends if its a stock image or a custom ROM you're running.
If you've flashed a stock image (doubtful because you say "ROM"), then you can accept it only if you have a stock radio, bootloader, system and recovery. Even if you're 100% stock but with a custom recovery (like CWM), you can't accept and auto-install an OTA. You have to install it manually.
If you're on a custom ROM, you cannot accept the OTA.

New Update Message

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.

rooting and ota

Hi,
I might sound dumb but will I be ablle to get OTA updates if I install custom recovery and root.
thechamp007 said:
Hi,
I might sound dumb but will I be ablle to get OTA updates if I install custom recovery and root.
Click to expand...
Click to collapse
No. OTA updates require stock recovery. However, you can revert to stock recovery and unroot as you please. Also, you can flash OTA updates through TWRP once a flashable zip is made, except you have to download it and flash it manually, just like installing a custom ROM. Cheers.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
I received the last update through OTA on a rooted Stock ROM with TWRP installed.
After the install was finished TWRP asked if I wanted to restore the root. All went smoothly.
To clarify.. I did not flash the ROM. I used the normal OTA update.
tigerdim said:
I received the last update through OTA on a rooted Stock ROM with TWRP installed.
After the install was finished TWRP asked if I wanted to restore the root. All went smoothly.
To clarify.. I did not flash the ROM. I used the normal OTA update.
Click to expand...
Click to collapse
I believe you can on small point updates. The full update from 4.3 to 4.4 most likely won't work with a custom recovery.
nbehary said:
I believe you can on small point updates. The full update from 4.3 to 4.4 most likely won't work with a custom recovery.
Click to expand...
Click to collapse
you must have stock /system folder + stock recovery
you can be rooted, by if you delete some files in /system - you break your ota
new ota will be with new radio too
after ota super-su apk will be removed by the ota
---------------
i restored /system apps from sdcard before 4.3 ota and migrate very well from 4.2.2
The ota 4.3 update removed my root and Twrp. Hope 4.4 doesn't do the same. It's always a pain for me to restore root with my Windows 7 laptop. It keeps installing the wrong usb drivers which get in the way of the wugfresh toolkit access to the nexus 7. So it's no easy task for me.

[Q] Update to 4.4.3

My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.
pctechdroid said:
My Nexus 7 wifi has the 4.4.3 update that has been prompting me to update. I tried doing the update which fails.
I do have TWRP installed, MultiROM, and a customer kernel. I tried flashing a custom kernel which did not resolve the issue.
I currently swap between stock and CM depending on what I would like to play with.
Click to expand...
Click to collapse
I'd do a nandroid before doing anything.
It might help if you state what the exact contents of the error is, my guess is that you have changed something in /system (unexpected contents error), and flashing a custom kernel won't fix it, in fact you would want to flash a stock 4.4.2 system.img and stock 4.4.2 boot.img if you want to use the OTA method, else you can just skip using the OTA and try and flash a 4.4.3 system.img and 4.4.3 boot.img, either way make sure you clear dalvik and cache before booting up after the system flashes.
You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?
mediumsteak said:
You cannot install official updates if your device is modified!
Since you mentioned that you are familiar with CM, why don't you update to the latest CM ROM?
Click to expand...
Click to collapse
I play with it every once in awhile but I don't know why I enjoy stock but I do. Maybe I will go back to CM.

Categories

Resources