please choosego to mobile | Continue to access the PC version
View: 19578|Reply: 27

OrangePi 2G-IOT: ADB mode(Under Android OS)

[Copy link]

10

threads

35

posts

305

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
305
Published in 2017-4-24 15:22:07 | Show all floors |Read mode
OrangePi 2G-IOT support ADB mode, it's helpful on non-screen mode.

So this section will introduce how to use adb on OrangePi 2G-IOT.
Note! OrangePi 2G-IOT can't support "USB host" and "OTG" at the same time.


First of all, change swith to select 'adb' mode, as follow:
The "1234" are "UP" and "5678" are "DOWN"


Then, configure adb on Linux or Windows.
If you haven't configure adb on your machine, please refer article on web.

Connect OrangePi 2G-IOT to PC with usb-cable


Next, use adb command to connect.
  1. adb devices
  2. adb root
  3. adb shell
Copy code

The last, utilize "Vysor" from chrome plug-in.
More article introduce how to install "Vysor" on Linux or Windows.





This thread contains more resources

You need to Log in to download or view,No account?    Register

x

1

threads

8

posts

27

credits

Novice

Rank: 1

credits
27
Published in 2017-5-9 16:57:33 | Show all floors
daca11 replied at 2017-5-4 01:18
Well... it seems that it's not working for me... I have the pin in nand mode, the switches as indi ...

"Stock" 2G-IoT NAND Android (at least for boards shipped in April) comes with Development ->USB debug option disabled.
It is kinda tricky to enable it with serial connection and manual edit of filesystem files - but is possible.



0

threads

3

posts

45

credits

Novice

Rank: 1

credits
45
Published in 2017-4-28 17:58:23 | Show all floors
Hi,

thanks in advance for the information.
I have a couple of questions:
1) The board comes with a ROM in the internal NAND already for use or I need to flash it first?
2) The default WIFI "OrangePi" are configurated in Android OS, Armbian and Debian Server?

Thanks!

1

threads

3

posts

27

credits

Novice

Rank: 1

credits
27
Published in 2017-5-4 01:18:08 | Show all floors
Edited by daca11 at 2017-5-4 01:20
  1. C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
  2. List of devices attached


  3. C:\Program Files (x86)\Minimal ADB and Fastboot>adb root
  4. adb: unable to connect for root: no devices/emulators found

  5. C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
  6. error: no devices/emulators found
Copy code


Well... it seems that it's not working for me... I have the pin in nand mode, the switches as indicated in the post it's and connected to the computer by the micro-usb (which gives power to it too). The board has a red light on though...And I can hear the "device connected" sound in windows, but nothing appears in the windows explorer, neither in the device administrator (only "Android ADB interface")

0

threads

1

posts

10

credits

Novice

Rank: 1

credits
10
Published in 2017-6-7 22:58:23 | Show all floors
xkremator replied at 2017-5-9 16:57
"Stock" 2G-IoT NAND Android (at least for boards shipped in April) comes with Development ->USB de ...

how did you do it?

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-4 17:12:55 | Show all floors
Any update about this ? I am facing the same problem.

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-9 13:44:29 | Show all floors
I am using the latest firmware, the board is recognized in windows 7 as Google Nexus 7 ADB Interface. Command line "ADB Devices" result in empty list of "List of devices attached". Any help ?

0

threads

5

posts

36

credits

Novice

Rank: 1

credits
36
Published in 2017-8-10 03:17:20 | Show all floors
xkremator replied at 2017-5-9 16:57
"Stock" 2G-IoT NAND Android (at least for boards shipped in April) comes with Development ->USB de ...

I have the same problem.
Connect the usb OTG to my windows PC and only appear RDA Phone like MTP device. Try to enable the USB debugging connecting to TTL debug pins with and TTL-USB cable like user manual show and i followed this steps:
Let it be simple (root possibly[1] required):
settings put global development_settings_enabled 1settings put global adb_enabled 1And then you need to
echo "mtp,adb" > /data/property/persist.sys.usb.config

(https://android.stackexchange.co ... -using-command-line)

Then i have luck and automatically appears an ADB interface in the device manager, the Vysor app detect the phone but when i try to connect says me something related with the RSA verification. If i could view the display then i could easily tap on YES to authorize the device, but i have not an screen.
Also i tried to reboot the board and after this, the Android doesn't boot anymore, in a few hour i can post the log. Even i try to update the Android NAND but i have not luck with that.
The steps I followed are:
1) Download and install tool, drivers and Android NAND bin.
2) Set jumper cap to boot from NAND and toggle switch 1234 UP 5678 DOWN.
3) In the writing tool, load bin image and press "Download", the soft says that wait for download link.
4) Connect with an USB cable the OTG port with the PC.
5) Push the power button for 5 seconds
6) And nothing happens.

Why have they disabled the USB debbuging from default?
I have not had a good start with this board. Hope i can make it work.
Regards!

0

threads

5

posts

36

credits

Novice

Rank: 1

credits
36
Published in 2017-8-10 03:25:27 | Show all floors
batojay replied at 2017-8-9 13:44
I am using the latest firmware, the board is recognized in windows 7 as Google Nexus 7 ADB Interface ...

You have the USB debugging enable or have you had to enable it?
Have you tried installing different drivers?
This installer has good references: 15 seconds ADB Installer
https://forum.xda-developers.com/showthread.php?t=2588979
Good luck!

0

threads

7

posts

48

credits

Novice

Rank: 1

credits
48
Published in 2017-8-10 10:06:24 | Show all floors
Edited by batojay at 2017-8-10 10:07
gtrangoni replied at 2017-8-10 03:25
You have the USB debugging enable or have you had to enable it?
Have you tried installing differen ...

It was enabled by default in the new firmware, although before that I took the same steps as you did for the old firmware (before upgrading to the new one, unfortunately I had no lcd screen back then so cannot verify the key). Now I have the lcd screen but problem with the adb. I tried the ADB installer but it did not recognize the phone. I will try a few different things & will let you know the results.
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list