Related
HuiFei - 2 DIN Pure Android 4.2.2/4.4.2/4.4.4 RK3066/RK3188 Car Stereo Radio Head Unit. KGL/KLD/RM/GS/JY/MD/KYD/BN/HA [ROOTED]
This is a new thread for this car dvd that was first reported on comment #2224 of the AN-21 U thread.
Probably you are here because:
you want to root your unit. Only units with ROMs 4.2.2 can be rooted (see below how). The only way to have a rooted 4.4.x is installing a pre-rooted ROM (see below how)
you have a problem (no internet, no sound, buttons do not work, bad mic quality, rear camera image not showing, door opening not showing, etc.
you want to upgrade your unit to a newer software that has sleep mode, personalized music app, personalized functions, root, xposed, can remap buttons, etc.
All this is covered in this post and most of the problems that you can have are summarized in this post too. Please read this first post before asking. And use the search function of the thread, before asking. Thanks.
TRICKS THAT MIGHT SAVE 1000 QUESTIONS ON THE THREAD
Read below and here for basic questions asked and answered 1000 times.
How to root my unit. Only 4.2.2 can be rooted with an app (see below). To have rooted 4.4x you must install a pre-rooted ROM (see below)
Get sound when in reverse (thanx to @Keylo Lo)
here
Engineering/Factory settings password "126" (thanx to @blankers)
This allows you to change logo, sound volume, SWC codification, etc.
Activate USB debugging --> Go to Factory Settings and enter password "adbon".
System sound is low compared to Radio--> Go to Factory settings and change volume levels
GPS button does not trigger GPS app You need to choose predefined GPS app, in Settings--> GPS
Get Into Recovery
1 Press reset button and power button together
2 After about 5 secs release reset button, but keep pressing power button
3 When booting screen appears release power button.
4 It boots into recovery.
--Update 1-- some units without front USB have a different procedure
Firstly power on the unit and then long press the power button and then reset. Then the unit will get three rings and you loose your hand on the power button and short press the power button again. (thanx @netay)
--Update 2-- some others have this procedure (thanx @R4D3N)
1. Turn off the unit by holding 3-4 sec the power button.
2. Hold the RESET button + POWER button for 5 sec
3. Release the RESET button and keep pressing the POWER button for 2 sec
4. Release the POWER button and wait. The Recovery menu appears.
5. With the Volume knob you can move up/down and long press on Volume/Power button to select the option.
Get Into Bootloader
The process is basically the same, with the difference that you need to have the computer attached to the unit via the front miniUSB (if you do not have a front USB, you will have to ask your seller how to get into bootloader mode)
1- boot the unit as usual.
2- plug the front usb of the unit to your computer usb.
3- Then, push the reset button and the power button at once and keep them pushed. The reset button is the tiny pin next to the mp3 sdcard. The power button is the volume knob. You will hear the power cut throught the speakers.
4- Release reset button and keep power button pushed. Now the unit will reboot. You will see nothing, just a black screen. Do not release the power button yet. Your computer will detect a " new hardware", that is the RolckChip. When you hear the windows noise of new detected hardware, you can release power button. It will automatically install the drivers.
------------------------------------------------------------------------------------------------------------
HOW TO UPGRADE YOUR SYSTEM
BEFORE UPGRADING YOUR UNIT YOU MUST KNOW
MCU your unit, there are many (KGL, KGL1, KGL2, KGL3, KGL4, KGL5, KLD, KLD1, KLD2, JY, GS, KYD, MD, BN, HA, MX), If you install the wrong MCU, you will brick your unit.
To know which one you have. Go to Settings -->About
If still not clear, see: here or here.
If you cannot find it here, it probably means that you are in the wrong thread.
Resolution of your unit. 800x480 or 1024x600. If you install the wrong ROM, you will brick your unit.
Chip of your unit RK3066 or RK3188. It does not really matter, ROMs and MCU are compatible between chips.
IT IS ADVISABLE TO BACKUP YOUR SYSTEM BEFORE PLAYING WITH IT
Upgrading is supposed to be a safe operation, but you never know what can happen. So, before updating make sure that:
1- To backup of your system the easiest way is download nandroid root from google play, and do a nandroid backup with TWRP format). Save it in your external SD.
2- make sure you can enter in bootloader mode (see below how to)
3- it is recommended to backup your apps and data (use titanium from google play). The update will do a factory reset.
FOLLOW THIS TO UPGRADE YOUR ROM AND/OR MCU
0- Do a back up (copy the files somewhere safe) of your internal SD card memory. It will be wiped during the process.
1- Download the ROM (Resolution 1024x600 or 800x480) and MCU (KGL, KLD, JY, GS,RM, MX, BN, HA) for your unit.
ROMs--> repository This will get you a file named update.img. There are different "flavors" of ROMs.
Code:
- [user=853627]@coudu[/user] (rooted, stock). Early v4.0 and v4.1 have some problems.
- [user=3590033]@Malaysk[/user] (rooted, with very useful mods, some come with NEXT launcher)
- [user=6041319]@dsa8310[/user] (rooted, almost stock)
MCUs--> Latest MCUs by Malaysk are here . This will get you a file named mcu.img
2- copy the update.img you have chosen to the root of your GPS card.
3- copy the mcu.img for your specific unit to the root of your GPS card (if you do not want to update mcu.img, you can skip this step)
4- insert back the GPS card to the unit. If no window pops up, reboot the unit. At boot, the presence of update.img will be detected and a pop up window will ask you whether you want to update your unit. It will automatically reboot into recovery mode and update your unit. Once done, remove update.img and mcu.img from the root of the gps card or you will be asked every boot for an update.
5- In some Coudu´s (sd partition of 3Gb) and Malaysk´s ROMs versions, it is necessary to do a factory reset just after the first boot so that everything works properly.
6- If you lost buttons or radio after the upgrade --> Go to Factory settings (password 126) and choose the proper canbus for your car and the radio chipset. You can change boot logo if you want.
* If you get Google services error after upgrading to KitKat see this and this
------------------------------------------------------------------------------------------------------------------
THINGS YOU MAY WONDER BEFORE BUYING A HEADUNIT
Code:
[B]- Boot Up:[/B]: time is around 30s.
[B]- GPS[/B]: GPS positions very fast. TomTom, Navigon, Sygic, and regular off-line GPS work. Navigon and Sygic have some problems with some ROMs
[B]- Stand by mode[/B]: Latest ROMs and MCU have the possibility of choosing stand by mode with various times chosen.
[B]- Radio:[/B] radio stations are saved as frequencies
[B]- Bluetooth contacts:[/B] contacts are saved on the device.
- Works fine with Bose system (Audi)
- Possible ground loop noise that needs some tricks to be removed (see section problems)
- Torque works and can run in parallel with A2DP
- ELM327 works (might need special app like CarService in very weird cases)
- Camera works (might be better to get the one with RK3188 chip)
- There is no automatic brightness control because the unit does not have light sensor, but there are apps that can help
- The touch screen is extremely responsive. It works as good as most phones.
-------------------------------------------------------------------------------------------------------------------
HOW TO ROOT AND INSTALL TWRP
Instructions to get root (thanx to @webdude12)
It only works for Android 4.2.2. If you want to root 4.4.x you need to take apart update.img and inject SuperUser app (this is only for experts as @coudu, @Malaysk, @dsa8310 ). The alternative is to install a 4.4.x pre-rooted image and you do not have to do anything else. See below in HOW TO UPGRADE YOUR UNIT section how to do it.
If you want to root your 4.2.2, download Root Master 2.1.1 here
Code:
1- Install the APK.
2- Make sure you are connected to WiFi and you have an internet connection.
3- Open Root Master (do not upgrade to newer version unless you can read chinese, The newest version has different options, all in chinese. Version 2.1.1 just has a button that says "root".))
4- Press root button
5- Chinese characters will flash across the screen.
6- A second popup box will appear, press the purple button.
The app will automatically install SuperUser.
This program connects to servers oversea sending hardware information. The downloads a script that will attempt to root the device. If the first script fails, it downloads additional ones. Future goal is monitor this communication with a data logger and find which script works, so that a unique program can be written to achieve root.------------------------------------------------------------------------------------------------------------------
How to install TWRP recovery (thanx to Abdul_pt from Freaktab and 1-2-Hak and coudu)
You do not really need to install TWRP unless you wanna mod the rom yourself, if you mod roms you will know that already.
- a.t.m. you need a mouse to use TWRP because touch is not working yet
- if you install TWRP, you will not be able to update the update.img and mcu.img the way it was explained above.
If you still want to install TWRP:
Android 4.2.2 800x480
Download files here
And follow the post by 1-2-Hak
Android 4.4.2 800x480
Follow this: this
TWRP for 1024x600
See this post------------------------------------------------------------------------------------------------------------------
TRICKS AND MODDED APPS THAT DO WONDERS
Install app without adb when regular install does not work
Sometimes the app won't install normally and you need to sideload it.. This means that you need a computer and adb wifi. There is another way with which you won't need a computer. You just need to install a terminal emulator (you need root ).
1- Download the terminal emulator app you prefer
2- Download the app you want to install to /mnt/sdcard
3- Open terminal emulator
4- On the terminal navigate to /mnt/sdcard by typing
Code:
- cd /mnt/sdcard
- su
- pm install "NameOfTheApp".apk
Done, you are app is now installed.
Modified Radio Apps
To install radios you need to copy the app using ESExplorer or Root Explorer straight to /system/app in place of MTCRadio.apk
Radio version 4.2.2 800x480
Blue theme (thanx @1-2-Hak)
Rally style Buttons have been moved and skin changed for a Rally like one.
Forest style. Colors have been changed and frequency name is in big.
Radio version 4.4.4 800x480
Blue tint. Stock radio with big names and all in blue shades.
Red tint
Radio version 4.4.4 (Malaysk v1, aka alive)
1024x600. Has animation, in blue tones
[*]Car Service. Allows to use SWC and buttons with 3rd party apps (Latest Malysk ROMs already include it).
Download here (thanx @@KeiserSozeyFr)
If it does not install, copy directly to /system/app
[*]Microntek HeadUnit Service Latest Malaysk ROMs include it. It allows to use SWC with non native apps. It allows to make calls and send messages from Android part of HU, and to show toasts. You can find it straight on Google Play.
There is a modified version (probably outdated) with early start of services here
[*]Moded Music app. Two versions. One is the original with expanded list, so full names can be seen, and the other one has the list integrated in the background so it is always visible.
http://forum.xda-developers.com/showpost.php?p=53352994&postcount=894 (thanx to @dark alex)
anoher one here
[*]Set Loud Latest ROMs do no need it.
Method 1:
Just install this app: http://forum.xda-developers.com/showpost.php?p=53463910&postcount=963 (thanx to @dark alex)Method 2:
You need Tasker or Automagic or similar app.
Set up a task that runs at boot with the following code as "shell command"
am broadcast -a com.microntek.irkeyDown --ei keyCode 44
How to: http://forum.xda-developers.com/showpost.php?p=53553617&postcount=1058
[*]Speed-sincronized volume increase (AKA GALA)
This app will modify the volume of your unit according to the speed. The amount sensitivity can be adjusted.
http://forum.xda-developers.com/showpost.php?p=53441283&postcount=931 (thanx to @dark alex)
[*]PowerAmp Toast (thanx @agentdr8)
This app will show title/album/album art when tracks change while PowerAmp is in background.
http://forum.xda-developers.com/showpost.php?p=53964813&postcount=1461
[*]Rear Camera without icons (icons were included in the KitKat version 4.4.2) (thanx @typos1 and 4pda.ru guys)
http://forum.xda-developers.com/showpost.php?p=56888840&postcount=5096
[*] KLD Launcher 4.4.2 with bigger date
Launcher see picture
---------------------------------------------------------------------------------------------------------
FILE REPOSITORY, FIRMWARES and MCUs for KGL/KLD/GS/RM/JY/MD
Repository (everything is here, firmware up to date, mcus not so much)
More updated MCUs from @Malaysk & @darkleo --> here
Some of the firmwares are... (list not updated)
Custom KitKat 4.4.2 by 4pad.ru (RK3066)
Coudu's 4.4.4 v4.2 (RK3066) (January 2015 release), see here
- Coudu v4.0 and v4.1 have some problems. v4.2 is good (specially releases 150113 for KLD and 150113 for KGL). You might need MTCControlSettings.apk as in these latest releases coudu removed it.
Malaysk's roms (RK3066) w/ and w/o NEXT launcher, also 4.4.4 here
JY Android version is this one
Malaysk's roms (RK3066) version 24/05/15 Download here. It allows the remapping of the radio buttons.
dsa8310 JY rooted ROM 150513 (RK3188) Download here
-------------------------------------------------------------------------------------------------------------------------------
WIKI-Page
Basic info on everything
Another wiki with general info here-------------------------------------------------------------------------------------------------------------------------------
PROBLEMS AND SOLUTIONS FOUND BY THE USERS
Unfortunately the first issues with the promising unit arrived.
@webdude12 got a black screen while driving due to a broken clip (see attachment to figure out which one). One solution is to glue the clip so that it does not get loose. Not doing that can end up in major problems.
Unit might not boot on very hot conditions as it has a thermostate to avoid possible problems. It will work normally when cooled down.
Some apps do not show completely in the screen due to the low resolution.
However, there's a great solutions for that:
- you need root
- install xposed framework (google it)
- probably you need to sideload the apk with ADB as the unit refuses to install it normally.
- install "app settings" module in xposed framework (you can change dpi for individual apps and make them fit in the screen)
When add a google account, it doesn't show under accounts
fix --> http://forum.xda-developers.com/showpost.php?p=53809274&postcount=1303
Wifi or buttons do not work after update to 1.86 or 1.99 firmware versions
- This happens because the MCU or kernel of the new version is not adequate for your unit. Luckily MCUs and kernels are mixable for the same unit.
fix --> Install newest firmware with an older MCU in the usual way. Then install the kernel of a version you know used to work.
To install kernel alone --> Here and files needed here.
Kernel install for doomies (with pics): here
No radio reception
fix --> your ground cable might be loose Sold it back. see this and this and this.
SD card unexpectedly removed // USB unexpectedly removed
fix --> Thanx to @ R4D3N here
Mic sound is awful
-- WARNING --
For any unit, before removing the capacitor with the purpose of separating the BT card from the internal mic, you must make sure (with a multimeter) that the capacitor to be cut interconnects the MIC entry of the BT card with the internal mic. Please note that the capacitor is on the motherboard in the immediate vicinity of the (vertical) BT card (pics on fix for JY units can help you)
fix for JY units --> http://forum.xda-developers.com/showpost.php?p=57982083&postcount=7036
fix for KGL units --> http://forum.xda-developers.com/showpost.php?p=55775852&postcount=3982 and http://forum.xda-developers.com/showpost.php?p=55769511&postcount=3964
fix for KLD units --> http://forum.xda-developers.com/showpost.php?p=56529110&postcount=4592
Bluetooth modules not pairing
fix --> http://forum.xda-developers.com/showpost.php?p=56450438&postcount=4544
Google service error after upgrading to KitKat 4.4.2
fix --> http://forum.xda-developers.com/showpost.php?p=56791126&postcount=4866
and --> http://forum.xda-developers.com/showpost.php?p=56793317&postcount=4925
Wrong door being shown open. Only VW and KitKat 4.4.2
fix --> Go to factory settings, change "Rude"
TomTom not working on KK 4.4.*
fix --> http://forum.xda-developers.com/showpost.php?p=56991862&postcount=5336
--WARNING-- if you installed chainfire SuperSU you have to slightly modify install-recovery.sh. You must substitute /system/xbin/su --daemon & --> /system/xbin/daemonsu --auto-daemon &
TomTom bundle: use maps stored on external SD// Update TomTom maps with map share free// Early start of softwares// SWC from boot/install-recovery.sh
see --> this (thanx to @dsa8310 WARNING: see post #10440 and comments therein when using install-recovery.sh)
summary of early start services commands --> here
Sygic not installing
see --> http://forum.xda-developers.com/showpost.php?p=58983985&postcount=9020
3G USB Dongle not working properly
Probably is due to the USB is underpowered. Use a (externally) powered USB hub. Or follow this how to to power the USBs of your unit.
how to --> http://forum.xda-developers.com/showpost.php?p=58949495&postcount=8949
short version-->http://forum.xda-developers.com/showpost.php?p=58970437&postcount=8983
the following 2-3 pages contain comments about that mod worth reading.
see --> http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614
Another how to for external powered USB hub--> http://forum.xda-developers.com/showpost.php?p=58979534&postcount=9011
3G connection lost after some drive
see --> http://forum.xda-developers.com/showpost.php?p=58539736&postcount=8162
and --> http://forum.xda-developers.com/showpost.php?p=58982926&postcount=9017
DVR camera not recording or stopping - DailyRoads Voyager app
see --> http://forum.xda-developers.com/showpost.php?p=58648519&postcount=8383
also --> http://forum.xda-developers.com/showpost.php?p=58977534&postcount=9007
Viper4Android not working properly
Check this and look for Viper4Android config here
When I try to install an app, I cannot tap the "install" button
This happens because you are using a screen dimmer. It is a protection function. Just temporarily disable screen dimmer app and you will be able to install the app.
Radio does not show proper pty
Download this modified version (it is v 4.2.2) of RadioMTC
Start apps while booting, you need install-recovery.sh script (included in latest Malaysk ROM)
Read this post to understand how it works. If PowerAmp is auto starting at everyboot, see this
Improve Radio quality by replacing hardware parts. Thanks to 4pda.ru
see --> http://forum.xda-developers.com/showpost.php?p=60895894&postcount=12932
and http://forum.xda-developers.com/showpost.php?p=60896400&postcount=12936
Remap radio buttons. Thanks to 4pda.ru and agentdr8
see -->http://forum.xda-developers.com/showpost.php?p=60941619&postcount=13030
Upgrade RK3066 to RK3188 (needs hardware replacement)
see --> http://forum.xda-developers.com/showpost.php?p=60972222&postcount=13086
or this --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
Replace damaged touch screen
tutorial --> http://forum.xda-developers.com/showpost.php?p=62832292&postcount=18752
I did not want to create a thread for this but I think it is best kept here then so if anyone want's to copy my signature to add aome links to the other sections here is it for you convenience:
Code:
MTCB Android Headunits: [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa"]Questions & Answers[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-android-head-unit-general"]General[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-hardware-development"]Hardware-Dev[/URL] | [*URL="http://forum.xda-developers.com/android-auto/mtcb-software-development"]Software-Dev[/URL]
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Please remove the asterisks (*) - That looks like this:
MTCB Android Headunits: Questions & Answers | General | Hardware-Dev | Software-Dev
"MTCB" covers Klyde, HuiFei (KGL), Joyous (Joying is reseller), GS, Eonon and many more vendors. Please check Settings->About tablet -> MCU Version. If it starts with "MTCB-" you are right in above forums.
Click to expand...
Click to collapse
Dear R4X users,
I am facing an issue since i bought this phone. I was using stock Global ROM for a while, after that I flashed LOS14 and now I am using Havoc OS. The thing that happens on every ROM is that touching fingerprint sensor wakes phone. I did not set up any fingerprints, I just skipped that configuration step. Is there option to disable that sensor? I cannot find anything in the settings, but I read somewhere that it should be possible to do by disconnecting device from driver via linux commands. Does anyone know how to find driver and device path? There are no matches when I scan all filesystem for "fpc".
Or does anyone know another way to disable that sensor?
Cheers.
follow this:
https://forum.xda-developers.com/xiaomi-redmi-4x/how-to/fixes-redmi-4x-t3858845
foneiamone said:
follow this:
https://forum.xda-developers.com/xiaomi-redmi-4x/how-to/fixes-redmi-4x-t3858845
Click to expand...
Click to collapse
I do not have this file present as I did not add any fingerprints. Altough I skipped fingerprint configuration, that sensor is still active and any touch wakes my phone.
Since no one could help me, I had to work it out myself. If anyone has the same problem, that's the solution:
Run this command:
echo -n "soc:fpc1020" > /sys/bus/platform/drivers/fpc1020/unbind
Fingerprint sensor is now inactive until next reboot.
Also, this thread can be closed now.
!!! Update lineage-16.0-20190910-UNOFFICIAL-clover.zip
https://androidfilehost.com/?fid=1899786940962581845
---------------------------------------
Download ROM https://androidfilehost.com/?fid=11410963190603907427
Supported-
DT2W
DT2C ( on Status bar)
exFAT
USB Preferences options (File transfe, usb tethering, MIDI,PTP,No data transfer)
Xiaomi performance setting option
!!!! Important
Unlocked Bootloader
Backup persist partition
(There are some project that changes your WIFI MAC Address. if it happened you will lost it forever.)
It shows wifi but after entering pwd it shows only saved. Can't connect at all.
Download TWRP--- https://mega.nz/#!qcA2BQIJ!xiBnnC0B4Z7fqpARbIY2ARdDY4hJLZgsriJsWaCCzNQ
-Boot TWRP
-connect your PC with USB
-your computer -Open CMD
cmd>adb shell
cmd>cd /dev/block/platform/soc/c0c4000.sdhci/by-name/
cmd>ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name/
cmd>dd if=/dev/block/platform/soc/c0c4000.sdhci/by-name/persist of=/sdcard/persist.img
(keep your persist.img in the safe place)
--------------------------
How to restore it if you have a problem.
(load your persist.img into sdcard.)
cmd>dd if=/sdcard/persist.img of=/dev/block/mmcblk0p48
------------------------------------------------------------
Step for Normal user
Flash Lastest Firmware (option)
https://github.com/XiaomiFirmwareUp...jKlFtxZa6wKy4bTGrLy5ptJJvfZy0d14c5fQlHypsZyLQ
Flash ROM
Flash GApps Nano 9.0
Boot System
Flash Magisk (Root Manager)-Option
-------------------------------------------------------------
****Step-For microG user (Test with NanoDroid 20.6)
Flash ROM
Flash Magisk (Root Manager)
Boot System for setting up Android.
Boot TWRP
Note download nanodroid here https://downloads.nanolx.org/NanoDroid/Stable/
-Flash NanoDroid-patcher
-Flash NanoDroid-microG
Boot System for setting up microG setting program.
-Self-Check --click menu for Adding System spoffs signature
-Google device registration (Enable)
-Google Cloud Messaging (Enable)
-Google SafetyNet (Enable)
-UnifiedNlp Setting
---tab Configur location backends menu then tic Deja vu location service
---tab Configure address lookup backens menu then tic Nominatim
Install fdroid.apk (lastest version. https://f-droid.org/en/) --No use NanoDroid-fdroid
-open f-droid program--->set up repo (Add 3 new repos below)
https://www.nanolx.org/fdroid/repo
https://fdroid.bromite.org/fdroid/repo
https://microg.org/fdroid/repo
Install satstate from f-droid
-Open device GPS by Use location widget from Status bar.
-Open satstate program and run GPS menu
Install MozillaNlpBackend from f-droid
Run microG Self-Check again but this time click UnifiedNlp setting---->Configure location backends-----Enable Mozilla Location Service
self-check Unifield status will pass all (6 options)
After a bit of a struggle I managed to get this installed and working last night
A few things I noticed:
1) It may have been previously unlocked by the ebay seller I got it from. The official unlocker I got from http://en.miui.com/unlock/ (https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/ has other details) had issues, finally got it, at one point in time, to say unlocked even though all 3 steps didn't have any checkboxes next to them... Strange, but I finally looked at the fastboot_unlock binary that came with the unlocker exe, and that indicated it was unlocked.
2) I found 3 different TWRP to try and install, with 2 of them (I _think_ the one linked here, and the one linked at the EU community thread above) kept giving me "too large to transfer". I finally got the one linked above by the following process:
start powered off
hold power + vol down to get to Fastboot
fastboot devices
fastboot -s <DEVICE ID> flash recovery recovery.img
At this point, the screen went black except for at the upper right it said "press any button to power off", and fastboot exe is saying "waiting for <DEVICE ID>"
press a button, device powers off, leave it connected to the computer
hold power + vol down to get to Fastboot, fastboot exe should see the device and now do it's thing to send/flash the recovery.img
after fastboot finishes, do fastboot boot recovery.img
should now boot to TWRP, should be able to tap a button/screen to get into it
3) I also found I needed to perform a device wipe/reset from within TWRP before copying the LOS and OpenGAPPs zip files over. First time I tried it without wiping it had some weird install/configuration left and caused major issues upon booting LOS. Seemed to think it wasn't a fresh install, and had most of the apps keep crashing and restarting.
Please tell me Is the problem of changed mac address occuring with gsi roms or it is also there with normal flashable zip roms
Can it be repaired by flashing fastboot rom with mi flash tool?
hey,
Can someone tell me what kind of processor mi pad 4 plus is using?
ARM, ARM64, or x86
You heard about search engines? --> https://www.gsmarena.com/xiaomi_mi_pad_4_plus-9295.php
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
r0b said:
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
Click to expand...
Click to collapse
Try LOS 17 Android 10
@tom.android:
I tried LOS 17, but it was not running well on my Pad 4 Plus.
So I switched to this one here and LOS 16 so far runs well.
Though I have a problem with auto brightness which is not working properly. Once activated it doesnt have any effect and from time to time it just lowers brightness to the lowest point.
From your LOS 17 post I grabbed the auto brightness fix and flashed it, but it didnt work for LOS 16. Is there another fix you know about?
Also from time to time the tablet wakes up without me using it and not going to sleep again. This results into the device being display on all night long. Really annoying
r0b said:
Hi Tom.
On one of your screenshots the lock screen says “charging rapidly”. I thought the pad 4 plus doesn’t support this function. Is it now possible with this version of LineageOS?
Click to expand...
Click to collapse
Looks like different device to me. ???
Hi all,
Recently I received my new Xiaomi mi8. Yesterday I was finally able to unlock the bootloader after 15 days. After that I started installing custom roms. All seems to work quite well except for the fingerprint sensor.
The fingerprint sensor works fine on any Xiaomi rom. However, it does not seem to work on any other custom rom. When installing Lineage OS 16 I am able to register fingerprints in the setup flow. After that I am able to unlock the phone exactly once with the finger print. After that the fingerprint system stops working (there is no haptic feedback anymore as well when pressing your finger on the sensor). In logcat I see the following messages when I try to unlock with the fingerprint:
Code:
04-27 17:42:53.924 4316 4316 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
04-27 17:42:53.926 4317 4317 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "vendor.
I have tried wiping everything multiple times (factory reset, format data, format dalvik + cache + system etc). I have tried flashing roms in a certain order (from xiaomi to custom). I have tried installing the latest firmware from
Code:
https://xiaomifirmwareupdater.com/
(latest stable and weekly). I have tried an older version of TWRP. Sadly, none of these steps worked in resolving the issue.
That's why I would really appreciate if someone could help me out in this :angel:! Thanks!
EDIT
After deleting the following files I am able to register new finger prints. After that I am able to unlock the device exactly once.
Code:
/data/system/locksettings.db
/data/system/user/0/fpdata
/data/system/user/0/settings_fingerprint.xml
marvingfx said:
Hi all,
Recently I received my new Xiaomi mi8. Yesterday I was finally able to unlock the bootloader after 15 days. After that I started installing custom roms. All seems to work quite well except for the fingerprint sensor.
The fingerprint sensor works fine on any Xiaomi rom. However, it does not seem to work on any other custom rom. When installing Lineage OS 16 I am able to register fingerprints in the setup flow. After that I am able to unlock the phone exactly once with the finger print. After that the fingerprint system stops working (there is no haptic feedback anymore as well when pressing your finger on the sensor). In logcat I see the following messages when I try to unlock with the fingerprint:
Code:
04-27 17:42:53.924 4316 4316 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
04-27 17:42:53.926 4317 4317 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "vendor.
I have tried wiping everything multiple times (factory reset, format data, format dalvik + cache + system etc). I have tried flashing roms in a certain order (from xiaomi to custom). I have tried installing the latest firmware from
Code:
https://xiaomifirmwareupdater.com/
(latest stable and weekly). I have tried an older version of TWRP. Sadly, none of these steps worked in resolving the issue.
That's why I would really appreciate if someone could help me out in this :angel:! Thanks!
EDIT
After deleting the following files I am able to register new finger prints. After that I am able to unlock the device exactly once.
Code:
/data/system/locksettings.db
/data/system/user/0/fpdata
/data/system/user/0/settings_fingerprint.xml
Click to expand...
Click to collapse
Hi. How to delete this file? The fingerprint system stop working and i don't resolve
I have been messing around with GSI roms on this device for a little over a month, and I've created some Magisk modules and an Xposed module to begin to fix the issues with the Cli display.
Disclaimers (READ THESE!!):
There are still a number of other issues with GSIs on this device, so I wouldn't recommend doing this if you use your razr as your main phone.
If you brick your device, it is your own responsibility. I am not responsible for any damage that my modules or advice might cause to your device. Do not blame me for bricking your device.
This is not written to be easy for beginners. If this is your first time modifying a device's firmware, I would advise against starting with this phone. But I would highly recommend you to start on a different device that has less restrictions and is much cheaper.
If I do not mention how to do something, you should look up a guide first before asking me. The guides that other people write are likely going to be much better and easier to understand than one I can write.
Please note that these modifications may not work on your device if the hardware is slightly different, even if it has the same model number as mine. These modifications are mainly a proof of concept, but I am open to modifying them to work on more devices.
If you are curious about how any of these modifications work, see the readme on the modules' github repositories.
By following the steps in this post, you accept that you may end up with either an expensive paperweight, or a mostly functional device with a GSI rom.
These modifications have been tested on my XT2071-3
First thing to do is to make sure you have a way of recovering your phone if it soft bricks. I downloaded the stock rom from lolinet. Make sure you have a rom that is the same version as your current rom. Motorola leaves anti-rollback enabled even if you have an unlocked bootloader.
If mess up, you can just restore it using fastboot (look up a guide)
If you really messed up, you can always try to use the "Rescue and Smart Assistant Tool", but that may be a last resort due to privacy concerns.
If you really really messed up, you may have to use a blank flash. I haven't ever had to use a blank flash, so I can't vouch for whether or not it will work. (don't do it if you don't have to)
The build number of the OS I used when installing the GSI is: RPSS31.Q1-40-34-15-10-15
Spoiler: Installing
It may also be worthwhile to flash copy-partitions-20210323_1922.zip from a custom recovery to prevent accidentally hard bricking your device. (this is recommended by the Lineage OS wiki for most devices with an a/b partition layout, so I figured I should probably use it just to be safe).
You can use thenameisnigel's unofficial TWRP image, or the unofficial lineage recovery that I attached to this post (I would not recommend flashing either one. Use "fastboot boot recovery.img" instead.) I attached the lineage recovery because it's easier to use without touch support, but either should work just fine.
You may also choose to root your phone with magisk before installing the GSI. It will be necessary for the post-install fixes, and may be harder to install after the fact.
I will not go into too much detail of how to install GSI roms, but here is a rough recreation of the fastboot commands I used:
Code:
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system gsi.img
fastboot -w
fastboot reboot
You should look up a tutorial if you need help. I'm not an expert on any of this.
I've tested:
This release of Phh Treble (the one with gapps doesn't work)
This release of Andy Yan's Lineage OS 19
This release of ponces' Pixel Experience GSI
All of them using the vndklite version, and I have not been able to get Android 11 to work.
Spoiler: Fixing the cli display
Once you boot into the GSI, you will notice that the Cli display will show a keyguard presentation that will freeze and stay on the screen after you unlock the device. You may also notice that touching the Cli display will interact with the main display, and not the Cli display like it should.
To fix this, you can install this magisk module: Razr5G Synaptics Touchscreen Device Associations
Before installing, you may want to mute your ringer, since it will break audio (more on that later)
This magisk module adds a configuration file that will map the touch screens to their respective displays.
Now the touch screen maps correctly, but there's still nothing to interact with.
To fix this, you can install another magisk module: Razr5G Foldable Device Fixes
These are two separate magisk modules because I will be releasing more modules that will utilize the cli display in different ways.
This magisk module will configure Android to treat the phone like a foldable device similar to the Samsung Z Fold. This is not the stock behavior of the device, which is why I will be making different modules that activate the display in a way closer to stock.
Now the cli display will actually show the UI if you turn off the display, close the device, and then wake the device. The UI will even transition from the cli display to the main display when you open the device. But if you close the device while the screen is on, the system will freeze. This has to do with Android's display manager referencing a display that the lid sensor just requested to turn off.
To avoid this conflict, I have an Xposed module this time: Cli Lid Functions
I recommend using LSPosed. You will need to enable this module for "System Framework"
This Xposed module will disable the lid sensor's ability to turn off the display. This is not ideal, but it's better than having to reboot your phone.
Spoiler: Fixing audio
For whatever reason, installing magisk modules that modify /vendor/etc on a GSI on phone will replace the audio policies with empty ones. This is not ideal, as it forces audio out of the speakers at full volume. The original audio policies still exist in the magisk mirror under vendor/etc (but not system/vendor/etc). You can overwrite the blank ones and change a setting to restore functioning audio.
1. Overwrite the blank audio policy:
You can do this with a root file explorer, or through the shell
Method A - Root File Explorer:
go to the magisk tmpfs (type "magisk --path" in a shell running as superuser. Example: `/dev/ABcD12`)
then go to .magisk/mirror/vendor/etc (you may need to show hidden files)
copy a2dp_audio_policy_configuration.xml and audio_policy_configuration.xml
paste them in /vendor/etc on the system root (make sure to overwrite the empty files)
Method B - Shell:
Run these commands in `adb shell` or your favorite terminal emulator
Code:
su
cp $(magisk --path)/.magisk/mirror/vendor/etc/a2dp_audio_policy_configuration.xml /vendor/etc
cp $(magisk --path)/.magisk/mirror/vendor/etc/audio_policy_configuration.xml /vendor/etc
After overwriting the files, do not reboot (otherwise they will get overwitten again).
2. Enable "Use alternative audio policy"
Go to `Settings > Phh Treble Settings > Qualcomm features` and enable "Use alternative audio policy"
3. Reboot
Now you can reboot, and you should have working audio again.
Spoiler: Working/Broken
What's working:
UI on the second display (opening apps, checking notifications, etc.)
Only one display on at a time
Display cutout
Camera (plus, only the outer camera works when the display is folded)
Volume buttons flipping when the lid is closed
Fingerprint
Wifi, Bluetooth, and Bluetooth audio (after disabling the hardware offload)
SMS (kind of... and only with an ims.apk)
Data
Battery life is better than stock
A lot more that I'm missing...
What's broken:
System UI is not optimized for the second display
Brightness on the secondary display
More that I'm missing...
I am still new to GSIs, so I haven't tested a whole lot, or attempted to fix much other than this.
Downloads:
Razr5G Synaptics Touchscreen Device Associations
Razr5G Foldable Device Fixes
Cli Lid Functions
Unofficial Lineage Recovery
While I could build my own GSI rom to deal with all of these issues, I chose not to since it would take more time. There is also another advantage of these modifications, which is that they can be applied to a wide variety of GSIs without having to modify each one manually.
Also, Motorola won't let a $1000+ phone boot with a modified vendor partition, for whatever reason.
This was my first time ever making a magisk module, my first time ever making an Xposed module, my first time ever working with the Android system on this low of a level, and my first time installing a GSI rom.
I may update this post with more progress in the future.
reserved