Database Users

[me176c/x] [K013] Collection of ROMs and Updates

[me176c/x] [K013] How to Root and update from .182 to Lollipop release
Stock ROMs up to v.182, all languages
ASUS' Download Center for the MeMo Pad 7 Link is now inaccessible as ASUS has redesigned their site. Even the support page for this tablet no longer has any links to download ROMs/updates. Sad panda. However, the ones below (ASUS' direct links included) still work! I am also in the process of reuploading/rehosting all of these as well, so stay tuned! So far everything is rehosted on Google Drive, and I plan to add more mirrors in the next couple of days. Pleasse bear with my snarkiness, I have been up late and it's now 4am. I must crash now.
Anyway........ Enjoy!!
WW 182 Full ROM
ASUS
Google Drive
WW OTA 191
ASUS
Google Drive
Google Drive (alt)
WW OTA 198
Google Drive
WW OTA 199
Mediafire
Google Drive
WW OTA 201
Google Drive
Zippyshare (ew)
WW Lollipop release
Mediafire
Google Drive
If you have other links to share, especially direct links from ASUS or non-GDrive hosts, please feel free to post them and I will credit you!
(Manually) Flashing Updates
Sometimes (read: often) an update will fail to install and reboot, and then the tablet will claim you're up to date when you check for updates (and we know it's full of crap). So you'll have to manually update yourself, and often, if only works if you start from .182 (or above), and flash each file in consecutive order. So here's how it works. Be sure to read over this before starting, to get an idea of what's in store for you. And to be safe, read it again. And to be doubly-sure, read it AGAIN (I cannot stress this enough).
Obligatory warnings:
Your warranty (expired by now, for sure) is now null and void. Regardless of whether you do this, it's no longer valid either way! :laugh:
I am not liable for any damages to your device (or your brain) that this process may cause. What you do to your device is on you, but if you play it safe and read this all carefully (and read it again! And AGAIN!), you shouldn't have any trouble.
Instructions:
First things first, install your drivers if you haven't already, and set up the Android Platform Tools (adb and fastboot exes and such, also attached to this OP). I highly suggest trying the Latest ADB Fastboot and USB Driver installer tool for Windows by @fawazahmed0 (or the various attached drivers below, if you still somehow have trouble with getting your PC to recognize this dinosaur of a device).
Next, before we continue, make sure USB debugging is enabled on your tablet. Go to Settings > About tablet, and tap on Build Number 7 times, and you'll see a toast, "You are now a developer!" Back out once and scroll down a bit, you'll now see Developer Options. Enter, and near the top you'll see an option for USB debugging, so check that box. Plug in your tablet to the PC, then open a command line interface (Hit Windows Key + R, then type in "cmd" and press enter). Type in "adb devices" (without quotes) and look at your tablet's screen for a prompt. Check the box and tap OK. Now. back in the command prompt, press up and enter on your keyboard (which will repeat that last command), and you'll see your tablet's serial number (a string of letters/numbers) and the word "device" if you did it correctly. Now you're ready for the next part.
1. Install the "RootZenFone-1.4.6.8r.apk" (attached to this OP, below) and run it. Beware, it may have some Chinese text/Engrish. It's fairly simple to figure out though, thankfully.
2. Turn on USB debugging if you haven't already (didn't you read this first? You're already slacking!).
3. Download the zip file(s) you need and rename it update.zip and transfer it to your tablet. Or copy all files to the tablet and rename them (with a file manager of your choice, see next step) as you go.
4. Download a file manager that has root access (such as MiXplorer or Root Browser).
5. Go to / (root) and manually copy your update.zip to the /data folder.
6. Download this command file (also attached below, in a zip) and copy it to the /cache/recovery folder. This must be present each time you install an update via this method, so leave a copy on your device.
7. Back to Windows Command Prompt, run the command, "adb shell" (without quotes, as before), wait a moment for it to reload the server, then type, "su" (again, without quotes). When you type in the "su" command for the first time, it will prompt for SuperSU access on your tablet, similar to how it requested the RSA perms with adb debugging. You must allow this root permission, or the following won't work!Now, type line by line (or better yet, copy and paste into the command prompt (a right click automatically pastes copied text into it, btw):
Code:
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
In brief, what this means is that you just ordered the "command" file to boot as a "recovery" in order to flash the update package you copied and renamed previously. Thus, the tablet will reboot and commence flashing. At least, I think that's what's happening here. Sorry, I'm no rocket surgeon. All I know, is that it works. However, if you are getting an error during the update process, as mentioned above, you will likely have to flash the next incremental update (the one just above your current version) instead and go from there, flashing each OTA in order using the coded commands above every time. Be sure to rename EACH ZIP to "update.zip" as you do this or the command cannot find the file! Yes, this sounds like a pain, and it is! But this has worked when the direct approach had failed.
Archive folder of everything needed, on Google Drive
ROOT ZenFone FAQ has a translated guide on how to fix ptotential issues with the root process.
Credits:
@plopingo and @jerbear294 for some of the links.
@lethardicus for finding most of the OTA zips again when one weirdly went missing @fawazahmed0 for the driver installer tool
@slayeralive for providing the basis for these instructions

Nice work sub

No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery

@GuyInDogSuit
Update
mirrored OTA 191, 198, 199, 201 & RootZenFone-1.4.6.8r apk => https://drive.google.com/folderview?id=0B5G23fyE72tnLS0yaXlUamVmcXc&usp=sharing#list

@GuyInDogSuit @slayeralive
I've try to update manually but it failed
how to flash .182 if I'm already in .191 ?

slayeralive said:
No need for adb just copy zip ti /data and command file to /cache/recovery and reboot to recovery
Click to expand...
Click to collapse
You don't have to do all the typing anymore?

GuyInDogSuit said:
You don't have to do all the typing anymore?
Click to expand...
Click to collapse
I've try, the tablet show android logo with no command on the screen after reboot without entering command

you did something wrong. command file is just txt file , and echo command in terminal is used for writing text in txt files.try to copy command file and reboot to recovery from terminal emulator with reboot recovery command. I created this method mainly for unbricking read post
http://forum.xda-developers.com/memo-pad-7/general/unbrick-asus-memopad-7-me176c-cx-t2970049

GuyInDogSuit said:
Thanks to @plopingo and @jerbear294 for some of the links.
Click to expand...
Click to collapse
OMG, I can't believe I JUST found this thread.
I have two of these tablets that I use as wall-mounted controllers for HA. One of them accepted the OTA updates and I was able to get it to .201 and keep it rooted. The other one, no matter what I tried, would not pull down anything above the .182 it was running.
This post has EVERYTHING you need to go from whatever all the way to .201 quickly and very easily. I installed 15 Second ADB, the ASUS ADB drivers, and ran through all of the updates. This, my friends, is awesomesauce.
HUGE THANK YOU to @GuyInDogSuit, @plopingo, and @jerbear294!

No luck
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast

peldo123 said:
im on .182. When I move the files to the directories and reboot to recovery it fails. i get an error. Could this be becuase i had modified the build prop with xblast
Click to expand...
Click to collapse
It could. I have made that last year and end up with a bricked tablet...
I had to make a complete reset.
I made a few tries until I get it right and found out that using certain terminal apps don't allow spaces between commands whilst others do... Try commands without breaks if you're using a terminal app. Or try temp cwm to update all the updates at once.

Can't get it to work
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!

kdlannoy said:
Every time i try this procedure this happens:
The tablet restarts after executing the adb shell step.
The tablet starts to update the firmware, but then suddenly throws an error. This happens with both the rom and the update files.
Anyone has any idea how to fix this?
Thx in advance!
Click to expand...
Click to collapse
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!

This fixed it! That was a stupid mistake

kdlannoy said:
This fixed it! That was a stupid mistake
Click to expand...
Click to collapse
I'm glad it worked. I once made the same mistake.

I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?

mrseverin said:
I an on 191
there is no /cache/recovery folder
ls /cache
aplogs
backup
lost+found
modemcrash
Should i create /cache/recovery ?
Click to expand...
Click to collapse
Should be safe. I had a recovery folder, but nonetheless I don't see why it would harm anything.

I've had several Android devices. That was the easiest root I've ever done.

bravesoul said:
Did you unzipped the file? You see, there's a zip inside another zip. Unzip the 1st time into root/data folder and rename it to update.zip!
Click to expand...
Click to collapse
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.

regele said:
Could you give me a little more detail? I can't seem to make it work. Also, I don't have a "data" folder in /root? Can I create one? Thanks. Nevermind, I got it to work.
Click to expand...
Click to collapse
"/root" isn't a folder. It's the source. For example. When you copy something to a hard drive you are copying to the root of that hard drive. The same goes with the root of the android. So. Copy the unzipped .zip file to root and to inside data folder. Rename it into update.zip and run the commands.
I realise you got it to work, but since this is a community I have explained to others.

[Utility] Android boot Manager APK

Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.

I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.

atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?

lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.

New version won't install on Kit Kat

PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.

atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt

Are extracted files accessible in file system? I can't find them

levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM

PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.

atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?

levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...

It seems that the image you want to unpack it is not an android image.

atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk

Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

MM 6.0.1 [TWRP] Recovery

GOT TROUBLE WHILE INSTALLING A RECOVERY? GET A WORKING TWRP RECOVERY AFTER 2 MINUTES ON YOUR XPERIA Z2 D6503/D6502:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
YOU HAVEN`T INSTALL ANDROID MARSHMALLOW YET BECAUSE YOU WANT TO KEEP ROOT RIGHT, XPOSED AND THE RECOVERY?
THEN CHECK OUT THIS THREAT
http://forum.xda-developers.com/xpe...03-23-5-0-570-prerooted-t3364817#post66513485
Another simple Method: thanks @meer_mortal
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Click to expand...
Click to collapse
BUGS: none
IMPROVABLE: boot into recovery only works manually (when it vibrates and a green LED shows up press VOL DOWN till the LED is purple) "QUICK BOOT" and similiar Applications cannot boot into the recovery!

Which files are inside .exe?

Can i get Decryption key? to download

wheal said:
Which files are inside .exe?
Click to expand...
Click to collapse
Only adb and fastboot files! You can also download them from "chip.de" it's called "Minimum adb and fastboot"
Sent from my D6503 using XDA-Developers mobile app

Natur said:
Can i get Decryption key? to download
Click to expand...
Click to collapse
I am sorry that i gave you the wrong link just a minute
Sent from my D6503 using XDA-Developers mobile app

Natur said:
Can i get Decryption key? to download
Click to expand...
Click to collapse
Now the right link is in the decsription...

freaky2xd said:
Now the right link is in the decsription...
Click to expand...
Click to collapse
Thanks,

is this method works if i use Android 5.x or 4.x ?

reknew said:
is this method works if i use Android 5.x or 4.x ?
Click to expand...
Click to collapse
you can try. but if I were you, i`d better use [NUT`s] DualRecovery! its simple and i have already used it for 4.4.4 and 5.1 on the Z2!
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
just look for the Z2 file... its a zip file! its installer and flashable zip!

thanks man.
this worked for me. I somehow lost recovery but regained it on Android M after following your steps!

pseudoheld said:
thanks man.
this worked for me. I somehow lost recovery but regained it on Android M after following your steps!
Click to expand...
Click to collapse
you are welcome the same happs why i created this threadened to me, that´s why I started this recovery fix thread

Hands health
İts works, good job thanks

Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat

balabanos said:
İts works, good job thanks
Click to expand...
Click to collapse
thanks

meer_mortal said:
Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat
Click to expand...
Click to collapse
try it.

meer_mortal said:
Thanks for this. You can also use root explorer to make the phones file system writable before running install.bat
Click to expand...
Click to collapse
This is a Statement not a question
freaky2xd said:
try it.
Click to expand...
Click to collapse
I did. That's how I got TWRP on MM
Following your guide
I downloaded the files from OP post
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Win!

meer_mortal said:
This is a Statement not a question
I did. That's how I got TWRP on MM
Following your guide
I downloaded the files from OP post
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Win!
Click to expand...
Click to collapse
oh yeah you`re right of course i thought it might be a question xD
I added your post as a quote to the description

You Want TWRP v3.0.0.2 ?
Then flash @pec0ra customKernel v8.1!
It unlocks:
Based on Sony 23.5.A.0.570 kernel sources
Compiled with linaro GCC 4.9.1 toolchain, -O3
Governors : interactive, ondemand, performance, conservative, smartassV2, intellidemand2 and intelliactive.
Fast hotplug
CPU overclock up to 2.8 GHz Thank's to Faux123 and DooMLoRD
Changed GPU frequency table to 27 - 657 MHz Thank's to Myself5
Sony RIC disabled
Undervolt
TWRP recovery included, fota partition support
Breathing notification light thank's to glocklee
Force Fast Charge
KCAL Advanced color control Thank's to savoca
Click to expand...
Click to collapse
Visit this Link:
http://forum.xda-developers.com/xperia-z2/orig-development/kernel-abricot-kernel-v3-t2965480

guys, after i open install.bat and phone rebooted. My phone didn't open. it is in bootloop now and after opening, phone try to open twrp but it can't so the phone reboot itselft over and over again.. i did hard reset. and open the phone again, same things happened. Help me please..!

Abdülcelil said:
guys, after i open install.bat and phone rebooted. My phone didn't open. it is in bootloop now and after opening, phone try to open twrp but it can't so the phone reboot itselft over and over again.. i did hard reset. and open the phone again, same things happened. Help me please..!
Click to expand...
Click to collapse
reinstall the firmware via flashtool. choose everything to wipe

[MOD]Add Face Unlock to any ANDROID

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 :/

Unable to get apps list while using app systemizer

I am using PE+ 11 on Moto G6, when I run command "su" and then "systemize" it does not list any apps. Can someone help?
I am using module "App Systemizer v17.3.1 by veez221" and "Busybox 1.31.1".

24INVINCIBLE24 said:
I am using PE+ 11 on Moto G6, when I run command "su" and then "systemize" it does not list any apps. Can someone help?
I am using module "App Systemizer v17.3.1 by veez221" and "Busybox 1.31.1".
Click to expand...
Click to collapse
I know your issue has already been solved. But what's the advantage of changing a user app to a system app? The next update installs the APK to /data again, which is the same as an user installed app...

An alternative is to use lucky patcher

Did
24INVINCIBLE24 said:
I am using PE+ 11 on Moto G6, when I run command "su" and then "systemize" it does not list any apps. Can someone help?
I am using module "App Systemizer v17.3.1 by veez221" and "Busybox 1.31.1".
Click to expand...
Click to collapse
Did you find a solution yet? I'm having the same issue on a Samsung S20 running Android 12 - same configuration as yours otherwise.

nacos said:
Did
Did you find a solution yet? I'm having the same issue on a Samsung S20 running Android 12 - same configuration as yours otherwise.
Click to expand...
Click to collapse
We need logs to find an error. It's explained in the thread for app systemizer:
veez21 said:
** Uploading logs
Go to the menu and type `logs`, this will upload the log files of this module and will generate a link.
Click to expand...
Click to collapse

Hi
WoKoschekk said:
We need logs to find an error. It's explained in the thread for app systemizer:
Click to expand...
Click to collapse
Hi, Thanks for the reply. I followed your directions and a file called "bash_history" seemed to have been created under /data/data/com.termux.com/home. Would you like me to post this file here?
Thanks!

nacos said:
Hi
Hi, Thanks for the reply. I followed your directions and a file called "bash_history" seemed to have been created under /data/data/com.termux.com/home. Would you like me to post this file here?
Thanks!
Click to expand...
Click to collapse
yes

Hi
WoKoschekk said:
We need logs to find an error. It's explained in the thread for app systemizer:
Click to expand...
Click to collapse
Hi, Thanks for the reply. I followed your directions and a file called "bash_history" seemed to have been created under /data/data/com.termux.com/home. Would you like me to post this file here?
Thanks!
WoKoschekk said:
yes
Click to expand...
Click to collapse

I had to archive (zip) the file to attach it here. Thanks!

nacos said:
I had to archive (zip) the file to attach it here. Thanks!
Click to expand...
Click to collapse
the file is only 8 bytes in size... not very helpful.
Above I've linked the instructions on how to create logs. Please follow it and post the links you'll create.

WoKoschekk said:
the file is only 8 bytes in size... not very helpful.
Above I've linked the instructions on how to create logs. Please follow it and post the links you'll create.
Click to expand...
Click to collapse
Unfortunately, none of the two suggested methods worked:
1. The generated link indicates ":/data/data/com.termux/files/home" however, there is no data in this folder other than the file I've already uploaded.
2. The alternative path, as suggested in the original thread doesn't contain such folder: "/cache/terminal_debloater-verbose.log".
I believe the reason is the access restriction on /data/data on Android 11 and above. I'm on Android 12 (Samsung S20). MiXPlore appears to be the only root file explorer, I have installed, that can access and read these folders.
Attached screenshots.

nacos said:
Unfortunately, none of the two suggested methods worked:
1. The generated link indicates ":/data/data/com.termux/files/home" however, there is no data in this folder other than the file I've already uploaded.
2. The alternative path, as suggested in the original thread doesn't contain such folder: "/cache/terminal_debloater-verbose.log".
I believe the reason is the access restriction on /data/data on Android 11 and above. I'm on Android 12 (Samsung S20). MiXPlore appears to be the only root file explorer, I have installed, that can access and read these folders.
Attached screenshots.
Click to expand...
Click to collapse
Screenshot #3:
Code:
[CHOICE]: logs
Testing internet connection - OK
Uploading logs
Link: :/data/data/com.termux/files/home #
Last line: After "Link:" there should appear a link like "https://termbin.com/XXX" where you can see the uploaded logs. That's an easy way to provide/share the logs for the dev.
Unfortunately the tool does not create any link for you and I don't know why.
The command "logs" exits the tool. So, you'll get back to your local shell and Termux shows the current directory you are in: /data/data/...
It does not mean you'll find the logs there. It should look like this:
On my device systemizer also stores logs in
/data/local/tmp. Maybe you'll find your logs there.

nacos said:
I believe the reason is the access restriction on /data/data on Android 11 and above.c
Click to expand...
Click to collapse
You are logged in as root. You have no restrictions as root.

nacos said:
I believe the reason is the access restriction on /data/data on Android 11 and above. I'm on Android 12 (Samsung S20). MiXPlore appears to be the only root file explorer, I have installed, that can access and read these folders.
Click to expand...
Click to collapse
Google restricted access for Android 10+ to the directory /storage/emulated/0/Android/data/*. The real path is /data/media/0/Android/data/*. The path /data/data/* is restricted since many years and contains all data of all your apps. Don't mix up the two paths as they are completely different!

What puzzles me is that I have two identical Samsung S20 phones running identical configurations with the exception of OS. One runs Android 10, the other one Android 12. Again, under the *exact same configuration the App Systemizer runs perfectly fine on Android 10 but not on Android 12.
* When I say exact same configuration I mean settings, apps, restrictions, etc. Obviously I do realize that the OS itself constitutes a significant difference.
Also, maybe it's also worth noting that Debloater runs fine on both phones.

nacos said:
What puzzles me is that I have two identical Samsung S20 phones running identical configurations with the exception of OS. One runs Android 10, the other one Android 12. Again, under the *exact same configuration the App Systemizer runs perfectly fine on Android 10 but not on Android 12.
* When I say exact same configuration I mean settings, apps, restrictions, etc. Obviously I do realize that the OS itself constitutes a significant difference.
Also, maybe it's also worth noting that Debloater runs fine on both phones.
Click to expand...
Click to collapse
Did you find the logs in /data/local/tmp? This will answer your questions.

WoKoschekk said:
Did you find the logs in /data/local/tmp? This will answer your questions.
Click to expand...
Click to collapse
Yes, I did! Thanks for suggesting the logs path.
"mount: can't find /data/adb/modules in /proc/mounts"
See attached log.

Finally I solved it. I needed to uninstall the 17.3.1 version and then install the 17.4.1 version through Magisk from here.
I would normally install/update all my modules through Fox Magisk Modules Manager however:
their repository shows version 17.3.1 as the latest one (the one that I've been experiencing problems with) plus,
the downloaded zip file saved from Androidacy repository appears to install only through their own Fox module. I tried installing it both through Magisk and TWRP but it fails.
Once I've installed the version 17.4.1 through Magisk everything works just fine.
Thank you for your support, I do appreciate it!