i was trying to install a rom,and in the CWM i formated the sd along with the others by mistake,now i can't reach the rom i transfered and the phones won't boot for sure
i tried to flash the google stock with gnex toolkit (using step 9) and i downloaded the file but it fails and what is shown to me is what you have in the attached image,it gets stuck at the "sending radio"
what should i do,i really need urgent help here
please just know that i'm a total noob so please tell me what to do step by step so i could understand
What Nexus do u have gsm or verizon? If it's Verizon you picked the wrong version and it's flashing a gsm radio. If it's gsm it could be a bad download or you picked the wrong version not too sure about that I have a Verizon nexus
Sent from my Galaxy Nexus using xda premium
it's a GSM,and i chose the right version stated in the toolkit thread and the one i installed the drivers and unlocked the bootloader and rooted the phones with it
is there a way to transfer a file in the CWM mode? can i transfer the rom in this mode?
You should do these commands in fastboot instead of using a toolkit.
Here is a step by step guide how to get back to stock. http://forum.xda-developers.com/showthread.php?t=1626895
Edit: to answer you question about pushing a file in recovery, you can. You must use adb. The command is adb push nameoffile.zip /data/media
Sent from my Nexus 7 using xda premium
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Put the zip in the same folder and hold shift and right click select open command prompt here. Then adb push the zip onto your phone.
You got clockwork recovery? If so, you need cwm flashable version of radio, boot loader and ROM
Sent from my Galaxy Nexus using xda app-developers app
rok3r said:
i installed the sdk and found the adb.exe in the platform tools folder now what should i do?!! should i transfer the rom .zip to the same directory of the adb.exe?
Click to expand...
Click to collapse
Yes move it to the same directory. Open the command window in that directory. (Shift+right click > open command window here)
Then type: adb push rom.zip /data/media
Sent from my Galaxy Nexus using xda premium
OMG!!! Device not found,same message i got in the toolkit when i tried to push the files (((((((
drivers?
Yes most likely a driver issue. Type adb devices in command. If if returns a device number everything is set up correctly. If not reinstall the drivers.
Sent from my Galaxy Nexus using xda premium
If you are trying to push in bootloader adb won't work. Get in to recovery cwm works fine than do the adB push
THAAAAAAAANNNNKKKKSSSSSS!!!
seriously thanks for the help,i am totally new to this and felt like i killed my phones with my inexperienced self
i was a driver problem and i used the toolkit to uninstall and install again the driver and then used the toolkit to push the files but it said something like adb is already in root access or whatever so i headed to the adb.exe and it did it!!!!
thanks man for the great help again!!!!!:good:
this will make me learn to do a nandroid hahahaha
@atifsh i was in the CWM,it was a driver problem after all,thanks for your reply
Related
This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error
Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.
Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)
Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.
Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.
Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?
w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!
Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD
looks pretty simple ... hopefully it will be the same process for us in the States
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus
Oh ok! I'll look at that now. Thanks fellas
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse
Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App
Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks
So my desire is rooted then I s off'd with revolutionary and loaded a new recovery, now I want to change hboots so I put an pb99img.zip file on the scard and booted into bootloader but the zip file is not found.... Am I missing something?
Sent from my HTC Desire using Tapatalk
It will be best if you start using fastboot, it's fastest easiest and safest way to do so.
Look for ADB/Fastboot guide (they are all over the place..), you need to setup it once and then you just flash hboot by simply executing few commands for example:
fastboot flash hboot cm7r2.img
fastboot erase cache
fastboot reboot-bootloader
And you're done, so just learn how to install and use adb.
If you want to use the pb99img.zip method, make sure that the file really is called PB99IMG.zip. Windows is default set that it doesn't display file type endings, so it would show "PB99IMG.zip", but the file really is called "PB99IMG.zip.zip", which won't be recognized.
Anyway, I prefer fastboot. If you can't use it (e.g. no own pc with adb around), the zip method also works. But fastboot is faster (as the name says!) and you don't have to mess with files on your sd.
Ok so readup a bit about adb and fast boot then installed jdk then installed the sdk then installed platform tools which included adb and fast boot and added path to adb folder under path environment variable. Connected phone and booted into fast boot. All good so far.
Running adb or fastboot devices command lists my phones serial number so all looks like its working so then I put the ing files I want to flash in the same folder as the adb.exe file then run the command - fastboot flash hboot bravo_alphaspl-oxygenr2.img but I get an error failed to load etc etc
Did I miss something? Am I putting the img files in the right place? Should I use the alpharev zip files instead of the img files?
Sent from my HTC Desire using Tapatalk
What errors exactly are you getting, it will be best if you paste whole log including commands that you were executing.
Sent from my HTC Desire using xda premium
see attached for error message
Just put the PM199IMG.ZIP File to the root of microSD card and goto boot loader and it will detect the update file and ask you if you want to update or not there just press yess and then goto recovery and restore your nandroid backup. Or flash New Rom.
Sent from my HTC Desire using XDA
Don't you mean PB99IMG.zip file not PM199IMG.zip? If so have tried that as per first post. If not then I'll try that too.
Sent from my HTC Desire using XDA
Maybe you have misspelled the img name, rename it to something shorter like oxygen.img also make sure you're in fastboot mode while flashing it! (power off, then hold vol- & power on, select fastboot)
And the last thing the img file has to be in same directory as the fastboot.exe
Sent from my HTC Desire using xda premium
Cuz, sorry to confuse you, but seriously, forget all about adb, terminal emulator, PB99IMG.zip etc. Just install Android Flasher, plug your phone to PC (leave on main screen, it'll be fine) and push .img file to phone.
It seriously is a piece of piss, mate. You will have no dramas.
There's a thread in dev section to give you the how-to.
E: If coming from another HBoot, make sure you push "downgrader" (from alpharev) first.
777ace said:
E: If coming from another HBoot, make sure you push "downgrader" (from alpharev) first.
Click to expand...
Click to collapse
No need.
10chars
kiwiflasher said:
Don't you mean PB99IMG.zip file not PM199IMG.zip? If so have tried that as per first post. If not then I'll try that too.
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
Typing error Sorry
kiwiflasher said:
Ok so readup a bit about adb and fast boot then installed jdk then installed the sdk then installed platform tools which included adb and fast boot and added path to adb folder under path environment variable. Connected phone and booted into fast boot. All good so far.
Running adb or fastboot devices command lists my phones serial number so all looks like its working so then I put the ing files I want to flash in the same folder as the adb.exe file then run the command - fastboot flash hboot bravo_alphaspl-oxygenr2.img but I get an error failed to load etc etc
Did I miss something? Am I putting the img files in the right place? Should I use the alpharev zip files instead of the img files?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
You are on right track, you just need to put the img file to the location of fastboot.exe .
Dunno why you guys are talking about adb...that's a completely different story and you can't flash hboots with adb.
Apart from that i am quite surprised about how far you got,given the partly confusing answers.
You either use fastboot or android flasher (which is basically a fastboot GUI I think) or the PBblabla.zip hboot-zip method. Don't mix them up - you are using fastboot (which is the safest and in my eyes most straight forward way) , so stick to it You're almost there!
Sent from my HTC Desire using xda premium
Ok so I put the image file in the same folder as the fastboot.exe file so sounds like I did nothing wrong and it should have worked? Must be something wrong with the jdk or sdk install so will try using the Android Flasher method.
Sent from my HTC Desire using XDA
Yay for Android Flasher that did the trick, thanks to all...
Sent from my HTC Desire using XDA
kiwiflasher said:
Yay for Android Flasher that did the trick, thanks to all...
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
Sweet as!
So everything gone fine till I try to push the framework-res.apk to my phone.
adb push framework-rez.apk /system/framework/
'adb' is not a recongnized as an internal or external command,
know I understand what that means but I installed SDK manager and had no cmd in there so I just used Command Prompt. If that is all of my problem how to I get SDK cmd? It didnt install when I installed the problem.
Omnicide said:
So everything gone fine till I try to push the framework-res.apk to my phone.
adb push framework-rez.apk /system/framework/
'adb' is not a recongnized as an internal or external command,
know I understand what that means but I installed SDK manager and had no cmd in there so I just used Command Prompt. If that is all of my problem how to I get SDK cmd? It didnt install when I installed the problem.
Click to expand...
Click to collapse
It's not enough to just install SDK manager, you also have to install ADB if you want to interface with your phone through your computer. You shouldn't have to go through SDK manager to use ADB once you have it installed, it should work straight through windows command prompt.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
That will walk you through installing adb. Good luck.
yoft1 said:
It's not enough to just install SDK manager, you also have to install ADB if you want to interface with your phone through your computer. You shouldn't have to go through SDK manager to use ADB once you have it installed, it should work straight through windows command prompt.
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
That will walk you through installing adb. Good luck.
Click to expand...
Click to collapse
Well thank you that helped me get pass that issue. Now how do I change the permissions on my phones framework-res.apk?
The error I have now is
"failed to copy 'framework-res.apk' to '/system/framework/framework-res.apl': Read-only file system."
I can't seem to figure a way around this.
Omnicide said:
Well thank you that helped me get pass that issue. Now how do I change the permissions on my phones framework-res.apk?
The error I have now is
"failed to copy 'framework-res.apk' to '/system/framework/framework-res.apl': Read-only file system."
I can't seem to figure a way around this.
Click to expand...
Click to collapse
I had that issue too, how I bypass it is to boot to CWM, go to "mounts and storage", then mount /system (and /data if that's relevant to what you're pushing). Others have used a line of code to mount the system from the PC end, but I find this easier to do through the phone.
yoft1 said:
I had that issue too, how I bypass it is to boot to CWM, go to "mounts and storage", then mount /system (and /data if that's relevant to what you're pushing). Others have used a line of code to mount the system from the PC end, but I find this easier to do through the phone.
Click to expand...
Click to collapse
Thank you that did the trick
Go to the system32 folder on your c drive and copy cmd from there to your tools folder in the sdk.
Now when you want to push, put the files you want to push in the tools folder and then open up the cmd that you placed in that folder, then run the push command.
Sent from my Galaxy Nexus using xda premium
Master&Slave™ said:
Go to the system32 folder on your c drive and copy cmd from there to your tools folder in the sdk.
Now when you want to push, put the files you want to push in the tools folder and then open up the cmd that you placed in that folder, then run the push command.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks ill give that a try in morning. That would be a better then how im doing it now my stuff is in all random folder and locations to get it to work.
Sent from my SGH-T989 using xda premium
Omnicide said:
Thanks ill give that a try in morning. That would be a better then how im doing it now my stuff is in all random folder and locations to get it to work.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
That's actually how I do it so it should work for you. Good luck
Sent from my Galaxy Nexus using xda premium
Master&Slave™ said:
That's actually how I do it so it should work for you. Good luck
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It worked for the file being in that folder and all. But I still have to do it in recovery and unmount system. I still get the read-only error
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.
Sorry if this is the wrong thread.
The run down. My phone is bootloader unlocked rooted etc. already flashed xenon rom and everything was great. (Just got the device today)
Ok so here's the trouble i'm in. I decided I wanted to try another rom so i boot into clockwork recovery wipe system,data cache etc. suddenly all my files dont exist.
I have no back up file (my stupidity). I can still get into fastboot, clockwork etc, but it does not recognize a sd card on the device.
i tried loading up Samnsung Toolkit v7.8.0 and all i see in the top menu is
fastboot-toolkit is not recognized as an internal or external command operable program or batch file
adb-toolkit is not recognized as an internal or external command operable program or batch file
this is what worries me. I plug the device in on my windows computer it recognizes something no sd card.. currently downloading factory images
BUT WHAT DO I DO?!!!! pls help and pls do not flame me etc. All I'm asking is simple help thanks
http://forum.xda-developers.com/showthread.php?t=1626895
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
kyokeun1234 said:
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
Click to expand...
Click to collapse
thank you will try that...question when i goto recovery mode its clockwork...when i hit mount sdcard nothing happens.
kyokeun1234 said:
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
Click to expand...
Click to collapse
also when tryin to access card via clockwork it states it cannot located directory...its like my sdcard does not exist
There is no sdcard on the gNex. As long as data is mounted you should be good
Sent from my Galaxy Nexus using Tapatalk 2
1st of all, Gnex doesn't have SDcard, therefore, you can't mount it. You can only use adb to push and pull files on recovery
2nd, are you sure you got proper driver? Do you actually have the ROM.zip on the same directory as adb.exe? If not, you need to do that. Also, if /sdcard/ doesn't work, /storage/sdcard0/ should work. It's a same directory. Just in different name for some reason.
3rdstring said:
There is no sdcard on the gNex. As long as data is mounted you should be good
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
just wanna say thanks guys!!!. i tried pushing as filename which pushed but still couldnt find it...decided to name the file update.zip and push then flash update zip and bang it worked i'm back up..dont know why my files disappeared but whatever i'm back up so i'm happy..thanks again
Gnex was a pain to get all the drivers installed, once they are Its a breeze to work with
Sent from my Galaxy Nexus using xda premium
daeshawn said:
just wanna say thanks guys!!!. i tried pushing as filename which pushed but still couldnt find it...decided to name the file update.zip and push then flash update zip and bang it worked i'm back up..dont know why my files disappeared but whatever i'm back up so i'm happy..thanks again
Click to expand...
Click to collapse
Just glad we helped
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
rsswga said:
Gnex was a pain to get all the drivers installed, once they are Its a breeze to work with
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus