Okay guys I was able to connect to adb on my phone via my non-hacked Chromebook Pro =D Here is how it's done (This will only work on chromebooks with android app support):
Enable Developer settings on your Chromebook's Android instance.
Enable adb debugging/Adb over network
Download GNURoot Debian from Play Store
Open GNURoot Debian, let it install
Run the following commands:
Code:
apt-get update
apt-get install android-tools-adb
apt-get install android-tools-fastboot
on your phone go to settings-> about phone -> status
Find your ip address and make a note of it
In the GNURoot terminal on your chromebook type the following command:
Code:
adb connect ipaddress
where ipaddress is the ip from earlier
Grant access when the prompt on your phone pops up
Done!
You cant activate adb if you are not on developer mode on chrome os
Related
I can get into console mode and mess about with some fedora commands but thats about it. Anyone feel free to take this further...
http://qole.org/files/fedora12-m5-v1a.img.ext2.lzma
Decompress with BitZipper and rename to fedora.img
http://www.mediafire.com/?9fw3vu463rs3vff fedboot
Place both files in sd card main directory and run in Terminal Emulator:
Code:
su
sh /sdcard/fedboot
After a few seconds [[email protected] root] should appear.
Code:
startx
is not a recognised command
Tried switching from Cli to GUI and changing runlevels using:
If you installed using a text login and wish to switch to a graphical login, follow this procedure.
If you are not already root, switch users to the root account:
su -
Provide the administrator password when prompted.
If you have not already done so, install the X Window System and a graphical desktop environment. For example, to install the GNOME desktop environment, use this command:
yum groupinstall "X Window System" "GNOME Desktop Environment"
To install the KDE desktop environment, use:
yum groupinstall "X Window System" KDE
To install the XFCE desktop environment, use:
yum groupinstall "X Window System" XFCE
This step may take some time as your Fedora system downloads and installs additional software. You may be asked to provide the installation media depending on your original installation source.
Run the following command to edit the /etc/inittab file:
vi /etc/inittab
Press the I key to enter insert mode.
Find the line that includes the text initdefault. Change the numeral 3 to 5.
Type :wq and press the Enter key to save the file and exit the vi text editor.
Reboot
Click to expand...
Click to collapse
But no luck after reboot.
Code:
su -c 'telinit 5'
Gives a communication refused message.
Hox do you make those versions? Where can I found a tutorial for learning how to make my versio of this (just for me).
Thanks
1. Linux(easy)
2. Mac(easy)
3. Windows(medium)
________________________________________________________
1. Linux
You don't need any special drivers for SDK on linux(adb shell), but you don't get fastboot binary in SDK package. To set fastboot for linux follow instructions:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot linux binary
http://www.mediafire.com/?ldlovlzi9mx3pbh
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
if you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it?
Copy this file to /etc/udev/rules.d
EDIT:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Easy?
______________________________________________________________
2. Mac
I don't have Mac, but it should be like for linux:
1. Download SDK(this isn't need if you want just fastboot)
http://developer.android.com/sdk/index.html
2. Download fastboot Mac binary:
http://www.mediafire.com/?kjozh1q5dyyqhn3
3. Copy it to your SDK directory
/path_to_your_SDK_directory/platform-tools
or
(I don't know that this is possible on Mac, try to change nautilus with Mac's default file browser?)If you use fastboot often and you don't want to type cd /path_to_your_SDK_directory/platform-tools, ./fastboot <action> every time, you can do this:
1. Open Terminal and type:
sudo nautilus
to get file browser with root privileges.
2. Copy fastboot binary to /bin directory
Now, just open terminal and type fastboot <action> and that's it? Easy?
______________________________________________________________
3. Windows
1. Download SDK
http://developer.android.com/sdk/index.html
2. Download Google USB Drivers from SDK Manager
3. After download, there're located in /path_to_your_SDK_directory/extras/google/usb_driver
4. Open android_winusb.inf and add this after [Google.NTx86] or [Google.NTamd64](32 bit or 64bit)
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
(Here is my modificated android_winusb.inf file here, but it's old and an updated version arrived from Google and it's compatible with 32bit and 64bit)
5. Open CMD from Start>Run and type:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
6. Reboot
==========================================================
7. On tablet go to Settings > Applications > Development and enable USB Debugging if it wasn't enabled and connect tablet with computer via USB.
8. Right-click on Computer and click Manage. Identify your device from the list(I think it's Tegra with board icon), right-click it and click Update Driver Software
9. Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer
10. Choose to view all devices and click Have Disk
11. Browse to the google-usb_driver folder inside your Android SDK folder(/path_to_your_SDK_directory/extras/google/usb_driver) and select the android_winusb.inf file
12. If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing
13. Once the drivers have been installed, you should be able to use ADB with your device
14. To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB
For fastboot you need to go to /path_to_your_SDK_directory/platform-tools in terminal(cd /path_to_your_SDK_directory/platform-tools) and type fastboot(.exe) <action> and before it to change ADB Interface to ADB
That's it, if you have some complaints, post them.
Bye!!!
EDIT: Changed android_winusb.inf file due error in it.
EDIT2:Changed android_winusb.inf file due error in it again.
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
shut the cmd say something ? because when i write the command and push enter its just jump to another line and says nothing ???
No. You can go to that file("%USERPROFILE%\.android\adb_usb.ini") and manualy add 0x955 to it.
Sorry!
I cannot connect to this link:http://www.mediafire.com/?kjozh1q5dyyqhn3
Please do me a favor, send fastboot as an attachment to this mail address:
[email protected]
I'll try because I'm not at home, I went to my grand parents and I have really slow internet.
Hello guys I have a problem, the step 5. Open CMD from Start> Run and type:
echo 0x955>> "% USERPROFILE% \. Android \ adb_usb.ini"
I run this step but I open a txt file that says this:
Android # USB Vendor ID 3RD PARTY LIST - DO NOT EDIT.
# USE 'adb Android update' TO GENERATE.
USB Vendor ID # 1 FOR LINE.
0x955
I now do not understand where I write echo 0x955?
/documents_and_settings/[your user name]/.Android(hidden file)/adb_usb.ini
Sent from my Xoom using Tapatalk
Nice guide. Think you forgot the udev rule for Linux:
Create a file called /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
Without that Linux won't give you write permission to the device.
Ok, I'll add.
Sent from my IDEOS S7 Slim using XDA App
So when I want to use fastboot, I install the Android Bootloader Interface driver? Not the ADB interface driver?
Needless to say I haven't got fastboot working yet but ADB works. One other thing: If I manage to install a firmware and do a wipe and everything works; can it be that I would experiance better performance if I as well managed to to a full wipe with fastboot? I mean, can it flush things that CWM can't? I'm using the latest cyanogenmod (test version) from DerArtem, but I am a bit interested in trying the latest progress of honeycomb...
I have problems with interfaces. On one computer is ADB interface and on other is something else but I prefer linux for doing any job that's connected with android. In theory wiping should be same with fastboot and recovery but, again, I prefer fastboot because it's JUST erase all on data/cache/system partition and recovery might don't have support for other partition types as well as other problems, but I don't say that it can be different.
Thanks. I hope I continue to have a functioning cwm. If it breaks I will have to install Linux
ı do everything but when ı wrote adb devices nothing
Linux or Windows?
Jon2555 said:
Linux or Windows?
Click to expand...
Click to collapse
windows 7 x64
When the tablet is open in USB Debugging mode I can see my device adb devices list but when ı restart my tablet fastboot mode ı can't find
The best slow to install Linux via VM. It complicated on windows, it's different from computer to computer.
Sent from my IDEOS S7 Slim using XDA App
do i type this exactly with all the " ???
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
????????????????/
HELP PLEASE
No
Sent from my IDEOS S7 Slim using XDA App
When i tipe the echo 0x955 line
It keeps on saying that system cannot find the path specified
can someone please help?
even when i open comand prompt and type adb it says adb is not recognised as an internal or external.........
I am writing a cmd script for my fire tv and am looking to see if there is a way for me to connect with the following
Code:
adb connect 192.168.1.5:5555
(the above command works)
but loop it if the device fails to connect, or wait/ retry until connect is successful... any help? sorry if explanation is not good
what my end goal is is to have a script running in the background that can start kodi when my fire tv stick starts
what I have that i can manually insert and it works to show my progress thus far, im a noob with this stuff BTW
Code:
adb kill-server
adb start-server
adb connect 192.168.1.5:5555
adb shell am force-stop org.xbmc.kodi
adb shell monkey -p org.xbmc.kodi 1
I could also use any tips on a way to check if kodi is running / or fireTV is on and pause / loop the code, any advice?
Hello, I'm new here.
I would like to ask you if someone has rooted this phone (Orange Rise 52 (Alcatel)) because it has 1GB RAM and with Orange carrier bloatware runs really slow and I would like to root it to remove all that software and maybe use as multimedia device or something like that.
How can I root this phone? What tools I need and steps must I take?
Regards and thanks for your time and patience!!
@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps
jwoegerbauer said:
@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps
Click to expand...
Click to collapse
@ jwoegerbauer Thanks, I will try it!!
jwoegerbauer said:
@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps
Click to expand...
Click to collapse
Hello, I installed both drivers but when I run adb devices it says "adb is not recognized as a internal or external command or bat"
Following the steps of manually installing driver I see some kind of warning in windows device management as you can check in this screenshot: https://ibb.co/gzVPbKQ
I tried to look for adb.exe but the one I found belongs to Xiaomi Mi9 phone which I used to remove Xiaomi Mi9 applications. I tried to run that adb executable but only detects Xiaomi phone and doesn't detect Orange Rise 52 phone.
What am I doing wrong?
EDITED: After installed those drivers, computer didn't recognize Xiaomi MI 9 phone, in some way destroyed Xiaomi Mi 9 drivers so even with system restore didn't work to recover a working Xiaomi Mi 9 connection so I had to restore a Aomei backup image so next try will be on a virtual machine where it doesn't affect these drivers installations to the ones I have or windows has. Is there any reason adb command is not working after installing adb usb driver for orange rise 52?
Regards and thanks.
knopfler1980 said:
Hello, I installed both drivers but when I run adb devices it says "adb is not recognized as a internal or external command or bat"
Following the steps of manually installing driver I see some kind of warning in windows device management as you can check in this screenshot: https://ibb.co/gzVPbKQ
I tried to look for adb.exe but the one I found belongs to Xiaomi Mi9 phone which I used to remove Xiaomi Mi9 applications. I tried to run that adb executable but only detects Xiaomi phone and doesn't detect Orange Rise 52 phone.
What am I doing wrong?
EDITED: After installed those drivers, computer didn't recognize Xiaomi MI 9 phone, in some way destroyed Xiaomi Mi 9 drivers so even with system restore didn't work to recover a working Xiaomi Mi 9 connection so I had to restore a Aomei backup image so next try will be on a virtual machine where it doesn't affect these drivers installations to the ones I have or windows has. Is there any reason adb command is not working after installing adb usb driver for orange rise 52?
Regards and thanks.
Click to expand...
Click to collapse
Sorry I didn't have usb debugging enabled. I will follow next steps, thanks a lot!!
knopfler1980 said:
Sorry I didn't have usb debugging enabled. I will follow next steps, thanks a lot!!
Click to expand...
Click to collapse
Hello again, I'm trying to reboot in fastboot but it doesn't work, phone boots normally.
I also tried a article I found that says you can also can start fastboot pressing up volume and power and stop pressing when bot appears but bot dissapears really fast that it's imposible stop pressing up and power, I only can see a menu in the phone that says recovery, is that fastboot? Also when I run command "fastboot devices" it doesn't detect anything because the phone didn't boot as fastboot using:
Up and power
adb reboot bootloader
Do you have any idea why is happening this?
I installed drivers from https://gsmusbdriver.com/orange-rise-52 but it doesn't seem to work with fastboot (computer detects it normally but not fastboot because I guess is not a driver problem but fastboot booting that is not happening)
Regards and thanks in advance!!
@knopfler1980
If no su binary is found on Android, then you have no root. So all you at least have to do is to install su binary in Android's /system partition. This can be achieved using ADB.
The command sequence is as follows
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
The su binary is downloadable from here: download it and extract the version that matches your phone's CPU-architecture to root of computer's drive C:
jwoegerbauer said:
@knopfler1980
If no su binary is found on Android, then you have no root. So all you at least have to do is to install su binary in Android's /system partition. This can be achieved using ADB.
The command sequence is as follows
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
The su binary is downloadable from here: download it and extract the version that matches your phone's CPU-architecture to root of computer's drive C:
Click to expand...
Click to collapse
Thanks for the help. I had a warning with the second step:
"Disable-verify" only works for userdebug builds
{
"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"
}
I will check on google.
Thanks a lot both for your support. I want to try sell my Xiaomi Mi 9 and Kospet Prime and buy a Ryzen 3900x and a motherboard, that's the reason I want to root the crap (sorry if someone has this phone) of Orange rise 52 because it's really slow.
Regards.
knopfler1980 said:
Thanks for the help. I had a warning with the second step:
"Disable-verify" only works for userdebug builds
I will check on google.
Thanks a lot both for your support. I want to try sell my Xiaomi Mi 9 and Kospet Prime and buy a Ryzen 3900x and a motherboard, that's the reason I want to root the crap (sorry if someone has this phone) of Orange rise 52 because it's really slow.
Regards.
Click to expand...
Click to collapse
I found this link https://stackoverflow.com/questions/38304435/how-to-enable-and-disable-dm-verity-on-android-devices that says:
"adb disable-verity will work only with adb version 1.0.33 and above. so upgrade your adb version"
So I'm going to try upgrade adb version in my virtual machine.
Thanks for the help guys!!
knopfler1980 said:
I found this link https://stackoverflow.com/questions/38304435/how-to-enable-and-disable-dm-verity-on-android-devices that says:
"adb disable-verity will work only with adb version 1.0.33 and above. so upgrade your adb version"
So I'm going to try upgrade adb version in my virtual machine.
Thanks for the help guys!!
Click to expand...
Click to collapse
Hi again.
I downloaded the latest SDK with latest adb version from here https://developer.android.com/studio/releases/platform-tools
I'm still getting the error
C:\platform-tools_r30.0.4-windows\platform-tools>adb disable-verity
disable-verity only works for userdebug builds
My adb version is as follows:
C:\platform-tools_r30.0.4-windows\platform-tools>adb version
Android Debug Bridge version 1.0.41
Version 30.0.4-6686687
Installed as C:\platform-tools_r30.0.4-windows\platform-tools\adb.exe
Is there anything else I'm not realizing?
Thanks in advance, I will keep searching.
Regards
knopfler1980 said:
Hi again.
...
I'm still getting the error
C:\platform-tools_r30.0.4-windows\platform-tools>adb disable-verity
disable-verity only works for userdebug builds
...
Click to expand...
Click to collapse
Signals that phone's Android isn't a user-debug build. Looks that phone's Android can't get rooted. But I'm not sure of this: all the phone's I had/have in use had/have a user-debug type Android OS.
FYI: You can query build type of your phone's Android OS
Code:
adb devices
adb shell "getprop ro.build.type"
BTW: Android OS comes as one of these 3 builds
eng - Engineering build comes with default root access.
user - User build is the one flashed on production phones. Has no root access.
user-debug - User debug build does not come with default root access but can be rooted.
jwoegerbauer said:
Signals that phone's Android isn't a user-debug build. Looks that phone's Android can't get rooted. But I'm not sure of this: all the phone's I had/have in use had/have a user-debug type Android OS.
FYI: You can query build type of your phone's Android OS
Code:
adb devices
adb shell "getprop ro.build.type"
BTW: Android OS comes as one of these 3 builds
eng - Engineering build comes with default root access.
user - User build is the one flashed on production phones. Has no root access.
user-debug - User debug build does not come with default root access but can be rooted.
Click to expand...
Click to collapse
Hi, thanks for your answer. I don't know what has happened but virtual machine is not detecting phone anymore, vmware workstation 15 pro problem. I was unable to see which's the problem. First started like 2 hours ago when physical machine without any changes didn't detect any of the phones, Xiaomi Mi 9 and Orange Rise 52. I checked windows device management and I saw that there was a problem with MTP driver, so I had to "update" (that's it's called in windows but I guess it installed it again) MTP driver for each phone. Now physical machine is detecting both but not vmware workstation 15 pro. I will keep checking it and I will try to run the command you adviced me.
In case Orange rise 52 is using a not compatible build, I will try again supersu method, but at the moment any of both will work until I get virtual machine detecting usb phone connection in VM -> Removable usb devices (it only appears 2 when I have 3 usb hard drives, one yubikey (hardware authentication) and identification card reader so it should detect 5 devices and it's only detecting 2).
Thanks for your time and help.
I have a Oneplus 8 with kali nethunter rooted with Termux installed.
I want to connect into the device using ssh over USB but something strange happen: ssh doesn't work if the device is offline, but if I connect the device to LAN once, the sshd service start to work.
So:
I plug the device with usb-c
open termux and set the password with `passwd`
install openssh
start sshd
Then:
Bash:
adb devices
# List of devices attached
# mserialnum00 device
adb forward tcp:8022 tcp:8022
ssh.exe -p 8022 localhost
This will work only if I connect the device at least once to the LAN.