Database Users

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.

Cant flash stock firmware on it and doesnt stay in media protocol

Hello. Well as the title says im having these issues. The main one is that im not able to flash anything on it using adb. I get a failed message. Everything was working fine until i flashed oreo on it 8.1. I was able to flash oreo with no issues but then once in oreo i couldnt flash twrp or another firmware at all and every time i connect it to a pc it stays on charging only and have to manually put it on media transfer. Could this be a software or hardware issue?
If i want to downgrade I just have to flash everything using adb right?

Has anyone had this issue?

The only time I have issues like yours is when my platform-tools folder gets wonky....so I just download the latest from Google and replace them all with the new ones. Maybe you have done this already but it doesn't hurt to try. Hope it helps

did you enabled developer settings and enabled usb debugging? and is your bootloader unlocked? I have no problems here on 8.1

notstevek said:
did you enabled developer settings and enabled usb debugging? and is your bootloader unlocked? I have no problems here on 8.1
Click to expand...
Click to collapse
I would do that and also make sure platrorm tools and drivers are up to date. Also check your usb ports on PC. Sometimes I have problems with one port but another works fine. Currently I have none of my ports work except one and only with a usb splitter weird right? Anyway check all those things and give it another try.

mojorisin7178 said:
I would do that and also make sure platrorm tools and drivers are up to date. Also check your usb ports on PC. Sometimes I have problems with one port but another works fine. Currently I have none of my ports work except one and only with a usb splitter weird right? Anyway check all those things and give it another try.
Click to expand...
Click to collapse
well it was actually my usb ports.. two of them just didnt work with fastboot but they worked fine with everything else like usb hubs, flash drives, etc... Althoguh I still got the problem when plugging it I have to change the setting on the phone for file transfer. Does it happen all the time in oreo? I havent gone back to nougat and try it out but when I was in nougat it was working just fine.
Another Issue I have is that I keep flashing twrp on it but everytime I restart the phone twrp gets delete and Im left with the regular recovery. Im trying with oreo 8.1

From the twrp website
"Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
hth

Im having some weird issues. First I cant keep twrp on oreo, no matter what version of twrp I use it always gets deleted. Second, when going back to nougat twrp stays installed but I cant boot into the system what combo would you suggest?

Nokia x6.1 bootloops to twrp.

So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.

Accidentally wiped OS when installing custom ROM--HELP!

I decided to switch my OP5 to Pixel Experience, so first step was to install TWRP. That went OK, and I then followed the instructions to wipe Dalvik/ART cache, Cache, System, Vendor and Data. However the big mistake I made was that I didn't first download the new firmware and OS to the phone. After wiping, the phone will no longer boot and is not recognized by my PC (though it does show up in Device Manager and is accessible via ADB). Turning the phone on results in a message that it's unlocked, then the screen goes blank and the notification light turns white. Power/Volume Up results in the fastboot screen and Power/Volume Down results in TWRP screen. I tried using ADB fastboot to flash the boot.img file to Boot, and now turning on the phone causes it to go to the fastboot screen, but that doesn't solve any problems.
I think what I need to do is find some way to get the ROM zip file onto the phone. (I have copies of OOS 9, 10.0 and 10.1 on my computer, as well as the Pixel Experience OS.) But how do I do that when the PC cannot find the phone? (I'm guessing it's connected as charging only, but obviously there's no way to change that on the phone.) I thought about getting a USB To Go adapter and using a thumb drive, but apparently you have to first turn on that option on the phone. Is there any way to use ADB/fastboot to flash a zip file rather than an img file?

You need to install the proper drivers for adb on your phone, it should then be able to detect the phone when it is plugged in on fastboot mode. From there, you should be able to fastboot flash what you need onto the phone.

have you tried adb push ROM.zip /sdcard/ ?, this would move the whole Rom to /sdcard for you to flash it though TWRP

Thank you, thank you, thank you!!! I was not aware of the ADB Push command, but now it's my best friend. I really appreciate you taking the time to save me.

Clashing Plaids said:
Thank you, thank you, thank you!!! I was not aware of the ADB Push command, but now it's my best friend. I really appreciate you taking the time to save me.
Click to expand...
Click to collapse
Ur welcome

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself