yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G4] eruisi:
Hi,

I have been using Lineage OS nightly build for a while, but I frequently encounter overheat problem (screen becomes very hot for games or unknown reasons) and battery drains very quickly.

I would like to try a more stable and cool ROM based on 7.1.X. I also need multi-user enabled, which is the main reason I stay away from LG stock ROM.

Really appreciate your suggestions.

Thanks
[T-Mobile LG G4] TecknoFreak:
I use the g5 port and is working great plus it have multiuser
[T-Mobile LG G4] eruisi:
Where is the link to get ROM. Is it rooted?
[T-Mobile LG G4] TecknoFreak:
Just to let you know is stock Rom and yes it is rooted. But I use SuperSU instead of magisk

https://xdaforums.com/showthread.php?t=3614857
[T-Mobile LG G4] eruisi:
This Is MM (android 6.X) not Nogurt (android 7.x)
[T-Mobile LG G4] TecknoFreak:
Yeah yeah, oops sorry didn't read that little detail
[T-Mobile LG G4] oari0909:
Dont use cypherOS, no tap to wake,they had it in the gestures but it just dont work,Always used power button.

whatsapp speaker issue (crash when you tap to it), *(after this I went back to stock)

Great battery life though... it was awesome to get 35% at 10 pm all day heavy use. :D
[T-Mobile LG G4] NighthawkXL:
Unfortunately, as it stands right now finding "stable" 7.1.x ROMs without missing features is rather difficult. Any LineageOS derived build is going to be having missing features, or occasional bugs such as the following due to lack of official Nougat drivers.

Lack of Stock Camera Quality

Wi-Fi Calling

Occasional Bluetooth issues

The list could go on, but if I were to recommend a 7.1.x ROM go ahead and try either Resurrection Remix or Dirty Unicorn I believe both of them have multiuser and decent battery. Flash one of them and use the Llama Sweet Kernel. They are the only two ROM's I've had any luck on 7.1.x thus far. LG is supposedly releasing Nougat later this year for the G4 which should fix most of the issues. Good luck.

Official Resurrection Remix

Tylerdurden's Unofficial Resurrection Remix

Gibbnich's Unofficial Dirty Unicorn
[T-Mobile LG G4] AlaskaLinuxUser:
Eruisi,

I don't wish to disagree with the former comments, but both my AOKP 7.1.2 and SlimRoms 7.1.2 are here in this forum, and both work great.

I have had no Bluetooth or other issues, nor have any of my users reported any issues like that.

The camera is not the stock camera app from LG, so if you are really big into your camera, you may wish to stick with stock ROMs. However, using open camera my photos come out great!

I highly recommend that you give one or both of these a try! If you want features upon features, try AOKP, of you want streamlined and simple, give SlimRoms a shot.

Hope that helps!
[T-Mobile LG G4] eruisi:
Thanks everyone. I will try the ROMs suggested by you folks.

I would hope there is a stock ROM rooted with multi-user enabled. I do feel stock ROM has better camera driver.
[T-Mobile LG G4] TecknoFreak:
What you mean multi-user enable? Do you mean this? Because the stock LG g4 port have that
[T-Mobile LG G4] eruisi:
Yes, this is what I am looking for. How to get this stock LG G4 port? Is it MM based or Nogurt based?
[T-Mobile LG G4] TecknoFreak:
Is MM base but since is a UX5 port it looks nicer then just our own stock. Try it is very nice, I highly recommend it specially from a guy that HATES Stock roms since the very first Android phone G1. If is not PURE AOSP base from Android then is no good to me and I like this one.

https://xdaforums.com/showthread.php?t=3614857
[T-Mobile LG G4] eruisi:
TecknoFreak

Did you try to add a new user for LG G5 Port ROM? I just installed this ROM on my H811 and tried to add a new user, but it shows "Deleting users, cannot add users. Try again later"

What the hell to show this function if it doesn't really work.
[T-Mobile LG G4] TecknoFreak:
I'm on Nougat mate. I don't have a use for that option so I dunno if it works or not on that rom. Right now I'm on a new rom Nougat stock With G6 ported for h811 and is amazing. I will post later over the weekend.
[T-Mobile LG G4] eruisi:
Ok. I think the multi-user feature doesn't work in G5 port. Would you please try it in your new Nogate G5 port ROM.

I like all nice features in G5 port, but missing multe-user feature is a killer.

Thank you very much to bring these amazing ROMs.
[T-Mobile LG G4] TecknoFreak:
Well. G5 port is actually [MENTION=6917540]Astrako[/MENTION] work mate I was linking to his OP. As for the G6 port he also is the guy to thank even I will port his port to H811. I should of been release the rom long ago but I'm just working on things to perfection.
[T-Mobile LG G4] eruisi:
Did you try add a new user to G6 port? It takes 30sec to try I guess. If works, I will definitely wait for your port ROM.
[T-Mobile LG G4] eruisi:
For the time being I had to go back to lineageOS which has a stable multi-user feature.

Looks like both G5 or G6 port won't enable multi-user feature.

I also tried SlimRom which does have multi-user feature, but ROM itself not stable, e.g, Phone reboots when USB debug is enabled and USB cable is plugged.

I really hope G5/G6 port could enable multi-user. It runs very cool and stable.

Thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] pezza123:
I upgraded my blue angel to WM6, which is brilliant. Only problems I'm getting are: turning off the phone from the menu leaves the green led flashing, and the phone can't be turned back on without a soft reset. That I can live with.

Second, it seems the upgraded rom doesn't use a serial connection over USB any longer, which is a pain, as I use Linux and the device doesn't appear as /dev/ttyUSB0 any more :(

Thirdly, when using wm2003 I was able to add my Linux box as a NAT router and surf via bluetooth. The router was discoverable, and the PAN service appeared on the list of services, now it doesn't, and I have no way of using the internet via bluetooth any more. Any suggestions welcome. I like using the upgraded rom too much to go back.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Kasush:
I can help with the USB over serial change. (I am also a linux user). search for rndis kernel module and use it with opensync and a perl plugin for opensync. I am sorry I don't have the names, but I have not yet fully configured it and am syncing in XP inside vmware. I plan on readdressing this as soon as I got a break from work.

Sorry for being vague but I expect that if you successfully synced WM2003 and linux you will be able to use these hints with skill.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] pezza123:
Appreciate it, thanks :) I'll look into that. It seems the rom upgrade syncs via TCP/IP, as xp needs its DHCP service enabled for activesync to work. With wm2003, I was able to sync with my Debian box over bluetooth and wifi as well as the cradle with synCE, which was very nice, and I miss it now it's gone. I'll persevere.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] pezza123:
Just bumping this thread to say it's all working, syncing nicely with evolution. The Ubuntu howto in the link below applied equally to my Debian installation as far as packages were concerned (well, Ubuntu's Debian-based after all) and with appropriate changes here and there should help users of other Linux distros too.

http://www.synce.org/moin/SynceWithUbuntu
[LG Watch Urbane] GiuloMaster:
Hi,

at the first installation I connected my watch to the phone via bluetooth and I could decide whether to answer either one or the other. After inserting a sim with the same number I can only receive either by phone or by clock depending on which of the two sim is set master.

I want to leave the sim in the watch, but if connected to BT decide what device use to answer.

I suppose that I must disable data line so not see the sim but doing so prevents me from making calls from the watch.

In addition BT paring setting on the phone I see that there is only the sharing of contacts and not as originally also audio and multimedia

Any suggestions?

Sorry for my english
[Samsung Galaxy S8 Questions and Answers] calinoi:
So, the thing is my parents live in Canada and they bought me a Galaxy s8 from the Samsung Store for me, and I live in Europe. My question is, can I use the phone here? The model number is SM-G950W and I just found out the global model is SM-G950F. Is there any reason for me to worry? From what I can see the 4G LTE cellular bands are different.

Cheers!
[Samsung Galaxy S8 Questions and Answers] Deleted member 7979271:
iirc if they unlock it in Canada you'll be fine.
[Samsung Galaxy S8 Questions and Answers] calinoi:
what do you mean unlock it in canada?
[Samsung Galaxy S8 Questions and Answers] Deleted member 7979271:
Activate it with Canadian SIM and make a call, that should activate it but don't take my word for it, not sure if it applies to your model.
[Samsung Galaxy S8 Questions and Answers] dagrim1:
On the european one I have (and I live in europe, so that's a good thing) it says 'for eu sim cards only' or something like that on the box. Would have to check the exact text this evening (not at home now). But from what I understand you can't simply use another regions S8 just like that.

Not sure how exactly it works though
[MTCD  Android Head Units Q&A] marchnz:
Ok - need to figure out how to force this PX3 board to 'maskrom' - this is the procedure where the NAND is suppressed by grounding the I/O or Oscillator to effectively stop the NAND. This then places the RockChip PX5 into Maskrom mode to then connect/reflash via USB.

Anyone tried this?

Feb 2018 - MASKROM methods have been identified for both PX3 and PX5 Modules. See posts later in thread.
[MTCD  Android Head Units Q&A] nixfu:
You seem to think you have both a PX3 and a PX5 board....it is one or the other.
[MTCD  Android Head Units Q&A] marchnz:
Thnaks for your reply - clarifying [I have a (JY) MTCD with HA 2..56 MCU PX5 stuck in a boot loop]

I have a PX3 Board that I have swapped back in to test - it is OK. The PX5 goes black screen if trying to boot from SDCARD recovery and I cannot seem to force it into [maskrom] to flash from PC either.

Would be interested to hear if other PX5 users who have swapped from PX3 to PX5 can access recovery OK.

Note that I foolishly screwed up and flashed a custom image thayt contained what I think may be the wrong achitecture of SUPERSU, hence the boot loop. BUT this doesnt explain why I can no-longer enter recovery, or does it?

Regards,
[MTCD  Android Head Units Q&A] ptclabs:
try holding the reset button for about a minute. it should auto restart into recovery. it will first go off, then it will either pop back on suddenly or start turning itself on and off. if it does the on and off thing i usually let it boot to recovery on the third one
[MTCD  Android Head Units Q&A] marchnz:
Thanks for the info.

Ive done everything but holding the power/vol knob or reset for 1 minute.

Tried forcing the unit into mask rom by very carefully exposing some of the obviously IO tracks between the cpu and flash and shorting a pair (this is the method described elsewhere, but usually there are copper test pads (you'll see these on the px3 module but not px5))

No matter what I try, I cant get my pc to see the head unit via either usb sockets. I made a 1 to 1 usb A male cable which works with a nexbox OK but not these headunits. The HU is a JY UL124 orginally px 3. It has 2 sdcard slots and two usb.
[MTCD  Android Head Units Q&A] marchnz:
After significant research and testing, I have a recovered PX5! See Post#1
[MTCD  Android Head Units Q&A] ikerg:
Good.....clap clap clap

Your tutorial is very clear and useful for other people....No more bricked devices....
[MTCD  Android Head Units Q&A] marchnz:
Thanks - updated op with a couple of images of my test/recovery jig and software.
[MTCD  Android Head Units Q&A] audisean:
good work there - would like to check my px3 board so did you ground to GND or D0 for reset on px3 pads ? and if you could show which wires on usb lead you connected to pin 27 & 28 on GL850 chip that would be very useful thanks
[MTCD  Android Head Units Q&A] marchnz:
Great question and good spotting - on px3 its possible to force "maskrom" by shorting [gnd] & [d0] pads. Unfortunately px5 do not have these pads and can only be achieved on px5 via carefully exposing track insulation to NAND - fortunately px5 will enter "loader" mode on recovery. So, no I did not do this, I used a GS board I have as a spare part and modified it to force recovery, by removing the SOM header "recovery" pin and grounding that pin via a switch - to force the SOM into recovery.

Note that OTG USB connections are made to the USB switch IC (if fitted) U27 [fsusb42]. If this IC/USB switch is not fitted, more drastic mods would be needed to disconnect the usb connections to the usb hub IC (by disconnecting the SOM header pins.) If you have a GS, you have U27. If not you will need to check.

Happy to answer questions here, we can all benefit through sharing.
[MTCD  Android Head Units Q&A] audisean:
Thanks for reply - my px3 board appears dead in unit thus far - think i've worked out how to solder usb A cable now just didn't want to cause any damage mixing tx/rx wires - i'll have to retest but i think I had 3.3 volts at GND & D0 pads - no time today but will have a go tomorrow (hoping this board is where Nand or fried chip fault lies) I have ordered a PX5 board so hopefully will get unit working
[MTCD  Android Head Units Q&A] audisean:
Had a try with px3 board - lifted pins 27 and 28 - put software and drivers on laptop - soldered usb lead to d+ and d- on px3 board and ground traced from u27 and ctl_recovery wire - nothing happens still - power at u27 is 3.3 volts
[MTCD  Android Head Units Q&A] marchnz:
Good work! How have you isolated the header pins - if they are still all connected (ctl_recovery, d+,d-) to respective ICs, it wont work because of contention with the connected ICs. E.g. ctl_recovery is connected to MCU and is pulled up to +3.3v by MCU - my solution was to remove respective header pins by careful desolder - they can then be refitted.
[MTCD  Android Head Units Q&A] audisean:
Knew i'd missed something - header pins still connected so will try to isolate guessing I need only connection at SOM board only..
[MTCD  Android Head Units Q&A] audisean:
pins isolated but no luck yet.... think maybe my chip is faulty (others report some px3 chips come from faulty batch) so will wait px5 board delivery - if that works I might order a replacement px3 chip and try replacement
[MTCD  Android Head Units Q&A] Cid6.7:
:eek: A bit over my head

Any chance I could get a hand ?

Maybe over Hangouts or something ?

Please Please Pretty Please lol ;)

Here's what I'm workin with https://goo.gl/photos/uNTpFnUYJxZ3VwSJ7
[MTCD  Android Head Units Q&A] audisean:
Got the new PX5 board (12 days from China :) ) put into head unit and worked straight away - posting here as I had major trouble re-soldering pins 27 & 28 when I pulled a leg off GL850G usb chip - see attached pic of wire I had to solder in place... thinking if I did this again I would probably just make a break in circuit tracks and use conductive glue or nickel pen to remake circuit - PX3 board is still dead - never got usb to pc connection - as for Cid6.7 board - looks like you found the usb hub chip and switch chip (different boards to mine though) pin 27 & 28 are opposite dot on chip - usb switch chip should go +5v, sel, d+ , d-, and ground
[MTCD  Android Head Units Q&A] Cid6.7:
Is all this done just for the pc to detect the unit..?

If so what if the pc already detects it BUT unable to write to it with 0 modifications done to it..?

https://goo.gl/photos/m7NGyrkD4ef2YydD7

audisean what did you pay for the PX5 board if I may ask..? I'm wondering if I am able to swap chips from Sofia to PX5 with no mods ;)
[MTCD  Android Head Units Q&A] audisean:
I paid about £95 for the board with airmail dispatch - not sure if it would work on yours - fitment looks similar with pin header - Witson 32814450733 is what I bought - worked straight away and recognised settings from previous android system in unit. The PX3 mods were necessary for otg cable to link pc and flash - if you have recovery by SD card or front usb you won't need it. Sofia looks pretty different but if you can link pc did you try rockchip batch tool ?
[MTCD  Android Head Units Q&A] marchnz:
Use tools, driver and android tool v2.35 from my pack and retry.
[MTCD  Android Head Units Q&A] fabiusx01:
I'm sorry I can not find your package with the software you could send me the link.

I found it, but I have a new problem :rolleyes::rolleyes:

I made progress, I managed to install sdupdate of malaysk, when I start the "Navigation System" logo appears but I can not get into recovery mode I tried everything .....
[MTCD  Android Head Units Q&A] fabiusx01:
:D:D:D wowww finally I succeeded ... I unmounted the card again and I tried reflash the original rom 6.0 finally installed it, now since I have a hard head try again to install android 8 :cool:
[MTCD  Android Head Units Q&A] elalvaro19:
Help with connections

Hello

I have an mtcd drive that I can not enter into the recovery mode in any way, this is the only way to recover it but I do not clarify with the information. I have a px3 motherboard that I attached in the photo. In order to detect the motherboard on the computer, do I have to make a wiring like the one attached to the photo or do I have to do something else?

Please I need your help is the only way I have to recover my unit
[MTCD  Android Head Units Q&A] scorillo_ro:
Yes, should work. Make the OTG cable and connect it as in the schema. Just flip the board in your picture on the other side. The pin numbering starts from the corner in diagonal of the one where the GPS antenna is soldered.
[MTCD  Android Head Units Q&A] elalvaro19:
I have made the otg usb but it does not work, it does not detect the computer. The resistors are 12k and 15k in pin recovery (pin 20) and pin usb detect (pin 28) I have a voltage of 1.8V, can that be the problem? If I remove the resistance 15k the computer detects the usb but not in the correct mode . Where is the problem?

Thank you.
[MTCD  Android Head Units Q&A] scorillo_ro:
Read the following post and maybe move the discussion on that thread which is more specific to the method you are using.

https://xdaforums.com/showpost.php?p=75994117&postcount=21

Also try to enter the maskrom mode. See the attached picture.
[MTCD  Android Head Units Q&A] elalvaro19:
Solve by making the cable smaller, thanks
[MTCD  Android Head Units Q&A] kmlnvm:
I've got a problem, PC detect device after connection but after few seconds it disappears.
[MTCD  Android Head Units Q&A] kmlnvm:
By accident I overrided LOADED partition 0x000000 is there any change to revive device?
[MTCD  Android Head Units Q&A] kmlnvm:
I manage to fixed loader, by finding maskrom key, thanks to this guy https://xdaforums.com/showpost.php?p=75931327&postcount=129
[MTCD  Android Head Units Q&A] marchnz:
Just flash it with complete oreo partitions or android 6 update.img, depending on the OS you want.
[MTCD  Android Head Units Q&A] scorillo_ro:
try maskrom mode

read https://xdaforums.com/android-auto/...px3-5-headunit-mod-recover-flash-som-t3766892

LE Just saw you managed to enter maskrom
[MTCD  Android Head Units Q&A] typos1:
Why you dont simply flash [MENTION=5092263]Hal9k_[/MENTION]'s or Malaysk's ROM, both of which are rooted [MENTION=5092263]Hal9k_[/MENTION]'s has Magisk), you dont need to back up your ROM as there are many, many stock ROMs available for download on XDA.
[MTCD  Android Head Units Q&A] kcs58box:
Hello there

I failed to upgrade

IDB failed?? (like photo)

What is the reason??
[MTCD  Android Head Units Q&A] InTheWorks:
I have already installed both Hal9k_ and Malaysk ROMs, but they are not what I am looking for.

I also would like to understand the process of backing up my ROM. It's also not entirely clear how I would flash it from Linux. I presume both backup and flash would be possible from the same tool. Do such Linux tools exist?

Eventually I would like to get to the step where I can flash a patched boot.img since that seems impossible from sdcard.
[MTCD  Android Head Units Q&A] typos1:
I dont think anyone has actually managed to backup a ROM from an MTCB/C/D/E device.

I use Ubuntu, but I ve never needed to flash a ROM from my pc, I ve used ADB to flash ROMs on phones before, or at least to push them to the phone, been years since I ve done that though, I just flash "on device" nowadays.
[MTCD  Android Head Units Q&A] InTheWorks:
Isn't that what happened in this thread:

https://xdaforums.com/android-auto/mtcd-software-development/px5-oreo-rom-t3736950

using windows tools?
[MTCD  Android Head Units Q&A] marchnz:
Yes, OTG method to backup Android Firmware with Rockchip tools. Thats what I did to extract Oreo.
[MTCD  Android Head Units Q&A] typos1:
Lol, I m subscribed to that thread.

You wouldnt "flash it from Linux" . . . well you would - youd flash it from Android recovery and Android IS Linux.
[MTCD  Android Head Units Q&A] InTheWorks:
I hate to ask, but that thread is long and full of noise. What tools did you use? Where can I get them from?
[MTCD  Android Head Units Q&A] InTheWorks:
Can anyone confirm that AndroidTool came from here:

https://github.com/rockchip-linux/tools
[MTCD  Android Head Units Q&A] InTheWorks:
Does anyone know why I can't fastboot boot.img?

Some background. I couldn't find any way to backup my ROM using linux tools. So I downloaded the ROM extracted from this thread and pulled out boot.img.

I then did:

adb reboot bootloader
fastboot -i 0x2207 boot boot.img

The unit responds with:

downloading 'boot.img'...
OKAY [ 0.599s]
booting...
OKAY [ 0.000s]
finished. total time: 0.599s

But the unit never boots.

I have a permanent usb otg connection on my unit. The usb lines from the SOM are disconnected from the usb hub. I can see a bunch of bad usb activity in dmesg after the fastboot command:

[282266.786283] usb 3-2: New USB device found, idVendor=2207, idProduct=0006
[282266.786296] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[282266.786306] usb 3-2: Product: rk30xx
[282266.786313] usb 3-2: Manufacturer: Rockchip
[282266.786324] usb 3-2: SerialNumber: 0123456789
[282266.786800] usb 3-2: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[282266.786821] usb 3-2: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
# the next part happens after fastboot command
[282291.166186] usb 3-2: USB disconnect, device number 5
[282291.878774] usb 3-2: new high-speed USB device number 6 using xhci_hcd
[282291.990868] usb 3-2: Device not responding to setup address.
[282292.194871] usb 3-2: Device not responding to setup address.
[282292.398775] usb 3-2: device not accepting address 6, error -71

I've tried everything I can think of. So I thought I would double check if boot.img from the oreo rom should be bootable in this manner.