yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] Psycho Dave:
I can't enter recovery mode since I don't have any physical buttons. Recovery 6 worked with a USB keyboard but recovery 8 does not do that. That is the reason why I'm asking for a way to go back to 6.
[MTCD Software Development] Oberbergler:
Don't you have a reset hole? Normally on headunits without physical buttons the reset button is used to enter into the recovery.
[MTCD Software Development] SkyBeam2048:
Did you try the upgrade/downgrade method I provided? Actually it should be fairly simple to downgrade. On my unit I certainly did it about 20 times. Switching bwtween Android 8 and Android 6 ROMs.

In short use the included SD Firmware Tool and flash a firmware update sd card using the included Android 6 Recovery sdupdate.img. Do not copy the Android 8 sdupdate.img to the SD card after.

Then insert your SD card and reset your device. The Android robot should show up installing updates. When its done you should ve asked to remove the sd card. The unit will reboot when you remove the card. Then just wait for the unit to reboot (eventually multiple times). It might end up stuck on a black screen as it cannot boot the installed Android 8 in NAND. So you need to enter recovery by long press the reset button until the lights flash and then turn solid. Then release reset and press it again (short press). Now you should be in Android 6 recovery. Now insert an sd card with a full Android 6 update.img on it (note: do not rename sdupdate.img) and apply it.

I strongly suggedt to use another SD card than the one you used SD Firmware tool on it. If you reuse the same SD card you need to assure the card is removed from the slot on each reboot as the unit will re-initiate the update and essentially destroy your ROM while swapping recovery.
[MTCD Software Development] TPXX:
Does anyone have the Kanor PX5 4GB Android 8.0 Head unit? If so, what is the MCU information. I'm trying to find out who makes it, i.e. is it HA or a GS etc. MCU?
[MTCD Software Development] Katze88:
My Kanor PX5 4gb Oreo is a GS
[MTCD Software Development] Psycho Dave:
Since I don't have any lights (LEDs), how do I know when to release the reset button?
[MTCD Software Development] TPXX:
The lights are the soft buttons that illuminate when reset is pressed eg the volume up/down touch buttons
[MTCD Software Development] cookie1338:
I tried disconnecting the 12v battery, reconnecting it while the sdcard was in my HU and powering the HU up but no luck. I tried this twice. The LEDs do flash now after holding the power button for 10secs but not further luck. Just a black screen.
[MTCD Software Development] Psycho Dave:
Don't have any buttons, LEDs or anything else like that. All controlled via CAN or LIN.
[MTCD Software Development] TPXX:
Got a picture of the front of your head unit? I've never seen one with no controls at all.
[MTCD Software Development] Psycho Dave:
[IMG="No buttons"]http://www.iceboxauto.com/content/images/thumbs/0008534_vauxhall-opel-insignia-2008-2011-android-80-n5753-black_550.jpeg[/IMG]

---------- Post added at 22:31 ---------- Previous post was at 22:18 ----------

So here is my situation.

I have no buttons except the reset button.

With recovery 6 (and Android 6) it was not possible to get in to recovery with just the reset button but it was possible with a USB keyboard and Alt+PrintScreen+E.

Updated to recovery 8 and everything went ok but after that it was not possible to get in to recovery with USB keyboard, and still not possible with only reset button.

Tried to downgrade to recovery 6 as the instruction but after it says that I shall remove the SD card and I do that it just shuts down. After that it will not start, it does not even turn on the backlight on the display. It does not matter if I do a long press on the reset button. OK, now I was lying a bit because I found a way to get it to wake up. If I put in a recovery update SD card and long presses the reset button it will in fact start, show the logo and then starts updating the recovery. If it is a recovery 6 update I'm back in the black hole, if it is a recovery 8 update I will be stuck in not getting in to the recovery.
[MTCD Software Development] TPXX:
All I can suggest is to hold the reset for about 12-15 seconds, release it and then do a quick press again. See if that works. If not, have you tried your canbus steering wheel controls to see if they do anything?
[MTCD Software Development] vipassana:
Hi, thanks to you I was able to update to Oreo, everything works except Bluetooth, I also have to update the Mcu? I have a kgl A53 2gb ram. Thanks
[MTCD Software Development] SkyBeam2048:
So you have a physical button. The reset button is a mechanical/clicking button usually. This button is accessed like hardware-buttons on devices with buttons around the screen. The reset button can even be programmed in factory settings like any other button. Also the reset button can be used in recovery to select the item (short-press to toggle selection, long-press to activate, very-long/10s press to reset).

This sounds very strange to me and is an effect I never seen. If your reset works (after 10s reset-press the soft-buttons start flashing and then become solid) it should be possible to enter Recovery like this unless your manufacturer potentially mis-wired the PX5 SoM preventing it entering recovery. I could also imagine any other signal interfering. Therefore I would recommend to disconnect everything from the device except 12V BATT and ACC. Esepecially disconnecting CANBUS. If the device is woken up by CANBUS you might just short out the ACC pin and put 12V on it to power on the device. Just try a minimal setup with just power applied to the unit and then try the reset method again to enter recovery.
[MTCD Software Development] janusz12561@gmail.com:
Today I lowered my DVD from android 8 to android 6 and there were no problems (rom "update_6_0_1_v_7.0_MAL_13_02_2018_MTCD_PX5"), i did it as described [MENTION=5357096]lucerna[/MENTION]. Android 8 has yet to wait until it's rooted on it
[MTCD Software Development] SkyBeam2048:
This is easy as it does not really matter how long you press it. You can also keep pressing the button for 20 or 30 secondes. Most devices will start flashing the buttons after about 10-15 seconds, flash a couple of times and then remain solid on until the button is released. So if you don't have any backlights on any buttons which start blinking, just try holding the reset for about 20 seconds, then release it and gently press it again.
[MTCD Software Development] Psycho Dave:
Since I get a lot of "you can get in to recovery with only a reset button" tossed at me, I did this video of were I boot from SD card, install recovery 8 and then tries to enter recovery with reset button.

So what am I doing wrong?

www.youtube.com/watch?v=YM1TBiP9T7I
[MTCD Software Development] SkyBeam2048:
I also asked you to check whether you have anything else connected to your device like canbus decoder, steering wheel buttons etc. I am asking since those things might impact the ability to enter recovery. In addition it's of course possible that some manufacturer wrongly/differently wired the reset button so it's impossible to use it to enter recovery. But then the only way would likely be to trigger recovery directly at the SoM header which requires hardware modification.

Edit: It actually looks like your reset button works as expected and resets the device but it does not enter recovery event hough you seem to use the right procedure. Did you try once to keep repeatedly clicking the reset button after holding it for 10 seconds?

So yes, I can't see anything you did wrongly. This procedure worked o n all devices I know up to now. The only thing which is strange to me is that the "erasing" label sticks there for quite a long time after first reboot (and yes, you can see from the round O-logo that you got Android 8 Recovery flashed properly). My devices just show the "erasing" label for about 2 seconds and then reboot.

Again, try disconnecting everything else from your device.
[MTCD Software Development] Psycho Dave:
I have updated with a link that should work.

Head unit is placed on a table running of a battery so nothing is connected.
[MTCD Software Development] SkyBeam2048:
So I have to suspect the mainboard layout preventing the reset signal to be directly forwarded to the SoM. Not sure if this is handled by MCU, it might be actually as the MCU also allows to map any other action like home button to the reset button.

What MCU software is it running? Is it the stock one or did you install any "cross-compatible" MCU firmware?
[MTCD Software Development] Conan_pg:
hello to all, on the android 8 rom the Bluetooth with MD725, RTL8723BU do not work because there are no driavers inserted.e. I do not think anyone will decide to activate them for the time being.
[MTCD Software Development] Psycho Dave:
I might have to mod the SoM connection to get in to recovery then.

Stock MX2 MCU.
[MTCD Software Development] Mad_Mod:
Hi Dave,

what you did wrong is the following:

as I once wrote here, there is or was no upgrade problems as long as man does exactly as the description said but man makes mistakes by himself!!

this is your (upgrade) mistake Dave:

after the wipe/erasing was finished -as you thought? but the headunit was not ready yet becoz- the hu Must at least 2 times goes on and off.. just wait, you have been too fast with it, you had to wait at least 15 (or 30 / 45 minutes to be very very sure on some headunits!!) until he is really finished the recover8 upgrade on the headunit rom.

well this is now become clear to you..

The Solution is:

try (do / repeat it) again but give him the time this time until he is really done with it, then reset the headunit by yourself (long press) and hurray what you have been waited for long time for it is there :The Recovery screen...

Godspeed

Ps:your/the headunit got confused and did not know what to do with the newer recovery8 upgrade for the very first time so thats why it must take some time to put it on the right -rom- place.. if i might call/describe it like that?
[MTCD Software Development] SkyBeam2048:
Well, you can try to wait longer and let the unit work for about an hour after recovery upgrade and the following SD removal. Just as [MENTION=8934753]Mad_Mod[/MENTION] suggested but actually it's not required on my units, so I have some doubts.

If your unit is special regarding the reset button you might have some Options left:

Mod your unit to trigger recovery manually via SoM header.

Temporary install your PX5 module into another unit (maybe you know someone having one).

Order a second unit which does not have this issue

I currently assume it's not a PX5 SoM issue. Nevertheless which PX5 SoM do you actually have? Which revision (written on the PX5 board) and how much Memory does it have (4GB/2GB)?

Again I suggest to check your MCU firmware and eventually try installing another one too.

That's basically all I can suggest at the moment based on my knowledge and your information.
[MTCD Software Development] Mad_Mod:
Hi Dave, just do what I already told you how to do it and you gonna send me a nice dark flowers, without 2 times on and off (or more?) you get never a recovery8 to seen on your headunit lcd display.. just believe in to old for this s..t and than you gonna be released from all that recovery8 pain!!
[MTCD Software Development] Ferdynand40:
I have just downgraded to Android 6 my earlier to A8 upgraded HU. And that was embarrassing easy.

All you need is beer (for courage) and the Oreo upgrade manual.....

Use this like before

https://xdaforums.com/showpost.php?p=75508634&postcount=156

AND

you have to make ONLY the FIRST step.... and thats was :)

You have now MM Recovery and MM System on your mSD... so put your card in the GPS slot, make your HU powerless, start it and wait, wait ,wait (about 10-15min)...... after that you will get an info that everything was ok and you should remove your SD...... after reboot you have to wait approx.. 10min and voila.... you will see this.

Now you can flash what you want.... e.g. malaysk 7 :)
[MTCD Software Development] Mad_Mod:
Read as wel plsl!!

This is what marchnz (see P16 pls) from the beginning wrote, and this is what Dave must also have to wait for it to be done.. as I also did & wrote here:

Originally Posted by kumarai

Updating Oreo

It's dangerous, you can break the device

Unzip the archive to the root of the disk

1. Create a bootable map - CreateCD by selecting an image to create from the Android-6 folder / firmware_new.img

2. After creating the map, delete sdupdate.img from the map

3. Copy to the map from Androud-8-sdupdate / sdupdate.img

4. Insert in the SD slot and restart

5. After the installation is complete, remove the card

6. Gray screen, wait for the inscription Erase

7. Copy the update from Finish-UpdateZIP-recovery-Oreo / update.zip to a clean (different, new) cd map

8. Go to the recovery and install the update

9. Restart

It WORKS!

Fantastic team work and great result guys! Thanks for the steps [MENTION=6738895]kumarai[/MENTION], the key is getting a Android 8 Recovery/Loader installed. From that, we flash the .ZIP package [MENTION=744370]ikerg[/MENTION] kindly provided.

What I provided from OTG, was the recovery and boot file images - these files:

bootloader Image/MiniLoaderAll.bin

parameter Image/parameter.txt

trust Image/trust.img

uboot Image/uboot.img

misc Image/misc.img

kernel Image/kernel.img

boot Image/boot.img

recovery Image/recovery.img

system RESERVED

vendor RESERVED

resource Image/resource.img

backup backupimage/backup.img

For me, after step 5 took a couple of reboots to get Android 8 Recovery installed. When the gray screen appears, wait 5 mins (from memory) for "ERASE" to appear. From that I received the "black screen".

After a couple of power cycles, [Recovery v8.0.5] Appeared. From there on to steps 7-9.

it is convincing now???
[MTCD Software Development] michael.jtf:
Me too struggling against with same problem, reset hole method doesn't work on my HU, in android 6 I can enter recovery with an USB KB (ALT+PRTSCR+E), but no way to enter recovery 8. Since the core board in my HU was soldered to base board instead of a detachable connector, it's very difficult to isolate the pin CTL_RECOVERY pin before SOM, so have to go back to Android 6 and waiting for a auto-start recovery 8
[MTCD Software Development] SkyBeam2048:
Is this your answer to my question what MCU version you run?

Can you be more specific? Depending on the manufacturer and how long the device was in stock at your vendor you might have totally outdated MCU version. I would even suggest to try several versions:

Stock/OEM MCU in latest version.

Try latest cross-compatible MCU like HA one.

As you can still enter Android 6 recovery you can flash different MCU versions. However you might have to boot an Android 6 ROM to get the current MCU version and manufacturer information.
[MTCD Software Development] kumarai:
ROOT rights for Oreo based on GS firmware from 20180118

Receiving the root only through the loading card. The load map contains a modified recovery, and the update.zip update is modified by the boot.

Download archive

Yandex - https://yadi.sk/d/pFSNkK4_3SwNx5

Google - https://drive.google.com/file/d/1xpzsUg1EAI6Am4lfw1rUNDcGmaEPfsjd/view

The archive contains the following folders:

Androud-8-sdupdateROOT

CreateCD

SD Formatter

UpdateZIP-patch-root

- In the CreateCD folder, create a bootable card using SD_Firmware_Tool (the program is configured, no checkboxes are set)

- Image to create a map from the folder Androud-8-sdupdateROOT

- After creating the boot card, delete sdupdate.img from the card

- Copy from the UpdateZIP-patch-root folder to the root of the card's SD update.zip

We insert the card into the recorder, reboot, install the update from the SD Card

Remove the card and reboot the radio.

Map formatted with the program from the folder SD Formatter

The root system / app script writes to MagiskManager-v5.6.1.apk
[MTCD Software Development] Al Ferro:
Many people like me own head units without an SD Card Reader, any solutions for us?
[MTCD Software Development] marchnz:
Yes, try usb. If not, add one. See hardware thread.
[MTCD Software Development] Al Ferro:
Yeah, i tried before the usb ports, and it did not work, i guess i'm gonna have to try to add the sd card reader like you suggested.:good:
[MTCD Software Development] warata:
Thank you as always. You are a really amazing guy!:good::good::good:

I currently own two PX5,HA (2G-RAM oreo updated by kumarai's method) worked fine, but GS (KANOR 4G-RAM originaly oreo) did not boot after flashing Magisk. Perhaps someone will have the same experience in this forum.
[MTCD Software Development] GTZ:
ok so I downloaded the archive extracted it,

used SD_Firmware_Tool with default options

but then I loose the ability to interact with the sd card. windows does not like it at all .

so I cannot delete the SD Update or copy the UpdateZIP-patch-root to the card. am I missing something?

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

never mind I gued the 13th time was the charm

---------- Post added at 10:07 PM ---------- Previous post was at 09:42 PM ----------
[MTCD Software Development] Mad_Mod:
First, many thanks for all your effort and work and attention Kamarasky.

I keep it short, I have already tested it, the result is not good, the headunit does not boot and does not reboot too.. GS!

Thanks anyway.
[MTCD Software Development] scorillo_ro:
I was tring to do a similar thing but without experience I bricked my unit, I guess because I changed some partition addresses in parameter.txt.

Thank you for your hard work on this!
[MTCD Software Development] kumarai:
With UBS it is impossible to upgrade to Oreo

parameter.txt. you can change after the recovery, if you change to the recovery you will receive a non-working device.

rebuilt assembly, updated boot https://xdaforums.com/showpost.php?p=75741195&postcount=519

systemless xposed working
[MTCD Software Development] scorillo_ro:
Yes, unfortunately I also changed the location of recovery. Now I have no recovery and also can't boot from sdcard anymore.

Maybe some day I will succeed to recover the SOM using OTG or maskrom.
[MTCD Software Development] supamicha:
Same Problem here. After flashing update.zip from root package unit does not boot anymore.

To recover the device i used sdupdate.img from Android 6 to 8 kit and update.zip from android 8 gs update.
[MTCD Software Development] ikerg:
Don't SPAM!!!

Android 8 contains RTL8723BU drivers for MD725

LOT's of people have MD725 and only two people complained that thie unit have bluetooths issues.

Only the January ROM OTA update from HA did not contain the drivers

DEcember HA OTa or the 11th January ROM from GS contains the drivers for MD725 and bluetooth is working successfully.
[MTCD Software Development] warata:
Hello. I am one of those who are in trouble because BT does not work on oreo. But thanks to kumarai's work, oreo finally had root authority. It is now possible to edit system files. Would it be possible to copy the driver from Android 6 if that is a problem with the driver? Unfortunately I do not know how.But I will spare no cooperation if you support me.
[MTCD Software Development] warata:
Thank you kumarai I tried the updated patch, but it seems that it is not stable yet.

And I found a simple phenomenon.

When boot becomes impossible after flashing Magisk, it can be boot again by disconnecting the power supply (B+ and ACC+) of the unit for 3 minutes.

And when the boot fails, the display time of the first logo is short.

https://youtu.be/QHtFeYZdOCc
[MTCD Software Development] Psycho Dave:
The file firmware_new.img that is selected when making the SD card and then replaced, what is it?

I have not been able to boot my unit but by mistake I forgot to change to the smaller sdupdate.img image but I remembered it half through the process and ejected the SD card, all of a sudden the unit booted in to my old Android.
[MTCD Software Development] michael.jtf:
Hi kumarai,

if i don't delete sdupdate.img, and don't copy the update.zip, can i use this created card to flash a android 8 recovery?
[MTCD Software Development] supamicha:
In root package from kumarai signature is changed to flash a modified update.zip

If you want flash a unmodified update.zip you must use sdupdate.img for Android 8 from this thread : https://xdaforums.com/showpost.php?p=75508634&postcount=156
[MTCD Software Development] leewp:
[MENTION=6738895]kumarai[/MENTION] Awesome work m8! All worked as intended. Up and running with rooted 8.0.

Only problem I have is with BT. It doesn't save the device name or pin on reboot of the device. And can't pair. Running the OTA 2018-01-18 from Kumarais zip

Anyone that have BT issues tried the december OTA och early January ?
[MTCD Software Development] Conan_pg:
, I said that badly on my not working bluetooth, I got to ask Witson, their answer that not all CIP will be supported !!!!! from 8.On 4Dpa there are guys with the same problem, everyone is free to say his, otherwise we have to do the sheep. Hello
[MTCD Software Development] ikerg:
You can say all you want....but with arguments....few days ago you started saying that in your case the Bluetooth didn't work with md725....several people answered that it worked with the same android Rom and bt module....and now you say that there are no drivers....then how could work for the other guys with the same Bluetooth module?

So without any proof you said that no drivers were included...SPAM!!!

You are trying to justify any other issue of your headunit by entering on panic to other guys....

So be cautious with your statements

Enviado desde mi SM-G950F mediante Tapatalk
[MTCD Software Development] Mad_Mod:
Hi,

I did not want to interfere, but Ikerg is 100% right when it comes to the md725 drivers, I myself have also a md725 BT and have absolutely no problem with it at all and the sound (call) quality is perfect, maybe it's your mobile phone?

just try one of the samsung foons with it.. to be very very sure of it and then reply back!

Godspeed
[MTCD Software Development] bettuccio:
Hello dear friends, Now that there is the root available I want to install Oreo.I have to do one thing at a time.I already have the SD boot ready to upgrade to Oreo. What is holding me back now is the bad thought of not being able to enter the new recovery 8 when the screen becomes gray because my unit allows me to do it only with the usb keyboard. What do you say I will have problems getting into recovery 8 from the keyboard? Will the key combination be the same?
[MTCD Software Development] warata:
Unfortunately Kumarai's Magisk patch is still incomplete. Or do you know other ROOT acquisition methods?
[MTCD Software Development] Eventer_:
Morning,

I currently use my PX5 Unit with the stock rom from February. Is it safe to do the upgrade? Do I currently have disadvantages with Oreo if I previously used version 6?
[MTCD Software Development] bettuccio:
No, I do not know them. So it is better to wait.
[MTCD Software Development] xdamember2:
After many attempts I got root to work on an upgraded (6-->8) SOM. The odd thing is the SD card has to be inserted when power (+12v) is applied or it does not boot.

update: The above turned out not to be true, it does not require the sd card. Sometimes I've had to remove and reapply power to get it to boot, but perhaps it improves over time. I installed Magisk Xposed and Graser Dasaita, but the white list does not work as expected.
[MTCD Software Development] dud89:
Regarding the root issue, I had the same issue with successful flash and when rebooting the android logo comes up and quickly disappears. Tried to boot a couple of times but still android logo and then just black screen. Had to go somewhere and took a 10~15 minute drive. And at some point the stereo booted as normal android started upgrade and I have a rooted unit.

So those with issues with your stereo not booting after flashing the root should wait a bit longer or take it for a 10~15 drive.