yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Technical:
Ok. Sorry. Living and learning.

But now I have a thread with 100 pages to find and read. Even searching busybox get a lot of entries.

It's past midnight and I can't use a toolkit as you say...

How can I uninstall Busybox and restore the files. Please, bear me, give me the link or the commands to do so.

I just use the Galaxy Nexus Toolkit downloaded from this forum.

When I can and when it works.

Now I'm trying to do all of it manually.

Please, be patient and try to help me. Thanks.

---------- Post added at 11:45 PM ---------- Previous post was at 11:39 PM ----------

I've tried this, but seems that I can only flash .zip files and not .img ones. Can you guide me? Thanks.

---------- Post added 17th July 2012 at 12:21 AM ---------- Previous post was 16th July 2012 at 11:45 PM ----------

1. I've followed "If you've replaced stock files with custom ones, either replace the stock ones, or go into the update zip file, and remove the assert for the file (although I don't recommend the later, as the update may not patch your custom file properly). If you are missing stock yakju or mysid files, download the factory images from here, extract the system.img from within, convert it to an .ext4.img by using this and then (for Windows users) use this to mount the .ext4.img and extract the file."

2. Then I've extracted gzip, ip and ping files to sdcard. Start Android and use Root Browser to copy them to \system\bin.

3. Start recovery with CWM non-touch and choose the .zip file of the OTA.

4. System seems to have patched but when I've booted back into Android, phone bricked... I cannot boot and cannot recover it... Now I'm in trouble :crying:

---------- Post added at 12:42 AM ---------- Previous post was at 12:21 AM ----------

If anybody can really help me how to start from the beginning.

I can start with bootloader but not with recovery anymore.

The normal boot never finish.

How can I get my phone back :crying :( :crying:
[Samsung Galaxy Nexus] efrant:
Your phone is NOT bricked. It is EXTREMELY DIFFICULT TO BRICK YOUR DEVICE. You have a few options:

1) Boot into CWM, and wipe data. This will wipe your apps and your app data, but NOT your /sdcard. (But wiping shouldn't matter, because you backed up before attempting this right?) Then reboot.

2) If that doesn't work, then copy all your data from /sdcard off your device when booted in CWM and plugged into a computer, by typing: adb pull /sdcard. Then follow the steps in the flash link in my sig to flash a full stock IMM76I unmodified ROM, then apply the update from this thread.
[Samsung Galaxy Nexus] Technical:
Thanks for the encouragement.

As I've said I cannot boot in Recovery Mode in anyway, I've got an Android icon with a red exclamation point.

So I cannot wipe the data.

I cannot boot in Android, so I cannot copy or even reach the /sdcard.

But I will follow tomorrow, your instructions or get a technician to help me.

Thanks again. It was a terrible experience with Android.
[Samsung Galaxy Nexus] marky9074:
Many thanks for this. I am on a ship with only a satellite connection, so couldn't really download the full image. I note in /system/bin there is a lot of reference to busybox (are they all symlinks?)...

Anyway, run the update again using stock recovery, and it failed on my tweaked gps.conf - once back to stock worked fine... jeez this update is temperamental? :confused:
[Samsung Galaxy Nexus] Mendeleev:
Boot CWM using fastboot boot cwm.img as in method 2 in the OP. Then wipe the data in there.
[Samsung Galaxy Nexus] NCguy:
Efrant, I just received the 4.1.1 OTA for one of my GNs but I want to leave it on ICS for a while. I see it in cache with root and es file explorer. What's the most convenient way to park it for later use?
[Samsung Galaxy Nexus] efrant:
There's no need to save it, as the link to the file is already available in the first post of this thread.

As for getting rid of the OTA notification, you can try editing the ro.build.fingerprint field, but I'm not entirely sure that trick still works in JB. It may.

1) Make a backup of your /system/build.prop file

2) Edit the line in it that starts with ro.build.fingerprint to read as follows:

ro.build.fingerprint=google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys

When you want to update, just replace your build.prop with the one you backed up.
[Samsung Galaxy Nexus] NCguy:
Great. Thanks for that info. Never messed with build.prop but I knew it was inevitable. Just use any text editor?
[Samsung Galaxy Nexus] efrant:
Yup. You can even do it using Root Explorer (or something similar) on your device -- it has a built in text editor.
[Samsung Galaxy Nexus] NCguy:
Sorry to keep asking details but will I need to mess with permissions?
[Samsung Galaxy Nexus] efrant:
Not permissions, no. But you will have to mount /system as r/w (Root Explorer has a little button on the top right to do that for you) as it is read-only by default. Then edit the file and save it, then mount /system as read-only again.
[Samsung Galaxy Nexus] NCguy:
Got it, thank you very much.
[Samsung Galaxy Nexus] Technical:
Well, I'm again here. The situation did not get better.

I could factory/reset the phone and I have 4.1.1 installed.

But the Recovery mode is broken (android with a red exclamation) and I lost root.

The Bootloader is open but I can't boot with CWM anymore. What means I can't get root...

The situation would be the Method 2, but I can't boot CWM either...

I don't know what to do...
[Samsung Galaxy Nexus] efrant:
Not to sound mean, but you have one major issue that if you don't solve, you will never fix your device: you need to take your time and read, particularly what I'm going to tell you now: CLICK ON THE "FLASH" LINK IN MY SIGNATURE. FOLLOW THE INSTRUCTIONS IN THE FIRST POST TO FLASH YAKJU IMM76I.

That is all you have to do. The steps are simple, and it is not difficult to follow. I'm mentioned this to you before, but you don't seem to want to take my advice.
[Samsung Galaxy Nexus] marky9074:
By the way, the chainsDD su.zip in the first post did not work for me...

I ended up using the one in the post below which worked fine :good:

http://xdaforums.com/showpost.php?p=27990824&postcount=3
[Samsung Galaxy Nexus] efrant:
You're right. That one was old, and I forgot to update the link for Jelly Bean.

If you want Superuser instead of SuperSU, see post #2 in the "flash" link in my signature.
[Samsung Galaxy Nexus] marky9074:
Just one question.. I guess I can just delete superuser.apk from /system/app and then reflash the other zip from your link?
[Samsung Galaxy Nexus] efrant:
You should be able to, yes.
[Samsung Galaxy Nexus] foxgalaxy:
URL

http://android.clients.google.com/p....signed-takju-JRO03C-from-IMM30D.5417aa8f.zip
[Samsung Galaxy Nexus] oldblue910:
I'm going to mirror that on randomphantasmagoria.com right now. Thank you!
[Samsung Galaxy Nexus] tailsthecat3:
Really hope somebody gets a hold of the vzw update zip sooner than later. Before the ota. /hopeful
[Samsung Galaxy Nexus] fpbasilio:
I noticed that after updating to 4.1.1 my GPS does not lock. Read about faster fix app but it says that busy box is not Installed. (I am rooted and titanium backup works fine) I tried using busy box Install apps from market but it fails. Any help ?
[Samsung Galaxy Nexus] luffyp:
It's not rom-related and you're not alone. It's probably due to a solar flare. http://xdaforums.com/showthread.php?t=1787375
[Samsung Galaxy Nexus] Dambuzbee:
Have you tried an older versions of busybox? Its possible the one your trying to install isn't compatible.
[Samsung Galaxy Nexus] fpbasilio:
I tried lower versions of busy box too. Still failed. Is there a way to install manually ? As for solar flare.. hmmm hope that's the case. Certainly hope its not hardware trouble
[Samsung Galaxy Nexus] spaceman860:
Go here http://xdaforums.com/showthread.php?p=29136222

Sent from my JB Yakju Nexus
[Samsung Galaxy Nexus] efrant:
Note: if you do that, make sure you back up the original file (or know how to extract it from the factory image), otherwise the next OTA update WILL fail.
[Samsung Galaxy Nexus] TWiTCommander:
yakjujp 4.0.2 ICL53F to yakjujp 4.0.4 IMM76K

yakjujp 4.0.2 ICL53F to yakjujp 4.0.4 IMM76K http://android.clients.google.com/packages/ota/samsung_proxima_yakjujp/bffebea53bd4.update_yakjujp_ICL53F_to_IMM76K.zip
[Samsung Galaxy Nexus] efrant:
Great, thanks! First post updated.
[Samsung Galaxy Nexus] andQlimax:
lately some people on my country, that bough a new gnext, have the build imm76k (gsm, yakju!) out of the box

and they don't have any ota notifications for Jelly Bean..if they want update, they need to manually put the 4.0.4 imm76i image to instantly get the OTA

did google forget about the imm76k build or samsung will handle this build, even if is a yakju ?
[Samsung Galaxy Nexus] efrant:
There is NO yakju IMM76K build.
[Samsung Galaxy Nexus] segv11:
I've seen IMM76K as mysid, and as a country-specific yakju{xyz}. The poster probably has the latter.

Sent from my Jelly Beaned Galaxy Nexus.
[Samsung Galaxy Nexus] zafuquazar:
Yes, have IMM76K (4.0.4) on a stock Verizon gnex (mysid)

//toro/tapatalk/ocie
[Samsung Galaxy Nexus] lfisher007:
thank you for sharing. i'm trying
[Samsung Galaxy Nexus] andQlimax:
well..i can assure u, there is..it was strange also for me

but everyone that buy a new GSM galaxy nexus now (at least in italy), have a yakju IMM76K build..they didnt received any ota, their phone was already flashed with that build

the fingerprint is: google/yakju/maguro:4.0.4/IMM76K/
[Samsung Galaxy Nexus] efrant:
Go to Settings>About phone and tell me what ALL the letters in Build number at the bottom.
[Samsung Galaxy Nexus] coluichepensa:
Hi, I'm trying to install JB with CW 6.0.0.7. I have a 9023 IMM76D with ICS 404 stock, rooted, with busy box installed. I tried to instal the jb download from google site (9ZGgDXDi.zip) and I get the following error:

installing update...

verifing current system...

assert failed: apply_patch_check("/system/build.prop", "5a11755c3b67986b1ea8beb466955e9339e3de2c1". "db469a8330031cea064b24c5ff8d7da080a79557")

E:Error in sdcard/applic utili/9ZGgDXDi.zip

(status 7).

Installation aborted.

I checked in the system folder and I have two files with that name the first one is named build.prop.bak. and the second one is named build.prop.

I made several tests without success. I installed the CW 5.0.8.2 but same problem. I restored a clean backup but nothing.

Someone can help me how to fix this problem?
[Samsung Galaxy Nexus] andQlimax:
im asking to the people with that build..i will update this post as soon i get the answer in an italian forum

anyway already about 4 people confirmed that..with android system info it show YAKJU (no other letters) and build IMM76K..this for new phones bought lately

that's what they said at least :)
[Samsung Galaxy Nexus] efrant:
Did you read post#2? See below:

I have yet to see anyone report that in these forums besides yourself. Have any links to posts? Thanks.
[Samsung Galaxy Nexus] andQlimax:
http://www.androidiani.com/forum/google-galaxy-nexus/170066-imm76k-2.html#post1916552
[Samsung Galaxy Nexus] swordfish123:
I already have 4.0.4 stock ICS. But my device is yakjujp. Can i flash 4.0.4 yakju build to make my device yakju. So that later i can get direct updates from google

Till now i have rooted, unlocked bootloader and installed clockworkmod recovery.
[Samsung Galaxy Nexus] spaceman860:
Edit wrong tread
[Samsung Galaxy Nexus] Dolphin Trainer:
Here's a brand new OTA for the Telstra Australian yakjudv Nexus. Released yesterday and updates 4.01 to 4.04. Includes a previously unreleased radio (DVLF1). Radio posted here.

yakjudv IMM76K.I9250TDVLF2 from ITL41F:

http://android.clients.google.com/p...62fc521fd.update_yakjudv_ITL41F_to_IMM76K.zip

I believe the other yakjudv ITL41F to IMM76K update here is Vodafone Australia specific. This link is for Telstra phones.
[Samsung Galaxy Nexus] efrant:
Great, thanks! first post updated.
[Samsung Galaxy Nexus] efrant:
First post updated for mysidspr FG01 from FD02.
[Samsung Galaxy Nexus] Winesnob:
Anyone have the VZW URL yet? Really surprised it's not up yet.
[Samsung Galaxy Nexus] efrant:
Which one? Jelly Bean for Verizon has not been released yet.
[Samsung Galaxy Nexus] tailsthecat3:
Can hardly wait.
[Samsung Galaxy Nexus] Winesnob:
Not officially, but expected that someone would have captured a leaked OTA and URL by this point. It certainly happened for IMM30B and IMM76K, not to mention the search killer IMM76Q. Outside of 4.0 to 4.0.2 I have never had to accept an official VZW OTA.

(And I wasn't duped into installing the search killer. I'm certain it won't make the phone better.) :D
[Samsung Galaxy Nexus] Thorgoth:
hmmmm.....

got a second galaxy nexus for the miss...

was yakjuxw but i did convert it to yakju..it got the 4.0.2 update almost after boot then i had some probs but i did manage to use efrant's guide and install the 4.0.4 IMM76I

now....i did got the 4.1 update notification from the phone..tho it did failed to install..i used command prompt to flash the new radio xxlf1 and when i tried to do the " fastboot flash flash system.img" i got an error showing "Exceed Buffer Size ((0x16000000)

the system.img is the one from the official google site with the nexus images..i did the same think for the phone to get to 4.0.4 so drivers etc etc are ok..now with newest radio xxlf1 cwm6.1 installed and i can not get the damn think to work...

any heads up on what i do wrong?
[Samsung Galaxy Nexus] efrant:
If you use the guide from my other thread, you would be directly on 4.1.1, as the images you would be flashing would be the 4.1.1 images. Try it again using the 4.1.1 (i.e., JRO03C images) as per the guide.

By the way, not sure if it's a type, but the command is not "fastboot flash flash system.img", it is fastboot flash system system.img...

The update from this post will not install if you have the new radio already flashed.

Again, I would suggest you go back to my other thread and follow the steps again to flash all of the JRO03C images.
[Samsung Galaxy Nexus] Thorgoth:
yeah the flash command was a typo...i know it's supposed to be "fastboot flash flash system.img" since i am getting the buffer error..

now the reason i ended up with 4.0.4 was cause i had tha image on my android sdk folder already and then i realised i could just flash the jb one..

tho i did follow all the steps and i know it worked for 4.0.4 i can't see why i get that cmd error about the buffer size..anyway doing it again and see...
[Samsung Galaxy Nexus] efrant:
It's supposed to be "fastboot flash system system.img"...
[Samsung Galaxy Nexus] Thorgoth:
i really can't understand...

basic steps...

flashing bootloader..rebooting..

flashing radio..rebooting..

flashing system...dead..

restart phone...wipe data/cache/dalv

pull out batt...

instert batt..

booting phone..

trying to install cwm..failed..

phone stucked on "google " with the open lock symbol..

finaly got into stock recovery..wipe data...wipe cache...phone rebooting..nope..stucked on google logo...thinks are getting worst...
[Samsung Galaxy Nexus] efrant:
I think you are grasping at straws here. If the system image did not flash, your device will not boot into Android. Period.

Close your command prompt window, reboot your PC, reboot your phone into fastboot mode and plug into your PC. Open a new command window and reflash the images. (If you already have the bootloader and radio flashed successfully, skip them.)

Please carry on this discussion in the other thread, as your issues are not at related to this thread's topic.
[Samsung Galaxy Nexus] Winesnob:
New binaries for toro are posted on Google Developers - JRO03H. Maybe we're getting closer to a little JB love from VZW
[Samsung Galaxy Nexus] segv11:
New binaries will help AOSP toro ROMs become more stable, but won't speed up VZW's "development" and "testing" of their update. I would expect a leak sometime in September or October and an official OTA in December or January. :(

Sent from my Jelly Beaned "toro" Galaxy Nexus.
[Samsung Galaxy Nexus] LudoAnders:
I also have jakjuxw/maguro:4.0.4/IMM76K, bought it last week, I live in the Netherlands but I think it's a German device
[Samsung Galaxy Nexus] efrant:
My question was relating to yakju IMM76K, not yakjuxw IMM76K.
[Samsung Galaxy Nexus] LudoAnders:
Ah my apologies I misread
[Samsung Galaxy Nexus] thechief095:
back to yakjuux

Hi everyone,

My first post, and I apologize if this has been mentioned somewhere in the ~100 pages of the thread before, bear with me.

First off, I used efrant's post to convert from Yakjuux on 4.0.1 to Yakju (IMM76I 4.0.4) and then OTA'd to Jelly Bean, after (like many others) got fed up with the whole Samsung no-update issue

However, after that my device started doing the battery indicator problem found here: http://xdaforums.com/showthread.php?t=1427539

I tried all those solutions to no avail, so I guess my only choice is to try to return the phone to my carrier (rogers) and hope they'll cover it under the warrantee. Being the n00b that I was at the time, I didn't back up my original yakjuux build. Currently I've flashed back to IMM76I, still on yakju

Is there any way I can go from IMM76I or JRO03C yakju back to a Yakjuux build?

Thanks guys
[Samsung Galaxy Nexus] el_charlie:
If there's a Yakjuux build around here you can flash it. but you can stay stock in yakju 4.1.1 and the relock the bootloader. They should cover the warranty like that because you're on a stock unmodded ROM with a locked bootloader.

Cheers!
[Samsung Galaxy Nexus] efrant:
There is a stock yakjuux build here.
[Samsung Galaxy Nexus] walkamake:
Hi all.

Has anyone already tried new way of installing OTA update with stock recovery, locked bootloader and no root via adb?

I found this option on JRO03C (JRN84D not checked)
[Samsung Galaxy Nexus] efrant:
That is a feature of the latest stock recoveries that come with Jelly Bean. I think most people following this thread have, by now, unlocked their bootloaders, so they would likely not have tried it.
[Samsung Galaxy Nexus] walkamake:
I want to say that maybe it's new way to install OTA by Method 4 in your first post? I've tried install OTA from 76i to 03c in 03c recovery and it seems to work.
[Samsung Galaxy Nexus] efrant:
If I have some time, I will try to write it up and add it to the first post. However, I will probably have to try it out myself, unless someone can write it up?
[Samsung Galaxy Nexus] thephantom:
Thinking out loud here. I don't think method 4 will allow it since it means everything is stock and locked bootloader. 4.0 recovery is different from 4.1 so stock recovery of 4.0 won't have that option yet. It may be possible with the takju 4.1 to 4.1.1 ota update because the Google i/o version already has the new recovery. If walkamake tried the install from 4.0 to 4.1 on the jb recovery then that means it's not pure stock anymore. Hope I'm making sense here.
[Samsung Galaxy Nexus] efrant:
Yes, it makes sense. That is what I was trying to say: it is a viable method to upgrade from 4.1 and newer for those with locked bootloaders and no root (but it won't work for those on 4.0.4 and older). So for the next update, an unlocked bootloader or root won't be required.

To all: if anyone has updated to 4.1.1 from 4.1 using the stock recovery ADB method and would like to write up a brief step-by-step for everyone, I'll add it to the first post. Otherwise, I'll write it up when the next OTA update comes out.
[Samsung Galaxy Nexus] sam_i9250:
Revert to original I9250XXLA2 IMM76K.I9250XWLD2 Rom

Hi all,

I recently updated to JRO03C 4.1.1 without having proper backup of the original 4.0.4 IMM76K.I9250XWLD2, Baseband I9250XXLA2 Rom.

I now would like to revert it back to its original, and I have searched everywhere for the Rom but without much luck.

Would anyone know where/how I can grab a copy ? I need to have the version numbers appearing exactly the same as that of the originals.

Thanks and Cheers.
[Samsung Galaxy Nexus] efrant:
If you want yakjuxw, you can find 4.0.1 here. From there, you will receive all the updates OTA to get you to IMM76K.
[Samsung Galaxy Nexus] sam_i9250:
Thanks for the quick reply.

So I'll just install ITL41F.XWKK9, and from there then it would update to 4.0.4 IMM76K.I9250XWLD2?

Regards.
[Samsung Galaxy Nexus] efrant:
Yes, that's what should happen.
[Samsung Galaxy Nexus] felix021274:
Recently bought a Galaxy Nexus...trouble updating to 4.1.1

I past through Riyadh airport recently and got the phone for a good price (compared to European prices!). I thought it would just be a case of an OTA update but no so simple.

The current build number is : IMM76K.I9250JPLE1 and it's on Android 4.0.4

I have rooted the handset and have ClockWorkMod ROM Manager v5.0.1.1. I have also installed BusyBox and Titanium Backup. I can't seem to find the relevent zip file to go from my build number to the latest and greatest version on Android.

Any help will be much appreciated!

Thanks in advance.
[Samsung Galaxy Nexus] efrant:
Please edit your post to remove the quote of the OP. There is no need to quote the first post in its entirety...

As for your question, there is no Jelly Bean update for yakjujp yet. You need to flash yakju or takju. See the "flash" link in my signature.
[Samsung Galaxy Nexus] felix021274:
Sorry about that..can't seem to edit the post to get rid of it all!

I followed the instructions..all seemed to go well until the final reboot but now the phone is stuck on Google logo. Worried.
[Samsung Galaxy Nexus] efrant:
A mod already edited it for you.

As for your issue, go back and re-flash the system, boot and userdata images, and erase the cache image again, then reboot. If you are still having issues, please post in the other thread, not in this one -- this thread is related to the OTA updates, not flashing the factory images.
[Samsung Galaxy Nexus] felix021274:
Appreciate the quick replies

There seems to be a problem with this step;

9) Flash the system partition: fastboot flash system system.img

I am getting "FASTBOOT STATUS - FAILExceed Buffer Size"

Any ideas?
[Samsung Galaxy Nexus] efrant:
See below:
[Samsung Galaxy Nexus] walkamake:
Ok, I installed 4.0.4 google image, then installed JRN84D takju on my phone via one-time-boot CWM. Then locked bootloader.

Then I went into stock recovery and choosed "apply update from ADB". Then wrote in cmd "adb sideload edfff6d328f1.signed-takju-JRO03C-from-JRN84D.edfff6d3.zip"

And update was installed. And now I have JRO03C takju.

So, it works.
[Samsung Galaxy Nexus] efrant:
Excellent, thanks!

I'll add it to the first post (when I have a minute) and give you credit.
[Samsung Galaxy Nexus] evil_penguin:
Just wanted to ask, why don't you support touch CWM recovery (5.8.0.2)? What's wrong with it ?

i am using 5.5.0.2.
[Samsung Galaxy Nexus] Zepius:
there were reported problems with it.. plus people touch things they dont mean to and like format their sdcard.
[Samsung Galaxy Nexus] evil_penguin:
Thanks for the information!:good:
[Samsung Galaxy Nexus] efrant:
First post updated. Thanks again.
[Samsung Galaxy Nexus] whitedragonz83:
Would this method of patching also work for tweaks such as "[FIX] Galaxy Nexus GSM low latency audio for Jelly Bean" http://xdaforums.com/showthread.php?t=1777261 ?

If so, would it be the same commandline of "adb sideload *.zip"?

Thanks
[Samsung Galaxy Nexus] efrant:
That's a very good question. I would take a guess of "no" because the stock recovery likely checks the signature of the file before flashing. So, unless you can get a hold of Google's platform keys :D , I think we are out of luck.
[Samsung Galaxy Nexus] walkamake:
As efrant said, it's impossible because recovery checks signature

I've tried install some .zip mods and rom, but failed
[Samsung Galaxy Nexus] tailsthecat3:
Waiting...
[Samsung Galaxy Nexus] efrant:
First post updated with yakjuvs IMM76K from ICL53F. Thanks ffosilva!