Anyone know anything about this??
http://forums.androidcentral.com/ve...ms-hacks/153931-ota-update-imm30b-4-04-a.html
http://forums.androidcentral.com/ve...ms-hacks/153931-ota-update-imm30b-4-04-a.html
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.
![]()
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
SD card? Last I checked, Galaxy Nexus doesn't have an SD card.
Sent from my Galaxy Nexus using XDA App
Yes it does its just internal and not removable
Sent from my Galaxy Nexus using xda premium
Yes it does its just internal and not removable
Sent from my Galaxy Nexus using xda premium
I thought 4.0.3 wasnt released to the public ota, so how are people getting 4.0.4 ota updates?
Here's the other post I mentioned.
http://androidforums.com/verizon-galaxy-nexus/491735-no-rumblings-update-yet.html#post3895993
Sent from my Galaxy Nexus using XDA App
Here's the deal: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.
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.