Help: "closed" message when trying to use sdb - Samsung Gear 2 Neo

Hi everyone!
I'll go right to the issue, I'm trying to change the icons on a Samsung Gear 2 Neo following the instructions on this thread: http://forum.xda-developers.com/showthread.php?t=2782669. So far I had to change the firmware so I could root it, fight with drivers, ROMs, Odin, and all that stuff, and finally could root it, but now that I run the command "sdb shell mount -o remount,rw /" I get the message "closed" and can't proceed. I tried changing firmware, resetting to factory, rerooting, everything to no avail. So I'd like to ask for your help to solve this issue. I'll leave a screencap of the command window here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance.

Related

[Q] Can't enable sideloading "cp: not found" error

Trying to use method 1 from this guide here to enable sideloading: http://forum.xda-developers.com/showthread.php?t=738376
When I type in..
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
I get..
cp: not found
I get the same error if I try copy instead of cp.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you install BusyBox? You need it to use "cp" command..
And, for BusyBox. you need to Root your phone first..
SnakeHaveYou said:
Did you install BusyBox? You need it to use "cp" command..
And, for BusyBox. you need to Root your phone first..
Click to expand...
Click to collapse
Thanks, the issue was my BusyBox install was FUBAR, reinstalled Busybox and everything went smoothly.

[Q] adb doesn't work for me on w8 pro n

Hello,
my problem is that, adb doesn't recognize my phone, and i wanna change my radio firmware...
i use this tuto, without any results.
Tuto.-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and the devices show me this .-.
thats all,
regards.
Pd: excuse my english...
It seems that adb is not found, you should add adb's directory to the PATH environment variable in Windows. After that, type "adb devices" in the command line, and you should see the list of connected devices.
i do,
and restarts .-.
Edit: nevermind, i fix that or i guess

Where to start for rooting NA Red Magic 3s?

I'm sorry if this is redundant but I would like to make sure I'm doing the right thing. I have a RM 3S, model NX629J, build NX629J_V1S_ENCommon_V1.04, running Android v9.
I've read quite a few threads here, watched a few youtube videos, and have seen some comments saying I wouldn't be able to root my version. I want to know if root is possible. There are some indications I'm reading that it is but to get TWRP I'll need the Chinese rom, is that correct?
One problem I've ran into as I'm trying things is I can get ADB to detect the device when I boot normally but once I go into fastboot, it's unable to detect the phone despite the driver being installed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the videos I watched was from this:
https://www.youtube.com/watch?v=pmyb2kh-1Jo
But I thought I've read that if my bootloader is locked, I wouldn't be able to patch the .img file thus I can't use Magisk on the RM 3S.
A little direction would be great. Thanks!

Need help with sideloading error

I keep getting an "Cannot read coral" update that released today. Been sideloading software updates for over 6 years and this is the first time I have ran into this. Any help is greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@win465 Because you are trying to flash an OTA image, I take it to mean via adb through recovery? In that case I would confirm your fastboot/adb binaries are up to date and try another USB-A to USB-C cable. What do you get from adb when you use the devices command? version command? If it can't read the file from your PC, the problem is likely with the adb setup on that PC.

TROUBLE MOTO E5 (XT1944-3)

Hello everyone, I'm new here. Hope you take care of me.
People I have an issue with my phone the imei is reported and I'm trying to fix it. I have already rooted with magisk and now I'm doing this (
) but when I try to enable the DIAG port in my phone doesn't let do it... Just installing the drivers it should appear in device manager but don't, by the way I was trying to enabling it by ADB writing this
Spoiler: THIS CODE
Code:
adb devices
adb shell
su
setprop sys.usb.config diag,adb
but when I try the answer is other.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does somebody knows what I have to do?
Thank you.
PD: Sorry if this is not the place where I have to put this post.

Categories

Resources