Develop Bugs

BRICKED Galaxy Nexus - please help me restore/advice

Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?

grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?

grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium

All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk

Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....

borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?

grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html

zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted

~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'

anybody have any other suggestions to this? or a follow up?

It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium

Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.

grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)

ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?

grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app

not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img

Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"

grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm

ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium

Think I hard bricked my GNEX

I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?

chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
I'm not the guy who can tell you what you need to do, but I will tell you that I have read other posts by people in your position. There are ways to push the necessary files to your phone, either toolkits or command prompt type setups, sorry but that's all I have. Google is your friend though. Galaxy Nexus toolkit, start with that, it's around here somewhere
Sent from my Galaxy Nexus using Tapatalk 2

You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium

El Daddy said:
You cannot mount the sd on the gnex through recovery. There is no SD to mount.
To move a file to your phone you must push it with adb
adb push nameofzip /storage/sdcard0
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.

chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
Yes, you do that on recovery mode.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
Click to expand...
Click to collapse
do it in recovery.

chaotic646 said:
Since there's no rom on my phone, would I need to be in recovery or bootloader to do that?
ADB wont even open up. This sucks.
Click to expand...
Click to collapse
Have you installed adb drivers? You probably should have done this already, unless you used a toolkit to unlock and root...
To install drivers, download the naked driver located here: http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Then, follow this guide to install them correctly.http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
If they are set up correctly you will be able to push the rom to your internal storage booted in recovery with adb. A list of adb commands is here: http://forum.xda-developers.com/showthread.php?t=1812959
If you aren't comfortable with that I recommend that you flash the stock images to your phone with fastboot following this guide: http://forum.xda-developers.com/showthread.php?t=1626895
This should be all the info you need. I'll be around to answer questions you may have. Just post them here.
Good Luck.

It fails because it says Im using an insecure bootloader

chaotic646 said:
It fails because it says Im using an insecure bootloader
Click to expand...
Click to collapse
What fails and when?

El Daddy said:
What fails and when?
Click to expand...
Click to collapse
The Galaxy Nexus Toolkit, which uses adb to push files to the phone. It gets about halfway through the process then fails because it says Im using an insecure bootloader

None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.

El Daddy said:
None of the info I gave you has anything to do with the toolkit. If you want to use it I cannot help you. Sorry. If you want to read my thoughts about toolkits check my sig.
However, If you follow what I posted in post #7 I will help you though the process as long as it takes.
Click to expand...
Click to collapse
I cant follow the guide you linked to install the drivers, because it instructs me to enable usb debugging...I have no rom installed on my phone so I cant enable it.

OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.

chaotic646 said:
I was trying to install a new rom but I wanted to reformat my sdcard first. I planned on reformatting, mounting the sdcard so my pc would pick it up, moving the rom I chose to the freshly formatted sdcard, then flashing the rom. I started by doing a full wipe of everything, then wiped the internal sdcard. The problem is when I try to mount the sdcard to transfer files nothing happens. I tried doing a restore using odin but it gets stuck at setup connection. Is there anything else I can do or is it completely bricked?
Click to expand...
Click to collapse
Use Odin bro...its in the forum
Sent from my Galaxy Nexus using xda premium

Dafuqq guys. The easiest way is flashing the stock fastboot images from google. Just flash them.in fastboot.
Sent from my Galaxy Nexus using Tapatalk 2

I'd stick with el daddy. .he seems to be directing you in a way that gets you away from that stupid kit and you're learning the proper way.. .with adb. Next time something happens you'll be far better off.

I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.

chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Because you're not supposed to open up adb by double clicking on it.
You're supposed to navigate to the location where it is using CMD and do commands from there.

chaotic646 said:
I got it situated and fixed with a different toolkit but I appreciate all the help. I couldnt get it going with adb, everytime I would try to open adb in command prompt it would open for a split second then crash. The toolkit I used uses the adb on my pc though and it worked just fine.
Click to expand...
Click to collapse
Go to the directory where you have adb.exe
Shift+Right Click the blank space (Don't click any files)
Click Open Command Prompt Here
Now you can use all the adb commands there.
Good luck

El Daddy said:
OK. I'm not sure if you can install the driver without debugging activated. But, I know you can install the fastboot driver when booted in the bootloader because I have done it.
1) Boot into the bootloader. (power + vol. up and down)
2) Connect to your pc
3) Open your device manager and you should see "android 1.0"
4) Right click on that and choose update driver.
5) Choose install from my computer and then install the naked driver.
6) Click done and then it should show Galaxy Nexus Bootloader Interface.
You will now be ready to flash the stock google image. Follow this guide.
You'll be up and running again. You can then flash a custom recovery and ROM if you so choose. OR just roll with stock.
Click to expand...
Click to collapse
You are a very patient person. I hope you help me when I get in a jam. You make these forums what they are - awesome. Thanks.
Sent from my Galaxy Nexus using Tapatalk 2

HELP pushing files

hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.

Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250

I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help

nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!

Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!

Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool

italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.

i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.

Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2

Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium

I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/

closed

closed

Read this whole thread. THE WHOLE THING. Preferably thoroughly.

edited

AJThePwnapple said:
Even though I have a factory cable, do you want me to go into fastboot using your method?
I tried flashing the images but my computer doesn't recognize the device (can't install otter2-prod-04) and stays at <waiting for device>. Will it be different using your method?
Sorry if I come off a bit noobish, I'm brand new to this.
Click to expand...
Click to collapse
you need the drivers (should have been mentioned on that thread.)
If you have a fbcable, use it. on windows, device manager, uninstall the current driver if there is any, and use KFU to install the fastboot driver. (only use kfu for the driver, don't do anything else.)

Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.

AJThePwnapple said:
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
Click to expand...
Click to collapse
No problem, i'm happy to help

I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC

Same here...
obsolete1 said:
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Click to expand...
Click to collapse
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...

yudanjah said:
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
Click to expand...
Click to collapse
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.

melvsmis ster said:
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
Click to expand...
Click to collapse
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck

gnandez said:
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
Click to expand...
Click to collapse
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr then plug device to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?

melvsmeister said:
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr tn plug devicle to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
Click to expand...
Click to collapse
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help

gnandez said:
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
Click to expand...
Click to collapse
I guess I'm missing some steps here or maybe I need to do something to make it work since my adb is not detected in TWRP but I can have it if I let it boot to blue kindle logo. I'm still having a hard time in pushing ROM due to "No space left on device" error and even though I can push gapps I can't find it in TWRP. I'll just wait for someone who might had the same issue and have other solution to resolve this problem. Thanks for your help!:good:

[Q] please help

i'm having bootloop after installing 17/02/2013 CM10.1 rom on my gsm gnex. the issues are:
1. i don't have any previous working cm10 rom saved in phone's sdcard.
2. can't get adb working, maybe because i never enabled usb debugging mode before.
fyi, i have never flashed any other roms, just CM roms. please assist..

Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.

eqjunkie829 said:
Go into recovery and transfer a new Rom download to your phone if you have a computer. There is an option to transfer files inside recovery.
Click to expand...
Click to collapse
that requires adb (adb_sideload- correct me if i'm wrong).. my adb is not working.. can't boot to android.. can't find a way to enable usb debugging mode.. so no adb..

Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.

bodh said:
Do you have a custom recovery or experience with fastboot? Boot a recovery image via "fastboot boot recoveryname*.img", and adb is enabled.
Click to expand...
Click to collapse
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""

[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
Attached is clockworkmod touch recovery for gsm galaxy nexus, maguro. Phone in bootloader mode, open a terminal, cd to directory of fastboot and where you move this file to, type fastboot devices to verify device is connected, then "fastboot boot CWMT6023.img", without the quotes of course. This will temporarily allow you to use clockworkmod recovery, and thus adb, without having it on your device once you have selected "reboot now".
And if that didn't help, try consulting http://forum.xda-developers.com/showthread.php?t=1626895, since i'm thinking you haven't used fastboot in a terminal, but only know it's 'mode', and may need help with drivers.
You also might want to consider just straight out flashing cwm recovery, since YOU NEED TO MAKE BACKUPS!

[email protected] said:
i don't have custom recovery, but i know how to get into fastboot. please explain how to ""Boot a recovery image via "fastboot boot recoveryname*.img"""
Click to expand...
Click to collapse
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
If u don't have a custom recovery how did u flash cm10?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sorry, i got cwm. but what does fastboot have to do with cwm? i can't use cwm to restore because files can't be sent from computer to it.
as of fastboot in terminal, it seems the phone not connected to computer. is there anything has to do with my drivers? "fastboot device" command shows <waiting for device>

I gave you that link to set up drivers more than anything else. If you already have cwm, boot to it and now you can adb push a rom.zip to your sdcard and install it, wipe caches and perhaps a factory reset [if you're changing to a different rom], OR, you can first try and wipe cache and advanced, dalvik cache to see if that fixes the bootloop.

1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM

EddyOS said:
1. Why didn't you make a backup?
2. Why didn't you make sure you know how to get out of this situation before flashing new ROMs?
3. Search as there are LOTS of tutorials on how to use adb to side load a new ROM via CWM
Click to expand...
Click to collapse
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.

[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
If you think that then you have no idea on how adb works...
That is ONLY applicable when Android is running. As it's not, it's irrelevant...

[email protected] said:
I know how to use the adb to sideload a new ROM, thank you.
But please read my earlier post, in order to use adb, usb debugging mode must be enabled in android settings.
Mine is disabled, and i can't enable it now.
Click to expand...
Click to collapse
ADB should work in your custom recovery regardless of USB debugging being enabled or disabled.
I can't tell you how many times I have rebooted into recovery, wiped, then realized I forgot to put a file on my sdcard that I wanted to flash. I then use adb to push the file(s) from within the recovery.
Edit: I really need to refresh prior to responding.

so i can't get adb working because of the driver? thats why i got "waiting for device" when pushing file to phone?
edit: i've installed all the required drivers, it's not my 1st time doing it. MAYBE, this computer never connected to my gnex before, as i've formatted it a few days ago. So the gnex driver was not properly installed.. Is it possible?

If that version of cm 10 is for 4.2.2., then i think you may have an issue accessing adb without first getting the rsa verification, even in recovery (but im not sure). Looks like your only other option would be to fastboot flash stock images. And of course it sounds like driver issues, especially if your fastboot is not even working. Again, that link I posted will get you back up and running. http://forum.xda-developers.com/showthread.php?t=1626895