[HELP] Fingerprint sensor does not work in any AOSP or Lineage based ROM - Xiaomi Mi 6 Questions & Answers

I bought Mi 6 and I am not a fan of MIUI for its confused settings. I always flash a Custom ROM (AOSP or Lineage based) whenever I got a new device. This time, I flashed every custom ROM in the ROM sections and I got these issues.
MIUI Camera with "Portrait Mode" is missing (but solved by flashing ported MIUI Camera). Okay, that's fine.
Fingerprint sensor does not work.
It is working perfectly on STOCK ROM.
I found fixes like "FPC Fingerprint patch".
But my Mi 6 has "Goodix Fingerprint" (I found "goodix_fp" folder in /sys/class/ on stock firmware MIUI 9.0.2.0 stable).
I have no idea how to fix it.
I am pretty sure I followed every single instruction very well.
I think I have tried every available method but no luck.
But other users seem to be okay with Goodix fingerprint on AOSP ROMs.
For me, I cannot even find fingerprint option in settings.
It does not even respond like it was broken in any AOSP and lineage based ROMs.
Kindly, please help me with this because I cannot live without AOSP or Lineage based ROMs.

I had the same problem. I fixed it by adding
ro.boot.fingerprint=goodix
in /system/build.prop , FP option and home button will work after a reboot.
Make sure you have goodix binaries in /system/lib64 and /system/lib64/hw if not post here, I'll upload them

Jerwinn7 said:
I had the same problem. I fixed it by adding
ro.boot.fingerprint=goodix
in /system/build.prop , FP option and home button will work after a reboot.
Make sure you have goodix binaries in /system/lib64 and /system/lib64/hw if not post here, I'll upload them
Click to expand...
Click to collapse
Hey, I think I could use this.
also, when I do:
Code:
adb shell setprop ro.boot.fingerprint goodix
I get:
Code:
setprop: failed to set property 'ro.boot.fingerprint' to 'goodix'
Any idea?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

SM26 said:
Hey, I think I could use this.
also, when I do:
Code:
adb shell setprop ro.boot.fingerprint goodix
I get:
Code:
setprop: failed to set property 'ro.boot.fingerprint' to 'goodix'
Any idea?
Click to expand...
Click to collapse
No idea bro, Try editing the build.prop file with vi, it should work

Jerwinn7 said:
No idea bro, Try editing the build.prop file with vi, it should work
Click to expand...
Click to collapse
Nope...I don't know what is wrong with it...
Code:
C:\Users\SM26\Downloads\MI6> adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop': couldn't create file: Read-only file system

SM26 said:
Nope...I don't know what is wrong with it...
Code:
C:\Users\SM26\Downloads\MI6> adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop': couldn't create file: Read-only file system
Click to expand...
Click to collapse
Remount your /system with
Code:
adb shell mount -o remount,rw /system
then push the file. After that make it read only again with
Code:
adb shell mount -o remount,ro /system

Jerwinn7 said:
Remount your /system with
Code:
adb shell mount -o remount,rw /system
then push the file. After that make it read only again with
Code:
adb shell mount -o remount,ro /system
Click to expand...
Click to collapse
Damn it, you are absolutely right!
I've done this:
PS C:\Users\SM26\Downloads\MI6> adb root
adbd is already running as root
PS C:\Users\SM26\Downloads\MI6> adb remount
remount succeeded
Click to expand...
Click to collapse
and after that the PUSH command is working!
now when I do the GetProp i get "goodix" instead of "fpc" (no quotes of course)
but still the home button isn't responding.
maybe I'm missing the files you talked about earlier?
could you please upload them?

Try rebooting, chances of missing those files are low

Jerwinn7 said:
Try rebooting, chances of missing those files are low
Click to expand...
Click to collapse
I've rebooted.
at /system/lib64 I have: libgoodixfingerprintd_binder.so
and at /system/lib64/hw I have: fingerprint.fpc.so & fingerprint.goodix.so
don't know what their content is.
just know I can view them via 7zip

Jerwinn7 said:
I had the same problem. I fixed it by adding
ro.boot.fingerprint=goodix
in /system/build.prop , FP option and home button will work after a reboot.
Make sure you have goodix binaries in /system/lib64 and /system/lib64/hw if not post here, I'll upload them
Click to expand...
Click to collapse
Please upload them, I will try to solve it asap. Thanks.

Sithu Htun said:
Please upload them, I will try to solve it asap. Thanks.
Click to expand...
Click to collapse
I've attached the files
Note that I'm using AOSPA Extended (unofficial oreo) with firmware 7.11.6

SM26 said:
I've rebooted.
at /system/lib64 I have: libgoodixfingerprintd_binder.so
and at /system/lib64/hw I have: fingerprint.fpc.so & fingerprint.goodix.so
don't know what their content is.
just know I can view them via 7zip
Click to expand...
Click to collapse
Are you using the correct firmware required? Otherwise, it won't work.
BTW which ROM are you using?

Sithu Htun said:
Please upload them, I will try to solve it asap. Thanks.
Click to expand...
Click to collapse
https://drive.google.com/open?id=1WQ63zE0ZocJzGREoXeluNrfKy9A7F5aX
Thanks in advance
sorry about that, wrong one.
Jerwinn7 said:
Are you using the correct firmware required? Otherwise, it won't work.
BTW which ROM are you using?
Click to expand...
Click to collapse
I've formatted my MI6, I've also wiped it clean.
flashed MIUI FW 7.11.6
flashed AICP 13.0 2017.11.12
flashed (kernel) HastyOreo-6.0
wipe dalvik and cache
home button doesn't work!
flashed fix_FPC_Fingerprint
home button still doesn't work!

SM26 said:
https://drive.google.com/open?id=1WQ63zE0ZocJzGREoXeluNrfKy9A7F5aX
Thanks in advance
sorry about that, wrong one.
I've formatted my MI6, I've also wiped it clean.
flashed MIUI FW 7.11.6
flashed AICP 13.0 2017.11.12
flashed (kernel) HastyOreo-6.0
wipe dalvik and cache
home button doesn't work!
flashed fix_FPC_Fingerprint
home button still doesn't work!
Click to expand...
Click to collapse
fix_FPC_Fingerprint doesn't work it's for the older version of AICP. I did the following steps and got it working
1,format data and wipe everything
2,flash firmware
3,install rom,gapps
4,install magisk
5,use any root explorer app to edit /system/build.prop and add/change ro.boot.fingerprint to goodix
6,reboot
Home button and fingerprint worked after that

Jerwinn7 said:
fix_FPC_Fingerprint doesn't work it's for the older version of AICP. I did the following steps and got it working
1,format data and wipe everything
2,flash firmware
3,install rom,gapps
4,install magisk
5,use any root explorer app to edit /system/build.prop and add/change ro.boot.fingerprint to goodix
6,reboot
Home button and fingerprint worked after that
Click to expand...
Click to collapse
it worked!
I've done it a bit differently, but it works now!
huge thanks

Jerwinn7 said:
I've attached the files
Note that I'm using AOSPA Extended (unofficial oreo) with firmware 7.11.6
Click to expand...
Click to collapse
Thanks, I will try and report you back.

SM26 said:
it worked!
I've done it a bit differently, but it works now!
huge thanks
Click to expand...
Click to collapse
What was your flow? Glad that it worked for you. I will follow these steps also. I will give thanks tomorrow, cuz it is limited to 8 thanks per day for me. Thanks for the help @Jerwinn7. I will confirm asap. ?

Sithu Htun said:
What was your flow? Glad that it worked for you. I will follow these steps also. I will give thanks tomorrow, cuz it is limited to 8 thanks per day for me. Thanks for the help @Jerwinn7. I will confirm asap.
Click to expand...
Click to collapse
That's okay lol, you need not do that. Hope it works for you

Related

[Recovery][TWRP][P930 / SU640] TeamWin Recovery Project 2.6.0.0 [2013-07-30]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P930 and SU640 now officially supported by TWRP team. I will no longer be building recoveries for these devices. However I will keep this thread updated to the best of my ability.
Team Win Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
If you want more information about twrp please go to this page.
Phone look:
CHANGE LOG: http://www.teamw.in/project/twrp2
DOWNLOAD:
P930: http://www.teamw.in/project/twrp2/162
SU640: http://teamw.in/project/twrp2/167
Installation Methods:
1 - GooManager (Android App)
Code:
Download the GooManager app from either location:
[URL="https://market.android.com/details?id=com.s0up.goomanager"]Market Link[/URL]
[URL="http://goo.im/devs/s0updev/gooinsideme"]Direct Download[/URL]
Install the app and open it.
Tap menu then hit Install OpenRecoveryScript.
Tap Yes.
Verify that the filename displays your device's code name and hit Yes.
The file will download and your device will reboot and install the recovery automatically.
2 - ADB
Code:
adb push openrecovery-twrp-*.img /sdcard/
adb shell
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
3 - Terminal Emulator
Copy openrecovery-twrp-*.img to root of SD card then in your terminal emulator type the following:
Code:
su
dd if=/sdcard/openrecovery-twrp-*.img of=/dev/block/mmcblk0p13
BUGS:
If you have found a bug, please consider posting it here,possibly with a recovery.log. It's very hard to keep up with multiple threads for multiple devices. Please search the issues list first. Your issue may have already been reported.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
DISCLAIMER:
I take no responsibility for bricked devices, nuclear wars or such things.
CREDITS:
TeamWin for making the recovery.
CyanogenMOD team for the device tree.
Goo.im for file hosting.
Thanks to Dees_Troy and TweakerL from twrp IRC for their help and guidance.
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
maybe. like p930's cwm recovery?
范凯爱西西 said:
can 640 use it?thx for ur work
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.
OK I WILL TEST FLASH IT TOMORROW IN MY SU640.....THX FOR UR WORK....HOPE MORE WORK FOR P930.....Sorry for my bad English....谢谢。
nexwave-mat said:
TBH I don't know and have no way of testing but my guess is that it should work. However if you are going to test make sure to use all the precautions you can and that you have time to unbrick if needed. Plus this is still in beta stages and not fully functional.
Let me know if you try and it works. Good luck.
Click to expand...
Click to collapse
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.
drumist said:
Hmm, I suspect it won't work. There are separate CWM builds for SU640 and P930. I assume there is some reason for that.
Click to expand...
Click to collapse
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
Ok,i sent these in your mail:[email protected]!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...
范凯爱西西 said:
Ok,i sent these in your mail:........THX!!! If u complete,plz upload it.....i first use it...haha....thank u...sorry for my bad english...
Click to expand...
Click to collapse
I never got the email. Can you please edit your post to remove my email address? I don't want to spam bots to find me! Thanks.
nexwave-mat said:
Could you please link the CWM .img for the SU640? I checked CWM's site and was unable to find it. I would like to compare the two.
Click to expand...
Click to collapse
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.0-su640.img
(It's listed under LG Optimus LTE on their site.)
Delete post
slg1119 said:
I think
TWRP for P93X have bug
it have...
Unmount/mount Bug!
Thx to your job~
Sent from my LG-SU640 using XDA
Click to expand...
Click to collapse
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.
nexwave-mat said:
This should be fixed in beta4.
On another note I will work on an SU640 version as soon as my schedule frees up.
Click to expand...
Click to collapse
I don't think it is fixed.
I get a bunch of lines in the log saying:
E:Unable to mount /sdcard (Invalid argument)
Click to expand...
Click to collapse
I'm on Paranoid Android/CM10 Hybrid ROM
mattman86 said:
I don't think it is fixed.
I get a bunch of lines in the log saying:
I'm on Paranoid Android/CM10 Hybrid ROM
Click to expand...
Click to collapse
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first
nexwave-mat said:
Ya that is another minor bug in twrp itself but in no way a show stopper. Its caused by the fact that our device has 2 different ways of mounting SDcards. When the first fails you get the error message then it tries the second.
I've already reported this bug to the twrp team. They said version 2.3.0.0 should resolve this.
Beta4 should be fully usable however I kept it in beta stage in order to have it tested by a wider audience so please make a backup first
Click to expand...
Click to collapse
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.
mattman86 said:
It seems like it is a show stopper because I cant use it for it's intended purpose because it can't backup/restore because it doesn't have anything to backup/restore to/from.
Click to expand...
Click to collapse
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,
nexwave-mat said:
Go into the install menu first. That should force a mount. Then go right back out and do your backup.
Once you have done this could you provide your recovery log please?
Thanks,
Click to expand...
Click to collapse
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
-- Could not mount: /sdcard.
-- Aborting.
Click to expand...
Click to collapse
mattman86 said:
It tells me that the backup was successful and shows the log.
At the bottom of the log, it says:
Click to expand...
Click to collapse
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks
nexwave-mat said:
Can you supply your full log please? Run this command while in twrp to copy the log file to your PC.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
http://pastebin.com/LdGuWbUM
mattman86 said:
http://pastebin.com/LdGuWbUM
Click to expand...
Click to collapse
Very particular, could you please test with another sdcard or reformat the one you have on a PC and try again?
Thanks
Sent from my LG-P930 using xda app-developers app

[TOOL] DSWP v2.1 - disable system write protection - NOW LOLLIPOP COMPATIBLE!

Hi
I've finished fully automatic sytem protection disable tool for stock kernel.
Code:
It wouldn't be possible without xda users, xda community, especially:
flar2 - for original kernel module,
which was made for HTC One M8
Ladies & Gentlemen...
DSWP [disable system write protection] !
[What is this?]
Its automatic tool which will install kernel module,
which I ported to get work with Htc Desire Eye,
to get system fully writable, without any problems,
such as not-deleting bloatware - after reboot comes back,
reboots on modifying /system partition, etc etc.
Install process includes:
fw version check,
install kernel module to /system partiion,
make kernel module autobooting,
check if module is active after reboot.
..all this with just one click
[Requirements]:
- root,
- busybox
- adb,
- stock kernel,
For now 100% compatible are:
* LATEST LOLLIPOP 2.19.xxx.xx 5.0.2!
* EU 1.17.401.9!
* US AT&T 1.15.502.7!
* THREE 1.17.771.5
* 1.17.166.9
* and...?
just check if it works on other fw versions!
if it would not work with your ver - i can make it compatible
[Changelog]:
Code:
[20.04.2015] v2.1:
- changed tool name to be more unique/recognizable :D,
- added busybox installer,
- recompiled init.d apk - now its permanently turned on!
- now you can make wipe/factory reset and you will still have mod!
[18.04.2015] v2.0:
- added compatibility for newest LOLLIPOP firmwares,
using now other autorun method for inserting module,
because of install-recovery.sh not working in lollipop :)
[18.02.2015] v1.2:
- confirmed/added compatibility with 1.17.166.9
[20.01.2015] v1.1:
- confirmed/added compatiblity with THREE 1.17.771.5
[09.02.2014] v1.0:
- initial version.
[Screenshots:]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Download]:
Attached to this thread.
[Donate]:
Keep this project alive - don't forget to donate!
br
condi
current_version=2.1
Thank you this worked perfectly on my att desire eye
I just keep getting the... Waiting for device message.
Baldilocks said:
I just keep getting the... Waiting for device message.
Click to expand...
Click to collapse
do you have USB debugging on?
ccb101 said:
do you have USB debugging on?
Click to expand...
Click to collapse
Yes, USB debugging is on. Do I need to have the file unzipped in a certain directory on my computer? Right now I have it in my Android Fastboot folder.
Baldilocks said:
I just keep getting the... Waiting for device message.
Click to expand...
Click to collapse
Baldilocks said:
Yes, USB debugging is on. Do I need to have the file unzipped in a certain directory on my computer? Right now I have it in my Android Fastboot folder.
Click to expand...
Click to collapse
shouldnt need to i ran mine from the desktop and all the adb files required are packaged up in the zip...
ccb101 said:
shouldnt need to i ran mine from the desktop and all the adb files required are packaged up in the zip...
Click to expand...
Click to collapse
Yeah, even when I click on ADB shell on the app it says Device Not Found.
***EDIT****
Rebooted my computer. Worked that time.
---------- Post added at 07:08 PM ---------- Previous post was at 06:13 PM ----------
Actually it's not working. Maybe my firmware is too new??
This is the message I get.
1.17.401.9
[*] Pushing kernel module...
cannot stat 'files\1.15.502.5_wp_mod.ko': No such file or directory
[*] Mounting /system as RW, and injecting kernel module...
[*] Done!
[*] Reboot and check...
Baldilocks said:
Yeah, even when I click on ADB shell on the app it says Device Not Found.
***EDIT****
Rebooted my computer. Worked that time.
---------- Post added at 07:08 PM ---------- Previous post was at 06:13 PM ----------
Actually it's not working. Maybe my firmware is too new??
This is the message I get.
1.17.401.9
[*] Pushing kernel module...
cannot stat 'files\1.15.502.5_wp_mod.ko': No such file or directory
[*] Mounting /system as RW, and injecting kernel module...
[*] Done!
[*] Reboot and check...
Click to expand...
Click to collapse
Extract zip archive, all the files, to root of C:\ drive (C:\EyE [...]\),
and run .bat from this directory.
DO NOT run .bat file directly from archive.
Not Working
This is not working in build 1.17.707.9.
Shameera_N said:
This is not working in build 1.17.707.9.
Click to expand...
Click to collapse
No problem. Pull /system/lib/modules/texfat.ko file and attach it.
I will make it compatible with your firmware.
br
condi
condi said:
No problem. Pull /system/lib/modules/texfat.ko file and attach it.
I will make it compatible with your firmware.
br
condi
Click to expand...
Click to collapse
I have done that...Thank you
condi said:
No problem. Pull /system/lib/modules/texfat.ko file and attach it.
I will make it compatible with your firmware.
br
condi
Click to expand...
Click to collapse
I have flashed SkyDragon EYE ROM And Kernal
Thank you
@OP
It worked as expected, thank you very much.
Do you have a bitcoin address, I would like to pay you a beer
Tealc said:
@OP
It worked as expected, thank you very much.
Do you have a bitcoin address, I would like to pay you a beer
Click to expand...
Click to collapse
I'm glad it worked well Unfortunatelly I've never used bitcoin.
But thanks anyway!
br
condi
this is my file can you update your app because it doesn't work with my phone
thanks
Hi and thanks.
This is the file for firmware 1.17.166.9, if you can make it compatible with this version...
Thanks in advance
nothing men????
blackjackalmiaobo said:
nothing men????
Click to expand...
Click to collapse
recently i've been busy. post me fw version which is your file from.
br
condi
condi said:
recently i've been busy. post me fw version which is your file from.
br
condi
Click to expand...
Click to collapse
Cid htc_031 italy no brand
Software 1.17.401.9
Kernel 3.4.0
Htc sdk api: 6.25
Build: 1.17.401.9 cl402884 release-keys
I tried with your 1.1 tool but nothing
elric1427 said:
Hi and thanks.
This is the file for firmware 1.17.166.9, if you can make it compatible with this version...
Thanks in advance
Click to expand...
Click to collapse
Try v1.2.
blackjackalmiaobo said:
Cid htc_031 italy no brand
Software 1.17.401.9
Kernel 3.4.0
Htc sdk api: 6.25
Build: 1.17.401.9 cl402884 release-keys
I tried with your 1.1 tool but nothing
Click to expand...
Click to collapse
1.17.401.9 is supported since v1.0 version.
Check with adb:
Code:
lsmod | grep /system/lib/modules/wp_mod
ls -l /system/lib/modules/wp_mod
and post it here

How to Fix Sensors Not working issue

I think you also in the same problem that sensors of your phone was not working right? Also After flash color os maybe your sensors not working or not working correctly right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But don't worry. Here I am (Nishantha Indika) to fix this... Just easy to do... It got me hard to find how to fix. Finnaly here Everything for you...
What you need
Root Access
Terminal Emulater App
persistnew.img http://d-h.st/7VAu
Open terminal emulater app and type
su
dd if=/dev/block/mmcblk0p26 of=/sdcard/persist.img
Then you will get the img file on sd card. copy and take it on a safe place... Like on External SD card or On PC...
Now copy the downloaded "persistnew.img" file to sd card and on terminal emulater app type
dd if=/sdcard/persistnew.img of=/dev/block/mmcblk0p26
After complete Reboot... Now check the sensors using "Sensor Box" app. Your sensors are back...
But still Proximity is not working correctly. It always showing as 0 right? On calls you getting black screen right? So let's fix it
Flash MIUI... Or if you on MIUI then allright
On dialpad type "*#*#6484#*#*
Go to proximity option
Cover your proximity by hand
Press calibrate
Now remove your hand from proximity
You will see the value 5 or any
Now press on pass button. And you will see another test thing. Just go back and exit the app.
All done... Enjoy... Now if you need flash any other rom you like... :highfive:
Credited
Nishantha Indika
TheDynamiteGuy
cile381
DirectDMG
Gautam Chetia
I Dragon said:
I think you also in the same problem that sensors of your phone was not working right? Also After flash color os maybe your sensors not working or not working correctly right?
But don't worry. Here I am (Nishantha Indika) to fix this... Just easy to do... It got me hard to find how to fix. Finnaly here Everything for you...
What you need
Root Access
Terminal Emulater App
persistnew.img http://d-h.st/7VAu
Open terminal emulater app and type
su
dd if=/dev/block/mmcblk0p26 of=/sdcard/persist.img
Then you will get the img file on sd card. copy and take it on a safe place... Like on External SD card or On PC...
Now copy the downloaded "persistnew.img" file to sd card and on terminal emulater app type
dd if=/sdcard/persistnew.img of=/dev/block/mmcblk0p26
After complete Reboot... Now check the sensors using "Sensor Box" app. Your sensors are back...
But still Proximity is not working correctly. It always showing as 0 right? On calls you getting black screen right? So let's fix it
Flash MIUI... Or if you on MIUI then allright
On dialpad type "*#*#6484#*#*
Go to proximity option
Cover your proximity by hand
Press calibrate
Now remove your hand from proximity
You will see the value 5 or any
Now press on pass button. And you will see another test thing. Just go back and exit the app.
All done... Enjoy... Now if you need flash any other rom you like... :highfive:
Credited
Nishantha Indika
TheDynamiteGuy
cile381
DirectDMG
Gautam Chetia
Click to expand...
Click to collapse
hello whats exactly in this file? I have similar problem with redmi note 2 (accelereometer acting crazy Y is always zero) and nothing and noone seems to help.i even flashed fastboot rom (flash all)which i thought will reset tje phone toatally but nothingchanged:/ where should i look for the solution?
paniczklos said:
hello whats exactly in this file? I have similar problem with redmi note 2 (accelereometer acting crazy Y is always zero) and nothing and noone seems to help.i even flashed fastboot rom (flash all)which i thought will reset tje phone toatally but nothingchanged:/ where should i look for the solution?
Click to expand...
Click to collapse
What was your phone?
I Dragon said:
What was your phone?
Click to expand...
Click to collapse
xiaomi redmi note 2
paniczklos said:
xiaomi redmi note 2
Click to expand...
Click to collapse
Whoa, be careful man. Different device, different partition number
aldirudianto said:
Whoa, be careful man. Different device, different partition number
Click to expand...
Click to collapse
Ok so I guess, when I'll know the partition name I'll ask someone with working sensors on redmi note 2 to backup the partition and I'll restore it on my device.
most google searches say it's 'userdata' partition, is it rgiht ? (seems it's not right ;p )
now i see it's these two files :
/root/misc/sensors/sns.reg
/root/.bt_nv.bin
EDIT : there's no sns.reg file in my system ;/ any ideas ?
This method not working ,no values in the proximity sensor menu.
No luck dude,May be the hardware is dead.
I Dragon said:
I think you also in the same problem that sensors of your phone was not working right? Also After flash color os maybe your sensors not working or not working correctly right?
Click to expand...
Click to collapse
Hey I am facing same issue after flashing a custom kernel on Mi4 no other kernel is able to detect sensors on my device even stock miui kernel but only one custom kernel detects all my sensors? Please help me out.
@I Dragon can you bring such a fix for Mi4?
Prince Chandela said:
@I Dragon can you bring such a fix for Mi4?
Click to expand...
Click to collapse
Try to get that persist img from another working Mi4. Or go to Service Center and tell them...
I Dragon said:
Try to get that persist img from another working Mi4. Or go to Service Center and tell them...
Click to expand...
Click to collapse
Hey thanks i can get one but do you know what partition number it is for Mi4?
how do i backup that .img file from other mi4?
Edit i found out that partition.
Prince Chandela said:
Hey thanks i can get one but do you know what partition number it is for Mi4?
how do i backup that .img file from other mi4?
Edit i found out that partition.
Click to expand...
Click to collapse
Awesome. Then backup it and flash it in yours. Make sure to backup your partition too...
I Dragon said:
Awesome. Then backup it and flash it in yours. Make sure to backup your partition too...
Click to expand...
Click to collapse
Hey i backed up my partition it is only 22KB. Strange i flashed yours .img file nothing happen still sensors are not working now i will try to get this from a working Mi4
btw my issue is little different on one custom kernel my all sensors works without issue but on stock kernel or any other custom kernel none of my sensors works even on miui 7 stable
Prince Chandela said:
Hey i backed up my partition it is only 22KB. Strange i flashed yours .img file nothing happen still sensors are not working now i will try to get this from a working Mi4
btw my issue is little different on one custom kernel my all sensors works without issue but on stock kernel or any other custom kernel none of my sensors works even on miui 7 stable
Click to expand...
Click to collapse
Please do not flash my image in Mi4. Your device will get bricked...
I Dragon said:
Please do not flash my image in Mi4. Your device will get bricked...
Click to expand...
Click to collapse
I already did but nothing happened nevermind is there any app to backup partitions?

[TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware

For D802 Only
I have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 Support firmware 30a/30d.
It can be use in other firmware version of D802
Download Link:
LGG2-D802-OneClickRootRecoveryV1.1.zip
http://bit.ly/1Ij1soU
If you like my work, want to support development and have few coins spare .You can Press button DONATE TO ME
How to install
Backup Data on SDCARD Before doing everything
AFTER SCRIPT FINISHED IT WILL BE REBOOT TO RECOVERY AUTOMATICLY
1. Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
2. Plug G2 into computer
3. Run OneClick_ROOT_RECOVERY.bat
4. Enjoy ROOT+TWRP on Lollipop Firmware
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>ports.bat
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
Click to expand...
Click to collapse
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\cc\LG Root Script\LGG2-D80230a-OneClickRootRecovery>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
ขอบคุณครับ
For. any question that want to ask me in private Please Leave a question in facebook group
https://www.facebook.com/groups/1420724551528661/
......... DON'T INBOX TO ME .........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original Script
[Guide] Root LG firmwares (KitKat / Lollipop) - One click script by @avicohh
Ok
Tested on 32g Spain Vodafone 30d Rom and works like a charm, thanks
Led Zeppelin said:
Tested on 32g Spain Vodafone 30d Rom and works like a charm, thanks
Click to expand...
Click to collapse
I will be update my script for One Click ROO+TWRP.
That would be awesome
would be awesome!!
somboons said:
I will be update my script for One Click ROO+TWRP.
Click to expand...
Click to collapse
waiting just for that.. thanks :fingers-crossed::highfive::victory:
OMERZEN said:
waiting just for that.. thanks :fingers-crossed::highfive::victory:
Click to expand...
Click to collapse
Link online.
Feedback to me.
What khappens now to ur flashable rooted v30a and v30d
legola said:
What khappens now to ur flashable rooted v30a and v30d
Click to expand...
Click to collapse
Bump stock kernel is different .I want to people use compatible kernel.
somboons said:
Feedback to me.
Click to expand...
Click to collapse
This downgrade laf and aboot to v20?
4Freedom said:
This downgrade laf and aboot to v20?
Click to expand...
Click to collapse
this is a concept.
Great job man! Root & Recovery on Lollipop with LG G2 D802 is easy to do now!
somboons said:
this is a concept.
Click to expand...
Click to collapse
Okay, so now we have kitkat bootloader and kitkat "downlaod mode" on lollipop.
Between, about recovery, MUST we use only bumped version?
And every rom is compatible now?
4Freedom said:
Okay, so now we have kitkat bootloader and kitkat "downlaod mode" on lollipop.
Between, about recovery, MUST we use only bumped version?
And every rom is compatible now?
Click to expand...
Click to collapse
I answered you on all this points: http://forum.xda-developers.com/showpost.php?p=59882657&postcount=2
again: kk bootloader=> only bumped recovery/kernel
only rom with bumped kernel work on KK bootloader
6ril1 said:
only rom with bumped kernel work on KK bootloader
Click to expand...
Click to collapse
How can i understand if a rom has a bumped kernel?
Like official cm12?
And thanks for everything
i have a problem it say Couldn't open the port \\:\ COM3 after the phone enter in download mode
remio33 said:
i have a problem it say Couldn't open the port \\:\ COM3 after the phone enter in download mode
Click to expand...
Click to collapse
Screen shot please
I'm stuck at :
special command : ENTER , LEAVE
#
I did the root script once ,but wanted recovery ... maybe the other root script from avicohh is interfering ?
How to uninstall the supersu completely ,because it worked with the avicohh script, but i wanted recovery too so trying to install your script now ?
Kuoi said:
I'm stuck at :
special command : ENTER , LEAVE
#
I did the root script once ,but wanted recovery ... maybe the other root script from avicohh is interfering ?
How to uninstall the supersu completely ,because it worked with the avicohh script, but i wanted recovery too so trying to install your script now ?
Click to expand...
Click to collapse
Can you copy of log that show on command dos to me?
This script working very well for me.
somboons said:
Can you copy of log that show on command dos to me?
This script working very well for me.
Click to expand...
Click to collapse
Trying the avihocc script now ,but as expected ... same , stuck on #
I think the first install of supersu with avihocc script interfered with yours , so now i think i have to do the installation of the rom again to test if it was

Enable Soli for any contries through Magisk module

The last post i write a EdXposed module to enable Soli.
Now I'm write a Magisk module to enable Soli without restart zygote,and reboot the device will keep Soli to enabled.
Please go to github and download this module ,the url is https://github.com/demj1206170/EnableSoli
and feedback if there have any issues.
I download the file and flashed by Magsik i got failed " This zip in not a Magsik Module
I am new in root+Magsik game
Pixel4XL - Oct
DinarQ8 said:
I download the file and flashed by Magsik i got failed " This zip in not a Magsik Module
I am new in root+Magsik game
Pixel4XL - Oct
Click to expand...
Click to collapse
If the error states that it's not a Magisk zip, or invalid zip in TWRP, the zip is not packaged correctly. Open up the zip and you'll likely see a folder (probably named something like <nameofmodule>-master or similar, or something completely different). Take all the contents of that folder and repack it to the root of the zip and try flashing it again.
dengxm said:
If the error states that it's not a Magisk zip, or invalid zip in TWRP, the zip is not packaged correctly. Open up the zip and you'll likely see a folder (probably named something like <nameofmodule>-master or similar, or something completely different). Take all the contents of that folder and repack it to the root of the zip and try flashing it again.
Click to expand...
Click to collapse
Thank you so much work great [emoji1360]
Sent from my Pixel 4 XL using Tapatalk
DinarQ8 said:
I download the file and flashed by Magsik i got failed " This zip in not a Magsik Module
I am new in root+Magsik game
Pixel4XL - Oct
Click to expand...
Click to collapse
i download the release file and flush it, no issue occured. Did you download this file from release page?
fortunedemj said:
i download the release file and flush it, no issue occured. Did you download this file from release page?
Click to expand...
Click to collapse
Just now i see i downloaded wrong file something name clone file this file not flashing. After edit the file i see there a original file on the site flashing without any issues [emoji4]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Pixel 4 XL using Tapatalk
Works great! I had to repackage the zip contents into a new zip folder but after that, no problem with the Magisk flashing. Thanks for the effort
i try to enable by this models
but nothing
i had edxpose models and disabled it and try to insall the magisk models and after flashing and reboot didnt work
do i need to uinstall the xdpose app and models and riru core and riru edxpsosed
thanks
or maby i clone wrong the files
hello, i repackaged the zip file but it is still saying that it is not a magisk module. Is there a specific program for repackaging or am i missing something?
Not working for me.
It's installed with no problem, but when I reboot, the Motion Sense is still disabled.
By the way, the following command still works.
Code:
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
dotcink said:
Not working for me.
It's installed with no problem, but when I reboot, the Motion Sense is still disabled.
By the way, the following command still works.
Code:
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
Click to expand...
Click to collapse
U can do this with magisk Hide props conf.
U should install this module, then install terminal, type :
Su
Props
Add new props (u should choose it from the list)
Add only this: pixel.oslo.allowed_override true
Reboot / profit
lapapunk said:
U can do this with magisk Hide props conf.
U should install this module, than install terminal, type :
Su
Props
Add new props (u should choose it from the list)
Add only this: pixel.oslo.allowed_override true
Reboot / profit
Click to expand...
Click to collapse
It works, thank you!:good:
lapapunk said:
U can do this with magisk Hide props conf.
U should install this module, then install terminal, type :
Su
Props
Add new props (u should choose it from the list)
Add only this: pixel.oslo.allowed_override true
Reboot / profit
Click to expand...
Click to collapse
This works perfectly fine and it's clean cut. Thanks.
ozikat12 said:
This works perfectly fine and it's clean cut. Thanks.
Click to expand...
Click to collapse
what magisk module should we use ??
nexusTHIRTEEN said:
what magisk module should we use ??
Click to expand...
Click to collapse
I've screen shot the required modules. Install Terminal apps and run the set prop command mentioned above thread.
ozikat12 said:
I've screen shot the required modules. Install Terminal apps and run the set prop command mentioned above thread.
Click to expand...
Click to collapse
EdXposed always bootloops my device !
nexusTHIRTEEN said:
EdXposed always bootloops my device !
Click to expand...
Click to collapse
Install only props and busybox modules! Its all that u need for soli
lapapunk said:
Install only props and busybox modules! Its all that u need for soli
Click to expand...
Click to collapse
Hi, I installed busybox and magiskhide props config but after that can you please provide a step by step description of what's next? I want to know where I went wrong. Thanks.
DinarQ8 said:
Thank you so much work great [emoji1360]
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Hi, I also got failed " This zip in not a Magsik Module." Can you explain how exactly you bypassed this?
onlyguynamedniles said:
Hi, I also got failed " This zip in not a Magsik Module." Can you explain how exactly you bypassed this?
Click to expand...
Click to collapse
This the correct file. But not work with Security Feb
Install v 1.1 from Edxposed
Sent from my Pixel 4 XL using Tapatalk
View attachment 4942519

Categories

Resources