Database Users

Samsung S4 i9505 semi bricked, need help!!!!!

After failing to install CM 10.1 I have custom recovery, CM is just stuck on boot logo, I don't even want it anymore.
Anyway I have made a back up in meanwin, but I moved it to my computer because it was too large, all I need is to copy that folder to my phone but I can't. I can use an sd card but I haven't purchased one yet.
How can I copy the backup folder? I tried the mounting option in custom recovery but it didn't show up in my computer.
Please help! any advice would be greatly appreciated!!

dateacake said:
After failing to install CM 10.1 I have custom recovery, CM is just stuck on boot logo, I don't even want it anymore.
Anyway I have made a back up in meanwin, but I moved it to my computer because it was too large, all I need is to copy that folder to my phone but I can't. I can use an sd card but I haven't purchased one yet.
How can I copy the backup folder? I tried the mounting option in custom recovery but it didn't show up in my computer.
Please help! any advice would be greatly appreciated!!
Click to expand...
Click to collapse
supposing that you have adb file on your pc or you have android SDK installed
boot into custom recovery, connect your phone to pc open cmd and type the following commands (you dont need to enable usb debug for this process):
Code:
adb devices
you must see a serial number
Code:
adb push C:\name of rom.zip or backup /data/media/
supposing that your rom/backup is on C
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip/backup from recovery, reboot.
EDIT : first wipe data and cache with recovery then reboot it may fix the bootloop
EDIT 1: if you find this hard (and it is not, it is good to learn something) you can make the wipe and flash stock firmware

samersh72 said:
supposing that you have adb file on your pc or you have android SDK installed
boot into custom recovery, connect your phone to pc open cmd and type the following commands (you dont need to enable usb debug for this process):
Code:
adb devices
you must see a serial number
Code:
adb push C:\name of rom.zip or backup /data/media/
supposing that your rom/backup is on C
Code:
adb reboot recovery
once done, go to your phone and install the rom.zip/backup from recovery, reboot.
EDIT : first wipe data and cache with recovery then reboot it may fix the bootloop
EDIT 1: if you find this hard (and it is not, it is good to learn something) you can make the wipe and flash stock firmware
Click to expand...
Click to collapse
I learned something new even if I don't need it but thanks

Stuck in recovery mode

Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!

Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2

rcholic said:
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Click to expand...
Click to collapse
Of course you are able to use ADB in recovery mode. Have you tried
Code:
adb push nameoftherom.zip /sdcard/
or if you are using a recovery where you are able to use adb sideload
Code:
adb sideload nameoftherom.zip
Then it should work. Or try mounting the usb in mounts/storage -> mount usb storage
scream4cheese said:
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Of course, it should work if the drivers are installed properly

Like others said use adb push to put a file on the device and then you can flash it with recovery.
If you don't have adb you can get it either by downloading android SDK or just downloading adb did
Sent from my Nexus 4 using xda app-developers app

Try flashing back to stock, then just root and put your ROM back on, I've had to do it once before
Sent from my Nexus 4

Cant boot out of TWRP

My brother installed TWRP and tried flashing a Rom with out making a back up. He is now stuck in twrp with no rom to install as he didn't transfer the rom to the phone before hand . How can we copy a rom onto the phone now?

ant78 said:
My brother installed TWRP and tried flashing a Rom with out making a back up. He is now stuck in twrp with no rom to install as he didn't transfer the rom to the phone before hand . How can we copy a rom onto the phone now?
Click to expand...
Click to collapse
You should be able to use adb with TWRP to push the rom onto the phone. Connect your phone to your computer and check to make sure adb sees it by running:
Code:
adb devices
If your device is listed, you can push the rom zip file by running:
Code:
adb push romzipfile.zip /sdcard/
Where romzipfile.zip is the name of the rom zip file that you want to install. Once the transfer has finished you should be able to install the zip using TWRP. Hope this helps!

thanks will give this a try :good:

says my device is not found?

ok i have my device sideloaded but when i push the rom to my phone it says "error closed" or "can not read zip"

Fixed. I rebooted my pc and my phone and it sideloaded fine

Stuck in CWM - device not recognised

Hi
I flashed CloudG3 rom under CWM, and after install it won't boot the system - it sends me to CWM recovery instead.
Figured I would install another ROM but my device is not recognised by windows (won't show up under my computer). Can you please guide me on what I could do to sort this?
Thanks

Install the lg g2 drivers to get recognised by the os, after you download driver for adb sideload and restart, run sideload in the recovery with the usb pulgged in ur pc.
Open Android folder, and then do to platform-tools, drag a ROM there to be installed. Open a command in this folder. Write what is in the cellphone, adb sideload romfilename.zip if i'm right, then it will start installing and then you get out of the recovery stuck.
Using TWRP.

Hi
I installed lg drivers but it didn't help - looked like it was CWM that was causing an issue to get the device detected by computer.
Before you posted, I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2739739 - this helped to get TWRP on top of CWM. Under TWRP, the device is detected by windows
Now should I install a rom using your guidance above or can I do it under TWRP? Or is it the same?

Can't copy files to /sdcard/

Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717

I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/

well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?

Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.

I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.