yashsingh1/xdaforums huggingface dataset:
[MTCD Hardware Development] Antoz1103:
So guys my unit is not updateable to Oreo so i am now Back and all is working! i have no BT Wifi and USB error anymore and want u to know what i did!

First of all i flashed the Android 6 Rom from the SD Formatter process with the Selfmade USB OTG Calbe i build! I flashed it with AndroidTool. Clicked on Download then loaded the img file and FIRST I DID ERASE FLASH!!! After this is done i Flashed the Android 6 Rom.

Then i plugged the PX5 Board to the Unit and took an Multimeter to Test the Signals of all 72 Pin connectors! In my Case 4 Pins where not Connectet! it was Pin: 20,28,29,30. Those are for USB connection in the Radio! and also Pin 71 or 72 was not connectet! THIS PIN IS VERY IMPORTANT! it binds the BT/Wife Module in the System!

So i plugged the PX5 Board again out of the Unit took a Needle and was Bending very Gently all Pins who had no connection! Plugged it back into the Unit and took again my Multimeter! Now All 72 Pins had Connection! now i Screwed all Together so all is good in place.

Then hooked it up in my Car and let it Start. Now it takes about 10 mins to boot into OS. And what i have to say is that my unit is now 100% fully restored! Sad that i cannot update to Oreo but for me its better to have all 3 usbs and BT/Wifi Back!

After all that Process i flashed the Malaysk 6,2 version via Update.img with SD Slot and now i am back! And newly added my subwoofer to the Device! :D

Hopefully i can help many people who have lost their connections and its only a bend over pin!

Greetz Tom

PS: If noone can help u! HELP URSELF like i did! :D
[MTCD Hardware Development] henfri123:
My instructions

Hello,

for me, several of the instructions I found in this thread did not work. Below, I write what I did do (finally leading to success), and I write what I think would have been sufficient.

What I did:

0) Install Drivers from [0]

1) I used AndroidTool 2.39 to flash sdupdate-A8-Kumarai.img [1]

2) Then I tried to flash the partitions from [1]. This did not work with AndroidTool 2.39.

3) Then I tried to flash the partitions from [1] with AndroidTool 2.19.

4) Next I started the Radio and saw Oreo :good:

5) Next I tried to update to Malaysk. I did this by putting the update.zip (zip!) from [4] on a stick and started the update from "Settings". This failed, as the Verification of the Zip failed.

6) Thus I connected the OTG Cable again and flashed sdupdate.img [3]

7) Then I repeated step 5) this time successfully.

I suspect that points 6,5 (in this order) would have been sufficient. Possibly 3,6,5

I would appreciate, if someone could confirm this.

**)

a) config.ini --> English

b) Download Image Tab

c) Copy "Image"(folder), "parameters", config_16.cfg into Android Tool folder

c) Rightclick below the list of files LoadConfig -> config_16.cfg

d) Checkmark at 'parameters'. Select parameters file by clicking onto empty right cell next to it.

e) Run

(see screenshot below)

[0] link

[1] link

[2] link

[3] from point 1.3 in the Malaysk-Oreo thread or direct link

[4] from point 2.1 from the direct link
[MTCD Hardware Development] Xorit:
I did it on a MX MCU by following [MENTION=2754277]dottorniù[/MENTION] instructions!

Had some troubles with the PINs tho - my OTG cable PINs are a bit thin.
[MTCD Hardware Development] henfri123:
By the way: I now have a Cable for sale now (I'm located in Germany).
[MTCD Hardware Development] capu81:
Can't enter recovery after firmware flash

Hi, i've a KGL MTCD PX5 (MCU 2.70) and i don't have hardware buttons (only soft touch). With android 6 i can enter in recovery mode by use an external USB Keyboard with this procedure:

I don't have C17 connector on my motherboard (or i can't find it)

Now, after flash of Android 8, i can't use this metod to enter recovery to flash ROM because KGL don't power up the usb port and keyboard wasn't recognized.

Can i flash only Malysk rom zip file with this OTG cable?
[MTCD Hardware Development] marchnz:
You could, by extracting and creating image files from the zip file and replacing those in the pack I created for Oreo for flashing via RockChip tool.
[MTCD Hardware Development] xdamember2:
With this mod can one get adb over USB? It seems every tool that requires adb, if it works over wifi requires a USB connection first. I'm sorry for the noobie off-topic question.:confused:
[MTCD Hardware Development] marchnz:
Hi,

The SOM is removed from the main unit, so no display, but probably work OK for adb booting into Android if the recovery pin is not connected.

My recovery /boot loop thread which details getting OTG via USB 1, either by direct connection to mainboard that already has all the right hardware in place or with mods to get it.

Hope that makes sense. Let me know if you need any info.
[MTCD Hardware Development] mad212:
Does anyone have one of these cables that they could sell me? I'm in the U.S.
[MTCD Hardware Development] gomylle:
Could anyone please take a look at my logcat logs and see if my non working usb ports is a hardware issue (bend pins after removing SOM) or and android 8.0 software issue?
[MTCD Hardware Development] marchnz:
log cat indicates USB channel for wifi is OK. What we can't see from log cat is USB hub as is a separate channel to that of wifi USB.

Suggest continuity check would determine any physical connection issue - OTG doesn't 'touch' the Wifi USB connections.

Do you have a multimeter?
[MTCD Hardware Development] pir8man:
I could not successfully update recovery to 8.0 via sd card. So I built this OTG cable...

First attempt: install sdupdate.img for recovery 8.0.

Second attempt: erase and re-write sdupdate.img. Then write full partition dump to SOM.

Both attempt results: LED's light up but screen stays black. No "ERASING", no recovery, nothing. It restarts 2 times to the same black screen, then powers off. And will not boot to recovery at all.

these results are the same as when I was attempting SDcard boot update of sdupdate.img for recovery 8.0.

My PX5 SOM is a 2GB unit and REV4.0. Perhaps my SOM is just incompatible with Oreo.

OTG flash of recovery 6 and a recovery based update back to 6.0 works just fine.
[MTCD Hardware Development] djtriso:
hello friends I need help I do not know how to solve my problem.

I want to flash SOM with OTG.

1. Open android tool 2.39

2. SOM recognize in maskrom mode ok

3. Upgrade firmware=test device fail

Chip info= fail

Restore= test device fail

No functions works, always test device fail, all connectors from the som to the pc are ok

Brick SOM?
[MTCD Hardware Development] pir8man:
first, it has been stated in the thread use official version (2.1) and nothing newer (modded).

second, I recommend to do a full erase from the point you are at now.
[MTCD Hardware Development] Taechit:
Hello everyone

I've bricked my PX3 unit after trying to root it. I've tried every recovery method on earth but it's failed. This is my story

http://f30.bimmerpost.com/forums/showpost.php?p=23387558&postcount=416

I've read through this thread and now I think it's the only way to recover my SOM back. However, my SOM looks different from Marchnz's SOM on the first page. How can I know which pin I need to connect? Or do I need a mapping diagram from the manufacturer?

In addition, does anyone sell the custom USB cable for this? I think I'm not good at soldering, but I think I need to try before giving up and buy the new SOM

Thanks.
[Nokia 6 Guides, News, & Discussion] ZeroPointMax:
I use ARISE Sound mod with VIPER4ARISE and it is working great. Only Dolby Atmos will not work with that, if you install the arise Dolby you will get a bootloop.
[Nokia 6 Guides, News, & Discussion] frince9000:
Wait, I don't understand... What's the difference between Vioer4android and Viper4ARISE and Arise itself...

And which of those causes bootloop, which ones are safe to install through twrp?
[Nokia 6 Guides, News, & Discussion] ZeroPointMax:
Viper4android is the original audio mod you were asking about. Some guys from created a collection of different mods and apps and made them work as best as they can - this is ARISE. They included Viper4android and modified the configs so it fits into arise - this is VIPER4ARISE. The main difference for the Nougat user is that the installation is simpler. You just place a text file on the internal storage which tells this twrp zip what to do and Flash through twrp - done. This means that you can easily install a variety of sound software with only minimal problems.

If you install arise however, the pre-installed Dolby from Nokia breaks. If you install Dolby Atmos from arise, you will end up with a bootloop.

I hope this was understandable.
[Nokia 6 Guides, News, & Discussion] frince9000:
How do I install Viper4arise.. I can't seem to be able to find links in google. Also, the files :/ if it doesn't bother you that is...
[Nokia 6 Guides, News, & Discussion] frince9000:
Also, have you tried installing Viper4android? Does it also cause the dolby atmos (speakers) of nokia 6 to malfunction? Or any side effects it might cause? I want the dolby atmos speaker function to remain while having installed Viper4android.
[Nokia 6 Guides, News, & Discussion] ZeroPointMax:
The speakers remain perfectly functional. But DOLBY ATMOS WILL NOT WORK after installing viper through arise at least. I have never installed stock viper so I cannot provide information about this.
[Nokia 6 Guides, News, & Discussion] frince9000:
Updated thread*
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
PORT [8.1][Pixel Experience] OREO From MiA1:

Thanks to @sooti

Download link Mi5X:

[PORT][OFFICIAL][ROM][8.1][Pixel Experience][07/06/18]

How to install:

- Unlock your bootloader

- [Optional] Flash A1 Oreo Firmware

- Flash Oreo TWRP modded

- Wipe Data/Cache/Dalvik/System

- Flash ROM zip through TWRP

- Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)

- In TWRP go to Advanced -> Terminal -> Write "a1to5x" -> press Enter

- Reboot to System

Known issues:

- If you dont flash A1 firmware your fingerprint will acts as a button while unlocked

- You tell me.

XDA:DevDB Information

Pixel Experience Oreo for Mi5X , ROM for the Xiaomi Mi 5X, ROM for the Xiaomi Mi 5X

Contributors

Alex12, sooti

ROM OS Version: 8.x Oreo

ROM Kernel: "Sooti"

ROM Firmware Required: TWRP oreo by Alex12

Version Information

Status: Beta
[Xiaomi Mi 5X Guides, News, & Discussion] rr111:
Hey [MENTION=6865662]bragon01[/MENTION] i have a problem with your rom!

Everytime I boot up your rom, it says somthing like "you entered a correct password, but your data is broken/corrupt" (sorry for bad translation, the text appears in german for me) and the only other thing on screen is a "factory reset" button. If I press it, it does a factory reset over twrp, boots up again and shows the message again. I wiped system/data/cache/dalvik-art cache before intallation.

Please help!:)
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
Did you do this step "- In TWRP go to Advanced -> Terminal -> Write "a1to5x" -> press Enter" ?
[Xiaomi Mi 5X Guides, News, & Discussion] rr111:
Yes I did, I also tried booting once without doing it, and it didn't boot up at all, it would just go to the aosp recovery.
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
I think your phone is data encrypted. You should reflash above custom TWRP, format the storage and do the installation process again.

When you install ROM and it does not boot into our custom TWRP, you should reflash TWRP again and continue next step.

Hope that help.
[Xiaomi Mi 5X Guides, News, & Discussion] rr111:
Can't I just decrypt data?

Or do I have do format internal?
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
Should better to boot into TWRP, copy data as back up and format interal
[Xiaomi Mi 5X Guides, News, & Discussion] rr111:
OK, thanks for your help mate!:)
[Xiaomi Mi 5X Guides, News, & Discussion] Kumczak:
Well, i had this problem when i tried to restore nougat a1 port when i was on oreo a1 port. I am not sure what caused the problem, but my first thought was the recovery - i was on the oreo recovery and tried to boot nougat rom...

Anyway, what i did eventually to fix it was to restore stock miui with official miui tool, unlocked bootloader again and then flashed the a1 firmware, oreo recovery and oreo rom. All is working well now.

The bad news is, your internal data is lost now, most probably.
[Xiaomi Mi 5X Guides, News, & Discussion] HasanAhmed:
Is the headphone jack working on this port?
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
Do I have install GApps for this rom? If it's should, which GApps do I have installed?
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
I installed this rom and working fine, but after several times I reboot the device, sometimes the SIM Card can't be detected, can you help me for fix this problem?
[Xiaomi Mi 5X Guides, News, & Discussion] giocos:
camera not work

camera non working

---------- Post added at 10:19 PM ---------- Previous post was at 09:53 PM ----------

Camera notizie work
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
Yes
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
Should try Google Camera HDR+ mod
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
I do not get this issue anymore. The origninal Mi A1 version has SIM setting issue. I will update new version
[Xiaomi Mi 5X Guides, News, & Discussion] giocos:
I try install gmod cam but It doesn't work.
[Xiaomi Mi 5X Guides, News, & Discussion] Lupine civic:
Hi, is there a camera module for this rom that is compatible, and not force close ..? please help, sorry my english still bad.
[Xiaomi Mi 5X Guides, News, & Discussion] giocos:
Can you give me a telegram group link?
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
You should try Arnova's v7beta9: GoogleCamera-Pixel2Mod-Arnova8G2-V7beta-test-9.apk here Google Camera

And of course, HAL3 Enabler.zip must be flash in Magisk to make this work
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
I like this ROM, for my opinion this rom was the best custom rom for mi 5x, but I hope the developer fix the bug for this rom like SIM Card can't be detected sometimes after reeboting for installing magisk module, some apps sometime force closed especially for game like Rules of Survival, when I put on mic function the game automatically close, and battery drain little bit faster than Mi A1 stock ROM, and this rom also not have audio/headset default settings for equalizer.

I hope the developer could fix that bug/issue that I found on this rom.

Anyway many thanks for developer [MENTION=4460995]sooti[/MENTION] for the great work..
[Xiaomi Mi 5X Guides, News, & Discussion] cleberwill20:
PORT [8.1] [Experiência de Pixel] para Mi5X

I would like to congratulate the developer of this rom

it is very good mi 5x ... guys follow the tutorial that the guys passed has no way to give error .. mine at the beginning was giving error because I was trying to install with my twrp that was already on the device, after I installed the twrp of them and I did the procedure of a1to5x the cell phone turned on normal and it was very top .. the only bad thing of the rom so far is the camera application that does not have, but then just install the google camera that is top ... thanks to developers ....:Boa::Boa:
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
Are you still using this rom? If yes, please tell me about the bug that you find so far, do you face the same problem like me that I wrote from my previous post?
[Xiaomi Mi 5X Guides, News, & Discussion] cleberwill20:
yes I am still using the rom pixel experience, I did not find any bug, but as I said the only thing I found bad is the camera application that does not have and the person is forced to install a third party application, you can put the camera application of xiaomi to use the two cameras?
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
When I write on terminal "a1to5x" after flashing this rom, I got measage "installed rom is not from A1" so it's mean I'm not installing this rom properly or what I did is correct?

Because ROM still work but with some problem like I said before (sometime after few reboot the SIMcard can't be detected and mic doesn't work for some apps, if I activated that mic, apps will be force closed).

Hope you could give me the solution, because I've been try many custom rom, this rom is the best and simple.

Thanks.
[Xiaomi Mi 5X Guides, News, & Discussion] cleberwill20:
then friend, all I did in my mi 5x was to install the twrp 3.2.1 and did the procedure of rom, I installed first then I went in advanced and I changed a1to5x I waited for it to finish, I gave a reboot and it is working normal, microphone .. are you using mi a1 or mi 5x?
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
So now I found my problem, because when I wrote on the terminal a1to5x TWRP not boot anything, I just got "installing not from a1", I'm using mi 5x with tiffany bootloader.
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
Dear everyone whos using this ROM.

I need help from you guys especially to developer, I still facing the problem with my phone during I activate my mic on for some apps/game for example : PUBG mobile and other apps that has feature mic on for online chating using mic, my problem is when I activate mic on the apps force close.

I was give permission microphone allowed for the apps but it's not fix the problem.

And also when I check Esfile explorer there's any folder name "ccmini", inside the folder there is a text file containing the log, I read that log and found like this :

[2018-04-20 01:04:23:641] AudioEngine::StopCapture

[2018-04-20 01:04:23:641] AudioCore::StopCapture

[2018-04-20 01:04:23:644] [session 1] Disconnect Audio causeOfTimeout 0

[2018-04-20 01:04:23:644] [session 1] Audio Tcp Disconnect err 0 reason -107 code 0

[2018-04-20 01:04:23:645] [session 1] Audio Udp Disconnected

I also attached the screenshot for making better explain, thank you for everyone, I hope someone of you can give the solution.

Best regards.
[Xiaomi Mi 5X Guides, News, & Discussion] jmrubio19:
Hi guys!

Last Saturday I installed this ROM and it's perfect, but I have two questions:

1. LED is not working with notifications. I've tried to adjust them in settings but it's impossible. It's a version's bug or can I fix it?

2. I've installed Arnova Gcam, and goes fine, but I'm not sure if in portrait mode, the app uses both cameras, because I think that the quality of photos is worst than Stock camera app on Emui.

Thanks and sorry for my english!
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
1. I don't know. When I flash franco custom kernel then LED notification does not work like you

2. As I know, GCam use only one len for portrait mode
[Xiaomi Mi 5X Guides, News, & Discussion] bandicout:
Good job [MENTION=6865662]bragon01[/MENTION]! Did you extract this rom from Mi A1? If so, could I update it according to the latest version? It seems that some bugs have been fixed in the latest updates like the notifications led, etc.
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
Updated at OP link as requested
[Xiaomi Mi 5X Guides, News, & Discussion] bandicout:
Great!!!
[Xiaomi Mi 5X Guides, News, & Discussion] RDFARHAN:
Could you share the changelog for the latest update on this rom?
[Xiaomi Mi 5X Guides, News, & Discussion] bragon01:
As Sooti updated at his OP. Here

Changelog:

17/04/18:

* Rebased to latest 3.18.105 kernel

* Fixed watermark in A1 stock cam

14/04/18:

* Returned to flex1911 base kernel plus minor tweaks (fixes camera not saving when motion is enabled)

* Fixed clicking sound from speaker

10/04/18:

* Merged linux kernel 3.18.104

* Changed offmode charging to MIUI (now shows percentage while charging when device is off)

08/04/18:

* Merged linux kernel 3.18.103 + some small patches from Franco Kernel

* Latest April 5 security patch

* Reverted interactive governor tunable changes (back to stock values, feel free to change via root)

* Small device tree cleanups for better stability

03/04/18

* Base kernel is now stock with some basic optimization picked from [MENTION=3292224]franciscofranco[/MENTION] kernels (no more fancy stuff other then vibrate, sound and kcal control), this will provide better battery life + performance

* Merged April security update from Google

01/04/18

* Removed some kernel junk that doesn't really help and may even lower battery life (fp boost, autosmp hotplug)

* Rebased to [MENTION=5120185]flex1911[/MENTION]'s latest kernel

* Improved some auto brightness values

28/03/18

* Fixed voLTE no working after reboot

27/03/18

* Fixed telephoto lens, works on both wide gcam magisk mod and a1 stock cam magisk mod

* Added FP boost for faster unlocking

* Fixed autosmp not showing up in kernel auditor

* Changed some of interactive governor defaults to less power hungry values for better battery life

* Add some IO schedulers (zen, FIOPS)

26/03/18

* Merged kernel 3.18.102 stable into our kernel

* Removed DSP for now since it crashes (no equalizer for now)

* Fixed dt2w sometimes not waking when in deep sleep

* Removed Dt2w toggle from display settings since it doesn't work

25/03/18

* Fixed crash in Sim settings

* Fixed audio control not showing up in kernel settings

* Did a proper rebase of March security update (Official PE is still in Feb)

* Rebased kernel to 3.18.101 from [MENTION=5120185]flex1911[/MENTION]

23/03/18

* Switched to Abhishek's implementation of Dt2w for kernel

* Fixed LED for notifications

* Added Google Camera Ultra Minimal (Same features as Pixel Cam) as default - credit [MENTION=5081847]Tolyan009[/MENTION]

21/03/18

* Fixed camera issues, should work 100%

* Added FP gestures for notification bar

* Added double tap to wake & Sweep to wake (Use kernel auditor to enable)

* Fixed FP deletion issues

19/03/18

* Initial release

* Merged march AOSP tags into project (official is currently on feb)