Database Users

[Q] CM7 Nightlies Not Flashing

There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.

hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.

Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.

Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA

ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA

Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239

hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.

janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery

having issues after bootloader unloack, and root

this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...

Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App

i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol

can you boot into fastboot or Android Recovery?

yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?

PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?

i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick

i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?

Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?

it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...

PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...

rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...

PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.

you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!

Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.

just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!

I installed cyanogen 7 and all I get is boot logo

I installed cyanogen 7 and all I get is boot logo this keeps resting "the cyanogen" logo and I do have my atrix unlocked and rooted.

Lack of the following specifics:
How did you flash CM7? (ADB push or through CWM or twrp)
What version of CM7 did you try to flash?
AT&T atrix or international atrix?
Did you flash a kernel or any additional zips prior to booting?
Did you perform a full wipe before installing?
And many other questions may arise, should we get more specifics from you.

Wipe data. Cache. Dalvick and re-install
Sent from my MB860 using xda premium

SirFork said:
Lack of the following specifics:
How did you flash CM7? (ADB push or through CWM or twrp)
What version of CM7 did you try to flash?
AT&T atrix or international atrix?
Did you flash a kernel or any additional zips prior to booting?
Did you perform a full wipe before installing?
And many other questions may arise, should we get more specifics from you.
Click to expand...
Click to collapse
How did you flash CM7? (ADB push or through CWM or twerp) I used rom manager from market store
What version of CM7 did you try to flash? the regular builds non nightly
AT&T atrix or international atrix? att
Did you flash a kernel or any additional zips prior to booting? no

You need to have installed a recovery program that you can get to by holding the VOL DOWN button while booting. ROM manager is useless without a recovery program behind it.

Oh so how can I flash an rom without a rom manger just using the computer?

I would spoon-feed you this information, however it would be like handing a monkey a rocket-propelled grenade. You need to take time to read before you create a very expensive paperweight.
http://forum.xda-developers.com/showthread.php?t=1154600
Please take the time to read this, all the way through. If you haphazardly install things without full knowledge of what it does, people will have very little to no sympathy for you when you brick your phone.

Yes I did do the following
While in Recovery install CM7 from internal storage
After installation select Data Wipe/Factory Reset
Then Wipe Cache Partition
Reboot system now
Watch awesome boot animation.
I do not see nothing else after the boot animation?

sillyshyme said:
Yes I did do the following
While in Recovery install CM7 from internal storage
After installation select Data Wipe/Factory Reset
Then Wipe Cache Partition
Reboot system now
Watch awesome boot animation.
I do not see nothing else after the boot animation?
Click to expand...
Click to collapse
If you installed CM7, and then did a factory reset, you undid your first step.
\\FROM ANDROID RECOVERY MODE// (hold volume down button then scroll through the options until you get to Android Recovery, then press VOL UP to confirm. If you don't see Android Recovery in the list, then you're missing something crucial)
1. Wipe/Factory reset
2. Install CM7
3. Wipe cache (optional)
4. Reboot

reead the noob guide for xda google search will reveal this awsome guide and video hehe
Sent from my MB860 using Tapatalk

You would think that it would undo, but it doesn't. The factory reset doesn't "unflash" the ROM. All it does, is flush cache and a few other directories.
Sent from my MB860 using xda premium

How long did you let the phone sit after rebooting? It can take 15 minutes on initial boot after flashing a ROM. All that time all you will see is the boot animation.
Sent from my MB860 using xda premium

Wipe dalvik and cache partition and factory reset it in the cwm. Make sure your boot loader is unlocked. Made that mistake my first time.?
Sent from my Nexus S using xda premium

heinst said:
Wipe dalvik and cache partition and factory reset it in the cwm. Make sure your boot loader is unlocked. Made that mistake my first time.?
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Definitely. I made that mistake myself the first time I went to flash CM7. In fact, what took me the longest the first time around was that I unlocked out of order, so I could not boot into CWM for the longest time.
Sent from my MB860 using xda premium

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

Help, I think I bricked it D:

Damn I'm dumb, I thought I'd have a go at attempting to make it so the bottom buttons would be hidden as I use gestures anyway
I modified the .prop file as a tutorial recommended but now after the Google logo (unlocked bl) I just get a black screen
I can access recovery which gives me the options START, RESTART BOOTLOADER, RECOVERY MODE and POWER OFF.
I am going to guess I need to bring it back to stock somehow - how would I go about doing this?
Any help is appreciated, Thanks
Kevin
TRIED:
Relocking and unlocking the bootloader - was hoping it would format the phone but it appears it keeps the build.prop.
I can boot into clockworkmod recovery but I'm scared to flash it for the moment before I get some advice from you guys
[EDIT] I see that Fastboot detects it - so I guess I can flash stuff.

In an attempt to fix this I flashed the stock rom from Google that ATGAdmin pointed out. Here's what I did below
0. Download above recovery image, extract into a directory with fastboot
1. Hold down power for 10 seconds to power off
2. Hold down voldown and then power for a few seconds until recovery appears
3. Run flash-all.bat or flash-all.sh if on Linux.
4. Phone should reboot.
Now device is stuck on nexus X logo, attempting reflash... Same problem
Halp D:

why dont you do restore the build.prop to the original one and also do a wipe cache and wipe dalvik from CWM

My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool

kn100 said:
My phone wasn't booting because of the broken build.prop and as such how was I supposed to restore it?
Now that I've flashed the stock rom I am now stuck at the nexus X logo, so I'm not sure what to do at this point, thanks for the help munchy_cool
Click to expand...
Click to collapse
You could sell me your phone:fingers-crossed: lol.... Hope you fix it

if you still have recovery clear dalvik cache and cache.
if you do not have recovery search for fastboot commands to do so as I guess you can still go into fastboot mode.

Recovery still works fine and I can boot into clockwork mod etc, it all appears to be working fine, except I just noticed in clockwork mod it's not able to format SDCard whatsoever - if this helps at all - I haven't flashed clockworkmod just to keep my options open, I just boot to it.
Any suggestions, I've tried flashing the google stock rom twice now and it doesn't appear to work.

boot in CWM and do a wipe dalvik and wipe data+cache bro ....

Try using mskip toolkit to flash stock image just done the exact same thing and works a treat. Didn't have any faults myself was just tinkering with it. Hope it helps
Sent from my Nexus 4 using xda premium

Booted into CWM
Wipe data/factory reset:
Wiping data, Formatting /data, Error mounting Data!
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure!
Skipping format
Data wipe complete.
wipe cache partition
Formatting /cache
Cache wipe complete
Wipe Dalvik cache
**page just refreshes, assume it just wiped**
After reboot stock recovery is used and again I am stuck at the X.

go into mounts, mount the data partition manually and then do a factory reset.

Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)

kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Glad you fixed it:good:

glad you can now enjoy it

kn100 said:
Used M-skips toolkit to flash the stock files which somehow fixed it. I am SO donating to that guy next week.
Holy crap pants are soiled.
Thanks everyone, disaster averted, time to flash CWM and to take a backup (that does work right)
Click to expand...
Click to collapse
Awesome bit of kit. Glad you got it sorted pal
Sent from my Nexus 4 using xda premium

Congratulations, you have been the first to almost* break their N4. You have now began the famous tradition for this model , many shall follow, but we shall always know of your name first.
, glad it's fixed

Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?

For what it's worth, all that needed doing was flashing system via fastboot.

kn100 said:
Heheh I'm quite proud of that! Reminds me of the old Motorola modding days with P2K and P2K05, Any of you guys part of that back in the day?
Click to expand...
Click to collapse
Hahaaha I remember those days (hint-my avatar)

As a side note, you could have just followed the Galaxy Nexus guides for restoring to stock, but just replacing the system image files with those applicable to the Nexus 4.