Hey,
Some Time ago I bricked my Android Head Unit by flashing the wrong firmware, because the manufacturer did not provide the correct Firmware.
Since then, the screen stays black and I am not able to enter recovery Mode to flash the correct Firmware (which was provided after long discussion).
I also tried to connect the Unit to PC via USB, but the Device is not recognized.
Is there any way to enablbe USB to flash the firmware via fastboot?
Kind regards
Fisatec
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?
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?
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
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
Hi is there anyone on these forums that can repair one of these chinese units
I have one of these https://www.ebay.co.uk/itm/384770479698 in my 2006 Merc. its a MTK8667 Android 11 based unit. FF_866X is the device name, i'm sorry I do not know the MCU
I was sent some update files from the seller https://we.tl/t-UeDC40i6Ul XRC-8667 升级软件 Q腾实UI多合一-国外-1280x720_v32_20220223
during the update process it copied the superimage ok but then something came up in red but it came up to a kind of recovery and said erasing... it then rebooted it gets to the car logo screen, before android screen then goes to a blank screen with the following in bottom left corner...FASTBOOT MODE and wont go any further
I have pressed RST then two fingers on screen until i get "detected" but all i get is the same fastboot mode again,
I have redownloaded and extracted the firmware and reformatted my usb drive to fat32 and tried the whole process again and tried in both usb slots but no sucess.
I have obtained other mtk8667 firmware files 8667.bin and 8667.upd from this topic https://forum.xda-developers.com/t/firmware-junsun-v1-8667q-8g-128g-vhd-qled.4405475/ on this forum but I have tried many different ones and it just wont read the usb, still just goes straight to fastboot mode....is anyone able to help me I have messaged the seller but no reply
So far I have tried about 7 or 8 different firmware versions, the sellers own, some junsun versions, ossuret versions even xtrons versions(all in correct format of 8667.bin and 8667.upd on root of usb formatted to fat32 but it does not read the usb.
The usb slots are still working as I can plug my phone in and it charges but the unit does not seem to have a full recovery mode
I have tried using a program called adb and fastboot on the computer but will not connect to the head unit
I have manually installed MTK drivers to the computer and tries a program called magic thunder but again would not connect to the unit.
I have tried to find a memory dump online but nothing, all I can find for mtk8667 is firmware consisting of 2 files 8667.bin and 8667.upd
I have now removed the unit from the car so i tried removing everything but 1 usb slot and removing the power for 10 mins before powering up and attempting to flash again
So i think i'm in need of expert help, so i'm looking for a repair shop, or person that can take the unit and hopefully get it working, more than happy to pay a fair fee and to post it to you, or if you are within a couple of hours travel from Yorkshire(Leeds area) I will happily come to you