Hello everybody!
The latest install of CyanogenMod Nightly 5. july constantly crashes System UI, whereas I press the OK button, and I got about 1 second before it pops up again. I can see that many others that installed the same nightly is having the same problem, and that there will be a fix in 6. july update.
My problem is that I can't access the Rom Manager to update CyanogenMod (since it crashes when I try to launch), and I seem to not be able to enter recovery mode. Therefore, I have no way to install the 6. july update when it comes out. Sadly, I'm not as skilled as the regular development user, and would be greatful for any help, tip or advice I might get.
I would've posted this in the CyanogenMod Nightly thread, but I haven't posted 10 posts yet.
Thanks
ipi
Maybe,just maybe,download the latest build on pc,then copy it on phone?
Or making a clean install of actual build you are using?
Sent from LG E975 pwd by CM 10.1
Yeah, that could absolutely work, but how can I enter CWM recovery without going through the ROM manager app?? :silly:
You can always use adb to enter recovery mode....
Sent from LG E975 pwd by CM 10.1
kimitza said:
You can always use adb to enter recovery mode....
Sent from LG E975 pwd by CM 10.1
Click to expand...
Click to collapse
I've never really understood adb, how it works or what it actually is. I've tried to look for good tutorials on how to install and how to use adb with my Optimus G, but so far I've only accomplished installing something I don't even think works, and I've never been able to communicate with my phone through any of the programs.
Do you have a link to a decent tutorial?
I would be very greatful!
I'm also unavaiable to find my phone listed as devices on My Computer, where can I find the USB settings on my phone?
EDIT: Ok, I am now able to boot my phone into CWM, only thing I'm missing now is transfering the updated ROM into my SD card, but I am still not able to find my phone on devices. What am I missing?
you can't mount usb on cwm, as you don't have external sdcard.
with adb the command would be
adb push /path/to/local/file /mnt/sdcard/path/to/file
for example,you have the file in D: ,the command would be adb push /D:/cm10.1 /mnt/sdcard/
this means you would copy the file from root of D: partition to root of the internat memory of phone.i just gave you an example.
it's easier to rename the file you are transfering to a short name and put it on root of partition.this way there are less chances to get syntax errors.
kimitza said:
you can't mount usb on cwm, as you don't have external sdcard.
with adb the command would be
adb push /path/to/local/file /mnt/sdcard/path/to/file
for example,you have the file in D: ,the command would be adb push /D:/cm10.1 /mnt/sdcard/
this means you would copy the file from root of D: partition to root of the internat memory of phone.i just gave you an example.
it's easier to rename the file you are transfering to a short name and put it on root of partition.this way there are less chances to get syntax errors.
Click to expand...
Click to collapse
Sounds pretty good, but how do I install adb?
GIYF.
Sent from LG E975 pwd by CM 10.1
nice to see i am not the only one, getting this, from rom cm-10.1-20130704-NIGHTLY-e975.zip to cm-10.1-20130708-NIGHTLY-e975.zip i get this i haven't tried cm-10.1-20130709-NIGHTLY-e975.zip that got out today.
Related
I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.
do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?
I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.
Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.
Yeah, for some reason it was downloading 404 page...
I reuploaded it.
I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys
First, I'd like to thank Chlinkchlink, Heritz, and Superoneclick application for your help and original Root.zip File! Wouldn't work without this!
I Finally found the perfect method to root this Virgin Mobile Device with S-On (Or OFF)! I Spent 3 days on my customers phone at my computer shop figuring a good method without read/write or freeze errors. I Simply EXTRACTED the SUPERUSER and ROOT files from SUPERONECLICK application and PASTED those files into the ROOT.ZIP File provided. Result? The ULTIMATE ROOT.ZIP MODIFICATION! Below are the methods....
Forget to mention... "I AM NOT RESPONSIBLE IF YOU BRICK/BREAK/THROUGH YOUR PHONE OUT THE WINDOW/ Etc!" That can only happen if you fail to backup your device or fail to read my steps and HTC Dev. Thanks and HAPPY ROOTING!
Follow The HTC Dev method to unlock your bootloader. Sorry. Due to rules I am too new to submit links.
Then install clockworkmod recovery like you would through adb on your computer. Download from attachment. make sure you Extract it!
Place the clockworkrecovery image inside your Android Adb folder. Place your phone in bootloader usb mode and plug it into the computer. Open command prompt and browse to the folder where you placed the recovery
example how:
cd c:/
cd Android
Now Flash this bad recovery!
example on cmd prompt:
fastboot flash recovery recovery-clockwork-5.0.2.8-marvelc.img
Now you have clockworkmod recovery!
Now hit Recovery on your cell...
Get My Modified Root.Zip File on link attached.
Now mount USB Storage and make sure your phone is still plugged in to computer.
Copy my modified Root.zip file you downloaded into the root of your MicroSD Card.
Unmount USB and flash the Root.zip file.
Reboot phone and you are now rooted! Donate / Like Me/ And good comments if I helped you!!!
Thanks for your help with my phone. I'm glad you were able to figure it out after i gave up trying. In a few wks i'll get the VM Evo 3d 4g and swing by to have you do that phone as well. I'll let you know if i run into any issues or updates. Thanks once again!
Can anyone else verify this works?
Finally found something for wf s CDMA. Only 1 other person out there that has tried this? Anyone else?
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Here you go
F9zSlavik said:
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Click to expand...
Click to collapse
Yes.. I am sure you need to go back to stock rooted rom. Then activate (or reactivate) with your carrier, then put the Hensemod back.
(Most HTC phones with SENSE won't activate with the carrier with any cyanogen based rom). It must have SENSE.
Nice tut, thanks
Sent from my new LG Optimus Elite
F9zSlavik said:
This would of helped me a while ago.
I had an issue where CWM 5.0.2.8 would freeze and restart itself. I had to use 4.X.X.X (don't remember the exact numbers) in order to be able to flash roms.
And maybe you can help me with this. I installed HenseMod with the VirginMobile patch, but I have no service. My carrier doesn't seem to know why either.
Does anyone know what the problem is?
Click to expand...
Click to collapse
what provider do you have? and if its vm try another ROM that was made by someone with a marvelc (the guy who made your ROM doesn't have the phone)
Sent from my HTC_A510c using Tapatalk
I never had a problem with any of the cwm on the marvelc, maybe it was a bad install? I just use the old version then use ROM manager to flash the new version
Sent from my new LG Optimus Elite
sweet, thanks
Very helpful and a good consolidated version. I had more trouble unlocking the bootloader than following your HowTo!!!
Thanx Again!
Unroot??
rgsgroup2005 said:
First, I'd like to thank Chlinkchlink, Heritz, and Superoneclick application for your help and original Root.zip File! Wouldn't work without this!
I Finally found the perfect method to root this Virgin Mobile Device with S-On (Or OFF)! I Spent 3 days on my customers phone at my computer shop figuring a good method without read/write or freeze errors. I Simply EXTRACTED the SUPERUSER and ROOT files from SUPERONECLICK application and PASTED those files into the ROOT.ZIP File provided. Result? The ULTIMATE ROOT.ZIP MODIFICATION! Below are the methods....
Forget to mention... "I AM NOT RESPONSIBLE IF YOU BRICK/BREAK/THROUGH YOUR PHONE OUT THE WINDOW/ Etc!" That can only happen if you fail to backup your device or fail to read my steps and HTC Dev. Thanks and HAPPY ROOTING!
Follow The HTC Dev method to unlock your bootloader. Sorry. Due to rules I am too new to submit links.
Then install clockworkmod recovery like you would through adb on your computer. Download from attachment. make sure you Extract it!
Place the clockworkrecovery image inside your Android Adb folder. Place your phone in bootloader usb mode and plug it into the computer. Open command prompt and browse to the folder where you placed the recovery
example how:
cd c:/
cd Android
Now Flash this bad recovery!
example on cmd prompt:
fastboot flash recovery recovery-clockwork-5.0.2.8-marvelc.img
Now you have clockworkmod recovery!
Now hit Recovery on your cell...
Get My Modified Root.Zip File on link attached.
Now mount USB Storage and make sure your phone is still plugged in to computer.
Copy my modified Root.zip file you downloaded into the root of your MicroSD Card.
Unmount USB and flash the Root.zip file.
Reboot phone and you are now rooted! Donate / Like Me/ And good comments if I helped you!!!
Click to expand...
Click to collapse
Hey do you know how to unroot the vmwfs? i used this to root
r=watch?v=rIKsoZf2BCA&list=PL44107726C058E557&index=1&feature=plpp_video[/url]
but i wanna unroot any ideas??
Finally a method easy and straightforward! well done!
I'm stuck at the end, this is a bit vague:
rgsgroup2005 said:
Unmount USB and flash the Root.zip file.
Click to expand...
Click to collapse
searching the forum I found this http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android is that what you mean?
Can't find any option to flash the on the boot menu... .zip file
Has anyone tried this with a recently purchased VM Wildfire S? Say July 2012 or after?
do we need to s-off
do we need to s-off the phone befor going ahead with the steps mentioned.I mean can we root the phone even without s-off
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic
you'll probably have to boot into download mode and use odin to get back to stock and start over.
^^^^^^^^^ That's what you're going to have to do.
There is a way to do ADB sideload through TWRP but you have to edit some files and the Odin method is a lot easier in my opinion. If you want to use ADB Sideload follow my instructions on this thread: http://forum.xda-developers.com/showpost.php?p=39849970&postcount=10. That shows you how to get ADB to recognize your phone in Recovery mode and then the adb sideload command will work.
Odin keep failing. It look like everything is going good then it will get to "get PIT for mapping" stay there for about 7 minutes then fail. I cant believe this:crying:
I would suggest you try my method with ADB sideload, do you know how to use ADB?
Im not familiar with ADB. Any help would be much appreciated.
I got to finding those two lines,
USB\VID_18D1&PID_D001&MI_01
USB\VID_18D1&PID_D001&REV_0228&MI_01
then I got lost.
It says I have to paste those two lines under
[Google.NTx86]
xxxxxx
;Google Nexus (generic)
xxxx
but I am a little lost there.
Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit
sevenpioverthree said:
Here is the guide for setting up ADB: http://forum.xda-developers.com/showthread.php?p=9936674
If you already have done that, then you should navigate to the directory I listed which is where the android_winusb.inf file is, this is the file you edit
Click to expand...
Click to collapse
Thanks for the help. I finally got odin to work after trying a dozen times. This definitely scared me a bit for a minute lol. The only downside now is that I lost about 2 weeks worth of data from my phone since that was my last backup point. Now I know how important back up can be.
Now back to this rooting..if I can remember:silly:
CyberGmonster said:
Let me make this short for you guys.
I was running carbon rom then decided to try CM 10.1 only because I am a romholic. CM was giving me small quirks so I tried to restore my carbon rom but for some odd reason it wouldnt go pass the samsung logo after it restored successfully. After trying to restore a few times over and over it just decided it was now going to fail. So I tried to go back to CM but now that also failed. So now I was trying to mount usb storage through TWRP but for some odd reason there's no way to do this. After trying to figure out wth was going on I finally made the biggest mistake of completely erasing my internal SD.
So now I am basically in TWRP 2.4.4.0 with no way to access usb storage and not knowing what I should do next.
Please help your fellow romholic
Click to expand...
Click to collapse
delete this / I replied after the fact....sorry.
When I installed the ROM, I realized I have downloaded the wrong file (Taro instead of Maguro) and I'm getting an installation abort.
I am trying to place the right ROM to my internal storage, however, it does not show when I'm inside CWM recovery (I only get to see my old files including the wrong ROM that was in there before)
I tried the following method below but with no success.
from cmd, I typed c:\android>adb push c:\(ROM) \sdcard - and I know the file got transfer to my phone because it shows 2123 kb/s <150717638 byes in 69.317s)
Sorry if this topic been posted before and my poor English and terminology. If anyone can guild me through this, it will be deeply appreciated.
ADB sideload saved many devices of mine.
Sent from my Liquid Powered Nexus!
try to use the latest galaxy nexus toolkit to inject the correct rom, be sure you've downloaded the correct rom, try paranoid android or cyanogen mod first to connect your booted device to pc