Error main cannot start client command adb - Исправление ошибок и поиск оптимальных решений проблем

adb server version (39) doesn't match this client (40); killing...
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
adb: error: failed to get feature set: protocol fault (couldn't read status): Connection reset by peer
* daemon not running; starting now at tcp:5037
* daemon started successfully
- waiting for device -
error: protocol fault (couldn't read status): Connection reset by peer

Alex P.

29.8k17 gold badges118 silver badges168 bronze badges

asked Sep 21, 2018 at 12:30

I have the same issue when running adb devices command.

adb devices
List of devices attached
adb server version (36) doesn't match this client (40); killing...
* daemon started successfully
2322dc3d    device

I ran command which adbwhich gave me the location of the adb that the previous command was using, in my case output was:

which adb
/usr/bin/adb

Then i ran whereis adb command which gave me the location of adb’s:

whereis adb
adb: /usr/bin/adb /home/arefin/Android/Sdk/platform-tools/adb 
/usr/share/man/man1/adb.1.gz

I get rid of this problem by moving the adb from /usr/bin directory with mv command: (meaning this is of no use thus instead of deleting just put in desktop),

/usr/bin$ `sudo mv adb /home/arefin/Desktop/`

After this i executed this command adb kill-server then ran adb devices. I found everything is fine this time.

My Android development related path in in $HOME/.profile file is, as below:

export ANDROID_HOME=/home/arefin/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$JAVA_HOME/bin

answered Nov 24, 2018 at 11:49

When encountered this error in Linux,I deleted the adb file in my

/usr/bin/

and replaced with one which located in path (usually in home path)

~/Android/Sdk/platform-tools/

and it worked.

AnasSafi

4,4391 gold badge32 silver badges32 bronze badges

answered Oct 14, 2020 at 12:36

As pointed out in previous answers, this is due to having multiple adb versions installed in your system. Probably one from the android-sdk-platform-tools installed via apt and other from Android Sdk itself (which is usually newer version).

The simplest way to solve this in Ubuntu (or Ubuntu-based OS’s) is to add this line at the end of ~/.bashrc file:

alias adb='~/Android/Sdk/platform-tools/adb' 
#Change path according to your Android Sdk installation directory

And then reopen terminal for changes to reflect.

This avoids the need to mess with system files as well.

answered Jan 23, 2021 at 12:07

Probably you have two versions of adb in two different locations in your system. The running server version is 39 and the adb client version is 40. You can resolve this by keeping only one adb in your PC.
You can figure it out as shown below-

In Linux below command gives you adb location if adb binary is added to path.

which adb

if adb is not added to path and still you are getting this error then search for adb using below command.

locate adb

if your adb client is other than above location, you may add newest version to above path and delete the old adb version.

If you are using windows, you figure it out the two adb locations and keep only at single place.

answered Sep 22, 2018 at 17:06

RilwanRilwan

2,2512 gold badges19 silver badges28 bronze badges

I know this is a little old, but if you have this problem and you have Vysor installed, then you can resolve it by looking in the Vysor application folder for the adb.exe (and Adb*.dll files) and replacing them from your Android SDK folder. I’m on a Windows machine and the relevant paths for me were:

Vysor
- C:Users\AppDataRoamingVysorcrxgidgenkbbabolejbgbpnhbimgjbffefmapp-2.1.7.crx-unpackednativewin32*
- (I’m guessing the path will vary according to the version, etc, but this will hopefully help figure it out.)
APK
- C:Users\AppDataLocalAndroidSdkplatform-tools

On my machine, the relevant files were:

adb.exe,
AdbWinApi.dll,
AdbWinUsbApi.dll

After this, you will need to kill the existing ADB task as described in the other answers to this post.

answered Aug 21, 2019 at 16:27

Dave WellingDave Welling

1,6101 gold badge17 silver badges13 bronze badges

Solved by

Open terminal in Android studio

adb kill-server

sudo cp ~/Android/Sdk/platform-tools/adb /usr/bin/adb

sudo chmod +x /usr/bin/adb

adb start-server

answered Nov 25, 2021 at 10:53

SubratsssSubratsss

7475 silver badges12 bronze badges

Run

tasklist | findstr adb

then kill the duplicate process

TASKKILL /PID "PID_NUMBER" /f

answered Mar 5, 2019 at 12:38

Encountered this problem myself, none of the solutions online worked for me.
did this by chance and it solved my problem!

I’m using Android Studio on a Macbook Pro.

first I tried to install adb from brew:

brew cask install android-platform-tools

then I uninstalled it:

brew cask uninstall android-platform-tools

After the last line adb didn’t work in terminal but did work in Android Studio immediately! =D

posted so it may help someone else — good luck!

answered Apr 5, 2020 at 10:52

Ariel YustAriel Yust

5854 silver badges11 bronze badges

For ubuntu (more precise — kubuntu) i had the similar problem.

The problem was in android-studio, to fix it you need to do these steps:

Go to SDK-Manager
In SDK-Manager click the SDK Tools menu.
Uncheck «Android SDK Command-line Tools (latest)»

answered Dec 21, 2020 at 11:28

shlopshlop

661 silver badge2 bronze badges

I had the same issue connecting to my SFTP Server app and could solve it as follows:

The error was caused (in my case, Ubuntu 18.04.5 LTS) by conflicting adb installations. One Installation coming with AndroidStudio (IntelliJ) located in .../Sdk/platform-tools and one coming with the package manager installation apt install located in the standard directory for executables /usr/bin. The installation location for AndroidStudio (IntelliJ) can be found in the AndroidStudio (IntelliJ) Menu: Tools → Android → SDK Manager: Android SDK Location. And the installation location related to the package manager can be found invoking the command which adb.

And the solution to this problem is to uninstall one of them.

Depending on your use case, if you’re most of the time working with AndroidStudio (IntelliJ) (and this version is up to date), then remove the (outdated) version installed with the package manager as follows.

To uninstall first find out which packages relates to /usr/bin/adb with the following command: dpkg -S /usr/bin/adb.

And then call apt autoremove adb to uninstall the adb package and all its dependencies.

And last but not least in order to still being able to call adb from the command line update the PATH variable in “/etc/profile”, if it should be accessible for all users, or ~/.bash_profile or ~/.profile (whichever exists) if it should only be accessible for the current user and append the path “…/Sdk/platform-tools” (that you looked up above) at the end. And then reboot or log-out & log-in for the new path to get applied.

answered Jan 31, 2021 at 18:44

In ubuntu

delete the adb

-> usr/bin 
-> (delete command) sudo rm -rf /usr/bin/adb

Android/Sdk/platform-tools/adb
```
-> copy this folderpath.
```
paste into
```
->usr/bin
->(paste command) sudo ln -s /home/yourfile/Android/Sdk/platform-tools/adb /usr/bin
```

answered Mar 16, 2022 at 8:53

restarting your system, would also work for you.

answered Mar 24, 2021 at 21:38

I have faced the following error and what worked in my case was just to restart the system.

could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon code here
adb.exe: failed to check server version: cannot connect to daemon

answered Apr 15, 2021 at 15:14

Rahul SharmaRahul Sharma

5,8274 gold badges36 silver badges46 bronze badges

I had a similar error. Two different adb versions were conflicting with each other which caused it to keep restarting.

Run this command in terminal => where adb.exe

This will show you where the different adb files are. You can look at the file property date to see which is the latest one. Then copy the latest one and use it to overwrite/replace the older one(s). This will make both adb versions be the same and prevent a conflict.

answered Nov 3, 2021 at 1:55

This generally happens when there are two adb paths are available. Uninstall one will help

—> npm uninstall adb

This worked in my case.

answered Dec 6, 2021 at 10:23

Ankit GuptaAnkit Gupta

7675 silver badges12 bronze badges

None of the other solutions worked for me — Windows/WSL2-Ubuntu

The error is misleading but for me it was cos the adb port 5037 was in use.

Solution: find and kill the process using port 5037

Windows: netstat -aon | findstr 5037 and Stop-Process -Id <id-from-netstat>

WSL will attempt to connect to Windows port 5037

answered Dec 26, 2021 at 23:26

piousonpiouson

2,3422 gold badges24 silver badges28 bronze badges

In my case wsl Ubuntu has different adb --version than Windows, I don’t have to keep my Android Studio latest(since this might not your choice and do not guarantee same version as apt) or try with $PATH(wsl run Windows exe is not make sense).

The solution is simple, I download both Linux and Windows SDK Platform-Tools from official site which guarantee same version, then invoke relevant adb on each platform.

answered Jan 26, 2022 at 10:02

林果皞林果皞

7,3813 gold badges52 silver badges69 bronze badges

In my case I’d installed «AirDroid» on my windows machine and it runs «AirDroid_adb.exe«, I had to kill that to get things to work. I have reported that they are using an old version of adb and they will hopefully fix it.

answered Sep 4, 2019 at 1:01

A Working Simple Answer for Windows:

make sure you have the sideload file (whatever.bin) in a sub directory of your adb executable.
make sure your adb executable folder, and sub directories are in PATH (look up DOS commands for PATH in Windows)
open a command prompt in the same directory as the sideload file
enter your command for example:
```
adb sideload mynewrom-5.4.3.2.1.bin
```

(Your device needs to be in recovery — sideload state before you send)

Stephen Rauch♦

46.7k31 gold badges109 silver badges131 bronze badges

answered Nov 9, 2018 at 0:30

Источник

adb server version (39) doesn't match this client (40); killing...
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
adb: error: failed to get feature set: protocol fault (couldn't read status): Connection reset by peer
* daemon not running; starting now at tcp:5037
* daemon started successfully
- waiting for device -
error: protocol fault (couldn't read status): Connection reset by peer

Ответы
13

Возможно, у вас есть две версии adb в двух разных местах вашей системы. Версия работающего сервера — 39, а версия клиента adb — 40. Вы можете решить эту проблему, оставив на вашем компьютере только один adb.
Вы можете понять это, как показано ниже —

In Linux below command gives you adb location if adb binary is added to path.

which adb

Если adb не добавлен в путь, но по-прежнему появляется эта ошибка, выполните поиск adb, используя команду ниже.

locate adb

Если ваш клиент adb находится не в указанном выше местоположении, вы можете добавить новейшую версию по указанному выше пути и удалить старую версию adb.

Если вы используете окна, вы определяете два местоположения adb и держите их только в одном месте.

Рабочий простой ответ для Windows:

Убедитесь, что у вас есть файл боковой загрузки (любой.bin) в подкаталоге вашего исполняемого файла adb.
Убедитесь, что ваша исполняемая папка adb и подкаталоги находятся в PATH (найдите команды DOS для PATH в Windows)
Откройте командную строку в том же каталоге, что и файл неопубликованной загрузки
Введите свою команду, например:
```
adb sideload mynewrom-5.4.3.2.1.bin
```

(Ваше устройство должно быть в состоянии восстановления — неопубликованная загрузка перед отправкой)

У меня такая же проблема при запуске команды adb devices.

adb devices
List of devices attached
adb server version (36) doesn't match this client (40); killing...
* daemon started successfully
2322dc3d    device

Я запустил команду which adb, которая дала мне местоположение adb, который использовала предыдущая команда, в моем случае вывод был:

which adb
/usr/bin/adb

Затем я запустил команду whereis adb, которая дала мне местоположение adb:

whereis adb
adb: /usr/bin/adb /home/arefin/Android/Sdk/platform-tools/adb 
/usr/share/man/man1/adb.1.gz

Я избавляюсь от этой проблемы, перемещая adb из каталога /usr/bin с помощью команды mv: (это означает, что это бесполезно вместо удаления, просто вставленного на рабочий стол),

/usr/bin$ `sudo mv adb /home/arefin/Desktop/`

После этого я выполнил эту команду adb kill-server, затем запустил adb devices. Я обнаружил, что на этот раз все в порядке.

Мой путь, связанный с разработкой Android в файле $HOME/.profile, выглядит следующим образом:

export ANDROID_HOME=/home/arefin/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/platform-tools
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/emulator
export PATH=$PATH:$JAVA_HOME/bin

Запустить

tasklist | findstr adb

Затем убейте повторяющийся процесс

TASKKILL /PID "PID_NUMBER" /f

Я знаю, что это немного устарело, но если у вас есть эта проблема и у вас установлен Vysor, вы можете решить ее, заглянув в папку приложения Vysor для файлов adb.exe (и файлов Adb * .dll) и заменив их из на свой Папка Android SDK. Я нахожусь на машине с Windows, и соответствующие пути для меня были:

Высор
- C: Users \ AppData Roaming Vysor crx gidgenkbbabolejbgbpnhbimgjbffefm app-2.1.7.crx-unpacked native win32 *
- (Я предполагаю, что путь будет зависеть от версии и т. д., Но, надеюсь, это поможет разобраться.)
APK-файл
- C: Users \ AppData Local Android Sdk platform-tools

На моей машине соответствующие файлы были:

adb.exe,
AdbWinApi.dll,
AdbWinUsbApi.dll

После этого вам нужно будет убить существующую задачу ADB, как описано в других ответах на этот пост.

В моем случае я установил «AirDroid» на свой компьютер с Windows, и он запускает «AirDroid_adb.exe», мне пришлось убить его, чтобы все заработало. Я сообщил, что они используют старую версию adb и, надеюсь, исправят ее.

Я столкнулся с этой проблемой, ни одно из решений в Интернете не помогло мне.
сделал это случайно, и это решило мою проблему!

Я использую Android Studio на Macbook Pro.

Сначала попробовал установить adb из brew:

brew cask install android-platform-tools

Затем я удалил его:

brew cask uninstall android-platform-tools

После последней строки adb не работал в терминале, но сразу работал в Android Studio! = D

Опубликовано, так что это может помочь кому-то другому — удачи!

Когда я столкнулся с этой ошибкой в Linux, я удалил файл adb в своем

/usr/bin/

И заменен одним в

/Android/Sdk/platform-tools/

И это сработало.

Для ubuntu (точнее — kubuntu) у меня была аналогичная проблема.

Проблема была в android-studio, чтобы исправить это, вам нужно сделать следующие шаги:

Заходим в SDK-Manager
В SDK-Manager откройте меню SDK Tools.
Снимите флажок «Инструменты командной строки Android SDK (последняя версия)».

Как указывалось в предыдущих ответах, это связано с тем, что в вашей системе установлено несколько версий adb. Вероятно, один из android-sdk-platform-tools, установленного через apt, а другой из самого Android Sdk (обычно более новой версии).

Самый простой способ решить эту проблему в Ubuntu (или ОС на базе Ubuntu) — добавить эту строку в конец файла ~/.bashrc:

alias adb='~/Android/Sdk/platform-tools/adb' 
#Change path according to your Android Sdk installation directory

Затем снова откройте терминал, чтобы изменения отразились.

Это также избавляет от необходимости возиться с системными файлами.

У меня была такая же проблема при подключении к моему приложению SFTP-сервер, и я мог решить ее следующим образом:

Ошибка была вызвана (в моем случае Ubuntu 18.04.5 LTS) конфликтующими установками adb. Одна установка поставляется с AndroidStudio (IntelliJ), расположенной на …/Sdk/platform-tools, а другая — с установкой диспетчера пакетов apt install, расположенной в стандартном каталоге для исполняемых файлов /usr/bin. Место установки AndroidStudio (IntelliJ) можно найти в меню AndroidStudio (IntelliJ): Tools → Android → SDK Manager: Android SDK Location. А место установки, относящееся к диспетчеру пакетов, можно найти, вызвав команду which adb.

И решение этой проблемы — удалить один из них.

В зависимости от вашего варианта использования, если вы большую часть времени работаете с AndroidStudio (IntelliJ) (и эта версия актуальна), удалите (устаревшую) версию, установленную с помощью диспетчера пакетов, как показано ниже.

Чтобы удалить, сначала выясните, какие пакеты относятся к /usr/bin/adb, с помощью следующей команды: dpkg -S /usr/bin/adb.

Затем вызовите apt autoremove adb, чтобы удалить пакет adb и все его зависимости.

И последнее, но не менее важное, чтобы по-прежнему иметь возможность вызывать adb из командной строки, обновите переменную PATH в «/ etc / profile», если она должна быть доступна для всех пользователей, или ~ / .bash_profile или ~ / .profile ( в зависимости от того, что существует), если он должен быть доступен только для текущего пользователя, и добавьте путь «… / Sdk / platform-tools» (который вы искали выше) в конце. А затем перезагрузитесь или выйдите из системы и войдите в систему, чтобы применить новый путь.

Перезапуск вашей системы также подойдет вам.

Я столкнулся со следующей ошибкой, и в моем случае сработало просто перезапустить систему.

could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon code here
adb.exe: failed to check server version: cannot connect to daemon

Другие вопросы по теме

Источник

hack3rcon: Posts: 541; Joined: 2015-02-16 09:54

Share Internet From PC To Android.

Post

by hack3rcon » 2021-04-04 09:08

Hello,
I want to share my Internet from PC to my Android cell phone. I looked at https://fossbytes.com/how-to-share-inte … gnirehtet/ and installed the Gnirehtet on my cell phone, but it doesn’t work:

Code: Select all

$ ./adb devices
List of devices attached
1163731066	device

Then:

Code: Select all

$ sudo ./adb -s 1163731066 install -r gnirehtet.apk 
Performing Streamed Install
Success

And finally:

Code: Select all

$ sudo ./gnirehtet run
2021-04-03 20:32:39.633 INFO Main: Checking gnirehtet client...
2021-04-03 20:32:39.633 INFO Main: Starting relay server on port 31416...
2021-04-03 20:32:39.633 INFO Relay: Relay server started
2021-04-03 20:32:39.633 ERROR Main: Cannot start client: Command adb ["shell", "dumpsys", "package", "com.genymobile.gnirehtet"] failed: No such file or directory (os error 2)

Any idea to solve it?

Thank you.

Источник

huliqan

Thanks a lot! Works fine on my Oculus Quest2 !
Virtual Desktop app works from USB connect to PC server without Wi-Fi !!!

huliqan

Virtual Desktop by USB use gnirehtet works fine in Quest2(with audio streaming disable)
But it works only if internet there is in the PC
If I disconnected ethernet cable from router, VD not found my PC :((( (PC ethernet connected to router)
How to fix it without internet ?

hi dear
when i connect my phone ( s21 ultra with android 12 ) with typec to laptop my telegram application not connect and say wait for network
also some other application like samsung bixby , psiphon , fish vpn , samsung cloud not work

I think the best next feature should be socks proxy support or http proxy support. What do you think? How complex it would to add this?
Do you have any idea where the proxy should be placed? I could try to do it myself if you don’t have the time…

I’m using gnirehtet to use my PC internet connection for my smartphone, but i want to share that connection from my smartphone to other devices thru hotspot or bluetooth. is this possible?

Hi All.

When using gnirehtet in combination with the android global proxy setting
the webbrowser traffic is proxied with the help of gnirehtet wich is exactly what i want but
i need additional the possibility to exculde certain website domains to not be proxied and just
go only over gnirehtet and not over the android global proxy.

Some time ago for this the android global setting global_http_proxy_exclusion_list was used
adb shell settings put global global_http_proxy_exclusion_list
and it worked but now this setting does not exist anymore for exclusion of webdomains.
3 Years ago somebody wrote that this is possible in combination with gnirehtet see here =>
https://gist.github.com/fuminchao/9df897782eee698e113360d4f10d6247
but i am not able to get it to work.

Despite the fact that android uses «http_proxy_exclusion_list» in the source code
https://cs.android.com/android/platform/superproject/+/master:packages/modules/Connectivity/framework/src/android/net/ConnectivitySettingsManager.java;l=214;drc=master
the possibility to set this global configuration value is missed in the global settings for some strange reason.
https://developer.android.com/reference/android/provider/Settings.Global
only http_proxy exist now and not global_http_proxy_exclusion_list !!!

I Pay a developer 50 USD over paypal if he can add the possibility to the gnirehtet app
to use addional a http proxy for webbrowsing but with the possibility to exculde certain domain from being proxied
on non rooted android phone.
At the moment i am just able only to proxie all webbrowser traffic or none.
It should be not like this.
This exclude host from proxied is actually a common feature for any proxy but somehow
it can not be configured in combination with gnirehtet and the android global proxy.

To solve this Pay a Developer 50 USD as it is very important to me.
Maybe the most easy solution for this is to use the android proxy library or the suggested VPN Proxy setting as written here:
https://developer.android.com/reference/android/net/VpnService.Builder#setHttpProxy(android.net.ProxyInfo)

setHttpProxy
Added in API level 29

public VpnService.Builder setHttpProxy (ProxyInfo proxyInfo)
Sets an HTTP proxy for the VPN network.

and addiding just the required configuration in the Gnirehtet app
to set the proxy hostname, proxy port, proxy exclusion list.

Whenever I connect my phone to pc and type the command gnirehtet rt it starts the server and installs the file on my phone I get the vpn sign as well on my phone but I instantly get the notification from Gnirehtet on my phone that «Disconnected from relay server»

I’ve tried using multiple cables so its not the cable or the usb port

Is there a way to make it appear on opened apps so I can lock gnirehtet so it won’t get closed when I’m clearing RAM on my phone?

The last pre-compiled version for macOS was gnirehtet-rust-macos64-v2.2.1.zip (old release). The brew install of v.2.5 requires the entire rust package be installed, which «weighs» 912 MB!

The stand-alone gnirehtet-rust-macos64-v2.2.1 gnirehtet binary got the few rust libs/ deps which gnirehtet relies upon integrated during compile, which has it «weigh» only 1.1 MB. In other words, brew installs more than 900 MB of rusty junk, at least in regards to gnirehtet..

If someone knows how to build a stand-alone RUST version for macOS, please share. @rom1v I’m aware you set this project to inactive recently, but if you were so kind and share the steps how to build a Mac version which does not rely on tons of unused deps, it would be really appreciated 👍

Thank you.

On the latest version it seems like there are high latency / data transit problems. No idea what’s going wrong but the console does spam a bunch of «file not found» errors when it’s running

cho-m

In Homebrew, we currently need to rebuild gnirehtet due to an issue with our Linux pre-built binary, but all recent rebuild attempts result in a binary that doesn’t work correctly.

Doing some debugging locally, I noticed that the binary built with Rust 1.64.0 or 1.65.0 will error:

❯ gnirehtet relay
2022-12-01 18:27:56.744 INFO Main: Starting relay server on port 31416...
2022-12-01 18:27:56.745 ERROR Main: Execution error: IO error: Address family not supported by protocol family (os error 47)

Experimenting with a few different versions of Rust, I found that the last version that didn’t error was 1.63.0:

❯ gnirehtet relay
2022-12-01 18:34:53.803 INFO Main: Starting relay server on port 31416...
2022-12-01 18:34:53.804 INFO Relay: Relay server started

I assume gnirehtet is not compatible with changes introduced with new Rust versions.

I’m getting this error on my Narzo 50. The gnirehtet app is installed via cmd. The drivers for my phone is installed. What should I do?

Exception occurred while executing ‘start’:
java.lang.SecurityException: Permission Denial: starting Intent { act=com.genymobile.gnirehtet.START flg=0x10000000 cmp=com.genymobile.gnirehtet/.GnirehtetActivity mCallingUid=2000 } from null (pid=8565, uid=2000) requires android.permission.WRITE_SECURE_SETTINGS
at com.android.server.wm.ActivityTaskSupervisor.checkStartAnyActivityPermission(ActivityTaskSupervisor.java:1117)
at com.android.server.wm.ActivityStarter.executeRequest(ActivityStarter.java:1089)
at com.android.server.wm.ActivityStarter.execute(ActivityStarter.java:731)
at com.android.server.wm.ActivityTaskManagerService.startActivityAsUser(ActivityTaskManagerService.java:1266)
at com.android.server.wm.ActivityTaskManagerService.startActivityAsUser(ActivityTaskManagerService.java:1231)
at com.android.server.am.ActivityManagerService.startActivityAsUserWithFeature(ActivityManagerService.java:3177)
at com.android.server.am.ActivityManagerShellCommand.runStartActivity(ActivityManagerShellCommand.java:567)
at com.android.server.am.ActivityManagerShellCommand.onCommand(ActivityManagerShellCommand.java:198)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.server.am.ActivityManagerService.onShellCommand(ActivityManagerService.java:9350)
at android.os.Binder.shellCommand(Binder.java:970)
at android.os.Binder.onTransact(Binder.java:854)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:5240)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2702)
at android.os.Binder.execTransactInternal(Binder.java:1226)
at android.os.Binder.execTransact(Binder.java:1163)
2022-11-21 11:54:27.121 ERROR Main: Cannot start client: Command adb [«shell», «am», «start», «-a», «com.genymobile.gnirehtet.START», «-n», «com.genymobile.gnirehtet/.GnirehtetActivity»] returned with value -1

It works fine in general, however, when I disconnect the cable from the phone and plug the cable in the phone again, gnirehtet is not working most of the times. Then, I have to stop gnirehtet on my phone so that it can restart when plugin in again, after which it works again.

This is very inconvenient, since I unplug my phone constantly because I only plug the cable in the sync it. Any good workaround for this?

Flipp2

Please if you could help. I have reinstalled multiple times. Samsung A30 if anyone had/have any similar issues

adb: failed to install gnirehtet.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]

How can I fix this?

Version: 2.3 Java
Windows7 32bit — Xiaomi Redmi 8 64bit
7.09Gb free space in phone, 216Gb free space in computer. I can’t download apk to phone.
failure

yaggit

Starting: Intent { act=com.genymobile.gnirehtet.START cmp=com.genymobile.gnirehtet/.GnirehtetActivity }
java.lang.NullPointerException: Attempt to invoke virtual method ‘boolean java.lang.String.equals(java.lang.Object)’ on a null object reference
at android.os.Parcel.readException(Parcel.java:1552)
at android.os.Parcel.readException(Parcel.java:1499)
at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:2663)
at com.android.commands.am.Am.runStart(Am.java:766)
at com.android.commands.am.Am.onRun(Am.java:305)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:97)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)

Getting this error after installation.

hmffa

I add IP addresses for some domains manually in Windows host file and I want to make my cellphone use the IP in the list. Pinging the domain in CMD returns desired IP but in the cellphone not. I know that by default it uses Google DNS but by defining DNS using -d to 127.0.0.1 or localhost or even 10.0.2.2 did not work for me. What should I do exactly. Can you please help?

hello i tested gnirehtet in many devices and working as expected even some of these devices are xiaomi devices with miui 12.5 and miui 13

but when i tried to make it run on my redmi 9t miui 12.5 ,, it can only provide internet in browsers and very few noticed apps like youtube

even in play store it can provide internet but can’t download any app

also tested it in apps like facebook lite ,, telegram ,, plus messenger and not working in all those and other apps

although such apps like fb lite and plus messenger was working on other devices with gnirehtet

if any one can help me
thanks

Источник

Ответы 13

Другие вопросы по теме

Share Internet From PC To Android.

Ответы
13