Develop Bugs

[Q] Rooted, CWM, Stock Rom - Will 4.0.3 update work?

I have a GSM Gnex running 4.0.2 stock rom, which I've rooted and replaced the stock recovery with clockworkmod.
Will a 4.0.3 OTA update work, or will I have to replace CWM with the stock recovery?
Edit: changed "stock bootloader" to "stock recovery"

njackson-uk said:
I have a GSM Gnex running 4.0.2 stock rom, which I've rooted and replaced the stock bootloader with clockworkmod.
Will a 4.0.3 OTA update work, or will I have to replace CWM with the stock bootloader?
Click to expand...
Click to collapse
I'm not 100% sure, but I think the ota update won't work if you have Cwm recovery. Bootloader isn't the same as recovery btw.
Sent from my Galaxy Nexus using Tapatalk

I meant recovery! Thanks for pointing that out.
I guess I'll just have to wait and see.

njackson-uk said:
I meant recovery! Thanks for pointing that out.
I guess I'll just have to wait and see.
Click to expand...
Click to collapse
It won't work dude. But if you are already rooted try a custom 4.0.3 rom yourself Good luck.

Wrong thread.

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.

Question about root and roms

If I root my S3 will I still be able to get the OTA updates? I rooted my Atrix and after that I couldn't get the OTA updates. Also what is the best ROM?

anaylor01 said:
If I root my S3 will I still be able to get the OTA updates? I rooted my Atrix and after that I couldn't get the OTA updates. Also what is the best ROM?
Click to expand...
Click to collapse
If you don't need a specific feature from the stock firmware (gestures, wifi calling, etc), just get CM or AOKP and save yourself a headache.
Best? As far as stock? I've read LI6 is decent.

Well with my Atrix when Android 3.0 came out I wasn't able to update it because I was rooted. So my question is when Jelly Bean comes out will I be able to update it to Jelly bean if I am rooted or have a custom rom installed?

anaylor01 said:
Well with my Atrix when Android 3.0 came out I wasn't able to update it because I was rooted. So my question is when Jelly Bean comes out will I be able to update it to Jelly bean if I am rooted or have a custom rom installed?
Click to expand...
Click to collapse
3.0 wasn't even for phones. If you install custom recovery you will not be able to receive an OTA until you flash the stock recovery. Just use a jellybean ROM.
Sent from my SGH-T999

joshnichols189 said:
If you install custom recovery you will not be able to receive an OTA until you flash the stock recovery.
Click to expand...
Click to collapse
How can this be true? This is what I did.
Restored a UVALEM nandroid (via CWM). It was the original firmware on the phone when I bought it (no custom install, but I rooted with the Sprint method a couple weeks prior), I just happened to keep this backup.
Reset factory defaults.
Nandroid again for clean UVALEM backup.
Use Software > About phone > Software update to get the UVALH2 update. It was ~90mb.
Phone rebooted after it was done.
Dropped into CWM to make another backup (CWM still here, was never removed).
Downloaded LI6 JB OTA from SamMobile. Installed that from CWM.
I have LI6, never removed CWM. And it is still there. Root should be, although I did not test to confirm.
If you can't receive OTAs with custom recovery/root, how did this work? Is it a feature that was not active in the UVALH2 build? What about the LI6 build I flashed from CWM?

Aerowinder said:
How can this be true? This is what I did.
Restored a UVALEM nandroid (via CWM). It was the original firmware on the phone when I bought it (no custom install, but I rooted with the Sprint method a couple weeks prior), I just happened to keep this backup.
Reset factory defaults.
Nandroid again for clean UVALEM backup.
Use Software > About phone > Software update to get the UVALH2 update. It was ~90mb.
Phone rebooted after it was done.
Dropped into CWM to make another backup (CWM still here, was never removed).
Downloaded LI6 JB OTA from SamMobile. Installed that from CWM.
I have LI6, never removed CWM. And it is still there. Root should be, although I did not test to confirm.
If you can't receive OTAs with custom recovery/root, how did this work? Is it a feature that was not active in the UVALH2 build? What about the LI6 build I flashed from CWM?
Click to expand...
Click to collapse
I don't know, clockworkmod is supposed to block the installation of OTA updates.
Sent from my SGH-T999

Hmm, I'm using 6.0.1.2, and it does ask me if I want to disable /system/etc/install-recovery.sh, when I try to exit.

Flashing OTA

I have 2 GNex running 4.2.1, these are stock 100% google images just rooted and custom recovery. I am using TWRP 2.4.x.x and tried with 2.3 as well and every time I try to flash the 4.2.2. OTA it fails saying error 7.
Any way to flash just the OTA without doing a full wipe or flash the new stock images from google? I was under the impression OTA's can be used with custom recoveries but I guess you can't?

jebise101 said:
I have 2 GNex running 4.2.1, these are stock 100% google images just rooted and custom recovery. I am using TWRP 2.4.x.x and tried with 2.3 as well and every time I try to flash the 4.2.2. OTA it fails saying error 7.
Any way to flash just the OTA without doing a full wipe or flash the new stock images from google? I was under the impression OTA's can be used with custom recoveries but I guess you can't?
Click to expand...
Click to collapse
You can flash ota with a custom recovery. What did the error say?
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
You can flash ota with a custom recovery. What did the error say?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
some error's with the libraries, guess it has to do with the nexus loud mod I added, ran the revert zip but still errored. Anywho not a bid deal, just used fastboot to flash system/radio/boot and its fine.

jebise101 said:
some error's with the libraries, guess it has to do with the nexus loud mod I added, ran the revert zip but still errored. Anywho not a bid deal, just used fastboot to flash system/radio/boot and its fine.
Click to expand...
Click to collapse
that is exactly why it errored. you were no longer using a stock rom.

[Solved] official JB 4.3 for Maguro ?

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.