Database Users

New guy rooting vibrant

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

Kindle fire stuck in TWRP 2.0 menu noob needs help. Im apologize...

Im sorry, I have tried everything to get my Kindle Fire up and running again. Ive read forum after forum trying to get it up and running. Ive tried the KFU the newest one and the older one. I tried to root my kindle fire and I some how got it stuck on TWRP 2.0. Here are the details of whats going on.
1. I am stuck on TWRP 2.0.
2. My PC does not recognize this device at all.
3. Ive tried deleting the drivers and re-installing the drivers.
4. None of the KFU devices see my KF on the pc.
5. I cant communicate with my KF device through ADB because the PC doesnt see anything.
6. I made the mistake of system restore through the OEM Amazon menu.
7. I dont have any custom roms on my KF device when I scroll through the TWRP menu.
8. I was a dummy and didnt backup the oem device version.
9. I cannot seem to push update.zip because there is no communication between my PC and the KF device.
10. The KF device is not even recognized for a quick second on my PC.
Any help would be greatly appreciated. I tried changing the INI file with the recommended numbers on the forum. Thanks for your time and thank you community in advances. I just wanted to get some better features on the device and i ended up paying the price. Once (i hope) it is restored I will never mess with the device again.

Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!

animefun135 said:
Mount your kindle like USB Storage ("Mount" in TWRP) download any rom and flash it!
Click to expand...
Click to collapse
can you explain a bit more? i pressed mount in TWRP, and i dont see my fire appearing in "My Computer"
Thanks

in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440

b63 said:
in twrp press mount - select sdcard - mount it
in device manager it should show up
if not you should update your drivers
you can use the ones from the newest kfu 0.9.2 http://forum.xda-developers.com/showthread.php?t=1399889
extract it to c:\ and rename to something like c:\kfu\ - sometimes it don't like spaces in pathname
if nothing shows up remove your old drivers: http://support.microsoft.com/kb/315539/en-us
and power down and power up your computer (no restart)
then it should detect something - use the drivers you downloaded - select them manually !!!
once you see the sdcard from your pc you can copy one of the prerooted roms (would take the secure version) or cm7 to the sdcard and install with twrp
prerooted stock images: http://forum.xda-developers.com/showthread.php?t=1402440
Click to expand...
Click to collapse
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.

bradlier said:
hey sorry but im having the same problem.. i can get it mounted and everything fine but when i move the prerooted stock you provided in the post it doesn't show up in twrp i have know idea what to do.
Click to expand...
Click to collapse
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything

b63 said:
try following:
rename the file to update.zip
copy to root of sdcard
sdcard is hopefully mounted in twrp since you don't see anything
Click to expand...
Click to collapse
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..

bradlier said:
i tried that and on my computer it shows up as a zip file but it wont show up on twrp but the other zips i have on the sd card do..
Click to expand...
Click to collapse
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad

b63 said:
can you open the file on your computer ?
i would try to re-download it - i think it has to be bad
Click to expand...
Click to collapse
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not

bradlier said:
yes the zip opens on the computer. i redownloaded and i got the zip to show up on twrp then flashed it then rebooted.. but all it does is show the yellow triangle thing and then the power button turns orange for a second and it goes right back to twrp.. im staring to think it might be bricked but i really hope not
Click to expand...
Click to collapse
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot

b63 said:
don't worry you'r not - it's simply the wrong boot mode
open adb and enter the following commands:
adb shell su -c "idme bootmode 4000"
adb reboot
Click to expand...
Click to collapse
sorry, but how do i do that?
command prompt? or something else?

bradlier said:
sorry, but how do i do that?
command prompt? or something else?
Click to expand...
Click to collapse
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands

b63 said:
do you have kfu available ? http://forum.xda-developers.com/showthread.php?t=1399889
if not download, extract to c:\ and rename "kindle fire utility" to "kfu"
you can let it kfu do for you:
run kfu by "run.bat" and select option 1 - change bootmode to normal
or do it manually by opening an (elevated) command prompt in the tools folder of kfu and issue the commands
Click to expand...
Click to collapse
hey man that was it.. thanks alot

Thanks for all the help. My actual problem was the drivers needed to be reinstalled and the USB cable I was using was no good. Go Figure!

[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.

How to put file on SDCard from Recovery

I need to flash a ROM, but I can't start my phone up to be able to transfer the file over. There used to be a Mount Storage Device option on my old DHD, but I noticed that on the N4, CWM does not have this option (maybe to do with MTP).
How can I copy a file over onto SDCard so I can flash it? I tried:
Code:
adb push file.zip /sdcard/file.zip
When I try and flash it, it says "Can't open /sdcard/file.zip (bad)

Flash TWRP via fastboot and mount the phone via usb the same drag it into the phone.
Alternatively as a last resort, flash back to stock using stock images provided by Google vis fast boot and then drag it onto the sd as well as reinstalling the recovery.
Sent from my Nexus 4 using xda premium

stefandunn said:
I need to flash a ROM, but I can't start my phone up to be able to transfer the file over. There used to be a Mount Storage Device option on my old DHD, but I noticed that on the N4, CWM does not have this option (maybe to do with MTP).
How can I copy a file over onto SDCard so I can flash it? I tried:
Code:
adb push file.zip /sdcard/file.zip
When I try and flash it, it says "Can't open /sdcard/file.zip (bad)
Click to expand...
Click to collapse
Remove the "file.zip" after the sdcard:
Code:
adb push file.zip /sdcard/
Also ensure the real file name doesn't contain spaces.
Edit: the command as you were typing it was telling adb to take the CONTENTS of file.zip and place them in a FOLDER called file.zip. Out of adb's range of abilities

Alternatively, if you're using CWM, you can use the "Install zip from sideload" option. Once you're in, push the file from adb using "adb sideload filename.zip"

The adb command you tried should work fine in recovery. Maybe you weren't in the correct folder where file.zip was located when you executed the adb command?
Also, if you don't have adb set in your PATH, then the adb app will need to be in the same folder as file.zip.
http://forum.xda-developers.com/showthread.php?t=1667929

se1000 said:
Alternatively, if you're using CWM, you can use the "Install zip from sideload" option. Once you're in, push the file from adb using "adb sideload filename.zip"
Click to expand...
Click to collapse
Thank you very much!

No OS but only CWM recovery

I want to flash a rom but i can't save the zip files to my storage. What do i do?
I have no os but only cwm. Please help, thanks.

dicksonjoe said:
I want to flash a rom but i can't save the zip files to my storage. What do i do?
I have no os but only cwm. Please help, thanks.
Click to expand...
Click to collapse
ADB Sideload
1. Connect your phone make sure it's actually connected. No errors in Device Manager
2. Rename the downloaded ROM you want to flash to something basic, like rom.zip (Names can get rather long)
3. Open CMD (command prompt), & navigate it to the folder you placed the ROM in. or just press shift and right click on the folder where the rom is and select open command prompt here
4. Boot to recovery on your phone and enable the ADB sideload function. Under Advanced in TWRP...not sure about CWM
5. in CMD type adb sideload rom.zip or what ever the name of the .zip is
6. Let TWRP or CWM flash the zip and prompt for reboot.
7. Reboot and be happy, your phone is fixed!
You can then transfer the gapps to your internal storage and flash the normal way through your reecovery or just go through the same process for the gapps after you flash the rom.

I am having trouble installing the adb file.
I don't know what mode my phone needs to be on in order to install adb file.

dicksonjoe said:
I am having trouble installing the adb file.
I don't know what mode my phone needs to be on in order to install adb file.
Click to expand...
Click to collapse
Installing adb doesnt have to do with what mode your phone is in.