Hello!
I've found this thread :
http://forum.xda-developers.com/showthread.php?t=1274656
And i can't find anything like it for the Sony Tablet S.
There's any way to install those drivers in the Sony S and make that work?
Has anyone tried to use an USB to Ethernet Adapter with the Sony S?, i've a male microUSB to Female USB and several USB to Ethernet adapters from several brands, and i can't make it work with the Sony Tablet S.
When i connect them, it says : "Unsupported USB Device".
Any help is highly appreciated, i tried to post in the developers forum (I'm a Software Developer), but it didn't let me since i don't have enough posts.
Thanks !
To my knowledge, the Sony does not support the USB to Ethernet adapter solution, but I can't be certain of this. Without opening it up, I couldn't say for sure whether the hardware is present to attach a wired Ethernet connection. With Sony's history, that seems unlikely. The USB port would need to be connected to the network module in just the right way to support one of those adapters and then you could try drivers, but I don't think they'd work either
I tried it
It does not work. My USB to ethernet adapter works with my Linux laptop but not with Sony tablet S.
I ordered adaptor from dealextreme (win 7 compatible, chip AX88772BLF)
Someone on this forum succesfuly tested it with asus TF101
But on ICS error "Unsupported USB Device".
Now our table is rooted.
Any way to use it? Some .ko mudule?
Strange because in the build.prop, Eth0 network interface is enabled which means it should work.
Sent from my Sony Tablet S using xda premium
---------- Post added at 09:55 PM ---------- Previous post was at 09:43 PM ----------
nikor4 said:
I ordered adaptor from dealextreme (win 7 compatible, chip AX88772BLF)
Someone on this forum succesfuly tested it with asus TF101
But on ICS error "Unsupported USB Device".
Now our table is rooted.
Any way to use it? Some .ko mudule?
Click to expand...
Click to collapse
No app for such thing but you can have a look at the details of the device
Remember, even if it says 'Unsupported USB Device' doesn't mean it does not work, i got some app which tests USB headsets ("Unsupported" USB Device for Sony Tablet S) and i still get audio from the microphone i spock in into the speakers in the USB headphones.
USB Device Info
https://play.google.com/store/apps/details?id=aws.apps.usbDeviceEnumerator
USB Audio Tester
https://play.google.com/store/apps/details?id=de.sobe.usbaudio
Sent from my Sony Tablet S using xda premium
Thank you for Links! App recognized device.
But from terminal emulator i don't see eth0 interface.
Can I set up this?
Netcfg
lo - UP
dummy0 - down
sit0 - down
ip6tn10 - down
rmnet0 - down
Code:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Vendor Specific (0xff)
Vendor ID: 0b95
Vendor Name: ASIX Electronics Corp.
Product ID: 07d2
Product Name: not in db
Interfaces
Interface #0
Class: Vendor Specific (0xff)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 11
Max Packet Size: 8
Attributes : 000000011
Endpoint: #1
Address : 130 (10000010)
Number : 2
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 512
Attributes : 000000010
Endpoint: #2
Address : 3 (000000011)
Number : 3
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 512
Attributes : 000000010
nikor4 said:
Thank you for Links! App recognized device.
But from terminal emulator i don't see eth0 interface.
Can I set up this?
Netcfg
lo - UP
dummy0 - down
sit0 - down
ip6tn10 - down
rmnet0 - down
Code:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Vendor Specific (0xff)
Vendor ID: 0b95
Vendor Name: ASIX Electronics Corp.
Product ID: 07d2
Product Name: not in db
Interfaces
Interface #0
Class: Vendor Specific (0xff)
Endpoint: #0
Address : 129 (10000001)
Number : 1
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 11
Max Packet Size: 8
Attributes : 000000011
Endpoint: #1
Address : 130 (10000010)
Number : 2
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 512
Attributes : 000000010
Endpoint: #2
Address : 3 (000000011)
Number : 3
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 512
Attributes : 000000010
Click to expand...
Click to collapse
Strange because i have some different network interfaces then you and no eth0 what so ever even if its in the build.prop
Properties in Build.prop:
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
EDIT: Try typing 'ifconfig eth0' with the device connected to the adapter which is connected to an wireless router, tell me what you get after that, after doing that try using 'ifconfig eth0 192.168.11.14 netmask 255.255.255.0 up'
EDIT1: I found out that you may need to be rooted D:
EDIT3: Bingo!, try using 'netcfg eth0 up' with the adapter connected
EDIT4: Read EDIT1.
Results: I checked the commands with my rooted android phone and it seems it works with root, so far there is an exploit from Bin4ry (Can take almost or if not 2 days just to try to get it working depending on your method.) and the root exploit works with the latest version
Sent from my Sony Tablet S using xda premium
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.
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
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
Hey,
I've recently updated my Nord 2 from A21 to C10. Phone was unlocked and rooted, so after having reflashed the original boot.img, I forced the installation of the official OTA through TWRP. I had to set ro.commonsoft.ota=OP515BL1 to make it work. After the installation, TWRP failed to mount /system, but that didn't surprised me. I checked that the boot partition has been well flashed.
Now every time I try to power on the phone, it directly tries to run into recovery mode. However it fails and start again and again...
Maybe the system tries to install the OTA using the original recovery, which of course fails, and because of an unknown reason, it doesn't reboot to system.
Because of the last update, fastboot is not accessible anymore using vol -, and BROM mode is not accessible using vol + / vol -.
I tried to crash the preloader using mtkclient but it didn't work.
I tried to use META mode to switch to fastboot, but preloader only answers "READY" (instead of "READYTOOBTSAF"), and nothing changes.
I try to reverse engineer preloader and lk but it's something new for me. META mode code is still present in the preloader, so I don't understand what's wrong with it. Maybe disabled by default on USB...
Does anyone has a solution to boot into BROM mode or make META mode work ?
Or maybe I could find DA authentication files somewhere ?
@Petitoto can you share a bit about how you got the meta command running?
I'm in a similar situation with a Nord 2T. While mtkclient can get some info out of the preloader, meta never seems to connect.
Code:
mtk gettargetconfig
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Port - Device detected :)
Preloader - CPU: MT6893(Dimensity 1200)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x950
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Preloader - Get Target info
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Main - Getting target info...
Preloader - Target config: 0x5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: False
Preloader - Mem write auth: False
Preloader - Cmd 0xC8 blocked: False
Code:
mtk meta FASTBOOT
META - Status: Waiting for PreLoader VCOM, please connect mobile
META - Hint:
Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.
...........
META - Hint:
Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.
...........
META - Hint:
Power off the phone before connecting.
For preloader mode, don't press any hw button and connect usb.
Hey @Beanow,
I have the same gettargetconfig output, which indicates that the phone is not in BROM mode but stuck in preloader. Trying to interact with the preloader always lead to error because of the DAA (DAA_SIG_VERIFY_FAILED for example).
I have the same issue with mtkclient and meta mode. You can use the following modified mtk-bootseq.py:
py mtk-bootseq.py FASTBOOT COMXX (or python3 mtk-bootseq.py FASTBOOT /dev/ttyACMXX on linux).
Python:
import sys
import time
from serial import Serial
BOOTSEQ = bytes(sys.argv[1], "ascii")
DEVICE = sys.argv[2]
CONFIRM = b"READY" + BOOTSEQ[::-1]
while True:
try:
s = Serial(DEVICE, 115200, timeout=0.1)
print(".\n[+] Device detected")
break
except OSError as e:
sys.stdout.write("."); sys.stdout.flush()
time.sleep(0.1)
print("<-", s.read(256))
def send(bytes):
s.write(bytes)
print("->", str(bytes))
resp = s.read(256)
print("<-", str(resp))
return resp
resp = b''
while resp != CONFIRM:
resp = send(BOOTSEQ)
print("[+] Boot sequence sent")
On another device, it works and I get:
Code:
...............................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READYTOOBTSAF'
[+] Boot sequence sent
However, on my Nord 2, I get:
Code:
...........................................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READY'
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
Then the next s.write() is hanging.
I get the same result for any other boot mode. However, the code is still present in the preloader.
I unfolded my phone to try to find a test point. I tried all golden points but I only found:
- a point which loads preloader (and not BROM...) in the same way vol + / - do (in red in the picture)
- a point which boots the phone but without Android and OnePlus pictures (what's that ??) (in green)
{
"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 don't know how test point is handled: if that's the role of preloader, it may have been disabled by the update (as the BROM and fastboot). We may need to find the DAT0 point of the eMMC to short it and prevent the BROM to find the preloader, making it to go in EDL mode. However, I think that this point isn't exposed, and I won't disassemble my phone further without beeing sure of success...
Thank you so much for the work so far!
Unfortunately I get no response at all on the Nord 2T.
Code:
.......................................
[+] Device detected
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
Traceback (most recent call last):
File "/media/droid-work/mtkclient/mtk-bootseq.py", line 31, in <module>
resp = send(BOOTSEQ)
File "/media/droid-work/mtkclient/mtk-bootseq.py", line 24, in send
resp = s.read(256)
File "/usr/lib/python3.10/site-packages/pyserial-3.5-py3.10.egg/serial/serialposix.py", line 595, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
How did you connect to the device that you're getting these responses?
In my case, I need to use vol+, vol- and power, like mtkclient, or the ttyACM0 won't exist.
(I've got udevadm monitor up, watching for the usb/tty to be added)
Indeed, you need to run into preloader using vol +, vol -
Maybe a driver / python module issue. I've got similar issues on my linux. Try on windows or try to reinstall drivers.
It should work at least for the first answer. Else it means that your preloader doesn't send any data, which is not the case as mtkclient works.
I also tried a different baud, because a pl_lk log from oplusreserve2 partition suggested it may be used. No luck though. Note, this was a very old log I saved early on. Definitely not reflective of latest Nord 2T update.
Code:
[PLFM] boot_tag size = 0x0
BOOT_TAG_VERSION: 0
BOOT_REASON: 0
BOOT_MODE: 0
META_COM TYPE: 0
META_COM ID: 0
META_COM PORT: 285220864
META LOG DISABLE: 0
FAST META GPIO: 5906
LOG_COM PORT: 285220864
LOG_COM BAUD: 921600
LOG_COM EN: 1
LOG_COM SWITCH: 0
MEM_NUM: 2
MEM_SIZE: 0xAE7B
MEM_SIZE: 0xAE8D
I guess I'll try windows then
Code:
python mtk-bootseq.py FASTBOOT COM4
...................................................................................................................................
[+] Device detected
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
Windows looks to behave similar. Though windows wouldn't take the MTK VCOM driver, so this is win10 default serial, in a VM over USB passthrough.
So, same result not in a VM. Though specifically with powershell I got the same output as you did.
Code:
...........................................
[+] Device detected
<- b'READYREADYREADYREADYREADY'
-> b'FASTBOOT'
<- b'READY'
-> b'FASTBOOT'
<- b''
-> b'FASTBOOT'
<- b''
This is really a helpfull post for us. I've already a oneplus nord 2 phn,from this post i know the more information about this phn.
Thank you so much.
@Beanow So same results...
It's weird that it doesn't work on Linux. Maybe an issue related to pyserial or connection settings.
What's preventing the device to be detected by mtkclient is line 54 in mtkclient/Library/meta.py: and cdc.pid == 0x2000 should be removed. So you can try to switch to fastboot using mtkclient on Linux, but with my Nord2 I get the same results as mtk-bootseq.py on Windows
Petitoto said:
@Beanow So same results...
It's weird that it doesn't work on Linux. Maybe an issue related to pyserial or connection settings.
What's preventing the device to be detected by mtkclient is line 54 in mtkclient/Library/meta.py: and cdc.pid == 0x2000 should be removed. So you can try to switch to fastboot using mtkclient on Linux, but with my Nord2 I get the same results as mtk-bootseq.py on Windows
Click to expand...
Click to collapse
Thanks for this. No need to switch to windows anymore, to use mtk client.
Petitoto said:
It's weird that it doesn't work on Linux. Maybe an issue related to pyserial or connection settings.
Click to expand...
Click to collapse
Is it 'not working' though? It's also weird to me that I had the same output as Linux using Windows' cmd, while there was READY spam in powershell. Same drivers, same python, same libraries, but different output?
I suspect that it might be a timing issue. Maybe the serial console doesn't care about or wait for input at all. And just spams READY a few times. It would be a matter of how fast the connection is established.
Perhaps as well there's a different subsystem sending commands to the 'meta' environment and the READY spam means it's processing those commands rather than whatever we're sending.
All theories, but I would find it really hard to believe there's a problem with Linux drivers / libraries for something as basic as a UART/serial console over USB.
Petitoto said:
@Beanow So same results...
It's weird that it doesn't work on Linux. Maybe an issue related to pyserial or connection settings.
What's preventing the device to be detected by mtkclient is line 54 in mtkclient/Library/meta.py: and cdc.pid == 0x2000 should be removed. So you can try to switch to fastboot using mtkclient on Linux, but with my Nord2 I get the same results as mtk-bootseq.py on Windows
Click to expand...
Click to collapse
I also suspected this PID check and tried to log the else cases, but never reaches those for me.
So removing the check didn't help for mtkclients' meta commands.
Is it 'not working' though? It's also weird to me that I had the same output as Linux using Windows' cmd, while there was READY spam in powershell. Same drivers, same python, same libraries, but different output?
Click to expand...
Click to collapse
Differents results when using cmd and powershell? There is really no reason for that. Unless it's not the same Python environment, with different pyserial for eg. I have issues to run mtk-bootseq on Linux, but always the same output on Windows' cmd.
I suspect that it might be a timing issue. Maybe the serial console doesn't care about or wait for input at all. And just spams READY a few times. It would be a matter of how fast the connection is established.
Click to expand...
Click to collapse
Maybe. On linux, I can get different results depending on baud rate, timeout (and luck?). If there is an issue related to the connection, it might explain why the preloader doesn't answer as expected. But as other commands (like mtk gettargetconfig, but also manually handshaking connections and gathering informations in pyserial) work well, I tend to think it's just disabled.
Perhaps as well there's a different subsystem sending commands to the 'meta' environment and the READY spam means it's processing those commands rather than whatever we're sending.
Click to expand...
Click to collapse
I don't really know how it works. The code is still present in the preloader. However this functionnality is not always enabled. Maybe reversing the preloader more or analysing the log you provided on Github might help to determine whether or not it is enabled. Moreover, even if we manage to switch to fastboot, if the bootloader has been fully disabled, we may face the issue of the preloader trying to run into a non existant fastboot. Maybe the FACTFACT mode may help to reset the device, but I don't really know a lot about this mode.
So removing the check didn't help for mtkclients' meta commands.
Click to expand...
Click to collapse
Once you removed this check, if you print the data sent by the preloader, you'll get the multiple "READY" like mtk-bootseq on Windows. Moreover, I can switch to fastboot using this command on another MTK device.
Dear Sir,
Do you have any method to recover my phone as the figure show?
Thank You