Database Users

Flashing A Recovery Rom..

I have searched this forum multiple times and i can not find my answer so i am posting this hoping someone with some patience will help me.. when i followed these steps.. "III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
•adb shell mount -o rw,remount /dev/block/mtdblock3 /system
•adb push recovery.img /sdcard
•adb push flash_image /system/bin
•adb shell chmod 755 /system/bin/flash_image
•adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
It says that what i have typed is not an executible file.. someone please help.

are you 100% sure that you extracted the file out of the zip and not just put the zip into the folder?

yea im sure

Are you typing out each command? or are you pasting them into your terminal? Also, what OS are you running ADB from, and have you had success with it before? Or is the eris your first android device
Also, you did the previous steps first correct? IE: you're ROOTED

there is an easier way posted by i think Zinfab it was something like.
su
adb shell
reboot bootloader
at this point make sure it says fastboot USB on the screen
then in the same window fastboot flash recovery recovery.img (make sure your recovery.img is in the same directory as all your SDK tools)
this worked for me when the method u posted didn't work

where do i type this stuff in at.. i have my phone plugged in usb debug checked i installed the usb driver update it and i have the recovery thing extraced in my tools folder now what do i use my computers command prompt or my phones command prompt

ashertheplague said:
where do i type this stuff in at.. i have my phone plugged in usb debug checked i installed the usb driver update it and i have the recovery thing extraced in my tools folder now what do i use my computers command prompt or my phones command prompt
Click to expand...
Click to collapse
did u set the enviromental variable? its not that important I'm just curious.
if not in command prompt first command would be
(directory to tools)\adb shell
"su"
"Reboot bootloader"
then once its in bootloader
(directory to tools)\"fastboot flash recovery (directory to recovery.img)"
now the quoted sections should be typed exactly as is, without the quotes, but you have to know your own directory.

when i type it in on my phone it says adb not found

whats that

ok my phone now is in fastboot usb mode what do i do know

as suggested, did you set the variable? type fastboot devices to see if its even working correctly, to start.

how do i get out of fastboot usb

Type in the command fastboot flash recovery recovery.img

ok now it says waiting for device

You didn't search that well.
http://forum.xda-developers.com/showthread.php?t=647974

well i went to that forum and it was still giving me problems.. but i got help from spence_moore so its all good

ashertheplague said:
well i went to that forum and it was still giving me problems.. but i got help from spence_moore so its all good
Click to expand...
Click to collapse
What step were you having a problem with? If there is something wrong I would like to fix it.

[Q] ADB Can't Read Sideload

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.

Messed up my Nexus 4 :(

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

[Q] Copying nandroid backups to MAC

I am sure this has been asked and answered, but I am not finding the answer. Anyone have a good method for backing up CWM backups to MAC? I know the CWM backups are stored at /data/media/clockworkmod which is not accessible to the MAC. I guess I could copy them to /data/media/0 and then access them from my mac. I guess I could also use ADB, but am looking for something simpler and less data manipulation. If this has been answered, please link me.

1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn

Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
I have done it with ADB. Was hoping for something more elegant. Thank you.
Sent from my Nexus 7 using xda app-developers app

Pirateghost said:
1. open terminal
2. ./adb pull /data/media{0, clockworkmod, twrp}
3. popcorn
Click to expand...
Click to collapse
Could you please write it in a more specific way? I'm a noob
I explain what I did:
I opened the terminal and I went in the folder were I keep the fastboot and adb etc..
I tried first with "./adb pull.." but nothing happened (aka: -bash: ./adb: No such file or directory)
Then I tried "./adb-mac pull.." and it didn't work either but I got the following long message:
"Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
environment variable.
etc..."
I tried both commands at first with the mobile on, then I reset it and I went in recovery mode with the same results..
I'm going insane, I even tried to copy the whole folder of clockworkmod with my backup to another folder, but I couldn't see it with my computer.
I'm running mac OS X, I could eventually try also to my PC windows 7.. I just need to copy my backup to a safe place :crying:

After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus

Pirateghost said:
After the pull command you need to tell it what to pull
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod

ziovelvet said:
Sorry Pirateghost, I meant that I wrote as you said:
./adb-mac pull /data/media{0, clockworkmod, twrp}
and I got just the long message from the Terminal and it doesn't work (even when using ./adb without the "-mac")
edit: ok I solved it:
I used this and it seems working (finally)
./adb-mac pull /data/media clockworkmod
Click to expand...
Click to collapse
the {0, clockworkmod, twrp} was to indicate that you can pull ONE of those folders at a time, or pull /data/media and get ALL of them at once

[Q] How to push file using TWRP adb sideload and Nexus 4 Toolkits

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