I have a Galaxy Nexus that after updating is stuck in a boot loop just recycling the Google logo. There is no ADB access as a result.
Is there anyway I can save my photos? Thanks!
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Like Eddy said. Via fastboot, boot up CWM, either you have it flashed or not.
From CWM, you can access the phone via adb over USB.
In a "adb shell", you can .tar.gz up the stuff you like (or your entire /sdcard). Afterwards you can "adb pull" that off the phone.
Requires quite a bit off commandline, but it's not hard, just cumbersome. If your data is important enough, it's definitely worth it.
EddyOS said:
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Click to expand...
Click to collapse
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
efrant said:
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
Click to expand...
Click to collapse
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
Correct. If your bootloader is locked, you're out of luck. Unlocking wipes everything.
EddyOS said:
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Click to expand...
Click to collapse
Once you boot up CWM, you have adb access to the files on your device. Not sure what "mount" you are talking about, but I have never had to do anything to get files off/on the /sdcard directory other than boot up CWM or my ROM.
Sent from my Galaxy Nexus using Tapatalk
Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
You are not mistaken. In that case, try booting to the stock recovery and use the adb pull command.
Sent from my Galaxy Nexus using Tapatalk
Boot loop
If you are having difficulty with boot loop, pull the battery. I had the same issue with my N1 didn't wipe dalvik cache after an update. And because of the loop couldn't get the timing for fastboot as the bootloop was not giving an indication of when the keypresses would activate the bootloader.
If you are unrooted and stock then try this:
Put device into the bootloader by holding down Vol Up + Vol Down + Power
use your volume buttons to change options next select (with power button) the fastboot option, after use the ADB instructions from the more knowledgeable members (ADB is somewhat cumbersome.... but it works and has saved my bacon) After wards using the Bootloader you should be able to resore to factory settings and reload your info after.
If you are Rooted with a custom bootloader and rom
same as above to get to bootloader, but then wipe your cache, and dalvik cache. Reflash latest ROM and Gapps. You shouldnt lose anything.
Good luck bud.... your Nexus isn't dead.... only in a Coma.... or a political promise...
J
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
danger-rat said:
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
Click to expand...
Click to collapse
Have you tried and gotten that to work in recovery? Although I haven't tried it, I don't think that works in recovery. It is a feature of ICS, so I'm pretty sure you need to be booted into your ROM for it to work.
Sent from my Galaxy Nexus using Tapatalk
sos lge960
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
bibi019 said:
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
Click to expand...
Click to collapse
My guess is this question is more appropriate for the nexus 4 forum
Sent from my Galaxy Nexus
Nooooo, necrobumping is fine, since he has the same issue, and this is the first hit on Google... even though he's on a different device. /s
Sent from my Nexus
Hey, I'm running to a similar problem with this guy.
I stupidly reformated my system files without having a rom on my internal sd.
The question is that I'm reading that I can use the adb to push files in but I'm just new to the whole adb.
How would I get my computer to use the adb?
Sorry for such a noob question -_-;
Edit: So it seems from looking around and reading other forums and faq's that I need to have the phone for the adb to be installed.
Is there away around that so that I can access the adb?
Edit2: Nevermind. Fixed it with a toolkit. Sorry to spam
Related
Hi guys. I wanted to try a new rom and put a corrupted .zip on it. Anyway long story short. i have a nandroid backup on my computer and I want copy it on the phone but I wiped my rom and cannot get it on. Can I use fastboot to access the sd card? I don't want to flash a stock image as i will lose all my photos etc.
Could you not just connect it to your pc, copy the rom over and run it in CWM?
You can't mount the phone in CWM but if you can boot it you should be able to use MTP to transfer the rom across?
I wiped so no rom to boot into
From the Q&A section: [Q] mount usb on recovery ?
Does flashing the system.img from a factory image really touch the user data?
I didn't think so but I am not 100% sure! If it doesn't adb/fastboot the stock images onto the device.
It does wipe all of the sd card as I have already tried it a while ago. Its bad for your photos. Especially ones of my newborn son.
robt772000 said:
It does wipe all of the sd card as I have already tried it a while ago. Its bad for your photos. Especially ones of my newborn son.
Click to expand...
Click to collapse
That sucks. Thanks for clearing it up.
robt772000 said:
Hi guys. I wanted to try a new rom and put a corrupted .zip on it. Anyway long story short. i have a nandroid backup on my computer and I want copy it on the phone but I wiped my rom and cannot get it on. Can I use fastboot to access the sd card? I don't want to flash a stock image as i will lose all my photos etc.
Click to expand...
Click to collapse
Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media
6) Done.
Note: I do not think the directory structure is preserved doing it this way, so all the files will end up in one directory.
Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel
deyoung said:
Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel
Click to expand...
Click to collapse
Unfortunately you are out of luck in that case. This is why I always recommend that you unlock (and leave unlocked) the bootloader right out of the box - even before booting Android for the first time. Make it a habit on any Nexus device you have, and you will never run into these issues.
As for your problem, if you can't boot into Android, and you did not have CWM flashed as your recovery, there is nothing you can do unfortunately.
Thanks for confirming what I suspected. The lesson about unlocking and installing CWM out of the box is one that I learned today.
deyoung said:
Thanks for confirming what I suspected. The lesson about unlocking and installing CWM out of the box is one that I learned today.
Click to expand...
Click to collapse
Just unlocking is important. Flashing CWM, not so much. Even if you do not have CWM installed, you can always boot if from your PC.
U
deyoung said:
Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel
Click to expand...
Click to collapse
You can use adb to pull the content of the sdcard partition. I've done it before. I think I used 'adb pull /mnt/sdcard'. It may just have been 'adb pull /sdcard'. If it doesn't work, try the adb remount command first.
mwalt2 said:
U
You can use adb to pull the content of the sdcard partition. I've done it before. I think I used 'adb pull /mnt/sdcard'. It may just have been 'adb pull /sdcard'. If it doesn't work, try the adb remount command first.
Click to expand...
Click to collapse
That only works if you can boot into Android (or CWM). If your device cannot boot, it's not going to be of much help...
Sent from my Galaxy Nexus using Tapatalk 2
You can't mount internal storage from CWM anyways
Sent from my Sprint Galaxy Nexus CDMA using XDA
AZ FadeOut said:
You can't mount internal storage from CWM anyways
Sent from my Sprint Galaxy Nexus CDMA using XDA
Click to expand...
Click to collapse
What are you referring to? The point is you can easily access /sdcard while booted in CWM so you can copy all the file you want to your PC, but you need to be booted into CWM (or your ROM). The Galaxy Nexus does not support USB Mass Storage at all in any case.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
That only works if you can boot into Android (or CWM). If your device cannot boot, it's not going to be of much help...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ha, didn't realize this thread was bumped from 6 months ago. I saw flashing of a custom rom in the first post and made too many assumptions. Guess I need to read more when using the xda app.
Thanks to everyone who provided helpful info.
Is the nature of format that's performed by the oem unlock simple enough that it would leave the file contents intact, allowing them to be recovered by an undelete utility of some kind?
Frustrating that the files are likely on the storage and not corrupt, but I am unable to get at them.
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
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2
JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.
RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.
Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars
Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps
If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.
mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.
Then just use the sideload, it works quite well for me.
mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.
No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement
stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone
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/
So I wanted to flash CarbonRom on my phone, but wanted to do a complete wipe of everything (pictures, music, etc) and then push the rom via adb but I ran into a problem.
So I booted into cwm (v6.0.3.1) did wipe data/factory reset, wipe cache partition, in mounts and storage I did format sdcard, format system, format cache, format data and /data/media (/sdcard), then wipe dalvik cache, and fix permissions. After that I opened up the GNex Toolkit v11.1.0 and entered push files to device, then it said “the toolkit will check for insecure boot.img” It asked am I using a custom rom or insecure boot.img I said no, it booted into fastboot and loaded boot.img then loaded back into cwm and then asked me to select file, I entered carbon* set the location, then about 20 seconds later said “An Error Occurred. You are not using an Insecure Boot Image”
I also tried this, unzipped CarbonRom and copy/pasted boot.img into sdk/platform-tools, then held down shift opened command prompt typed in fastboot devices, my device showed up, then typed in fastboot flash boot boot.img then booted into cwm, and tried to push files again through the GNex toolkit and the same thing happened “An Error Occurred. You are not using an Insecure Boot Image” I also tried this with another Rom (Vanilla RootBox) but got the same error.
I finally tried this, went to My Computer, Local Disk (C: Drive) Galaxy Nexus Toolkit, root, copy/pasted boot-insecure-jdq39-toro.img to sdk/platform-tools, typed in fastboot flash boot boot-insecure-jdq39-toro.img, then went into gnex toolkit and tried the push file and got the same error. I realize I could do adb push in sdk/platform-tools but I’m new to command lines and felt more comfortable using the toolkit.
I think there must be an easier way to do this. Before thinking of adb push to load the rom I was hoping that maybe there was someway that I could wipe everything and then mount my phone as a storage device and just drag and drop the rom and gapps onto my device and then install the zip from sdcard, but then I got this whole boot.img thing (I don’t know what it is) so my plan of dragging and dropping probably wouldn’t have worked. or maybe it would have? is it possible to do that CWM or TWRP? If so what would happen to the boot.img step?
I’m all out of ideas as to what to do next. Any help/advice is greatly appreciated! Thank you
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Zepius said:
why are you using a toolkit? it did nothing for you
1) you will never be able to mount your phone, so dont even bother.
2) adb push a rom to your phone or adb sideload it.
3) STOP USING A TOOLKIT
Click to expand...
Click to collapse
Thank you so much! I stopped using the toolkit and just pushed it via adb with command prompt in sdk/platform-tools and it worked!
However next time if I want to flash a rom and do a full wipe of my phone will I have to flash the boot.img via fastboot (taken from the rom) & then push the rom via adb? (sdk/platform-tools) or just push via adb and do nothing to the boot.img ? I'm assuming do nothing wtth boot.img and that it was just the toolkit that was giving me that strange error, is this correct?
Thanks, again