Archos 101 g9 8gb & Huawei modem E173u-1[No driver found] - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Hi, I am having issues with a Huawei modem E173u-1 on my tablet Archos 101 g9 8gb
driver not found.
Can you help me, pls?
USB_ModeSwitch log from Wed Apr 09 17:50:44 PKT 2014
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HUAWEI
product HUAWEI Mobile
serial
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/12d1.14fe
! matched. Reading config data
devList 1:
config: TargetVendor set to 12d1
config: TargetProduct set to 1506
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 12d1 -p 14fe -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x12d1
DefaultProduct= 0x14fe
TargetVendor= 0x12d1
TargetProduct= 0x1506
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456780000000000000011062000000100000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 12d1:14fe
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HUAWEI
Product: HUAWEI Mobile
Serial No.: not provided
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x01
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Waiting for device file system (2 sec.) ...
Waiting for device file system (3 sec.) ...
Waiting for device file system (4 sec.) ...
Waiting for device file system (5 sec.) ...
Waiting for device file system (6 sec.) ...
Waiting for device file system (7 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 12d1:1506 (HUAWEI: HUAWEI Mobile)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /sbin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /lib/modules/usb_wwan.ko
Error: insmod: cannot insert '/lib/modules/usb_wwan.ko': Invalid module format (-1): Exec
format error
Loading main driver module "option"
Error: insmod: cannot insert '/lib/modules/option.ko': Invalid module format (-1): Exec
format error
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding seems to have failed
All done, exiting
please answer!!!

i'm solved the problem by replacing the nucleus

Related

[Problem] USB Dongle ZTE MF190 - modeswitch fail

Hi ... ive got the O2 ZTE MF190 USB Dongle .... but when i use the [HowTo] from "nenadr" -> http://forum.xda-developers.com/showthread.php?t=940470
I tried many things but everytime after the "/system/xbin/3Gmodem_detect.sh" command it looks like this :
# su
# /system/xbin/3Gmodem_detect.sh
Supported USB device found !!!! VendorID: 19d2 - ProductID: 0083
New VendorID: 19d2
New ProductID: 0124
Switching device to usbserial mode !
Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 004 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached
SCSI inquiry data (for identification)
-------------------------
Vendor String: ZTE
Model String: USB SCSI CD-ROM
Revision String: 2.31
-------------------------
USB description data (for identification)
-------------------------
Manufacturer: ZTE,Incorporated
Product: ZTE WCDMA Technologies MSM
Serial No.: P671A2TMED010000
-------------------------
Setting up communication with interface 0 ...
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to the message (CSW) ...
OK, response successfully read (13 bytes).
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Checking for mode switch (max. 20 times, once per second) ...
Waiting for original device to vanish ...
Original device can't be accessed anymore. Good.
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
Searching for target devices ...
No new devices in target mode or class found
Mode switch has failed. Bye.
3Gmodem_detect.sh didn't found USB device of adequate Vendor and Product after switching. Exitig.
#
Click to expand...
Click to collapse
Ive Root & Use the Uruk 1.64 RC Kernel ...
Cant post in the Original Threat cause i dont have the accsess.
Maybe someone had a same Problem ... :/

[Q] MTP installation on debian doesn't work

Hello,
I've compiled the latest version of libmtp (1.1.2) and installed properly. It seems that the device is recognized but still without the ability to connect to it. Here is the log. I got two different outputs. So I'll post both of them:
1.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 12
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
2.
Code:
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 13
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
I've read about a samsung-proprietary mtp protocol which would not work with libmtp. I hope those rumors are wrong, aren't they?
I'd really appreciate any help. I've been working on it for a couple of days and it starts really anoying me.
regards, hornby
I have the same issue. I am trying to connect my Linux Mint Debian machine to my SGS2 running CM9 nightly. Debian can see the device but communication is a nogo.
Here is mtp-detect:
Code:
~ $ mtp-detect
libmtp version: 1.1.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
ignoring usb_claim_interface = -110Android device detected, assigning default bug flags
USB low-level info:
Using kernel interface "usbfs"
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 04e8
idProduct: 6860
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 9
Device entry info:
Vendor: Samsung
Vendor id: 0x04e8
Product: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus
Vendor id: 0x6860
Device flags: 0x08008106
Device info:
Manufacturer: samsung
Model: GT-I9100
Device version: 1.0
Serial number: ????????
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Unknown (95c1)
95c2: Unknown (95c2)
95c3: Unknown (95c3)
95c4: Unknown (95c4)
95c5: Unknown (95c5)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
3001: Association/Directory
3004: Text
3005: HTML
3008: MS Wave
3009: MP3
300b: MPEG
3801: JPEG
3802: TIFF EP
3807: GIF
3808: JFIF
380b: PNG
380d: TIFF
b901: WMA
b902: OGG
b903: AAC
b982: MP4
b983: MP2
b984: 3GP
ba05: Abstract Audio Video Playlist
ba10: WPL Playlist
ba11: M3U Playlist
ba14: PLS Playlist
ba82: XMLDocument
b906: FLAC
Storage Devices:
StorageID: 0x00010001
StorageType: 0x0003 fixed RAM storage
FilesystemType: 0x0002 generic hierarchical
AccessCapability: 0x0000 read/write
MaxCapacity: 12332314624
FreeSpaceInBytes: 6137163776
FreeSpaceInObjects: 1073741824
StorageDescription: Internal Storage
VolumeIdentifier: (null)
Special directories:
Default music folder: 0x0000001a
Default playlist folder: 0xffffffff
Default picture folder: 0x0000001f
Default video folder: 0xffffffff
Default organizer folder: 0xffffffff
Default zencast folder: 0xffffffff
Default album folder: 0xffffffff
Default text folder: 0xffffffff
MTP-specific device properties:
Friendly name: (NULL)
Synchronization partner: (NULL)
libmtp supported (playable) filetypes:
Folder
Text file
HTML file
RIFF WAVE file
ISO MPEG-1 Audio Layer 3
MPEG video stream
JPEG file
GIF bitmap file
JFIF file
Portable Network Graphics
TIFF bitmap file
Microsoft Windows Media Audio
Ogg container format
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
ISO MPEG-1 Audio Layer 2
Abstract Playlist file
XML file
Free Lossless Audio Codec (FLAC)
ERROR: Could not close session!
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
OK.

[Q] updated to 4.0.4 Bionic cant be found by adb on osx

1st I'm a noob, so be kind. After getting the 4.0.4 update pushed from Verizon, my Motorola Bionic has disappeared from adb radar. terminal command "adb devices" returns nothing under list of devices attached, when its usb connected. (I've updated my android sdks. to latest platform tools).
I have tried each of the 3 usb settings 4.0.4 offers (Mass Storage, Media Device(MTP) and Camera (PTP), with debugging both on and off. Still no joy. I have killed and started adb server and rebooted both the macbook pro and the bionic. BTW - the original android os it started with had a "Charge Only" mode, which was the usb connection type that adb connection had previously required, but that's gone from this 4.0.4 upgrade for some reason. I have searched numerous forums and threads, but haven't found anything that seems to specifically apply to what i'm encountering. Those forums that did have posts about adb not finding connected device, mostly suggested rebooting and updated sdks. A couple suggested editing some config files, but I couldn't locate those. Any and all suggestions/solutions will be gratefully attempted. Thanks in advance for your analysis.
I'm running osx lion 10.7.5 on a MacBook Pro. I can provide phone system info if necessary. I've copied below the info I've gathered about the usb port the device is connected to from USB Prober.
Using usb prober the device appears as "Composit device: "XT875" in the bus probe. Port Info shows as: 0x1018, not captive, external device, connected, enabled. Device Descriptor shows as: Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x22B8/0x4353 (Motorola MDS)
Device Version Number: 0x0216
Number of Configurations: 1
Manufacturer String: 2 "Motorola"
Product String: 3 "XT875"
Serial Number String: 4 "0A3BAA470C01100C"
Interfaces show as: Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Device Qualifier Descriptor
Descriptor Version Number: 0x0200
Device Class 0 (Composite)
Device Subclass 0
Device Protocol 0
Device MaxPacketSize: 64
Number of Configurations: 1
bReserved: 0
Other Speed Configuration Descriptor
Length (and contents): 69
Number of Interfaces: 2
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 500 ma
Interface #0 - Vendor-specific .............................................. "MTP"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 255 (Vendor-specific)
Interface Subclass; 255 (Vendor-specific)
Interface Protocol: 0
Endpoint 0x81 - Bulk Input
Endpoint 0x02 - Bulk Output
Endpoint 0x82 - Interrupt Input
Interface #1 - Communications-Control .............................................. "Motorola Networking Interface"
Alternate Setting 0
Number of Endpoints 3
Interface Class: 2 (Communications-Control)
Interface Subclass; 10
Interface Protocol: 1
Endpoint 0x83 - Bulk Input
Endpoint 0x03 - Bulk Output
Endpoint 0x04 - Interrupt Output
Same issue
I am trying to root a Bionic running 4.0.4 and it is having the same issue with the ADB driver. Using the same computer and a rooted razr, the ADB drivers show up as soon as it is pluged in. Any help with this matter would be a big help.

[Q] chroot + framebuffer [Ainol Fire][Android 4.0.4]

Hi, I'm trying to force Xorg to use /dev/grapgics/fb0 of android. Android's /dev is binded to chroot's /dev.
When I run "cat /dev/urandom > /dev/graphics/fb0" in chroot I see random color pixels on screen, but I can't setup Xorg to properly to use fb0.
I'm using "setprop ctl.stop media && setprop ctl.stop zygote" to kill Android ui to avoid using fb0. After starting Xorg i cant see any changes on screen.
[device: Ainol Fire, A4.0.4(feiyu), Mali400Mp2, 1280x800]
Any ideas what im doing wrong?
Xorg.conf:
Code:
Section "ServerLayout"
Identifier "Default"
Screen 0 "Default Screen" 0 0
# InputDevice "Touchscreen" "CorePointer"
EndSection
#Section "InputDevice"
# Identifier "Touchscreen"
# Driver "tslib"
# Option "Device" "/dev/input/event5"
#EndSection
Section "Device"
Identifier "Configured Video Device"
Driver "fbdev"
Option "fbdev" "/dev/graphics/fb0"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
DisplaySize 1280 800
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
EndSection
Section "ServerFlags"
Option "DefaultServerLayout" "Default"
Xorg log on pastebin: "Wngrb9D7" (I can't post url)
Hi, on my Samsung Galaxy Tab 2 10.1" I have a running X11 with this config.
Code:
[email protected]:/# cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "Layout0"
Screen "Screen0"
#InputDevice "Mouse0" "CorePointer"
InputDevice "cyttsp-i2c" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
#Option "Device" "/dev/input/event7"
Option "Device" "/dev/input/event9"
Option "Protocol" "usb"
EndSection
Section "InputDevice"
Identifier "Mouse0"
#Driver "evdev"
Driver "mouse"
Option "Protocol" "IMPS/2"
#Option "Device" "/dev/input/event0"
Option "Device" "/dev/input/mice"
#Option "Protocol" "usb"
EndSection
Section "InputDevice"
Identifier "cyttsp-i2c"
Driver "multitouch"
Option "Device" "/dev/input/event0"
# mouse should move as fast as finger and not faster
Option "AccelerationScheme" "none"
# evdev has it, multitouch doesn't so it behaves like touchpad
# Option "IgnoreRelativeAxes" "True"
EndSection
Section "Device"
Identifier "Card0"
Driver "fbdev"
Option "fbdev" "/dev/graphics/fb0"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x600_60.00"
EndSubSection
EndSection
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection
I hope it helps
I tried with conf like this and still is something wrong, can you post xorg.conf.d conf files and xorg.0.log? (or pm)
AW: [Q] chroot + framebuffer [Ainol Fire][Android 4.0.4]
Try to shutdown surfaceflinger with:
setprop ctl.stop surfaceflinger
May thats the problem...
Sent from my GT-S5830 using xda app-developers app
Only screen frezee, nothing changed on screen/buffer like a xorg cant acces to fb (im pretty sure about this). In log I cant see anything about fbdevhw, maybe it is related to problem?
//edit
On gt540 (Android 2.3.7) it works without killing android, screen goes black and xorg starts successfully, but msm7227 needs something to refresh screen (i can see desktop when im killing xorg and zygote+media gets back framebuffer). So is there any other part of android (killed zygote, media, drm, surfaceflinger) using framebuffer in Android 4.0.4 ?
//edit
Partial success, xorg is using framebuffer, but there is an errror
Anybody know how to fix it?
Code:
[[email protected] /]# xinit -- :0 ttyS0 vt1 -verbose
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.13.2.901 (1.13.3 RC 1)
Release Date: 2013-02-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.34-1-FARM armv7l
Current Operating System: Linux localhost 3.0.8 #3 SMP PREEMPT Wed Nov 14 11:26:15 CST 2012 armv7l
Kernel command line: init=/init console=ttyS0,115200n8 hlt no_console_suspend vmalloc=256m mem=1024m logo=osd1,loaded,panel,debug hdmitx=vdacoff,powermode1,unplug_powerdown a9_clk_max=1512000000
Build Date: 24 February 2013 12:25:58AM
Current version of pixman: 0.28.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 11 09:08:09 2013
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(**) ServerLayout "Layout0"
(**) |-->Screen "DefaultScreen" (0)
(**) | |-->Monitor "Configured Monitor"
(**) | |-->Device "Mali FBDEV"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Automatically adding GPU devices
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/OTF/" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/Type1/" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
(==) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is disabled
(**) Extension "RENDER" is enabled
(II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.13.2.901, module version = 1.0.0
(==) AIGLX enabled
Loading extension GLX
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.13.0, module version = 0.4.3
(II) FBDEV: driver for framebuffer: fbdev
(++) using VT number 1
(WW) Falling back to old probe method for fbdev
(II) Loading /usr/lib/xorg/modules/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.13.2.901, module version = 0.0.2
(II) FBDEV(0): using /dev/graphics/fb0
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(**) FBDEV(0): Depth 32, (--) framebuffer bpp 32
(EE) FBDEV(0): Weight given (000) is inconsistent with the depth (32)
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
[[email protected] /]#
So it works (24bit depth), touch as touchpad, usb keyboard/mouse works too (only if connected before startx).
And first time i get sound working in chroot (visible as pcm card) but works only with rhytmbox playing mp3 stream, when i try to play mp3 file i get gstreamer backend error (not enough data). Sound works too with flash player (10.1).
I have the same tab as you (ainol fire, F-0506 A4.2.2) and want to get ubuntu working on my device. I faced with the same problem: Xorg don't want work with my fb0. So I want know: how you solved this problem?
Sorry for my bad English
EDIT
Framebuffer works, I can see some parts of full picture, but not full. I use gnome environment and all i see is mouse pointer that doesn't respond and Hide all buttom in left bottom corner. What I am doing wrong?
EDIT
Yes, I completely right, fb works, but with lags. I don't know why.. may be this lag is in cause of using new feiyu's kernel.. I take a photo of screen but I can't show them.
Also after I choose (I MADE IT!) Shut down - my fire freeze & I can't doing anything except restart my device.

Vivo 1901 SP Flash Tools ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142)

Hello guys,
I am trying to bring back to life a dead Vivo 1901 (V15) phone using SP Flash Tools v5.2036. The Firmware I am using comes in a file named, "Vivo_Y15_PD1901BF_MT6765_EX_A_1.12.4_11062019_(by_vivofirmware.com)",
which also provides MT6765 scatter file.
The auth file, scatter file and DA file that I am using for flashing is attached with this post. Upon selecting these files and flashing ( first tried with download only, then using format all + download, but results are same), I the following messages appear in the output of the tool.
Code:
$ sudo sh flash_tool.sh
[sudo] password for sarkar4540:
sysname:Linux
nodename:sarkar4540-X556UQK
release:5.4.0-49-generic
version:#53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020
machine:x86_64
domainame:(none)
cur_kernel_version = 5.4.0
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xc00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0
add@/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2
[email protected]/module/cdc_acm
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 0003
device pid = 0003
com portName is: /dev/ttyACM0
Total wait time = -1601887002.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_SHUTDOWN_CMD_EXCEPTION(-1073414142)
Disconnect!
BROM Exception! ( ERROR : STATUS_SHUTDOWN_CMD_EXCEPTION (-1073414142) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,149))
Following are the outputs of various commands in the system I am using.
Code:
$ uname -a
Linux sarkar4540-X556UQK 5.4.0-49-generic #53~18.04.1-Ubuntu SMP Mon Sep 21 14:12:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Code:
$ dmesg
.
.
.
[ 324.046688] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[ 324.195603] usb 1-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00
[ 324.195605] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 324.248243] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[ 324.249509] usbcore: registered new interface driver cdc_acm
[ 324.249510] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 324.275093] usbcore: registered new interface driver usbserial_generic
[ 324.275106] usbserial: USB Serial support registered for generic
[ 324.300238] usbcore: registered new interface driver option
[ 324.300261] usbserial: USB Serial support registered for GSM modem (1-port)
I request you guys to please show me where to head. I shall always be grateful to you if you can help me out of this misery.
Regards,
A. Sarkar

Categories

Resources