I've bought one Mi Smart Clock. I love this device: so compact, nice and solid design, a 4inch LCD screen, WiFi and BT capabilities.
There's "too much google" for me, so i'm wondering if it's possible to hack it and run a custom firmware.
Connecting an USB on boot, firstly i got a MediaTek MT65xx Preloader:
Code:
usb 2-2: new high-speed USB device number 22 using xhci_hcd
usb 2-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: MT65xx Preloader
usb 2-2: Manufacturer: MediaTek
cdc_acm 2-2:1.0: Zero length descriptor references
cdc_acm: probe of 2-2:1.0 failed with error -22
cdc_acm 2-2:1.1: ttyACM0: USB ACM device
usb 2-2: USB disconnect, device number 22
that send a lot of "READY" to /dev/ttyACM0 device.
After few seconds, it disconnect and connect a:
Code:
usb 2-2: new high-speed USB device number 7 using xhci_hcd
usb 2-2: New USB device found, idVendor=0e8d, idProduct=2008, bcdDevice= 2.23
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: X04G
usb 2-2: Manufacturer: Xiaomi
but i was not able to do something more that configure it as firmware allow.
Anyone already did something? There's any team/group/someone else interested in build an hack for this nice device?
Thanks for any help, really appreciated!
I bought the Chinese version, and its model is slightly different from yours. It is said that this is the overseas version of the Chinese version. I compiled a twrp for this device, not sure if it will work on yours.
GitHub - MaxCaiLC/twrp_xiaomi_lx04_device_tree
Contribute to MaxCaiLC/twrp_xiaomi_lx04_device_tree development by creating an account on GitHub.
github.com
Can you back up your firmware with mtkclient and send it to me? I am interested in this model.
Is there a way to add a custom alarm sound?
Hi!...I also have a LX04 version of the firmware, have you been able to extract the X04G version to be able to update the firmware???
MaxCaiLC said:
I bought the Chinese version, and its model is slightly different from yours. It is said that this is the overseas version of the Chinese version. I compiled a twrp for this device, not sure if it will work on yours.
GitHub - MaxCaiLC/twrp_xiaomi_lx04_device_tree
Contribute to MaxCaiLC/twrp_xiaomi_lx04_device_tree development by creating an account on GitHub.
github.com
Can you back up your firmware with mtkclient and send it to me? I am interested in this model.
Click to expand...
Click to collapse
Did you get the firmware version with google assistant?
TIA
Jordi Escolà said:
Hi!...I also have a LX04 version of the firmware, have you been able to extract the X04G version to be able to update the firmware???
Click to expand...
Click to collapse
I have a device with x04g firmware on it. How can i extract the firmware?
Related
Hello everybody out there.
I am trying to add support for the AR9271 USB WiFi device in the CM11 release kernel on my i9507. I've managed to compile the kernel with ath9k and mac80211 (dependency) baked in instead of as modules. I believe this would skip the need to load and unload modules to get the card working. I booted successfully and plugged in my adapter with an OTG cable, but upon ifconfiging and whatnot, I could not find the adapter at all. I tried using Pcap Capture by Kismet, and that reported no connected USB NICs.
I'm losing sleep . What am I doing wrong? Does anybody have an idea? I can release my build of kernel with ath9k support if anyone wants it, although I guess anyone who answers this probably doesn't need it anyway ._.
Thanks guys.
EDIT:
Apparently Kismet Pcap only works with that one Realtek chipset in the Alfa, so that's out the window.
Anyway, I have installed the firmware file (htc_9271.fw) to /system/etc/firmware and the device shows up with lsusb with ID 13d3:3327, so it's being recognized, but the kernel still takes one look at it, laughs, and dies.
Here is the dmesg output:
<6>[14516.472685] usb 2-1: New USB device found, idVendor=13d3, idProduct=3327
<6>[14516.472716] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[14516.472747] usb 2-1: Product: UB93
<6>[14516.472747] usb 2-1: Manufacturer: ATHEROS
<6>[14516.472777] usb 2-1: SerialNumber: 12345
It seems like the kernel just derps and doesn't load the ath9k_htc stuff it's supposed to. I do remember that when I compiled the kernel, I got errors compiling the ath9k modules. I found no patches for this problem, so I took the ath folder from the linux kernel backports (compat-wireless) and plopped it in the CM kernel drivers folder, replacing the old one. Worst way to merge code, I know. The kernel compiles fine, but according to dmesg, the drivers either aren't there, or aren't doing anything.
I have an old Canadian Bell based Galaxy s4, with a dead screen. I'd like to try to get files off it, but did not enable usb debugging mode prior to the screen breaking.
Is there any way to access the file system on the phone in this situation? I've done a bit of looking around and can see that I should be able to access it via adb if I have usb debugging turned on, but debugging isn't on in this case.
I have usb connected the phone to my fedora machine and can see via dmesg that it does get detected. I can hear the thing start up, but beyond that I can't see anything else.
Googling around it sounds like I should be able to load a recover kernel, with debugging turned on if I use the right process, but I can't find enough into to get me going.
dmesg output is below just in case it helps...
.....................................................................................
[ 4104.343749] usb 2-2: USB disconnect, device number 6
[ 4180.261104] usb 2-2: new high-speed USB device number 7 using ehci-pci
[ 4180.376385] usb 2-2: New USB device found, idVendor=04e8, idProduct=6860
[ 4180.376390] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4180.376394] usb 2-2: Product: SAMSUNG_Android
[ 4180.376396] usb 2-2: Manufacturer: SAMSUNG
[ 4180.376399] usb 2-2: SerialNumber: ........
Any help is much appreciated!
If you can get a custom recovery on you can use adb without use debugging on. I assume you have an i337m. Try this with twrp http://galaxys4root.com/clockworkmodtwrp-recoveries/
Sent from my Nexus 9 using XDA Free mobile app
If you have a custom recovery plug it up to hdmi thru HML and use the TV for the screen. Hopefully the touchscreen still works. This worked for mine. No lcd but the digitizer was still good.
Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.
hohassan444 said:
Any one tried flashing using Linux version of SP flash tool? . I tried but seems the device not recognized by pc.
Click to expand...
Click to collapse
Do you mind providing a link to the linux version so that i can test?
kirito9 said:
Do you mind providing a link to the linux version so that i can test?
Click to expand...
Click to collapse
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note: currently latest version on that page actually is SP Flash Tool v5.1520.00
Nofan Tasi said:
http://www.needrom.com/download/sp-flash-tool-v5-1424-00/
note latest version on that page actually is SP Flash Tool v5.1520.00
Click to expand...
Click to collapse
Alright, thanks
I found a solution for S_BROM_CMD_JUMP_DA_FAIL (2035) here:
The “modemmanager” package integrated by default on your computer it is not compatible with the MTK Flash Tool for the Linux (14.04 and 14.10) latest versions, and must be uninstalled beforehand. This package is used as a protective USB modem device. Any user configuration file will remain after you uninstall and install the package. Though, we can reinstate our current configuration if necessary, after using the tool.
The following steps will be necessary for the latest versions of Ubuntu:
º Uninstall the designated package using the following commands:
♦sudo apt*-get remove modemmanager
♦sudo service udev restart
Udev restart the service without restarting the computer
Udev restart the service without restarting the computer
This may have the side effect of removing the kernel module “cdc_acm”. To check if so, run the following command:
♦lsmod | grep cdc_acm
Check kernel module
Check kernel module
º If it gives you an empty list in return, you must install the following module:
♦sudo modprobe cdc_acm
Click to expand...
Click to collapse
After this, the tool connected to my phone without errors.
I reinstalled modemmanager after flashing:
Code:
sudo apt-get install modemmanager
I slightly modified Sergio Riveros excellent! marvellous! perfect! tutorial and translated it into German for android-hilfe.de
I will post an English version here within the next couple of days...
I finally can put the ancient XP netbook back where it came from to (hopefully) never have to come out again.
The linux SP flash tool works just fine and, yes: cdc_acm module is needed as dmesg shows:
--
usb 1-5: new high-speed USB device number 6 using ehci-pci
usb 1-5: New USB device found, idVendor=0e8d, idProduct=2000
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: MT65xx Preloader
usb 1-5: Manufacturer: MediaTek
cdc_acm 1-5:1.1: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
--
Either all my USB-A to USB-C cables are broken, or the USB-C on my Nexus 6P is broken. In any case, I cannot detect my phone from my computer. When I connect it I get
Code:
[319203.836580] usb 3-2: new full-speed USB device number 18 using xhci_hcd
[319203.949925] usb 3-2: device descriptor read/64, error -71
[319204.173299] usb 3-2: device descriptor read/64, error -71
So, the question is: Is there any way to install an OTA update without using the cable? I have tried to install it from the update menu under "about", but it reboots directly to TWRP, so does not work.
Any clues?
Are you rooted? If so, you could try FlashFire.
Yes, I am. Thank you! That is exactly what I was looking for. I'll try it and let you know whether it worked or not.
Update: I worked like a charm. I will buy the pro version just to support the developer for his amazing job.
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the factory Google image back to the phone?
burntpuppy said:
Hi All; my pixel 4 test phone got unhappy. I was trying to reinstall twrp and screwed up. So now when I try to boot I get the screen below. And nothing seems to work, any idea on what to try? ADB and fast boot don't respond. Dmesg show the device is enumerated.
[950748.188201] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[950749.179852] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[950749.179860] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[950749.179863] usb 3-1: Product: Pixel 4
[950749.179866] usb 3-1: Manufacturer: Google
[950749.179869] usb 3-1: SerialNumber: 9B061FFAZ**0**2
Thanks for any advice. Is there a jtag pinout?
Click to expand...
Click to collapse
Did you try flashing the Google stock factory image?
I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel
burntpuppy said:
I cant seem to get anything other than that screen, phone doesn't show up in adb devices, or in fastboot devices. I've p
ulled the battery, and finally the fastboot devices showed the pixel
Click to expand...
Click to collapse
If it's detecting the device your fine. Go here, https://flash.android.com/build/7005429?target=flame-user&signed. and re-flash the firmware and you will be good to go.
I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working
burntpuppy said:
I reflashed boot.img to slots A and B, and system.img to system. Now I get "Failed to load/verify boot image". Still no adb but fast boot is now working
Click to expand...
Click to collapse
You need to re-flash everything. It should do all the work for you. Maybe you flashed the wrong boot.img? Here is the main page for all devices. https://developers.google.com/android/images Select your device, you can choose flash and it will do it all for you or you can download the image, extract it all to your adb folder, double click flash-all and it should flash everything on its own.