Android Head Unit loop bootanimation - Android Auto General

Asking help from you guys.
Change my bootanimation and now my device keep booting. Bootloop forever and never go to main menu.
How to put my device in recovery mode. Maybe it will help if i can do factory reset in recovery menu.
Android: YT9217C_00005_V003_20190307_HIFI
system: Android 8.1 Go kenel 3.18.22
CAN Pro: no canbus-V4.1-disconnect
FLASH: 16G
cpu: A7 1.3GHz x 4
Capacitance: 10000 UF
Amplifier: AC7315 MOS bile duct 45W X 4
display: 1024*600
MCU1: HW8227L-3.3-SWO-1.5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hai, aready have solution for your problem?

Alfain said:
Hai, aready have solution for your problem?
Click to expand...
Click to collapse
Not yet. And you have same issues?

I am having similar issue where my unit would start up, but only to reboot itself after 5-30 seconds.
I don't seem to be able to get my pc to connect the the unit properly as well.
Any one with feed back

jimmyche said:
I am having similar issue where my unit would start up, but only to reboot itself after 5-30 seconds.
I don't seem to be able to get my pc to connect the the unit properly as well.
Any one with feed back
Click to expand...
Click to collapse
Same model?

Same model, and Same situation. Did you find any solution?
my post: https://forum.xda-developers.com/android-auto/android-head-units/rom-firmware-chinese-7-head-unit-ac8227-t3931863
aqishimie said:
Asking help from you guys.
Change my bootanimation and now my device keep booting. Bootloop forever and never go to main menu.
How to put my device in recovery mode. Maybe it will help if i can do factory reset in recovery menu.
Android: YT9217C_00005_V003_20190307_HIFI
system: Android 8.1 Go kenel 3.18.22
CAN Pro: no canbus-V4.1-disconnect
FLASH: 16G
cpu: A7 1.3GHz x 4
Capacitance: 10000 UF
Amplifier: AC7315 MOS bile duct 45W X 4
display: 1024*600
MCU1: HW8227L-3.3-SWO-1.5
Click to expand...
Click to collapse

I have exact same model, and exact same problem. did you get any factory ROM for this unit to re-flash it? or any other solution? I bricked mine trying to install other available ROMs.

New Update. Solve my issue. Change new device because still under warranty

Related

[HELP] Weird / Random Nexus 6 crashes (see images)

So i've been facing this issue on the Nexus 6 for a long time now. It was there even when i was running stock.
Current state : Rooted, Chroma ROM 5.0.2
Issue count (daily) : 4-5 times
The problem : Random crashes. There is nothing specific that seems to trigger it. Dont know whether this is a memory leak issue or not.
When the devices crashes / freezes, a glitch distortion appears on screen, rendering all keys except power useless. A forced restart is the only way to get back.
Please follow the images for better understanding :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Questions :
1) Is this a common issue?
2) Should i relock the device and get it exchanged?
3) If i cant exchange it, what should i do?
Thanks.
Thats never happened to me on stock or CM12....
I would contact who ever you bought it from motorola, google , or a carrier and get it replaces you have the year warranty and the pictures you took can be your proof? ...
same issue
I have same issues friend, from the first day. Now i flash latest 5.1 and testing. if i have it again i'll return my device
After testing lollipop 5.1 muy phone freeze again with same distorsión on screen. Its a fresh flash from factory images. I think i RMA because i dont know what cause this
I had the same issues, it happened randomly usually while using the camera or texting with Textra. I was using Liquid Smooth.
I flashed the latest Rebased version of Liquid Smooth and havent had a crash in over a week now. Hope this helps.
Thanks friend, im going to try líquid smooth
mistermoha said:
Thanks friend, im going to try líquid smooth
Click to expand...
Click to collapse
Did it work for you? Crashes have lessened on my chroma 5.0.1 flash but still not sure about whether the issue is fixed or not. Hell, i dont even know what this is :crying:

Note 5: bad firmware/OS - can't get around it

I'm working on a Galaxy Note 5 that I am trying to reset the firmware on. Someone's installed a custom build (that's verified in the "about phone" details) and it co-opts the volume down button boot sequence, so I can't get into download or safe mode. I've attached a screenshot. Has anyone seen this before and how to I purge this thing?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your image isn't showing.
Image not showing
Ok, let's hope this works as a link to the image:
This happens with the power-volume down and power-volume down-home sequences, so I can't get it into safe mode. Someone's definitely put a custom image on, but I'm not sure how to clean it/replace it.
The power-volume up sequence works fine, but since this is a custom image, it won't get cleaned off by wiping the cache and/or factory reset.
Apparently, since I'm a newbie here, I can't post external links, which makes the forced external URLs for images a little useless to me right now...
Can't you just power off, boot into download mode and Odin a stock firmware, then re-root after?
blud7 said:
Can't you just power off, boot into download mode and Odin a stock firmware, then re-root after?
Click to expand...
Click to collapse
That's the thing - whoever did this co-opted the sequence to boot into download mode - power + volume-down/power + volume-down + home. I did find a way to do it without needing to go into boot mode, but I can't post the link here because I'm a newbie! That should solve my problem - I'm just setting it up on Linux and I'll keep people posted on the solution.
What's happened is that someone's basically done a custom firmware/kernel combo that makes it impossible to get into download mode, so you have to totally backdoor it. When I get it working and verify it, I'll post the solution here.

Question Help, flashing 10R ROM onto my 1+ Ace racing now it's hard bricked.

Hi
So uhh, I followed this link about flashing 10R firmware into oneplus ace racing, I followed it and not sure where it went wrong.
now my phone is hard bricked with a blank screen like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can turn it off when it's unplugged, by holding power and vol+ button. But when a cable is plugged in, the phone will keep rebooting into that screen.
I found the stock firmware to reflash into this phone, but my computer doesn't see the device when it's plugged in, and it won't turn off.
I can't see the phone on adb or fastboot powershell either.
Anything advice please?
The only way is to send it back to oneplus center. 10R firmware doesn't fit ACE Racing Edition.
sidluk said:
The only way is to send it back to oneplus center. 10R firmware doesn't fit ACE Racing Edition.
Click to expand...
Click to collapse
what if I can't? is there any online fix? people who sold me the phone said they can't send it back..
wanderingwan said:
Hi
So uhh, I followed this link about flashing 10R firmware into oneplus ace racing, I followed it and not sure where it went wrong.
now my phone is hard bricked with a blank screen like this.View attachment 5731211
I can turn it off when it's unplugged, by holding power and vol+ button. But when a cable is plugged in, the phone will keep rebooting into that screen.
I found the stock firmware to reflash into this phone, but my computer doesn't see the device when it's plugged in, and it won't turn off.
I can't see the phone on adb or fastboot powershell either.
Anything advice please?
Click to expand...
Click to collapse
You should not have done that. That guide was specifically for OnePlus Ace because Ace(Released in China with ColorOS) and 10R(Released in India with OxygenOS) are same device, just for different region so it's firmware is inter-changeable.
OnePlus Ace Racing is different device entirely. It will not have OxygenOS since it is not released in any other region expect China.

[RESOLVED] Redmi Note 9 Hard Hard Hard Bricked Help?

Okkaayy guys, so, i'll take you to the end of the whole thing which is, I installed and downgraded 2 versions in stock rom, which was V12.5.1.0 worked like a charm, then I updated the version with Xiaomi's original it's own system updater to newer version and it was still fine then I updated it to Android 12, MIUI 13 and it bootlooped.
So, I wasn't able to get into recovery, trieedd soo many times and neither I was able to get in to fastboot mode. What did I do? Flashed it again with Format All + Download option. I got the bar and everything but I waited a bit and nothing happened. I'm like, is this working? And I did the mistake. I pulled the plug. And here I am. Surely I've 60+ battery. Besides that I charged it for more than 15 minutes. No power button works, no fastboot, no recovery. Nothing "HAPPENS". Literally. No matter what I do, how long I press to any button, device won't turn on in any sort of way. Libusb still detects it as Mediatek driver but I can't use SP Flash Tool because simply device won't turn on. Bypass utility stays like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Held power button for 5 min (literally I did) nothing happened
No fastboot or recovery
SP Flash Tool simply can't do the trick because device doesn't turn on
I have 60+ battery %100 surely.
USBLIB still able to detect the port.
What do? Is it even possible to rescue this poor guy? It was my main phone btw...
EDIT - UPDATE: I have no idea how but I was playing around with SP Flash Tool, trying to do some things, nothing was actually happening but like after few minutes phone just gone back into bootloop, It turned on, I genuinely don't know how and just for confirmation, after I installed stock rom back my charge is %73 so surely it wasn't related to my battery. IDK this devices are weird. Sorry for the topic mods..

Touch screen not working after latest update

Hello,
I have upgraded my S20 FE 5G to the latest firmware version (G781BXXS5HWD4). But the right edge of the touch screen stopped working after that. I have also cleared Android system cache. Nothing is helping.
The screenshot is attached for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tuhi009 said:
Hello,
I have upgraded my S20 FE 5G to the latest firmware version (G781BXXS5HWD4). But the right edge of the touch screen stopped working after that. I have also cleared Android system cache. Nothing is helping.
The screenshot is attached for reference.
View attachment 5919657
Click to expand...
Click to collapse
Hi how are things,
the security patch is from april.
If you don't have a solution, download the March patch system.
It's the maximum you can download.
you are already binary 5
You are tied to android 13 without being able to go down to 12 or 11.
have a backup
First of all, you can do factory reset.
If it doesn't work, do what I said above.
mezacorleehone said:
Hi how are things,
the security patch is from april.
If you don't have a solution, download the March patch system.
It's the maximum you can download.
you are already binary 5
You are tied to android 13 without being able to go down to 12 or 11.
have a backup
First of all, you can do factory reset.
If it doesn't work, do what I said above.
Click to expand...
Click to collapse
I downgraded to G781BXXU5HWCH with factory reset. But the issue is still there.
I think it might be physical damage somehow. Thanks for the help anyways.
tuhi009 said:
I downgraded to G781BXXU5HWCH with factory reset. But the issue is still there.
I think it might be physical damage somehow. Thanks for the help anyways.
Click to expand...
Click to collapse
It mentions that it was after an update.
It wouldn't make sense to something physical.
but let us never doubt anything in this life.
wait for the May patch.

Categories

Resources