Develop Bugs

HELP pushing files

hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.

Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250

I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help

nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!

Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!

Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool

italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.

i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.

Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2

Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium

I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/

[Q] Not really bricked but bricked for the time being

Hello. I currently have 2 S4 minis (I19195). One works perfectly and is mine. I also have only one SD card. I was in the process of installing CM on the new one and I wiped the SD card by accident (it contained the CM installation and gapps package).
The SD card refuses to work with either device now and I don't have a card reader.
The device currently has no OS on it. It's got CWM working, though. I need to get it running ASAP.
Is there a way to a) fix the card or b)get the CM files on it somehow or c)install CM solely through odin?
EDIT: I should also mention it refuses to mount USB storage through CWM.

In CWM you should be able to use adb. Try using adb push to upload files from your computer to the internal sd

Whosat said:
In CWM you should be able to use adb. Try using adb push to upload files from your computer to the internal sd
Click to expand...
Click to collapse
Thanks a lot for your reply, however I can't seem to find the option for adb in CWM.

teokk1 said:
Thanks a lot for your reply, however I can't seem to find the option for adb in CWM.
Click to expand...
Click to collapse
You can either adb push a rom.zip to your internal sdcard. Or side load the zip
Sent from my Nexus 5

jd1639 said:
You can either adb push a rom.zip to your internal sdcard. Or side load the zip
Sent from my Nexus 5
Click to expand...
Click to collapse
The problem is I have no way to access the internal sd card (other than odin, unless that's what you meant).
Also I tried flashing stock back onto it, which failed, and now I get a screen saying "Firmware upgrade enctountered an issue. Please select recovery mode in Kies & try again." I also seem not to be able to enter into recovery anymore, just download mode.

teokk1 said:
The problem is I have no way to access the internal sd card (other than odin, unless that's what you meant).
Also I tried flashing stock back onto it, which failed, and now I get a screen saying "Firmware upgrade enctountered an issue. Please select recovery mode in Kies & try again." I also seem not to be able to enter into recovery anymore, just download mode.
Click to expand...
Click to collapse
Boot into recovery and then from a cmd prompt on your pc type adb devices. It should show your device. If it does then, adb push rom.zip /sdcard. Where rom.zip is a rom you have on your pc and can push it to your device
Sent from my Nexus 5

jd1639 said:
Boot into recovery and then from a cmd prompt on your pc type adb devices. It should show your device. If it does then, adb push rom.zip /sdcard. Where rom.zip is a rom you have on your pc and can push it to your device
Sent from my Nexus 5
Click to expand...
Click to collapse
Unfortunately I can't boot into recovery anymore. Just download mode and the stupid broken screen.

teokk1 said:
Unfortunately I can't boot into recovery anymore. Just download mode and the stupid broken screen.
Click to expand...
Click to collapse
I don't know your device well. Can you download the firmware from sammobile and flash that in Odin?
Sent from my Nexus 5

jd1639 said:
I don't know your device well. Can you download the firmware from sammobile and flash that in Odin?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yep that's exactly what I did.
Anyway, I was just about to post everything I ever did to the phone to clarify. However I figured I should flash CWM once again and maybe get that to work.
After doing that and rebooting the phone EVERYTHING works, it booted straight into the OS and I just finished installing CM which works now. I'm not even going to pretend I understand what happened (and I have a degree in computer science...). Anyway, I'm very happy it works, and thank you both so much for helping me out!

teokk1 said:
Yep that's exactly what I did.
Anyway, I was just about to post everything I ever did to the phone to clarify. However I figured I should flash CWM once again and maybe get that to work.
After doing that and rebooting the phone EVERYTHING works, it booted straight into the OS and I just finished installing CM which works now. I'm not even going to pretend I understand what happened (and I have a degree in computer science...). Anyway, I'm very happy it works, and thank you both so much for helping me out!
Click to expand...
Click to collapse
Glad you got it working again
Sent from my Nexus 5

[Q] Unable to mount /sdcard/

How can I try to use my internal SDCard in CWM, or would I be able to use my laptop to install SuperSU? I am not able to get a new microSD card until christmas and would like to root

TheGamingBarrel said:
How can I try to use my internal SDCard in CWM, or would I be able to use my laptop to install SuperSU? I am not able to get a new microSD card until christmas and would like to root
Click to expand...
Click to collapse
Try adb sideload. It installs packages in cwm via the usb connection so you won't need to put them on the external sd first.

4m8 said:
Try adb sideload. It installs packages in cwm via the usb connection so you won't need to put them on the external sd first.
Click to expand...
Click to collapse
When I am trying to send the file I get this message "* cannot read 'UPDATE-SuperSU-v1.34' *"
EDIT: I am an idiot, I forgot to put .zip but now it says that it cant find the device

TheGamingBarrel said:
When I am trying to send the file I get this message "* cannot read 'UPDATE-SuperSU-v1.34' *"
EDIT: I am an idiot, I forgot to put .zip but now it says that it cant find the device
Click to expand...
Click to collapse
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.

4m8 said:
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.
Click to expand...
Click to collapse
I changed to TWRP and it worked, but thanks for your help!

4m8 said:
Can you see the device if you type "adb devices"?
Yes? Did you put the phone into sideload mode?
No? Check your setup, There should be plenty of tutorials on how to setup adb for any OS.
Click to expand...
Click to collapse
Ok, I plugged it in, went to sideload in TWRP and windows asked me to format the disk in drive E:/ Could this fix it?

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about

I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...

adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.

adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...

Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient

badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...

adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery

Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!

rooted and unlocked m9 in boot loop

So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.

paleost0ner said:
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
Click to expand...
Click to collapse
Sounds like your sdcard failed. You said you can get into recovery, so try getting ahold of another sdcard with Viper ROM zip file on it and flash it.

Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone

l7777 said:
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
Click to expand...
Click to collapse
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Sent from my HTC6535LVW using XDA-Developers mobile app

mikelikesbikes said:
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Click to expand...
Click to collapse
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.

l7777 said:
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
Click to expand...
Click to collapse
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Sent from my HTC6535LVW using XDA-Developers mobile app
---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need? Looking at the instructions I see the SD card must be formatted to fat32. I have no idea if mine is, but I have extras. I can format one of them to fat32, keep that file on it, and in case I ever need it I can pop it in the phone and flash it?
Sent from my HTC6535LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my HTC6535LVW using XDA-Developers mobile app

mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Click to expand...
Click to collapse
Yes. It must have a special name and be in the root of the sdcard. I don't remember exactly what the name is for the M9 but it is posted in the RUU threads.