Hi everybody
Today I've just messed up my phone by deleting all TWRP backups as well as ROM zip files on my N4 (haven't found out why i did it, hell!)
Now after wipe my current rom, I've totally in the middle of "NoRom"
I have TWRP, and Nexus 4 Toolkits installed on my PC. I think all drivers are installed correctly as well, since I used them to unlock bootloader and root my N4 before.
But i just cannot figure out how to "ADB sideload" zip file to my device in order to flash a new rom.
So please guild me to do this. Many thanks
Note: I read on TWRP page and they say that I have to enable adb sideload in TWRP on my N4 (of which i've done), then "From the command line, type adb sideload /path/to/rom.zip". From that point I cannot understand. How and where could I open the command line?
(sounds noobie but since downloading that Toolkits, I've got rid of pure ADB things, so now I don't have the sdk)
Thank you.
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thank you, i'll try it
Back to the past when i got G1, i was familiar with sdk and adb thing. But as time passing by, i'm getting lazier and lazier lol, so i've almost forgotten those useful stuffs, just use some 1-click tools like the toolkits.
Help
Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried sideload on my nexus 4 but it gives me this error...
"failed to write data 'protocol fault (no status)"
I have been trying to sideload cm 10.2 since my phone is stuck on the google boot logo...any ideas as to how to solve this problem?
Cheers beforehand!
close "adb.exe" in task manager
Help please. I've done the same thing as the OP. I do not know what to do next.
I am unable to mount the phone. I click on "Mount" from TWRP's main screen and nothing registers on my computer.
Under Advanced I am able to click on ADB Sideload but then the adb commands do not work to sideload a rom. I am able to use the command adb devices and that returns a response. I have also tried the adb push command to move the rom onto the phone with no response.
What should I do next?
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks that worked.
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey bro it says device not found. what do i do?
---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.1.9 it didnt work for me it said device not found
---------- Post added at 10:37 PM ---------- Previous post was at 09:46 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey Thank i got it working, but one thing i cant understand is i got in a boot loop cause install cm10.1.3 RC2 coming from cm 10.2 nightly version, i also flased gapp 4.2.2 assuming the rom was 4.2.2 that why. is this correct? i wanna go to cm10.1.3 RC2 current on 10.2 nightly how can i do this? which gapps should i install?
Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app
Hi,
I moved from slimbean build 8 (4.2.2) to Slimbean 5 (4.3)
After a couple of reboot the phone stucks an google screen, I tried to reflash the rom from twpr but nothing chaged.
If I try to sideload small files (like supersu) it works, with rom.zip files not..
I have "* failed to write data 'protocol fault (no status)' *" after some seconds.
If I try to use sideload from twpr home (2.6.0.0) adb doesn't work,
adb devices
List of devices attached
0076a0288a8c04be recovery
Cwm
Is it possible to do the same with Cwm instead of twrp? If so, how? Also, i have both twrp and cwm according to rom manager. How?
Thanks your a life saver!
Alex240188 said:
Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
HElp
Hi guys,
I had the same problem while trying to install a new rom and i got into a bootloop stuff.
I tried what its say before on this thread but my phone can't be found. what can i do ?
Excuse my english i'm French.
Thx for your help if somebody can help me.
i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.
Jens_Karlsson said:
i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.
Click to expand...
Click to collapse
being a noob at all of this, I am getting nowhere..... all I did so far was install android sdk. and put phone into sideload....
when I did adb push rom.zip /sdcard and it did some things?
then I do adb devices (in the cmd line of windows) and it gave me my serial number.... but what now?
I see nothing on the phone to load/install?
also: I type this: adb push rom.zip /sdcard
it says error closed.
Even i have been caught up with this same problem , and i found this thread which was pretty helpful
HTML:
http://forum.xda-developers.com/showthread.php?t=2318497
that saved my day !!
I have the same problem
I have the same issues. When i type adb devices in command prompt, I get
List of devices attached
(there are nothing under it) what should i to ? Help me please
Install http://koush.com/post/universal-adb-driver
Report back if still having issues.
help!!!!!
I get this but now what???
C:\adb> adb push rom.zip /sdcard
_
Nothing more and in my phones sd its the rom but failed when i tried to install it
Related
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
Hay, my name's Nick, been reading the posts for a while, decided to join. Iv'e been wanting to root my T-mobile vibrant so i can get a more streamlined ROM will less features to make the ones i use go smoother and faster and get the full potential out of the device. I rooted it no problem with one click root, installed clockwork rom manager, and titanium backup, installed clockwork recovery (i love the clockwork orange icons by the way) put the latest "insanity 0.6.7.zip" in the root of the internal SD, and hit the "install rom" option on the rom manager and selected the .zip, and it made my phone go into the standard recovery mode, no option to install any .zip files. So i opened the rom manager and manually put it into CWM recovery so i could manually install the rom. It looked like it was going to work, but then it sent my phone back to the recovery screen with white text that said "install update.zip" so i did what it said, and it sent my phone into a boot loop. I can get into recovery mode, but when ever i try to recover my backup or access any files it says "no files found, operation canceled" or something like that. It also fails to mount via USB. I can get it to go to download mode but have not tried odin yet, because im on a mac (working on getting bootcamp working now to run windows)
Odin seems like my only option now right? anyone have any idea ware I went wrong? it must have been the incorrect update.zip file right?
I dont think u flashed a vibrant rom
Just mount your internal sd from clockwork and copy over a vibrant rom, and flash
Sent from my SGH-T959 using XDA Premium App
have any idea why it wont let me mount my sd card? that makes me worried it wont connect to a Pc in download mode but i haven't had the opportunity to try that yet.
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
when it booted up it went to my normal "vibrant" screen, then to an unfamiliar "galaxy s 19000" screen. Im assuming there is a difference between galaxy s and vibrant right?
jRi0T68 said:
I'd download your rom of choice, there are a ton that are perfect fit first timers. Trigger and Bionix-V seem very stable. Pop your external sd into your computer, copy the .zip for the rom, go into recovery, select install from zip and flash your rom.
Odin is last resort. I'm not familiar with insanity, but maybe it was a bad download?
Click to expand...
Click to collapse
tried that, when i try to to install zip from sdcard it says "no files found"
i assume it's looking for files on the internal and not the external right? so i tried mounting the external sd card from the mounts and storage menu, and i got an error message that said "E:INFO is WRONError mounting SDEXT !"
In recovery, do you see any folders when you click install from zip, or is that when you get an error message?
If you see folders, can you navigate to external_sd?
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
niik000 said:
i click "install zip from SD" and it brings me to a menu with the options to apply sdcard.update.zip or choose zip from sd card, and when try ether one of those options it says "No Files Found"
I have a rom in a zip on the root of my external now, just cant get to it.
Too bad i cant help trying to fix things that aren't broken
Click to expand...
Click to collapse
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
amandadam said:
If you can access xda from your phone,download a vibrant rom from there.
Once it's downloaded,it will be in the root of your internal sd,under download.You can then flash it in cwm,or when the download is complete,click on it and choose Rom Manager to open it,and you can flash it from there.
Here's a link to Bionix 1.3.1,on xda.
http://forum.xda-developers.com/showthread.php?t=925548
Click to expand...
Click to collapse
That's useful for me as well.!
shreddintyres said:
not your external sd, zip should be on your internal sd
since you can get into recovery you can try using adb to push the zip from your computer to the phone
install android sdk and drivers for vibrant then using command prompt navigate to the following directory in the android-sdk folder
\platform-tools\
then execute the following command again in cmd prompt
adb push <dir for zip> /sdcard
if that doesnt work then odin will be your only choice and you must be in download mode to do that
Click to expand...
Click to collapse
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
niik000 said:
do i need an update.zip? or just the bionix-v-1.3.1.zip? or am i supposed to rename the bionix zip to update.zip?
Click to expand...
Click to collapse
Never rename rom zips to update.zip leave it at bionix.zip and flash through clockwork mod recovery.
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
niik000 said:
now i cant figure out how to get any of the ADB commands to work, i have ADB running and it put a list of commands in he terminal but when i try any of those commands it says "command not found"
i tried
"adb devices" (c-bash: adb: command not found)
"./adb devices" (directory not found)
and "devices" (-bash: devices: command not found
)
am i doing something wrong?
Click to expand...
Click to collapse
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
i ran the SDK and AVd manager and installed the rest of the SDK packages, then found the ADB file and drug it into the terminal, that gave me the list of commands. I plugged in the phone and tried "adb devices" and it said "command not found" tried quitting and restarting terminal a few times and still nothing
shreddintyres said:
first you have to be in the android sdk directory and second you must run the sdk manager process and download the rest of the sdk, the bit that you download from the website does not include the full android sdk, you will also need to have java runtime environment 5 or later installed on your pc.
also if you are running adb in linux you need to sudo or su adb commands
in linux you will need to restart the adb daemon
su
adb kill-server
adb start-server
adb devices
hope this helps
Click to expand...
Click to collapse
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
niik000 said:
when i enter "su" it asks for a password, but it will not let me type anything. Iv'e never really worked with commands like this but im interested in learning, thats kind of why i decided to mess with the phone
Click to expand...
Click to collapse
thats a security feature within linux it wont show what you are typing but rest assured its registering keystrokes, and you dont drag and drop to terminal
assuming the androidsdk is in your home directory you would type
cd /home/username/android-sdk/platform-tools
then ./adb devices (this is just a check to make sure your phone is being recognized)
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
niik000 said:
i type
/Users/<my username>/android-sdk-mac_x86/platform-tools
and it tells me
/Users/<my username>/android-sdk-mac_x86/platform-tools: is a directory
then i type ./adb devices
and it says
-bash: ./adb: No such file or directory
im getting really confused, it seems like im making a really simple mistake i just cant figure out what im doing wrong
Click to expand...
Click to collapse
ok so you are doing this from mac then? i apologize as i have no experience messing with android using a mac, id imagine itd be much like linux although terminal commands may be different. If i were you id google using adb commands in mac os and see what you can find, personally i use windows normally and am only just learning how to work linux
Hi,
I have been trying to educate myself by using TWRP (ver 2.3.2.1) and loading custom ROM's
I have used the format option in TWRP and now I can no long load or push any files to the SD card. I am able to use WegFresh Root Tool Kit (ver 1.6.1) and get to TWRP and to the bootloader (Android laying on it's back - chest open)
How do I re-create the proper file structure to be able to load ROM's once again. As an example..... "/system" is completely empty.
Thank you....
Update - The problem has been solved and it was due to the driver between my laptop and the Nex7. In Device Manager it was showing up as "Andriod Phone - Andriod Bootloader Interface" THIS WILL NOT WORK!
Your device manager has to say - "Android Phone - Android ADB Interface" for it to be able to push files to the Nex7
Thanks to all who helped me.
Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3
RMarkwald said:
Have you reflashed your ROM of choice?
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks
Dekan54 said:
Thank you for the reply. I am unable to push any ROM (zip file) using TWRP or adb push.....
When I use a DOS prompt and type - "adb push rom.zip /sdcard" I get a reply "error: device not found" It seems as thought I can't write any files to the sdcard since I formatted the sdcard. Is it a permission issue? How can I restore the proper file structure of the sdcard so that a rom can be pushed and loaded?
Thanks
Click to expand...
Click to collapse
How does the device show up in Device Manager? I assume you're using Windows.
- Sent from my US Cellular SGS3
Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks
Dekan54 said:
Yes - I am using Windows 8 (64bit)
In Device Manager it shows as "Andriod Phone - Andriod Bootloader Interface"
I have no OS on the NEX 7 so I can't turn "debug mode" on......
TWRP see the device id......
Thanks
Click to expand...
Click to collapse
I've heard that Win8 causes issues, specifically with fastboot flashing files. I've heard you can install the drivers and is recommended to turn off driver signing.
Debug mode only works when the device is booted in the OS, not recovery. Do you have access to another OS, like Linux or Win7? This may be easier to do.
- Sent from my US Cellular SGS3
I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.
Dekan54 said:
I will fire up my old Win 7 laptop in the morning and give that go.....
Thank you for your help this evening.
Click to expand...
Click to collapse
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3
if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app
ngoralph said:
if still not working reflash stock rom from google
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks
RMarkwald said:
No problem! The reason I've suggested this is I've worked with someone for three hours and in the end it was Win8. Win7 worked in minutes.
Good luck! Post with an update!
- Sent from my US Cellular SGS3
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
And honestly, I'd flash to stock 4.2.1 from Google, re-root, flash recovery, then flash ROM of choice. With the latest version of Recovery of your choice you shouldn't run into this issue in the future.
- Sent from my US Cellular SGS3
Click to expand...
Click to collapse
Just an update....
I am getting the same results with Win7 OS that I was getting last night when you were helping me. My Nex7 is displayed in the device manager as - "Android Phone - Android Bootloader Interface" in Win7 just as it is in Win8.
I have been using Wegfresh's Nexus Root Toolkit (1.6.1). It will show me the device ID went I click the button - show device id. I am able to reboot into bootloader. I am able to boot into recovery and get to TWRP and navigate around.
If I could just get a stock or custom ROM file to the NEX7 I would be in good shape. But I am unable to "adb push" anything to the nex7.
I will be glad to go "step by step" to trouble shoot this with you.
Thanks
I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Blackdragon77 said:
I've not mypc, so I can't help you step by step.
You can use the advanced options of the toolkit to flash a zip or use the sdk to use the adb sideload.
google will help you to found how use "adb sideload", as the option you can see in recovery.
Click to expand...
Click to collapse
Thank you for the reply. I have tried the "adb sideload" option in TWRP and it fails. I get the error - "error - device not found"
I welcome anyone who might have some idea's for me to try.
Thanks
Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb
Blackdragon77 said:
Thy to see my edit upon how to run sideload.
You must not use the tookit, but you must install android sdk and use the true adb
Click to expand...
Click to collapse
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.
No problem! Tell me if that's the solution!
Inviato dal mio Nexus 7 con Tapatalk 2
I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.
Dekan54 said:
I would love to reflash any rom.... (cwm 10, Google, etc....) but my NEX7 will not except (push) any files to it. If I could just get a rom.zip file over to it I could then load it via TWRP.
I am open to suggestions from anyone.
Thanks
Click to expand...
Click to collapse
Do you connect your N7 with adb ? if yes, try the clockworkmod recovery v6.0.1.9 , it has a fuction very good to push rooms, it is the "instal zip from sideload"
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
Dekan54 said:
I will load the true adb sdk toolkit and give that a shot. Thank you for your help.
Click to expand...
Click to collapse
follow this videos :
1º How to Install ADB Drivers for Google Devices
http://www.youtube.com/watch?v=vUSRmtexmUo
2º How To Install ADB and Fastboot for Windows
http://www.youtube.com/watch?v=Yc4z-KYypgY
it worked for me
tabbiex said:
I was having the same problem also. Correct me if I'm wrong, but I believe in Fastboot mode (Android laying on it's back - chest open), you cannot use adb. Here you can use Fastboot. Adb is use when in Recovery mode. Have you tried using fastboot.
Click to expand...
Click to collapse
You are correct, the OP needs to go into recovery (TWRP recovery is fine) and use adb to push files to the device- you can't use adb from fastboot.
I have used exactly the same method myself as I was in exactly the same situation myself.
Of course the OP needs adb on his PC from the SDK as mentioned earlier in the thread.
Still having the same error after installing adb from the sdk on my Win7 computer. I also made sure I installed JAVA and downloader the updates for the adb sdk.
The error is still - "error - device not found"
When I use TWRP to look at the files on my Nex7 the following folders are present
cache
data
dev
proc
res
root
sbin
sdcard
sys
system
tmp
usb-otg
default.prop
fstab.grouper
fstab.qcom
init
init.rc
ueventd.goldfish.rc
ueventd.grouper.rc
uevent.rc
The folder "sdcard is empty except for a twrp folder....
Any other things I should try?
Thanks
Guys i have a problem...
I wantes to delete all data on my N4 and start again with a fresh device, My phone is rooted and i had an custom rom installed, i deleted all data pictures and everything else, after that i also formated the sd card, cache etc etc and thats where it went wrong Now i can go into cwm but nothing more... when i reboot i see the black screen with google on it and after that nothing happens...
How can i solve this problem? I hope that i didnt bricked my phone
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
I just helped a user with the same problem yesterday.
Here's the link with steps how to push a rom to your phone with adb: http://forum.xda-developers.com/showthread.php?t=2137976
can you get into fastboot? if you can then all you have to do is follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312
coffmad said:
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
Click to expand...
Click to collapse
No, you can't mount USB in recovery. The Nexus 4 does not use UMS.
Ok thanks for the fast reply, im gonna try to push a rom with adb.
''I know you don't have a rom on your phone. This is how you can push one to your phone.
You must be booted in recovery
Put the rom in the same directory on your PC where you have adb.exe
Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/
The file with push to your phone and then your can select it and flash it from recovery''.
I see this in another thread, Where can i find adb.exe? Im terrible with computers...
Adb is part of of the platform tools for android. Since you unlocked and flashed a custom rom you should have it on your computer.
If you need it, it is located as an attachment at the bottom of this post: http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Mr Djoegoe said:
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Click to expand...
Click to collapse
Extract the files in that .zip into a folder and name it something like "Android."
Move the Rom.zip into that folder as well.
Then do the shift and right click and open the command window pointed to that directory. (as I explained above)
Make sure its connected properly and there isn't a driver issue by typing the command: adb devices. If it returns your serial number you are good to go. (If not, you need to install the correct drivers, which are linked in Section A of the post I linked earlier.)
Then type the command. adb push nameofRom.zip /sdcard/
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Edit: hahahaha i see what i do wrong nameofRom.zip
Are you actually typing "nameofrom.zip" ?
Sent from my Nexus 4 using xda app-developers app
Mr Djoegoe said:
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Click to expand...
Click to collapse
You replace "nameofRom" with the name of your ROM your trying to push
moses992 said:
Are you actually typing "nameofrom.zip" ?
Click to expand...
Click to collapse
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Mr Djoegoe said:
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Click to expand...
Click to collapse
Thanks for that. Unneeded, but very appreciated!
Sent from my Nexus 7 using Tapatalk HD
You certainly haven't bricked it. The fact you can get to recovery means, you can get to fastboot. Simply open fastboot and reflash stock and be more careful next time
I recently rooted my phone. I have not installed any ROMs because i love the stock rom so much but i decided to try one today. I didnt have my computer with me so i downloaded one today and rebooted into recovery. I saved my current rom and then wiped and accidently pressed Data, it asks if i want to wipe everything and i press back. I go to look at my downloads and they are all gone. I look for my backup i had JUST nandroid backed up and it was gone.
So there i am stuck. There is a thread for returning to Stock rom. Sure ok, but its a long process including the 2 gig download which is only uploading at 260mbit/s so another hour or 2.
I have tried sideloading a rom but it fails.
Any suggestions on how to get a rom onto the phone without booting it? I dont have a micro usb to sd card or i would have done that already =/
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
fr4nk1yn said:
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
via sideload or no?
No. Sideload could work, I don't remember the command off hand.
Adb push copies it to the internal memory then you flash through the menu normal.
Sent from my Nexus 7 using Tapatalk
fr4nk1yn said:
You need adb on the pc, connect, then in terminal or cmd
Code:
adb push ROM.zip /sdcard
Copying the zip to the folder with adb makes it easier and the above command correct, (of course replace ROM.zip with the actual name).
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I gave you thanks.
That seems to work. For anyone that gets into this situation where there are no roms in your phone and you have no way to transfer them. Boot into TWRP, do not use sideload. Just main screen. Device manager will show to be just "g2" and you need the driver. In the driver folder from http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869 driver section, update driver and browse to 64BitADB and choose androidandadb. It will then give you a list of options starting with Testing drivers, one that dates back to 2010 and another thats 2012. You want the one thats 2nd from the bottom called LG G2 verizon net adb or something like that. Works perfect and connects to adb.
If anyone truely needs this process i can break it down to specifics on how to get it to work. Thanks so much for your help fr4nk1yn!