yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Mickosis:
Me too I seem to get the Error 1 on CWM upon flashing jb-takju.zip

I have flashed it before, just not with the bootloader and radio imgs. Maybe we should flash jb-takju first? Before the two?

Update: Okay still got the Error 1. @___@

Update 2 : It's now fixed! I rooted the 4.0.4 ROM first and installed recovery via the CWM App.
[Samsung Galaxy Nexus] superdx:
I followed this guide to the letter, with the exception I did it with a Parallels VM running Windows 7 64-bit, it still worked perfectly. If you're on a Mac, you don't need to run off and find a Windows machine...!
[Samsung Galaxy Nexus] efrant:
You don't even need Parallels - it will work natively in MacOS. :)
[Samsung Galaxy Nexus] Mickosis:
BTW efrant,

Is there a way to check if I got to flash the right bootloader and radio imgs? Kinda noob in those 2 things as I always use stock imgs
[Samsung Galaxy Nexus] efrant:
Reboot your device into the fastboot mode. There you can read the bootloader and radio your device is using.

For stock takju/yakju IMM76I, you should have LA03 and XXLA2

For stock takju JRN84D, you should have LC03 and XXLF1

Bootloaders and radios can be found in the bootloader and radio threads, respectively.
[Samsung Galaxy Nexus] Mickosis:
Thanks for the quick reply! Enjoying stock JB right now.
[Samsung Galaxy Nexus] Nano3:
A bit help needed

How do i do this? Where is this file located at? CWM will not stick to the phone without doing this and i get a crashed alien when booting into recovery
[Samsung Galaxy Nexus] Rodrigo Ark:
Hi efrant

Do you know if there is a method to upgrade to ("stock" without modifications) jb from ics 4.0.4 yakju build with CWM recovery, bootloader locked on gsm galaxy nexus without having to wipe the information on the phone?

If there is a way could you show me? And if it will be the same OTA that Google said will send for all the galaxy nexus in the next weeks.

Thank you
[Samsung Galaxy Nexus] efrant:
I gave you the file location... :confused:

If it is too complicated, don't do it; just reflash cwm after and delete the file once you have root. Or wait for the ota.

As I said in post #2, it may or may not work without wiping data. It will certainly work if you do wipe though.

The best thing is to wait to for the ota.
[Samsung Galaxy Nexus] Rodrigo Ark:
Thank you,

So, when Google release the OTA I Just have to download from here (because I think here will be the first place where someone put it) and install with CWM recovery like any other OTA right?
[Samsung Galaxy Nexus] efrant:
Correct.

(The problem we have at the moment, is that the update is only for takju IMM30D -- if you are running yha build, you can update to JB without wiping. Once the updates become available for the other builds, you can update without wiping.)
[Samsung Galaxy Nexus] Rodrigo Ark:
Thank you, understood!

that's why someone flash the takju IMM30D stock image and then upgrade to jb with the OTA but in order to do that you HAVE to wipe the phone.

Well, so I'll wait for Google's OTA.
[Samsung Galaxy Nexus] shooter365:
I can't send SMS with my GN with stock rom and kernel, please help!
[Samsung Galaxy Nexus] efrant:
You prob messed up your SMSC settings. See here to fix: http://wiki.cyanogenmod.com/wiki/SMSC_Updates
[Samsung Galaxy Nexus] Su_Tweetz:
Questions related to recovery and CWM flashable files

Hi Efrant,

Thanks a lot for the guide again! Few questions before I try it out:

1. I am a bit confused about this recovery image. How do I check which recovery image I have at the moment? (I'm guessing it's stock but not really sure.)

When I converted my build to Yakju from Yakjuxe according to your guide, I rooted the phone. In the process as you have said, I downloaded and changed the file name to cwm.img to get root access and to install SU as per your guide. I assume this does not mean I have installed CWM recovery 5.5.0.2. Can you install a recovery without flashing a ROM? What is the purpose of it? If can, and if I do that, does this mean I will get future OTA updates?

2. Just to understand the technical aspect, can you briefly explain how these fastboot files work with the relevant images? Does it act like a bridge to install these images? Why are we opening a command prompt in the folder which the fastboot files are? And do these fastboot files also have different versions? (Can I use the fastboot files which I downloaded in your first post to use in the method in this post and in the future as well?)

3. With regard to the two methods described in your post to install JRN84D:

In both methods, you have mentioned to use to the CWM flashable radio, image and the bootloader. Why are there two files in each down location if you only need CWM files for both methods?

In radio download post the two files are CWM-radio... and radio-maguro..., similarly in the bootloader download post you get CWM-...-lc03 and bootloader-maguro-...-lc03. However I noticed one file is .zip while the other is .img.zip - Just let me know the difference and whether I need both the files.

I can remember in the first post, when converting to Yakju, the files that you have pointed to download started with radio-maguro... for the radio and bootloader-maguro-...-la03 for the bootloader - What is the difference betweem this and the CWM flashable files?

4. Out of curiosity, what is Dalvik Cache?

I did check some other articles, but I like the way how you address these issues. So I would like to get your answers. Thanks in advance!
[Samsung Galaxy Nexus] shooter365:
It works!! Thanks ! You saved my day!
[Samsung Galaxy Nexus] efrant:
@ Su_Tweetz: wow that's a lot of questions! :) I'll answer them when I'm in front of a PC.
[Samsung Galaxy Nexus] tawheed12:
I just bought a galaxy nexus just to try jellybean out, it was already rooted and had CWM installed. I followed these instructions, wiped cache, dalvik etc and installed the radio, kernel and jb-takju.zip file using CWM. Everything works fine except if I try to go into recovery now all I get is a android with a red triangle in him.. I'm assuming I lost CWM somehow, no matter, I just want to get the stock recovery back on .. Where would I find this?
[Samsung Galaxy Nexus] dannycorker:
OK, a little confused by the number of guides floating around. New GNex coming in next few days, I want to root it but ensure I get updates OTA from Google as soon as possible. Not too bothered about flashing cutom ROMs yet, might just enjoy stock for a while first (coming from HTC with ICS port).

So which method should I use? Am I fine to just use the toolbox or should I follow the steps here? In the UK by the way.
[Samsung Galaxy Nexus] thephantom:
You can use whatever method you like but for you to learn and understand the process, nothing beats the efrant method

Jellybean on my Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
The Android with the red triangle IS THE STOCK RECOVERY.

There are two files included in every OTA update that are responsible for re-flashing the stock recovery on every boot. If you do not rename (or delete) one or both of them, the stock recovery will replace whatever recovery you flash.

The files are:

/system/etc/install-recovery.sh

/system/recovery-from-boot.p

As thephantom suggested, if you want to learn anything (and you should want to), use the instructions posted in this thread (or one similar I guess). I NEVER advocate toolkits: they are not any faster/easier if you know what you are doing, and if you don't know what you are doing, you won't learn, and will never know how to troubleshoot any issues that may arise on your device. You'll be right be here posting: "PLZZ HELPS!! I HAZ NO IDEA HOW TO FIX MY FONE!!" ;)
[Samsung Galaxy Nexus] efrant:
If you haven't flashed anything, then you have the stock recovery coresponding to the Android build version you are currently running.

If you followed these instructions, then no, you did not install CWM, you simply booted it.

A ROM and a recovery are two different things, so yes.

A recovery is like a mini ROM, a mini operating system. It is limited in its functionality, but it allows you to do certain things... usually to "recover" your device if something goes wrong with your main operating system (your "ROM"). The stock recovery is very limited in its functionality; custom recoveries like CMW, have significantly more functionality.

There are a few things to remember here:

1) Receiving the OTA notification on your device saying something like "there is an update available" is different from actually being able to update your device with that OTA update. Most,if not all ROMs will get a notification saying that there is an update available (even custom ROMs), although having it install requires a stock ROM (and usually kernel and radio).

2) You will probably see the update file here on XDA (most likely here) before you get it on your device. See instructions in that thread on how to install.

3) Manually updating your device with an OTA update file like mentioned above works the same way as having it done automatically, but having it done automatically requires the stock recovery from the Android build you are running.

I'm not sure I understand everything you are asking here, but fastboot, I guess, refers to a few things: a) the mode" on your device when you boot it by holding vol+/vol-/power, b) the fastboot.exe file on your PC, and c) the actual interface. It has a few different commands (some are: flash, boot and erase). Flash allows you to flash all most of the partitions on your with images stored on your PC. Using fastboot will replace what ever you have in that partition with the image you are telling it to flash. Boot allows you to boot kernels from your PC without flashing them to your device. Erase does just that, it erases partitions. To you fastboot commands, you need to run them in a command prompt. As for different versions, yes, there are, but for our purposes here, you can use any version of fastboot -- the ones in the first post are fine.

One file is a zip file packaged up so that CWM can flash it -- CWM requires anything that needs to be flashed to be packaged up a certain way, with a certain script. The other file (the .img.zip) is just the image in a zip file -- you can extract the image and flash it in fastboot if you want, instead of downloading the CWM-flashable version. It makes no difference.

See above.

Android is a virtual machine that runs on a linux-based kernel. That VM is named "Dalvik". Without getting too technical, the Dalvik cache is a cache that the VM needs to operate. If you wipe it, the VM will rebuild it on the next boot. (That is what is happening when you see "Android is optimizing applications" or whatever message is displayed when you flash a new ROM.)
[Samsung Galaxy Nexus] shooter365:
If I want to flash the stock recovery do I only need to flash the deleted file? I thought about the file you mentioned in your instruction.

Or I need to flash

When yes in which order?

Thanks

Gesendet von meinem Stock Jelly Bean GN
[Samsung Galaxy Nexus] efrant:
If you used method 1 in post #2 of this thread to flash JB, then yes, if you copy back the install script, it will automatically flash the JB stock recovery.
[Samsung Galaxy Nexus] shooter365:
Yes I used this method. Thanks.

Gesendet von meinem Stock Jelly Bean GN
[Samsung Galaxy Nexus] dannycorker:
Sounds sensible to me! Quite happy with adb etc, was just checking that both methods were in fact the same. Thanks for the reply :)

Sent from my Desire HD
[Samsung Galaxy Nexus] tawheed12:
The amount of great information in this thread is amazing! Thanks, efrant! One quick question, I notice now my sdcard shows up also as \storage\sdcard0 - is this normal for jelly bean?
[Samsung Galaxy Nexus] efrant:
Yes, everyone on JB has that now. Not sure why Google thought we would need an extra mounting point though. Prob has to do with some app incompatibilities.
[Samsung Galaxy Nexus] tawheed12:
Must say, I've learned more about android modding from this thread in the last 12 hours than I had in the last two years.. Did it all on my mac too, thanks again, sir! There's so much scattered information out there and this much useful information plus your quick responses are extremely appreciated!
[Samsung Galaxy Nexus] FecalLord:
Stuck at step D-10, first time flashing!

Hi everyone I'm completely new at flashing phones here, but understand the concept and read the guide and for the most part it has been very easy to follow.

I successfully unlocked the bootloader, flashed bootloader, flashed radio and rebooted after each one.

I then flashed system and did the same for userdata right afterwards (no restart in between). But the userdata flashing was sent ok, and is now stuck at writing 'userdata'...

How long is this step supposed to take, as it's been about 10+ mins now

Any help would be appreciated as to what I should do next, eg CTRL+C in CMD and reboot before flashing this step again?

EDIT: I just pit the bullet, and did as above to restart and flash again and it finished in 11seconds. So I'll see how the rest of the steps go from here, thanks all the same!
[Samsung Galaxy Nexus] efrant:
Yeah, just close the command prompt and reopen it and try again.
[Samsung Galaxy Nexus] FecalLord:
Thanks a lot!

I got it all done and I'm loving 4.0.4 (was on 4.0.1 before), just in time to wait out the official JB Rom going up.
[Samsung Galaxy Nexus] thegios:
Any chance to have the new official and stock JRO03C (JB 4.1.1)?

I know where to find it here but it's already rooted and unfortunately DEODEXED... :-(
[Samsung Galaxy Nexus] thephantom:
You have to be a little patient on this mate. Source codes have just been released so it'll be a couple more days for the factory images to come out. But when they do, for sure it will be posted
[Samsung Galaxy Nexus] thegios:
well I was asking as the guy here > http://xdaforums.com/showthread.php?t=1737849&page=318 already has 4.1.1 rooted and deodexed, but since I have been told the deodexed roms are slower, I wanted to wait for an official stock one (I already have the 4.1 linked at post n.2 here).
[Samsung Galaxy Nexus] Su_Tweetz:
Hi Efrant,

Got loads of my questions answered from you in your last reply to my post and I've gained alotta knowledge thanks to you! And here comes more! :)

I noticed that in the Google developers site they have released the latest binaries - developers.google.com/android/nexus/drivers#panda (cannot hyper-link as yet)

I haven't flashed JRN84D yet (I was planning to do so tonight on my Yakju GN). Now it seems like in the developers site, that particular build is not there which is now replaced with JRO03C. Should I go ahead with JRN84D or can I just download the JRO03C from the site and flash it like before when I did to convert to Yakju? - Just wanted a heads up from you and a guide too if there is anything else that needs to be done.

And also, I noticed that Nexus 7 now goes as "Grouper" whereas it was "Nakasi" before if I remember correctly. Any idea why? (just curious)

Thanks in advance!
[Samsung Galaxy Nexus] efrant:
That is a AOSP build, not a stock build. The JRO03C source has been released to AOSP, but Google has not provided a full stock ROM or an update yet.

It seems like JRO03C full ROM will be out in the next few hours/days, so you might as well wait for that. You can flash the full ROM as per post #1. No other special instructions.

The OTA to JRO03C should be out at the same time as well, and we are guessing that there will be one from JRN84D to JRO03C, so you could also flash JRN84D if you are impatient :) and you should get the updated to JRO03C.

No idea.
[Samsung Galaxy Nexus] Su_Tweetz:
I got a bit confused there. I have mistaken binaries for factory images. The latter which I assume is the full ROM.

I might as well flash the JRN84D for now since I'm a bit impatient :rolleyes:

And also I think I have a broken recovery atm cuz when I go to fastboot mode and scroll to recovery and select there's an Android bot lying down with a red triangle. I wonder why this is happening. I'm gonna flash CWM recovery now.

Just outta curiosity, these factory images released by Google, are these the ones that developers use to port stock images to other Android devices in ways of custom ROMs? Can't these ROMs be flashed as they are to other devices? (I'm guessing not due to hardware differences - just to confirm)

I love the fact I got a Galaxy Nexus and the support is way superior than customer support from the manufacturer even!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] efrant:
I just saw what you were referring to. The binaries that are posted are for the device, which I guess is called grouper. nakasi is the name of the OS build for grouper. This is similar to what it is for other devices. For example, the GSM GNex: takju, yakju, yakju(xx) are the builds, and maguro is the device.
[Samsung Galaxy Nexus] efrant:
What you are seeing there is the stock recovery. To access the menu (from that screen), press the power button and volume up.

Yes, some use those images to port them to other devices, but that is a hack job. When the source is out, you can build it from there.
[Samsung Galaxy Nexus] thegios:
efrant, so pls let us know in this thread when the official 4.1.1 rom will out and possibly post a link: now that I am on your same rom of you signature, I'd rather wait...

I simply hope that to move from 4.1 to 4.1.1 a dirty flash would do and that a cache wipe would be enough ;-)
[Samsung Galaxy Nexus] efrant:
As always:

- If it relates to official updates, I post all incremental updates in this thread.

- If it relates to official full images, I update this thread.
[Samsung Galaxy Nexus] rommel76:
Hi i bought a nexus yday and found out I got yakjuxw, from what I been reading in the forums I should get all updates about a month later than yakju versions. But I updated to 4.04 through OTA update, is that normal?

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] efrant:
Not sure what you are asking. Yakju got the OTA update to 4.0.4 (IMM76I) on April 20th.
[Samsung Galaxy Nexus] rommel76:
My bad then, thanks anyway.

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] Su_Tweetz:
Help!

Hi Efrant!

Need help now :( I was flashing JB just as you have said. All went okay until I tried to flash the last zip file JRN84D. It starts installing and then aborts giving a Status 1 error :S Installation aborted!!!

And when I try to reboot it just keeps booting to CWM.

Please help! Awaiting your reply! :(

I don't have any backups (i'm really worried about this).
[Samsung Galaxy Nexus] thegios:
I was having this probl when modifying the zip to remove the file st step 1, maybr somthing wrong in the compression.

Try the original zip file that worked for me: you csn delete the file afterwards using root explore.

If it fails again, try 2 or 3 mote times right after the error: for some it worked.
[Samsung Galaxy Nexus] Su_Tweetz:
I'm sorry, I didn't quite get what you said there. What do you mean try the original zip file? All what I have in my /sdcard which I can access now through CWM is the relevant zip files which I have downloaded from the second post. And I have renamed the recovery in the jb-takju.zip.

I have the following files atm:

1. Both the bootloader's CWM flashable zip and the stock one (I just copied this, only flashed CWM zip)

2. Both the radio's CWM flashable zip and the stock one (I just copied this, only flashed CWM zip)

3. jb-takju.zip - which is JRN84D

4. CWM SU zip

You mean to repeat from step 1 again? Yeah I think I'll have to give it a try since i'm just stuck at recovery mode atm.
[Samsung Galaxy Nexus] spaceman860:
Do a full wipe flash takju zip then SU zip and reboot go through setup then flash radio then bootlooder zips

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] efrant:
First of all, try to relax. Your device is fine! :)

Second: did you try to modify the jb-takju.zip file, or did you try to flash it as is? It seems people are having problems modifying it, so try flashing it as is.

As was mentioned by the previous poster, wipe data/cache/dalvik again and re-flash the unmodified jb-takju.zip file.
[Samsung Galaxy Nexus] Su_Tweetz:
Just tried that, and it still won't work. Gives the same error message when I try to flash jb-takju zip :S

E:Error in /sdcard/jb-takju.zip

(Status 1)

Installation aborted.

:( :(
[Samsung Galaxy Nexus] thegios:
what I am saying is noy to rename/delete the recovery in the zip file but to use the zip file as originally downloaded.

I was having the same error when renaming the recovery in the zip, so I flashed the original zip.

Do a full wipe and clrar caches

Flash original zip (dony rename recovery)

Flash su

Reboot

Install root explorer, run it and rename recovery file in the phone
[Samsung Galaxy Nexus] Su_Tweetz:
Oh you are back! Bit relaxed now with that :)

All what I did is, I opened the file from 7zip, and renamed the recovery file as you have mentioned in the guide. That's all.

How can I use an unmodified file? Where I can only access the ones that are in /sdcard now since I'm stuck in CWM.
[Samsung Galaxy Nexus] efrant:
Seems people are having issues with renaming the install-recovery.sh file. Forget about doing that.

Download the unmodified file to your PC into the same directory as your adb.exe file, connect your phone to your PC, and open a command prompt. Type:

adb push jb-takju.zip /sdcard/jb-takju-original.zip

Then flash it in CWM.
[Samsung Galaxy Nexus] Su_Tweetz:
This might take around an hour to download (PC runs on a 512Kbps line). I will download it and try it again. Hopefully it will work.

I will give you an update afterwards.
[Samsung Galaxy Nexus] Su_Tweetz:
I downloaded the original file and tried to push it as given above. After I give the cmd in cmd prompt it says the file has been transferred. However, I do not see this new zip file in the /sdcard folder in CWM. Any idea why?

And also, when wiping cache, the following message is displayed after the wiping is complete.

E:unknown volume for path [/sd-ext] - I hope this is normal
[Samsung Galaxy Nexus] efrant:
Try mounting /data in CWM under mounts.
[Samsung Galaxy Nexus] Su_Tweetz:
It seems to be mounted already. It reads the following:

- mount /system

- unmount /cache

- unmount /data

- format /system

- format /cache

- format /data

- mount USB storage

***Go back***
[Samsung Galaxy Nexus] efrant:
Ok, reboot into CWM. If you still can't see it, try pushing it to /data/media instead of /sdcard
[Samsung Galaxy Nexus] Su_Tweetz:
Tried pushing to /data/media. Again in cmd it says transferred. However when I go to /data there are only two folders which are /beautifulwidgets and /titaniumbackup. The file is not being showed there as well.

I rebooted to CWM and checked and still can't see :(
[Samsung Galaxy Nexus] efrant:
Strange. You are typing the command exactly as I posted, right?
[Samsung Galaxy Nexus] Su_Tweetz:
I renamed the file jb-takju.zip to jb-takju-original.zip when I downloaded. Nothing else.

In the cmd I typed:

adb push jb-takju-original.zip /sdcard/jb-takju-original.zip

It says file transfer completed and gives the location and the transfer rate in KB/s and the time it took.

And I also tried the cmd:

adb push jb-takju-original.zip /sdcard/

Again it said file transferred as above.

I can't see it though :(
[Samsung Galaxy Nexus] efrant:
Type the following and tell me what you see:

adb shell

cd /sdcard

ls
[Samsung Galaxy Nexus] Su_Tweetz:
displays: ~ #

I typed: cd /sdcard (same line as above)

displays: /data/media # (in the next line)

I typed: Is (same line as above)

/sbin/sh: Is: not found (next line)

/data/media # (next line)
[Samsung Galaxy Nexus] efrant:
The command is LS in lower case, not IS... :)