Database Info

[HOWTO] Milestone USB-Host mode & using USB devices

Motorola Milestone - USB OTG - USBHost Mode
Found on Chris Paget's blog and since there isn't anything related, I'm postin' it here for xda-devs (with some clarifications and corrections in his words).
You’ll need to make two things, a micro-dongle to enable the USBHost mode (that you'll plugin during boot time) and a cable with the right connectors on each end (for connecting your peripheral).
To do this you’ll need three cables:
- A car charging cable (off-the-shelf at the Verizon store)
- A Micro-USB cable (as above)
- A USB extender cable (the tiny ones that sometimes come free with USB keys work great)
Start with the car charging cable. Break open the micro-usb connector (it comes apart fairly easily) and look at the little PCB inside – there should be a single tiny surface-mount resistor and two wires from the charger cable. Unsolder both wires and the resistor, and then bridge the pads where the resistor used to be so that it’s completely shorted.
The end result should look something like this:
{
"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"
}
(Micro Dongle)
Next up, you need to make your connector cable. Cut the end off the USB extender cable, you want to keep the socket end and discard the plug. Cut the micro-usb cable as well, but on this one you want to keep the plug and discard the socket. You should now have a micro-usb plug that’ll fit into your droid and a usb socket that you could plug a memory stick into. Strip the wires off the ends of both cables and join them to each other, connecting like colours (and the shield) together. When it’s finished it should look something like this:
For using USB-Host mode and your USB peripherals you have to do the following:
- Turn your Milestone off
- Plug the micro-dongle into the USB port
- Turn the Milestone on
- Unplug the micro-dongle as soon as the Motorola logo disappears (when the Android bootscreen is appearing).
Once your Milestone is booted, pull up a terminal and look at dmesg – after plugging in your USB peripheral using the cable you made earlier you should see the usual kernel notifications about new USB devices being connected; they’ll also turn on (or start charging) if they’re powered by USB.
You’ll only be able to plug in one peripheral before the port reverts to peripheral mode and you’ll have to reboot with the micro-dongle if you want to go back into host mode.
Also, if you leave the micro-dongle plugged in too long it triggers another bug, the port gets stuck supplying power to devices but not actually recognising them. Hopefully the drivers are sufficiently open-source that these are easy bugs to squash, and that dynamically switching between host mode and peripheral mode won’t be too hard to add either.
USB external storage won't work, but USB Keyboards are working. Anyway, we can compile a module for making the Linux kernel to recognize all we want since we can insmod as root.
--kholk

and the same text are here

Is it possible to load a module witch allows usb memory sticks?
Sent from my Milestone using XDA App

I made a USB host cable based on Gowthamj reply on the same blog.

Anyone sell this on ebay?

rizdroid said:
I made a USB host cable based on Gowthamj reply on the same blog.
Click to expand...
Click to collapse
Hi,
Some schematics or blueprint that you can upload here?. Look great!!!
EDIT: Got it!: http://sites.google.com/a/gowthamj.com/www/

i do host cable with blueprint from post #6 and... Something work
I'dont have any classic usb keybord (only wireless), but i try with usb storage.
After reboot and pressing button red led on pendrive blink a few times, after i release button (after M logo) they turned black.
It means that cable is ok, in dmesg i saw notification of connecting USB Device. But without drivers in kernel we can put this in our... boxes with accesories... kernel is locked, host usb is IMO only a funny feature of Motorola Milestone

Cant we use the modules they use to connect usb memory sticks to their N1s?
Would this work?
Sent from my Milestone using XDA App

royalcs said:
Cant we use the modules they use to connect usb memory sticks to their N1s?
Would this work?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
No, because the N1 uses a different kernel and modules as to the Motorola Milestone.

Is there a chance for external USB sound card to work?

bump!
I'm not a linux guy so anyway - do the drivers for usb host HAVE to be compiled in kernel? As on milestone the kernel can't be modified this implies the usb host on milestone works just with - usb keyboards?
Is there any way to use other usb devices? I'm asking because if not it seems it isn't worth to make the "micro usb host + switch" cable...

there is no way untill we can put or own kernel signed by owrselves on the milestone
Live long and prosper- tapatalk

thx but we all know that.

MuF123 said:
thx but we all know that.
Click to expand...
Click to collapse
so.. we all know that the only included driver available is for keyboard, no one has ever reported anything but, and yet... there is a post asking about it, isnt it?
Live long and prosper- tapatalk

Khul said:
so.. we all know that the only included driver available is for keyboard, no one has ever reported anything but, and yet... there is a post asking about it, isnt it?
Live long and prosper- tapatalk
Click to expand...
Click to collapse
could you please read what you post?
Khul said:
there is no way untill we can put or own kernel signed by owrselves on the milestone
Live long and prosper- tapatalk
Click to expand...
Click to collapse
You said kernel is locked.
We all know that.
And if being smarta*s is the only thing you can do here I think noone is interested in your posts Bye.

Please ppl don't become offensive...Just ignore some posts and let's continue to be productive about the topic

we can try to load modules for the kernel. no need for custom kernel. just compile the module sources against the milestone kernel and present libs (for ex. the now famous kernel 2.6.32.9-ge635aa4

so it is possible, but requires better knowledge of linux stuff like compiling etc - that I as a windows user don't know... however - for a person who knows how to do that - is it possible without much effort to do that? or do you need to code your own driver or what
edit> what do we need to do that? let's say I will come to my friend to do the compiling for me - what does he need to do that? how will I then use those drivers? is it same as in linux so will some guide for linux apply to android?

MuF123 said:
if being smarta*s is the only thing you can do here I think noone is interested in your posts.
Click to expand...
Click to collapse
wow jumpi huh? no need to mate, not being smarta*, just returning your "we all know that" right back at ya. nothing more, its all good.
anyways, i didnt think you could actually add more drivers and get them to load properly... thats nice to hear.
Live long and prosper- tapatalk

Awesome!!Nice guide!!! Thank you!!!

USB download mode working on Genbook108 need .img files

I've gotten the genbook 108 into Download mode by opening it up and holding down the s1 button next to the cpu board inside this unit. With the correct cable and drivers I can see the unit now inside windows. I want to get the images so I can start flashing and attempting to dev this without worrying about bricking the unit. Augen is AWOL (out of business) and the company selling them now is an asset recovery company.

I just bought one of these, and am disappointed in the Android 2.1 implementation the mfg used. If you get a linux version or higher than Android 2.1 working, I would be happy to be a beta tester.

I've also now relace the crappy internal wlan with a tenda .. its usb ftw littlesoldering
Sent from my SPH-D700 using XDA App

Progress?
Darkpoe, have you had any progress with your setup? I have the genbook and have been stuck without any luck. Could you maybe post some pictures of your setup?

darkpoe said:
I've gotten the genbook 108 into Download mode by opening it up and holding down the s1 button next to the cpu board inside this unit. With the correct cable and drivers I can see the unit now inside windows.
Click to expand...
Click to collapse
I drilled a hole in the bottom of my unit to expose S1 but I can't figure out how long to hold it down for. Hints?
When you say "Correct Cable" you mean an A-A USB cable?

genbook roms
Anyone attempting to reflash a genbook 10.2 beware if you flash wrong rom you will brick the netbook for sure,you must have correct fdwn files to restore the system as of this posting i have not been able to locate them since augen is now out of busniess.If you brick it you will have to open up the unit and short out the rom chip several times to get computer and fwdn program to see the netbook doing this too much with short out the pins which are very very soft material and will mash together causing a perment short circuit.You can only do this about 3 times before this will happen so make sure you have all the fwdn files ready to flash before using this program

PX5 stuck in bootloop

This Post details how OTG/LOADER can be achieved to recover a corrupt PX5 or PX3 - any RockChip MTCx SOM
Update 2/2018 - anyone can make a gig without modifying their main board. BUT FIRST try a USB port, some have OTG out of the box.
From the work I've now done, Ive realised you don't need to hack your mainboard. You could temporarily solder connections to SOM or make JIG from header pins or make a simple cable from an old USB cable and two resistors: see: https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Making a jig is necessary , as MCU cuts power to SOM after a few minutes during OTG.( Theory is the MCU watchdog senses an unknown condition in SOM, so resets by power off.) This can be bypassed by another mod to board, but much easier to just make a simple jig.
Need:
Remove SOM from mainboard.
Header pins to fit SOM (or solder temporarily to SOM PCB header)
USB male cable, cut one end off for wires to attach to SOM.
5v and 3.3v power supply.
1. Using schematic as guide. Connect earth and +5v pins. Connect 3.3v to [rtc_3.3]
2. Connect USB wires to SOM [USB-OTG] connections
3. Connect wire to SOM [ctl_recovery] and wire that to 3.3v.
Colour codes & Notes:
GREEN = PSU Earth [0v/(-)]
RED = +5v to PSU
BLUE = USB
YELLOW = +3.3 Via 3.3v supply OR use two resistors as a voltage divider 10K to 5v (R1 in image), 15k to earth (R2 in image), center = 3.3v
NOTE: SINK [CTL_WAKEUP) to GROUND (0v) if unit does not power ON
+5v = 1,2,3
0v = 4,5,6,71,72,73 and SOM Mounts
+3.3 = 20,28 (and possibly 9 & 15 - see note re. 15.)
With USB connected, power on. Use tools/load driver as described in recovery thread.
Q/Why hardware mods?
A/Mods were necessary because out-of-the-box (default) both my GS and JY boards would not enter USB OTG/Loader mode to connect it to a PC for recovery. We now know that a "jig" can be made without sacrificing your mainboard and simply wiring to header pins or buying a SOM header from say Digi-Key.
- Your MTCD may be different -so test first!
Q/My SOM won't appear in device manager or Rockchip Android tool
A/ If all connections are correct and power is Ok, force MASKROM as detailed here:
https://forum.xda-developers.com/sho...&postcount=128
https://forum.xda-developers.com/sho...&postcount=129
***Updated 08/Dec/2017 - Attach image showing USB Male cable connections to mainboard***
** Note - SD recovery boot card did not work for me on PX5 - probably due to version of [rockchip sdcard image create tool] - if anyone has a version that works, please post here.
Updated Feb 2018 - Android 6 SDCARD create tool is now available. Recommend SDCARD method and then OTG if SDCard method fails
Synopsis
My corrupt NAND was successfully reflashed using OTG "LOADER" mode as follows. It became corrupt , stuck in a bootloop and unable to enter recover following flashing a custom (bad) firmware image file.
- Using an MTCD GS board - which I have as a spare part - no display, only board.
+ Windows 10 x86 notebook with rockchip batchtools v1.8, rkimagerepack tool, latest PX5 image.
+ USB stick formatted fat32 with latest PX5 image
Do not do the below mainboard mods, this is completely unnecessary and posted for background on the journey to find a simple way of getting OTG.
1. Modified the board as follows:
A. Desolder and lift pins 27 & 28 of USB hub GL850 (thanks to xda user @ikerg and 4pda - for the lead)
B. Solder Male USB a cable to GS board USB 1 connections (See below attached image showing where USB male plug wires were soldered)
C. Remove pin to RK PX5 SOM [ctl_recovery]
D. Solder a wire directly on PX5 SOM header on [ctl_recovery]. This wire is used to trigger recovery.
Process
Initial recovery image: Because the PX5 firmware (OTG) "LOADER" process timeout appears to be approx 1 minute, it was necessary to create a recovery only image, as the 1.2gb PX5 firmware file exceeds the timeout, aborting the flash.
Using RKIMAGEREPACK, I created a image with a dummy zero byte system.img. This resulted in a 200mb image file.
- Loaded [rockchip batch tools] on notebook.
- Installed rockchip drivers
- connected USB cable to notebook
- held [ctl_recovery] wire to [mcu 3.3v test pad]
- Powered headunit on
- Notebook 'USB chime' was heard and board became connected, as indicated as highlighted '1' in rkbatchtools
- wiped flash
- selected firmware image without system created above and flashed to PX5
- powered off, removed PX5 SOM and refitted to JY headunit board
- On JY headunit, powered on, entered recovery via [holding powerbutton for approx 15sec - wait for 3 flashes of led] press once more.
Successful boot into recovery - started booting recovery and warned that system image was not valid. PX5 self-formatted system and awaited image.
- inserted USB stick with latest PX5 image and upgraded.
First boot waited for 5 minutes. Pressed reset and rebooted - successful recovery!
The warning here is that the PX3 SDCARD image create tool does not work for PX5 - even when using a PX5 image.
Why did I post this? Original Post:
I have a (JY) MTCD with HA 2..56 MCU PX5 stuck in a boot loop - "starting apps" appeared and then it reboots, looping. I was unable to access recovery via any of the standard recovery processes (e.g.holding the power button or boot into recovery via bootable SDCARD.
========================================
On SDCard boot - works OK on PX3 but on PX5, only a black screen is displayed without any text.
SDCard and button holding recovery methods worked OK on PX3 board, but not the PX5 Module when the SOM NAND was corrupt.

Ok - need to figure out how to force this PX3 board to 'maskrom' - this is the procedure where the NAND is suppressed by grounding the I/O or Oscillator to effectively stop the NAND. This then places the RockChip PX5 into Maskrom mode to then connect/reflash via USB.
Anyone tried this?
Feb 2018 - MASKROM methods have been identified for both PX3 and PX5 Modules. See posts later in thread.

You seem to think you have both a PX3 and a PX5 board....it is one or the other.

nixfu said:
You seem to think you have both a PX3 and a PX5 board....it is one or the other.
Click to expand...
Click to collapse
Thnaks for your reply - clarifying [I have a (JY) MTCD with HA 2..56 MCU PX5 stuck in a boot loop]
I have a PX3 Board that I have swapped back in to test - it is OK. The PX5 goes black screen if trying to boot from SDCARD recovery and I cannot seem to force it into [maskrom] to flash from PC either.
Would be interested to hear if other PX5 users who have swapped from PX3 to PX5 can access recovery OK.
Note that I foolishly screwed up and flashed a custom image thayt contained what I think may be the wrong achitecture of SUPERSU, hence the boot loop. BUT this doesnt explain why I can no-longer enter recovery, or does it?
Regards,

try holding the reset button for about a minute. it should auto restart into recovery. it will first go off, then it will either pop back on suddenly or start turning itself on and off. if it does the on and off thing i usually let it boot to recovery on the third one

Thanks for the info.
Ive done everything but holding the power/vol knob or reset for 1 minute.
Tried forcing the unit into mask rom by very carefully exposing some of the obviously IO tracks between the cpu and flash and shorting a pair (this is the method described elsewhere, but usually there are copper test pads (you'll see these on the px3 module but not px5))
No matter what I try, I cant get my pc to see the head unit via either usb sockets. I made a 1 to 1 usb A male cable which works with a nexbox OK but not these headunits. The HU is a JY UL124 orginally px 3. It has 2 sdcard slots and two usb.

After significant research and testing, I have a recovered PX5! See Post#1

Good.....clap clap clap
Your tutorial is very clear and useful for other people....No more bricked devices....

ikerg said:
Good.....clap clap clap
Your tutorial is very clear and useful for other people....No more bricked devices....
Click to expand...
Click to collapse
Thanks - updated op with a couple of images of my test/recovery jig and software.

marchnz said:
After significant research and testing, I have a recovered PX5! See Post#1
Click to expand...
Click to collapse
good work there - would like to check my px3 board so did you ground to GND or D0 for reset on px3 pads ? and if you could show which wires on usb lead you connected to pin 27 & 28 on GL850 chip that would be very useful thanks

audisean said:
good work there - would like to check my px3 board so did you ground to GND or D0 for reset on px3 pads ? and if you could show which wires on usb lead you connected to pin 27 & 28 on GL850 chip that would be very useful thanks
Click to expand...
Click to collapse
Great question and good spotting - on px3 its possible to force "maskrom" by shorting [gnd] & [d0] pads. Unfortunately px5 do not have these pads and can only be achieved on px5 via carefully exposing track insulation to NAND - fortunately px5 will enter "loader" mode on recovery. So, no I did not do this, I used a GS board I have as a spare part and modified it to force recovery, by removing the SOM header "recovery" pin and grounding that pin via a switch - to force the SOM into recovery.
Note that OTG USB connections are made to the USB switch IC (if fitted) U27 [fsusb42]. If this IC/USB switch is not fitted, more drastic mods would be needed to disconnect the usb connections to the usb hub IC (by disconnecting the SOM header pins.) If you have a GS, you have U27. If not you will need to check.
Happy to answer questions here, we can all benefit through sharing.

marchnz said:
Great question and good spotting - on px3 its possible to force "maskrom" by shorting [gnd] & [d0] pads. Unfortunately px5 do not have these pads and can only be achieved on px5 via carefully exposing track insulation to NAND - fortunately px5 will enter "loader" mode on recovery. So, no I did not do this, I used a GS board I have as a spare part and modified it to force recovery, by removing the SOM header "recovery" pin and grounding that pin via a switch - to force the SOM into recovery.
Note that OTG USB connections are made to the USB switch IC (if fitted) U27 [fsusb42]. If this IC/USB switch is not fitted, more drastic mods would be needed to disconnect the usb connections to the usb hub IC (by disconnecting the SOM header pins.) If you have a GS, you have U27. If not you will need to check.
Happy to answer questions here, we can all benefit through sharing.
Click to expand...
Click to collapse
Thanks for reply - my px3 board appears dead in unit thus far - think i've worked out how to solder usb A cable now just didn't want to cause any damage mixing tx/rx wires - i'll have to retest but i think I had 3.3 volts at GND & D0 pads - no time today but will have a go tomorrow (hoping this board is where Nand or fried chip fault lies) I have ordered a PX5 board so hopefully will get unit working

Had a try with px3 board - lifted pins 27 and 28 - put software and drivers on laptop - soldered usb lead to d+ and d- on px3 board and ground traced from u27 and ctl_recovery wire - nothing happens still - power at u27 is 3.3 volts

audisean said:
Had a try with px3 board - lifted pins 27 and 28 - put software and drivers on laptop - soldered usb lead to d+ and d- on px3 board and ground traced from u27 and ctl_recovery wire - nothing happens still - power at u27 is 3.3 volts
Click to expand...
Click to collapse
Good work! How have you isolated the header pins - if they are still all connected (ctl_recovery, d+,d-) to respective ICs, it wont work because of contention with the connected ICs. E.g. ctl_recovery is connected to MCU and is pulled up to +3.3v by MCU - my solution was to remove respective header pins by careful desolder - they can then be refitted.

Knew i'd missed something - header pins still connected so will try to isolate guessing I need only connection at SOM board only..

pins isolated but no luck yet.... think maybe my chip is faulty (others report some px3 chips come from faulty batch) so will wait px5 board delivery - if that works I might order a replacement px3 chip and try replacement

A bit over my head
Any chance I could get a hand ?
Maybe over Hangouts or something ?
Please Please Pretty Please lol
Here's what I'm workin with https://goo.gl/photos/uNTpFnUYJxZ3VwSJ7

Got the new PX5 board (12 days from China ) put into head unit and worked straight away - posting here as I had major trouble re-soldering pins 27 & 28 when I pulled a leg off GL850G usb chip - see attached pic of wire I had to solder in place... thinking if I did this again I would probably just make a break in circuit tracks and use conductive glue or nickel pen to remake circuit - PX3 board is still dead - never got usb to pc connection - as for Cid6.7 board - looks like you found the usb hub chip and switch chip (different boards to mine though) pin 27 & 28 are opposite dot on chip - usb switch chip should go +5v, sel, d+ , d-, and ground

Is all this done just for the pc to detect the unit..?
If so what if the pc already detects it BUT unable to write to it with 0 modifications done to it..?
https://goo.gl/photos/m7NGyrkD4ef2YydD7
audisean what did you pay for the PX5 board if I may ask..? I'm wondering if I am able to swap chips from Sofia to PX5 with no mods

Cid6.7 said:
Is all this done just for the pc to detect the unit..?
If so what if the pc already detects it BUT unable to write to it with 0 modifications done to it..?
https://goo.gl/photos/m7NGyrkD4ef2YydD7
audisean what did you pay for the PX5 board if I may ask..? I'm wondering if I am able to swap chips from Sofia to PX5 with no mods
Click to expand...
Click to collapse
I paid about £95 for the board with airmail dispatch - not sure if it would work on yours - fitment looks similar with pin header - Witson 32814450733 is what I bought - worked straight away and recognised settings from previous android system in unit. The PX3 mods were necessary for otg cable to link pc and flash - if you have recovery by SD card or front usb you won't need it. Sofia looks pretty different but if you can link pc did you try rockchip batch tool ?

Question Some questions about a FYT unit with Unisoc UIS8581A

Hi gents and ladieas alike,
Recently I purchased a unit with the info
{
"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"
}
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance

iionas said:
Hi gents and ladieas alike,
Recently I purchased a unit with the info
its a 4gb 8core with 32gb of storage.
Iam extremely new to this and Im yet to figure out what certain things mean so please be gentle
1. Is there any mods worth doing?
2. Is there any better firmware to flash/use to make this unit 'better'
3. I have changed to nova launcher and it seems to be snappier, any questions here?
4. What can I use to re-program buttons on my steering wheel? What it comes with doesnt seem to work.
5. Its actually android 10, not 11, its spoofed I checked.
The Device manufacturer is SPRD
Any help would be greatful!
Thanks in advance
Click to expand...
Click to collapse
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..

surfer63 said:
It's a FYT unit. Any firmware from a FYT reseller can be used be it for uis7862 or uis8581A. The 8581A is simply the "lighter" less poweful brother of the uis7862. There are some minimal tweaks you have to apply and the lsecupdate binary is different. Of course, if you find a real uis8581firmware it might be better.
1. Only if you have problems, go for a mod.
2. If you do not even know the brand/reseller of your unit, how can anyone advice for better firmware? Next to that: 98% of the firmware for FYT units is identical. Only some differences in "theme" for the launcher (but you use Nova anyway). Your app firmware is of December 2021. There is newer available, but that means it will wipe your system. So far I only flashed newer kernels (read the uis7862 Q&A, etc. thread) hoping they patched the kernel with Android bugfixes and security improvments in the newer kernels, and keep the rest as it is (no AllAppUpdate.bin), thereby also keeping all my settings and 3rd party apps. Again: If you don't encounter errors, there is no need for other firmware. Note: do not flash T'eyes firmware. It is not bad but it does contain quite some restricted firmware making your unit perform much worse.
3. I use Nova as well and I am happy with it. No questions here
4. Do you have a CAN-bus? if so, they are hard-coded and you can't reprogram them unless you use something like my "FYT HW OneKey" app that lets you reprogram part of the buttons.
5. That's correct. The android level is determined by the SDK. The Android version setting (for easy version status) is nothing more than a property and can just as easily be set (or faked) to 17, 31 or 145, etc..
Click to expand...
Click to collapse
Wow thanks for the reply mate you're an absolute damn legend
I'm quite ok with how it functions I don't have any said errors or problems. Good to know some of this info really I mean it thanks again.
Mine is faked however I don't really mind or care I didn't think the components would have been able to power this soc!
I don't have any functions for a cheap Chinese thing it does it job with Waze and music. And occasionally YouTube for a podcast.
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there

iionas said:
Yes sir I do have canbus so I'll be looking for that tool asap. I wanted to reprogram a button for Spotify next song. Nothing special!
Is there ever a time where I should be updating the firmware at all? Like sau year down the track? Or do they stop servicing them?
I was hoping there was a hal9k mod for this one too but I lucked out there
Click to expand...
Click to collapse
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.

surfer63 said:
In the settings you can reverse next-previous and/or Vol-Up/Vol-Down if your app/system reacts the other way round, like Spotify does for example. You do not need my app for that.
Like said: so far I have only updated the kernel (6513_1.zip) and nothing else. I only use the unit for navigation, radio and music. Note though that those FYTs still contain an error where they erase your Google contacts if you sync them. It seems the latest T'eyes/Joying firmware doesn't do that anymore, which als means that the somewhat slower resellers like Mekede etcetera should follow soon. (but I don't call from my car. Maybe twice a year)
All those mods are for MTCD/E models, not for FYT.
The only FYT mod is made by @gordgelin but only for real T'eyes models (like mentioned :some T'eyes stuff only works if you have a T'eyes id on your unit).
Tyukta at 4pda makes "a best of" mod where he simply takes the latest kernel and combines it with (what he considers) the best apps (themes actually) from other firmwares (the AllAppUpdate.bin) and he himself also does some theming to apps.
Click to expand...
Click to collapse
Cool well thats pretty straight forward I dont have any issues with it, so Ill be leaving it for now and just using your tool for re-programming buttons.
The infamous google contact deletion happened to me, i managed to restore which is really good, however it was annoying. It would of been really good if the google phone app would of worked with it over BT, but it does require a sim (the unit goes support 4g however i dont use a sim).
Ill be ready over the guides today to see for your tools

Hi Gentlemen,
I bought same FYT few days back, succeeded with installation to old MB w211. However i faced problem with Bluetooth connection. It seems like Bluetooth driver or module in head unit is not working properly. I tried to reset factory settings, but still have issue with Bluetooth connection.
Could you please be so kind and share your advice on that. Maybe firmware update is required, but i don't know where to find it out.
I would really appreciate your assistance. Sorry for my English, i am not native speakers.
Thanks in advance Gentlemen.

Hi, is anyone willing to share about what kernel to download? And my Bluetooth is not working recently and shows “null”. Help!!! My android SDK29

how to get the firmware for this unit.

how to get the firmware for this unit.
Uis8581A

saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
One reviews forum or contacts seller.

saifulmly said:
how to get the firmware for this unit.
Uis8581A
Click to expand...
Click to collapse
This unit? Which unit?
That is like: "My phone has a snapdragon-750 cpu". Which firmware should I download?
(select about 25 brands with 200+ models).
Be more specific.

I have a k4811 (8581) and was wondering if there is a way to fix adb to make it work? enabling it in dev options does nothing (the device isn't detected when a laptop is plugged in to USB and adb wifi also rejects connections).... will the FYT MC app work on this device? ex. root button?

Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller

fabius12 said:
Hello everyone, I bought a UIS8581A and I also have problems with bluetooth where I can't connect my ELM327 adapter because I can't even open the bluetooth settings to do so.
The salesman who sold me the radio can't help me right now. Can anyone help me?
Otherwise I have to return the radio to the seller
Click to expand...
Click to collapse
You should have an app called "Bluetooth" (not inside settings, but an actual preinstalled app).
What happens when you open the Bluetooth app?

I continue the discussion here which talks about my problem with the OBD module
OBD over WIFI and the Internet
I am a recent FYT user on UIS8581A, Android 11 (fake). I have a sim card connected to it that provides internet. When I connect WiFi with OBD, internet connectivity is broken. WiFi without internet has priority in data transmission over SIM card...
forum.xda-developers.com

Yesterday I tried to pair by changing the radio name, password and all the craziest tests I could think of but nothing.
My bluetooth screen is the first photo I attach
When I try to connect one of my three working ELM327 minis, nothing happens, I touch the symbol of the chain to connect, it asks me for the pin of the ELM module, I insert it (it is 1234), after a few seconds a message appears "pairing succeeded". But that's not true, because the chain symbol doesn't change, in Torque I don't see the module (try various versions of torque) and I can repeat the bluetooth pairing indefinitely but it never works.
Any app I use for bluettoth tells me that bluetooth is not working or can't be turned on. But if I connect a smartphone it works.
I do not know what to do
Anyone can help me?
Whats App Image 2023 03 08 at 10 49 16 — Postimages
postimg.cc

I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW. It appears to be completely dead apart from feeling warmth on the rear of the unit when I add power to yellow and red (power and acc) wires while it is grounded (black). I have an update.zip (1.2GB) and a full firmware (3.6GB) from the seller.
The part I am wishing to understand is this:
With the full FW uncompressed in an update folder on a USB stick's root, plugged into the 4pin usb port on the unit, I power the unit on and there is no indication of the USB stick being accessed (red LED on USB stick not lit). I have a USB-A to USB-A cable plugged into the second USB port (6 pin). When I plug the other end of the male to male USB into my laptop (up to date USB drivers installed) that is powered on, the USB stick's LED begins to flash as indication it is being accessed. The LED remains lit for several minutes and then begins to flash (appears to be random flashes). After about 20-30 minutes the USB's LED flashes in a repeating pattern. I have left this USB stick continue whatever it is doing for hours. After disconnecting the laptop from the USB, disconnecting the USB stick, and cycling the power to the unit, the unit is still bricked. Plugging the USB stick back into the 4 pin USB port (with power on), the USB's LED remains unlit indicating it is not being accessed still. Recycling the power to the unit does nothing. Only when I re-connect the USB-A to USB-A cable from the unit to my laptop the USB stick is accessed. Disconnecting the cable, the LED turns off. This is the only life I have witnessed since bricking the unit.
I am wondering why the USB is indicating it is being accessed, only when connected to my laptop.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Please don't reply, unless you have specific knowledge.
To all who don't reply, thank you for not wasting my time! It is appreciated...

@S2artb What comes to mind is how you are resetting your unit. I'm not sure if this will work and/or if this applies to your unit. There is a reset hole in the top left of the display. I'm not sure of the exact sequence, but you can try that. Search this or the forum that applies to your unit, if this forum doesn't apply to yours.

S2artb said:
I am trying to understand what is happening with my bricked UIS8581A unit.
I flashed the wrong FW.
Does anyone know what is going on here when I connect the unit with my laptop and the USB's LED indicates it is being accessed?
Click to expand...
Click to collapse
Do not connect your unit with the laptop. This will not help at all.
Which unit do you have? This is the FYT forum and there are many UIS8581A units that are not FYT.
Which wrong firmware did you use?
You tell us absolutely nothing that we need to help you.

Help me to Identify what pins to short (amlogic tv box)

I have an amlogic tv box that i want to revive. Its a generic chinese box.
With a lot of help of the community i managed ti identify the board, Is the one from this link:
https://www.szjytx.com/?id=13299
The one from the link (as you can see by the photos i posted) is the same one physically. The only thing i couldn't identify was the real processor (the manufacturer was faking it), because when i removed the heat ink, the painting on the chip got erased.
So i started to experiment with it.
I couldn't find any ROM for the processor that that chinese page says (S905L-B)
After various tries , I could install twrp (for the s905w processor)
The first working one was one for the "x96 mini", it worked but it only showed 1/4 of the total screen.
Then i tried one for the tanix tx3 mini, and it worked like charm, i could backup and restore roms.
---------------------------------------------------------------------------------------------------------------------------------------------------------
After that introduction, here's the problem:
The box has no reset button, so the only roms i could try were from twrp update zips.
So, as i did with the recovery, i tested first installing a "x96 mini" rom, and i had the same result, a bootable rom showing 1/4 of the screen.
The next was to try a "tanix tx3 mini" rom, and after the flash it never booted again (not even the logo), so i think is bricked at bootloader level. Te power led powers on, but no image.
I think my only hope to revive it is to flash a rom trough the amlogic burn tool.
The problem is that the device can't be recognized by the tool.
i only had partial luck /really strange behavior) with a malfunctioning usb male to male cable, testing it sometimes it got recognized for a few seconds (of course i couldn't install any rom with that little gap).
With a brand new male to male usb cable it gets nothing.
This new cable works, because the power led of the device turns on, but it doesn't get recognized by windows or the tool.
I know that there's a method to force the box to go to download mode, by shorting two pins, but i cant tell what pins are the correct ones, o some hint to it.
I attached pictures form both sides of the board.
https://imgur.com/a/EBYsTYk
Thanks in advance

I am having the same problem. Did you solve the problem?