Hello all, I have a little project I'd like some help on. I have recently bought an Alba 4 inch with android 7 (Nougat). I'd like to use this phone purely for SatNav work, but it appears that it doesn't like working the GPS without SIM or wireless. I have done some research and apparently, a few people have experienced a similar issue when updating from android 6 to 7. So I thought I'd root my 'Alba' and flash it back to 6 to see if that improves the GPS usage unless someone can tell me otherwise. It's quite maddening as I have an old Nokia Lumia 925 (Windows 8.1) which has no problem using the internal GPS device without wireless or SIM card - in fact, my old N8 and X6 have no problem at all and I still use those but software is now almost defunct. However, I'd like to pursue with the 'Alba' as I want to install OsmAnd or equivalent app and upload created gpx routes from my laptop, for me to use on my mountain bike or road bike. The reason I'm going for a fairly simple mobile, but should fit the bill, is that it can be charged while out in the wild with a basic solar power pack. My other phone the Honor 8 requires more than a simple solar pack....
Details of phone - Alba 4 3g (AC40AS3G / SKU133814622) with Archos android 7.
Steps taken...
'OneClickRoot' doesn't have a root app entry for my particular phone. Now I've done the build number trick, allowed usb debugging, got the PC authorised on the phone, installed android sdk on my Ubuntu 12.04 laptop and I can run adb and some commands:
'adb devices' creates:
[email protected]:~$ adb devices
List of devices attached
18643080980731 device
'adb shell' creates:
[email protected]:~$ adb shell
ac40as3g:/ $
'adb reboot bootloader' - gives a screen with 'fastboot mode' in the top left corner of the mobile.
'fastboot oem unlock' and 'fastboot flashing unlock- both give "< waiting for any device >" but no listing
'fastboot devices' - this then produces "no permissions (user in plugdev group; are your udev rules wrong?); see [developer website] "
My lsusb command produces this, with phone connected in normal mode:
userATlaptop:~$ lsusb
Bus 002 Device 004: ID 0e79:5604 Archos, Inc.
Bus 008 Device 002: ID 8086:0189 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
My 51-android.rules file contains :
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666", GROUP="plugdev"
I also have a custom rule called '70-abdroid-custom-device.rules' which I created from some 'googled' page...
# Archos 4
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5609", TAG+="uaccess"
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", ATTRS{idProduct}=="5604", TAG+="uaccess"
'fastboot flashing get_unlock_ability' - this produces "< waiting for any device >" but nothing.
So questions are:
Have I got my udev right?
What would be the next step after correcting the first question?
...any other suggestions? Apart from 'throw it in the bin...' thanks.
Related
Not really a development question, but I still think this section of the forum suites best.
My device (Acer A500 tab) is not recognized by Eclipse when I plug it in via USB (USB debugging is set, ofc). It is, however, recognized by OS as a valid USB device - I can see it with lsusb.
Any suggestions?
Thanks in advance.
P.S. I never had such a problem on Windows. I can't beleive Linux cannot be use for development.
Sorry, my bad. The device couldn't connect via USB because it was already connected over Wi-Fi, and I forgot about it
Please close the topis.
Connecting via USB to Linux (Ubuntu)
I could not get my Ubuntu machines to recognize the tablet when I plugged in the USB cable. Bummer.
Digging around I found a similar issue experienced by Xoom owners. The original article describing the fix is here. The steps listed there are for the Xoom, not the Acer, although the fix is almost the same.
I am posting the slightly modified instructions again here for clarity and brevity.
I did this fix on both Ubuntu 10.10 (Maverick) and 11.04 (Natty). Your mileage may vary.
1. Get the mtpfs package installed on your machine.
Code:
sudo apt-get install mtpfs
2. In the tablet, go to Settings->Applications->Development and turn USB Debugging on (check the box). For me, this was required for file transfers to work.
3. Plug your USB cable into the tablet and your Ubuntu machine.
4. Open your Terminal app on the Ubuntu machine.
5. Use the lsusb command to get the vendor id. Type "lsusb" in Terminal.
6. The output should look something like this:
Code:
[email protected]:~$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 006: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 003 Device 005: ID 05af:0802 Jing-Mold Enterprise Co., Ltd
Bus 003 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0502:3325 Acer, Inc.
Bus 001 Device 003: ID 04f2:b16b Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The line with "Acer, Inc." in it tells you the VendorID. In the example above, it's 0502.
** Disconnect the USB cable at this point **
7. Create a UDEV rule file. Use your editor of choice, mine is nano.
Code:
sudo nano /etc/udev/rules.d/51-android.rules
The file should contain this line when you are finished:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
8. Create a mount point and make yourself the owner.
Code:
sudo mkdir /media/a500
sudo chown user:user /media/a500
IMPORTANT: Replace user:user with your user name and default group on your Ubuntu machine. For most people it will be your login name. If your login is "bob", then replace user:user with bob:bob, capice?
9. Add the mount point to fstab.
Code:
sudo nano /etc/fstab
At the bottom of the file, type this stuff:
Code:
# mount point for Acer A500
mtpfs /media/a500 fuse user,noauto,allow_other 0 0
10. Modify fuse.conf. Uncomment user_allow_other.
Code:
sudo nano /etc/fuse.conf
Look for #user_allow_other and remove the #.
11. Add yourself to the fuse group.
Code:
sudo nano /etc/group
Look for the line starting with "fuse" and put your login at the end of that line (if it's not already there).
12. Reboot.
You should see your mount point in Nautilus when you open it. After plugging in the USB cable, you can click the a500 entry under Places to mount the tablet.
Hi guys,
I have used the following tutorials:
http://forum.xda-developers.com/showthread.php?t=735375
http://forum.xda-developers.com/showthread.php?t=921169&page=2
But still when I type "./adb devices" or "sudo ./adb devices" all I get is "List of aevices attached" followed by a blank. Do you know a way to fix this?
I'm using a Samsung Galaxy Tab.
Thanks in advance.
Could you paste your dmesg? What's your OS?
Could you paste your 51-android.rules and output of lsusb?
My OS is Ubuntu 11.10
The output of lsusb is:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:5c11 Hewlett-Packard PhotoSmart C4200 Printer series
Bus 003 Device 002: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000
Bus 006 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 006 Device 003: ID 045e:0730 Microsoft Corp.
Bus 002 Device 005: ID 04e8:6877 Samsung Electronics Co., Ltd
Click to expand...
Click to collapse
The 51-android-rules file contains
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
Click to expand...
Click to collapse
Are you using the stock USB cable that came with your tablet? Is the cable in good shape?
I had a Samsung device that would not show up under my devices in Ubuntu. I later discovered it was because my cable was damaged internally. It charged, but had trouble connecting for data.
Is there any way this could be the issue?
adb driver
are you sure you have install the adb driver ?
The vendor id in your udev file is the HTC vendor id.. you should use the samsung one: 04e8
Besides, you can just try:
adb kill-server
and then:
sudo adb start-server
and see if you can get your device listed
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="users"
Click to expand...
Click to collapse
My lsusb while telephone connected in MTP:
[email protected]:~> lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 006 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 021: ID 0fce:0167 Sony Ericsson Mobile Communications AB
[email protected]:~>
Click to expand...
Click to collapse
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.
RudahXimenes said:
Hello, dear.
I have installed the CM 10 rom from FXP, and I have found some bugs.
I don't know what should I do, so I am creating this thread. If I am wrong, please, excuse me and tell me.
So, in FPX 151, I don't have access to my SDCard while I connect my telphone in my notebook, that is OpenSuSE Linux. Before this version, my SDCard was connecting correctly.
Ps.: In Windows operating system I can open my SD.
Ps².: Maybe is a OS unrecognizing, but I already do the udev rules correctly.
/etc/udev/rules.d/51-android.rules
My lsusb while telephone connected in MTP:
The other bug I found occur just in my ST15 and it's occuring in all releases after FX152. I haven't tested the FX152, but all releases until the FX207, my telephone doesn't start the WiFi.
When I try to start my WiFi, I get the message that is starting, but still ever there. Maybe it's a kernel bug.
Can someone help me?
Regards,
Rudah Ximenes.
Click to expand...
Click to collapse
Hi
I can't help you with the linux stuff, but I can help you with the wifi!
[INDEX] ROMs, KERNELS, FTFs, TOOLKITS and GUIDES - http://forum.xda-developers.com/showthread.php?t=2148684
Check out this list of all the kernels,
find the kernel you use,
go to thread , find modules,
flash modules in [cwm, twrp], ??????, click thanks after rebooting the phone:fingers-crossed:
Hi
I have installed Arch Linux but cannot find suitable material on setting up drivers and utilities for flashing rom on Linux specifically arch linux.
I can setup arch even if instructions are available for other distro Linux Mint and Ubuntu so any link can come in handy.
I was using flashtool in windows but after shifting to Arch, I am not sure whats the right procedure to do it.
I have unlocked bootloader and rooted rom (FXP kernel + MIUI) installed as of now which I want to change asap.
Please help.
Regards
Hello,
You don't need any drivers,just install android-udev and android-sdk-platform-tools for adb and fastboot (both from aur).
Download latest flastool and run it from the terminal just like you do in windows (it requires jre and libusbx from official repos ).
Ok I have reinstalled fatsboot, android-sdk-platform-tools and openjre
Now I still cannot use fastboot devices , its list nothing.
Also since I should have adb available (from sdk-platform) when I run adb it says no command ?
Code:
[[email protected] fastboot]$ fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo adb
sudo: adb: command not found
[[email protected] fastboot]$ adb
bash: adb: command not found
I have also installed udev-android , previous I created 51-android.rules manually but still doesnt work.
fastboot won't list the devices nor it works.
Code:
[sha[email protected] fastboot]$ lsusb
Bus 002 Device 005: ID 413c:2107 Dell Computer Corp.
Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0fce:5146 Sony Ericsson Mobile Communications AB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First of all make sure you have enabled usb debugging on your phone.Adb and fastboot should be under /opt/android-sdk/platform-tools/ and also 51-android.rules file in /usr/lib/udev/rules.d/ (with -rw-r--r-- permissions).
With these things i have everything in my sytem to flash roms etc,maybe you're missing something with your installation.
Also for more information check wiki from archlinux wiki.archlinux.org/index.php/android
Hi,
I guess I brought myself into trouble today.
I have an alldaymall A88S 8GB tablet which I have bought on eb*y. Today I sent a "adb reboot bootloader" to it. That resulted in a mode where a little green robot is visible in the middle of the screen.
Now I can't power down the device. Pressing the power button results into a dark screen and then the green robot again. Power+Vol leads to the same.
Adb and fastboot show no device. lsusb still lists the device.
Any suggestions?
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
theodleif said:
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
Click to expand...
Click to collapse
Thanks man! This really helped. I was stuck for couple of hours.
My Mediacom SmartPad Go MP726GOG was stuck after issuing "adb reboot bootloader". My vendor device was the same as yours (1f3a), but in case someone else is stuck, you can check the connected devices (on linux, at least) with the command lsusb.
Code:
$ lsusb
Bus 007 Device 047: ID 1f3a:1010 Onda (unverified)
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0cf2:6230 ENE Technology, Inc. SD Card Reader (UB623X)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 09da:0260 A4Tech Co., Ltd. KV-300H Isolation Keyboard
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 09da:9090 A4Tech Co., Ltd. XL-730K / XL-750BK / XL-755BK Mice
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
where you can see the onda device with id 1f3a:1010.
There should also be a windows specific way to get the vendor id, probably device manager or similar, but I am not familiar with windows.
Cheers!
Need Firmware for this unit any help
alldaymall model:A88S
A33