I'm trying to install the 4.1.2 update using the adb sideload method from Android Central but my Windows cmd window states a message saying
* cannot read 'sideload' *
Any ideas to what I'm doing wrong?
Sarg92 said:
I'm trying to install the 4.1.2 update using the adb sideload method from Android Central but my Windows cmd window states a message saying
* cannot read 'sideload' *
Any ideas to what I'm doing wrong?
Click to expand...
Click to collapse
Rightclick in the adb window, choose 'open command prompt here' that way you don't have to manually navigate to the right directory. Once the command prompt is open, type:
Code:
adb sideload {name of file}
NOT a developer here, just have some experience with the basics. Good luck to you.
Thanks!
The update is installing now so this thread can be closed!
Sarg92 said:
Thanks!
The update is installing now so this thread can be closed!
Click to expand...
Click to collapse
Awesome, glad it worked out.... edited typos for others, but you obviously figured it out. Good job!
GT-P6800
GT-N8013
Ok. Real noob question. How do you get to the adb window to right click?
rip93 said:
Ok. Real noob question. How do you get to the adb window to right click?
Click to expand...
Click to collapse
You dont. Navigate to your adb platform tools folder, right-click in the window (just anywhere in the empty space), and select "open command prompt here" --in the same folder that adb.exe resides in---
Then you can type (in the command window)
Code:
adb devices
just to make sure you're connecting to your device, if so then type
Code:
adb sideload {name of file}
don't type {name of file}, just type the name of the file you're wanting to sideload, including the file extension (the 4.1.2 update I'm guessing) --make sure the file is in the same folder as adb.exe so you don't need to type the path name...
Hope that helps
GT-P6800
GT-N8013
aletheus said:
You dont. Navigate to your adb platform tools folder, right-click in the window (just anywhere in the empty space), and select "open command prompt here" --in the same folder that adb.exe resides in---
Then you can type (in the command window)
Code:
adb devices
just to make sure you're connecting to your device, if so then type
Code:
adb sideload {name of file}
don't type {name of file}, just type the name of the file you're wanting to sideload, including the file extension (the 4.1.2 update I'm guessing) --make sure the file is in the same folder as adb.exe so you don't need to type the path name...
Hope that helps
GT-P6800
GT-N8013
Click to expand...
Click to collapse
When I do this, I get same result as typing in "adb help." I don't understand since I see the device when typing "adb devices."
http://www.farside.org.uk/200906/adb_no_devices_found
GT-P6800
GT-N8013
I'm having issues as well. ADB recognizes my N7. I have the file in my /android/platform-tools folder. But when I run adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip, it does the same thing as if I use just the command adb.
Any ideas?
I'm in my adb directory and the file is in there as well
What does it say when you type "adb devices" ?
It lists the device serial number.
Does it also say "sideload" next to the device serial number?
janedoesmith said:
Does it also say "sideload" next to the device serial number?
Click to expand...
Click to collapse
No, it says host.
That's a new one on me. Are you using a Mac? I'm using Win7 x64. When in stock recovery and in the "apply update from adb" screen, mine says:
<device serial number> sideload
janedoesmith said:
That's a new one on me. Are you using a Mac? I'm using Win7 x64. When in stock recovery and in the "apply update from adb" screen, mine says:
<device serial number> sideload
Click to expand...
Click to collapse
Win7 here too, LOL
asimons81 said:
Win7 here too, LOL
Click to expand...
Click to collapse
I'm sorry, I've neverhad tis problem. If your device id is showing up in an adb devices query, you should be able to type
Code:
adb sideload {path to file/name of file}
And it should run.... is your device in recovery? Or just plugged in? Have you enabled USB debugging in settings>developer options?
GT-P6800
GT-N8013
aletheus said:
I'm sorry, I've neverhad tis problem. If. Our device I'd is showingup in an adb devices query, you should be able to type:
Code:
adb sideload {path to file/name of file}
And it should run.... is your device in recovery? Or just plugged in? Have you enabled USB debugging in settings>developer options?
GT-P6800
GT-N8013
Click to expand...
Click to collapse
I reinstalled my drivers. I now have serial number / sideload, but using the adb sideload code still runs the same as typing just adb.
------------------------------------------------------------------------
SOLVED: Had to delete my platform-tools folder and reinstall adb. Worked first try. =D
broadwayblues said:
When I do this, I get same result as typing in "adb help." I don't understand since I see the device when typing "adb devices."
Click to expand...
Click to collapse
I'm getting this too. Any advice?
Edit: Ignore this. Reinstalled and works fine.
Great
sikagoon7 said:
You need to cd to your adb directory and type in: adb sideload C:\path-to-ota\ota.zip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That is the solution :laugh::good:
Thanks
Related
figured it out thanks for all the help please delete......
my fear said:
ok i downloaded everything that this link tells me:
http://forum.xda-developers.com/showthread.php?t=532719
but when i put in
cd C:\android-sdk-windows\tools
it just stays in that folder i cant do anything past that. when i type adb shell it says 'adb' is not recognized as an internal or external command, operable program or batch file.
i just redid my computer from windows 7 32 bit to now i have 64 bit. am i missing something? when i had 32 bit i had it working but now nothing and i have all the same stuff as before. yes my phone has debugging checked.
any help is appreciated.
thanks,
Stephen.
Click to expand...
Click to collapse
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
rsfaze said:
if its saying adb is not a recognized command you are not in the tools folder.
Which directory are you in?
If you do a dir it should list all of the files in the current directory , do you see adb.exe ?
Click to expand...
Click to collapse
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
my fear said:
ok when i start cmd the line says C:\users\Mr. Tarno>
then i put in cd C:\ android-sdk-windows\tools and then it is in that folder then i did what you said and typed dir and yes it shows adb.exe, its the top file.
when i type adb.exe it shows all the possible commands that i could type but when i try it says adb is not a recognized command.
Click to expand...
Click to collapse
That would be right.
I think you're trying to type adb -d shell for example instead of adb.exe -d shell. You would need to include the file extension as well when including commands to be done by ADB.
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
UpsideDownAce said:
So, I've been trying to force over the 4.2 update to my N7 with adb. And every time I try to sideload the update, I get "adb cann't ready sideload"
I don't understand why it won't work. Every other adb command works fine. I'm on rev. 21 for sdk tools and 16 for platform tools. I literally just downloaded the SDK.
Any ideas?
Click to expand...
Click to collapse
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
uncleswoop said:
I've been wondering the same thing.... No one seems to know or care to help. Bump this post...
Click to expand...
Click to collapse
Just to be sure, you've apply sideload from adb in the recovery, correct?
ducatic said:
Just to be sure, you've apply sideload from adb in the recovery, correct?
Click to expand...
Click to collapse
I'm in the same boat! I tried, today, several times to sideload the update but I'm constantly getting the cannot read sideload error message. I guess I'm off to other sites to see what the fix is.
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
adb sideload 094f6629314a.signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
Click to expand...
Click to collapse
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
I might be just an idiot but why are you guys trying to SideLoad a system update?
AFAIK... sideload is merely to install apps into your rom that Jellybean or the Playstore doesn't like.
I think you guys want to use "ADB Fastboot" commands instead. Get a guide before you attempt to do this though. I used Wugs Toolkit to install the bootloader from 4.2.2 update.
fede01_8 said:
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
Click to expand...
Click to collapse
:laugh: true
For clarity:
- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.
Code:
adb sideload update.zip
- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
fac851 said:
I had this problem too, but solved it this way:
Place the file you're trying to sideload is in the same adb directory, f.i. C:\Android
And when in the CMD window, change the active directory to this directory before you type: adb sideload [name of file]
So:
- run CMD window
- change your active directory to adb C:\Android
Code:
cd\
cd android
- type:
Code:
adb devices
(List of devices should indicate a number of the connected device)
- type:
Code:
adb sideload [name of file]
Click to expand...
Click to collapse
fede01_8 said:
YES! i have found the solution. i just registered to share it to anyone with the same problem. i spend HOURS and HOURS, literally sweat and frustation like i've never experienced before to update this POS. i was ready to smash my one week old Nexus 7.
the solution is so simple and stupid that i want to smash my forehead on my keyboard.
i was using this video as a guide to manually update the N7 youtube /watch?v=iQhyerPfGes
what it doesn't say is that you DON'T HAVE TO UNZIP THE FIRMWARE!!!
You have to issue the command from the platform-tools folder (or the directory in which adb.exe resides). Right-click n the folder window and choose "open command prompt here." Then type
remember, don't unzip the firmware
my Nexus 7 still doesn't finish the update because it say something about an error, but that's another problem
but at least i'm not getting "cannot read sideload" anymore :laugh:
Click to expand...
Click to collapse
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
brandnewyc said:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
Click to expand...
Click to collapse
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!
Please help!!
Same problem...fixed
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
jihoon526 said:
I had the same cannot read sideload problem.
The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".
Because this was done in windows, the file system recognized it as "kk.zip.zip".
Just rename the file without ".zip" (just "kk")
then try again - in my example: adb sideload kk.zip
it works~
Click to expand...
Click to collapse
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Fix
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
hkleiner said:
For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
Click to expand...
Click to collapse
are you on the same directory as your file?
teaclarke said:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
Click to expand...
Click to collapse
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
DigitalOSH said:
So I had a similar experience. when I tried to use
Code:
adb push
, it would say error:closed. This was weird since the device showed up when I ran
Code:
adb devices
.
When I tried to do
Code:
adb sideload xxx.zip
I would get the
Code:
cannot read sideload
error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
Click to expand...
Click to collapse
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.
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
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
Hey, I just updated my PC to latest version so I can't open cdm. It asks to open PowerShell Command prompt, witch I can't use to flash images! I searched in Google how to disable it for ever, but no answer. Can anyone help me?
Just throw cmd to start menu and then use cd command to go to your adb directory
Vika__ said:
Just throw cmd to start menu and then use cd command to go to your adb directory
Click to expand...
Click to collapse
I tried that, and it can't find Fastboot or Adb other files it show!
RootingPro-18 said:
I tried that, and it can't find Fastboot or Adb other files it show!
Click to expand...
Click to collapse
Try adding ./ in front of adb command if you have folder specific adb
This should work on PowerShell
like this
Code:
./adb devices