Related
Well this question is for anyone who has some idea with the kitchen android and I'm cursing a few weeks ago to do a damn deodex ... The thing is, I have an S5 (SM-G900H) the problem that I have is I can not start because I deodex rom throws: 0 Status did I?
* Deodexe with Dsixda
* I modified the updater-script
* Took another rom deodex the updater-script and updater-binary
* I tried other cuisines (archi, ricky)
* I tried updater-script and update-binary I made in Linux (the latter gives me brick)
* Install cwm Philz, classic and TWRP
All attempts with the same result (Status 0). I tried to install a virtual machine (plus it is very slow gives me more errors).
I do everything with Windows with cygwin. I honestly do not know what to do, I'm running out of ideas and ability to install Linux does not help. I read that the problem is binary, but WHAT is the problem?
In any case as it should do to "activate" the support for my team in the kitchen. What should I add? I saw that I stand up for Note, but not for my model.
The updater-script to use Linux then were apparently also generates the "error".
From already thank you very much for reading and receive any suggestions.
My updater-script
Sorry my bad English.
..
fffft said:
You didn't provide enough information to really narrow much down e.g. a detailed, step by step description of what you did, a search to see if you missed any odexed files, directory listings with permission flags shown, system log, etc.
More than likely you missed some odex files, perhaps in preload. Or possibly messed up some critical system files. That might mean corruption, but permissions are a common error.
The first thing to try is wiping your system cache from recovery mode. If the problem persists, then restore your backup or flash a full, stock ROM to recover. Then you can try again or you may prefer to avail yourself to the 900H ROMs that are already deodexed.
.
Click to expand...
Click to collapse
did not understand anything I wrote above. : P
..
fffft said:
That might have a lot to do with the confusing way in which your wrote your post. I've replied to a thousand or so others to help them and had no trouble understanding their intent.
If you felt misunderstood, the logical thing to do would have been to elaborate further. Which you didn't do.
Good luck with your issues.
.
Click to expand...
Click to collapse
My problem it's fixed. Thanks anyway...
Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.
Excellent work friend @ondrejvaroscak. Congrats! Awesome
Was waiting a long time for this! Thanks man! working perfectly.
Working perfectly on D6603, thanks
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Thanks Bro , Very Nice !!
Perfect Work !!
Z1, C6903
Thank you for this great solution, works on Z1.
NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app
norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..
Working on fully setup 5.02 on Z2 thanks.
ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).
Ok fine... for verify all you said:
{
"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"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?
hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Great thanks
ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line
hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?
Hello boys & girls!
I want to port the Kali Nethunter rom to the OnePlus 5.
Because it is my first time i need some people who can port it together with me.
Offensive Security has a nice tutorial on their website but its getting complicated when i come to the modify kernel part.
I really need some help with that.
More info:
offensive-security.com/kali-linux-nethunter-download
Porting info:
github.com/offensive-security/kali-nethunter/wiki/Porting-Nethunter
Sorry due the spam restrictions i cant post the links.
If you got some tips or advice on how to do it let me know! :good:
Greetings,
Stefjoe
Let me see...
EDIT: Ok. I can't help sorry
_MartyMan_ said:
Let me see...
EDIT: Ok. I can't help sorry
Click to expand...
Click to collapse
Damn.... too bad
Any luck with this? Having a hard time myself.
I've looked at it myself and it seems complicated to me because I've never done that before but maybe anyone here is able to do it...
stefjoe said:
Damn.... too bad
Click to expand...
Click to collapse
Any progress?
The only problem to port nethunter to the OP5 is to add HID and CDROM support to the kernel but in order to do so, those patches have to be ported to kernel version 4.4+ ...
Otherwise packet injection over usb works fine on OOS.
I'm trying to compile a kernel with packet injection for RR.
Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.
Arka1n said:
The only problem to port nethunter to the OP5 is to add HID and CDROM support to the kernel but in order to do so, those patches have to be ported to kernel version 4.4+ ...
Otherwise packet injection over usb works fine on OOS.
I'm trying to compile a kernel with packet injection for RR.
Click to expand...
Click to collapse
I think you can find the patch for HID and CDROM support here:
https://forum.xda-developers.com/showthread.php?t=2196707
https://github.com/CyanogenMod/andr...mmit/46bd47757a9f34c1d95dd2620414893212fb0526
FYI I don't know anything about patching kernels so i might be wrong
Well this leads to the hid patch :
github.com/pelya/android-keyboard-gadget/blob/master/kernel-3.4.patch
And this to something about the CDROM patch for the OP3 :
github.com/binkybear/androiddevs_kernel_oneplus_msm8996/commit/fc6f4b6b5f70509fbc5d583e8315f88119acb3c2
Not yet allowed to post links...
Anyway i need some help from other devs to port those to 4.4 :silly:...
Arka1n,
Hey,
I saw the post regarding putting nethuntr on the 1+ 5.
Are you willing to give me the needed kernel too plz?
Thanks
Jazzzzz
Arka1n said:
Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.
Click to expand...
Click to collapse
Most definitely would like it! Message me
Arka1n said:
Tell me if you want the kernel ... I've modded Adin's kernel (OOS) and Lightning kernel (LOS).
You will then have to install the nethunter chroot zip and you're good to go.
Click to expand...
Click to collapse
I definitely would like it too !!!
Crappy upload rate so it may take some time...
[WOOT]
Here : https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810 :victory:
OnePlus5
I just got mine and want to do the same. I currently have nethunter on the original oneplus one and it works great. I am hoping it's the same process. Has anyone done it on any of the oneplus phones before? I ask because it took me at least 3 weeks every day after work playing with it. I bricked it maybe 3 times and OnePlus team remotely fixed it and finally I got it working. It wasn't easy.
If somebody has, please share your experience. I will try to pull up all of the links I used and videos I watched before I finally got nethunter to boot.
I want to do this to the oneplus 5 so I can use it for nethunter then wipe the onplus one and use it as my phone. Any help/advice is greatly appreciated. I will come back and post the info I used for the oneplus one and anything I find for the oneplus 5.
cheers
Nethunter for OnePlus 5
I found a way to "port" but not the entire kernel.
I managed to create chroot and can run Kali shell after one failed trail.
IMPORTANT : I went into bootloop(only boots into twrp) once while trying to remount /system as rw. But then I figured out SElinux must be disabled. You know what to do if you went into a bootloop, but just take a backup (nandroid backup didn't work for me)
And I also lost all of my data after I flashed stock recovery.
Everything seems to be working fine. But there is a problem with the Nethunter 3.0.
The
Code:
apt-get
does not work.
However, I pinged google.com and I get replies.
So, we need to install metapackages manually. At least for now.
What I did :
1. Download OnePlus One nethunter 3.0 ROM
2. Locate the apks (<nethunter_extracted>/data/app)
3. Install in this order :
• Nhterminal
• VNC
• Nethunter app
4. Open the Nethunter app and install the chroot
( I selected full chroot, however, you may choose minimal chroot too instead )
5. From any root explorer, we need to copy the files that are under /data/data/com.offsec.nethunter/files/scripts/*
to
/system/bin
(If you don't find the .../files/scripts, open Nethunter app and try again)
6. After copying the files to /system/bin,
There are three important files :
•bootkali
•bootkali_bash
•bootkali_login
We need to symlink these ↑
Important : we need to make the system writable first.
Run from AndroidSU shell:
Code:
#setenforce 0
Code:
#mount -o rw,remount /system
Then, linking :
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali /system/bin/bootkali
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali_bash /system/bin/bootkali_bash
Code:
ln -s /data/data/com.offsec.nethunter/files/scripts/bootkali_login /system/bin/bootkali_login
You can remount /system to read-only if you wish to.
7. Next, install BusyBox to /system/bin
Usually, it is installed to /su/xbin.
But we need to install to /system/bin too.
This step is necessary.
8. Now, the Kali shell works fine.
Try running
Code:
#bootkali
in AndroidSU shell and you should be in the Kali shell
You can also open Nhterminal app and select Kali.
9. You may install the other apks now.
Enjoy ~ !!
Unable to start monitor mode error showing pls rply
Whats the problem
---------- Post added at 02:39 AM ---------- Previous post was at 02:16 AM ----------
I m using oneplus 5 naughat 7.1 rom and kali nethunter installed.
But problem in monitor mode
Error:Newly created monitor mode interface wlan0mon is *NOT* in monitor mode.
Removing non-monitor wlan0mon interface...
WARNING: unable to start monitor mode, please run "airmon-ng check kill"
I m trying this command 'airmon-ng check kill' but same problem
ADD FACE UNLOCK TO ANY ANDROID
NOTE:- I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE
So finally i have discovered a way to add face unlock to any android by using the Google Smart Lock feature...
This feature is available in most of the android devices:good:...
There are two methods of doing THIS 1. Using ROOT2. Without root(using adb)
LETS START
1. USING ROOT
-download gapps compatible with your android(gapps must be nano or above)
-install ''RAR'' to your phone
-extract gapps.zip to your phone[make a separate folder(optional)]
-open the extracted files and open GApps folder
-here you will find 4 files (1.facedetect-lib-arm.tar.lz, 2.faceunlock-all.tar.lz, 3.faceunlock-common.tar.lz, 4.faceunlock-lib-arm.tar.lz)
-open facedetect-lib-armcommonlib and copy libfilterpack_facedetect.so to systemlib and set the permissions
-similarlly copy all the files and if required create new folder with the permissions and paste the files from all the 4 files
-EX:- copy Face Lock folder to system/app and set permissions
-reboot your device
-open settings>security>smart lock... here you will find Trusted Face option
-ADD YOUR FACE ND ENJOY....!!!
NOTE:- Permissions details will be in second post...
2. Without root(using adb)
I will be updating the fourm later with full adb method details...
BUT, if you want to give it a try... then learn some adb commands for pushing files to system folder and setting up the commands...
Your would have to one by push the files and the folders and set the specific permissions...
***In the screenshot section, the first screenshot is of setting permissions for file and the second one is for setting permissions for folder***
NOTE:- I used es file explorer for doing this modification.
NOTE:- I tried this on a700fd on stock touchwiz android 6 rom... and it worked perfectly:laugh:
***If this helped you, please Press THANKS***
***For any query, REPLY***
XDA:DevDB Information
FACE UNLOCK, Tool/Utility for all devices (see above for details)
Contributors
smart123123
Version Information
Status: Testing
Created 2018-10-23
Last Updated 2018-10-23
Reserved
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
D2U2 said:
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
Click to expand...
Click to collapse
Yes but i would recommend you to use the root method bcz in adb method you have to side load everything and then give specific permissions...
adb method
smart123123 said:
Yes but i would recommend you to use the root method bcz in adb method you have to side load everything and then give specific permissions...
Click to expand...
Click to collapse
please i need adb method too can anyone help?
I have tried root method and is not working for me. I'm on Havoc OS Android AOSP 9.0 on a Xiaomi Mi Max 2 device.
Your guide isn't clear at all but I think that I made all the steps. When I reboot the phone, folder with files added in system/app are missing and of course the face unlock option at Smart Lock menu is not present. Seems that Android erase the files by itself, don't know why.
Thanks anyway.
Inotalas said:
I have tried root method and is not working for me. I'm on Havoc OS Android AOSP 9.0 on a Xiaomi Mi Max 2 device.
Your guide isn't clear at all but I think that I made all the steps. When I reboot the phone, folder with files added in system/app are missing and of course the face unlock option at Smart Lock menu is not present. Seems that Android erase the files by itself, don't know why.
Thanks anyway.
Click to expand...
Click to collapse
Have u rooted ur phn with magisk??
smart123123 said:
Have u rooted ur phn with magisk??
Click to expand...
Click to collapse
hey
It sounded risky when I read it but, I gave it a try using the root method. It works for me.
Thanks for these fantastic tricks.
OFRA562 said:
hey
Click to expand...
Click to collapse
Yes... Post any type is difficulty you aaya facing... I'll surely reply...
How can we get assistance spotlight for dark environment......
Will this work in android 10
there are no such files in the gapps for android 10
This should be at least be half a fix for android 10 faceunlock
MaximusPrime said:
there are no such files in the gapps for android 10
Click to expand...
Click to collapse
maybe this is a newb response but if the files aren't in android 10 it shouldn't matter since this mod is putting the files there. So the files will be there. Maybe the dev that started this thread or someone with more experience can chime in here because thats exactly why im here. They removed the faceunlock framework from opengapps and i figure if they can remove it then it can be added back. I kinda feel like something will still be missing if you do this mod alone on android 10 though. I would like to know what exactly they removed from opengapps and then compare that with the files in this mod and maybe the 2 combined should get it working. Thats the line of thinking that im on. Sometimes it's that simple. I mean look at how many features can be turned on with flags and simple build.prop edits. I'm just not sure exactly how the face detect and faceunlock was removed and i need that little piece of information to grasp the scope of the problem a little better. Anybody Tried this on lineage 17 or any other android 10/q rom yet?:silly:
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
esparkinfo said:
It sounded risky when I read it but, I gave it a try using the root method. It works for me.
Thanks for these fantastic tricks.
Click to expand...
Click to collapse
What Rom/Device/and android version did you use??? Give us a little more info so more of us can try with less risk and a little more confidence.
Thanks
can i install it on Android 6.0？
Anything for Android 10?
Is it working in CUSTOM ROM AOSP 7.2
ON ONE PLUS 2?
CAN YOU PLEASE DESCRIBE WHAT TO EXACTLY DO?
Did you get anything?????
D2U2 said:
Hi, i need install trusted face using adb method in my j701m with android 8.1.0.. you can help me? Thanks
Click to expand...
Click to collapse
I don't want to root my device but I need face unlock in my Mi A2 device.
pixel experience （android Q） has this face lock feature, so I guess maybe we could extract from it
Welp, OpenGapps does not include the face unlock anymore so RIP :/
i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7
nadjibbb said:
i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7
Click to expand...
Click to collapse
Hey, it's all ok dude..
I bet you didn't make a nandroid backup, if yes just restore it !
Not made a backup and rooted with superSU ?
Here on XDA find and try to use 'unSU.zip' file or simply click here. Flash it in recovery,
then if will work re-root the device with your favorite superuser app.
Hope your device will be newly usable.
Let the community know if all gone well...
P.S.: PM are ok but a post can be read by everyone, well done !
P.S.2: THX to @osm0sis for unSU script.
Cheers
Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >
nadjibbb said:
Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >
Click to expand...
Click to collapse
I believe / sh is recoverable only with a backup made previously.
Now you probably need to re-install, even to prevent other possible problems, the entire system.
Save all your files you want to keep and
keep your bootloader unlock code handy (maybe you don't need it).
I can suggest which files to use...
You can still expect some tips from more experienced users ..
You decide.
Cheers