Develop Bugs

MDA Pro/HTC Universal Help!!!!!!!!!!!!

Tried to upload the software on my MDA Pro and all of a sudden the screen on the MDA goes blank. I've tried master reset and i press 0 and it says clearing or whatever. Then it goes to the USB/Serial Screen and it reads v1.01 at the bottom. What do I do?

Hi, could you please post some more details? e.g. Which version was originally on the Universal and which version did you flash....
Cheers
Michael

Hi,
You just need to run the Upgrade again. As long as it says USB when you have it connected, no harm is done.
Cheers,
vma

No...There is definately some damage done. Its stuck on the boot load screen Where it says Serial at the top and V1.01 on the bottom. I just got it new in the box untouched and totally screwed it up trying to update the software to "UNI_TMUK_130114_130232_11003_WWE_BL101_Ship" I dont know what the original rom software was at all. It went to the grey screen that it is stuck on now and the power nor reset button works. The letters are still there in black on a grey non lit screen. Master reset (soft keys+rest) brings me to the screen but after i press 0 it says clearing now but goes right back to the serial/v# screen(boot load mode)....thats it...

Look it's not damaged. It boots to the bootloader. So long as it has the bootloader it's COMPLETELY recoverable.
1st thing you need to do is look here.
Scroll to the bottom and use method 2... It's a LOT easier and has saved my bacon many times!.
Psi

Possible hardware failure? Unable to boot - claims no OS and won't mount data etc

I think my phone may have had a catastrophic hardware failure but I am hoping not and maybe some of you clever people can help me resurrect it.
I have been running KK ParanoidAndroid without any problems for a few months. Yesterday I tried to boot it up and after showing the Google screen the screen went black then a single horizontal white line appeared 3/4 way down the screen. It stalled there forever so I pulled the battery and booted into TWRP recovery. It seemed to take a lot longer than normal but did boot into TWRP OK.
Once there however TWRP reported no backups, no OS and no storage space (0 MB). I couldn't mount any partitions,. I tried factory reset but it appeared to fail and just made the phone vibrate for a while. The log shows:
Unable to mount - /system, /cache, /data etc and something about no valid partition for MTP
Then the screen greyed out, faded to black and the phone powered off. Now it seems pretty much non responsive.
Any thoughts, other than bin it and get a new phone?
EDIT: It seems it hadn't powered off, just gone blank whilst attempting to wipe. I am now back in TWRP but the factory reset has failed. So. It seems I still have a functional recovery but not much else. Any help much appreciated.

In the absence of any responses I've searched a bit more and decided in the end to try to install a factory image using fastboot. I was holding out to see if there was any way I could save any user data but in the end that seems unlikely anyway.
So, I followed this guide: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
It all seemed to go smoothly until the final commend - after flashing the zip containing the system, boot and recovery images I got the error message "FAILED (remote: Write Fail)"
Hmmm...
Regardless I tried to finish off with fastboot reboot. As I hit enter the device screen faded slowly to a kind of washed out grey and the horizontal white line appeared on the display again (as before - see my first post). No further progress, and the device became unresponsive. I pulled the battery and tried to boot, and it bootlooped once to the Google screen before the screen faded to a washed out grey again and it became once more unresponsive.
After pulling the battery once more I can still get to fastboot, and I can now get to stock recovery, but otherwise I can't seem to get any further.
Is it toast??

Recovery Help Please

Just had an Eonon GA2160 head unit installed in my wife's car - unit was becoming unresponsive, and after contacting Eonon tech support they advised that i flash an updated firmware which they provided- this unit has all touch buttons plus the reset hole FYI - after flashing using the normal, non-recovery System Update in settings, firmware flashed but upon restart the unit is stuck on the lock screen and won't move on to full boot - I've hit reset using the pin hole on the front, and have tried to initiate a re-flash of firmware using the method provided by Eonon tech support (turning key to ACC, reset hole, turn key off, then back on again) - that method doesn't work - is there another way to get into recovery mode with these units? The only physical button is the pin hole reset -
I have an older Eonon unit with physical buttons and it's so easy to get into recovery mode if I run into any problems - I've googled and searched forums but can't really find any definitive method with the touch only units - thanks to anyone who can help -

Hey Bro,
Did you got any succes? I am stuck in this also. The screen is black only the touch buttons lights are ON. If i press the reset button the light is flashong on the button every 10 seconds and thats it...
How do i go to recovery mode?
Thanks!

georged84 said:
Hey Bro,
Did you got any succes? I am stuck in this also. The screen is black only the touch buttons lights are ON. If i press the reset button the light is flashong on the button every 10 seconds and thats it...
How do i go to recovery mode?
Thanks!
Click to expand...
Click to collapse
I was sent instruction by the manufacturer to get into upgrade mode - they sent me a link to the appropriate firmware for my unit, and had me unzip the files on a FAT32 formatted micro sd card - here is a link to a video they sent me to show how to get it going, but my unit just sat on the boot logo screen no matter what I did - manufacturer told me that the unit is bad, so I packed it up this morning and am sending back for replacement - keep in mind this method is get you into upgrade/flash mode - doesn't look like it gets you into recovery mode which was so easy on older models with actual buttons -
https://www.youtube.com/watch?v=mBtzL_iiA8Q&feature=youtu.be
If anyone else has any info about getting these touch control only units into Recovery Mode that would be awesome

Help recovering a "bricked" MTCE, PX6 (Xtrons) unit

Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.

So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.

I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.

Help identify ST LINK points in old Joying?

Unit is a Joying JY-UQ124 PX3 - https://www.amazon.com/gp/product/B00XGEYU26
No idea what specific MCU and all that it is now as I bricked it several years ago when I accidentally put the wrong firmware on when attempting to go back to stock from a Malaysk ROM, and now only get black screen on power on with front panel lights on. Can't get into recovery, attempting to restore via SD card isn't working - never seems to start loading from the SD, screen just stays black.
Bought a new radio, put this one on the shelf, and now I'm trying to recover it again via the ST-LINK. Except that the only 5 holes empty on my board aren't marked, and I suspect it may actually be an unpopulated USB connector.
The PX3 SOM is a card edge RAM style connector, so I can't easily attach to header pins there either.
Do I have options here for recovery, or am I SOL with a paperweight on my hands?

SOM or MCU, photo show SOM. What is bricked, som or MCU

I'm _guessing_ it's the MCU? If the SOM gets bricked, wouldn't I still be seeing _something_ on the screen at boot?
It's been a while since I played with this one last, but I seem to recall that I accidentally tried to push the update image from my Sofia unit into this one, and didn't catch my mistake until after it was too late to do anything about it.
But honestly, I'm not really sure what exactly is wrong with it at this point, nor do I remember exactly what I did to it prior, other than trying to roll back to stock from a Malaysk ROM, and it didn't boot afterwards.