OTA Update IMM30B 4.04

Search This thread

cshort0982

Senior Member
Dec 17, 2010
244
104
Texas

Attachments

  • Screenshot_2012-02-04-13-24-13.jpg
    Screenshot_2012-02-04-13-24-13.jpg
    40 KB · Views: 4,537

adrynalyne

Inactive Recognized Developer
Dec 13, 2008
10,950
6,471
That or its a chop.

I haven't had enough otas to know if they start changing around the way information is displayed, but I doubt it. Note top right, it just shows build, not the Android version. Sorry, its in my nature to automatically doubt ota screenshots that conveniently never update.
Verizon-Samsung-Galaxy-Nexus-ICL53F-Android-4.0.2-Update.jpg
 
Last edited:

cshort0982

Senior Member
Dec 17, 2010
244
104
Texas
That or its a chop.

I haven't had enough otas to know if they start changing around the way information is displayed, but I doubt it. Note top right, it just shows build, not the Android version. Sorry, its in my nature to automatically doubt ota screenshots that conveniently never update.
Verizon-Samsung-Galaxy-Nexus-ICL53F-Android-4.0.2-Update.jpg

I'm with ya on that! I'm seeing if I can get the guy to pull the update file and post it. Anyone know how to do this??
 

adrynalyne

Inactive Recognized Developer
Dec 13, 2008
10,950
6,471
It will be under /cache. I've never had a Nexus before now to know what it will be named, but it will be ~29mb.

adb pull /cache/filename.whatever.

Should save to his/her computer.
 
  • Like
Reactions: cshort0982

akellar

Senior Member
Jan 9, 2011
4,007
2,425
Iowa
There are more pics floating around showing this too. New radios and 4.0.4. No clue if real or not of course.

Sent from my Galaxy Nexus using XDA App
 

cshort0982

Senior Member
Dec 17, 2010
244
104
Texas
"i use andexplorer

i checked the cache folder and it was empty (screenshots attached). i ensured that hidden files are to be shown.

SD doesn't have a cache folder"

This is where we are at right now....
 

adrynalyne

Inactive Recognized Developer
Dec 13, 2008
10,950
6,471
Tell him/her to use adb shell.

You cannot view cache from an explorer, unless its a root explorer.

adb shell ls /cache
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Okay, so I recently flashed this rom. Works great, nice and fast, noticeable improvements all around.

    Before I flashed it I was running stock 4.0.2 rooted

    Upon flashing it Ive lost root privilages. So I go to reroot using a terminal in ADB "adb reboot bootloader"

    I get to fastboot, hit recovery, and I get the freakin exclamation point. After scouring around for an answer one such solution seems to be to delete the file /System/boot.p

    I hit mount as R/W in root explorer, attempt to delete the file with a press and hold and tapping delete. I get the message that the file cannot be deleted because it is read-only. Im guessing I cant delete it because Im not rooted(hence mount as R/W) but I cant boot into CWR and root SO i can remove it.
    Here's the deal:
    1) Every OTA update changes the permissions on the su binary, so you effectively lose root access.
    2) Every OTA update to date places 2 files on your ROM that are responsbile for re-flashing the stock recovery (which is what you are seeing, i.e., "the freakin exclamation point") on EVERY boot. As long as these two files exist on your ROM, your CWM recovery will disappear after a reboot.

    What you need to do is re-boot you device into fastboot mode and flash CWM, then boot into CWM, delete those 2 files, then change permissions on the su binary, and you are all set.

    Here's a step-by-step (which assumes you have the drivers for your device installed):
    1) Download the attachment and extract it to a directory on your computer.
    2) Download CWM, rename it to cwm.img and place it in the same directory.
    3) Reboot your device into fastboot mode and plug it into your computer.
    4) Open a command prompt in the same directory and do the following:

    1) Flash CWM: fastboot flash recovery cwm.img
    2) Boot CWM: fastboot boot cwm.img
    3) Open a shell: adb shell
    4) Mount the /system partition as r/w: mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
    5) Change permissions on su (you will need the right path. mine is in /system/bin): chmod 06755 /system/bin/su
    6) Change permissions on Superuser.apk (not sure this is needed, but it wont' hurt): chmod 0644 /system/app/Superuser.apk
    7) Remove the first file: rm /system/recovery-from-boot.p
    8) Remove the second file: rm /system/etc/install-recovery.sh
    9) Mount the /system partition as r/o: mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
    10) Exit shell: exit
    11) Reboot: adb reboot
    12) Done.

    EDIT: I like posting the manual way of doing things, as people learn when they do them that way. But yes, as ATnTdude said, once you boot CWM, you can just flash the su zip file, and it automatically does steps 4,5,6 and 9 for you. You still have to remove the two files yourself.
    2
    So what are those of us that updated to 4.0.3 radios supposed to do? Will the OTA not hit us now either? I'm assuming there's some checksum in place to make sure the 4.0.2 drivers are installed, but why would it check each individual thing? Why not just check main system version then overwrite the rest.

    If I'm going to have to wait for modded 4.0.4 installs I'll be pissed...I like user-made stuff, but not when I have the option to use Google-made stuff.

    You will have to reflash 4.0.2 radios and bootloader temporarily using fastboot before applying the update (which updates them anyways).

    Here's links to each one you will need:

    Bootloader
    Radio
    Radio-CDMA


    Issue the following commands:

    fastboot flash bootloader bootloader-toro-primekk15.img
    fastboot flash radio radio-toro-i515.ek02.img
    fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img


    After that just boot into recovery and try to update again.
    2
    Sorry, here you go:
    Screenshot_2012-02-04-18-21-58.png
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone