Related
so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 after i did a full wipe and it installed perfectly but i rebooted my phone to check something and when i did it bootlooped i panicked cause i couldn't restore a backup or get it running again i got REALLY LUCKY and for some reason i was able to get my backup to restore after countless times of trying so now I'm back on m6 i fear of going back to aokp jb until i know it's safe to go from aokp m6 to aokp jb i can't brick another phone has any had this problem or i was just unlucky or what
Sent from my Galaxy Nexus using xda app-developers app
Try to wipe all data and reflash the rom,(including cache+dalvik cache) because every time you flash a rom with a different version of Android this procedure should be done to avoid problems like this
Wipe/Factory Reset
Wipe everything/factory reset and reflash rom and gapps. This will fix your issues. Good Luck!!
I wiped everything the first time im sorta scared to go through it again to see if it will work cause when i flashed it ran perfectly but i noticed when i was trying to change my softkey icons rom control kept force closing for some reason so that's when i rebooted and then i got the boot loop
Sent from my Galaxy Nexus using xda app-developers app
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Zepius said:
dont complain about issues if you dirty flash roms.
if you have problems with a dirty flash, wipe and then reflash.
Click to expand...
Click to collapse
I flashed everything perfect i wiped everything before i flashed the Rom so i didnt dirty flash ive been flashing roms since the first droid so i know how to flash unfortunately flashing this build of aokp didn't go to well for me
Sent from my Galaxy Nexus using xda app-developers app
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue. As for bricking, it's a Nexus. Kinda hard.
Sent from my Nexus 7
masully84 said:
I'm confused you flashed over M6 and didn't dirty flash? AOKP always recommends a full wipe. I flashed Build 3 last night, clean without a single issue.
Sent from my Nexus 7
Click to expand...
Click to collapse
I didnt flash directly over m6 without wipeing everything first before flashing the new aokp jb b3 i think thats where people getting alil confused
Sent from my Galaxy Nexus using xda app-developers app
jave16 said:
so i thought id take it upon myself to download the latest aokp jb build 3 and flashed it over aokp m6 and it installed perfectly
Click to expand...
Click to collapse
you said you just flashed it over.
Zepius said:
you said you just flashed it over.
Click to expand...
Click to collapse
My mistake i was trying to say coming from m6 i flashed from that to aokp jb after i wiped everything first
Sent from my Galaxy Nexus using xda app-developers app
Factory reset
Wipe cache
Wipe dalvic cache
Format system
Flash build 3
Flash gapps
Fix permissions
Reboot
Hey guys, I'm really new to rooting, flashing roms, and Android in general (I've used iOS since 2007 until a month ago... please have mercy on my soul). I have an AT&T GN2 that I would like to remove the bloatware from, hence why I began investigating rooting, but it's snowballed into my desire to try out some of the amazing ROMs that the developers here have produced. Since the Note 2 uses the Exynos 4, I rooted using the ExynosAbuse exploit and downloaded Titanium Backup to freeze the AT&T apps. So far, so good.
However, I am wanting to get into how to flash custom ROMs, like CyanogenMod, so I downloaded the CWM RomManager and flashed the CWM Recovery. I downloaded the CyanogenMod 10.1 release for the i317 model (here: http://forum.xda-developers.com/showthread.php?t=2024495) and the latest gApps package (for 4.2.1), and flashed both from CWM RomManager. When it rebooted, it showed the CyanogenMod boot screen, but it appears to be stuck there. I'm not sure what to do at this point, and am hoping I didn't brick my phone. Is there anything I can do at this point?
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Have you changed kernel???
Sent from my MT11i using xda app-developers app
id10terrordfw said:
Use the three button combo to get into recovery, should be volume up, home, and power, and then wipe data or install a stock rooted ROM. That should help get you to a bootable stage.
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
When I booted into recovery, I got the CWM recovery (which is a good thing, I suppose). I wiped the cache, and then installed the CM 10.1 zip and gApps zip. However, I think I still need to wipe data/factory reset, right?
So, at this point, I've:
1. Rooted the device using Chainfire's ExynosAbuse apk (super easy).
2. Installed RootChecker (success) and TI backup (froze bloatware apps).
3. Downloaded CWM RomManager.
4. Flashed CWM Recovery.
5. Downloaded CM 10.1 port for i317 (the AT&T GN2 model) and the 4.2.1 gApps zips.
6. Chose to install ROM from SD card in RomManager, added both CM 10.1 and gApps, and only selected install (did not wipe cache or user data at this point).
7. Received blue CyanogenMod boot screen... excited... but it remains on the boot screen. Sad face.
8. Removed battery to power the device off, placed battery back in, and then booted into recovery mode (CWM recovery).
9. Installed the CM 10.1 zip and gApps zip from SD, then wiped cache.
10. ???
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Peleus16 said:
Have you changed kernel???
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
This is a great point, at no point op has mentioned kernel.
Sent from my SAMSUNG-SGH-I317 using xda premium
cdshepherd said:
Wipe data factory reset. Wipe cache/dalvik. Flash cm, flash gapps. Reboot
And dont use rom manager. Do it in recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
NowhereOutThere said:
Okay, booted into CMW recovery and performed all in that order. It booted! Hurrah. Only problem: the AOSP keyboard crashes constantly, making text input not possible. Sigh...
Click to expand...
Click to collapse
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Boot back into recovery and fix permissions. That may help
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
NowhereOutThere said:
Okay, I booted into recovery mode and fixed permissions... the keyboard still crashes, which means I can't type anything. Do I have to do anything with the kernel? I didn't wipe the dalvik cache, should I have done that?
EDIT: wiped dalvik cache, didn't do anything... apparently, this was a fine release so I'm not sure what could be causing the keyboard issues.
Click to expand...
Click to collapse
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Im not exactly sure either. I have yet to flash cm. Read the cm thread?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
NowhereOutThere said:
So what ROM are you using? I just picked cyanogenmod because I've heard of it before, but I would like something that works. Is there a way to add another ROM onto the phone's storage, as I don't have an SD card... And since I can't type anything, it's not like I can download it from the phone's browser?
Click to expand...
Click to collapse
Plug it into your computer and see if you can mount your internal sd. If you can download a new rom to your computer and transfer it to sd. Did you make a backup before flashing?
Im just running stock rooted for now.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Well, I'm downloading CleanROM right now. I also downloaded another cm 10.1 file just in case, perhaps it's because I downloaded it on the mobile Chrome browser that I'm having problems? I also downloaded a kernel from the thread to help with performance. However, if I can't get these on the phone, it doesn't matter. Since I'm on a Mac, I have to use Android File Transfer, and it isn't registering my phone, unfortunately. I may have to go out and buy a cheap SD card and throw the files on there. It may not hurt to have one around, anyways.
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
Text yourself the download link to CleanRom. :thumbup:
And chrome shouldnt have made a difference. I take it you didnt make a nandroid backup before you flashed cm?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
No... I thought that a backup of the original ROM was made when flashing CWM recovery, but I am a noob and that did not happen. Unfortunately, the browser doesn't even work! So I cannot text myself the link for the download. I should be able to flash a zip file from a micro sdhc, right?
Flash the right GAPPS, the crashing keyboard is a symptom of incorrect GAPPS. The December one is for 4.2.1 only, which is what CM10.1 is based on. Make sure you flash the right GAPPS with the right CM version.
Sent from my GT-N7105 using xda premium
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
ManelScout4Life said:
The CM you linked in the OP is CM10 not 10.1, so you flashed the wrong GAPPs
Click to expand...
Click to collapse
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Just grab goo manager from the market and dl the correct gapps to your phone. Either that or use your phones browser. No need for a pc. Boot in recovery, wipe cache and dalvik and flash correct gapps. Should be gtg.
Edit: just saw your browser isn't working. Goo manager's your best bet. Could always try another browser from the market as well. Good luck.
NowhereOutThere said:
Oh... crap. Is there any way I can get the correct gApps on my phone? Ugh... I'm going to have access to a Windows machine today, so I can download the correct GAPPS and put them on my flash drive. I can still put it in USB debugging mode, but will the PC recognize it? Android File Transfer software for Mac does not recognize the phone any more, so I'm a bit limited in what I can do. Unless, like I said before, I can just pop in an SD card with the correct file.
Click to expand...
Click to collapse
While in recovery plug usb into computer (make sure drivers are installed) in recovery menu navigate to mount usb storage. See if that works
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Sorry for the noob question. I searched but i couldn't find the answer I'm looking for. Here's the deal...i have had alot of rooted phones but i just rooted my own phone for the first time,obviously the GNex. I used the toolkit i found on here and it went great. I am using TWRP recovery cause it was recommended by AOKP and when i flashed there new Jb ROM i noticed how twrp is set up a lot different then CWM. I found out that i had to factory wipe before flashing. So getting to my question. When i flash the update do i do that same wipe or do i wipe cache,davlik and/or system? Also i gotta do a back up first right? Then with gapps is it the same steps as flashing the update? If someone can show me the way that would be great. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
[email protected] said:
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
Click to expand...
Click to collapse
Thank you. I wasn't sure exactly what to wipe........my ass i know, but still learning this stuff.
Sent from my Galaxy Nexus using xda app-developers app
EddyOS said:
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Click to expand...
Click to collapse
If you're staying on the same rom with just an update you probably don't have to wipe unless you have issues upon reboot but otherwise you probably always should.
so i got an update notification from goo saying my rom and gapps have an update (aokp jb 4.2 mr1 build 2) so i flashed em and i got my stock reboot screen then every google app foreclosing over and over but rom still there. what the hell????
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
elliot2112 said:
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Toro would be Verizon.
sent from my Google Galaxy Nexus
bk201doesntexist said:
Toro would be Verizon.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
ok it is build 2 on aokp. so gapps must be the same one i have been using? because this new one everything was foreclosing.
Better off doing updates manually and not using an app to do it for you
elliot2112 said:
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
Click to expand...
Click to collapse
From the date I think you flashed a gapps for jb 4.1 on a 4.2 ROM. Pretty sure that the 4.2 gapps is dated 12/12/12.
EddyOS said:
Better off doing updates manually and not using an app to do it for you
Click to expand...
Click to collapse
ya thats what im about to do now.
i went and downloaded build 2 straight from aokp and flashed that with same gapps for build 1 cause that hasnt changed on there site. my boot animation is the stock nexus logo instead of that pink unicorn with the gears. i figured it still wasnt working but everything seems to be running normal.....actually really fricken smooth and snappier. thanks for all your input everybody!
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.
Whiplashh said:
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Click to expand...
Click to collapse
I am running the latest M snapshot which can be found here. Its date added is: 2013-01-21 02:18:19 and it is 163.46 MB.
kj4pvf said:
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.
Click to expand...
Click to collapse
Were you on Ktoonsez kernel? Also, what gapps are you flashing?
LakeSoccer2 said:
Were you on Ktoonsez kernel? Also, what gapps are you flashing?
Click to expand...
Click to collapse
I was on Ktoonsez for 10.1 as I am now, and I flashed the correct kernel for 4.2 because I triple checked before I flashed.
When I installed 10.1 I flashed the 20121212 gapps.
Right now, on 10.0, I'm using 20121011.
I got the gapps from roozwiki
I'm running the nightly cm10.1 with the stock kernel, and the camera is lovely.
sent from a secret underground bunker
kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
Per other suggestions, and not trying to browbeat you, but flashing to a newer better version of CM (10.1 M version) is a not too burdensome final solution to your problem.
But if you are loathe to do it for some unstated reason... nm.
HTH
Sconnie
Thanks guys. I will upgrade to 10.1 just with stock kernel to see if that fixes the problem. Just one more quick question, can I use the built in CM upgrade to upgrade directly or do I need to re-flash with the new gapps?
All help is greatly appreciated
Sent from my SPH-L710 using Tapatalk 2
I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker
mjben said:
I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm having the same issue but it's happens on other rooms as well.
Any suggestions
Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2
kj4pvf said:
Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
How are you at wiping partitions and flashing zips?
Personally, I would mount and format the system partition, then install the cm zip and gapps. Wipe you're caches and then I would expect everything to work fine.
Remember, always make a nandroid backup!
sent from a secret underground bunker
Well what I've been doing is:
1. Go into clockwork and wipe data and cache partition
2. Wipe cache partition just to be safe
3. Wipe dalvik
4. Flash rom then gapps and restart.
That's how I've been doing it this whole time
Sent from my SPH-L710 using Tapatalk 2
Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker
I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2
kj4pvf said:
I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
The 0 folder is normal, from JB and up all data is stored there (why, I dont know)
Sent from my PG06100
mjben said:
Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker
Click to expand...
Click to collapse
I've tried all suggestions listed on this to fix the same issue on any ROM's I use. Would there be a mod or something out there that I could flash to replace it. All I get is a failed to connect to camera.
I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker
mjben said:
I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker
Click to expand...
Click to collapse
The camera works 100% in stock, even when rooted and with a custom kernel, the camera works with the stock rom.
Must be a firmware issue.
Hi
So I decided to install CyanogenMod on my Galaxy Nexus. I unlocked the bootloader, installed TWRP, but when I tried to install the .zip, I got an error 'Error executing updater binary'. Tried CWM too, got Status 7. How can I fix this? Thanks
Maybe a corrupted download. Try re-downloading it.
adamgraver said:
Maybe a corrupted download. Try re-downloading it.
Click to expand...
Click to collapse
Tried it already, didn't work.
Sent from my One M8 using XDA Free mobile app
Go into mounts and unmount system. That fixed errors for me.
Sent from my Galaxy Nexus
applerulez1 said:
Go into mounts and unmount system. That fixed errors for me.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Already was unmounted. Tried mounting it, but installing the zip seems to automatically unmount it.
Sent from my One M8 using XDA Free mobile app
What .zip are you trying to flash? I could try it on mine, are you sure its flashable or for your model? I'm running out of ideas sorry. Possibly reinstall your recovery if all else fails.
Sent from my Galaxy Nexus
applerulez1 said:
What .zip are you trying to flash? I could try it on mine, are you sure its flashable or for your model? I'm running out of ideas sorry. Possibly reinstall your recovery if all else fails.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm trying to flash the latest Cyanogenmod nightly, I'm sure it's flashable and I have reinstalled the recovery several times already. Even tried an older version of TWRP.
Sent from my One M8 using XDA Free mobile app
Okay so how I did that was I actually just installed the latest stable cm10. Then I went to the update section in settings and tapped update. It will update you to the cm11 snapshot, that is as far as I went but it also allows you to update to night builds as well. So just install cm10 and go from there, that's what I did at least unless somebody chimes in an easier way.
Sent from my Galaxy Nexus
applerulez1 said:
Okay so how I did that was I actually just installed the latest stable cm10. Then I went to the update section in settings and tapped update. It will update you to the cm11 snapshot, that is as far as I went but it also allows you to update to night builds as well. So just install cm10 and go from there, that's what I did at least unless somebody chimes in an easier way.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Tried it, didn't work. Now I'm stuck at the CM11 bootlogo (yes, CM11). And yes, I did clear cache.
Sent from my One M8 using XDA Free mobile app
Go back to stock then try what I said above again. It is possibly a hardware issue. I wish you luck c:
Sent from my Galaxy Nexus
applerulez1 said:
Go back to stock then try what I said above again. It is possibly a hardware issue. I wish you luck c:
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok, I reset it to stock, flashed TWRP recovery, installed CM10.2 and the 4.3 GApps package and updated it through CM Updater. For some reason, it worked! Thanks! The 4.4 GApps install was also successful, and now I have CM11 nightly! Thank you very much for your help!
No problem, anything to help a fellow galaxy nexus user! :3