yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] Mikos:
SnooperStopper

Android device ecryption password manager and failed unlock attempts monitor

SnooperStopper allows you to have different device encryption password than

screen unlock pattern/PIN/password. You can have strong device encryption

password (which you only need to enter once after booting your device) but

simple pattern/PIN/password for unlocking your screen.

If attacker tries to guess your simple pattern/PIN/password, he has only

few tries (default is 3) after which the device is rebooted and he needs

to enter your strong device encryption password again.

Where to get it:

Google Play

Eutopia.cz F-Droid Repository

Project on GitHub

Why is it needed:

Android always sets device encryption password same as screen unlock pattern/PIN/password.

This is very unfortunate, because you should have encryption password as strong

as possible, but nobody wants to enter long password all the time just to unlock screen.

There is Android issue #29468

requesting different passwords for encryption and screen lock, but it seems to be

ignored by Google (it is there from 2012 and recently marked Obsolete by Google).

How to use it:

After installation, start SnooperStopper and grant it superuser permissions. Then

enable device admin in app, which allows SnooperStopper to monitor failed screen

unlock attempts and reboot device if maximum number is exceeded.

Whenever you change your screen unlock pattern/PIN/password, Android also changes

your device encryption password, so you have to set your strong encryption

password again. SnooperStopper automatically opens window where you can change it

right after you change your screen unlock pattern/PIN/password, so you should never

forget about it.

Requirements:

Android >= 4.0.3

enabled device encryption (Settings => Security => Encrypt phone )

root (Android doesn't allow apps to change device encryption password or reboot your device without root access)

Credits:

Whole device encryption password changing code is taken from Nikolay Elenkov's

Cryptfs Password Manager.

XDA:DevDB Information

SnooperStopper, App for all devices (see above for details)

Contributors

Mikos, Nikolay Elenkov

Source Code: https://github.com/xmikos/SnooperStopper

Version Information

Status: Stable

Current Stable Version: 1.3

Stable Release Date: 2016-03-21

Created 2015-07-13

Last Updated 2016-03-21
[Android Apps and Games] mischasworld:
Hello,

Thanks for your great tool, this really fills the gap between a safe encrypted and a everyday easy to use device.

Unfortunately I can't change the encryption password on my maguro galaxy nexus device.

When I try to change my encryption password I get the message cannot get super access

For a short time the root access symbol lights up and disappears.

Snooper Stopper is listed in the device admin list. My nexus (which runs on slim rom lollipop ) asked me whether I would like to give root access to snooper stopper and I agreed.

I'd really like to help to fix this bug so I can use your tool.

Many greetings

Michael

P.S. Already opened a issue at github before I found this thread on xda :mad:
[Android Apps and Games] Mikos:
Like I said on GitHub (writing it also here for reference):

It is problem with SELinux policy. if you have Android >= 5.0, you also need sepolicy-inject utility (you can find it here: setools-android with sepolicy-inject) or supolicy (part of SuperSU - but SuperSU is not opensource, so I highly discourage it).
[Android Apps and Games] Mikos:
New version 1.3 is compatible with Android 6 and CyanogenMod 13. Also starting from version 1.1 sepolicy-inject tool is included into SnooperStopper, so you don't need to install any external utility.
[Galaxy S6 Edge Themes and Apps] GuestK00326:
here are mine and a few i have edited from morgan1202's post belowe
[Galaxy S6 Edge Themes and Apps] morgan1202:


---------- Post added at 12:42 AM ---------- Previous post was at 12:40 AM ----------
[Galaxy S6 Edge Themes and Apps] GuestK00326:
Look nice I was thinking green wallpapers like ones I put but oh well others look nice as well
[Galaxy S6 Edge Themes and Apps] morgan1202:
Lol somehow only read edge,not green edge,my bad
[Galaxy S6 Edge Themes and Apps] GuestK00326:
(Y)
[Galaxy S6 Edge Themes and Apps] aamir2day:
Nice collection. .
[Galaxy S6 Edge Themes and Apps] MarcSinger:
Wallpapers for S6 Edge Emerald Green

Here's a zipped collection of some green wallpapers I use in conjunction with the Material Dark (Green) Theme.

Samples:

Link:

http://d-h.st/mQlI
[Galaxy S6 Edge Themes and Apps] GuestK00326:
file will not open for me when downloaded
[Galaxy S6 Edge Themes and Apps] elmassari:
From new Android 6.0 Marshmallow wallpapers... ??
[Galaxy S6 Edge Themes and Apps] GuestK00326:
more
[Galaxy S6 Edge Themes and Apps] herbivor:
Dots......

￼
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] heartbrake:
So I used CM 11 Team Canjica for almost a year but I really got tired of the bad battery backup and sometimes the force close error. Now I have flashed the Stock JB 4.1 via Odin but I am not getting signal at the same position in my house where I used to get 2 bars of signal in CM 11. When I move my phone near the window then the signal will come but it drops after few second and I am not able to call from inside my house. This is a Stock JB problem as I did not have this problem in CM 11 TC. Now what should I do to get my signal back? I also flashed the Cocore refresh r24 kernel via Universal Kernel flash but I am still getting the same signal drop problem.
[Verizon LG G2] NuttyEngineer:
Hi everyone,

I've been tinkering around with my VS980 for the past 2 months. Here is what I've done so far to it:

Stock (11A or 10B I believe) to CM12 -- Everything works, great battery lifetime, but no LTE connectivity

CM12 to 39A via kdz method -- LTE connectivity, but degraded battery usage hours, which some users reported getting fixed by a factory reset

Factory reset while on 39A -- Even worse battery lifetime, lasted only 3 hours on a full charge and phone warms up

Re-flashed 39A using kdz -- Upon boot phone registers on Tmobile, and I get a notification for voicemail then keeps on bouncing connected/unconnected forever

Flashed 27A using kdz -- everything seems stable so far ... no LTE ... but glitchy network connection still. Bounces connected/unconnected a few times then goes solid connection. Battery lifetime seems to have improved to what is expected from a G2. The network bounciness happens everytime I check the phone, but I can still receive SMS and make phone calls

I have a verizon SIM that came with the phone and when I plug it in, the phone shows a solid connection to Verizon network. The glitchy behavior so far seems to be only happening with with Tmobile.

Any idea what exactly could have gone wrong?
[Verizon LG G2] angelgaa:
I have the same problem, looking for a fix as well
[Ascend Mate 7 Original Android Development] acbka:
TWRP Recovery 3.0.2-0 Mate7 Android 6.0

Download only Android 6.0 \ EMUI 4.0​

Features:

* Custom.bin and cust symlinks are saved/restored (if they were exist) in case of Wipe/Format Data. So there not gonna be "cust" issues after factory reset in TWRP. * thank Kostyan_nsk

install

fastboot flash recovery twrp_3.0.2_mate7_6.0.img

screenshot​

View attachment 3735298

Old version for android 5.1

TWRP Recovery 2.8.7.0 for MATE7 Android 5.1

Install​

download twrp with BasketBuild only emui3.1 / Android 5.1

adb reboot bootloader
fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img
fastboot reboot

regards ,

acbka aka asyan4ik =)
[Ascend Mate 7 Original Android Development] cadfertiyu:
And so can anybody make â flashable version of lollipop ?
[Ascend Mate 7 Original Android Development] taitai9616:
so good
[Ascend Mate 7 Original Android Development] Getoo:
Thank you so much Sir, I finally got myself a working recovery
[Ascend Mate 7 Original Android Development] CCDillon:
Great work, my friend. Thank you very much.

Anyone try to get Xposed working? I know there is a super alpha for 5.1.1 but I don't want to risk anything on my device.
[Ascend Mate 7 Original Android Development] Getoo:
Tried that, broke my SysUI.
[Ascend Mate 7 Original Android Development] paulopais:
It will work on 5.1.1 ? :)
[Ascend Mate 7 Original Android Development] acbka:
yes , work only 5.1+
[Ascend Mate 7 Original Android Development] paulopais:
you are the best .. waiting for b312 , then i will install both, twrp + b312 and make backup to share :)
[Ascend Mate 7 Original Android Development] bubble_cat:
Thank you, previous version works perfectly on MT7-TL10 ;)
[Ascend Mate 7 Original Android Development] acbka:
no problem, any suggestions please write here
[Ascend Mate 7 Original Android Development] paulopais:
Thank you a lot my friend .. Great job .. How can I make backup from original recovery ?
[Ascend Mate 7 Original Android Development] acbka:
this twrp work only 3.1 emui/ 5.1 android . Huawei in 5.1 change many links . Not use this twrp for restore 3.0emui / 4.4 android .

I'm working on dual/multiboot recovery .

View attachment 3407577

tomorrow will add a link to the original recovery =)

if you have any questions write me in viber +375293294774

regards
[Ascend Mate 7 Original Android Development] elroy944:
Works for all variants of mate 7 with lollipop?
[Ascend Mate 7 Original Android Development] acbka:
try it, what is the difference in recovery ?
[Ascend Mate 7 Original Android Development] elroy944:
Can't try atm as my device is in for repair [emoji14] just wanted to know for when i get it back to flash the moment i receive
[Ascend Mate 7 Original Android Development] stanlawren:
Thanks For The great work. I think I might Just install Viber so we talk more. Need to learn how to compile twrp
[Ascend Mate 7 Original Android Development] djzero86:
A backup of original recovery will be great...
[Ascend Mate 7 Original Android Development] OscarBaia:
Does it work on b312 mtl-09?
[Ascend Mate 7 Original Android Development] acbka:
i have mt7-l09 / b312 - work perfectly.
[Ascend Mate 7 Original Android Development] OscarBaia:
How can i do it? Im new to huawey. Please help
[Ascend Mate 7 Original Android Development] xSplash99x:
I get a bad massage: too many links. I dont understand this because i already flash the drivers and i bootloader unlocked and rooted and lollipop on the board :) what can i do?
[Ascend Mate 7 Original Android Development] stanlawren:
Es ist ganz einfach!

You have to download mate 7 zip file containing The drivers and recovery. From mate7.net

Extract the recovery to your desktop and open The tools folder

Now copy the downloaded twrp to the same place You extracted the recovery to

Now Just hold The shift key and right-click and select open command window here

When You are in command window connect your phone via USB and input the code

adb reboot bootloader

fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img

fastboot reboot

Disconnect your phone all done
[Ascend Mate 7 Original Android Development] acbka:
screenshot plz
[Ascend Mate 7 Original Android Development] rowihel2012:
Do you think this recovery will work with the new B313 5.1.1???
[Ascend Mate 7 Original Android Development] paulopais:
Can you help twrp on B313 ? i want to test if it works but i need b313 original recovery .

thank you
[Ascend Mate 7 Original Android Development] rowihel2012:
Is thier a way to root it and make a backup to recovery with flashfy??
[Ascend Mate 7 Original Android Development] paulopais:
i think no. :| .. acbka will resolve the problem fast :)

---------- Post added at 09:27 PM ---------- Previous post was at 08:34 PM ----------

twrp installed :) .. it works -- b313

now just need stock recovery for future updates :)
[Ascend Mate 7 Original Android Development] rowihel2012:
Wow worked with you

So the 5.1 stock recovery will work with b313

Try it
[Ascend Mate 7 Original Android Development] elroy944:
Anyone got stock b312 mt7-l09 recovery? I want to roll back
[Ascend Mate 7 Original Android Development] rowihel2012:
https://onedrive.live.com/redir?res...2861&authkey=!AK4eHGGHjQf--Dw&ithint=file,img

works with all lolipop roms in mtl09 and mtl10
[Ascend Mate 7 Original Android Development] elroy944:
Thanks that did the job. Flashed 2 times back and eventually stayed at b300 (transition firmware) as in b312 i don't get carrier aggregation and in b300 and below its no problem. Did several wipes and also rollbacks but not comming back in b312. (and i need it as i have amazing fast download speed on lte-a)
[Ascend Mate 7 Original Android Development] rowihel2012:
it is great to have one recovery works with all make it easy :D

kitkat is way better faster and smoother
[Ascend Mate 7 Original Android Development] cata88pl:
Hi!

I have Mate 7 L09 (2gb of ram). Before i had lollipop 5.1.1 (b312) on my phone. Everything was ok, but i remembered that before on kitkat i had some "ios" animation pack installed and it was ok.

So from custom recovery, i installed that pack. (big mistake, don't do it) my phone started by i doesn't work properly. I had access only to settings. After that i did a wipe and a factory reset.

And from here my phone didn't want to boot. I only see the huawei logo. I tried to install the transition pack (by pressing vol - + vol + power) after many attempts i installed the pack. When i wanted to install the kitkat it froze at 90%. I did another wipe, another factory reset. And from here i tried a lot of combination. Lollipop bootloader, with kikkat installer, lollipop bootloader with update pack for lollipop, with transition pack. I tried also with kikkat bootloader and all the combination from above. When i install a custom twrp it tells me that i don't have any operation system on my phone.

Can you help me?

Thank you!
[Ascend Mate 7 Original Android Development] demang:
Where can I download lollipop? thanks
[Ascend Mate 7 Original Android Development] paulopais:
To update to B324 i have to install stock recovery?

Enviado do meu HUAWEI MT7-TL10 através de Tapatalk
[Ascend Mate 7 Original Android Development] stanlawren:
To update to any software version be it beta or official, you must have stock recovery installed

HUAWEI software updates don't install on custom recoveries
[Ascend Mate 7 Original Android Development] tdude:
Is it just me.. I keep getting disc image file corrupt. downloaded 4 times so far.
[Ascend Mate 7 Original Android Development] rOman2205:
I updated to B324, 5.1.1, M7 T10, Unlocked Bootloader, installed TWRP 2.8.7.0, but supersu showing no binaries installed.

Any thoughts.......

Note: Solved. Just flashed Supersu from phone's internel memory, via TWRP.

Thnks for the awesome work.
[Ascend Mate 7 Original Android Development] RedyRock:
Where did you get that Supersu from? Mine is saying the samething...
[Ascend Mate 7 Original Android Development] rOman2205:
Got it from the official website of Chainfire.

Just make sure that it is in the internal phone storage not in the external sd card.

Installation from google play will give u the msg that no binary is installed.
[Ascend Mate 7 Original Android Development] RedyRock:
Got it, it worked.! Thanks man
[Ascend Mate 7 Original Android Development] ahhl:
Can the OP pin this. to first thread
[Ascend Mate 7 Original Android Development] armude:
For your interest, doing a factory reset from TWRP will erase internal sd and external sd, now i have no rom to flash, no backup, nothing, and mega server is not working(To download KangVIP rom)
[Ascend Mate 7 Original Android Development] snake65:
Any one having there sd card preparing every time screen comes on.

If any one has this issue try plugging back into the huawei program on comp and it should fix it.
[Ascend Mate 7 Original Android Development] kingrk:
I tried to install it today on my phone (Ascend Mate 7 MT7-TL10) running Android 5.1.1 and got this error: "FAILED (remote: image verification error). I tried various options, installed USB drivers, restarted both my phone and PC (Windows 10) but nothing has helped. When I run "fastboot devices", it lists my device in the bootloader mode.

Just to clarify, the bootloader screen shows "PHONE Unlocked", which I believe means that the bootloader is unlocked (I also used the command "fastboot oem get-bootinfo", which showed "(bootloader) unlocked"). I also have Developer Options activated and USB debugging activated.

Result of the command "fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img":

target reported max download size of 471859200 bytes

sending 'recovery' (12644 KB)...

OKAY [ 1.368s]

writing 'recovery'...

FAILED (remote: image verification error)

finished. total time: 1.371s

Can someone please advise what can be done to overcome this? Thanks in advance!
[Ascend Mate 7 Original Android Development] stanlawren:
Two things can cause this

1. Damaged or bad twrp recovery file

2. The file isn't properly named

I suggest you download another twrp recovery file and verify the filename is correct before flashing
[Ascend Mate 7 Original Android Development] kingrk:
No. The bootloader is locked and the command "fastboot oem get-bootinfo" probably shows that it is not locked to a carrier. When I used the command "fastboot oem get-lockstate", it came back as "locked".

I am still searching for a way to unlock the Bootloader. I also installed the Huawei Cloud Application on my phone (from Google Play) but it fails to log in. I think that the device has to connect to the Huawei cloud using this mobile app and then wait for a minimum of 14 days after which, the EMUI web site of Huawei will disclose the Unlock Code for bootloader. After that, rooting will be possible using a custom Recovery.

Huawei has made it extremely difficult to unlock their bootloader.

Any suggestions are welcome.

Thanks!
[Ascend Mate 7 Original Android Development] kingrk:
I got the Bootloader Unlock code and I unlocked my Mate 7 using the command "Fastboot oem unlock <code>" and it showed "done". I repeated the command and it showed "remote: already user unlocked", which convinces me that the bootloader is finally unlocked.

However, when I tried to flash TWRP recovery using "fastboot flash recovery twrp_2.8.7.0_mate7_5.1.img", I still get the same error "FAILED (remote: image verification error)". I have checked the XDA pages and the TWRP version seems to be right, as I used the link (https://basketbuild.com/devs/asyan4ik/hwmt7_l09) given on this post only.

Sequence as follows:

Fastboot Flash Recovery twrp_2.8.7.0_mate7_5.1.img

target reported max download size of 471859200 bytes

sending 'recovery' (12644 KB)...

OKAY [ 1.384s]

writing 'recovery'...

FAILED (remote: image verification error)

finished. total time: 1.404s

Is there a separate TWRP version for MT7-TL10 version? If yes, can someone provide the link, please?

This is very frustrating because it's a great phone and not being able to root is very limiting!
[Ascend Mate 7 Original Android Development] kui425:
does it work on Android 6 ?
[Ascend Mate 7 Original Android Development] blackhawk_LA:
This happened to me and I think I solved it updating my fastboot binaries. But I'm not sure since it was long time ago

Sent from my Mate
[Ascend Mate 7 Original Android Development] XenSA:
there is no android 6 for the mate 7?
[Ascend Mate 7 Original Android Development] acbka:
Nop , is not android 6 . i not have mate 7 device working on android 6 .
[Ascend Mate 7 Original Android Development] Skorpi58:
Of course is there Android 6 for Mate 7.....:D

http://xdaforums.com/mate-7/general/android-6-0-marshmallow-update-huawei-t3226744
[Ascend Mate 7 Original Android Development] fmurillo:
I have mate 7 b510 mm installed on my device... And no root... We need your help!!!
[Ascend Mate 7 Original Android Development] albert-so758:
http://xdaforums.com/mate-7/development/beta-b510-android
[Ascend Mate 7 Original Android Development] acbka:
twrp update ver. 3.0.2-0
[Ascend Mate 7 Original Android Development] kr1shna:
Works perfectly thank you :)
[Ascend Mate 7 Original Android Development] OscarBaia:
Fantastic on mate 7 golg mtl10
[Ascend Mate 7 Original Android Development] chudy_85:
Work great but restore its very slow.

Send from hell ✌
[Ascend Mate 7 Original Android Development] Skorpi58:
Hmmmm that's bad with restoring.... and SuperSu Pro 2,64 is Ok with this TWRP Version?
[Ascend Mate 7 Original Android Development] chudy_85:
I try and work for me

Send from hell ✌

---------- Post added at 08:08 PM ---------- Previous post was at 07:46 PM ----------

Fill restore 5 gb my backup take 900 second

Send from hell ✌
[Ascend Mate 7 Original Android Development] RobboW:
Sounds similar to mine. SD card will slow it down compared to internal NAND memory, but backup to internal is IMO, pointless.

Don't use less than a class 10 SD card. If possible, use a faster Sandisk. Mine is a 64Gb class 10 Kingston and it does have a slightly slower constant write speed than a decent Sandisk, but is still fast enough for playing movie files.

I just set up a 64Gb class 10 Kingston in my son's Mate 7 and a class 10 128Gb Kingston in my oppo and both were about the same transfer speed so fortunately no penalty going to the higher data density.
[Ascend Mate 7 Original Android Development] kr1shna:
I've tried many memory cards but found samsung evo + the best in speed and it's light on pocket.
[Ascend Mate 7 Original Android Development] acbka:
I need some tests on the location file " data/custom.bin" after data reset

thank
[Ascend Mate 7 Original Android Development] OscarBaia:
Hello got it working on mt-10 gold with kangvip 560 but when trying to wipe dalvik/cache is not working. Any solution?
[Ascend Mate 7 Original Android Development] acbka:
Use rm –rf
[Ascend Mate 7 Original Android Development] OscarBaia:
Can you explain more, please.

Regards
[Ascend Mate 7 Original Android Development] acbka:
development stopped, split screen ((((((((((((((
[Ascend Mate 7 Original Android Development] stanlawren:
Does this mean you're now working on Android N TWRP recovery for our Mate 7?

Thanks for your work

Es ist oft frustrierend, wenn man alle Antworten weiß, aber niemand kümmert sich darum die Fragen zu stellen :|
[Ascend Mate 7 Original Android Development] Curtz1209:
Hey guys, please help. I have Mate 7 L09 and flashed TWRP 3.0.2 all went well. I then flashed SuperSU 2.76 and now it won't boot.

I can still boot to recovery

Please help
[Ascend Mate 7 Original Android Development] stanlawren:
Just rewrite your original stock recovery using fastboot. Then copy a ROM to the dload folder of your sd card then use the force upgrade method to install it. When done your phone should boot up normally.

You can then flash twrp via fastboot again and this time use supersu 2.64 pro

Any other version and you're on your own!

NB: you can also download any compatible stock TWRP backup and restore it from TWRP. Really the options are many but the choice is yours to make.

Es ist oft frustrierend, wenn man alle Antworten weiß, aber niemand kümmert sich darum die Fragen zu stellen :|
[Ascend Mate 7 Original Android Development] Curtz1209:
Hey, Many thanks.

I managed to fix it using the first method you stated.

Flashing TWRP backups just left me in a bootloop.

I was not aware that a specific version of SuperSU was required
[Ascend Mate 7 Original Android Development] hhacker4422537:
need help

Hello everyone

my phone is mt7_tl09 and when i want to flash recovery with fastboot i came with an error:

can't write to recovery

FAILD

can anyone help me?
[Ascend Mate 7 Original Android Development] chudy_85:
Unlock bootloader
[Ascend Mate 7 Original Android Development] hhacker4422537:
my bootloader is unlocked :crying::crying::crying:
[Ascend Mate 7 Original Android Development] hhacker4422537:
helpppppppppppppppppppp :confused:
[Ascend Mate 7 Original Android Development] chudy_85:
Unlock again bootloader
[Ascend Mate 7 Original Android Development] CloudCompute:
Just unlock bootloder again, even if it shows unlocked already. If required relock and unlock again. You should be good after that.
[Ascend Mate 7 Original Android Development] hhacker4422537:
now it says :

FAILED (remote: Command not allowed)

and adb says my device is offlien
[Ascend Mate 7 Original Android Development] hhacker4422537:
help please