Develop Bugs

Utmost help needed please.

Sorry for being noobish, just got a nexus, UK and it's on 4.0.1, been reading a lot, and very much overwhelmind, now, coming from my galaxy s2, which, I had been used to flashing and routing daily. I managed to use the toolkit, to root my phone, smashing app, will definitely donate, to the dev, as i managed to root, in pretty much 5mins. My problem is, whats the best route, to follow, in order for me to have the latest stock 4.0.4, because I have read a lot of stuff, so now muddled as to what path to take. Is it a matter, of just downloading the official rom, in the general section, and flashing it via custom recovery, sorry for the noobish questions, it's been a long day, trying to get to know the phone, am sure, if someone can help me from here, all be fine. I also tried to seek for an update, under about, but phone says am on latest firmware, which is 4.0.1,so appreciate your guidance please.

marvi0 said:
Sorry for being noobish, just got a nexus, UK and it's on 4.0.1, been reading a lot, and very much overwhelmind, now, coming from my galaxy s2, which, I had been used to flashing and routing daily. I managed to use the toolkit, to root my phone, smashing app, will definitely donate, to the dev, as i managed to root, in pretty much 5mins. My problem is, whats the best route, to follow, in order for me to have the latest stock 4.0.4, because I have read a lot of stuff, so now muddled as to what path to take. Is it a matter, of just downloading the official rom, in the general section, and flashing it via custom recovery, sorry for the noobish questions, it's been a long day, trying to get to know the phone, am sure, if someone can help me from here, all be fine. I also tried to seek for an update, under about, but phone says am on latest firmware, which is 4.0.1,so appreciate your guidance please.
Click to expand...
Click to collapse
Follow the directions here. Note that this will wipe your data...

efrant said:
Follow the directions here. Note that this will wipe your data...
Click to expand...
Click to collapse
Phew cheers buddy, haven't tried this yet, as at work, will give it a short when I get home, anything easier than this please, as i just have a forbia for anything called adb please? Also, don't understand why my device is still on 4. 0. 1, been hitting the update button continously with no luck, but prepared to use other means, as suggested above, to get the device updated. Thanks again in advance.

marvi0 said:
Phew cheers buddy, haven't tried this yet, as at work, will give it a short when I get home, anything easier than this please, as i just have a forbia for anything called adb please? Also, don't understand why my device is still on 4. 0. 1, been hitting the update button continously with no luck, but prepared to use other means, as suggested above, to get the device updated. Thanks again in advance.
Click to expand...
Click to collapse
You CAN flash factory images through the toolkit you know. You can download them at Google, put them in the correct subfolder of the GNEX toolkit folder and flash away. In order to do that you do have to have an unlocked bootloader and you will loose your root. Unlocking the bootloader will loose all your data (including under the SDCARD folder (so everything you stored will be gone)!. Rooting can be done again through the toolkit...
Or you can download a different flashable zip file that you can flash from CWM recovery.

Hmm thanks this looks more like my sort of of a thing "different flashable zip file that you can flash from CWM recovery.", were can i find this please?. Thanks.

OK to install 4.0.4 OTA on rooted/unlocked Nexus?

My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA

I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.

Ok, that's what I expected. Sounds like we need to run the manual update. I'm in the process of packing and moving this weekend so I was hoping for an easy fix. Thx for your reply.
Sent from my Galaxy Nexus using XDA

hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.

cryptiq said:
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If you did not change anything (other than root), you can install it no issue. However, if you have changed your radio, kernel, recovery, or any system file, then the update will not work.
Not however, that you need to install something like OTA Rootkeeper BEFORE you go through the update process, as you will lose root otherwise.
dogunter said:
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Click to expand...
Click to collapse
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
FellX said:
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
Click to expand...
Click to collapse
An update does not affect the "unlocked status" as you say.
See my comments above about root.
You comments about switching to a non-stock ROM don't really make sense for someone who likes stock ROMs and wants to update...

Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/

efrant said:
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
Click to expand...
Click to collapse
He is right, once upon a time I had flashed a rom and then wanted to go back to stock. I used someones method first (I dont remember whose it was) and I thought I was on stock but I got the android guy on his back and it wasnt working properly (I think the radio was the wrong one) so I then flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process.
So more than likely there is something that isnt stock on your phones.

WiredPirate said:
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
Click to expand...
Click to collapse
That is NOT an update. The guy wants to update his build, not flash a brand new one...

same issue
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!

galaxy_sexus said:
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
Click to expand...
Click to collapse
I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that you are fully stock. (Leave the bootloader unlocked.) Once you do that, then you can have a look here for how to use the OTA update file to update.

hmm
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.

galaxy_sexus said:
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
Click to expand...
Click to collapse
You are good to proceed. You won't get the wipe prompt if your bootloader is already unlocked. No worries, just keep going with the steps.
Sent from my Galaxy Nexus using Tapatalk 2

thanks
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.

galaxy_sexus said:
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
Click to expand...
Click to collapse
The first thing i would do is reboot. If that doesn't work, then I would just flash the images one more time. (Just in case one of them messed up.) Make sure both radios flash successfully.
Sent from my Galaxy Nexus using Tapatalk 2

got it
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.

galaxy_sexus said:
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
Click to expand...
Click to collapse
useful thread

GSM Telstra rom (Yakjudv) how to upgrade to 4.0.4 or JB?

Hi everyone,
I must apologise for adding to the large number of threads on subjects such as this, but having trawled through forums (Both here and elsewhere), I'm struggling a bit to know which guide to use.
I'm currently using a Galaxy Nexus which is running stock Android 4.0.1 yakjudv (Telstra GSM). I'm wanting to change my phone to a stock Google rom, as I currently don't get any OTA updates. I would be happy with 4.0.4, or JB. The problem I have is, having looked through all the guides, I don't know exactly what I need to do to achieve what I'm looking for. I'm trying to do the minimum to get the result, and don't need to remain rooted/unlocked after I upgrade.
As I'm quite afraid of doing something wrong, I wondered if anyone could point me in the direction of the best guide to use. I've looked at
http://forum.xda-developers.com/showthread.php?t=1614827
and
http://www.pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/
and have downloaded the rom from:
https://developers.google.com/android/nexus/images (Yakju)
I would appreciate any guidance.
Thank you so much, and once again my apologies for posting yet another question. I do promise that I have tried to find the information on my own for a number of hours. I may simply be inept at searching!

Download the galaxy nexus toolkit then backup your data then install the drivers then download the factory image 4.0.4 then use the galaxy nexus toolkit to unlock the bootloader then put the galaxy nexus image file in c:\galaxynexustoolkit\google image goes here then use the galaxy nexus toolkit to install the 4.0.4 galaxy nexus image the use the galaxy nexus toolkit to root the device and to keep root use OTA root keeper from google play store then install ota jelly bean update there you go that how you install the google image on your telstra galaxy nexus and I use a galaxy nexus on Telstra
Sent from my Galaxy Nexus using xda app-developers app

morgy59 said:
Download the galaxy nexus toolkit ...
Click to expand...
Click to collapse
No, don't use a toolkit.
OP, follow this guide. Extremely easy and it doesn't matter what your current build is, you'll be flashing to 4.0.4 "takju" and quickly receive the 4.1.1. OTA update. You'll be stock and update by Google from here on out: http://forum.xda-developers.com/showthread.php?t=1626895

Use the galaxy nexus toolkit because its very easy to use and I've used it for my Galaxy Nexus on Telstra
Sent from my Galaxy Nexus using xda app-developers app

martonikaj said:
No, don't use a toolkit.
OP, follow this guide. Extremely easy and it doesn't matter what your current build is, you'll be flashing to 4.0.4 "takju" and quickly receive the 4.1.1. OTA update. You'll be stock and update by Google from here on out: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you both for the replies. If I follow the guide to flash to 4.0.4 "Takju", will this cause any difficulties in using the phone here in Australia? (I read something about not being able to use HD audio or something like that on another forum and just want to be sue that the upgrade will work on my phone here in Aus!)

morgy59 said:
Use the galaxy nexus toolkit because its very easy to use and I've used it for my Galaxy Nexus on Telstra
Click to expand...
Click to collapse
But then when something goes wrong (it usually does with new users and toolkits), you have absolutely no idea what's happened and no way to fix it. Just spend the few minutes to learn a manual guide and understand what you're doing. You'll thank yourself when you can diagnose problems.
paul-g said:
Thank you both for the replies. If I follow the guide to flash to 4.0.4 "Takju", will this cause any difficulties in using the phone here in Australia? (I read something about not being able to use HD audio or something like that on another forum and just want to be sue that the upgrade will work on my phone here in Aus!)
Click to expand...
Click to collapse
It'll work just fine. I've not heard anything specific about Australian users having issues being on stock Google firmware (no reason why they would). The only issue I could see is the radio not providing the best results. You can always flash back to an AUS-specific radio, although this then prevents you from auto-installing OTA's, which was your goal in the first place...

martonikaj said:
But then when something goes wrong (it usually does with new users and toolkits), you have absolutely no idea what's happened and no way to fix it. Just spend the few minutes to learn a manual guide and understand what you're doing. You'll thank yourself when you can diagnose problems.
It'll work just fine. I've not heard anything specific about Australian users having issues being on stock Google firmware (no reason why they would). The only issue I could see is the radio not providing the best results. You can always flash back to an AUS-specific radio, although this then prevents you from auto-installing OTA's, which was your goal in the first place...
Click to expand...
Click to collapse
Thanks again!
I've just tried following the guide and was going to backup my phone first, but CWM tells me 'Can't mount backup path". Does this mean there is something wrong that I should know about before I try the full process?

Sorry to double post - I thought I should just check - Last night I installed drivers using Wug's toolkit, and when I fastboot devices, I get a serial number. It also let me view the device both in normal and recovery mode.
I assumed that meant that I didn't need to reinstall the drivers. Is that correct?
Thanks so much!
Paul

Update 4.1 - Doesn't work, still in 4.0.4

Hello,
So, I will try to explain clearly my problem. I'm french, so I have an Galaxy Nexus with Android 4.0.4 (IMM76I) - Yakju.
I bought my phone at the very beginning, with the first ICS version. After that, I tried to use " Font changer ", and my phone rebooted, and loading... infinite
So, that was a big problem. To recover it, I tried so many thing, Wipe data, cache, etc... And I flashed the phone with the Factory Image. And it worked. Since this incident, I ALWAYS must flash the new factory image to use new versions of ICS. For 4.0.4 and 4.1. Because on every update, my phone reboot, it loads, and I get the Bugdroid with Warning icon :/
But I'm pissed of, and I want to do something, I'm bored to have that phone, and must do so much tricks for a simple update
So, I'm coming to you, for answers, if there are ?
Thanks !

So when you flashed the factory images, have you been flashing the corresponding radio, bootloader and recovery? And have you modified any system files since then? All of these things will prevent you from applying an OTA.

I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !

draentor said:
I used all factory elements from here : h**ps://developers.google.com/android/nexus/images?hl=fr
But now you ask me if I flashed bootloader, recovery, and radio, and I'm not sure :/
If I use the Gnex Toolkit, does he flash all of this himself ? Because I didn't use it before, and I don't remember me flashing the recovery.
I will wait for the 4.1 factory image to be released by Google, and do all of this
Thanks !
Click to expand...
Click to collapse
Don't use a toolkit and you will know what gets flashed. Follow steps in post #1 here.

Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?

draentor said:
Ok, I will follow all steps with 4.1 update.
And after that, I still can use the Toolkit right ?
Click to expand...
Click to collapse
No. Follow the steps in the link I sent you, and you will get the OTA update for 4.1.1 shortly after.

Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?

draentor said:
Yeah, I thinked about it, and that's the better solution.
But for root and others things, absolutely use your way ?
And what's the avantages and inconveniences of the tho methods ?
Click to expand...
Click to collapse
Use any way you want. Except when you are learning, you should not use any toolkits or 1-click methods <-- you don't know what they are doing, and if something messes up, it will be difficult for you to troubleshoot.

erec, icandoit
Yeah, seems logical.
I must do it the old way, before use new things
So, thanks for all your quick answers, there are much more knowledge here than the FrAndroid French forum

Return to Stock Yakjudv

Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.

http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know

atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)

Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up

Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.

real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.

Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery

real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/

Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2

real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro

efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.

Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.

LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me

I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.

efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?

Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.

Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.

picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175

efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.

picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?