Related
[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.
Why do we have to make long distance calls and send sms to use this app?
http://forum.xda-developers.com/showthread.php?t=1422969
Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.
XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb
Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....
Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?
Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk
xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838
xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.
itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^
srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse
seems there is work being done on android nougat in miui for the nikel if im not mistaking ( miui V8.5.2.0.MBFCNED )
link to official thread: http://en.miui.com/thread-645476-1-1.html
Nope. This was on marshmallow
Tapatalk - Redmi Note 4 MKT
crap.. read this in changelog
"System
New - A smarter and more efficient CPU allocation strategy (04-05)
New - Android N update (06-01)"
thought it was on android N
since i dont use miui im not familiar with it from what i understood and probably im wrong.. i thought N updates werent just on coming miui 9 but also on 8.x builds..
too bad.. hope there is a good future for this great phone with updates
Fake changelog.
Read comments there
Someone updated but still MM
Tapatalk - Redmi Note 4 MKT
That update got suspended later. And its going to be suspended till August hopefully. They are planning a huge upgrade for a number of devices. Its gonna be at least MIUI 9 if not Nuget for RN4-MTK.
magnum_2007 said:
That update got suspended later. And its going to be suspended till August hopefully. They are planning a huge upgrade for a number of devices. Its gonna be at least MIUI 9 if not Nuget for RN4-MTK.
Click to expand...
Click to collapse
I'd say MIUI 9 but not nougat based (for our RN4 MTK at least). Remember Xiaomi have a tendency to update with their MIUI version/features but not update the base android version, especially likely to be the case for our MTK device since Mediatek are bad at releasing sources.
what about the threads that are floating around claiming to be the mtk x20 kernel sources for the rn4? havent really delved in, they arent released yet?
i got this phone mainly for its benchmark performance price ratio but also because i had the expectation it would have better development since its more popular than my last..
seems sad that the SD with its lesser tech has so much support and MTK seem unhelpful so were stuck on old firmwares...
thanas said:
what about the threads that are floating around claiming to be the mtk x20 kernel sources for the rn4? havent really delved in, they arent released yet?
i got this phone mainly for its benchmark performance price ratio but also because i had the expectation it would have better development since its more popular than my last..
seems sad that the SD with its lesser tech has so much support and MTK seem unhelpful so were stuck on old firmwares...
Click to expand...
Click to collapse
I don't think we have the necessary files we need ie drivers specifically for the note 4 mtk hardware, hence the limited development. Snapdragon devices are always supported better by devs due to qualcom sharing all their sources.
It's still great phone for the money with lots of great features. If you're looking for rom development, snapdragon is the way to go though.
Sent from my Redmi Note 4 using Tapatalk
What is this???
Is this android nougat???!!!
Yes
Tapatalk - Redmi Note 4 MKT
I want learn how to use custom rom and step before use custom rom for this phone, im already google for tutorial but i dint found.
zaffan said:
I want learn how to use custom rom and step before use custom rom for this phone, im already google for tutorial but i dint found.
Click to expand...
Click to collapse
You probably want to start at the below thread about unlocking your boot loader and installing twrp etc. There's plenty of guides on XDA, and there's a noob Q&A thread in the Q&A section which is best to check out also and ask any questions rather than this development section.
https://r.tapatalk.com/shareLink?ur...share_tid=3517806&share_fid=3793&share_type=t
[Guide] Redmi Note 4 - Unlock Bootloader / Unbrick / Recovery
Sent from my Redmi Note 4 using Tapatalk
Hey!!!!!im so happy you reply my question!!!!!not like in team miui team so hard for reply to user!!!thanks alot bro reply!!!
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
Im user redmi note 4x 4gb/64gb mediatek.u have any tutorial for me sir?so hapy if you can help.
Nougat
del
del too
No nougat no oreo
Yesterday Miui 9 7.8.28 beta was given to the testers but is still android 6.
Illuminatus_ said:
Yesterday Miui 9 7.8.28 beta was given to the testers but is still android 6.
Click to expand...
Click to collapse
Link plz to fastboot or recovery image
Delete thread please
Sent from my Redmi Note 4X using Tapatalk
We have the source code now:
http://consumer.huawei.com/en/openso...e=10&curPage=1
Can someone please port Lineage OS to the Mate 9? I will buy them a coffee.
Nickco43 said:
We have the source code now:
http://consumer.huawei.com/en/openso...e=10&curPage=1
Can someone please port Lineage OS to the Mate 9? I will buy them a coffee.
Click to expand...
Click to collapse
beer!! from me
me too.or can produce mokee
Please, somebody can help us? We will need a reverse engineer for the drivers to port and somebody from Lineage crew.
AFAIK, the problem with the published source code by Huawei is that the camera does not work.
tusko5 said:
AFAIK, the problem with the published source code by Huawei is that the camera does not work.
Click to expand...
Click to collapse
Can you provide the technical details on the error messages ?
There is a LineageOS image for Honor8 (which has problems with random crashes) but the actual kernel interface differences between Honor8 and Mate9 are minimal.
Sorry I don't know the details but there has been some discussion in this thread:
https://forum.xda-developers.com/mate-9/help/kernel-source-code-t3556352
cr2 said:
Can you provide the technical details on the error messages ?
There is a LineageOS image for Honor8 (which has problems with random crashes) but the actual kernel interface differences between Honor8 and Mate9 are minimal.
Click to expand...
Click to collapse
The camera itself works, it's when you take a picture that the image doesn't save.
I narrowed it down to a sqlite error when trying to save:
Code:
06-09 12:00:45.188 E/SQLiteDatabase(26762): android.database.sqlite.SQLiteConstraintException: UNIQUE constraint failed: gallery_media._data (Sqlite code 2067), (OS error - 2:No such file or directory)
I'm not sure how to fix that actually.
gallery_media._data seems to have a dot too many imo, but maybe it's supposed to be that way.
I never tried with another camera app, to check if it's just stock that doesn't work.
Edit: This can apparently mean 2 things, either the db is not read/write or the ID (gallery_media._data) already exists.
Edit 2: Actually, this error no longer exists on B185.
Google Camera works fine. It's just Huawei's camera app that doesn't work correctly.
Then, if the kernel works, what are the general steps to start working on a Mate 9 Lineage port?
If the kernel interface is similar to that of Honor 8, shouldn't the Honor 8 Lineage sources be the base for a Mate 9 port?
tusko5 said:
Then, if the kernel works, what are the general steps to start working on a Mate 9 Lineage port?
If the kernel interface is similar to that of Honor 8, shouldn't the Honor 8 Lineage sources be the base for a Mate 9 port?
Click to expand...
Click to collapse
Apparently the unofficial lineage for Honor 8 uses stock honor 8 kernel.
I'm syncing now, might take a while.
Hopefully we just need to edit the Honor 8 sources for Mate 9.
ante0 said:
Apparently the unofficial lineage for Honor 8 uses stock honor 8 kernel.
I'm syncing now, might take a while.
Hopefully we just need to edit the Honor 8 sources for Mate 9.
Click to expand...
Click to collapse
I hope so!
It seems like we need some serious talent to get a proper rom ported.
I started messing around with building the kernel but, given my lack of experience, I wouldn't expect much.
Any progress on this my friend? @ante0
albertobom said:
Any progress on this my friend? @ante0
Click to expand...
Click to collapse
I gave up, but might start again soon.
ante0 said:
I gave up, but might start again soon.
Click to expand...
Click to collapse
There are few more devs here maybe you should unite. Don't give up just yet.
How far did you get/where did you get stuck? I've got time to mess around with things next week. @ante0
thenellt said:
How far did you get/where did you get stuck? I've got time to mess around with things next week. @ante0
Click to expand...
Click to collapse
I've only just started. I changed everything in devices, vendor left now. But that's just replacing Honor 8 text with Mate 9 text.
Got to replace files too.
I'm not a dev, I'm more a fixer guy xD
I'm not a dev, but I have programming experience and am willing to help since I'm now a Mate 9 user.
So guys, anyone set a team to work on this?
As some of you have already noticed, a couple of weeks ago @Dinolek and I published a utility, that allows bypassing authentication on MTK devices.
The tool is based on an exploit dubbed kamakiri, which was originally found by @xyz` and released for the Amazon FireTV Stick 4K (mantis)
What does this mean?
You can use this utility to bypass Serial Link Authentication and Download Agent Authentication on supported devices to use software such as SP Flash Tool to unbrick devices that would otherwise require authentication (AUTH-file).
The tool has since been expanded to support more SOCs by contributions from @viperbjk, @Rortiz2 and others.
It currently supports the following SOCs (and their variations):
mt6261
mt6572
mt6580
mt6582
mt6592
mt6595
mt6735
mt6737
mt6739
mt6750
mt6753
mt6755
mt6757
mt6761
mt6763
mt6765
mt6768
mt6771
mt6779
mt6785
mt6795
mt6797
mt6799
mt6833
mt6853
mt6873
mt6885
mt8127
mt8163
mt8167
mt8173
mt8590
mt8695
There are two parts to this project, the Utility itself and the Exploit Collection.
Please refer to the projects README how to set up your environment to use this utility successfully.
Please note, this project has already been incorporated in multiple commercial tools without even a mention.
This software is free to use, but the courtesy of at least mentioning the original authors is expected.
If you like this software and would like to support us, you can donate
reserved #1
reserved #2
Donated, fantastic work!
Nice work!
This will work on MTK devices that misconfigured on preloader, like this one:
Code:
MTK_SEC_CHIP_SUPPORT=yes
MTK_SEC_USBDL=ATTR_SUSBDL_ONLY_ENABLE_ON_SCHIP
MTK_SEC_BOOT=ATTR_SBOOT_ONLY_ENABLE_ON_SCHIP
MTK_SECURITY_SW_SUPPORT=yes
CUSTOM_SEC_AUTH_SUPPORT=no
Which means the phone was secured but no authentication file is generated, and impossible to revive without some sort of programmer back then. An example is Nokia 3.
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
Same! Spent days a few weeks ago trying to get around the authentication. Is it possible for MT6750?
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
It depends, if the developers will have a device with the same soc or a device with a similar soc then it is possible that they port it, or even another person who is good at decompilers who wants to port can do it, you can also but you always depend on whether you can do it
Yoss Roness said:
Wow! Amazing work! Quick question, is there any chance in the future of expanding this exploit to support MTK6762? My Redmi 6 has been bricked for two years now because I can't get access to a Xiaomi Auth account...
Click to expand...
Click to collapse
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
k4y0z said:
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
Click to expand...
Click to collapse
Can you create a guide on how to port (for noobs though)? I also have an unsupported device and would like to try porting.
XRed_CubeX said:
Can you create a guide on how to port (for noobs though)? I also have an unsupported device and would like to try porting.
Click to expand...
Click to collapse
I can't really create a porting guide.
As said, first step is to get a bootrom-dump.
This may be achieved using testmode.
What SOC do you have?
k4y0z said:
I can't really create a porting guide.
As said, first step is to get a bootrom-dump.
This may be achieved using testmode.
What SOC do you have?
Click to expand...
Click to collapse
MT8321
k4y0z said:
MT6762 should be the same as MT6761, so that should already be supported.
For unsupported devices you can try running the utility in testmode.
Code:
./main.py -t
If you can get a bootrom-dump, we can see what we can do about support.
Click to expand...
Click to collapse
I tried, but when I ran your command I recieved this error: Unable to create process using '/bin/python3
XRed_CubeX said:
MT8321
Click to expand...
Click to collapse
Did you try dumping bootrom using testmode?
Yoss Roness said:
I tried, but when I ran your command I recieved this error: Unable to create process using '/bin/python3
Click to expand...
Click to collapse
Please refer to the README how to set up python and libusb or use FireISO
XRed_CubeX said:
MT8321
Click to expand...
Click to collapse
Can't find a lot of info on MT8321, can you give more information what device this is?
k4y0z said:
Can't find a lot of info on MT8321, can you give more information what device this is?
Click to expand...
Click to collapse
Alcatel 3c
XRed_CubeX said:
Alcatel 3c
Click to expand...
Click to collapse
Any luck with testmode?
k4y0z said:
Any luck with testmode?
Click to expand...
Click to collapse
I haven't tried yet
firstly this is huge, soon enough we'll probably get rid of oems' dumb restrictions and paywalls for having permission over your own device but it doesnt work on my redmi note 8 pro global
it's just stuck on waiting for device, i've tried everything like cmd in admin, restarting, all the debug parameters, even class filters. i dont see mtk6785t but 6785 is there so i think that shouldnt be an issue? idk but any help would be great, i have the payloads in the payloads/ folder and the default_config.json5 file in the dir with main.py in it
i'm running it on a pc w ryzen 5 3600 so that could be why? i've checked the code it seems to just not find the serial port. if i should try on an intel cpu, how would i use it with a mac? because i dont have any other pcs. maybe through vm but i doubt that'd work. anyways amazing work just wait for someone to make a gui for it (maybe me but.. cries in tkinter) and it'll be an end to all the stupid oem stuff
again any help would be really appreciated i dont wanna get a realme or something just because i hate miui
wentaas said:
it's just stuck on waiting for device, i've tried everything like cmd in admin, restarting, all the debug parameters, even class filters. i dont see mtk6785t but 6785 is there so i think that shouldnt be an issue?
Click to expand...
Click to collapse
I don't know if mt6785 and mt6785t are the same.
If it doesn't even see your device your issue is something else.
Make sure your device is in bootrom-mode.
Is there any port of android 12 for our device? I see there are ports fot op8 and op8pro. Can they he used for ours?
Im currently testing if beta 2 gsi will work bia DSU. First boot with it just got an Android 11 dsu but im trying the second option it gives which i believe is just without gms. At this point I don't think that will be any different but ill update after I try it.
Update: as i expected that still didn't work. I suspect in order for ot to actually load an Android 12 system the gsi build needs special OnePlus keys.
Also, can you provide a link to these ports you're talking of? Im not finding anything on xda or via a google search.
Hi. This is the link to video and files
kirankowshik said:
Hi. This is the link to video and files
Click to expand...
Click to collapse
the beta 4 from this channel has broken call functionality.. a cell phone without call feature is plain useless. Is there anything else that can be done?