Phoenix automotive Android 9 px6 mk3 mcu RL7Ac bricked - Android Head-Units

So I've recently been having alot of issues with my backup camera sticking, needing to reboot to fix it. So I first flashed the rom, issue persisted. I then flashed the simplecan and then flashed the mcu (both the correct files). After the mcu upgrade it rebooted. It has been stuck in a boot loop ever since. I have spent countless hours trying to figure out how to get the unit into recovery, fastboot, maskerom. I've tried tons of button combinations, a keyboard, jumping the Dow pins (suggestion from Sergey firmware), soldering off the org resistor on the som. I figured the mcu was bricked but I'm not 100% as the air conditioning controls and such still work. This thing is really kicking my butt. I have the proper recovery.zip and mcu file I just need someone to point me in the right direction.

Bump

Related

[Q] Only getting bootloops when I try to flash other roms?

Hey all, so I've got a nice little nexus 7 that I'm trying to turn into a head unit for my car, but I don't seem to be able to flash any other roms.
I got off the stock rom almost as soon as I got the tablet, unlocked bootloader, converted to f2fs, and flashed Xenon HD with 5.0.2. After that, I didn't really touch it much until now, and all I get when I try to flash other roms is a bootloop and I'm hoping someone can help me out. I initially started with USB ROM and Timur's kernel, but that just stuck me at the boot screen so I went to try Autodroid 1.2. Very surprisingly, that was a bootloop too. Getting somewhat worried, I went back and restored my backup which didn't have any problems, and booted straight into the system. Thinking maybe there was just an issue with the these head unit replacement roms for some reason, I tried Optipop and got the same thing, then on a suggestion I saw in the autodroid thread I tried flashing Slimkat since that's what Autodroid is based on, not sure why that would help but I was willing to try anything. And, surprise surprise, still just a bootloop. So now I'm back on my Xenon backup and really quite stumped.
Thanks for your assistance!

complete noob trying to fix my headunit

Everything I was familiar with on my head unit disappeared one day when I started the car and the "windows embedded CE 6.0" start page was showing. I'm at a loss and don't know what to do or where to start. Any help and suggestions would be amazing. I was gonna post a link but it won't let me since I'm new.
Have you tried going into recovery and resetting your system?
If you don't know how to do a reset; detail which system you have and I can tell you how.

Seicane S305690G, boots twice, how to change bootanimation

Hello,
I recently installed my headunit from seicane (seicane S305690G) , but I noticed that sometimes the unit has to boot up twice.
First time it boots, it goes asfar as "android is starting up .." and immediatly after that the system reboots, again, second boot has always worked so far.
Any idea if doing a master reset to factory settings could fix this? and what exactly happens when i do a factory reset, my headunit currently works on oreo 8.1 wich i'm not really fond of, will a factory reset or undo all things seicane has installed? i have the feeling the OS isnt all that stable, the headunit also takes an entire minute to boot, idk but that seems a bit long no?
Another thing I would want to do is change the bootanimation, there was already a standard app on the unit called bootanimation that i can't remove/uninstall, after some digging i found the bootanimations app where you can download other bootanimations, but for this to work i need to be able to write to system/media folder wich i have no acces for , any idea's on how to overcome this, preferably without rooting, if i need to root it i'd preferably install a diffrent Firmware like android 7.X if that's possible and compatible with my unit offcourse...
tablet specs:
android 8.1.0
MCU version: T8.3.19-3-80-043101-180525
System version: V9.3.1_20180518.095309_ACX13
Board: exdroid
brand: Allwinner
device: T8-p1
CPU ABI: armeabi-v7a
CPU ABI2: armeabi
Sky-High said:
Hello,
I recently installed my headunit from seicane (seicane S305690G) , but I noticed that sometimes the unit has to boot up twice.
First time it boots, it goes asfar as "android is starting up .." and immediatly after that the system reboots, again, second boot has always worked so far.
Any idea if doing a master reset to factory settings could fix this? and what exactly happens when i do a factory reset, my headunit currently works on oreo 8.1 wich i'm not really fond of, will a factory reset or undo all things seicane has installed? i have the feeling the OS isnt all that stable, the headunit also takes an entire minute to boot, idk but that seems a bit long no?
Another thing I would want to do is change the bootanimation, there was already a standard app on the unit called bootanimation that i can't remove/uninstall, after some digging i found the bootanimations app where you can download other bootanimations, but for this to work i need to be able to write to system/media folder wich i have no acces for , any idea's on how to overcome this, preferably without rooting, if i need to root it i'd preferably install a diffrent Firmware like android 7.X if that's possible and compatible with my unit offcourse...
Click to expand...
Click to collapse
Question 1: The unit checks on startup whther new programs have been installed and does an optimization step building the dalvik cache for that new application. One of those applications is corrupt, broken, whatever. It crashes the process and your unit restarts. The second boot either skips the apk or now it is going correct. so check what you have installed as 3rd party apps and install/deinstall one by one to find the culprit. And on reinstall it might work correctly as something might have gone wrong during first install or later upgrade.
Question 2: You can only do this via adb, either adb over usb, or adb over tcpip. Please do some googling otherwise this will be a very lengthy explanation which others probably already did better.
surfer63 said:
Question 1: The unit checks on startup whther new programs have been installed and does an optimization step building the dalvik cache for that new application. One of those applications is corrupt, broken, whatever. It crashes the process and your unit restarts. The second boot either skips the apk or now it is going correct. so check what you have installed as 3rd party apps and install/deinstall one by one to find the culprit. And on reinstall it might work correctly as something might have gone wrong during first install or later upgrade.
Question 2: You can only do this via adb, either adb over usb, or adb over tcpip. Please do some googling otherwise this will be a very lengthy explanation which others probably already did better.
Click to expand...
Click to collapse
Thank you for your response surfer63, very interesting indeed seems to be the case here, i'll try to take it into account, i havent seen this happening yet but i havent installed any new apps yet aswell.
I will certainly look into it, but will the adb over usb method work without rooting the device?
Maybe you know how i can enter recovery mode on my headunit, havent tried the reset button yet, but i figure it is needed, i tried all other key combo's but nothing worked so far (capacitive buttons). If i press the reset mini button on my unit what exactly will happen, will it do a factory reset or does that need some extra actions?
I have searched youtube and google but can't seem to find my headunit and there are lots of diffrent methods to get into it with no physical buttons, maybe you know the most used method for these kind of things? Haven't tried anything yet with the reset button though, but i wanna know what it does exactly before i start fidling around with that button.

Galaxy Tab s2 SM-T810 - nothing will flash successfully!

Hi all,
I was given a Tab S2 that was stuck in a boot loop. Original owner had no idea why. I have tried flashing stock, and various development images but I cab't get anything to boot.
I CAN flash twrp 3.1.0-1 from one of the threads, and then successfully boot into it in recovery mode.
In recovery when I try and install a ROM I get an error with "this device is ." at the end. I have tried a workaround to set the device ID but it doesn't seem to work.
Also, I have tried flashing the original firmware using ODIN and once again just get stuck in a boot loop and have to re-flash twrp.
I cannot flash any later version of twrp (the 3.4 versions for this tablet do not boot flashing in exactly the same way as the 3.1.0-1 version that works fine).
I've searched the forums a LOT but can't find anyone with this problem. If anyone else has been here and has a way to get either stock back on, or a late dev version (preferably) I would very much appreciate some advice.
thanks,
Matt
Mine had an Error 7.
I would recommend trying to get 3.4 to work.
However. Grab yourself Lineage 16.0, Nano Gapps and jump into recovery. Go into Wipe and hit Format Data. Then Advanced wipe and clean everything out but your SD card. And do a factory reset for good measure.
Then reboot into recovery again, plug the tablet into your laptop and transfer Lineage 16 and Gapps + Magisk if you want. My key backlights broke after Magisk tho. Flash em all, Lin first Magisk last.
If it's still broken you can just repair all the file systems. Just don't change any settings and try again to flash.
Tablet works great now. :3 Definitely worth it. Fast, smooth most the time. Definitely doesn't lock up it just chugs along with a pretty ol' OLED screen. Charges slow but it's not an OS issue. That's just how she is. But if my battery wasn't 87% wear it'd last well over 6hrs. It does about 5.5 screen on right now! It sick! Btw get Accubattery so you can see the charging speed and so you know if you need a new wire and battery health in case the battery is messed up. It normally tops out at 1600mAh with the stock charger and a good wire. If it's anything under that you have a connection issue.
P.S; This tablet is terribly picky with wires. I had luck with an Onn wire from Walmart. 1 out of the 2 managed to flash it. One would only charge and the other worked but if I bumped it it would disconnect. Bare in mind these are both brand new out of the box. lol It can definitely lead to flaky incomplete flashes and weirdly they fail precisely at the exact same point too. So definitely get wires. Lots of them. At least 3 attempts. With any luck one will work long enough for you to flash it.
P.S.S; The same Onn wire that worked for transfer yesterday doesn't even try to connect today btw. I'm srs. This tablet is alergic to wires. Still charging at 1536mAh but doesn't show on my laptop.

No name Chinese headunit. Allwinner t3p1

Ok so I purchased a android headunit from eBay for my Lexus. Installed it worked great. Then Google stopped working which led me to these threads trying to fix it.
Upon apps I downloaded I managed to find out the device is a Allwinner t3p1 running android 8.1 (was told it was 10). I've tried reaching out to my seller but don't think he was official think it was just a kid that didn't understand it. But he has vanished so no help there. I tried reaching out to all winner with no response.
I managed to do a factory reset and now it's stuck on Android boot logo.
I managed to get some pics before the unit got stuck
Need some assistance on what I need to do to get it working again.
I've attached photos that have the version, MCU, and other info of unit.
HELP ME

Categories

Resources