yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] ipgoogle:
Thanks for reply, and you have type 2 from MD725 BT ?? And whats MCU type you have ??
[MTCD Software Development] yves31:
It must be a type 1.

However, I just did new tests and realized that type 1/2 does not make sense anymore. We should call a driver compatible/incompatible module.

Here is my story. I have a MTCD PX3 radio which used to run Android 5.1.1/7.1.2 and bluetooth worked well. I upgraded coreboard to PX5 with Android 8 and BT was not working anymore. BT module was not detected and BT name/code were empty. Downgraded to Android 6 and BT worked again. Using getprop bt.md725.type I saw "2", indicating it is a type md725 type 2 module. I always want to come back Android 8, so I am constantly monitoring new versions of Oreo firmware. Yesterday I upgraded to Hal9K's Oreo version 3.1.1 with mcu HA 2.99, and noticed some changes. BT name/code were showing up and my phone was able to see CarKit BT. Unfortunately they cannot pair, so BT is still not working. Then I typed "getprop bt.md725.type" and I saw "1" this time. My module became type "1" !

In short md725 BT driver is getting better in new Oreo firmware, but is still incompatible with our old modules. Hope the driver will be improved and our module will be running in future.
[MTCD Software Development] marchnz:
Thanks for your story.

BT issue has zero to do with md725 driver. See forums posts.

If you want type 1, change md725 to type 1.
[MTCD Software Development] yves31:
I used to think this way, but not anymore.

Android 6 saw the module as type 2, and now recent Oreo shows type 1.
[MTCD Software Development] msb111:
Mine shows as Type 1 in Oreo too but does not work.

With the HAL ROM installed, my phone would see the Unit but would not pair to it.

With Malaysk ROM, the PIN and Name in the Bluetooth app don't show and my phone cannot find the unit.
[MTCD Software Development] yves31:
This is exactly what I saw in my HU.

HAL rom is based on a newer and Malaysk is based on an older one. Newer Oreo made some improvements on MD725 driver, but is still not functional for our modules.
[MTCD Software Development] ruboncio:
Hello there,

I'm experiencing a similar issue here.. mic doesn't work when making a BT call from my phone. It does work out of the BT, in apps etc..

It doesn't matter whether I use a external mic or the in-built... I have upgraded the MCU to the latest 3.11 and still happens.

P.S- I can pair and I can see contact etc... it's just the microphone not working.

Any ideas?
[MTCD Software Development] Seicane-Misery:
try another phone..

Hi,

I had written about that before, I have a newer headunit and (if I pairing it) with my meizu 6 pro plus

gave (have) the same problem "as yours" but when I used my old s6 with a RR-P v7.0 custom rom worked without any problems at all.

so with other words, use or try another or newer phone with it.. try a loan (samsung) phone from your buddy or family to test it with it.. it maybe works for you too as I did and got a 100% working headunit bt & s6 phone combination?

try
[MTCD Software Development] Sindre.B:
Has anyone tried replacing their module with one of these?

I lost bluetooth after changing to a PX5 8.0 board in my PX3 5.1.1 MTCD unit.

I have updated my MCU to KLD 3.01 after trying both 2.57 and 2.88 with same results.
[MTCD Software Development] reverendhtc:
As far as I know, yes this has been tried. The result was extremely slow transfer speeds when Bluetooth and WiFi are used at the same time. When Bluetooth is switched off, WiFi speed returns to normal.

Others can confirm.
[MTCD Software Development] zeyret:
I changed the module and I am satisfied.
[MTCD Software Development] abagos:
I can confirm. I wonder if this https://xdaforums.com/showpost.php?p=79298836&postcount=2736 could improve things. That is replacing both WiFi/BT and USB modules would solve the problem.
[MTCD Software Development] ipgoogle:
Hello , any new update or fix for this problem , i hope it will fix in android 9 FW so we can update to it ?
[MTCD Software Development] Arjen-S:
This problem is not solved with Android 9, tried it, i see the HU on my Phone but cannot pair with it, same with Android 8. Only Android 6 and 7 will work with my Huawei mate.
[MTCD Software Development] reverendhtc:
Same here. Tried with A8 and A9, no luck.

I personally reverted back to the Witson version of A6, until a solution appears, but I'm not holding my breath.
[MTCD Software Development] ipgoogle:
[MENTION=3260627]switchboy[/MENTION] hi , are you still working on this fix ? and any new info about it ?

thanks for your hard work
[MTCD Software Development] switchboy:
Small update: normal life got in the way but recently (with Ghidra) I was able to decompile sdsdk to a C file! And best of all the output mostly makes sense. The next step will be to try and build this code in a build envioroment for Android ARM against 'current' audio and bluetooth libraries and try to fix build errors as they pup-up.

As I write C++ as a hobby game developer but never tried getting decompiled code to compile again, I might get this to work sometime. But since I am not that familiar with plain C let alone ever attempted to write a lower lever driver. I have a feeling that I might be in somewhat over my head right now.

Also Ghidra is complaining about the missing libraries as well so it might give functions/calls to the lib files jibberish names as well. Maybe I should try this decompiling again when I get my hands on the dependencies. Which are:

[libtinyalsa.so] -> not found
[libmedia.so] -> not found
[libutils.so] -> not found
[libbinder.so] -> not found
[liblog.so] -> not found
[libstdc++.so] -> not found
[libm.so] -> not found
[libc.so] -> not found
[libdl.so] -> not found

For anyone interested and/or willing to pick this up where I am struggling I added the decompiled source.

Get the sourcecode here: https://gofile.io/d/7jQ0ZE
[MTCD Software Development] marchnz:
Is this relevant? https://github.com/wuwenjun08/Gocsdkapk_code/tree/master/src/com/goodocom/gocsdk
[MTCD Software Development] airbay:
Thanks for the instructions
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
#reserved
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gimpy1:
I am on the twrp vs 996_20f. Working very well. Thx, seadersn, and all others involved for your fine work.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gimpy1:
Deleted
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gimpy1:
Third time is a charm. Finally got it to load, I think
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
nice, i can finally add security patch date now, thx! :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] cmrntnnr:
[MENTION=3138121]seadersn[/MENTION], the rom works perfectly, flashed it from DOTOS with US998a firmware. It works perfectly. Awesome, many thanks for making this and other TWRP flashable zips available!

I need native tether and so had to restore, and there was a quirk. I mention it not to complain but out of curiosity and to make others aware. TWRP complained about no partitions being selected when attempting to directly restore either my stock US998 setup or DOTOS. Flashing westwood's US998b rom fixed matters. Can you explain what is happening? It seems like TWRP backups are specific to a model firmware.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
hmm, that would be news for me: what exactly did you do to restore? just selected backup, chosen partitions, restore? or was the backup folder not visible? and: do you have a log of this? ;)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] cmrntnnr:
I'll try to be specific and detailed and hopefully not offer too much useless fluff. The phone is an open market us998 v30s. It has never been flashed with any other firmware. I keep a stock and DOTOS TWRP backups. Restoring between them or with any of the other aosp roms has always worked perfectly. I've wanted to see what additional features might be in the Verizon rom so I downloaded the your fresh zip, verified md5sum , factory reset on TWRPv6a and flashed. After satisfying my curiosity, I button danced back to TWRP to restore. This is where things got weird. The names of the backups matched the phone serial number rather than the dated backup name. TWRP gave the no partitions selected error when attempting to restore. At this point I thought maybe the backups got damaged and so popped in the sdcard with extra backups, ;). Those backups did not register their names properly and would not restore either. At this point I was resigned to setting up the phone again and just moved forward with a factory reset and flash of ww's 998b zip. I thought maybe there was something about the firmware change the affected the ability to restore so I rebooted TWRP. The correct names for the backups appeared and they would flash.

No logs, but I can repeat the process and gather information.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
twrp has different mechanisms for setting backup folders names, the serial number is one of them (and the default). it may be that something boot.img or other related has changed in this new firmware, so that old backups have another name than newer ones.

would be nice to have some additional testing. with the new firmware installed. means: install the new firmware zip, then do a cache format, reboot to recovery and then try a restore: does this change everything back to normal?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] cmrntnnr:
It all repeated just like the first time. Clearing the caches had no effect. What is the best way to send you the logs?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
pastebin.com :good:
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] Mrxyzl:
Oh well, if you remember me, i flashed your h930h twrp on us998 based with boombox before. I backup the Rom using latest twrp too. Then after i lost connection as i already told you, i tried to restore this backup, it show the name of backup correctly but there is no option to select which partitions to restore, i mean it completely blank without anything to select. Just then i thought it was corrupted backup but there is now someone like me. I kdz back to us998e but somehow lost twrp and fastboot unable to flash it back ( showing FAILED (remote: Requested download size is more than max allowed ). But after a few kdz back to nougat and us998b with relock and unlock bootloader i can flash twrp again. So not sure what really happened
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
the log is in /cache/recovery/last_log, you can copy it to sdcard within twrp or adb pull it.

boombox; this was some weeks ago, right :good: i hope, this could be solved finally, i think this really could be firmware & partition table related, which indeed can only be fixed by a kdz flash or with the zip used before flashing this one (or relevant other firmware zip).
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] cmrntnnr:
Apologies for disappearing in the middle of an activity, work called. The problem is a bug in TWRP. One could make the argument that backups are model-firmware specific, but the reason is not exciting and hardly genuine. The installed firmware model is being pre-pended to the serial number of the backup folder name. If model firmware changes then backups made with another model firmware aren't visible. Renaming the backup folder is probably an interim work-around to enable TWRP to see the backups and carry out the restore. A longer-term solution would be to just not prepend anything. Let me know if you still want the recoverly logs and I'll put them onto pastebin.

Here is a snippet from the recovery log with the VS996:

I:Setting up '/data' as data/media emulated storage.

I:mount -o bind '/data/media' '/sdcard' process ended with RC=0

I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0

I:Setting up '/data' as data/media emulated storage.

I:mount -o bind '/data/media' '/sdcard' process ended with RC=0

I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0

I:Backup folder set to '/data/media/0/TWRP/BACKUPS/VS996xxyyzzaa'​

This is the same snippet after flashing back to US998D:

I:Setting up '/data' as data/media emulated storage.

I:mount -o bind '/data/media' '/sdcard' process ended with RC=0

I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0

I:Setting up '/data' as data/media emulated storage.

I:mount -o bind '/data/media' '/sdcard' process ended with RC=0

I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0

I:Backup folder set to '/data/media/0/TWRP/BACKUPS/LGUS998xxyyzzaa'​
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
aaaaaahhhh...! :D very nice finding :) :good: sounds and looks logical, and *is* logical: *and* makes sense: it appends the model number, which seems legit in terms of security for your phone while restoring. think about two different models which just aren't compatible to each other. what will happen if you restore a wrong firmware's or model's backup to another hardware? it won't boot. to prevent that, it changes the names of the backup folders. absolutely ok. unfortunately :(

so i just didn't fully get this problem and its meanings... sry for that: but thanks to you! now we know what happened / -s and can write a little tipp for a workaround in one of the first posts of recovery thread. as i said: i don't like the crossflashing stuff :D thank you :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] cmrntnnr:
It absolutely makes sense as a safety feature. Perhaps it is best not to remove like I had suggested. Working around the folder naming convention for restores is a minor inconvenience compared to a brick, :D.

With regard to safety in TWRP, is there any way to increase the space between the radio buttons used for selection of partitions. I once had an unfortunate fat-finger event and a phone that would't boot.

Happy Armistice Day
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] schwinn8:
I just want to be clear before flashing... this can be applied to an existing US998 -> VS996 phone, correct? I see "H930" in the first post, so I was concerned about that.

Also, the issue mentioned in the last few posts - I'm planning to dirty-flash from VS996 20d to this... that won't experience any issue, correct?

Will I need TWRP 3.2.3-6a or will my existing 3.2.3-5 work fine?

I prefer to be over prepared, instead of running into problems!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] gimpy1:
I am a Verizon customer with the Verizon vs996 phone I ordered new from them back in April or May of this year when I upgraded from the droid turbo. If you see the third or fourth post in this thread, I took a screen shot of the phone system. I am still currently on this rom but, am a "flashaholic", so in the next day or so will probably change it again (probably flash the twrp US998 rom or maybe pie 9:)).

In the first post, seadersn tells you how to install it on your phone from "oreo". That is the procedure I used. I am pretty sure that I used the most current version of twrp, the one that says something like 6a data IMG.

Edit: I just went into twrp and checked the version. It is the 6a data IMG version that I am on.

Sorry, I just reread your post. You went from the US998 to the VS996, not the other way around as I first thought. I would think it would still l work, but, again, I started out with the VS996.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] seadersn:
changed the h930 to V30 :D sry, forgot to change this ;)

but these issues were special ones, more related to twrp than to this firmware. firmware itself is fine, it's just all the images of the kdz converted to twrp flashable zip :good: when you experience problems, these problems will be there too when flashing the kdz :)

your recovery version is fine, beside the fact that it has wrong modem partition handling. updating is always the best :good: i would suggest to install -6a.

i don't know anything about all these conversions, can therefore not give any tipps if this will work or not. for info about that [MENTION=2839177]schwinn8[/MENTION] has to search or ask on other places :(
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
John sent this to me last night, I didn't know you could get bootloop logs either. It's on the third post of the thread. https://xdaforums.com/showthread.php?t=2274119 I'll be doing it in a bit.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] ChazzMatt:
Over in the T-mobile thread, [MENTION=9374982]weakNPCdotCom[/MENTION] says his TWRP-flashable will be delayed due to "new KDZ format." Could this possibly be the Verizon issue?

Apologies is this is not relevant whatsoever.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
John and I are working on it. Mostly him doing stuff and me getting logs. So just hold on for a bit.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
nope. mine and [MENTION=3138121]seadersn[/MENTION] build script supports the new format already
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] dv|dt:
Subscribing for updates to the bootloop problem!

Mine also hangs on the LG 30 screen after flash from 20g and I get the same Magisk error.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] ChazzMatt:
Which Magisk?

Sent via open market LG US998 V30/V30+
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
That's not the issue. It's related to system.img
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] dv|dt:
both 18.0 downloaded separately and 18.1 downloaded through the app (last update prompt I got, I believe). Both fail on the boot image step with red text
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
We've confirmed it's not the KDZ. We're making progress.
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] drewcu:
Can someone please confirm whether the latest 4/3 8am hosted 20J works for them?

I had tried with at least 3 earlier versions and finally gave up and decided to just wait until there's confirmation of a working version.

Thanks!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] KittySparkles:
Tried the one you stated out of curiosity. Doesn't boot. Just wait for the OP to update with the fixed download.

Usually there's a reason there's no Update Post on downloads. lol
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] TotallyAnxious:
I'm on 20j because I flashed the kdz to get a twrp backup of the system.img because for whatever reason the system.img is failing to inflate (unzip) during flashing after 1.5gb or so (when it's almost 6gb in size), it reports out of storage, when that's clearly not an issue.

The AFH keeps showing new builds because that's how he's sending me new stuff to test.

I flashed the kdz, everything except the recovery partition. And sent John a backup of the system.img for comparison.

Luckily we're both in the same time zone but it's still hard to line up time when we're both able/willing to work on stuff together. He's gonna being doing the Sprint update next, and see if he runs into the same issue. (He is on Sprint) As it's not the easiest thing to debug something you don't have.

He's also working on a unity version of my module that patches files, instead of replacing files. Making it compatible with all v30 models (theoretically).
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] pierre898:
Hey, long time lurker, first time poster.

I tried flashing 20j with TWRP several times last night (kicking myself, should have fully read the thread) and having similar issues as Drew. I have No Bootloader Unlocked Screen, ADB cannot reboot to bootloader, no fastboot, and No Download Mode. I have the additional issue of Magisk NOT working when I put 20i back on, but the phone functions with 20i, just cannot achieve root how ever I try.

I have tried several reflashes and have gone all way way back to restoring with the backups I made when I first flashed TWRP... all attempts have landed be back to the same state: 20i working, but no bootloader and no root. Any ideas how I can get the bootloader functioning again?

- Peter
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
Do not flash any 20j zips until i post that there's a working one. It seems LG might have changed something to do with kdzs but I don't think it's the format/headers because my build script supports the latest format. Just give me a few more days and I'll get vs996 ls998 and us998 updated
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] drewcu:
So Peter I can tell you that you probably CAN still flash Magisk assuming you still have TWRP installed as I found out that I can also. In TWRP, Magisk failed for me initially so I wiped everything (system, data, internal, etc), and then installed 20i and booted into it. Then I went back into TWRP and installed Magisk successfully so I now have a ROOTED 20i. If your bootloader is unlocked, I don't think it can somehow lock itself so you are probably ok. Download mode for me is still borked but in its place I put a second copy of TWRP (how-to link below) so at least I have a fail safe.

No Bootloader Unlocked Screen - Because you are on a Verizon ROM (not on US998 anymore)

ADB cannot reboot to bootloader, no fastboot - Because you are on a Verizon ROM (not on US998 anymore)

No Download Mode - See my post in the thread I started about this: https://xdaforums.com/showpost.php?p=79244347&postcount=16
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] pierre898:
Copy on the first two, noob, being noob, haha. Makes sense, thanks for explaining.

Which Magisk version are you using? I have tried reflashing v18.1 (after putting 20i back on) and I get zero errors in TWRP, but there is no Magisk app when I reboot and Titanium says it cant achieve root. Am I missing a step?

---------- Post added at 01:48 PM ---------- Previous post was at 01:31 PM ----------

Never mind, just installed Magisk Manager manually, its all good now...

I apologize, I haven't rooted a phone since my Moto Droid 2 QWERTY Slider
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] drewcu:
It's ok! I've only been on the V30 a week and I'm loving it, but someone had to explain all these things to me, too lol. Glad I could help and that it's working for you now!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] pierre898:
Yeah, Ive had mine a while, just got bored with the LG UI.

I love the hardware... I just wish it had mostly vanilla Android and less bloat. Nova Launcher and root will take care of that :)
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] drewcu:
I am coming from a rooted and crazy slow Galaxy S5 with Touchwiz so this V30 Android IS vanilla to me lol (I know it isn't). Root and unlocking the bootloader on Verizon was the main reason I got the V30 (was considering Pixel 2 XL for that as well). Also use Nova Launcher too -- the spyware riddled stock launcher had to go!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] schwinn8:
Given the issues with this ROM, I would suggest that the link be taken down... can the OP do that, please? It beats leading people into trouble...
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
So it's going to be a little bit before I can do the update. My power supply just died in my pc and idk when I'll be able to get a new one. I can't afford one right now
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
If people actually read like they should it's how I'm sending the zips out to my testers. Regardless I can't do much about it anyway with pc out of commission until idk when
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] schwinn8:
Yeah, I know people should read, too... but putting forth a known-problem isn't the best idea either, that's all.

Desktop PC power supply? If so, I may have a spare I could send you. I haven't needed it all this time, and it would be for a good cause, haha!
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] KittySparkles:
Got a way to donate to you for a new one?
[LG V30 ROMs, Kernels, Recoveries, & Other Developm] JohnFawkes:
Link is in the OP at the bottom