Related
Hello,
I have an android unit as;
allwinner a20 cpu, 1gb ram, 16Gb rom.
MCU>>>STM8S207___RBT6___99ODH-VG___NYS99 603
TDA7388
TEA6851
I rooted my device and with some 3rd app, booted into recovery and there is just android logo. No recovery page, then boot into android.
So i decided to upload twrp recovery.img (from one webpage) file to my unit.
I uploaded the recovery.img file with dd command from terminal emulator. Now my device is in black screen, no boot into android.
Anyone can help me? any idea what to do?
I just have update.zip file from seller company.
In dark room whan i connect the head unit to power, there is nothing on the screen. Just dark screen.
Thanks in advance.
Hello,
I tried to access to the device via ADB but i cant.
I prepared a usb male to male cable and pluged in to my laptop.
When i power on the device (connect b+, -, acc), there is no backlight of the LCD screen in dark room. Also there is no detection the device by windows.
Last time i used mobile uncle tool program to enter the recovery. The device got into dark screen and there is nothing.
I found a topic on forum. For another device someone found a way to reset the mcu, then the device boots into android.
There are some CN and JP on the mainboard. May be they are used for reset the unit. Anybody any idea?
Hi,
I Bought this android head unit a month ago. After having some problem with apps i decided to set head unit to factory settings. After that i got stuck on bootloop
I trie reseting it via RST button but, that didn't helped. So i think i need somehow to get into recovery for data wipe. None of button combination leeds me there.
Does anybody now, how to get into recovery mode ?
i Have video uploaded into youtube, but as im new in this forum, i can't paste it here.
youtube com/watch?v=_zYjHY9D0kc
Tried:
- various button combination (reset, reset + power, etc)
- Connect USB male<->male connector to head unit and PC. No response, pc wont find new device (android adb)
- Solder wires to pins on mainboard GND, VCC, D+, D- and connect to pc. No response
- contacted seller. He aproved that android is stuck and head unit needs to be restored from update (or data wipe out). Seller asked me for my email, but its already two weeks after this problem and still no instruction what to do.
Please HELP!!! ((
Isudar h53
hello did you solve the problem? I have the same
Hello!
I've recently got a Silverstrong Android 9 Head Unit: https://www.aliexpress.com/item/32822937592.html?spm=a2g0s.9042311.0.0.328e4c4dWZb7Fi
Can someone help me on how to get adb access or a custom recovery (mainly for rooting purpose)?
I have to mention that I've tried connecting a notebook with adb via and USB cable (male USB type A to USB type A), but it seems nothing happens. I can tell that the unit's USB ports are working for USB sticks.
I have also tried some combination implying the reset hole present on the front, but I couldn't make it work.
Any help is appreciated! Thanks!
Edit: I have to mention that the unit packs a MediaTek MT8321M if it matters.
Just an update: I have followed the instructions provided here for rooting: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740 . Everything went well until I tried to reboot the device. Now it is stuck in a bootloop (it passes the kernel bootlogo but it is stuck on Android bootlogo) and I really need to access its recovery. It would be my only hope to try to unbrick it. Unfortunately the only physical switch of the unit is just a reset hole on the front which will cut the power right away (tried multiple pressing combinations, none worked). I really need to enter recovery mode and I am pretty desperate, so any advice is welcome. Thanks!
I couldn't make it boot into recovery mode, but it did boot when I placed on a usb stick a file named "ZQ_MTK1B_UPDATE_HeXinDa_EN_8003_08152051.zip" and then it started to flash it automatically. After the flash completed, the unit recovered from bootloop, but now it seems there is no sound and no radio. I posted all of this just in case somebody ever will have to deal with same kind of trouble. It seems the unit is actually branded as alps ZQ8003 and I will ask the seller for some firmware/more technical info.
Hi, I have the same problem. Did you make it?
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?
Hi all, a need help. After an unsuccessful update, I received a bootloop. There are no physical buttons on the device. Found instructions for recovery through ANDROID TOOL. I connected it to the computer in maskrom mode, but I can’t find the firmware that needs to be uploaded in order for the device to work. Share a dump that suits me or give instructions on how I can restore the device.
They're all there in the MTCD forums.
Thanks for the answer, but all I found is different ota update.zip. And my device is loaded only in maskrom mode.
That's why I'm looking for a full recovery version.
Hi, you have to use the IMG file that contains the recovery and then update normally via OTA. For example, the IMG is:
CHS2_RK3399_10.0_IMG(20200424)
HCT7_rk3399_10.0_IMG(20200415)
OLS_rk3399_10.0_IMG(20201012)
Яндекс
Найдётся всё
disk.yandex.ru
I recommend reading this thread, you will find answers to your questions here:
[MTCD/E] Android 10 upgrade using official Free tools
To upgrade a MTCD/E PX3, PX5, PX6 from Android 6+ on using official Rockchip free tools - a reminder, bringing together multiple threads. First note - if coming from Android 6 - early versions of Realtek dual BT/WIFI (type 2) are not supported...
forum.xda-developers.com
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
s.danyliak said:
I downloaded the firmware, I start to flash it and every time it breaks off by 50-60%. I used different firmware from the attached ones and different versions of AndroidTool. And different driver versions. Log attached.
Click to expand...
Click to collapse
Erase first
I did, first cleared, reboot and firmware. The result is the same I read a lot of documentation, they wrote that there may not be enough power, but the power supply is 5A.
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
s.danyliak said:
I noticed that the device turns itself off after a couple of minutes of operation. Possible overheating! I will check it.
Click to expand...
Click to collapse
I had the same problem I bricked my headunit (rk3399 PX6 Android 10) trying to recover root after updating magisk to 25.1 went into maskrom mode but device lost connection to my PC and flash fails at different percentage.
Cause ended up being the adapter i was using to power the device I used 12v 2A adapter
After switching to 12v 10A adapter it finished flashing. BUT make sure the chip has cooling like a heatsink or it will overheat during flash.
I changed the power supply to 10A. Installed cooling. The result is the same. The device reboots even if nothing is done.
Have you tested another USB cable? @s.danyliak
I have tried two different cables. But I connect via usb which is from the device kit and also the usb a - usb a cable is possible in this problem. There are also only 4 contacts, and for otg you need 5. I did not find information on the board I attached the photo.
Does anyone have any ideas ?
Ask seller for schematic and share here for feedback
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
s.danyliak said:
So I was able to achieve some result and broke everything even worse. In maskrom mode, I flashed boot. And was able to see the device as fastboot. But my joy did not last long. After rash actions, I flashed the wrong boot and now I can’t enter maskrom as I did before by closing the contacts on the keyboard. Approximately as in the photo below. The question is, how can I force him to enter maskrom mode?
Click to expand...
Click to collapse
Short the two pads while powering on. Lift short after powering on
I tried, I can no longer enter maskrom with this method