[ROM][Official] Kali NetHunter for the Nokia 3.1 Android 9 - Nokia 3.1 ROMs, Kernels, Recoveries, & Other Devel

{
"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"
}
I present to you: Kali NetHunter for the Nokia 3.1 Android 9
The first Nokia with Kali Nethunter! (in chronological order)
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks, as well as a client to the Kali NetHunter App Store.
Beyond the penetration testing tools arsenal within Kali Linux and the Kali NetHunter App Store, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
~ Prerequisites ~
- Android 9 Stock (V3.180) https://androidfilehost.com/?fid=4349826312261827395
- Universal Force Encryption Disabler - https://www.androidfilehost.com/?fid=8889791610682920239
- TWRP with fixed touch by @belkaliz - https://forum.xda-developers.com/attachments/recovery-boot_a_twrp_nokia31-20211016-0945-img.5435907/
- TWRP (no touch) unofficial - https://www.androidfilehost.com/?fid=8889791610682928997
- Magisk – https://forum.xda-developers.com/apps/magisk
- Unlocked bootloader by Hikari Calyx https://t.me/HikariCalyxFIH
~~ Downloads ~~
- NetHunter installer: https://kali.org/get-kali#kali-mobile
- NetHunter bootanimation and firmwares: https://www.androidfilehost.com/?fid=8889791610682929010
~~ How to Install ~~
Assuming you have unlocked bootloader, stock Pie (v3.180).
Please note due to the lack of device tree, my TWRP porting skills and time, we're using my TWRP with no touch. Several methods and solutions were tried by not only me without success.
I can only think of that the touch driver is being initialised from /vendor during boot.
Feel free to contribute if you make a working TWRP
You'll need an OTG cable and mouse to do one step of the following process. You'll also need a Linux or Windows PC with adb tools downloaded
- Do initial setup after unlocked bootloader - don't use wifi at setup, as you don't want OTA, they are not supported
- Plug your phone into your PC
- Turn on ADB debug in Developer Settings, then adb reboot bootloader - or do it with plug in USB when powered off and hold power + vol down
- Flash TWRP
Code:
fastboot flash boot_a boot_a_twrp.img
- Do "fastboot reboot" into TWRP (to do this, as soon as it vibrates, hold power+vol up, release power on AndriodOne logo, release vol on twrp logo)
- Use OTG mouse: Format data and reboot into TWRP
- Do adb push FBEDisabler and install it
Code:
adb push DisableForceEncryption_Treble.zip /sdcard/
twrp install zip /sdcard/DisableForceEncryption_Treble.zip
- Do initial setup, enable ADB
- Reboot to recovery,
Code:
adb reboot recovery
- Do adb push NH, Magisk, bootanimation, firmware zip and scripts (from unzipped nokia_nh.zip) to /sdcard/ and flash them.
Code:
adb push <DOWNLOADED_FILES_PATH>/* /sdcard/
adb shell
twrp install zip /sdcard/nethunter-2020.3-es2-pie-kalifs-minimal.zip
twrp install zip /sdcard/Magisk-v20.1.zip
cd /sdcard/
sh bootanimation.sh
sh firmware.sh
reboot
- Start Kali NH App and do a final reboot
- To upgrade to full Kali fs, do
Code:
apt-get update && apt-get install kali-linux-nethunter -y
~~~ Notes & Updates ~~~
Credits: The Offensive Security Team and the NetHunter community
Android Version: 9.0
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the Nokia 3.1
Contributors
@yesimxev
For bootloader unlock and general Nokia support: @hikari_calyx
Source Code: https://gitlab.com/kalilinux/nethunter
Kernel Source: https://github.com/yesimxev/android_kernel_nokia_es2

Reserved

Reserved #2

Hi there,
Thank for very much for the release and the flashing instructions. I'm wondering though if you'll be releasing the TWRP sources. Perhaps your work will help others make a release with touch support.
Cheers

ivan_the_persnickety said:
Hi there,
Thank for very much for the release and the flashing instructions. I'm wondering though if you'll be releasing the TWRP sources. Perhaps your work will help others make a release with touch support.
Cheers
Click to expand...
Click to collapse
Sorry for the late reply, I wanted to give a better code for you but I mainly used this in the above TWRP hybrid :laugh:
Built with twrpbuilder device tree generator with omni 7 source. I'm aware that 8 or 9 should have been used but it didn't build successfully for me.
https://github.com/yesimxev/android_device_nokia_ES2_sprout/
twrp.fstab is with with system_a vendor_a etc now, because it was always using _b even if I was booting into _a, but I left it like that because slotselect should really work

Hey again Yesimxev, Does the Nokia 3.1 offer Wireless monitor mode? Thanks

TrillbyMcTipp said:
Hey again Yesimxev, Does the Nokia 3.1 offer Wireless monitor mode? Thanks
Click to expand...
Click to collapse
No, unfortunately it doesn't

Hello! Does the TWRP recovery work on Android 10? (I don't need the ROM, just the recovery)

Gabi_203 said:
Hello! Does the TWRP recovery work on Android 10? (I don't need the ROM, just the recovery)
Click to expand...
Click to collapse
Not sure as this was made of and for Pie source

Hello, wanted to ask if anyone here has tried this or knows it'll work for the 3.1 Plus?

AFAIK it has a different kernel source and no TWRP, so not likely

I fixed touch in your TWRP.

belkaliz said:
I fixed touch in your TWRP.
Click to expand...
Click to collapse
You're a champ! Unfortunately I don't own a 3.1 since, but I'll try as soon as I get one again

Hi all! I guess I'm stuck on the step #1 and all other are failing. I get Error 1 when tring to install Nethunter, both full and minimal versions.
Where do I get the Android 9 Stock (V3.180)?

Марија said:
Hi all! I guess I'm stuck on the step #1 and all other are failing. I get Error 1 when tring to install Nethunter, both full and minimal versions.
Where do I get the Android 9 Stock (V3.180)?
Click to expand...
Click to collapse
Do you have android 10 now? @hikari_calyx is 3.1 downgradable to v3.180? He has the images but I don't remember

Марија said:
Hi all! I guess I'm stuck on the step #1 and all other are failing. I get Error 1 when tring to install Nethunter, both full and minimal versions.
Where do I get the Android 9 Stock (V3.180)?
Click to expand...
Click to collapse
Hello here : https://sourceforge.net/projects/fihsw-mtk/ . I downloaded, and i install in my nokia 3.1. it's a good version 9.0 pie. Is the @hikari_calix link.

Hi yesimxev, I see you are here, just a quick question. I installed your Kali nh in my nokia 3.1. I followed step by step, and every folder or zip downloaded, and installed well in my phone. But I have a problem at the end, when I restart my phone I don't have the nh app and the magisk app, just a nice screenshot, and the standard google apps. in the second to last command you say: and flash them,, but in the commands below I don't see for example: "fastboot flash boot_a /path to nethunter/".
Could you just clarify these lines of code, please.

Dooblewoops said:
Hi yesimxev, I see you are here, just a quick question. I installed your Kali nh in my nokia 3.1. I followed step by step, and every folder or zip downloaded, and installed well in my phone. But I have a problem at the end, when I restart my phone I don't have the nh app and the magisk app, just a nice screenshot, and the standard google apps. in the second to last command you say: and flash them,, but in the commands below I don't see for example: "fastboot flash boot_a /path to nethunter/".
Could you just clarify these lines of code, please.
Click to expand...
Click to collapse
I see. Flash NH means to install the NH zip through recovery

hi yesimxev, tank's for you quick reply. i do make something false, because i have the confirmation the magisk is installed, but i have not magisk in my phone ? You say "do initial setup" where ? in the twrp or in app magisk on the phone ?

Initial setup is android first start after formatting data and flashing force encryption disabler and Magisk. NetHunter can only be installed after android setup is done. And Magisk has to be started once, to finish it's setup after installed in TWRP

Related

[Kernel+][Exynos] Kali NetHunter for the Galaxy S7

​
WARNING: When using custom kernels on the S7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
OKAY SO
This is Kali NetHunter 3.15.2 for the Galaxy S7.
If you don't know what Kali NetHunter is, well, it's the entire Kali Linux operating system in a chroot on your phone, plus a bunch of awesome apps for executing exploits, fixing things, doing cool things. It goes on, I suppose.
I'm gonna be honest guys, I'm not a security person. When it comes to security, I'm more of a Paul Blart.
What I do know though, is that there is apt-get, and apt-get is life.
Find much more information here: https://github.com/offensive-security/kali-nethunter/wiki
The answer to all your questions, generally the answer is YES, IT CAN DO THAT.
Most ROMs should be supported, as our installer uses a dynamic patching method on your current boot image!
The NetHunter installer zip will add a few files to your /system partition, and install all of the NetHunter apps to your /data partition.
The chroot is located in /data/local/nhsystem, so you don't have to worry about your system partition being full. It's full read/write capable.
Understand that the zip will replace your current kernel with a completely different one.
This is necessary because most stock or custom kernels don't provide the drivers needed to operate most of Kali NetHunter's features.
NetHunter also includes its own Busybox that gives you full large file support and some extra applets.
It will not overwrite your current one, and will happily install alongside it as busybox_nh.
DOWNLOAD
Current version: 3.15.2 (stable, 2016-11-04)
Please be careful to download the right version based on this table:
SM-G930F, SM-G930FD, SM-G930W8, SM-G930X: kernel-nethunter-herolte-*
SM-G930K, SM-G930L, SM-G930S: kernel-nethunter-heroltekor-*
S7 edge: You're in the wrong forum!
All others be sad.
For the apps, chroot, and everything other than just the kernel, you will also need to download:
nethunter-generic-arm64-*
See installation instructions before proceeding!
Downloads are available at: http://build.nethunter.com/nightly/
BEFORE INSTALLING
IMPORTANT: Kali NetHunter requires write access to your data partition!
This means that if your data partition is encrypted, you will need to use the [Format Data] button in TWRP to remove encryption.
This will delete all your data, including internal storage.
You should back everything up first before installing Kali NetHunter.
Samsung Smart Switch Mobile can be useful for this, and allows you to back up your apps to a location on an external SDcard.
Unfortunately it doesn't back up most app data.
The Kali chroot and apps are installed on your data partition (in /data/local/nhsystem for chroot). To initialize the chroot and install Kali Linux, you need to start the Kali NetHunter app.
The generic NetHunter installer will automatically install SuperSU. We try to keep it up to date, but it isn't always.
If you already have SuperSU or another root method installed, please simply delete the supersu.zip from the root of the zip file before installing it.
It's recommended that you restore or flash your ROM's original kernel before installing NetHunter.
It's become apparent that there may be issues with the stock ROM and this kernel, and that it might run best on a Note 7 port.
FULL INSTALLATION STEPS
Install Team Win Recovery Project to your recovery partition.
{
"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"
}
Recommended: If you have a custom kernel or SuperSU installed, restore your stock kernel. (called Boot in TWRP)
This isn't entirely necessary, but you may need to flash the NetHunter kernel again if SuperSU replaces it.
If your data partition doesn't mount in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Once your data partition is formatted, go to [Reboot] -> [Recovery].
Download the kernel-nethunter zip specific to your device.
Without exiting TWRP, transfer the NetHunter kernel installer zip to your device over MTP* and flash it using [Install] in TWRP.
If you wiped your data partition in step 2:
Go to [Reboot] -> [System].
Set up your phone by following the Android setup wizard.
Once it's set up, reboot back into recovery.
For new installations: Download the nethunter-generic-arm64-kalifs zip.
For upgrades: Download the update-nethunter-generic-arm64 zip.
Without exiting TWRP, transfer the NetHunter generic arm64 installer zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
Open the NetHunter app to initialize the environment
You're done!
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TO A NEWER BUILD OR UPDATING YOUR ROM
Follow the installation steps above. NetHunter can be installed over itself as many times as you'd like.
If you don't want to lose your chroot, flash the smaller update-nethunter-generic-arm64 zip instead.
THE KERNEL
The NetHunter kernel for the Galaxy S7 is based on Samsung's OSRC N930SKSU2BPID Note 7 kernel sources.
It has the following changes:
Carefully updated to Linux 3.18.44 (with dirtycow vulnerability patched)
SELinux permissive
F2FS updated to Jaeguek Kim's latest kernel.org f2fs-stable sources
F2FS formatted data partition support
Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
FIOPS IO scheduler as default IO scheduler, SIO available
USB HID Gadget keyboard & mouse support
mac80211 packet injection support
DriveDroid compatibility
Additional drivers built in for the full Kali NetHunter experience
Data partition encryption disabled (not supported by custom kernels at the moment)
Kernel module support, insert your own modules!
CIFS, NFS available through included kernel modules
RAN INTO AN ISSUE OR BUG?
In order for me to help you, you have to at minimum reply with:
The link to the exact zip you downloaded
Your device model
The name of the ROM you're flashing it on
The version and build date of the ROM you're flashing it on
A complete description of your problem
If your issue is with a specific app, it might be better to contact the developer of that app.
For Kali NetHunter bugs/issues, you can open a ticket at: https://github.com/offensive-security/kali-nethunter/issues
If your issue is during the installation (ex. flashing the NetHunter zip), then please collect a TWRP recovery.log for me.
If you found a problem and were able to fix it, and no one's mentioned it in the thread already, it would be kind to state the issue and your fix for others to make use of as well.
You can join me and the other NetHunter developers on IRC at the #nethunter room on freenode to more handily diagnose problems together.
I apologize, but I can't do house calls at this time.
KNOWN ISSUES
USB Keyboard - The keyboard is unusable when using Google Keyboard as your input method. Switch to Hacker's Keyboard.
Reboot after 60 seconds - Sometimes when you boot your device it could reboot after 60 seconds because of a Samsung secure service not responding. Unresolved, but rare, and only happens within 60 seconds of a boot.
DEVELOPMENT
You can see the main branch of NetHunter's development on the Offensive Security GitHub: https://github.com/offensive-security/kali-nethunter
Galaxy S7 NetHunter kernel source: https://github.com/jcadduono/android_kernel_samsung_universal8890/tree/nethunter-6.0
SCREENSHOTS
DISCLAIMER
I am not affiliated with Offensive Security. They seem like cool guys though.
I'm not even a novice when it comes to security and penetration. I'm just a simple system administrator with a passion for breaking Android.
Please restrain yourselves from asking me security related questions.
XDA:DevDB Information
Kali NetHunter for the Galaxy S7, Kernel for the Samsung Galaxy S7
Contributors
jcadduono, The Kali NetHunter team
Source Code: https://github.com/offensive-security/kali-nethunter
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.15.2
Stable Release Date: 2016-11-04
Created 2016-10-06
Last Updated 2016-11-04
I cannot test this today, but i ****in love you !
saphirrot said:
I cannot test this today, but i ****in love you !
Click to expand...
Click to collapse
Yeah I just hope it's all working fine this time Last time I opened a thread for NetHunter on S7 it was a little embarrassing as I didn't own any recent Galaxy phones I had no idea they'd be such a challenge to get custom development going on.
I still haven't exactly tested this, but I do have the Note 7 now so I'm really hoping that everything done to make it work on the Note 7 makes it work on the S7 and S7 edge too... *crosses fingers*
We've got a few issues to fix before an actual release but they're all related to the apps.
1. The NetHunter Terminal app is quite buggy, so you might want to use JuiceSSH local terminal for now. (type su -c bootkali_login to enter Kali environment)
2. The NetHunter app's scripts are all hardcoded for armhf right now. I've actually completed arm64 support in the installer and we can build working arm64 rootfs and install it, just the NetHunter app can't see it yet so we're using armhf on arm64 instead for now.
Anyways, hope to hear some good news from ya! These remaining issues shouldn't take long for us to overcome...
For s7 edge do I have download the arm packages or arm64 packages?
Handeman707 said:
For s7 edge do I have download the arm packages or arm64 packages?
Click to expand...
Click to collapse
you're in the wrong forum, go to S7 edge forum
http://forum.xda-developers.com/s7-edge/development/kernel-kali-nethunter-galaxy-s7-edge-t3475413
this probably isn't something you want to play around with if you don't know if your phone is arm or arm64 :/
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
XanSama said:
Has anyone else been able to get DriveDroid working bootabley (definitely a real word) on this build / Galaxy S7?
I can get the device to show in Windows, but none of the configuration options seem to make it show up as a boot option.
I've tried with both the DriveDroid apk in the nethunter installer, and the latest one from the DriveDroid website.
(P.S. It's not a configuration issue on my laptop as it works with DriveDroid on a Nexus 5. )
Click to expand...
Click to collapse
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
jcadduono said:
I've never been able to boot from DriveDroid CDROM mode but always just mounted ISOs as USB Storage and booted off that, essentially the same as dd'ing an ISO to a flash drive.
Not sure what the Nexus 5 is doing differently... It is kernel related though, as actually mounting this stuff is very trivial and can be done through terminal.
Click to expand...
Click to collapse
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
XanSama said:
Doesn't seem to be working for me in USB RW, USB RO, or CDROM mode on this build; are you saying that the one of the USB modes -is- functioning for you currently? or none at all (same as me?)
Click to expand...
Click to collapse
Used USB RO to install Windows 10 from boot the other day, but that was in UEFI mode
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
ahamed.rafi135 said:
dude pls tell me what is the best rom to have nethunter because i tried a lot of roms it keeps ending in bootloop. also pls tell me whether it works in stock rom...
Click to expand...
Click to collapse
Only tested on latest stock FXXU1BPI firmware
jcadduono said:
Only tested on latest stock FXXU1BPI firmware
Click to expand...
Click to collapse
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
ahamed.rafi135 said:
but when i try flashing on stock it says boot image failed
boot image file xxxxxbits larger
Click to expand...
Click to collapse
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040‬ bytes :/
jcadduono said:
recovery log...
doesnt make sense, by my calculations the resulting image should be close to 40953856 bytes and partition should fit it at *41943040‬ bytes :/
Click to expand...
Click to collapse
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
ahamed.rafi135 said:
yeah dude just gimme a moment flashing stock rom, btw i just did all the setup in bobcat rom it is soooooo lagggy
and i would like to have this on stock rom. And one more thing thanks for your continuous support.
AND MY FIRMWARE IS G935FXXU1APB6 is it ok?
Click to expand...
Click to collapse
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
i have attached the log
jcadduono said:
i have no idea...only tested on FXXU1BP firmware... maybe consider updating?
i will see about maybe removing ffu and signature checker binaries to reduce size, i dont think they are even able to run except by OTAs/stock anyway which are broken by custom kernels
Click to expand...
Click to collapse
also which rom do you recommend?
ahamed.rafi135 said:
also which rom do you recommend?
Click to expand...
Click to collapse
the one that matches your boot image...
i will always recommend stock over anything else though
ok try a build from here instead:
http://build.nethunter.com/test-builds/
update: tested myself and it worked fine, posted new nightly build with changes
it will remove the firmware upgrade service from boot image, which is useless anyway as we can't take OTAs with custom kernels
Hi, I have flashed both of the lastest kernels (kernel-nethunter-herolte-marshmallow-3.15.2-20161024-2241) and (kernel-nethunter-herolte-marshmallow-3.15.2-20161023-0148) but they are still laggy and are having poor CPU performance in geekbench tests. Any fix?
Does it requires an external WiFi adapter to test my internet security or does the WiFi adapter of the S7 can do the job ?
Thank you

KaliLinux NetHunter v1.0 [Kali v2.0/Backtrack 5][athene]

{
"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"
}
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, [URL="https://github.com/offensive-security/kali-nethunter/wiki/NetHunter-Mana-Wireless"]Evil AP MANA attacks[/URL], and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
FIRST THINGS FIRST, SERIOUSLY:
Your warranty was void as soon as you unlocked your bootloader.
Although Kali Nethunter should be safe to use, I am not responsible for whatever happens to your device, router, or whatever networking infrastructure because of YOU misusing the available facilities of Kali.
Remember that while Kali can be absolutely safe, if you handle root access improperly, no one will help you.
Make sure you read all of the info here and have some basic knowledge about networking, kernels and Linux/Unix.
Even if you're able to find a vulnerability on a different host (often called victim) , don't misuse the advantage you have.
Report the issue to the device's owner and the OEM. Do not complain if the attacks aren't working. Security has been ramping up ever since the wikileaks incident and the Edward Snowden thing.
FEATURES:
Kali NetHunter Application
Home Screen - General information panel, network interfaces and HID device status.
Kali Chroot Manager - For managing chroot metapackage installations.
Check App Update - For checking Kali NetHunter Android App updates.
Kali Services - Start / stop various chrooted services. Enable or disable them at boot time.
Custom Commands - Add your own custom commands and functions to the launcher.
MAC Changer - Change your Wi-Fi MAC address (only on certain devices)
VNC Manager - Set up an instant VNC session with your Kali chroot.
HID Attacks - Various HID attacks, Teensy style.
DuckHunter HID - Rubber Ducky style HID attacks
BadUSB MITM Attack - Nuff said.
MANA Wireless Toolkit - Setup a malicious Access Point at the click of a button.
MITM Framework - Inject binary backdoors into downloaded executables on the fly.
NMap Scan - Quick Nmap scanner interface.
Metasploit Payload Generator - Generating Metasploit payloads on the fly.
Searchsploit - Easy searching for exploits in the Exploit-DB.
3rd Party Android Applications (WIP)
NetHunter Terminal Application
DriveDroid
USB Keyboard
Shodan
Router Keygen
cSploit
Remember that there might be many other exploits and attack features available online, the ones mentioned above are officially documented by Kali. Secondly, not much support will be possible regarding the attacking since not everyone will have the same opportunities.
DOWNLOADS
Sourceforge might show this file as Malware for obvious reasons, but open the filename and choose the directlink. I will contact their support team for this soon, meanwhile you can also check the Android File Host mirror.
1. For N Custom ROMs :
Sourceforge folder
Android Filehost
2. For stock N:
3. For MM Custom ROMs:
4. For Stock MM:
INSTALLATION
IMPORTANT NOTE: Kali NetHunter is NOT an Android ROM, but it is an overlay ( you have to flash it above android).
The builds currently provided are to be used on Nougat based custom ROMs ONLY. (which use the LineageOS kernel)
Installing it on a ROM which uses the LineageOS 14.1 kernel. (examples include all of our N custom ROMs like Lineage, AEX, AICP, AOKP, DU ) :
1. Make sure you are running the latest available build of the ROM you have installed.
2. Reboot to TWRP.
3. Make sure you backup Boot, System and Data partitions, just incase you want to remove Kali, you can restore it.
3. Wipe Cache and ART Cache (Formerly known as Dalvik Cache). Do NOT wipe your data partition.
4. Install the zip file.
5. Reboot to System.
POST INSTALLATION:
1. Open the NetHunter App and start the Kali Chroot Manager.
2. You might want to download the real packages which might be around 400-500 MB in size.
3. Set up Hacker Keyboard.
4. Configure Kali Services, such as SSH.
5. Set up custom commands.
6. Initialize the Exploit Database.
BUGS:
Please read the help thread before you point out issues here. It has been created specifically to help new users to adapt to custom roms easier. Before you post your issue, please check if it has already been reported and if a fix has already been mentioned.
SCREENSHOTS:
https://vimeo.com/132329259
https://youtu.be/yV6AzqgdBo4
IMPORTANT LINKS:
1. My build of TWRP
2. KaliLinux NetHunter Github Wiki
3. KaliLinux NetHunter Website
4. Source for athene: https://github.com/tywinlannister7/nethunter-devices
XDA:DevDB Information
KaliNethunter for athene, ROM for the Moto G4 Plus
Contributors
tywinlannister7 @keerten
Source Code: https://github.com/offensive-security/kali-nethunter
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest stock Nougat firmware
Version Information
Status: Stable
Created 2017-07-20
Last Updated 2017-07-20
Reserved
Reserved
Will it work on AOSP CAF?
aravindmj said:
Will it work on AOSP CAF?
Click to expand...
Click to collapse
It uses the LineageOS kernel, so YES. :good:
First off thank you for this second how do we add HID devices to kali
khaoticking said:
First off thank you for this second how do we add HID devices to kali
Click to expand...
Click to collapse
You're welcome.
The NetHunter HID Atacks turn any device and its OTG USB cable into a pre-programmed keyboard, able to type any given commands. HID here refers to the Human Interface Devices like your keyboard mouse touchpad etc. The mounting process should be similar like you do on any android device. If you're not sure that kali isn't detecting the device, you might want to try running this command in the terminal:
Code:
lsusb
tywinlannister7 said:
You're welcome.
The NetHunter HID Atacks turn any device and its OTG USB cable into a pre-programmed keyboard, able to type any given commands. HID here refers to the Human Interface Devices like your keyboard mouse touchpad etc. The mounting process should be similar like you do on any android device. If you're not sure that kali isn't detecting the device, you might want to try running this command in the terminal:
Click to expand...
Click to collapse
Kali doesn't detect any HID devices when trying to run the hello world duck script it won't type anything
Can you give me the link to the kernel sources...
khaoticking said:
First off thank you for this second how do we add HID devices to kali
Click to expand...
Click to collapse
The Android HID patch as mentioned by pelya has not been applied to the kernel sources. That's why there is no HID Interfaces...
If anybody knows how to custom compile a kernel then one can look at @pelya guide how to patch it..
Link to kernel source of tywinlannister https://github.com/tywinlannister7/elementalx_kernel_motorola_msm8952
Link to patched kernel sources Jleeblanch but it is not compiling he is the official maintainer of Resurrection remix for Athene "the Kali branch"
https://github.com/Jleeblanch/android_kernel_motorola_msm8952
If anybody looks into the matter we can get fully functional Kali nethunter...
Thanks in advance..:good:
Does it work on Moto g4 plus and how to remove the Kali overlay latter. Thanks
Sobhan Bhuyan said:
Does it work on Moto g4 plus and how to remove the Kali overlay latter. Thanks
Click to expand...
Click to collapse
This is in the G4 Plus forum. That usually means it works on the G4 Plus.
zeomal said:
This is in the G4 Plus forum. That usually means it works on the G4 Plus.
Click to expand...
Click to collapse
I flashed it and got an error in twrp ( named error one or something) and then there were no overlays to be seen inside. Later I knew that caller ID is not visible while calling or being called. Restored then. Pls advice. Should I flash again.
Managed to get the error message from twrp. Pls advice
Sobhan Bhuyan said:
Managed to get the error message from twrp. Pls advice
Click to expand...
Click to collapse
As it says in the TWRP error, did you boot and set up your device, then reboot to flash the Kali overlay? From the opening post, this appears to flash over existing custom ROMs.
What ROM are you attempting to flash Kali over?
Sobhan Bhuyan said:
Managed to get the error message from twrp. Pls advice
Click to expand...
Click to collapse
First of all a ROM must be installed and on top of that only nethunter should be flashed(so only it is called overlay ROM ,something has to be underneath it...:good: )
echo92 said:
As it says in the TWRP error, did you boot and set up your device, then reboot to flash the Kali overlay? From the opening post, this appears to flash over existing custom ROMs.
What ROM are you attempting to flash Kali over?
Click to expand...
Click to collapse
I m currently on ressurection remix ROM ,device XT1643
So you mean that after wiping cache I must set up device as new first then reboot and flash the overlay. Ok I will try and let you know
Sorry to bother, but what about ElementalEx kernel? Is it compatible, untested, or uncompatible?
Also, does it need a fresh ROM flash, or could it be used over an already flashed, rooted and used ROM with EX ?
Will it work for Viper OS 7.1 nougat?
What is the difference between this version and version 3.0?
'

[ROM][12L][OFFICIAL] crDroid 8.x FOR MOTO ONE (DEEN)

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
crdroid_features/README.mkdn at 12.1 · crdroidandroid/crdroid_features
our main features (why you love us). Contribute to crdroidandroid/crdroid_features development by creating an account on GitHub.
github.com
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
flash crDroid recovery like every other recovery on this phone
Format data
Flash the ROM zip either from adb sideload or internal storage
Reboot in to recovery
Format data
Flash GApps (If wanted)
Reboot and enjoy!
Update installation:
Reboot to recovery
Flash the ROM in twrp or use adb sideload
Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_motorola_deen
Download:
ROM https://crdroid.net/deen
Changelog: https://crdroid.net/deen/8#changelog
Known issues:
- Dolby broken
- Adb sideload
- Ota Update
- You tell me
Visit official website @ crDroid.net
crDroid Deen Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
20220810
- ADB: Wireless debugging: turns off frequently
- ADB: Wireless debugging: No debuggable process in Android Studio (but other devices works OK); App Inspection & Profiler not working
- ADB: Enable USB debugging -> device restarts (kernel panic?)
In the Logcat I got something like this:
Code:
I/adbd (533): opening control endpoint /dev/usb-ffs/adb/ep0
E/adbd (533): failed to write USB strings: No such device
20220807
- UPDATE: OTA: not working 20220807->20220810: Could not change profiles (https://paste.crdroid.net/J4u9b6). Is it a problem with permissions or problems caused by Magisk's changes into the system?
- UPDATE: sideload update 20220807->20220810 infinity boot loop with Magisk (without Magisk no problem)
- GAPPS: Device is not certified by Google (to solve this problem just follow: https://www.google.com/android/uncertified/)
But this ROM is still awesome! Thank you so much.
I'm trying to fix the root and debug issues
This looks awesome. I'm waiting for the new display to arrive and I'm rocking this phone back. Would this rom enable VoWifi? Or does it need certain hardware for vowifi?
Will come a Version in near future, that has no issues with OTA functionality?
Last 2 updates did not work with OTA. In Telegram Group Deen Brasil was mentioned, that a server is needed to make twpr download possible, before update is installed, cause there is no recovery patition.
Is there not way to add a recovery pation?
Hi their I was wondering when flashing this rom are these steps required? Like the pixel ROM for the Deen:
1. Download Rom
2. Download TWRP
3. fastboot getvar all
4. fastboot boot twrp
5. Do full wipe
6. Format Data
7. Flash ROM
8. Reboot to Bootloader
9. fastboot getvar all
10. If fastboot getvar all (current-slot label) from step 3 equals this from step 9 change the slot to opposite, if a then b if b then a, command is fastboot --set-active=SLOT
11. Boot to TWRP again
13. Flash Magisk (optional)
14. Reboot to system
I tried booting into recovery but i got this error
Edit : That was a long time ago.
tldr - im stupid and didnt unlock the bootloader properly.
Tobyash said:
I tried booting into recovery but i got this error View attachment 5744289
Click to expand...
Click to collapse
Looks like your bootloader is locked.
baseline2016 said:
Looks like your bootloader is locked.
Click to expand...
Click to collapse
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.
Tobyash said:
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.
Click to expand...
Click to collapse
Maybe you have to run the command in Windows as an administrator. And the command is fastboot boot recovery c:/....img
I followed the steps I mentioned in my post #6 and the ROM works excellent.
How do you update with twrp? It gives me error no matter what slot I choose. CrDroid recovery or OTA doesn't work.
there is a problem, the microphone is recording very low audios, with this crdroid rom.
Hello,
Gapps link is broken. I tried NikGapps but it stuck my boot...
Could you please fix the link?
Thanks in advance!
EDIT:
Found it here, just in case anyone is wondering:
Release Squeak Releases · ChonDoit/TheGappsInstaller
20220607 | Merged June changes | Unified some Overlays | Updated apns list
github.com
I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?
whats-in-a-name said:
I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?
Click to expand...
Click to collapse
Solved by installing stock and from there installing lineage-18.1-20220523-UNOFFICIAL-deen.zip
Hi. I'm trying to build a user version of your rom. The build works but I get an error during update (sideload). This happens at the end, after the vendor is flashed and during `Running backuptool scripts`
Code:
Update_engine_sideload [ERROR: postinstall_runner_action.cc] Failed to set backuptool context
I wonder why this could be ? Perhaps I have not reconstructed your manifest correctly?
note: I'm flashing from Recovery using a USB UTG stick and also flashing from TWRP using the same stick..
I have been using the Motorola One with this rom as my main phone for the past day or two, so far ive been enjoying it! Im hoping for more updates in the future.
Good afternoon,
I wanted to share with you my experience trying to install rom 20230414 for the Moto one tx 1941-3.
Although I was able to install and use the previous version without problems, it was impossible for me with this latest version since it stuck to the android logo. It doesn't flash or reset, it just stays there.
I find this system incredible so I would love to use the update
Thank you

[ROM][UNOFFICIAL][13.0][OTA][Signature Spoofing][Open Source][Encryption] LineageOS 20 for Galaxy S10e/S10/S10+/S10 5G Exynos

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/Linux4/android_kernel_samsung_exynos9820/tree/lineage-20.0
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.
Features
SELinux enforcing
AES-256-XTS FBE encryption
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
You tell me
Likely more
My English is not very good, so I don't understand some things. My phone is Samsung Galaxy S10 (SM-G973F), Android 12, (HVG4). The bootloader is unlocked. I am confused by these instructions, and I would like to try this.
ZmisiS said:
My English is not very good, so I don't understand some things. My phone is Samsung Galaxy S10 (SM-G973F), Android 12, (HVG4). The bootloader is unlocked. I am confused by these instructions, and I would like to try this.
Click to expand...
Click to collapse
maybe to write what you don't understand
I don't understand:
Any Q, R or S based firmware installed on your device.
Flash lineage recovery (Get from here)
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
where i can find gapps 13 android?
kolyan2282 said:
where i can find gapps 13 android?
Click to expand...
Click to collapse
Google apps | LineageOS Wiki
wiki.lineageos.org
Thanks so much for working on our device, so exited to see this new version on Android on the s10, I will wait though for it to get more mature.
DOGASP said:
Google apps | LineageOS Wiki
wiki.lineageos.org
Click to expand...
Click to collapse
Thanks... Should I try the one for Lineage 19? Ie (12L)?
Can few screenshots of the interface of this android?
ZmisiS said:
Can few screenshots of the interface of this android?
Click to expand...
Click to collapse
It looks mostly the same as AOSP Android 12-based ROMs.
ThePS4Gamer said:
It looks mostly the same as AOSP Android 12-based ROMs.
Click to expand...
Click to collapse
I never had AOSP installed, and I couldn't get to the images.
Has anyone installed this ROM? If it is, please write something about it for those of us who intend to install it. I hope that's not a problem?
I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.
good morning, yes.
I reverted to stock ROM.
ZmisiS said:
I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.
Click to expand...
Click to collapse
you can't install gaaps A12.1 on OS Android 13, i.e. you can, but it won't work, you need gaaps 13
ZmisiS said:
I installed this and I need some samsung apps as well as google apps. I installed Gaaps 12.1. I don't have Google Play Store.
Click to expand...
Click to collapse
unfortunately, you cannot have both on the AOSP system, you install gaaps for Google services, and you cannot run Samsung applications on AOSP or a pure Android system
@Linux4 will it work on G977N ?

Paranoid Android Topaz Stable 1 - realme X50 Pro 5G

{
"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"
}
We are very excited to announce the stable release of Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* FOD might not work correctly on first boot, simply reboot and register fingerprint again.
Requirements
Make sure you've latest platform tools for Android.
Make sure you've latest RealmeUI 3.0 firmware flashed before flashing the ROM.
Make sure you've latest TWRP 3.7.0 for FBEv2 flashed before flashing the ROM.
Only RMX2071, RMX2075 and RMX2076 are supported. The realme X50 Pro Player is not supported.
Download
You can always get our Stable builds from our website Paranoid Android website
Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions
Recovery Method
Reboot to Recovery.
Format data.
Install PA zip package.
Reboot to system.
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Paranoid Android Community for realme SM8250 (Telegram)
Cheers and #StayParanoid!
Reserved #1
Reserved #2
New build will come as soon as possible, main PA team told me to make the thread now.
We are live!
https://paranoidandroid.co/bladerunner
Yeah, just on time!
Cool stuff guys.
Have anyone tried it yet?
aleksandar.1 said:
Cool stuff guys.
Have anyone tried it yet?
Click to expand...
Click to collapse
Yep, everything works its muchhhh better than crappy realme ui
but make sure to be really on latest realme ui firmware
Hi,
I have a Chinese RMX2071 (Android 12) with recovery for Android 12 (v3.6.2_12). I tried to upload Paranoid Android but it shows a message that it is not for my model. Can I force install? Please help..
Any one tell how to flash the rom for 2 options for fastboot options or recovery options , how to install,any one tell me the proper installation step by step
Pasupathiraj0 said:
Any one tell how to flash the rom for 2 options for fastboot options or recovery options , how to install,any one tell me the proper installation step by step
Click to expand...
Click to collapse
I see you know each other. I am a beginner. Write which files and in what order to upload so that the phone accepts paranoid android. Thanks in advance.

			
				
I am very proud of this. thank you very much! I think that this is the only existing rom for this device (RMX2075) and it is amazing that someone is doing it because I think that Realme is leaving us alone
aleksandar.1 said:
Cool stuff guys.
Have anyone tried it yet?
Click to expand...
Click to collapse
Hi, thanks to developer for the first ROM on x50 pro, but ... I had installed on my rmx2075 and was very disappointed - very poor customization options, no always on display, and camera works with only one sensor, (better don't talk about camera app). After one day came back to stock (was not so ease...) .
dzenius said:
Hi, thanks to developer for the first ROM on x50 pro, but ... I had installed on my rmx2075 and was very disappointed - very poor customization options, no always on display, and camera works with only one sensor, (better don't talk about camera app). After one day came back to stock (was not so ease...) .
Click to expand...
Click to collapse
Do you use Telegram tutorial ?
Wipe all in TWRP, flash stock ROM, wipe data, dalvik, cache.
TheMalachite :​Thanks for your work.
Unfortunately I've some issues :
- Fingerprint registered but not recognized, even after reboot, deleting, recreating).
- USB connection stop working (all parameters greyed out) > Solved by activating USB debugging
Sorry, I'ven't logcat configured...
Battosai94 said:
Do you use Telegram tutorial ?
Wipe all in TWRP, flash stock ROM, wipe data, dalvik, cache.
TheMalachite :​Thanks for your work.
Unfortunately I've some issues :
- Fingerprint registered but not recognized, even after reboot, deleting, recreating).
- USB connection stop working (all parameters greyed out) > Solved by activating USB debugging
Sorry, I'ven't logcat configured...
Click to expand...
Click to collapse
after few not successful times flashing with official realme flash tool (https://www.xda-developers.com/real...ool-for-installing-coloros-realme-ui-updates/)
I use this flash tool. (Windows version give a positive virus alert, so must unable antivirus app and after revert pc to earlier restore point (just in case) )
SrCDA said:
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool.
THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED​Features​
soft unbrick
install stock firmware
switch device region
Credits​
italorecife
bkerler oppo_decrypt
All contributors
Installation​Install​Linux (in the example below I will use ubuntu)​Install adb & fastboot and simg2img​
Code:
sudo apt-get install android-tools-adb android-tools-fastboot simg2img
Install python >=3.8, git and other deps​
Code:
sudo apt install python3 git python3-pip
Grab files​
Code:
git clone https://github.com/italorecife/OppoRealme-OFP-Flash
cd OppoRealme-OFP-Flash
pip3 install -r requirements.txt
Windows​Install the adb & fastboot drivers.
Install python + git​
Install python 3.9 and git
WIN+R
Code:
cmd
Grab files and install​
Code:
git clone https://github.com/italorecife/OppoRealme-OFP-Flash
cd OppoRealme-OFP-Flash
pip3 install -r requirements.txt
Usage​Put the .ofp file in the same folder as the program, then put your device in mode fastboot to start flash.
Run:
Code:
python3 flash.py
if you have windows OS you can run normally by double clicking, and you have linux use terminal.
DOWNLOAD
Source Code​
Click to expand...
Click to collapse
Thanks. Does it work in my case? What ofp should I download and try to flash? Global for rmx2071 or global for rmx2076? The phone is rmx2071 (china rom). As you can see in the images I uploaded, it asks for rmx2076L under twrp.
or paranoid?
it works great on my RMX2071 the only problem i have is play protect certification
Pasupathiraj0 said:
Any one tell how to flash the rom for 2 options for fastboot options or recovery options , how to install,any one tell me the proper installation step by step
Click to expand...
Click to collapse
If you going for recovery option make sure you have latest TWRP 3.7.0 i used this one https://www.pling.com/p/1945031/

Categories

Resources