"joying" radio stops after sleep - Android Head-Units

Hello!
I am a total noob at this so please forgive me if I don't give the correct information.
I have searched for this.
I appear to have successfully rooted my ebay head unit with this firmware. It is a Sofia 3GR, 2GB ram, Android 6.0.1.
https://forum.xda-developers.com/an.../rom-gtx-joying-stock-rom-2018-01-29-t3742482
Works Great!
When I remove the key from the ignition and leave it for 2 minuets the radio will not play/resume at all.
I have to go to go settings/apps/ radio and force stop it every time I want the radio to work.
The radio just started doing this BEFORE the firmware update. I thought it would fix it.

So looks like another one of those noob posts that no one can answer.
I have done more searching and found a few options.
There seems to be a "kill app" system on standby?
But I don't know if this is possible to change.
Replace radio app with another one?
I don't know which one will work
I am also struggling to put the Joying firmware back on.
Or buy another head unit. I have done this but still want to fix this one.
But also have to wait 2 months.

Icarusza said:
When I remove the key from the ignition and leave it for 2 minuets the radio will not play/resume at all.
I have to go to go settings/apps/ radio and force stop it every time I want the radio to work.
Click to expand...
Click to collapse
2 minutes? or longer?
The Sofia takes 4 minutes to fully close down to deep sleep. So yes, if you do this within 2 minutes you might have that behavior.
If you do that after approximately 4 minutes it should behave correct.
That is on the default ROM.
The gtxaspec ROM has Xposed. Check if Xposed is active.
As far as I can remember it comes standard with the XSofia Xposed module which I wrote for the most part. If not it might have the stand-alone nokill mod.

surfer63 said:
2 minutes? or longer?
The Sofia takes 4 minutes to fully close down to deep sleep. So yes, if you do this within 2 minutes you might have that behavior.
If you do that after approximately 4 minutes it should behave correct.
That is on the default ROM.
The gtxaspec ROM has Xposed. Check if Xposed is active.
As far as I can remember it comes standard with the XSofia Xposed module which I wrote for the most part. If not it might have the stand-alone nokill mod.
Click to expand...
Click to collapse
Oh my my! The famous surfer63 has responded to my silly little post!
I can confirm defiantly longer then 4 minuets as well and the radio ill not play after that.
Apologies but there is where I am more of a noob.
I do have an Xposed app on the head unit but am unsure of how to use it.
(Took me a year to find out where the RDS TXT was hiding) (so this is how slow I am)

Icarusza said:
I can confirm defiantly longer then 4 minuets as well and the radio ill not play after that.
Apologies but there is where I am more of a noob.
I do have an Xposed app on the head unit but am unsure of how to use it.
Click to expand...
Click to collapse
Do not underestimate your skills or overestimate mine.
By default all apps are killed, apart from a few very important ones. The radio app is not one of them and will be killed upon ignition off.
I really don't have a clue why it doesn't work for you.
You should be able to reflash the Joying firmware. The gtxaspec software uses a modified twrp recovery image, but after flashing the default Joying recovery is flashed back. Simply to make it possible to always go back to the Joying one.
- You did use the Custom.apk to prepare the unit for flashing the gtxaspec unit. Use this same app to check if you have the default Joying recovery in place. If not, use the Custom.apk to reinstall/reflash the standard Joying recovery.
- Which firmware version do you try to flash back?
- If the standard Joying recovery is in place and you have the correct Joying firmware, then please use a needle (or so) to reset the unit (RST pinhole). When the boot logo appears, reset it again. Do this 3 times. Then the leds will flash purple and your unit MUST start to reflash from usb-stick/SD-card.

surfer63 said:
Do not underestimate your skills or overestimate mine.
By default all apps are killed, apart from a few very important ones. The radio app is not one of them and will be killed upon ignition off.
I really don't have a clue why it doesn't work for you.
You should be able to reflash the Joying firmware. The gtxaspec software uses a modified twrp recovery image, but after flashing the default Joying recovery is flashed back. Simply to make it possible to always go back to the Joying one.
- You did use the Custom.apk to prepare the unit for flashing the gtxaspec unit. Use this same app to check if you have the default Joying recovery in place. If not, use the Custom.apk to reinstall/reflash the standard Joying recovery. Yes! as you described. (unless i messed something up I followed the instructions)
- Which firmware version do you try to flash back? This has always been my "safe firmware" as I don't have an original Joying https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view
- If the standard Joying recovery is in place and you have the correct Joying firmware, then please use a needle (or so) to reset the unit (RST pinhole). When the boot logo appears, reset it again. Do this 3 times. Then the leds will flash purple and your unit MUST start to reflash from usb-stick/SD-card.
Click to expand...
Click to collapse
I think my re flash procedure is incorrect.
Run Custom
RESTORE STOCK
VERIFY RECOVERY
Reboot to twrp?
INSTALL CUSTOM ROM?
Thought i would give Reboot to twrp a go which have an "Error wait here..." message and I have read that on another post. I will go read there...
https://forum.xda-developers.com/an...ange-problems-joying-2gb-intel-sofia-t3800556
Thanks for your assistance. The head unit is sitting with a black screen. I will wait and see what happens.

Icarusza said:
I think my re flash procedure is incorrect.
Run Custom
RESTORE STOCK
VERIFY RECOVERY
Reboot to twrp?
INSTALL CUSTOM ROM?
Thought i would give Reboot to twrp a go which have an "Error wait here..." message and I have read that on another post. I will go read there...
https://forum.xda-developers.com/an...ange-problems-joying-2gb-intel-sofia-t3800556
Thanks for your assistance. The head unit is sitting with a black screen. I will wait and see what happens.
Click to expand...
Click to collapse
For Joying firmware:
RESTORE STOCK
VERIFY RECOVERY
REBOOT (Just simple reboot to Android)
Insert Joying firmware
And if the screen stays black or you stay in a boot loop: Use the triple reset option.

surfer63 said:
For Joying firmware:
RESTORE STOCK
VERIFY RECOVERY
REBOOT (Just simple reboot to Android)
Insert Joying firmware
And if the screen stays black or you stay in a boot loop: Use the triple reset option.
Click to expand...
Click to collapse
This works up to the booting and remains in a boot loop even after trying the tipple reset.

Icarusza said:
This works up to the booting and remains in a boot loop even after trying the tipple reset.
Click to expand...
Click to collapse
Do you have the stock recovery on your system?
Did you get the purple leds? Note that the purple leds means "3 times unsuccesful boot. forced flash". It will not nicely reboot afterwards.
Did you put in the USB-stick/SD-card before reset? If there's nothing in the slots, it can't flash of course.

surfer63 said:
Do you have the stock recovery on your system?
Did you get the purple leds? Note that the purple leds means "3 times unsuccesful boot. forced flash". It will not nicely reboot afterwards.
Did you put in the USB-stick/SD-card before reset? If there's nothing in the slots, it can't flash of course.
Click to expand...
Click to collapse
1. Do you mean using
RESTORE STOCK
VERIFY RECOVERY
to get it on my system? If so then yes.
Your steps helped me get further this time.
2. No purple led's installed in this head unit.
3. Yes.
Should I used another firmware?
Should I try reinstall the GTX firmware?

Icarusza said:
2. No purple led's installed in this head unit.
3. Yes.
Click to expand...
Click to collapse
2. Sorry. I meant hardware buttons. They have leds which are normally set to a color, but turn purple after 3 incorrect boots. But if you do not have hardware buttons ....
Which firmware are you trying to flash? Have a link?

surfer63 said:
2. Sorry. I meant hardware buttons. They have leds which are normally set to a color, but turn purple after 3 incorrect boots. But if you do not have hardware buttons ....
Which firmware are you trying to flash? Have a link?
Click to expand...
Click to collapse
Oh no I have those touch buttons.
https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update/
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
MCU version is 5.25 or more earlier please click Here
https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view <--this one

Icarusza said:
Oh no I have those touch buttons.
https://www.joyingauto.com/blog/post/joying-intel-sofia-android-car-stereo-software-update/
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
MCU version is 5.25 or more earlier please click Here
https://drive.google.com/file/d/1b-b0sYd32DtzJ-WVYvd28dP80Ry52Ipm/view <--this one
Click to expand...
Click to collapse
First of all: The first post in the gtxaspec thread mentions "you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM".
Were you doing that? And if so, why is your MCU version still 5.25?
If you have applied that firmware version for MCU version < 5.25, it will update your MCU version to >9.20.
I guess you can't check right now on the MCU version, but the next time you flash you need to take the "MCU version is 9.20 or more later" firmware and try that one.

surfer63 said:
First of all: The first post in the gtxaspec thread mentions "you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM".
Were you doing that? And if so, why is your MCU version still 5.25?
If you have applied that firmware version for MCU version < 5.25, it will update your MCU version to >9.20.
I guess you can't check right now on the MCU version, but the next time you flash you need to take the "MCU version is 9.20 or more later" firmware and try that one.
Click to expand...
Click to collapse
Yes you're right. It was 9.20
Before that, back when. I couldn't figure out the MCU versions and what I should use. So I closed my eyes and tried both and both worked and both solved issues.
So I did upgrade to the GTX from 9.20
OK let me try 9.20.

9.20 boot loop solved!
:laugh:

Jy firmware installed!
Will currently running in inside on a test rig. Will install in the car tomorrow.

Update!
The head unit has been in my car on standby for 2 hours and the radio still works! I will test it longer and over night.
This issue happened before the GTX so I might try go back to that.
I was dumb and put 12V on the right amp channel blowing it up so looking at a replacement amp.
Thank for putting up with this one @ surfer63!!
Much appreciated!

So another update.
If I install the GTX firmware then I get the radio issue which started this post.
However the radido issue did start on the Joying Firmware.... So Cant explain that.
Not on topic.
After blowing up the YD7388 I ordered a TDA7388. This have been fitted and running well!
I then added an extra heatsink to so will perform a bit better which has helped.
I still hope for the GTX to work but waiting on another head unit so I don't have to keep ripping my dash apart.

Related

Ebay Android Head Unit won't boot

Hi All,
Wondering if someone can help me.
We have an Android head unit installed in our pajero, purchased in about june 2015, its one of the generic units that was sold on ebay at the time.
Pretty sure it was running Android 4.1.
All of a sudden it has stopped working. It powers on and the "Mitsubishi" symbol comes up and flashes, but that's all it does, will not go any further and boot up. Reverse camera still functions.
Is there a simple way i can reload the system hardware back on it or give it an update in the hope it will come good?
Anyone?
Would be happy to pay someone in Aus who could provide some firmware for my unit on a SD that would get it going again.
Cheers
Pajero2010 said:
Anyone?
Would be happy to pay someone in Aus who could provide some firmware for my unit on a SD that would get it going again.
Cheers
Click to expand...
Click to collapse
Try to get into Recovery and do Wipe data/factory reset. You may find Recovery information on old Android units here:
https://forum.xda-developers.com/wiki/Hui_Fei_Type
yves31 said:
Try to get into Recovery and do Wipe data/factory reset. You may find Recovery information on old Android units here:
https://forum.xda-developers.com/wiki/Hui_Fei_Type
Click to expand...
Click to collapse
Thanks for that, will give the recovery procedure a try.
yves31 said:
Try to get into Recovery and do Wipe data/factory reset. You may find Recovery information on old Android units here:
https://forum.xda-developers.com/wiki/Hui_Fei_Type
Click to expand...
Click to collapse
Thankyou for that link.
I carried out the Recovery, factory reset/clear data/cache as per that link and our unit now works again!
For the record it has the Kitkat 4.4.4 Android operating system, was able to see that now i could get it booted up.
Hi .. what model Pajero
Did you originaly have just a radio or the MMCS GPS etc
Cheers

Boot loop on EONON GA7165s

Hello,
I got my Android unit to boot loop. It reboots on the "Optimizing app ..." screen.
I found out how to make it load files on boot from SD card (key combination), but I don't know what to put on the card.
The problem is that I don't know pretty much anything about the unit, except the official specs.
How I got to this point:
1. Tried to root with kingoapp.com - didn't work.
2. Rebooted successfully and worked after that.
3. From Settings -> apps -> system I disabled Google system app (foolish, I know...)
4. Now it reboots on the "Optimizing app ..." screen.
Please suggest how to fix it.
Thank you!
Here is my conversation with Eonon support.
Hello,
I installed bad app on my head unit and now it can not boot. I shows "Installing apps 15/16" and then back screen and restart.
Please suggest how to fix it.
Regards,
Todor Tsvetkov
Click to expand...
Click to collapse
Dear Sir,
Nice day.
About the issue you mentioned, we suggest you upgrade the unit for checking. Please download the upgrade file from this link:
/file/d/0BwOAE5pUHp8hUTdMYS1VSm9lbEE/view?
us
p=
sharing
Here is the video to you for reference, pls have a look.
/watch?v=3ryHoKKypAU&feature=youtu.be
Instructions:
1. Format a SD card to FAT32 first, then decompress the upgrade file and copy the 6 files to this formatted SD card.
2. Insert the SD card to the unit's GPS SD card slot.
3. Go to Settings of the unit, choose Car settings, then click System updates.
Settings--->Car settings--->System update
4. When the unit detects the upgrade files, please choose exrSD. Then the unit will start upgrade.
5, The unit will turn on automatically after finishing upgrade,
and then pls set the unit back to the original setting as the
following steps
Settings--->Car settings--->Reset factory(password:7890)
6, After reset the factory setting, the unit will turn on automatically, and pls set the unit with the following steps.
Setps:Settings--->Car settings--->Extra
settings(password:123456)--->Model choose--->Select
E90(5.3.19,HZ,CONFIG,NODVD,1Din FZ,Rohm37xxx,TEF668X)
Then the unit turn on automatically will be ok.
Attention: Please do not cut off the power and take out the SD card during the upgrade. It may take about 10 minutes to do the upgrade. So please be patient. And please follow the instructions strictly.
Pls have a try and tell us the result, we will help you further, thank you. If you have any other questions, please feel free to contact us.
Best regards!
Lynn
Customer Service
Click to expand...
Click to collapse
Thank you for the instructions but the device can NOT reach the menus. Steps 3+ in the instructions is not possible.
Click to expand...
Click to collapse
Dear Sir ,
Thanks for your email.
Could you please take a short video to show us the problem and how you do the upgrade?
Then we can check it for you soon.
Video can be sent on this site easily: wetransfer... You can send the download link to us directly, then it will be OK, thanks.
If you have further question, please do not hesitate to let us know.
Best regards!
Lynn
Customer Service
Click to expand...
Click to collapse
This is the video link - LINK The device
does this over and over again.
Now it's out of the car, but when it was in, it was the same problem.
Regards,
Todor Tsvetkov
Click to expand...
Click to collapse
Dear Sir,
Thanks for waitting.
As the problem you mentioned, it may need to change the core board.
Your order was pass the 1 year warranty, you need to pay for the core board.
But the factory doesnot produce this model now, we cannot get the core board now.
We have the updated version GA9265B now, this one is Android 8.1 system. Maybe you can pls consider buying a new unit to use?
And the unit is on promotion now, it is with good price now. Below is the link for reference, pls check it.
/itm/292993336928?
If you have any question, please feel free to contact us, thanks.
Best regards!
Lynn
Customer Service
Click to expand...
Click to collapse
Kye combination
TodorTsvetkov said:
Hello,
I got my Android unit to boot loop. It reboots on the "Optimizing app ..." screen.
I found out how to make it load files on boot from SD card (key combination), but I don't know what to put on the card.
The problem is that I don't know pretty much anything about the unit, except the official specs.
How I got to this point:
1. Tried to root with kingoapp.com - didn't work.
2. Rebooted successfully and worked after that.
3. From Settings -> apps -> system I disabled Google system app (foolish, I know...)
4. Now it reboots on the "Optimizing app ..." screen.
Please suggest how to fix it.
Thank you!
Click to expand...
Click to collapse
Hi. Can you tell me what is the kye combination for this model. I have the same problems and the same talk with Eonon. They suggested to bye new radio.
Regards.
Lukas
It turns out that the unit has Recovery mode.
You must plug in real PC keyboard in one of the USB ports and press Alt + Print Screen + i on boot.
Try both usb ports and google the combination if it's not working, it was a long time ago I'm not 100% sure.
Kye combination Eonon Android
TodorTsvetkov said:
It turns out that the unit has Recovery mode.
You must plug in real PC keyboard in one of the USB ports and press Alt + Print Screen + i on boot.
Try both usb ports and google the combination if it's not working, it was a long time ago I'm not 100% sure.
Click to expand...
Click to collapse
Thanks. It is working with my radio.
The most funny is that EONON technical support told me that this model don't have recovery mode.
They completely don't know anything about android
Xlukas11 said:
Thanks. It is working with my radio.
The most funny is that EONON technical support told me that this model don't have recovery mode.
They completely don't know anything about android
Click to expand...
Click to collapse
I think they just want to sell more...
By the way, when mine went into boot loop I replaced it with a stock BMW Professional (with Bluetooth) and the audio quality improved significantly.
Y recently purchased a 8802 with the intention of connect to megasquirt ecu or obd2 via bluetooth and have the same problem, i resolved this adding a hc05 bluetooth module in master mode to unit

[Note 3] SM-N9005 TWRP not installing

SM-N9005 with stock Lollipop
Using Odin 3.09 to flash N9005 (with working, stock Lollipop ) with TWRP 3.3.1.0 (hlte) - get success message however on reboot after message "set warranty bit : recovery" the device boots to Lollipop. No boot loop however on subsequent reboots I still have stock recovery with Odin mode then reporting custom install (previously stock). So it appears to be installing OK but just not defeating the stock recovery reversion. Tried also removing battery after install message on Odin before reboot however same issue.
Subsequently tried multiple variations of Odin 3.12, TWRP 2.8.7 and a different, known clean Windows OS on a different device - no change. . Same issue with reflashing stock ROM although it does appear to be installing stock Lollipop on finishing the install on the device it just reboots to the existing install. Odin mode still reports install as custom.
Any thoughts ?
There's a file on /system named "recovery-from-boot.p", it reverts stock recovery back whenever it checks a non-stock recovery installed.
Removing that file should fix your problem.
It won't harm you.
Mohamedkam000 said:
There's a file on /system named "recovery-from-boot.p", it reverts stock recovery back whenever it checks a non-stock recovery installed.
Removing that file should fix your problem.
It won't harm you.
Click to expand...
Click to collapse
Thanks - found it via adb however since I don't have root access I can't get further forward.
Can anyone suggest a way forward please ?
I have got a stock BT firmware from Sammobile and will reflash to stock.
Next step will be to try installing TWRP again.
mrwibble3bw said:
Thanks - found it via adb however since I don't have root access I can't get further forward.
Can anyone suggest a way forward please ?
Click to expand...
Click to collapse
Easy, falsh twrp, boot into twrp recovery, mount system, go to file manager and browse to that file, and remove it.
Or use adb from recovery maybe.
mrwibble3bw said:
I have got a stock BT firmware from Sammobile and will reflash to stock.
Next step will be to try installing TWRP again.
Click to expand...
Click to collapse
Update : Managed to get back to official status via Sammobile stock firmware, used Odin 3.09 to reflash twrp however same result - no twrp installed. Recovery boot signals "Set Warranty Bit : recovery" and then reboots to Lollipop.
I can adb into the phone afterwards and see it has a read-only file structure so can't rename recovery-from-boot.p. Bootloader version is N9005XXSGBRI2.
Rebooting into recovery again gives the same results - no stock recovery or twrp.
Not sure where to go now.
Multiple post on this Failed TWRP problem .
Unable to flash on some phones for unknown reason .
Look in the TWRP thread and search q&A .
You may have tried this but . . .
Flash TWRP 2.8.7 via Odin.
Then you have to be quick . . .As soon as the phone tries to reboot hold and press Volume Up + Home button + Power button (Entry to recovery button combination).
I tried it a couple of times and finally got TWRP installed.
grwalker said:
You may have tried this but . . .
Flash TWRP 2.8.7 via Odin.
Then you have to be quick . . .As soon as the phone tries to reboot hold and press Volume Up + Home button + Power button (Entry to recovery button combination).
I tried it a couple of times and finally got TWRP installed.
Click to expand...
Click to collapse
Bingo ! Worked first time with 2.8.7 !!!!
Now I am on the road to Pie ...
Thanks
mrwibble3bw said:
Bingo ! Worked first time with 2.8.7 !!!!
Now I am on the road to Pie ...
Thanks
Click to expand...
Click to collapse
I would be very interested to hear if you have success with flashing a version of TWRP greater than 2.8.7, which you need to be able to flasha Pie ROM. (using the same method you did for 2.8.7)
I found that whilst Odin reports a successful flash of a version of TWRP greater than 2.8.7, the phone goes into a bootloop. I was only able to flash 2.8.7, nothing higher, no matter what i did. (I have the hlte). That meant i couldn't flash a ROM greater than 7.0
grwalker said:
I would be very interested to hear if you have success with flashing a version of TWRP greater than 2.8.7, which you need to be able to flasha Pie ROM. (using the same method you did for 2.8.7)
I found that whilst Odin reports a successful flash of a version of TWRP greater than 2.8.7, the phone goes into a bootloop. I was only able to flash 2.8.7, nothing higher, no matter what i did. (I have the hlte). That meant i couldn't flash a ROM greater than 7.0
Click to expand...
Click to collapse
Finally found why I can't flash - I replaced a defective screen with one from a non N9005 Note 3. See https://forum.xda-developers.com/showpost.php?p=80756445&postcount=522 for further info.
I replaced my screen (or rather the whole upper unit including the display) about a year ago with one from a non N9005 Note 3 - think it was a US unit - after I got water on it at the beach. These replacement units are very competitively priced - assume they are from Chinese recycling of old units around the world - but they don't let you choose the Note 3 model. It has worked fine with stock so the issue was hidden until I tried flashing TWRP.
Sadly it looks like I am restricted to 7.1 until / unless I source an N9005 upper unit. Very frustrating.
mrwibble3bw said:
Finally found why I can't flash - I replaced a defective screen with one from a non N9005 Note 3. See https://forum.xda-developers.com/showpost.php?p=80756445&postcount=522 for further info.
I replaced my screen (or rather the whole upper unit including the display) about a year ago with one from a non N9005 Note 3 - think it was a US unit - after I got water on it at the beach. These replacement units are very competitively priced - assume they are from Chinese recycling of old units around the world - but they don't let you choose the Note 3 model. It has worked fine with stock so the issue was hidden until I tried flashing TWRP.
Sadly it looks like I am restricted to 7.1 until / unless I source an N9005 upper unit. Very frustrating.
Click to expand...
Click to collapse
Thanks for the info. I did the same thing about a year ago. Bought a replacement LCD on ebay from UK reseller. Info was that it was a 9005 unit, but i guess not. Would be interesting to know the difference between a "fake" LCD and an original and how to tell.
grwalker said:
Thanks for the info. I did the same thing about a year ago. Bought a replacement LCD on ebay from UK reseller. Info was that it was a 9005 unit, but i guess not. Would be interesting to know the difference between a "fake" LCD and an original and how to tell.
Click to expand...
Click to collapse
I'm fairly certain that my old one had "LTE" moulded into the frame on the reverse whereas the current one had something else. It worked fine in stock which was all it needed to do. I would imagine phones sent in for recycling are split in China and it would be pot luck which one you get. I know that I raised it with the eBay vendor (also in UK) and he could not guarantee the model.
If you look at current eBay UK listings they all have images with LTE prominently displayed on the frame reverse so I am mulling another swap.
mrwibble3bw said:
I'm fairly certain that my old one had "LTE" moulded into the frame on the reverse whereas the current one had something else. It worked fine in stock which was all it needed to do. I would imagine phones sent in for recycling are split in China and it would be pot luck which one you get. I know that I raised it with the eBay vendor (also in UK) and he could not guarantee the model.
If you look at current eBay UK listings they all have images with LTE prominently displayed on the frame reverse so I am mulling another swap.
Click to expand...
Click to collapse
Thanks
I checked mine. the original screen had LTE moulded in to the case. And so did the replacement.
grwalker said:
Thanks
I checked mine. the original screen had LTE moulded in to the case. And so did the replacement.
Click to expand...
Click to collapse
Sorry I can't add much to that - I got Nougat working well - a few minor issues with the Playstore notwithstanding and now resolved. This meets my use case for the phone which was to allow Life 360 app (my wife uses it for family tracking) from the Playstore (nothing before 6 supported by developers). Now my teen son can be tracked on his way home from school on days he needs to be somewhere ("Where are you ?", "Errrrr ... by a building", etc etc).
Many thanks to all who helped me btw

YT216B - Black screen after Android logo

Hi!
After couple of days of trying to restore my chinese head unit, I finally flashed anything successfully.
At first I tried to flash firmware with root and TWRP included. Due to faulty cable it failed and it got bricked (I think so.)
I tried several firmwares, with or without test point method, using usb flash drive - the most I get is Android logo showing up for 3-4 seconds, then single screen flickering and black screen.
The only software that got me so far was one from XYAUTO fileserver - YT9216B_UI1
Some firmwares gaved me error with "Obtaining DRAM (5054)" if it doesn't have preloader with it.
I thought maybe it's logo problem? Since it's failing to boot after android logo, so I wanted to upload firmware that's booted that far and logo file from other firmwares, but sp flash tool won't let me do this.
Before breaking, my unit was: YT261B_00002_V004_20200608, 2G/32G, MCU 3.1 and XYAUTO 1.1(8227L)
Can anyone help me in any way?
bump
lagakappa96 said:
bump
Click to expand...
Click to collapse
Try this brand new guide
It's not new. I tried it several times.
lagakappa96 said:
It's not new. I tried it several times.
Click to expand...
Click to collapse
The method is not new. This video guide is as I uploaded it very recently. Did you succeed though?
No, I did not. I know this method inside out, it's not working for me. My problem is more complex in the end. I bought another unit in the meantime, the old broken one is laying in a box for half a year now.
lagakappa96 said:
No, I did not. I know this method inside out, it's not working for me. My problem is more complex in the end. I bought another unit in the meantime, the old broken one is laying in a box for half a year now.
Click to expand...
Click to collapse
Would you consider donating it for mod development for XDA folks?
Hey, does your unit have the RST button? Normally this button is on the left side and you can just click it with sharp object.
martin869 said:
Hey, does your unit have the RST button? Normally this button is on the left side and you can just click it with sharp object.
Click to expand...
Click to collapse
Now this was funny

Touch screen and buttons stopped working help!

My touch screen isn’t working tried everything reset, power unplug, battery unplug. Only works with mouse and dongle,
I want to try to reflash original firmware does anyone have?
This is the same exact model
Double din
Android 8.1
7 inch
Ac8227L
firmware zxdz_2019.18.15
mcu version cvd1810_wj_19.08.02_011
Hi, I think you have wrong PSA / canbus settings in factory menu. Do you have wheel commands and are they working ?
Anton TNT said:
Hi, I think you have wrong PSA / canbus settings in factory menu. Do you have wheel commands and are they working ?
Click to expand...
Click to collapse
No wheel commands only the mouse works with Donghee plugged into usb. GPS keeps rerouting. No touch or buttons working. It’s the same exact unit in the YouTube video. Tried commenting to user but no reply.
System platform Ac8227L
firmware android 8.1 7 inch double din. zxdz_2019.18.15
mcu version cvd1810_wj_19.08.02_011
zxdz_2019.18.15 is the base for software search here, but I see it uses 8227L chipset, so in fact it can use any 8227L based firmware upgrade.
I have firmwares with android 10 , 8 I don't have. But will search for you on net.
This is your device : https://romprovider.com/stock-firmware-head-unit-zxdz-01/
Firmware and flash tools are inside ! READ CAREFULLY and proceed with update.
Try first update firmware - if it isn't working contact someone who will flash ROM, DO NOT DO IT YOURSELF as you can brick your device if you are not sure what you are doing!
(NOTE: before downloading files in most cases you must ask for permission to download firmware as it is connected to some personal account on Google drive, if not asked anything just proceed with download)
Wish you happy installing and keep me informed if you succeed.
Anton TNT said:
This is your device : https://romprovider.com/stock-firmware-head-unit-zxdz-01/
Firmware and flash tools are inside ! READ CAREFULLY and proceed with update.
Try first update firmware - if it isn't working contact someone who will flash ROM, DO NOT DO IT YOURSELF as you can brick your device if you are not sure what you are doing!
(NOTE: before downloading files in most cases you must ask for permission to download firmware as it is connected to some personal account on Google drive, if not asked anything just proceed with download)
Wish you happy installing and keep me informed if you succeed.
Click to expand...
Click to collapse
You are the best! I will try and let you know thank you sir!
Hi
Any possible solution?
djdinger said:
You are the best! I will try and let you know thank you sir!
Click to expand...
Click to collapse
Can u share ur experience please?

Categories

Resources