hi,
bought ISUDAR 2DIN with Android Oreo 8.0 (PX5) couple of days ago and the wifi keeps turning off after couple of minutes. No matter if I'm using my phone as hotspot or connecting to my home wifi.
Any ideas?
thanks
I,ve bougth this model too, and in mine it works well.
Have you tried a factory reset
Hello, I also bought headunit from ISUDAR May 7 and I have the same problem with WiFi. I tried the factory reset, changed the MCU (I have uploaded all available) and the problem still occurs.
After turning on the headunit WIFI turns on for a second, then turns off. Again, manually switching on WIFI results in a temporary switch on. After a moment, the switching off takes place. Yes over and over.
I also noticed that when WiFi turns off automatically, it is removed from the SD Card and USB system. After 2-5 seconds, the SD Card and USB are connected again.
Did you solve the problem because I see that this is not an isolated case?
I have too problem
https://forum.xda-developers.com/showthread.php?p=77727622
New ROM link for this?
model
px5 (1024x600)
core version
4.4.93+
[email protected] #343
Sat Sep 15 11:41:25 CST 2018
build number
px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180919.210032 test-keys
MCU verse
MTCE_GS_V2.94_3
Sep 13 2018 11:26:51
CPU
8 core 64-bit CPU Coretex-A53 @ 1,5G
Memory
3891 MB
Odesláno z mého Le X821 pomocí Tapatalk
Hi guys
i have a Sofia 3GR Head unit that out of nowhere i decided to upgrade the firmware!
so i searched the internet and installed the first one i saw! "JOYING Intel SOFIA Android Car Stereo Software Update".
the process was too easy to hesitate!
after the installation i got a yellow error bar in top of the screen "UI and MCU does not match". (OS works smooth and fine though)
so, i started wandering in the web to find a solution , meanwhile i figured out that my old firmware was Ownice C300, and the Head unit is VoxX (according to the Web page that sells the head unit in my country).
i tried to download and install the firmware that page provided.
i think i have to enter recovery mode to install it, and this unit has a reset button that when i press it resets the head unit immediately! and no repair menu after 3 time! so no chance to enter recovery i think!
when i presses (Alt+PrtSc+i repeatedly) with USB Keyboard black screen appears that says:
ADPI mode V1
Sofia 3.0
error waite here ....
or something like that! i dont know if it is recovery mode or not.
the unit model is:
Quad Core CPU 4G, MTK
MT3561 Quad Core, ARM A53 (64Bit), 1.3GHz RIM
1 GB Ram
built-in 16 GB of internal memory,
and upgradeable to Android 8.2.1 Dual-Core
1024*600 resolution.
i liked the Ownice firmware much more, or at least the yellow error goes away in joying!
does Ownice has a easy to install Firmware like Joying?
any suggestions?
My device is a 8227l ALPS demo but doesn't seem to be a run of the mill setup. Getting this device customized has been taking me weeks of frustrations and headaches but it's getting there. My info from my head unit is as follows:
Kernel Version: 3.18.79
HMI: TSKJ.D.Q.F.3.C02.2019.11.08.08.30
MCU: TS907.190108(h)
MEDIA: HC_V2.0.0_190923_1100_e(v1.71)
BTV: BT.19.11.06.1230(c0:81:35:20:d1:a6 -my mac address for wifi/bt)
If you are trying to connect to your 8227L, and you cannot get your computer to recognize for flashtools (or debugging), this variant board has different USB config. Most guides will say to power down and remove ALL connectors from the radio, except the 4pin USB port. In this model, you will actually connect to the 6 pin unit, and will need power to flash to the board.
For regular ADB use, while unit is powered on, plug the USB into the 6pin plug (not the 4pin).
(Update: it appears that if you change USB in the system menu, it changes the default ADB USB. For example, when on USB value 0 ADB was the 4pin, but when on 1 it was the 6pin.)
Basically to identify your ADB, plug your PC in while the unit is on. To identify if it the flashable port, power down the unit while still connected to USB. Then Power on the unit. If you get a device connection sound in your OS while the unit powers on but before the logo appears, you are using the right connection.
to use flashtools like in the guide for other 8227L units, like the amazing one by @ExtremeMOD here leave the USB connected, and the power connections. Either poke the reset button on the front of the unit, or cycle the power to the unit.
After whatever you are doing with flashtools, the unit will display a lit but black screen. This is normal. After the process is done the connection will drop (you'll hear it on your computer if using windows). Then unplug USB and either power cycle or hit the reset button.
Of course, disclaimer this may not work for your unit. Please see pictures below.
also, in need of a little help myself. This board does not appear to have testpoints, the reset button is truly a reset button only and have tried shorting the C17 resistor. I have not been able to get the device into recovery with any physical interaction to the unit, only through ADB commands. Also tried USB keyboard. Tapping screen while powering up does go to the USB flash menu ("detected"). Underside of the board has no chips or testpoint pads. Does anyone have any ideas to control the unit when in the bootloader or recovery? See update
Markings on the board come up with NO results in google or here.
XPH-806B-DSP-MB
E353226
display board: XPH-806B-10.1TFT-V01
Unlock Bootloader:
BEFORE BEGINNING ANYTHING ENSURE YOU HAVE MADE FULL BACKUPS/DUMPS/SCATTERFILE MADE
First you need to get to the "test point" on the board. It is covered by the heatsink. You can either pry off the heatsink cover, or remove the whole heatsink frame by removing the solder. I removed the whole frame, but popped the cover off first as I needed to inspect the board for other points.
Note: on this unit you do NOT have to short the test point to use SP Flashtools at all!!! This is for bootloader unlock only!
If you want to remove the cover only, get a small but strong flathead screwdriver, wedge it in between the cover and frame and press in while twisting to separate the cover. Of course be mindfull of how much pressure you push and your angles. I wound up actually removing the whole front display and ribbon cables to get to a better angle.
With the cover removed you will be able to see the test points. One is Vol down, and the other is ground.
You will need to short this pin to ground to unlock the bootloader in fastboot: See steps below. You do not have to fickle with tweezers if you don't want, It just needs to be grounded when the time comes. I used my screwdriver when I had the frame still on, making sure to touch the frame and the test point.
To test your test point: when unit is powered up and running, short this pin momentarily, volume should go down.
The process to upgrade this unit is very fickle and the steps have to be done in the proper orders.
They are: Get memory dumps, Get root, unlock bootloader, install TWRP, then have fun.
To unlock Bootloader:
-Do NOT flash TWRP yet. Factory recovery needs to be installed.
-Root device first (I was never able to get magisk to work, even after unlocking bootloader, so SuperSu procedures worked for me)
Ensure you have the proper settings in the system menu (8888 menu: Protection OFF, Install ON, OEM unlock enabled, etc) and in developer tools (unlock bootloader)
While unit is powered on and loaded:
adb devices (ensure you are connected)
adb reboot bootloader (unit should reboot to FASTBOOT mode)
fastboot devices (should show device)
fastboot oem unlock
You should see this screen:
Now short your testpoint. Just for a second. Youll get an update in command prompt and on the device.
fastboot reboot
You will get a warning:
"Orange State:
Your device cannot be trusted and will restart in 5 seconds"
Don't panic!
Let it do it's thing. It will restart a couple of times. Your computer will go a little crazy with device connects and disconnects. It will restart twice, then will automatically start to factory reset. Root may not be enabled and may have to do it again.
To verify bootloader is unlocked:
adb reboot bootloader
fastboot getvar all
A wall of text will display. At the bottom you should see:
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: 8227L_DEMO
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.115s
If unlocked is set to yes, congrats, you unlocked your bootloader.
Now you will continue to get that orange state message you can ignore it or fix it.
To fix it follow this guide
Or you can try my edited LK file attached. Flash with SP tools with your scatter file.
I was able to get TWRP installed however I used a ported ROM and the touch is inverted. After I get it fixed and this whole unit polished the way I want I will upload the files and update the instructions. I know it's all a little scattered right now but it's a work in progress.
Hey @h1p1n3
thx for the tutorial, you rock !
i got some issures on my device
8227L
Kernel Version: 3.18.79 (gcc version 6.3.1 20170404 Linaro GCC 6.3-2017.05)
HMI: BMW.D.Q.F.2.01.2020.06.11.09.30
MCU: TS907.190518(H)
MEDIA: HC_v2.0.0_200612_1530(v1.71)
BTV: BT.20.06.01.1430(CO:81:35:10:97:17)
i followed the instruction from @ExtremeMOD (cool tutorial ty man) and made the backup with SP Flashtools
but when i tried to install my old backup some error accured.
Now my headunit is stuck on a blackscreen.
when i tried to put the usbcable ( 4 & 6 Pin ) i hear no connection sound or get no notification from my pc.
i also tried the RST button but my headunit only start the background led.
have you any idea to fix this problem ?
bimmer_993 said:
Hey @h1p1n3
thx for the tutorial, you rock !
i got some issures on my device
8227L
Kernel Version: 3.18.79 (gcc version 6.3.1 20170404 Linaro GCC 6.3-2017.05)
HMI: BMW.D.Q.F.2.01.2020.06.11.09.30
MCU: TS907.190518(H)
MEDIA: HC_v2.0.0_200612_1530(v1.71)
BTV: BT.20.06.01.1430(CO:81:35:10:97:17)
i followed the instruction from @ExtremeMOD (cool tutorial ty man) and made the backup with SP Flashtools
but when i tried to install my old backup some error accured.
Now my headunit is stuck on a blackscreen.
when i tried to put the usbcable ( 4 & 6 Pin ) i hear no connection sound or get no notification from my pc.
i also tried the RST button but my headunit only start the background led.
have you any idea to fix this problem ?
Click to expand...
Click to collapse
Did you try his recovery video steps? Your unit may not allow writing without the test points shorted. Here's the video.
If there's not test points under your heatsink cover (although there should) they may be one of these. I would check for voltage before poking around.
h1p1n3 said:
Did you try his recovery video steps? Your unit may not allow writing without the test points shorted. Here's the video.
If there's not test points under your heatsink cover (although there should) they may be one of these. I would check for voltage before poking around.
Click to expand...
Click to collapse
To add, some units require to be connected to power 3 seconds after the USB cable is inserted.
Try that first before attempting the Test Point method.
In general, Hizpo units are notoriously troublesome to deal with.
Hey guys!
thanks for your quick answer's
@h1p1n3 i tried the test points you showed me but the headunit didn't respond to this method.
I also tried some other points ( mic + mic - etc.)
But I got no reaction from the headunit.
On the weekend I will try to remove the heatsink from the motherboard and look for more testpoints. Can I just easily remove it ?
@ExtremeMOD
I tried all possibility ( usb 4 pin, usb 6 pin, with powercable, without powercable and some different points to shortened) But my unit didn't response. Maybe I get another way to get new firmware to this unit without SP Flashtools.
Hizpo don't like to get flashed I think
Just for the worst case.. do you know a headunit with easy ways to flash ?
I hope to find the test points I'm looking for to fix the problem.
bimmer_993 said:
Hey guys!
thanks for your quick answer's
@h1p1n3 i tried the test points you showed me but the headunit didn't respond to this method.
I also tried some other points ( mic + mic - etc.)
But I got no reaction from the headunit.
On the weekend I will try to remove the heatsink from the motherboard and look for more testpoints. Can I just easily remove it ?
@ExtremeMOD
I tried all possibility ( usb 4 pin, usb 6 pin, with powercable, without powercable and some different points to shortened) But my unit didn't response. Maybe I get another way to get new firmware to this unit without SP Flashtools.
Hizpo don't like to get flashed I think
Just for the worst case.. do you know a headunit with easy ways to flash ?
I hope to find the test points I'm looking for to fix the problem.
Click to expand...
Click to collapse
If you look at our signature you can see what models are supported for our SuperMOD packages and they are very common.
You are more than welcome to PM us for buying advice.
I am new here but not sure where to ask. Sorry if I am in the wrong chat.
Like to check if it is possible to update my player android version?
TIA
Roy15C said:
I am new here but not sure where to ask. Sorry if I am in the wrong chat.
Like to check if it is possible to update my player android version?
TIA
View attachment 5461195
Click to expand...
Click to collapse
It is possible but it won't improve anything unless you can find a custom firmware package. If you are located in UK, we can "borrow" your head unit and create one. Otherwise, search for YT3518CH on the internet. That's your model.
Hey guys!
I removed the backplate and it seems there is no test points.
I messaged the seller maybe he has a clue where to find the test point ( or he can restore my unit )
Hi to all ...
Has any of you got similar motherboard and schematics or picture of it - my unit is ALPS FF5000/firmwares -8227L
Model 8227L
CPU AC8227L QuadCore 1,2 GHz MTK8227L
RAM DDR3 1 GB
ROM 16GB
IPS 1024x600
GPS MT6625L
Radio TDA7786
DAC TDA7851L 4x45W
Wi-Fi MT6625L 802.11n
Bluetooth MT6625L 4.0
Android 8.1.0
Kernel 3.18.79 (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) [email protected] #90 Fri Sep 14 11:04:34 CST 2018
Build alps-mp-01.mp5
Custom build alps-mp-o1.mp5
I need it for buying right RADIO chip for my device, I was aiming at NX6686 I have now TDA7786
h1p1n3 said:
My device is a 8227l ALPS demo but doesn't seem to be a run of the mill setup. Getting this device customized has been taking me weeks of frustrations and headaches but it's getting there. My info from my head unit is as follows:
Kernel Version: 3.18.79
HMI: TSKJ.D.Q.F.3.C02.2019.11.08.08.30
MCU: TS907.190108(h)
MEDIA: HC_V2.0.0_190923_1100_e(v1.71)
BTV: BT.19.11.06.1230(c0:81:35:20:d1:a6 -my mac address for wifi/bt)
If you are trying to connect to your 8227L, and you cannot get your computer to recognize for flashtools (or debugging), this variant board has different USB config. Most guides will say to power down and remove ALL connectors from the radio, except the 4pin USB port. In this model, you will actually connect to the 6 pin unit, and will need power to flash to the board.
For regular ADB use, while unit is powered on, plug the USB into the 6pin plug (not the 4pin).
(Update: it appears that if you change USB in the system menu, it changes the default ADB USB. For example, when on USB value 0 ADB was the 4pin, but when on 1 it was the 6pin.)
Basically to identify your ADB, plug your PC in while the unit is on. To identify if it the flashable port, power down the unit while still connected to USB. Then Power on the unit. If you get a device connection sound in your OS while the unit powers on but before the logo appears, you are using the right connection.
to use flashtools like in the guide for other 8227L units, like the amazing one by @ExtremeMOD here leave the USB connected, and the power connections. Either poke the reset button on the front of the unit, or cycle the power to the unit.
After whatever you are doing with flashtools, the unit will display a lit but black screen. This is normal. After the process is done the connection will drop (you'll hear it on your computer if using windows). Then unplug USB and either power cycle or hit the reset button.
Of course, disclaimer this may not work for your unit. Please see pictures below.
also, in need of a little help myself. This board does not appear to have testpoints, the reset button is truly a reset button only and have tried shorting the C17 resistor. I have not been able to get the device into recovery with any physical interaction to the unit, only through ADB commands. Also tried USB keyboard. Tapping screen while powering up does go to the USB flash menu ("detected"). Underside of the board has no chips or testpoint pads. Does anyone have any ideas to control the unit when in the bootloader or recovery? See update
Markings on the board come up with NO results in google or here.
XPH-806B-DSP-MB
E353226
display board: XPH-806B-10.1TFT-V01
Click to expand...
Click to collapse
Hello. I have a problem with my device. I have the same software as you. Unfortunately, I got a black screen and I cannot flash when I connect it, it says "usb device not recognized". I installed the drivers according to the ExtremeMod guide. I take usb 4 pin and 6pin. The effect is none. I've tried everything and nothing comes out.
bimmer_993 said:
Hey guys!
thanks for your quick answer's
@h1p1n3 i tried the test points you showed me but the headunit didn't respond to this method.
I also tried some other points ( mic + mic - etc.)
But I got no reaction from the headunit.
On the weekend I will try to remove the heatsink from the motherboard and look for more testpoints. Can I just easily remove it ?
@ExtremeMOD
I tried all possibility ( usb 4 pin, usb 6 pin, with powercable, without powercable and some different points to shortened) But my unit didn't response. Maybe I get another way to get new firmware to this unit without SP Flashtools.
Hizpo don't like to get flashed I think
Just for the worst case.. do you know a headunit with easy ways to flash ?
I hope to find the test points I'm looking for to fix the problem.
Click to expand...
Click to collapse
Hello. I have the same problem as you. Laptop can't see any usb or 4 pin or 6 pin. Have you solved this problem?
Here you have recovery files I got from chinese store AUTOTOP when asked from another account (on which they havent blocked me)
Android 8.1 with "bmw os 1.09"
BMW-8227L_demo.zip
drive.google.com
There are instructions how to proceed recovery but shortly: You have to format pendrive to fat32 and put folder CKXUPG on it. Like for example E:\CKXUPG\~files that are in CKXUPG~. Then You should plug that pendrive in one of USB cables from radio (I dont remember which one, I tried both till success). There is a reset button on left side of radio that you can use for trying another cable, you dont need to unplug car battery or whatsoever
There is no newer version than Android 8.1. All androids 8+ works worse than this one and are faked androids 10....
I also have version of "bmw os 1.26 with fake android 10":
BMWID6_OS_1.26--10.0.zip
drive.google.com
and version "bmw os 1.31" but I think i didnt manage to update to that version:
XRC_BMW_OS_1.31.zip
drive.google.com
p.s. from what I remember if everything is OK there should be some console output running in left top corner right few seconds after booting. If it doesnt happen you get stuck on bootlogo and have to reset device.
BTW. dont try to use Media button or "Your BMW tab" untill you configure headunit in factory settings (few times click on android version and then inserting 8888 code. If you dont have CCC/CIC and you selected wrong options the headunit is trying to display signal from CCC/CIC and you're basically stuck.
hello do you have the mcu update please cordially
Hello All,
I am in need of assistance with my 13.3' HA2208-Scout head unit Model: PX6 running Android 10. I have had it for a little over a year with no issues. I shut the vehicle off when I got home, and the next day when I went to leave the side screen buttons stopped working, and the touch screen was unresponsive.
I placed the unit in recovery mode and reset the cache with no change. I then completed a factory reset with no change. After reviewing the logs I found that I am getting a:
GTP-Error I2C Read: 0x0847, 1 bytes failed, errcode: -6! Process reset.
It will do this error and fail 5 time, then presents:
<goodix_ts_probe>_4411 I2C communication ERROR!
<goodix_ts_probe>_4502 prob error !!!!!!!!!!!!!!!
CPU: Rockchip RK3399, running Linux 4.19.111
I have emailed Dasiata 15 times with only 1 response asking about my order number, and can not seem to get any technical support. I have searched the forum with no luck finding this same issue so I am hoping someone may be able to assist. This is a completely stock unit with no modification to hardware or software.
Thanks,