Develop Bugs

[Q] About updating to 4.0.4

I am using GSM GN with 4.0.2 stock rom but modified the battery icon, radio is XXLA2 and bootloader is PRIMELA03 and already relocked bootloader
I know the OTA update now is only for completely stock 4.0.2 and I cannot find any custom "Stock rooted deodexed IMM76D" rom for GSM GN
Is there any method to update the rom to stock 4.0.4 without wiping my data??

hello, i have a related question but i didnt want to make another thread to avoid the spam and all the forum trolls.
my question is, i got the 4.0.4 android update (OTA) i did not update yet because i dont have stock, i have Android revolution ROM.
what will happen if i update ? will my device get unrooted ?
will my data be wiped ?
thanks a lot.

punalex said:
I am using GSM GN with 4.0.2 stock rom but modified the battery icon, radio is XXLA2 and bootloader is PRIMELA03 and already relocked bootloader
I know the OTA update now is only for completely stock 4.0.2 and I cannot find any custom "Stock rooted deodexed IMM76D" rom for GSM GN
Is there any method to update the rom to stock 4.0.4 without wiping my data??
Click to expand...
Click to collapse
best is to wipe all , like uprade to win7 from vista compared to clean installation
beirouty said:
hello, i have a related question but i didnt want to make another thread to avoid the spam and all the forum trolls.
my question is, i got the 4.0.4 android update (OTA) i did not update yet because i dont have stock, i have Android revolution ROM.
what will happen if i update ? will my device get unrooted ?
will my data be wiped ?
thanks a lot.
Click to expand...
Click to collapse
dude, as stated also in other threads, you will never be able to install OTA update due to custom recovery
seeya mates

I know the best is to wipe, but it need to backup the whole sdcard folder which is about 10GB data to my computer and then restore and need to reconfig the phone setting after wipe which really take a long long long time!!!!
So I want to find out the method of bypassing the complete 4.0.2 limitation or wait for someone to make a custom rom like "stock 4.0.4 rooted deodexed"
this kind of rom is available everytime a stock rom come out but not in this time!!?

with root explorer, or better with adb under cwm recovery if u have it, u can restore the files modified by the battery mod, and restore that files with the original 4.0.2 ones
in this way, u can apply the 4.0.4 ota when u get the notification

However, my rom is already deodexed!! Anyone have 4.0.2 rom(stock odexed but no need to wipe), radio and bootloader link (CWM zip), so I can flash this three in recovery and then the OTA update

[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

[Q] Flashing 4.0.4 yakju (coming from 4.0.2 yakjuux)

I have unlocked, rooted, and installed Clockwork Recovery on my Galaxy Nexus (GSM, Wind Canada), and now I want to flash 4.0.4 yakju.
My current bootloader is PRIMEKK15 and my current radio baseband is UGLA4
Is flashing 4.0.4 yakju as simple as downloading the image found on google's site (yakju-imm76i-factory-8001e72f.tgz), putting it on the phone, going to Clockwork Mod, navigating to "install zip from SDcard", then choosing yakju-imm76i-factory-8001e72f.tgz, or do I have to open the tgz, then open the tar inside, and then extract this zip and install that in CWM http://i.imgur.com/wXC64.png
Since it's not a custom ROM like AOKP or CM, do I have to wipe data/factory reset in clockwork? Do I have to flash gapps?
Do I have to flash the new bootloader and radio baseband found in 4.0.4 separately?
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/showpost.php?p=23149491&postcount=139
I think that's all the questions I have, lol.

Well first off, if you're going to do it I'd just recommend you wait for the 4.1.1 image for the GSM GNex to drop. If you're really ansy, then you could flash 4.0.4 and you'll still get the OTA, but just something to think about.
Now to the question, no, you don't flash it like a ROM in CWM recovery. If you wish to completely move to yakju (or takju) to get on the Google update line (not sure why else you'd do it), you need to flash the images via fastboot. All parts of the images. It's important to have the proper bootloader and radio if you intend to receive and automatically install OTA updates. If you don't, you won't be able to install it as it checks for the radio and bootloader as part of the install process.
Follow this guide from Efrant, it's gold: http://forum.xda-developers.com/showthread.php?t=1626895
Don't use a toolkit!
Also, some people report reception problems with the baseband included in 4.0.4. If I want to go back to UGLA4, is that possible? I would be using the CWM "radio.img" for UGLA4 found here http://forum.xda-developers.com/show...&postcount=139
Click to expand...
Click to collapse
I haven't heard about any issues with the latest 4.0.4 radio outside of isolated problems. You can change the radio if you want (via fastboot, rly quick), but as I said, it'll stop you from auto-installing OTAs (which is why you went to yakju, isn't it?). You'll also get a new radio with 4.1.1.

Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
EDIT: Say Google puts up a 4.1 image next week, I would just need to download it and follow the same steps that are outlined in that post (flashing all the different images in fastboot)?

Matt08642 said:
Hmm, I might not even bother, seeing as to get the updates I'd lose CWM and root. Perhaps I will just wait for 4.1 like you said and install that.
Click to expand...
Click to collapse
You can flash CWM and root it again after going to yakju, but you'll have to update manually (no auto-installing OTA) after that. You have to pull the image and flash it, and use an app like "OTA root keeper" to hold onto root.
By the way, since I am on 4.0.2 but I have CWM, does that mean even if my yakjuux build got 4.0.4 OTA, I wouldn't get notified (because of the custom recovery)??
Click to expand...
Click to collapse
You'll be notified, but the update won't install. It requires stock recovery to auto-install.

Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!

Matt08642 said:
Cool. In that case, I will just wait for JB, then once I flash that image myself, I will reflash CWM and root my phone again.
Thanks for the help, and thanks for the link to that thread!
Click to expand...
Click to collapse
No problem.
Sent from my Galaxy Nexus using xda premium

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.

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